Date Format Changes

I am working on Rebate agreement.  In Rebate payments---->Drill Down.  I am getiing dates in month format but users want dates in day format.   How the format for the dates can be change.

>>>>> 
The T-code Su01 is for (User maintenance role) and T-code Su53 is for (User Authorizations)

Answer. 
-------

The process as follows for the change of the date in day format.

1. When you login to SAP and the come to menu screen

2. You can find the option of the System on the last right hand side of the screen on the top.

3. Press that option you will get the Drop down menu.

4. There you choose User Profile Option

5. Then again you find further drop down menu.

6. Choose the Option Own Data

7. The moment you choose this option will go into the screen of Maintain User Profile.

8. You will the Tab Screens (1. Address 2. Defaults 3. Partners )

9. Choose the Default Tab View Scree.

10. You will get to see the Date format and then the Currency format.

11. Go to  the Date format which has the 3 Radio Buttons options.

12. You can choose the Radio Button option which has the date in day format.

13. Then save it.

14. Then you can run your system and the transactions which you want to do will be coming the day format.

Syetem ----> Own Data ---> Maintain User Profile ----> Address, Defaults, Partners.

Delivery/Billing Due List - Select/Unselect the Default

On the document lists of the delivery list (Transaction VL04), the billing due list (Transaction VF04) and the work list for invoice lists (Transaction VF24), all items are selected when you display the list for the first time.  If the user click save at the initial screen, where all items were selected, SAP will do a mass save for all the documents display on the due list.  Users might feel unsecured with this features.

To change the default selection, refer to R/3 note no. 16711.  However, it seems that the note have been removed from OSS.

Here is an extract of the remove note 16711.

If you do not want the list to be predefined with selections, you can carry out one or both of the modifications described in the attachment in your system.

o  The modifications to objects MV50SFS0 and MV50SFZC (the latter only Release 3.1I to 4.5B) are relevant for the delivery list VL04

o  For the billing due list and the work list for invoice lists, make the modification to object MV60SFS0. As a result of the 
modification, the display of both lists is influenced at the same time.  However, the correction is only valid for the billing due list up to and including Release 4.0B; as of Release 4.5A, the modification in this note consequently only affects the work list 
for invoice lists.  To create the function in the billing due list as of Release 4.5A, refer to Note 139888 or customer function 008 within customer enhancement V60P0001. You can activate this customer enhancement  using Transaction CMOD.

Remark: Note that this modification also affects background processing: If the list is set up without selections, no list entries to be edited can be found during background processing either. Nevertheless, you can use the modification for background processing if you replace the line to be inserted with the following source code:

       IF SY-BINPT NE SPACE OR SY-BATCH NE SPACE. 
         POSTAB-SELKZ = 'X'. 
       ELSE. 
         POSTAB-SELKZ = '_'. 
       ENDIF.

This note is a modification and will not be included in a Hot Package.  Check whether you require the correction described in your system. When you apply a Hot Package, the system may overwrite parts of this correction. Therefore, when applying a Hot Package, make sure that this correction (SPAM/SPAU) is retained unchanged in your system.

     Source code corrections

     *$*$----------------------------------------------------------------$*$* 
     *$ Correction instructions  : 0120024545 0000000398                   $* 
     *$ Software component       : SAP_APPL   SAP Application              $* 
     *$--------------------------------------------------------------------$* 
     *$ Validity    : 30A          No patches                             $* 
     *$             : 30B          No patches                              $* 
     *$             : 30C          SAPKH30C01 - SAPKH30C14                 $* 
     *$             : 30D          All patches                             $* 
     *$             : 30E          SAPKH30E01 - SAPKH30E27                 $* 
     *$             : 30F          All patches                             $* 
     *$             : 310          No patches                              $* 
     *$             : 31G          SAPKH31G01 - SAPKH31G13                 $* 
     *$             : 31H          All patches                             $* 
     *$--------------------------------------------------------------------$* 
     *$ Changes/objects not contained in standard SAP system               $* 
     *$*$----------------------------------------------------------------$*$* 
     *&---------------------------------------------------------------------* 
     *& Object          REPS MV50SFS0 
     *& Object header   PROG MV50SFS0 
     *&---------------------------------------------------------------------* 
     *& This object has been generated from an advance correction           * 
     *& attached to a R/3 note.                                             * 
     *&---------------------------------------------------------------------* 
     *&---------------------------------------------------------------------* 
     *& Title: Correction A (VL04)                                          * 
     *&---------------------------------------------------------------------* 
     ... 
     FORM SELEKTION_AUSFUEHREN. 
      ... 
       LOOP AT POSTAB. 
         POSTAB-ACTIV = '0'. 
     *   POSTAB-SELKZ = 'X'.                        "<<<<<< delete note 16711 
         POSTAB-SELKZ = '_'.                        "<<<<<< insert note 16711 
         POSTAB-ZAEHL = SY-TABIX. 
         IF NOT ( POSTAB-LIFSP IS INITIAL ). 
            POSTAB-SELKZ = 'Z'. 
         ENDIF. 
         MODIFY POSTAB. 
         ... 
       ENDLOOP. 
        ... 
     *&---------------------------------------------------------------------* 
     *&---------------------------------------------------------------------* 
     *& Object          REPS MV60SFS0 
     *& Object header   PROG MV60SFS0 
     *&---------------------------------------------------------------------* 
     *& This object has been generated from an advance correction           * 
     *& attached to a R/3 note.                                             * 
     *&---------------------------------------------------------------------* 
     *&---------------------------------------------------------------------* 
     *& Title: Correction B (VF04 until 4.0B/VF24)                          * 
     *&---------------------------------------------------------------------* 
      ... 
     FORM SELEKTION_AUSFUEHREN. 
       ... 
       LOOP AT POSTAB. 
         POSTAB-ACTIV = '0'. 
     *   POSTAB-SELKZ = 'X'.                        "<<<<<< delete note 16711 
         POSTAB-SELKZ = '_'.                        "<<<<<< insert note 16711 
         POSTAB-ZAEHL = SY-TABIX. 
         IF RV60A-FKART IS INITIAL. 
           POSTAB-V_FKART = POSTAB-FKART. 
         ELSE. 
           POSTAB-V_FKART = RV60A-FKART. 
         ENDIF. 
         ... 
       ENDLOOP. 
     ENDFORM. 
       ... 
     *$*$----------------------------------------------------------------$*$* 
     *$ Correction instructions  : 0120024545 0000000399                   $* 
     *$ Software component       : SAP_APPL   SAP Application              $* 
     *$--------------------------------------------------------------------$* 
     *$ Validity    : 31I          All patches                             $* 
     *$             : 40A          SAPKH40A01 - SAPKH40A25                 $* 
     *$             : 40B          All patches                             $* 
     *$             : 45A          All patches                             $* 
     *$             : 45B          All patches                             $* 
     *$             : 46A          All patches                             $* 
     *$             : 46B          All patches                             $* 
     *$             : 46C          All patches                             $* 
     *$--------------------------------------------------------------------$* 
     *$ Changes/objects not contained in standard SAP system               $* 
     *$*$----------------------------------------------------------------$*$* 
     *&---------------------------------------------------------------------* 
     *& Object          REPS MV50SFS0 
     *& Object header   PROG MV50SFS0 
     *&---------------------------------------------------------------------* 
     *& This object has been generated from an advance correction           * 
     *& attached to a R/3 note.                                             * 
     *&---------------------------------------------------------------------* 
     *&---------------------------------------------------------------------* 
     *& Title: Correction A (VL04)                                          * 
     *&---------------------------------------------------------------------* 
       ... 
     FORM SELEKTION_AUSFUEHREN. 
       ... 
       LOOP AT POSTAB. 
         POSTAB-ACTIV = '0'. 
     *   POSTAB-SELKZ = 'X'.                        "<<<<<< delete note 16711 
         POSTAB-SELKZ = '_'.                        "<<<<<< insert note 16711 
         POSTAB-ZAEHL = SY-TABIX. 
         IF NOT ( POSTAB-LIFSP IS INITIAL ). 
            POSTAB-SELKZ = 'Z'. 
         ENDIF. 
         MODIFY POSTAB. 
         ... 
       ENDLOOP. 
        ... 
     *&---------------------------------------------------------------------* 
     *&---------------------------------------------------------------------* 
     *& Object          REPS MV50SFZC 
     *& Object header   PROG MV50SFZC 
     *&---------------------------------------------------------------------* 
     *& This object has been generated from an advance correction           * 
     *& attached to a R/3 note.                                             * 
     *&---------------------------------------------------------------------* 
     *&---------------------------------------------------------------------* 
     *& Title: Correction A (VL04)                                          * 
     *&---------------------------------------------------------------------* 
     FORM ZEILE_AUSGEBEN. 
       ... 
       IF POSTAB-SELKZ = 'Z'. 
          SELKZFLAG = '0'. 
     *    POSTAB-SELKZ = 'X'.                       "<<<<<< delete note 16711 
          POSTAB-SELKZ = '_'.                       "<<<<<< insert note 16711 
          COLOR = C_GESPERRT. 
       ENDIF. 
       IF POSTAB-SELKZ = '*'.

          ... 
     ... 
     *&---------------------------------------------------------------------* 
     *&---------------------------------------------------------------------* 
     *& Object          REPS MV60SFS0 
     *& Object header   PROG MV60SFS0 
     *&---------------------------------------------------------------------* 
     *& This object has been generated from an advance correction           * 
     *& attached to a R/3 note.                                             * 
     *&---------------------------------------------------------------------* 
     *&---------------------------------------------------------------------* 
     *& Title: Correction B (VF04 until 4.0B/VF24)                          * 
     *&---------------------------------------------------------------------* 
      ... 
     FORM SELEKTION_AUSFUEHREN. 
       ... 
       LOOP AT POSTAB. 
         POSTAB-ACTIV = '0'. 
     *   POSTAB-SELKZ = 'X'.                        "<<<<<< delete note 16711 
         POSTAB-SELKZ = '_'.                        "<<<<<< insert note 16711 
         POSTAB-ZAEHL = SY-TABIX. 
         IF RV60A-FKART IS INITIAL. 
           POSTAB-V_FKART = POSTAB-FKART. 
         ELSE. 
           POSTAB-V_FKART = RV60A-FKART. 
         ENDIF. 
         ...

       ENDLOOP. 
     ENDFORM.

