 STEP FOR RETURN ORDER

 Item category REN

 Billing relevance – Order releted billing
 Pricing-standared
 No credit limit active
  Cash sale and rush order-

What are the differences between cash sales and rush order?

1) Cash sale : in this delivery automatically happen when you save the sales order. After that you have to
give an invoice to the customer.

2) Rush order. Here also delivery automatically happen when you save the sales order. But the difference is
you can send invoice after some time but the delivery should happen immidately.

If you goto any super market first, you pick up the item and then pay the bill and then you will get the bill,
this process is cash sales.

Cash sales is order related billing whereas RO is delivery related.

Cash sales is not relevant for availability check as you will be picking the goods whereas RO is relevant for
availability check.

Cash sales is also not relevant for credit management whereas RO is relevant credit management.

Cash sales uses RD03 as output which immediately prints the invoice whereas RO uses standard output
RD00.

Cash sales has one time customer account group where as RO normally doesn't.

For cash sales order type is BV or CS and for RO it is RO

Cash sales triggers petty cash a/c where as in RO customers account is debited.

Delivery and settlement will be done immediately in cash sales where as in RO only delivery will be done
immediatrly.

Rush Order/Cash Sales –

Rush orders and Cash sales are sales document types that are used in the sales from plant process or when
the customer needs to pick their goods immediately from the warehouse.

In the sales document type, the following changes have to be made for rush order/cash sales –

 order type – RO/CS

 shipping conditions – immediately
 immediate delivery – X
 lead time in days – not to be specified
 delivery type – LF/BV
 billing type – F2/BV
 item category – TAN/BVN
 schedule line category – CP/CP
In case of rush orders and cash sales once the goods have been withdrawn from the warehouse, picking and
posting goods issue can begin.

In case of rush orders, when you create the billing documents the system prints the invoice papers and sends
them to the customer.

But in case of cash sales, an order related billing index is generated automatically. This updates the billing
due list. Billing type BV is created, while the billing due list is being processed and the system does not print
invoices during billing for a cash sale.

In cash sales when you save the order, the system automatically generates a cash receipt that can be given to
the customer as an invoice and the goods are picked up from the warehouse immediately by the customer.
You control the output with output type RD03, contained in the output determination procedure for order
type CS.

Process Flow :

 Create Cash Sales order using VA01 and Upon Save, outbound delivery is created automatically
 Goto T.Code VL02N or VL03N to change or display outbound delivery
 Goto VL02N and perform PGI
 Goto VF01 to perform billing document

Rush order
This process used when a credit customer requires immediate delivery.
In this case below are the points to be remembered :

 Normal credit customer is used during sales order processing and Delivery automatically happens
when you save the sales order.
 Rush order document and its relevant item category is relevant for credit check
 Rush Order uses delivery related billing and uses standard delivery type 'LF' for delivery
processing
 Rush Order is relevant for picking
 Rush Order uses standard output RD00.
 Standard Billing type 'F2' is being used and Customer account will be debited after commercial
invoice posting
 Cancellation document type 'S1' is used for cash sales

Process Flow :
 Create Rush order using VA01 and Upon Save, outbound delivery is created automatically
 Goto T.Code VL02N or VL03N to change or display outbound delivery
 Goto VL02N and perform PGI. Goto VF01 to perform billing document
Fig.Tcode and tables for OTC cycle
 Third party process-

Third party process is an integration between SD + MM

Scenario 1 :- Most of the companies will not manufacture all the products which they are selling or have in
their product portfolio, they will manufacture some products and for remaining products they will do third
party process.

Scenario 2 :- In some scenarios even though company manufacture the products and if stock is not available
or if there is some problem in manufacturing unit then they go for third party process.

Third party process: - when our customer place order for third party material and when we create 3rd party
sales order in SAP, then system automatically generates PR and PR will converted to PO and PO will be send to
vendor and vendor delivers the goods to customer and vendor will send the invoice to company and company
will raise invoice to customer

 Without shipping notification in third party process, is a standard third party process, in which vendor
will send immediate invoice and based on MIRO we raise invoice to customer.

 We do third party with shipping notification, if vendor is not ready to send the invoice
immediately, if vendor is not sending the invoice then we cannot raise invoice to customer because
we don‟t know that how much quantity vendor has delivered to customer.
 In this situation we ask vendor to send shipping notification to the company which consists of
material details and quantity details which vendor has delivered to customer. Then we can do MIGO
in SAP and based on MIGO quantity we raise invoice to customer.

Important points in Third party process:- Item Category TAS

