Skip to main content

Cash Sales and Rush Order process in SAP SD


Cash sale 

Ideally, there will be customers for whom transactions will happen through Cash Sale and in this case below are the points to be remembered.
  • Cash sales have one-time customer account group and Cash sales (CS) are also not relevant for credit management is used during sales order processing
  • Delivery automatically happens when you save the sales order.  



  • Cash sales is order related billing and doesn't have credit active


  • Cash sales items are not relevant for picking during delivery processing as you will be picking the goods on our own.

  • Ideally business uses separate shipping point for Cash sales delivery processing
  • Billing type 'BV' is used during Cash Sale process
  • Cash sales uses RD03 as output which immediately prints the invoice
  • Cancellation document type 'SV' is used for cash sales

  • Ideally, cash settlement account determination procedure 'KOFIAC' is used and Cash settlement account will be debited after commercial invoice posting

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

Rush order

This process used when a credit customer requires immediate delivery.

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

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

Comments

  1. Anonymous23 February 2019 at 21:36

    It was a very useful post about Cash Sales and Rush Order process in SAP SD as it giving the detailed info about detailed explanation of Cash Sales and Rush Order process.
    Reach now SAP SD Online Training in Hyderabad to learn SAP SD skills.

    ReplyDelete
  2. Famatechnologies10 June 2019 at 03:55

    Wanted to take this opportunity to let you know that I read your blog posts on a regular basis. Your writing style is impressive, keep it up! Call Paging System | Customer Call Paging Systems | Customer Order Display

    ReplyDelete

Post a Comment

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).
4 comments
Read more

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.
Post a Comment
Read more

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...
1 comment
Read more