4.6x Default Column Sequence for Sales Order

To default for all the users :-

• Go to any of the Sales Order screen VA01 / VA02 / VA03. ( the settings will affect all the screens)
• Click and hold the column you want, drag and drop at where you want the column to be
• Click the Table Settings located on the right hand side of the Sales Order Item.
• Put in a Variant Name
• Tick Use as a standard settings and click Create
• Click Administrator
• Click Activate

Mandatory Order Reason for certain Document Type

Is there a configuration that can be done to ensure that the Order Reason field is selected for certain doc types?

A*Order reason field cud be made mandatory for standard orders but it cannot be made for selected orders 

*check the incompletion procedure at documnet type - transaction flow. there u can maintained the requirements for completion. like reason no 14 checks for order reason.

*u can acheive this by incompletion procedure... the incompletion procedure 14 in the group A- Sales header which is used in the returns can be assigned to your sales order (where ever you require the order reason is manadatory)... Or you can define your own incompletion procedure and assign it to the sales order...

*You could even try screen variants. Very easy to set up. You will find this in the IMG -> Basis services -> app tayloring. TCODE SHD0. Then assign the variant to the sales order type.

Copy BUS2032 to ZBUS2032 and change to your specification.

Default values for Sales Order by users

You can specify the default values for transaction such as VA01 e.g. Order type ->  OR.  The default value can only be done at the User level.

SU01 -  Type in the user and click parameters

PID        Parameter  value         Short text 
AAT       OR                               Order type 
SPA        XX                               Division 
VKO      XX                               Sales organization 
VTW      XX                               Distribution channel

Difference Between Cash Sales 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 –

a. order type – RO/CS

b. shipping conditions – immediately

c. immediate delivery – X

d. lead time in days – not to be specified

e. delivery type – LF/BV

f. billing type – F2/BV

g. item category – TAN/BVN 

h. 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.

Mass Updation of SO

What is the transaction for mass updation of sales order and what are the fields it will affect?

by: Ketan Rathor

There is a Transaction MASS which can be used to carry out mass changes in the sales order.

In T Code MASS please select Sales Orders and execute.

Then you choose the relevant tables and the fields which you want to change and then execute it. 

Thereafter you enter the document range and also the relevant datas and then you choose "Selection Field". Add the fields from Pool to Selection Field using the arrows. 

Now you go to Mass Maintenance menu and click on "Enter New Field Values".   

Choose the data and then you execute it . Thereafter you will see that the datas have changed and then you need to save it .

Once it has been saved, the values will change. 

You can check the status through sm37. 

You can alternatively go to se16 and go the particular table. Then do mass maintenance and compare the results. If they match then it has been done .

What is the transaction for mass updation of sales order and what are the fields it will affect?

There is a Transaction MASS which can be used to carry out mass changes in the sales order.

In T Code MASS please select Sales Orders and execute.

Then you choose the relevant tables and the fields which you want to change and then execute it. 

Thereafter you enter the document range and also the relevant datas and then you choose "Selection Field". Add the fields from Pool to Selection Field using the arrows. 

Now you go to Mass Maintenance menu and click on "Enter New Field Values".   

Choose the data and then you execute it . Thereafter you will see that the datas have changed and then you need to save it .

Once it has been saved, the values will change. 

You can check the status through sm37. 

You can alternatively go to se16 and go the particular table. Then do mass maintenance and compare the results. If they match then it has been done .

What is Stock Transfer Order? What are the IMG configurations? How do you create a STO?

The following steps have to be followed in order to configure stock transport order between two plants.

1. Create a vendor for the Company code of the receiving plant using account group 0007 via T-Code XK01. 
2. In the purchasing data view assign the supplying plant and the schema group. 
3. Create customer with the sales area of the vendor.  
4. The shipping conditions, the delivering plant and the transportation zone determine the route in the STO. 
5. In the pricing procedure determination relevant to the STO assign document pricing procedure and customer pricing procedure to get the pricing in the invoice. 
6. Maintain condition records for pricing condition. 
7. Maintain carrier as a partner in the customer master. 
8. In OMGN select the supplying plant and assign the company code and sales area. Similarly select the receiving plant and assign the company code and sales area (The company code to which the plant is assigned to). 
9. Assign the delivery type and checking rule to the document type.  
10. And finally, assign the purchasing document type to the supplying plant and the receiving plant. 
11. Create the STO using T-Code ME 21N and save. 
12. Check for release strategy if any and release using T-Code ME 28. 
13. Create delivery in background using VL10G. 
14. If delivery is created, it is an indication of correct configuration and master data creation.

