Skip to main content

Material Listing and Exclusion in ERP SD

At times, Business tries to control the materials to be sold to customers and this can be achieved to Material Listing and Exclusion Functionality.

With material listing or exclusion, you can control which materials can be sold to each customer. Material listing lists which materials a customer can buy. Material exclusion lists which materials a customer cannot buy.

During sales order processing system perform listing and exclusion as an initial check as soon as material is keyed in and if material listing/exclusion functionality is not active then system considers all the materials entered but however if listing/exclusion functionality is active, the system will allow creating orders for the materials that are listed.

Listing/ Exclusion as well follows condition technique in order to filter materials list.

Below are the process steps need to be followed.

1. Maintain condition tables for listing/exclusion
2. Maintain access sequences for listing/exclusion
3. Maintain listing/exclusion types
4. Procedures for maintaining listing/exclusion
5. Activate listing/exclusion by sales document type

Maintain condition tables for listing/exclusion

Ideally, the Standard system has provided condition tables which we can make use but however, if standard tables don't suffice the requirement then we will proceed with the customer table creation which ranges between 501-999.

Listing and Exclusion tables will be stored in database tables with prefix KOTG<Condition Table>.


Maintain access sequences for listing/exclusion


Maintain listing/exclusion types



 Procedures for maintaining listing/exclusion





 Activate listing/exclusion by sales document type



Master Data Maintenance

VB01 / VB02 / VB03: Used to create, change, display condition record for listing and exclusion

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