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 .