Stock transfer between two plants in different company codes is known as inter company stock transfer. 
1. Material should be maintained in both supplying and receiving plant MM01 
2. Stock should maintain only in supplying plant MB1C 
3. Create receiving plant as a customer in supplying plants company code and sales area XD01 
4. Assign this customer number in receiving plant details OMGN 
5. Assign supplying sales area in supplying plant details OMGN 
6. Assign delivery type NB for in combination of supplying/ receiving plants.

Create STO ME21N 
As it is normal there in the item details were should get shipping date i.e. customer number

Go for Delivery VL10B 
Shipping point ***** 
Select PO go for execute  
then select the delivery then go for delivery ............create delivery,,,, delivery number generated.

Goods Issue VL02 
Delivery doc ********** 
Click on picking 
enter the picking qty 
Click on PGI

In the mean time check in the PO history you will get the details 

Goods receipt MIGO 
In Stock overview, the stock will be updated....

Consignment Pickup and Consignment Return Process

Difference between the Consignment Pickup Process and Consignment Return Process.

The difference between Consignment Pickup and Return are:

1. In Consignment Pickup what ever the goods lying at the customers point as Consigment stock will be taken back before consignment issue to the said stock. Which means the Special stock will be converted in to actual stock or unrestricted stock.

2. In Consignment Return the goods were already sold to the customer by doing Consigment Issue. And the customer want to return the stock because of some reason (like Poor quality, Unable to sell, Price changes, Expiry etc). After doing consignment Return the stock will be once again added to the Special stock but not to the Unrestricted stock. If we want it to be unrestricted we should once do the process by using Consigment pick up. 

---

Consignment pickup: Process where the consignee (person who stocks the  goods to sell)  has not yet sold the goods and has returned them  back to the consigner (company that manufactures the goods) due to damage.

Goods flow :- CONSIGNER ----> CONSIGNEE ---> CONSIGNER

Consignment return: Process where the customer returns d goods to the  consignee and consignee returns the same to the company. here as the  consignee has already sold (& billed) d goods to the  customer,  the company has to issue a credit memo to the consignee  (AS IN CONSIGNMENT PROCESS COMPANY PAYS THE CONSIGNEE ONLY WHEN HE  SELLS THE GOODS TO THE CUSTOMER).

Goods flow :- CONSIGNER ----> CONSIGNEE ----> CUSTOMER ----> CONSIGNEE ----> CONSIGNER.

---

KB - Fill up 
You leave the material in customer premise (say 100  items)  
Materialis lying in customer 's place but stock is still in your books.

KE - Issue 
Your customer consumes (sells to his cutomer if he is in retail / uses up for production if he is in mfg) 
25 items now 25 items have been invoiced on him

KR - Returns 
If the material issue (25 items) are defective you will take it back using KR (returns)

KA - Pickup 
75 items not used by your customer, if you want to take back you will be using  KA            *-- Raja Reddy

How The System Proposes Probability For Each Item

You have to enter probability % in IMG of sales document header. 
  
The probability (expressed as a percentage) of the customer confirming the inquiry or quotation as part of a sales order. 
  
The system uses the probability and net value of each item to calculate a total expected order value for the sales document. The expected order value appears in the double-line entry screen. 
  
The system proposes the probability for each item. You can change the value manually depending on the sales document category. 
  
For example: 
  
A quotation contains two items:  A quotation contains two items: 
- Item 1 has a value of $100 and a probability of 100% 
- Item 2 has a value of $200 and a probability of  25% 
  
The system calculates the total probability as follows: 
($100 x 100% + $200 x 25% ) divided by $300 = 50% 
  
In this case, the probability of this quotation resulting in a sales order is 50%. 
  
You can generate requirements from quotations. The probability of the quotation items affects how the system passes on requirements. For example, a quotation for 100 pieces and a probability of 50% will generate requirements for 50 pieces.

Schedule Line Categories and Schedule Agreements

What is the meaning of schedule line categories and schedule agreements?

If you take a sales order document, it is divided into three parts:

Header Level information : 
This consist of the overall information of the sales document, for example Net value of the sales order and the like.

Item level information : 
This consist of information at item level, like Item 1 has a material with a net price so and so, item 2 has another material with another net price and so and so.

Schedule line information : 
This gives the information of the time a sales order has to be delivered to the customer, to view this select the item you want to view and to the menu under item >> Schedule line. This date is actually calculated from the delivery date in the Sales document. 
  
Schedule line Agreement : 
Use the T.code VA31 (and choose Scheduleline agreement) : This agreement lets you to predetermine scheduling of different materials with in a given period of time (This is same like the other contracts).

First enter the material with quantity say for example Material 1 Qty: 40, go to Edit from the menu >> Item >> Schedule line

There select within the time period defined two dates, say for example on 12: 01: 2005  20 quantity and on 13: 01: 2005 another 20 (The qty has to be same as the one in the sales order) .

Once this is done you have created a schedule line agreement.

Call this agreement in your sales order (with reference) and use them. 
  
Note: You will be able to deliver only 20 qty on the 12th and 20 qty on the 13th, even though the sales order is for qty 40

Backorder Processing

Backorder processing is a functionality in SAP where you can change the committments and over-ride the blockage of stocks 
marked against sales documents/deliveries. For e.g. you receive an order from a very important customer for material "A" but 
the entire quantity of A is committed to another customer "B" via earlier sales orders and this is where BACKORDER processing helps you to change the committment and shift stock due for B to A. This is the benefit of this funtionality.

OMIH - Checking rule for updating backorders 
OPJL   - Define new checking rule 
OPJJ   - Define scope of check

V_RA - Backorder Processing

Data selection:- 
Sold-to-party             Customer code            Mandatory 
Sales Organization                                         Mandatory 
Distribution Channel                                       Mandatory 
Division                                                         Mandatory

Changed confirmed quantity :- 
Tick the material you want to changed and click the Backorder button 
Confirmed quantity that still can be changed are highlighted.

V.15 - Backorder List 
Sales Organization                                         Mandatory 
Distribution Channel                                       Mandatory 
Division                                                         Mandatory

Analyze the difference between Forecast and Confirm sales orders

MD73 - Display Total Requirements

Enter theMaterial or MRP controller you want to analyze.

Assignment field options :- 
1 - If you with to look at how the planned independent requirements have been match to the sales order.  Sales order which 
     are over and above that forecasted are not shown. 
2 - If you are interested primarily in seeing what sales order are over and above the sales forecast. 
3 - If you are interested in seeing all the sales order with indication of whether or not they have been anticipated in the forecast. 
4 - If you wish to see all the three reports of the above three options together. 
   - Blank if you with to see a complete list of sales order, without any indication of whether they have been anticipated in the forecast.

Sales Order Stock

Sales Order Stock are stock with Special Stock type E. It can fall into the usual stock categories such as unrestricted, blocked etc. but "belongs" to a sales order.  For example, you create a sales order for a part and assign a sales item category that generates an individual requisition, the requirement has an account assignment linking it to the sales order schedule line, you convert that requisition to a Purchase Order.

