CPP (Config) Html5EN
CPP (Config) Html5EN
PUBLIC
2023-04-26
2 Standard Customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1 MRP areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Transport settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3 ATP Check executed by the CPP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Checking rule 'RP'. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Checking rule from Customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.4 ATP Check executed by the SAP standard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3 CPP Customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1 Application Customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Stock Transfer Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Priority of Sending Plants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Delivery Times. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
MRP Elements for Alternative Stock Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Document Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Texts for CPP Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Processing Priority of Requirement Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
MRP Element Profiles for Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Cust. Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Tasks for Customizing Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2 Output Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3 Alternative Stock Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.4 Technical Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
1. Date of Last Material Movement: If this date is before the slow mover date entered in the CPP, the
material is classified as a slow mover.
• Field name: LASTMOVE
2. Strategic Material
• Field name: STRATEGIC
• Field values: X = no automatic stock transfer possible; no value = automatic stock transfer possible
3. Released for Stock Transfer
• Field name: RELEASED
• Field values: X = release for stock transfer; no value = no release for stock transfer
4. Stock Transfer Type: To create a stock transfer, the value of the receiving plant/MRP area is read. If the
field contains no value, STO is used as the default value.
• Field name: ST_TRANS_TYPE
• Field values: STO = stock transfer order, STR = stock transport requisition, RES = stock transfer
reservation
The specified fields can be maintained at plant, MRP area, and storage location level. The information is saved
in the following three database tables:
To use a Material as Supplier for Stock Transfers in CPP, you must set the flag in the field "Released for
Stock Transfer" at plant or MRP area level. If the flag for the field "Strategic Material" is set, the material is
not used since the strategy indicator acts as an ultimate exclusion criterion. If no entries exist for a material in
table /SAPLOM/MEH_MM01 or /SAPLOM/MEH_MM02, it cannot be used as a supplier for stock transfers.
It is possible for individual storage locations to be excluded as suppliers. For this, the entries must be
maintained at plant or MRP area level, as described above, and an entry must exist at storage location level.
The flag for "Strategic Material" must be set at storage location level. Exclusion of storage locations is also used
when MRP elements are considered in scenario 9. It does not influence the calculation of Consum and Demand
in the alternative stock calculation. If there is no entry at storage location level, the storage location is treated
the same as the higher-level entries at plant level or MRP area level.
Maintenance can be carried out manually using material master maintenance or using the mass maintenance
transactions. Manual maintenance is carried out using transaction MM02 at plant level. From here, you can
navigate to MRP Area Level and Storage Location Level.
The fields Date of Last Material Movement and Released for Stock Transfer can be maintained using the
SMU Report. For more information, see Determination of Status as a Slow-moving Item and Release for Stock
Transfer.
All fields can be maintained using the Configuring Rule Set Maintenance. To do this, you add the required table
fields in transaction /N/SAPLOM/XMM_CONS so that they can be maintained in the rule set. The table name
determines at which level the fields (table /SAPLOM/MEH_MM01 for plant level, MM02 for MRP area level, and
MM03 for storage location level) are maintained. Any sequence can be chosen.
Now the fields in transaction /N/SAPLOM/XMM_RULE are displayed under "Consequences (Update Values)".
Create a new rule, select the update conditions, and enter the associated field values.
The transaction /N/SAPLOM/MM17 is then used to carry out mass maintenance for the selected materials. For
this, the checkbox "Rule-Based Material Master Update" must be selected.
On the results screen, you can select the required materials and maintain them using the "Rule-Based" button.
This documentation provides information on the standard customizing which should be done before using
the Cross Plant Planning tool. The settings in chapter 1 should be maintained, if the CPP will be executed on
MRP area level. The steps of chapter 2 are necessary for using the CPP itself. Chapter 3 and 4 describe the
procedure of maintaining the availability check. This quantity check can be either executed by the CPP itself
(chapter 3) or be executed by the SAP standard within the stock transfer depending on the stock transfer type
(chapter 4). Customized settings are required for both options.
Go to transaction SPRO and click on “SAP Reference IMG”. Select Materials Management > Purchasing >
Purchase Order > Set up stock transport order > Set up stock transfer between storage locations. Here you will
find the customizing for the stock transfer between storage locations.
Go to transaction SPRO and click on “SAP Reference IMG”. Select Materials Management > Purchasing >
Purchase Order > Set up stock transport order. Here you will find the customizing for the shipping data for
plants and the delivery type.
Click on “Define shipping data for plants” and double click on the plant you want to maintain data for.
Click on “Assign delivery type and checking rule”. You can maintain the delivery types here, as well as the rule
for the availability check (please see chapters for ATP Check).
The ATP check executed by the CPP can be done with the checking rule 'RP' (ATP-Option 1) or with the
checking rule from Customizing (ATP-Option 3).
For more information on the configuration of the checking rule 'RP', please see Checking rule 'RP' [page 12].
If you want to use the checking rule from Customizing and therefore be able to consider not only confirmed
quantities, please see Checking rule from Customizing [page 16].
To maintain the checking rule 'RP', go to transaction SPRO and click on “SAP Reference IMG”. Select Materials
Management > Purchasing. Here you will find the customizing for purchase requisitions and purchase orders.
Choose “Create Checking Rule” and create the rule “RP”, if it has not been created already.
Go back and choose “Define Checking Rule”. Use a double click on the combination of checking rule = “RP” and
the checking group for availability check, which is maintained in the material master, field MARC- MTVFP (in
this example: “01”).
Go back and choose “Assign Checking Rule”. Make sure the checking rule ‘RP’ is maintained for the supplying
plants you want to use for CPP.
In order to use the ATP Check with requirement quantities (not only confirmed quantities), some manual
actions are required to be performed in the customer system. The following steps are necessary:
In transaction SE80 create a new package ZSAPLOME with description “Customer-activated enhancements
for /SAPLOM/ tools” and with package type “Development package”. Include this to the suitable transport
request.
Alternatively, you may consult with your technical team and define which already existing package can be used
(but please make sure that it should be created in customer namespace Z*).
In transaction CMOD create a new enhancement project ZSAPLOME with description “Customer-activated
enhancements for /SAPLOM/ tools” and assign it to the package from point a. Here also there is option to align
with your technical team the usage of different already existing enhancement project instead.
In transaction CMOD go to “Enhancement assignments” page for the project and add line for the standard
enhancement having code W61V0001 “User exit for BAPI ATP information”.
In transaction SE38 create an include ZXACKU01 with the description “Include for user-exit enhancement
W61V0001” and type I ‘Include program”. Assign the include to the package from point a.
Please note that here the name of the include ZXACKU01 is fixed and can’t be changed since it’s part of
standard FM EXIT_SAPLW61V_001 (which is the component of above mentioned enhancement W61V0001).
Open include ZXACKU01 for edit and add the following ABAP line to the top of it:
The ATP Check of the SAP standard is executed within the stock transfer and depending on the stock transfer
type. To customize the settings, go to transaction SPRO and click on “SAP Reference IMG”. Select Materials
Management.
The settings for the STO can be found under Purchasing > Purchase order > Set up stock transfer order >
Assign delivery type and checking rule.
Enter the names of the created checking rules here and save your changes.
The settings for the STR are maintained under Purchasing > Purchase Requisition > Assign checking rule.
The settings for the RES are maintained under Materials Management > Inventory Management and Physical
Inventory > Reservation > Set dynamic availability check.
Customizing for CPP is called via transaction /N/SAPLOM/CPP_CUST. Here, you can make settings for the
execution logic of the CPP, the output areas, the alternative scenarios, and the technical settings.
The settings for priority, delivery times, MRP elements, processing priority, MRP element profiles, and
Customizing requirements are customer-specific. This means that SAP does not provide any default settings.
Instead, these settings must be made in line with the individual circumstances in your company. No change
requests are required to save changes to these settings.
After the CPP workbench transport has been imported, you have to import the Customizing transport. This
loads the CPP standard settings into the corresponding Customizing tables.
Under stock transfer type, you maintain standard order types or custom order types. It is possible to maintain
orders and purchase requisitions only. Settings in Customizing are required only if customer-specific order
types are used or if special order types are used in the stock transfer process. Standard settings are delivered
automatically. If you use only standard order types, such as UB and NB, you do not have to make any settings.
In this Customizing, you define for each plant or MRP area to which order types the selection is restricted. For
each plant or MRP area, multiple order types can be maintained. If no order type is specified for a plant or MRP
area, the system uses the values maintained for "*".
Reservations use standard movement type 301 for stock transfers between different plants, and movement
type 311 for stock transfers within a plant.
When you maintain the plant relations, you specify Priorities that determine the sequence in which the
supplying plants are checked for stocks to be transferred. Using the value "X" excludes a stock transfer in
the specified areas. You can specify different scenarios by assigning different plant relation keys and selecting
the relevant key on the selection screen.
Under Delivery Times, the delivery time from the supplying plant to the receiving plant or MRP area is
maintained. For all relevant plant relations, you maintain the delivery time (in days) that is to be taken into
account during the process to decide whether a stock transport order is to be created. If no value is maintained
for a plant relation here, no separate delivery time (therefore, 0 days) is taken into account. A delivery date is
determined based on the delivery time. If this date is later than the requirement date of the receiving plant, no
stock transport order is created despite stock being available for transfer.
The maintenance of the MRP elements for the alternative stock calculation is relevant only when you use
the alternative DEMAND scenario, if the number 2 (Only Stock from Customizing for MRP Elements) or 4
is selected as the requirement scenario option. This Customizing is optional and is only to be maintained if
required by the customer.
You can maintain MRP segments and corresponding MRP elements at plant and MRP area level. Before a stock
transfer is created, these are subtracted from the available stock of a supplying plant or MRP area so that
only the stock that is actually available is transferred. You can use Customizing to select which requirement
elements are to be subtracted from the available stock. You can use '*' for the area to cover all areas.
The elements are only considered if the corresponding profile is entered on the selection screen (see
Alternative Stock Calculation).
Under Selection Document Types, you can maintain document types for the planned orders. Only the specified
document types are taken into account for the stock transfer. By using the checkbox for all document types, all
document types are considered for the specified area.
Inter/cross document types Customizing identifies cross-company and internal-company movement types
through order types. If you use non-standard order types, they must be defined in Customizing here. This
enables CPP, in conjunction with the standard Customizing in which the order type is specified for a plant
relation, to make the correct assignment to an inter-company or intra-company operation. If multiple order
types are to be used, all of them must be maintained.
The Texts for CPP elements area enables the modification of description texts for the MRP elements in MD04.
In the Processing Priority view, you can determine the priority with which purchase requisitions, stock transport
requisitions, planned orders, reservations, and Customizing Requirements are processed.
To use scenario 9, you must maintain the MRP element profiles for the receipts in Application Customizing.
In the area MRP elements for profiles, the MRP elements that are to be used as unrestricted-use stock are
assigned to the profile. This profile can then be assigned to the area (plant or MRP area) in Profiles for areas.
In this case, the program only processes materials that are released. The profiles themselves must first be
created in MRP element profiles for receipts.
By maintaining this table, individual requirement coverage elements can be selected in addition to planned
orders, purchase requisitions, reservations, and stock transfer requirements, to be replaced by stock transfers.
For this, on the selection screen on the "Receiving Plant" tab, you must select the "Cust. Requirements"
checkbox.
If the Cust. Requirements [page 26] for which the CPP created stock transfers is not adjusted or deleted by
the subsequent MRP run, the Task Function can be used. Using this function, elements that have already been
processed by CPP can receive a selection in the form of a task, through which the CPP can recognize in the
next run that a stock transfer has already been created for this element, even if the original element is still in
the stock/requirements list.
In the first step, the tasks to be used must be created using transaction /N/SAPLOM/X_MEAS_C. The way this
works is described in Creating Tasks. Cross-plant planning must be maintained under Consulting Solution.
In the second step, the CPP Application Customizing [page 23] is opened using transaction /N/SAPLOM/
CPP_CUST. The bottom table Maintenance: Tasks for Customizing Requirements is relevant here. The tasks to
be created can be selected here. A task can be set for each requirement element that is completely processed
and partially processed. If Customizing is saved, CPP can be used as usual.
Created tasks can be displayed in the Tasks Overview using transaction /N/SAPLOM/X_MEAS. In this
overview, the user can edit and delete tasks.
In Customizing for output areas (transaction /SAPLOM/CPP_CUST_DC → Output Areas), the labels for the
various output tables of the results screen are saved. The entries are supplied as standard with cross-plant
planning.
If you change the description or the sequence of the output tables, make sure that you do not use the initial
Customizing transport when you import subsequent releases or other transports (for example, for customer-
specific developments). A Customizing upgrade transport is provided that is required specifically for this case.
The calculation scenarios for the alternative stock calculation are determined in Customizing, in the
transaction /SAPLOM/CPP_CUST → Non-Standard Scenarios.
To create a new scenario, enter a name of your choice (scenario ID) for the scenario and choose a calculation
logic. You can also select the periods in the future and in the past that are to be considered. If required,
additionally select the relevant field to determine whether the reorder point and/or safety stock are to be taken
into account.
Note
Note that in the CONSUM scenario, no periods in the future can be maintained.
You can use the maintenance of the technical settings for CPP to decide whether a Parallelization of Processes
is to be used for the selection of the requirement coverage elements. You can maintain a logon/server group
and a percentage load.
Based on the type of required object, you can filter non-required elements (inspection stock, for example)
or change the following parameters:
• ELEMENT_ID
• ELEMENT_TYPE
• BNFPO
• RSPOS
• RSART
• TYPE
• WERKS
• MATNR
• BERID
• LGORT
• MENGE
• UNIT
• EKORG
• EKGRP
• LFDAT
• OPERATION_AREA
3. /SAPLOM/IF_CPP_ELEMENT_CHANGE
This BAdI enables you to manually reduce the amount of the reservation, planned order, or purchase
requisition in the case of a partial quantity stock transfer due to customer requirements. This step takes
place before the amount is reduced automatically.
4. /SAPLOM/CPP_EHS_PROGRAM
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.