Skip to main content

Sales Document type field control - Part 2 General Control

Reference Mandatory


If the business requires to create a sales document only by copying it from an existing document then leverage this field.


For instance, if the business requires creating sales order only with reference to a quotation document or Inquiry document then we can select either choose 'B' or 'A'  here for quotation or inquiry restrict sales document from getting created standalone.

You can set up the SAP system to create a new sales document with reference to the
following:

A: inquiry
B: quotation
C: sales order
E:  scheduling agreement
G:  contract
M:  billing document

Remember that a selection in this field will only make it compulsory for the document to refer to an existing document. 

Copy Control Settings :

This will have a dependency on the copy controls as the actual flow of data between the two documents will happen once it is maintained.

Item Division

When selected, it allows the item division to be copied from the material master data. If left unchecked, the item division is copied from the sales document header.

Check Division: 

This field checks whether the division in the document header is different from the document items. The following options are available:

·         Leave the field blank: Different divisions between the header and the items are allowed without any message to the user.
·         Select 1: Divisions can be different, but a warning message is issued.
·         Select 2: Divisions cannot be different, and an error message is issued.

Read Info Record:

Ideally when sales document is created through external system, then the material number will be retrieved based on the customer material number maintained in the customer material info record.

In this case, we are required to enable this field so that customer material info will be carried over during creation.

Enter Purchase Order No:

This used if the business requires maintaining purchase order number same that of the Sales order number in case of missing purchase order then enable this field.

Ex. For a Sales Order '1234' PO number will be as '1234' in case of purchase order number is not maintained during SO creation

Check Purchase Order No:

This field is used a duplicate check for the Purchase order maintenance during Sales Order creation. In case if a Sales Order is already created with a Purchase Order then system give you warning message as per standard functionality.

In case business requires maintaining an error message this can be done through sales document message control.

Ideally, If Sales Order is getting created automatically through the external system then if this is check is not enabled there might be a chance of creating multiple Sales Orders for Same Purchase Order if the IDocs are reprocessed by mistake. Always it's a good practice to enable this check. 

Check Credit Limit:

Specifies whether the credit check is activated / Deactivated for a specific document type and how it responds to the check during sales order processing.

This further specifies if the document type is enabled with simple credit check or Automatic credit check.

For Simple credit check, Message handling will be done at document level i.e.,
  • You can set the following system responses for when the credit limit has been reached: A (warning), B (error message), C (delivery block).
A: This runs a simple credit check with a warning message displayed when a credit check for the document fails.
B: This runs a simple credit check with an error message displayed when a credit check for the document fails.
C: This runs a simple credit check and blocks the delivery for the sales document if the credit check for the document fails.
D: This runs a rule-based automatic credit check. 

Credit Group :

In the standard SAP system, We can carry out the credit check at the sales order, delivery, and Goods issue level in case of automatic credit check.

There are three credit groups available in standard SAP:
  • 01 for sales orders
  • 02 for deliveries
  • 03 for goods issue
For sales orders, the credit group is always 01.This field is only relevant during Automatic Credit Check process.

Shipping and Billing Info

The contains default values for delivery or Billing document creation for a specific sales document

Delivery Type

The system automatically proposes for the delivery type maintained in the field during delivery processing for a specific sales document

Delivery Block

This will enable the delivery block at header level of the sales document. If the business requires validating Sales Order data before proceeding with dispatch activities then we can leverage this field.

Shipping Conditions

This gives the info about how the delivery needs to be done i.e., Express delivery, Immediate or Standard.

This is one of the parameters used during Shipping point determination.

Shipping conditions can be maintained at Customer Master data level besides Sales document type.

But however, Shipping Conditions maintained at sales document level will be given highest priority which fetching for shipping point determination

Immediately Delivery
.
If the business requires creating immediately delivery upon creation of sales order then we can make use of this field.

'Blank' Create delivery separately
'A'         Create delivery immediately
'X'         Create delivery immediately, if quantity confirmed for today

Ideally, business performing delivery rescheduling before the creation of deliveries so that quantity allocations will be done to the customers based on the delivery priority in the customer master.So by default, This field will be blank for standard deliveries which are created through background Job Processing.

If the business doesn't contain delivery rescheduling functionality then we can use 'A' or 'X' for creating deliveries automatically.

'A' is used if business requires creating delivery if the confirmed quantity date is at later date as well
'X' is used only if the confirmed quantity date of a sales document is today.

Ship Cost Info Profile

This is ideally used during transportation functionality where the rough estimate of delivery cost is required to be displayed at sales document level prior to shipment processing.

Delivery  / Order / Intercompany Related Billing Type

This field is used to fetch billing type during billing document creation for delivery related billing.

If delivery doesn't exist for specific items such as service etc .. then these are considered as Order related billing and system fetch billing type from this field.

In case of Intercompany Billing type such as intercompany scenarios, then the system needs to fetch billing type from this field.










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