When you receive the Purchase Order, the stock is placed in sales order stock. It will show against the sales order/sales order line. It can only be delivered against that sales order line. Any availability check etc for that material on any other sales order will not take it into account as it is not available except to the sales order line the stock is assigned to.

Sales reservation

Sales reservation takes place automatically through availability check

The setting is on the checking group ( OVZ2 - Define Checking Groups ). 
You must set the "Accumul." column. Without setting this it will only check availability but not reserve it!

SAP recommend Accumul. = 3 -> Accumulate the requirements quantity when creating and accumulate the confirmed quantity when making changes.

For manual reservation, you can used MB21, movement type 251 - Goods Issue for sales. 
To activate the Sales Order number field, do the followings :- 
Activate transaction OMBW 
double click movement type 251 
double click additional acct. assign. 
Tick the required/optional button as per your requirement.

The user have to manage the maual reservation using MBVR.

Reserving material without sales order

In Order to reserve the specific materials for a particular customer, use Strategy 50 to plan your MRP with the materials getting reserved for customer when you make Ind/Collective requirement(1) in MRP4 view of Material Master

or you can create a manual reservation against that particular material and give the customer name in the Receipent Field so that you can easily identify the Material which belong to the Customer

Sales Order Item price is grey

• Retrieve the sales order
• Click the sales order item
• Click Environment -> Document flow
• If there is any Billing Invoice including partial deliveries, price cannot be changed.

Wrong/duplicate RE Created

• Check Document Flow for RE

Decision:-
• No Goods Issue and No Credit Memo created
• Reject the sales order item
• No Goods Issue and Credit Memo created
• Cancel Credit Memo
• Reject the sales order item
• Goods Issue and Credit Memo created
• Create another OR to offset the credit memo created.  Treat this as a normal OR process.  Ensure that account receivable is informed by typing in the item text.  Please do not send invoice to customer as the RE is wrongly/duplicate.
Note: When you create another OR, the delivery department may actually go and delivery the goods to customer.  Thus, it is important to inform them that this OR is for internal adjustment.  The process of posting the goods issue must be done by the delivery side for proper flow.

Block Material in Sales Order

Is there a way for me to block a material from ever being entered in the Sales Order, if so how?

----------------------------------------------------------------------------------------------- 
If you want a material to be blocked, go to the Basic data 1 view of the material,there in the genral data you have " X-plant material status ". Also in Cost estimate 1 view of the material you have Plant Specific Material status. Use the options available to block the material in these two views.

You cannot use the material in sales order

Prakash.k

----------------------------------------------------------------------------------------------- 
Use the material exclusion function:

FUNCTIONALITY: 
SD> Master data > Products > Listing/Exclusion> Create 
( Tcodes VBO1, VB02, VB03)

Enter the list/exclusion type B001: For the required

customer: 
Enter Maintain materials > Save > Exit

Create the order and enter material excluded to test exclusion.

CONFIGURATION: IMG SETTINGS 
For IMG settings; Go to IMG > SD > Basic Functions>Listing/Exclusion

ENsure that the listing/exclusion procedure is activated for your order type. You can also create your own condition types access sequences and procedures or use the SAP provided ones.

Kris J

----------------------------------------------------------------------------------------------- 
Additionally, another option is the sales block in the material master... 
It is in one of the two sales data tabs and you are able to configure specific blocks that allow it to be entered on credits but not on orders, blocked from all activity, allowed for quotes only, etc.  It is one setting that becomes sales area specific and can easily be removed if you change your mind.   It also has an effectivity date that can be used.

Block Sales Document Type / Delivery / Billing by Customer

When there is a temporarily stop of business with a customer, you can block new orders to be created for this customer. You can have the options of blocking all the work flow or let the delivery and billing to continue for any open orders.

VD05 - Block/Unblock Customer

OVAS - Sales Order Type Blocking reasons 
OVAL - Blocking reasons links with Sales Order Type

OVZ7 - Delivery Blocking reasons 
OVV3 - Billing Blocking reasons

In 4.6x, if you found that your Sales Order Billing Block is not working, it is because you need to build the Billing Block for the Billing Type.

SM30 - Table/View   V_TVFSP

Common Distribution Channel and Division

How to configure common distribution channel and division?

You can define common distribution channels and divisions. This is possible for two areas of SAP, for all master relevant data, and for all condition relevant data. 
  
The path is as follows: 
IMG -> Sales and distribution -> Master data -> Define common distribution channels. 
IMG -> Sales and distribution -> Master data -> Define common divisions. 
  
Transaction Code - The code here is [ VOR1 ]. 
  
After creating the organizational structure and relevant master records you want to use as the masters, that is, in the distribution channels and divisions you are going to use as a reference, you can group distribution channels and divisions separately for master data (which combines customer master and material master records), group condition records, or both master data and condition records. 
  
Let’s say you have a product range that is not different for the four different distribution channels you have (the channels could be telesales, retail, industry, and wholesale.) Neither is there a difference in the customers’ details when they purchase through one or the other. Thus, you will not want to create a multiple of four views of customer master and material master records. Merely create the customer master records and material master records in one of the distribution channels, such as retail. Then assign the other distribution channels you created in the organizational structure setup to this one.

Don’t forget this means you can only create or change master data in the distribution channel that is being referenced. In the scenario above, this means you can only change data for the retail distribution channel. Even if you should access a customer or material master in change mode, press F4 (possible entries), and select telesales, industry, or wholesale, you will receive a message “Sales area is not defined . . . ”

The same is true for the sharing of conditions. If conditions are shared, you need only create a condition in the distribution channel or division you are using as the reference. Obviously, this only pertains to conditions that have the distribution channel and/or division in their key, such as a price based on sales area."

How To Configure New Division/Sales Area/Sales Office

New Division/Sales Area/Sales Office

4.6x

OVXA - Assign division to sales organization 
OVXG - Set up sales area

OVXM - Assign sales office to sales area 
e.g  Sales Organization -> Distriubtion Channel -> Division 
                                   | 
                                   ->  Sales Office

VOR2 - Define Common Divisions

OVAN - Combine divisions allows you to share sales document type data between different divisions. You define the sales document types in a central division and then use it as a reference division. 
For e.g. 
Sales Organization     Division      Reference division 
       ALL                     01               01 
       ALL                     02               01 
       ALL                     03               01

OVKK - Define Pricing Procedure Determination 
For e.g. 
Sales Organization     Distribution Channel     Division    Document Procedure     Pricing Procedure 
       ALL                                  01                    01                        A                             1

SM30 Table/View : 
V_TSPA             - Define New Division 
V_T134G_WS   - Assign Business Area To Plant 
V_TVTA_GRE - Define Rules By Sales Area 
V_TVTA_KFV - Assign business area by sales area 
V_TVAKZ        - Assign sales order types permitted for sales areas

---

SAP SD Questions: 
What is the difference between sales organization and sales area?

When you're talking about a company, based on which thing should we take? Is it different company codes for different locations or is it based on the product group?

Sales Organisation is the organisational unit which responsible for the selling of the product, movement of goods to the customet,customer right of recourse

Sales Area is the combination of the Sales: 
Organisation + Distribution Channel +  Division.

Company code of an organisation is the legal entity which have separate Balansheet and profit & loss A/C required by law for the legal purpose so whenever an organisational unit have different Balance sheet and P/L A/c you can define a company 
code.

