Ansicht
Dokumentation

Multilevel ATP Check ( RELNAPO_310_ATP_MULTILVL )

Multilevel ATP Check ( RELNAPO_310_ATP_MULTILVL )

Fill RESBD Structure from EBP Component Structure   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Multilevel ATP Check

Use

As of SAP APO 3.1, you can use the multilevel ATP check.

There are industry areas (for example, PC assembly) in which a large part of the value-added activity arises at final assembly. The assemblies on the lower production levels have already been produced or procured before the sales order comes in, but final assembly is only initiated when the sales order arrives.

The multilevel ATP check is usually used in these areas, since the components that are required to produce an end product are checked when a sales order is created.

A particularly suitable use of the multilevel ATP check is sales order entry for configured products. A sales order can only be accepted when all required components are available. Which components are needed specifically, however, depends on the configuration requested by the customer and can only be checked at the time of sales order entry. Further uses are order entry via the internet as well as within heterogeneous system landscapes.

In contrast to Capable-To-Promise (CTP), no receipt elements are created during the multilevel ATP check in the order network of SAP APO. Instead, the check results are stored in the ATP tree structure. Receipt elements are only generated later when the ATP tree structure is converted in PP/DS. This allows improved performance during the check. However, statements on capacity availability can only be rough (on a daily basis) and not as detailed as in CTP (in seconds).

As long as no receipt elements exist, the ATP tree structure exists in the SAP APO database. Requirements at component level are represented as aggregated quantity assignments. The ATP tree structure and the aggregated quantity assignments are deleted and/or reduced directly after the ATP tree structure is converted into receipt elements.

The multilevel ATP check supports the following functions:

  • Check against the forecast at component level
  • Mapping of capacities using product allocations
  • Exclusion of specific components from the check (that is, complete confirmation of the components without check)
  • Return of data via the components/characteristics that have lead to a delay and/or reduction of the confirmation (see missing parts list)
  • Rules-based ATP check at component level; in PP/DS, a location determination results in a stock transport requisition, a product substitution in a planned order with corresponding components.
  • Cross-system third-party order processing at finished product level, together with multilevel ATP check

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

The following enhancements have been made in Customizing so that a multilevel ATP check can be carried out. For detailed information on the settings for the multilevel ATP check, see the online documentation.

  • In the check step Maintain Check Mode, you can now select the value multilevel ATP check in the production type field.
  • If you would like to define another determination of the rule strategy for the rules-based ATP check at component level, you can define a separate business transaction in the work step Create business transaction for the multilevel ATP check.

Further Information

Release information Conversion of ATP tree Structures into Procurement Proposals of PP/DS

Release information Recreation of receipt elements

For detailed information on the multilevel ATP check and its constraints, see the online documentation.






BAL_S_LOG - Application Log: Log header data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 5583 Date: 20240328 Time: 214224     sap01-206 ( 90 ms )