OPP_SD_INTEGRATION - Messages related to OPP SD Integration

The following messages are stored in message class OPP_SD_INTEGRATION: Messages related to OPP SD Integration.
It is part of development package OPP_SD_INTEGRATION in software component LO-RFM-OPP. This development package consists of objects that can be grouped under "Integration of OPP into SD".
Message Nr
Message Text
001Maintain OPP SD configuration for pricing procedure &1
002Maintain ISO code for unit of measure &1 used by item &2
003Value &1 is not allowed in Customizing. Use whole numbers for index.
004Enter condition type &1 only once
005Cannot determine discountable indicator for &1 / &2 / &3 / &4
006Plant &1 to be used for price calculation not found
007Merchandise group &1 to be used for price calculation not found
008Error during determination of the hierarchy of merchandise group &1
009Pricing dates at item level are different, &1 is used by PPS
010No condition types with formula &1 found in pricing procedure &2
011Plant used for PPS call could not be determined
012Plant used for price calculation not found for customer &1
013Pricing using PPS is not possible for sales order &1
014Enter pricing date in header data
015Regular price has been redetermined by PPS
016Value &1 is not allowed in Customizing for execution sequence number
017You cannot change the quantity &1 &2 of returns item &3
018You cannot enter new items in returns with reference
100Activate business function ISR_RETAIL_OPP
101Activate formula &1 via transaction VOFM
102No condition mapping found for pricing procedure &1
103Condition type &1 has neither response source nor request target
105Condition type &1 does not exist
106Condition category of condition type &1 does not have required value &2
107Condition class of condition type &1 does not have required value &2
108Calculation type of condition type &1 does not have required value &2
109Condition type &1 uses request target &2
110Condition type &1 is not open for manual entry of regular price
111Condition type &1 using formula &2 is expected to be returned by PPS
112Condition mapping exists for condition type &1 not used in procedure &2
114Filter criterion is ignored for response source &2 of condition type &1
116Value &3 for condition type &1 with filter &2 is not a positive integer
117Condition type &1 uses response source &2
118Condition type &1: Value &3 for filter &2 too long
119Condition type &1: Condition type &3 for filter &2 does not exist
120Cond. type &1 with calc. type unequal 'B' must have a condition mapping
121Condition type &1 is not used as statistical condition
122Assign filter to percentage condition type &1 in condition mapping
123Condition type &1: Condition type &3 for filter &2 not in pricing proc.
124Create formula &1 with transaction VOFM
125Value &3 for condition type &1 with filter &2 is not a positive integer
126&1 must be the first condition type for PPS in pricing procedure
Privacy Policy