-- Sanjay yadav

Organistational Structure broadly refers to the way a company follows a set path of systems/hierarchies. 
Different companies do have different structures and the differences in structures emanates basically from the strategies. STRUCTURE FOLLOWS STRATEGY...

A Company's structure can be mapped in R/3 which would facilitate flow of information, flow of process and also facilitates work flow in a logical way.

A Sales Organisations structure is based on the Elements of the Organisation which are as follows.

1. Comapny Code 
2. Sales Organisation 
3. Distribution Channel 
4. Division 
5. Plant 
6. Shipping POint.

A Company Code is generally created by finance guys and it broadly represents the highest point of structure.

The relation between Sales Org and Company code is Unique. One Sales Organisation can be assigned to one Comapny code. Think of one practical situation where in u can Say that Essar is One Group (Client). 
Essar Infotech (Company Code),  Essar Oil (Company Code). 
Essar Oil may have Essar South (Sales Org) and Essar North( Sales Org). You have to remember that Essar SOuth is only assigned to Essar Oil and not Essar Infotech right....

A Combination of Sales Org, Distribution Channel and Division is called a Sales Area and a Sales Area is assigned to the company thru the Sales Orgn.

A plant is assigned to the company code. It is also assigned to the Sales Org and Dist Channe and this channel is called Delivering Plant.

A Shipping POint is assigned to the CLIENT.                

Sales Document Type

Sales document can have many different document type.  Each document type have its own usage..

Some commonly used document type are:-

• OR - Standard Order
• RE -  Returns
• FD - Delivery Free of Charge

Different Sales Document type have different control parameters.

For e.g. Document type ZOWN :-

General control :- 
Check Division - 
Blank -> no checks 
       1 -> Dialog to inform user that the division is different from material master 
       2 -> Error when division is different from material master

Shipping 
Immediate Delivery 
Blank -> Create delivery separately 
       1 -> Create delivery immediately when sales order is save 
       2 -> Create delivery if quantity can be confirmed to day

Maintain Sales Document Type

• Transaction VOV8 - Double click on the document type to check the configuration.

Some configurations you can specify:-

• Check credit limit
• Define the default Delivery type
• Define the default Billing type
• Block the Document Type from being used etc.

Screens in the Sales Documents

Sales Order

Each sales order item can have multiple deliveries at different date.  Multiple deliveries for each sales item is specify in the Schedule line of the Sales Order.

When the Sales order was created (VA01) the system automatically proposes data from the relevant master records:

• From the customer master record (VD03) of the sold-to party, the system proposes sales, shipping, pricing, and billing data. In addition, the system copies customer-specific master data about texts, partners, and contact people at the customer site.
• For each material in the sales order, the system automatically proposes data from the relevant material master records (MM03 - Sales view), such as data for pricing, delivery plant, availability check, tax determination, and weight and volume determination.

VD53 - Customer-material  info record. When you create the sales order item, the customer material number will be copy into the item Customer Material. In the Sales order, click Item -> Purchase Order data.

Sold To Party In Sales Order Screen

After entering sales order (va01) screen, system giving default sold to party. How to disable this?

This is due to activation of userexit V45A0002. You need to deactivate this. Take the help from ABAPer to find the project which is assigned to the userexit and deactivate the same. 

or 

Can you also check in your SU3 Parameters whether there is any entry with Parameter ID - VAU?

If some value is set for this parameter , it will be copied by default in SOLD-TO-PARTY during creation of the Sales Document (VA01)

You can remove this ID or clear the Value.

You can also check if there is any Transaction Variant associated with your Transaction in SHD0 through which the default sold-to-party can come.

---

Change sold to party in sales order 

We have the below requirement of changing sold to party after creation of sales order:

Once sales order is created, purchase requisition is created automatically and purchase order is created with reference to the purchase requisition. So when Goods receipt is done, the respective stock is getting reserved for that sales order.

We wanted to change the sold to party option.

After creation of purchase order, sold to party option in sales order is display only.

How to make it changeable?

As long as you have not created subsequent document like delivery or invoice, you can change the sold to party in sale order either in creation mode (VA01) or in change mode (VA02). But once you created the subsequent document, you cannot change the sold to party bocz, the said field will become uneditable.

---

Effect of sold to party in sales order   

What is the effect of sold to party in sales order?

Suppose we are creating the sales order with customer '11' and material 'abc', but before saving the sales order document we changed the customer and new customer is '21', so after this change which is redetermined in the sales order.

These will get redetermine

-->Tax

-->Price

-->Frieght

-->Payment terms

-->Shipping conditions

-->Partner (Ship to party, bill to party and Payer).

-->Route.

If the Sold to party is changed from 11 to 21, then the new SP (21) may be valid for some other Sales Area, may have different SH,PY &BP. So accordingly those data will change.

If different SP, then Price may vary, Shipping condition may vary. So those data may change.

As different SH may be different, then Route may be different, Plant may be different, and as Tax is mostly Plant dependent, so Tax may change.

If SP is different PY may be different, so Payment Term, Incoterm & Credit limit may be different, so those data will be changed/redetermined accordingly.

Explain The Meaning Of An Open Sales Order

What is an open sales order?

An open sales order is where the order has not been delivered (physical goods).

Open Sales order : I will explain taking an example, suppose there is an order for 100 qty and against this order, only 50 are being delivered till its delivery date . i.e. it is partially delivered. then its status will be open . because it is not fully delivered.

You can check the open order status in VA02 in status tab. (double click on item and at item level chk the status) or check in transaction VA05 all the open orders.

In SAP SD, the document flow will summarize the status of each document. In order, they are:

1. Sales order : once delivery has been created, the status of the order changes from "open" to "completed".

2. Outbound delivery : when items are picked and posted for goods issue, the status remains at "being processed"; the status becomes complete only when billing is done.

3. Billing document : when billing document is created and saved, and posted to accounting, the status of the delivery becomes "complete"; the status of billing becomes "complete" as well; an accounting document is created and the status is "not cleared".

4. Payments posting affects the status of the accounting document; hence, you look at table BSEG. once payment is posted with reference to this accounting document, the status becomes "cleared". 
 

How can we know using data in tables whether a sales order is open or not?

Check in Transaction VA05 and in table the status filed will tell you the status of open order. 

Table VBAP / VBAK / VBUK (header) and VBUP (item) 
 

Which table is updated when customer pays against an invoice?

Check table VBAK / VBAP / VBRK / VBRP and VBFA you can chk the document flow. 
 

Can you tell if a sales order can be considered open if delivery has happened but payment has not been done yet?

Yes, that sales order will be considered as complete order. not open order.

Delivery will be open against which billing is not happened. 
 

How to close any open sales order?

Go to transaction VA05, here you can see list of all Sales order open for any particular sales area. 

You can either do mass maintenance to close all the open order by giving rejection reason. Or you can check one by one order & reject the pending item. 

Go to VA02, input the sale order and execute. Now select the line item and assign Reason for Rejection which you will find on the right top side.

If you have not delivered any quantity, then you can delete the sales order from the tcode VA02 - Enter your doc no- in the menu bar go to sales document-then DELETE.

Default Storage Location In Sales Order

Where to maintain settings if we want to make storage location appear by default at the time of creating the sales order?

