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

Post a Comment

Popular posts from this blog

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...
1 comment
Read more

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than  < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.
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