ATP Customising

Purpose

The purpose of this page is to explain how ERP ATP check is customized.

Overview

Essential steps and methods for customising ERP ATP Check.

Requirement types and requirement class determination

The system allows the standard search strategy and two alternate search strategies. This is helpful for the customers that wish to base their requirements type/class on the sales process (triggered by the item category) rather than being limited by using only the planning characteristics of the material (= production process).

Standard search strategy

The system uses a series of checks to determine the requirements type. The sequence of checks are called a search strategy.

 First, the system will look for a Strategy Group. This is maintained in the material master (MRP view). The requirements type is defaulted from the strategy group in OPPT. The details of thestrategy group can be viewed within transaction OPPS.

 If there is no strategy group maintained, then the system looks at the MRP group, from the material master. The plant and the MRP group are used to determine the strategy group, which will determine the requirement type (using the method described above).  This configuration is found within transaction OPPU.

 If there is no strategy group and  no MRP group exists in the material master,  the system will then look at the material type as maintained within transaction OPPR. MRP group = Material type.  The system will use the MRP group information to derive the strategy group, etc, as described above.

 If there is no strategy group and no MRP group in the material master, and no MRP group equals the material type, then the system will look at the Item Category and MRP Type to find theRequirement Type. This is configured within transaction OVZI. It is also possible to have configuration with the Item category + BLANK = requirements type within the table.

 Finally, if the system has been unable to determine a requirements type by using the steps above, the system will leave the field blank in the sales document.

Alternate search strategies

Item category and MRP type (1)

 The standard search is performed and the entry from OVZI (Item category + MRP type) is used as the Requirements type even if this is not a valid requirements type from the standard search. It is still possible to enter different requirement types manually, since more than one valid requirement type is possible because there can be several Strategies within a Strategy Group.

Item Category and MRP Type with validity check (2)

The standard search is performed and then the Requirements Type from OVZI (Item Category + MRP type) is used ONLY if it is valid from the standard search method. If the entry from OVZI is not valid then the requirements type derived from the standard search method is used.

If the Item Category + MRP type combination cannot be found on transaction OVZI, you can add a new entry on the customizing transaction VOV5. 

Note: If you want to find the requirements class without checking the configuration, go to the schedule line screen and hit ‘/H’ and check contents of XVBEP. The fields are BDART and PLART. The fields must be combined to get the actual requirement class.

 Example

BDART = 04

PLART = 1

Requirement class = 041

Illustration of ERP ATP Customizing.

1.Material Master: relevant fields: 

• MRP1 View:  MRP type, MRP group.
• MRP3 View :   Strategy Group.
• Sales org. 2:  Item Category Group

2.DEBUGGING: relevant fields:

• xvbap-pstyv = Item Category
• xvbap-bedae = Requirements Type
• xvbep-bdart + xvbep-plart = together in this order show Requirements Class

Detailed Customising for Required for Sales order

Related Content

Related Documents

Related SAP Notes/KBA

Fonte: https://wiki.scn.sap.com/wiki/display/SCM/ATP+Customising