There is No storage location determination at Sales order level.. Only we can enter manually.

Storage location will be determined at Delivery level only.. 

System does not determine storage location at sales order level. User has to indicate it at time of creating sales order. The storage location entered in the order item is copied into the outbound delivery.  If no storage location for picking is specified in the order item, the system determines the storage location when it creates the outbound delivery and copies it into the delivery item. The system determines the picking location based on a MALA, RETA, MARA rule defined in the delivery type.

This functionality is not available in the standard SAP. If you want the system to check the stock at a specific storage location, the storage location has to be entered manually at item level or you have to go for development so that it will be defaulted under the specific conditions specified. You have to create a Z-table and maintain the table with data under which that specific storage location has to be determined. 

A userexit has to be used so that it will default the appropriate storage location after checking the table.

Storage loction determination in Sales order is only possible via a user exit. You cannot configure storage location into sales order: you need to use user  
exit MV45AFZB USEREXIT_SOURCE_DETERMIN

or

You can use userexit_save_document

Userexit_save_document_prepare

or

The relevant forms to be used are:

USEREXIT_MOVE_FIELD_TO_VBAK -- to default in Header.

USEREXIT_MOVE_FIELD_TO_VBAP -- to default in item.

User exit: MV45AFZZ

---

Standard SAP can't determine storage location at sales order level. If required to give manually. But at deliver it'll determine automatic.

Do the proper settings at Delivery level:

SPRO --> LOGISTICS EXECUTION --> SHIPPING --> PICKING --> DETERMINE PICKING LOCATION --> Define Rules for Picking Location Determination.

If sales order level by default require, then you have to use user EXIT.

Partner Determination For Sales Doc

Explain me how to get partner determination for sales doc header level.

By: Micro Irrigation

First determine one account group ( Trans code OBD2 ) assign number range for acct group ( Trans code OBAR ).

Define partner determination procedure: 
IMG -> SD -> Basic Functions -> Partner Determination -> Setup Partner Determination -> Partner Determination For Sales Doc Header 
  
Click on Partner Type 
Go To New Entries and Define Partner Types 
Customer KU 
Vendor LI 
Contact Person AP 
Sales Employ SE 
  
Select Partner Type KU and Go To Details Icon and Maintain Partner Functions 
SP Sold To Party 
SH Ship To Party 
BP Bill To Party 
PY Payer 

Come Back and Click On 
Assign Partner Type To Sales Doc Header 
KU To TA 

Assign Partner Functions To Account Group 
SP To ACC GROUP 
SH 
BP 
PY Same. 

For Sales Doc Header The Partner Functions Can Be Determined From Customer Master.

Normal Sales Order Cycle Configuration

What are those initial sales order config?

By: Anuradha

Normal Sales Order Cycle:-

Step 1: Sales Document Type 
IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Header:

1. Sales Document Type: The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order. 

2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team. 

3. Assign Sales Area To Sales Document Types:  
A. Combine sales organizations / Combine distribution channels / Combine 
divisions: Ensure to maintain these, else Sales Order creation will give error. 

B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.

Sales Document Item: 
1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New. 

2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category

Schedule Line: 
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New. 

2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.

Step 2: 
IMG > Logistic Execution > Shipping > Deliveries > 
1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New. 

2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New. 

3. Define Number Ranges for Deliveries: Ensure to maintain number range.

Step 3: 
IMG > Sales and Distribution > Billing > 
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New. 

2. Define Number Range For Billing Documents: Ensure to maintain number range. 

3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.

The configuration differs from scenario to scenario & requirement of the client.

Configure inter-company Stock Transport Order

Explain STO.

STO is Stock Transport order. It is used for inter company transfer of goods. Plant to plant transfer and even transferring raw material to Third party contractors (Job Work).

The Process is you create a STO do delivery against the STO and create a Billing Document against the STO.

How to configure the inter-company Stock Transport Order? - Prassee

Material should exist in both the plants (Delivering  & Ordering),

Internal customer should be assigned to the ordering plant ( MM -> Purchasing -> Purchase Order -> Setup stock transport order -> assign the internal customer to the ordering plant and assign the Sales area of the internal customer.

Tcode : OMGN

Assign its Sales area to the delivering plant

Assign the document type and Delivery type  NB and NLCC

Assign the Supplying plant --> Receiving Plant --> NB 

Take the delivering plant and assign the sales area.

Vendor master has to be created and assaign the supply source ( Delivering Plant).

Create a puchase order ME21N ---> Save

Delivery VL10 G ---> Calculation rule (appropriate) --> Assaign the purchase order number here and execute.

Select the Delivery creation line and do the back ground process.

Start the log display and see the delivery document number by the documents button

Goto VL02N --> do picking and PGI --> Then do the MIGO with respect to the delivery document.

Billing (Intercompany pricing conditions should be set).

What is Debit note and Credit note

What is Debit note and Credit note?  What is the purpose?  How we create?

1. A transaction that reduces Amounts Receivable from a customer is a credit memo. For eg. The customer could return damaged goods.  A debit memo is a transaction that reduces Amounts Payable  to a vendor because, you send damaged goods back to your vendor. 
    
2. Credit memo request is a sales document used in complaints processing to request a credit memo for a customer. If the price calculated for the customer is too high, for example, because the wrong scale prices were used or a discount was forgotten, you can create a credit memo request. The credit memo request is blocked for further processing so that it can be checked. If the request is approved, you can remove the block. The system uses the credit memo request to create a credit memo. 
    
You can use credit memos in Sales and Distribution (SD) for assigning credit memo requests to the open invoices and in Financial Accounting (FI) for assigning  credit memos and payments to the open invoices and carry out clearing with them.  If you use both Financial Accounting (FI) and Sales and Distribution (SD),  there is a 1:1 relationship between the credit memo request and the credit memo item posted in Financial Accounting (FI). As soon as you bill the credit memo request together with other sales orders, or distribute the items of one credit memo request to several billing documents, the assignment is no longer valid and the system will not process it.

For  credit memos, credit memo requests, and payments, you have the following assignment options: 
- Assignment to a single invoice 
- Assignment of a partial amount to an invoice 
- Assignment to several invoices 
    
When you post  credit memos, the payment programme processes them automatically. If the credit memo is specifically related to a particular open invoice item, the payment program automatically attempts to offset the credit memo against the open item. If it is not possible to completely offset the credit memo against an invoice, you can post a debit memo to the vendor, who is to reimburse the amount.  Then you can apply a multilevel dunning program.  
    
3.  Debit memo request is a sales document used in complaints processing to request a debit memo for a customer. If the prices calculated for the customer were too low, for example, calculated with the wrong scaled prices, you can create a debit memo request. The debit memo request can be blocked so that it can be checked. When it has been approved, you can remove the block. It is  like a standard order. The system uses the debit memo request to create a debit memo. 
    
4.  As mentioned above, creating a credit or debit memo request enables you to create credit or debit memos based on a complaint. For this first create a sales document with the order type for a credit or debit memo  request. You can create the debit  or credit memo requests in the following ways:  
– Without reference to an order 
– With reference to an existing order 
Here you enter which order the complaint refers to. 
 – With reference to an invoice 
Here you enter which invoice the complaint refers to. 
In all cases, you specify the value or quantity that should be in the credit or debit memo 
    
5. You can block the credit or debit memo  request from being billed in Customizing. Go to Sales -> Sales Documents -> Sales document header -> Define sales document type and select the billing block field in the billing section.  This request can later be reviewed along with similar ones, - if necessary, by another department. The request for a credit or debit memo  can then be approved or rejected. 

Number Ranges In Sales Order

This is regarding number ranges defining and assigning tips which you can follow as below:

Whenever there is a new Sales Org being created, you will be required to maintain Number Ranges for Sales Documents which are allowed for your New Sales Area.

Number Ranges can be maintained Internally by the system, however it can be maintained externally also if you customize it accordingly.

In Standard SAP the Transaction code for Maintaiing Number ranges externally is VN01.

Defining - The same can be reached through in IMG as : Sales & Distribution-->Sales-->Sales Document Header-->Define Number Ranges for Sales Documents.

Here you provide the system a specific Number range as follows:

Number range Key +Start Number range+ End Number Range+Current Number

For Example: If you want to propose the following Number Range

*1     9000076000      9000076999      0

The Current Number field will be kept zero as you are proposing new number range and no sales documents have been created on it , Obviously..

*1 is a Unique Two digit Alphanumeric Key, while proposing your key, you should ensure that it should not be there in the system as existing.

If you propose a key that is there in the system or if the Number Range (Start and End Series) is there in the system already, the system will throw a message that Interval already already exists. So choose a key that is unique, and which is not there in the system.

Here , by making this , you are assigning a Key to a Number Range Series.

All the symbols can be used along with numbers from 0 to 9 and Alphabets from A to Z and in any order. For example: !1, ^A, BB,Z*,M2.........

Assigning - In Assigning, you assign the particular Sales Document to the Number Range you have already proposed as above.

The Assigning Part is done as follows:

The Two digit Alpha Numeric Key is maintained or Assigned to the respective Sales Document type in V0V8.

This can also be reached in IMG by:

Sales & Distribution-->Sales-->Sales Document Header-->Define Sales Document Types

Locate the particular Sales Doc Type, and double click on it to display it configuration. Here you put the Two Digit Number key in the Field- "Number range External Assignment"

Besides this:

If a new Shipping Point is created then Delivery Number ranges are required to be maintained.

Similarly,

If a new Plant is created then Billing Number Ranges are required to be maintained.

Steps for SD Variant Configuration

Some light on Variant Configuration in Detail.

The procedure is as follows:

• Create a Material - KMAT type with Item category (002)
• Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc
• Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for)
• Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page.
• Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass.
• Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and save
• Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
• Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save
• Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
• Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create the sales order.                     

