Ansicht
Dokumentation

/ACCGO/CPE_MAPPING018 - Different per unit of measure or quantity in conditions; see long text - /ACCGO/CPE_MAPPING 018

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Diagnosis

The mapping from Commodity Pricing Engine (CPE) conditions to pricing aspects failed because when mapping a set of conditions to a pricing aspect condition type, the unit of measure or quantity differs.

To understand it better, consider the following examples:

CPE Condition to Pricing Aspect Mapping

ZAW0 -> FP01

ZAW1 ->BP01

ZAWP -> BP01

Note that both conditions ZAW1 and ZAWP map to BP01.

Example 1 - Different 'per' unit of measures

,,Consider we have the following CPE price fixations:

,,ZAW0

,,,,20 TO, with 5 USD per 1 TO

,,ZAW1

,,,,20 TO, with 5 USD per 1 KG

,,ZAWP

,,,,20 TO, with 5 USD per 1 LB

Note that the Per unit of measure in ZAW1 and ZAWP differs. Being so, it is not possible to determine which "per" unit of measure shall be used, and thus, this error is raised.

Example 2 - Different 'per' quantities

ZAW0

,,,,20 TO, with 5 USD per 1 TO

,,ZAW1

,,,,20 TO, with 5 USD per 3 TO

,,ZAWP

,,,,20 TO, with 5 USD per 5 TO

Note that the per quantity in ZAW1 and ZAWP differs. Being so, it is not possible to determine which "per" quantity shall be used, and thus, this error is raised.

System Response

The mapping routine fails and it is not possible to save the contract

Procedure

Price using the same "per" quantity and unit of measure.

Procedure for System Administration

rdisp/max_wprun_time - Maximum work process run time   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 1728 Date: 20240419 Time: 035151     sap01-206 ( 23 ms )