Skip to main content

Sales Document type field control - Part 1


Sales Document Type: 

This field represents the identifier and description for the sales document type. We can define our own sales document type starting with characters 'Y' or 'Z'.

As a best practice, it is always good to copy the existing document type and create a new one referencing it.


Sales Document Category :

This classifies different types of sales documents that we can process in the SD module such as Inquiry ,Quotations, sales orders, deliveries, and invoices.

The document category determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing of the sales document.

When you create your sales document via the copy with reference option, this category field enables

the SAP system to provide the status information about the reference documents.

Below are the standard sales document categories exist in the SAP system

A  Inquiry
B  Quotation
C  Order
D  Item proposal
E  Scheduling agreement
F  Scheduling agreement with external servic
G  Contract
H  Returns
I  Order w/o charge
K  Credit memo request
L  Debit memo request
W  Independent reqts plan

0  Master contract

Sales document block

If we disable or stop any of the existing process for which we leverage this document type then we can restrict business user by using this document type by blocking it.

If user still try to use it then system throws an error message.

Further, This field also controls if the document type is available only for automatic processing.

Ex. Rebates.

Below are the selection fields for processing :

Blank - If document type is available to use then leave this field as blank.

'X' - If the value of the field is 'X' then system restrict this documents from using during sales order processing.

'A' - If the value of the field is 'A" then this will be used only during automatic processing of sales documents.

Number Ranges

Sales documents accepts both internal and external number ranges. System by default gives first preference to internal number range if non exist in system checks for external number range.

Number ranges are maintained using T.Code VN01 and assign interval in sales documents.

It is not a best practice to transport number ranges instead creates individually in each and every system independently.

Item Number Increment

This will gives the multiples in which item number need to be incremented

 Always it is best practice to maintain gaps in item numbers.

Line item 10 , 20 , 30 for first , second and third line respectively.

Sub Item Increment

If sub items exists for a main materials then this sub item increment is used. Ideally this will be used for BOM and other structural materials

Comments

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

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.

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