Tell me about variant configaration?  
What are the type of questions we can expect in that?

Variant configuration is used where you have a configurable material like computer (made up of components like processor, monitor, keyboard, mouse etc). These components are called as characteristics in variant config. Again this will be having values like processor can be either P4 or P3, monitor can be 15" or 17" etc.

Based on the values selected the variant pricing will happen using the condition type VA00. 
    
Possible questions you can expect are: 
    
- What is variant configuration? 
- What is characteristic? 
- What is value? 
- What is class? 
- What is configuration profile? 
- What is dependency and what are the types? 
- What is a variant table? 
- And the transaction codes for the above.  

Difference between Item Proposal and Material Determination

What is the difference between the item proposal and material determination product proposal?

Item proposal and product proposal are the same.

Item proposal is the list of materials and order quantities that can be copied into the sales order from the customer master data.

We use VA51 to create the item proposal. Here we get a number.This number is then linked to the customer master data in the sales view. This is very commonly used. 
  
Material determination is very closely related to item proposal /product proposal  and is used to swap one material for another in the sales order using the condition technique. I have not seen Material  determination procedures used in the projects I have worked. 
  

Item Proposal or Product proposal:

"Item proposal is same as product proposal & SAP uses the two terms interchangeably.

"An item proposal is a list of materials and order quantities that can be copied into the sales order.  Items can also be selected from a list and copied into a sales order."

1) Use transaction [VOV8] to configure the document type ("MS" for product proposal). 
2) Use transaction [VA51] to create a proposal. 
3) Enter the item proposal on the sales area data (sales tab) of the customer master record. 
4) In [VA01] to create a sales order, Select Edit & propose items." 
  
Material determination: 
"Material determination uses the condition technique to swap one material for another when certain conditions apply. Material 
determination is triggered by the material entered in the line item of the sales order.

Use transaction [VB11] to create a material determination condition record.  And [OV12] for configuration of material determination.

Material determination is useful when old product is becoming obsolete or a new product is released by the company at specific date."

Batch Determination

On batch determination, the whole process, how it is determined automatically in the order.

A1) Normaly we use batch determination at delivery level, because at the time of order material may or may not be created.for this material should be configured with batch and batch determination should be checked in sales views of material.

A2) Batch Determination during order Creation. 
For this you need to maintain a Classes d for you Material. Depending on the Manufacturing process you can define the characteristics for your material.

Ex: Purity for Medicines,  Resistance for Electric Items.

You need to create a class (You might have to create a new class type) which incorporates the characteristic.

First Create the Characteristic Using Ct04 and then using Cl02 create the Class  including this characteristic.

Then in your material master Classification View Enter this class.

Then Create a Batch for the particular plant and Stor Loc using MSC1N.Give the value of the characteristics in this batch.

Then go to SPRO ->Logistics General ->Batch Management and maintain the Condition Technique (Procedure, Strategy Types and assignment to sales docs etc).

Then Create the Batch Determination Record using VCH1.

Supressing Fields in Sale Order

To make optional / mandatory you can use in IMG - S&D-> Basic > Functions-> Log of incomplete Procedures =>  select the fields > from the tables and the system will check for them (OVA2/VUA2)

To make a filed entry enabled or grey (non-entry allowed):

User exits in the program MV45AFZZ-USEREXIT_FIELD_MODIFICATION

This user exit can be used to modify the attributes of the screen  fields.

To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP.

If a field has no field name, it cannot be allocated to a group. The usage of the field groups (modification group 1-4) is as follows:

Modification group 1: Automatic modification with transaction MFAW

Modification group 2: It contains 'LOO' for step loop fields

Modification group 3: For modifications which depend on check tables or on other fixed information

Modification group 4: is not used 
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit. This FORM routine is called up by the module FELDAUSWAHL.

With Compliments by: Taner Yuksel

Actually suppressing fielding sales orders userwise is quite easy. We are doing it in our company. For this we use userexit FORM USEREXIT_FIELD_MODIFICATION in MV45AFZZ.

Below is the sample code

IF SCREEN-NAME = 'VBKD-ABSSC'.

AUTHORITY-CHECK OBJECT 'ZMV45AFZZ' ID 'SCRFNAME' FIELD SCREEN-NAME.

  IF sy-subrc = 0. 
    SCREEN-INPUT = 1. 
  else. 
    SCREEN-INPUT = 0. 
  ENDIF. 
endif.

You place the authority check object in authorization profile in the role of the users, who should have access to the field (in this case it is VBKD-ABSSC), and there assign the corresponding fields that are to be accessed via this userexit.

Issue free goods to selected Customers

Client wants to issue free goods to selected customers after the said customer buys a specified quantity of a good during the festive season starting 02 December to mid January. for example customer A buys 34 cartons of Corn Ice-cream, we offer him 12 free corns. this should then reflect as cost in our accounts. the rest of the system is already up and running and should not be inconvinienced. How do I set it up?  
 