1. For third party material maintain “Item category group” as [BANS] and maintain material type as
„HAWA.
Item category group BANS will help to determine item category „TAS‟ in sales document.
2. Third party item category determination OR + BANS + Blank + Blank = TAS.
3. Billing relevance „F‟ standard. F means order related billing status according to MIRO.
If we want 3rd party with shipping notification then we maintain billing relevance as „G‟ and G
means order related billing status according to MIGO. Billing relevance „F‟ controls that in 3rd party w/o
shipping notification if MIRO is not created then system will not allow to create invoice to customer. Billing
relevance „G‟ controls that in third party with shipping notification if MIGO is not created then system will
not allow to create invoice to customer.
4. Create PO automatically – In standard process of 3rd party when we create sales order, system
automatically generates PR but if we want system to generate direct PO automatically then check this field.
Along with ALE data for purchases order in sales organisation.

Controls in CS (Schedule line category)

5. Order type “NB” – it will help to generate purchases requisition automatically in the background while
creating sales order in third party process.

6. Item category – purpose of item category in schedule line category :- like sales documents, MM
documents also require item category information while creating PR manually. User will assign item
category manually , but in third party process we are generating PR automatically in the background so we
are passing item category information from schedule line category to PR.

7. Item category [5]: - item category [5] controls that even we do MIGO in third party with shipping
notification system will treat it as dummy MIGO and stock will not be update.

8. Account assignment category [1]: - It controls that whether to generate inventory accounting document or
not while doing MIGO and PGI (this field controls the cost should be assigned to any special cost object or
not).This also helps to pass on customer information from order to PR….

9. In copy control between order to invoice (OR – F2) TAS has billing quantity „F‟ and it will help to copy
the quantity from MIRO to invoice while creating invoice to customer in third party process.

If we want third party process with shipping notification then we maintain billing quantity “E” which helps
to copy the quantity from MIGO to invoice while creating invoice to customer in third party process.
 Stock Transfer Order (STO)

Transferring the stock from one plant to another plant within a company. It can be plant to depot or depot to
depot.

STO 2 Step Process

 In STO two step process 1st receiving plant will raise the PO to supplying plant, and then supplying
plant will do delivery with reference to PO.

 When we do delivery in supplying plant then stock will be reduced from supplying plant and stock
will be displayed as stock in transit in receiving plant.

 The control is in movement type [641]. When the goods reached at receiving plat then they do
MIGO, and when they do MIGO the actual stock updates till then it shows as stock in transit.

PO type in STO process is [UB]

Delivery type in STO process is [NL]

Delivery item category in STO process is [NLN]

Delivery item category determination is NL
NORM
V
Blank
NLN
 Interview Questions for STO process

Q.1. Explain STO process?

Ans. In STO two step process 1st receiving plant will raise the PO to supplying plant then supplying plant
will do delivery with reference to PO and do proforma invoice, when we do delivery in supplying plant then
stock will be reduce from supplying plant and stock will be displayed as stock in transit in receiving plant.
The control is in movement type [641]. When the goods reaches to receiving plat then they do MIGO and
when they do MIGO the actual stock update till then stock in transit.

Q.2. What is the difference between one step and two step process?

Ans. In two steps MIGO is done and in one step MIGO is not required.

Q.3. In STO process while creating PO i want to create delivery automatically in background. Where is the
control?

Ans. With the help of configuration that activate automatic delivery creation with order type UB and plant
and also activate automatic delivery creation PO type & shipping point.

Q.4. Where is the control that whether to go one step or two step?

Ans. Check one step in assign document type 1 step procedure under delivery tolerance.

Q.5. What is PO type for STO process?

Ans. UB.

Q.6. I want to copy PO price in STO performa invoice. How to do this?

Ans. Maintain price source as [A] in VTFL

Q.7. Do we have any copy control between from PO to delivery?

Ans. Yes, we have control between [DL – NL] in copy control.

Q.8. What is delivery type of STO process?

Ans. [NL].

Q.9. What is the schedule line Category for STO process?

Ans. [NN].

Q.10. What is the movement type for one step and two steps?
Ans. 1 step – 647, 2 steps – 641.

Q.13. What is the inventory accounting document generate in STO process?

Ans. Stock inward movement A/c ........Dr. To, stock outward A/c........Cr.

Q.14. How delivery item category determine in STO process?

Ans. NL + NORM + V + Blank = NLN.

Q.15. What is the configuration required for STO process?

Ans. 1.Define shipping data for plants, 2. Assign delivering type & checking rule and 3. Assign document type 1
step procedure under delivery tolerance.

Q.16. Can i restrict the user to increase the quantity in delivery in STO process?

Ans. No, in STO process there is no over delivery tolerance provision, only under delivery tolerance.

Q.17. What scenario shipping data will not determine?

Ans. If STO configuration is not in place and shipping point determination is not in place in delivering plant.

Q.18. How pricing procedure determine in STO perform invoice?

Ans. Based on document pricing procedure [T].

Q.19. In STO process even though we create delivery with reference to PO. How system is determining
movement type information?