1.Run trans. VBN2 to first create master record for free goods as follows:

Enter following information in selection screen: 
- Free goods type: NA00 
- Sales org, distribution channel, customer # and execute.

Now in next screen create the record as follows: 
- First select the exclusive button and verify that you are in exclusive view.  
  (that is if you want exclusive) 
- Material#, Min qty - Say 34 cartons. (check in what units you want to manage) 
  From: 34 cartons 
  unit of measure:  
  Free goods: 12 Pcs 
  Unit of measure: Pcs 
  Calcualtion type: 1 or try the other options 
  Deliver control: Blank or any of the other options suitable to you.

Now save and exit.

Now run VA01 for 34 cartons and press enter. The system will automatically propose the free goods 

item at no additional charge. Try higher order qtys and see if the free goods qty are scaling up. 

If not adjust the calculation parameters in the master record screen

It should be transaction VBN1. Sorry for the error.  
VBN2 is to change the record. VBN1 creates it.

Kris J 
 

If you want to give free goods to some of the customers than

1. create a customer group say 99 for FREE GOODS

In Free Goods Menu: 
2. add a feild catalog for CUSTOMER GROUP 
3. create a condition table (free goods) say 555 only for customer group 
4. create a sequence say FREE with condition table 555 
5. create a condition type say FREE with 
6. maintain pricing procedure say ZFREE with condition type FREE

Now assign: 
7. Active Free goods Determination or Assign with your sales organisation this procedure ZFREE 
8. Create free goods determination with transaction code /nvbn1 for FREE with Key Csuomer Group 

99 for exclusive

Give customer Group say 99 and from 34 to 34 free 12

Consignment Sales Process in SAP

The consignment process in SAP standard consist of four small processes: 

Consignment fillup (send materials to customer consignment).  
Here you have a consignment fillup order and a consignment fillup delivery. 

Consignment issue (issue materials from customer consignment to the customer).  
Here you have a consignment issue order, consignment issue delivery and a consignment issue invoice. (the flow is very similar to a normal OR flow, but the materials are issued from the consignment stock instead of plant stock unrestricted). 

Consignment return (return materials from customer ownership to customer consignment).  
Here you have a consignment return order, consignment return delivery and a consignment return invoice. (the flow is very similar to a normal RE flow, but the materials are returned to the consignment stock instead of plant stock returns). 

Consignment pickup (pickup consignment stock and move it to plant stock).  
Here you have a consignment pickup order and a consignment pickup delivery. 

Note that in consignment fillup and consignment pickup there are no invoices since there is no change of ownership for the materials.  
 

How to perform a consignment order?

In consignment orders you are allowing the stock to sit in your customer location. Once he informs that he used the stock you will invoice him. If he returns the stock you will accept the stock to take it back.

It is defined in 4 steps.

1. Consignment fill up:  
Sales document type is KB 
Item category KBN 
shedule line category E1

In this step, you are not invoicing the customer. document flow is sales order ---- delivery item category. It will not be relevent for billing and pricing because you are not charging money for these goods in this step.

In schedule line category, you will set movement type 631 & set for availability check and TOR.

2. Consignment Issue. 
Once the customer informed you that he used all the goods or partial goods then you will create consignment issue for used goods.

Sales document: KE 
Item category: KEN 
shedule line category: C0 or C1

Here you are invoicing the customer(because he used the goods). you are assigning the delivery documnt and billing document to the sales document.

In item category, you are setting relevent for billing, pricing, special stock.

In schedule line category, your setting is 633 movement type, relevent for availability check & TOR.

3. Consignment Return: 
Customer found that some goods are damaged or he not able to sold the goods he want to send it back. that you are creating this document.

Sales document type: KR 
Item category: KRN 
Shedule line category: D0

You will assign delivery document and billing to sales document. you will create return order, return delivery, return billing. 
Your setting item category relevent for billing, returns, pricing, special stock. 
Your setting schedule line item category: 634 movement type, NO availability NO TOR.

4. Consignment Pick up: 
Even if you create the consignment return the goods are not come to direct to your plant. For that you need to create consignment pick up. here the owner ship is not changing so you do not need to create billing. 
Assign retrun delivery to sales document type.

Sales document: KA 
Item category: KAN 
schedule line category: F0 & F1

Your setting item category relevent for returns. any shedule line category relevent for 632 movement type, MRP, availability check, delivery.

Now you check your plant stock. Stock will increase.   

Rebate Process with Ref. to SO

If I need to make a rebate for a customer what is the process involved.

I am providing some info on rebates which I know.

Rebate agreemnts is based on agreement types.Conditon records which are created like B001 and B002 are linked to the rebate agreeements specifying the rebate rate + the accrual rates.condition records specify the rebate rate and the accrual rates.

Consider an example..

You decided to give a rebate of 3% to a customer whose sales vol is $1000 for a particular SO 
Then the rebate value is $30..

Now when you make the rebate settlement by doiing the Credit memo and you decide to pay $27, then the accounting will be generated saying  27$ paid towards rebate and 3$ is the accrual which you owe to the customer

Procedure: 
Rebate agreement: Transaction code: VB01 
When you go to VB01, choose agreement type 0002 and then in conditions give 
Material     rebate 
1                 20 
20               30

Now create a sales order with a material say M-11 for SOrg 1000 12 00 with QTY 6

Now check VB03 and see rebate agreemtent it will say Accruals 120 and payments 0 
since your rebate is not settled still.

Rebate setllement 
Go to VB02 enter ur sales deal no, and change the agreemetn status to B then enter Shift+F12 and enter the amount to be paid for example u say $80

Then check in rebate payments rebate doc and partial setllemetn since you have not paid in full.

View the credit memo request 
Remove the Billing bloock Go to VA01 and put order type G2 ,,,go to create with ref and enter ur Sales order no,,,save the doc now...

Then go to VF01 and enter the credit memo reqst no generated...save the doc no and go to VF02 and say release to accounting

Now the final settlement will be this way

Accruals:120 
Accrual reversed:80 
Rebate pay:80 
Amount payable:40

So the balance 40 is still the accrual

This is an example how a rebate will be processed with ref to a SO with an example.

SAP SD Tips by: Priyam

How to do a rebate agreement for a  specific customers with settings details?

1. Create a condition by copying a a standard condition like BO03 in V/06 
2. Assign this condition in the std pricing procedure with acct key as ERB and accural key as ERU - V/08 
3.Create a  Rebate Agreement in VBO1 (It is O = Owl and not zero). No will be generated 
choose 003 - Customer rebates, enter the customer code, the validity and check for the status shld be in Open, click on the conditions enter the percentage and accrual amount. You also can have scales in this. Also you need to maintain the material for the settlement 
4. Create a sales order for that customer and check the rebate agreement. 
5. You can see the rebate condition in the invoice only. 
6. Once you have posted the invoices, then go to rebate agrrement no. clicl on verficayion and it will show the order details. 
7. For settlement change the status of the rebate to B - release for the settlement. 
8. Credit memo request will b generated copy the no. and go to VA02, remove the blocks if any and create an invoice (credit memo).this will show u the accrual amount. 
9. In both the invoice and the credit memo check the posting - accounting document it will show u the accrual as negative. 
10. Again go to rebate aggreement and check the status it will show you D - Final settlement of agreement already carried out