Ans. Default order type [DL].

Q.20. In STO process what is the need of creating receiving plant as customer?

Ans. For ship to party address.

 Also following types of Stock Transfer options are available:
a) Manufacturing Plant to Depot
b) Depot to Depot
c) Depot to Manufacturing Plant
The following covers the total config and cycle of STO:
 Create a vendor for the company code of receiving plant, using account group :0007
using T-Code XK01.
 2. Assign this vendor to Delivering plant
Go to XK02 >Purchasing view>Extras>Add. Purchasing data>Plant
 3. Create internal customer with the sales area of the vendor. Go To XD01
 4. In Pricing procedure determination relevant to STO, assign document Pricing
Procedure and customer pricing procedure appropriate for STO to get the pricing in
the invoice.
 5 . Maintain condition records for the relevant pricing condition.
 6. Some more setting for STO: Go to MM> Purchasing > Purchase Order > Set up
STO> define shipping data for plants > Go to Receiving plant >assign customer here
& Supplying SA (for billing) to Receiving plant here
 7. Go to MM> Purchasing > Purchase Order > Set up STO> define shipping data
for plants > Go to Supplying plant and assign the sales area of receiving plant.
 8. Go to MM> Purchasing > Purchase Order > Set up STO> assign delivery Type &
Checking rule
 Assign the delivery type to document type. In this case, Delivery type NLCC is
assigned to Document type NB
 9. Go to MM> Purchasing > Purchase Order > Set up STO>Assign document Type,
One step Procedure, Under delivery tolerance
Assign the document type NB to supplying plant and receiving plant
 10. After all settings , Create the STO using T-Code:ME21N and Save.
 11. Create Delivery :VL10G
Click on the Background Button after selecting line item
A message is flashed : See log for information> next Click on Log for delivery creation Button
>click on line item>click on document button to get Delivery document No
 12. Picking, PGI:VL02N
 13. Billing:VF01.
 Use this link:
 http://help.sap.com/saphelp_45b/helpdata/en/4d/2b916b43ad11d189410000e829fbbd/fram
eset.htm
Thanks & Regards,
Navahsek

 Share
  What are the components of GST?

There are 3 taxes applicable under this system: CGST, SGST & IGST.

 CGST: Collected by the Central Government on an intra-state sale (Eg: transaction happening
within Maharashtra)
 SGST: Collected by the State Government on an intra-state sale (Eg: transaction happening within
Maharashtra)
 IGST: Collected by the Central Government for inter-state sale (Eg: Maharashtra to Tamil Nadu)

In most cases, the tax structure under the new regime will be as follows:

New
Transaction Old Regime
Regime
Sale within the CGST + VAT + Central Revenue will be shared equally between the Centre and
State SGST Excise/Service tax the State
There will only be one type of tax (central) in case of
Sale to another Central Sales Tax + inter-state sales. The Centre will then share the IGST
IGST
State Excise/Service Tax revenue based on the destination of good.
 Pricing scenario for interview

 The clients‟ requirement is any order if the total document value reaches to 10,00,000/- then they
want to propose 20,000/- discount.
Solution:- For group condition total document value, we need to create a condition table with the field only
sales organisation. (In this condition material will not be taken).
1st step – Create new condition table with sales organization field .
2nd step – Create access sequence and placed the condition table (ZGRP). Go to V/07 go to new entries
Create [ZGRP] [group condition] go to new entries no [10] [350] exclusive check save it.
3rd step – Create new group condition type
Copy K004 condition type ZGRP access sequence (ZGRP) change the calculation type [B] Check group
condition maintain group condition routine [1] check rounding difference
Comparison scroll down and go to scale basis as [B-value scale] save it.

End. Page 189.

2.
Condition update: - Restricting the condition record up to particular quantity or value or number of orders. It is
called as condition update.

 The clients requirement is whenever they launch new product they want to offer 6000/- discount to
the 1st 10 Lakh quantity.
In condition update concept SAP restrict the number of orders to 3(This is a GAP) Configuration for
condition update
1st step –
Create new discount condition type, a copy of K004 ZUPP and check condition update save it.
2nd step –
Place the condition type in pricing procedure [ZVAA01] or [ZVAA02] and place ZUPP save it. When
pricing procedure [ZVAA01]

3rd step – Maintain condition record

Condition type [ZUPP] ZDOMZ1vaxin15006000/-INR select the condition record and go to additional data
(If any condition type if we check condition update then we get extra 3 fields in condition record that we call
is as limit for pricing)
Maximum condition value [ ]

Maximum no. of order [ ] (GAP IN SAP)

Maximum condition base value [1000] enter save it.

4th step – go to OVKK and check pricing procedure i.e. [ZVAA01] or [ZVAA02] [YPR0] it should be.
Go to VA01 and create an order and check condition update when pricing procedure is [ZVAA01].
3.

 Client‟s requirement is any customer if he purchase slow moving items then they want to offer 20
days extra credit period.
Ans. Create one new condition type a copy of KO04 Placed the condition type in pricing procedure in the
last and make it statistical save it.
Maintain condition record: VK11 maintain material X, Y, Z and Rs. 1,1,1 go to additional data one by one
and maintain additional value days [20] save it.
MATERIAL DETERMINATION
Material Determination uses cond tech to swap one material for another in a sales order, when certain
conditions apply. Substituting one product with another product is called material determination. The
product is only substituted during the specific period.

You can use material det if you want the system to automatically substitute, for e.g.:
- Customer specific product numbers with your own material numbers.
- International article numbers (EAN's) with your own material numbers.
- Substituting discontinued materials with newer materials
- Seasonal products.

SPRO- IMG- SD- Basic Functions- Material Determination-

- Maintain prerequisites for material determination
- Assign procedure to sales doc types: determination rule
- Define substitute reasons: OVRQ

Create Condition Table: select 'Material Entered' from field catalog & save
Maintain Access Sequence: go to new entries, give 4-digit code with descp. Select the 4-digit code and go to
Accesses and fill access no, table, descp, requirement (blank). Select the line and go to Fields and save.
Maintain Condition Type: go to new entries, give the same 4-digit code as given to acc seq. Assign acc seq
to cond type and mention valid from and valid to date.
Maintain Procedure: go to new entries, define 6-digit code with descp. Select the 6-digit code and go to
control data and assign cond type to the procedure.
Assign Procedure to Doc Type: assign sales doc type to the 6-digit procedure.
Define Substitution Reasons: go to new entries, define 4-digit code with descp. In substitution reasons you
will also find entry, warning, strategy & outcome.
- Entry: check this field if you want the original material and not substitutes to be printed in the output.
- Warning: check this field & a warning message is displayed before material is substituted
- Substitution Strategy: controls whether product selection should occur automatically in the
background or whether the alternative materials should be offered for selection in a dialog box.

- Outcome of substitution: controls whether the outcome of product selection should replace the original
entry or whether it should be recorded as a sub item of the original entry

Condition Records: VB11, enter original material, substitute material, substitution reason & validity. For
multiple items select product & click on 'Alternative Materials Button'.
o Leave the warning & strategy indicators blank, or you will not be able to perform automatic product
selection based on ATP.
o In outcome of Substitution, you must choose either A or B. Do not leave this field blank. One of the
most important decisions that you have to make about the product selection process is whether or not
substitutions determined in the order are to be redetermined in the delivery.
How to Create Partner Function & Partner Determination: SAP VOPAN

What is Partner Function?

Partner function is two-character identification key that describes the people and
organization with whom you do the business, and who are therefore involved in
transaction. Here is some standard Partner Function for customer-

1. Sold-to party
2. Ship-to party
3. Bill-to party
4. Payer

What is Partner Determination?

The Partner and business partner term in SAP SD refers to parties with whom you do
business. Each business partner has specific role. E.g. Sold-to party - Business Partner
who order the goods / Services. The Partner Determination can be done in three steps-

Step 1 Define Partner Function

Step 2 Create Partner Determination procedure by grouping Partner function.

Step 3 Assign the partner determination procedure to respective partner object.

Step 1 - Define Partner Function:

1. Enter T-Code VOPAN in Command Bar.

2. Select Customer Master Partner Object
3. Click on Change Button, Partner Determination Procedure Screen appear.
1. Click On New Entries Button.

1. Enter Partner Determination Procedure and name.

2. Double click on Partner Function node - Screen as below appear.

3. Click on New Entries Button.

4. Enter Partner Function Detail

Enter Partner Function / Name / Partner Type.

Field Name Desc

Partner Function Two-character unique identifier for

each partner function.

Name A meaningful description for this

partner function.

Partner Type It tells whether the partner function

is for a customer (KU), a vendor
(LI), a contact person (AP), and so
on.

Step 2 - Partner Determination procedure by grouping Partner function.

1. Click on Partner Function in procedure node.

2. Enter Partner Det. Procedure / Partner function / Name.

Step 3 - Assign the partner determination procedure to respective partner

object. We are creating partner function for customer, so here partner object is
customer and assign to Account Group.

Partner Object Assign to

Customer Account Group

Sales Document Header Sales Document Type

Sales Document Item Item category Type

Delivery Header Delivery Document Type

Shipment Header Shipment Document Type

Billing Header Billing Document Type

Billing Item Billing Item Category type

Contact Contact type

1. Click on Account groups - Function Node and click on New entries Button.
2. Enter Partner function / Name / Account Group / Name.

Click on Save Button to save partner Function.