/SAPAPO/CMDS_EDI_APO - CMDS-SD: messages EDI inbound processing, variable message
The following messages are stored in message class /SAPAPO/CMDS_EDI_APO: CMDS-SD: messages EDI inbound processing, variable message.
It is part of development package /SAPAPO/CMDS in software component SCM-APO-PPS-CDS. This development package consists of objects that can be grouped under "Collaborative Management of Delivery Schedules (SD)".
It is part of development package /SAPAPO/CMDS in software component SCM-APO-PPS-CDS. This development package consists of objects that can be grouped under "Collaborative Management of Delivery Schedules (SD)".
Message Nr ▲ | Message Text |
|---|---|
| 008 | Error during the determination of the time zone for the sched. agreement |
| 009 | Could not select location (locto) for scheduling agreement |
| 010 | Delivery schedule for scheduling agreement &1 has been processed |
| 011 | Could not successfully process scheduling agreement &1 |
| 012 | BAPI cancelled during the processing of the IDoc with the number &1 |
| 018 | LiveCache: Error in function module: RRP_COMMIT , scheduling agreement &1 |
| 019 | Could not process scheduling agreement &1 delivered by IDoc |
| 020 | Cannot process delivery schedule ID &1 in IDoc |
| 021 | Cannot process forecast delivery schedule key &1 in IDoc |
| 022 | No entry for the customer material exists in IDoc &1 |
| 023 | Error &1 = &2 has been transmitted by the translator |
| 024 | More than one item exists in IDoc &1 |
| 025 | Transmitted date qualifier &1 is invalid |
| 045 | No unique unit of measure for converting IDoc to SAP unit of measure |
| 046 | No conversion of IDoc Sales unit of measure &1 to SAP Sales unit |
| 047 | IDoc has no value for the sales unit of measure |
| 048 | Different units of measure IDoc with &1, scheduling agreement &2 with &3 |
| 049 | Scheduling agreement &1 is not active |
| 050 | No sold-to party found for vendor number &1, plant &2, unloading point &3 |
| 051 | Sold-to party &1 has no special rule |
| 052 | Forecast del. schedule for sold-to party &1 has no 'Testrun' indicator |
| 053 | 'Testrun' indicator set for operative del. schedule for sold-to party &1 |
| 054 | Determination of scheduling agreement canceled |
| 055 | No scheduling agreement could be determined |
| 056 | Error during scheduling agreement selection within the popup |
| 057 | Scheduling agrmt &1, material, customer &2, sold-to party &3, plant &4 |
| 058 | Unloading point &1, usage indicator &2, sales org. &3, distr.channel &4 |
| 059 | Division &1, order type &2, customer PO number &3 |
| 060 | Selected &1 scheduling agreements, no unique selection possible |
| 061 | Date: from-to different for schedule line with the date type & |
| 062 | Date: from-to not correct for the interval entry for schedule line & |
| 063 | Error when checking the date: from-to at schedule line level |
| 064 | System selected & sched. agrmts., implicit determination started |
| 065 | Could not find scheduling agreement with the sales document number & |
| 066 | IDoc scheduling terminated |
| 067 | No scheduling agreement with the order number & has been selected |
| 068 | No scheduling agreement could be determined |
| 069 | Could not select one unique scheduling agreement |
| 071 | Odette is only partially supported in the transmission of the pickup date |
| 100 | Confirmation has been processed for scheduling agreement &2 |
| 101 | Confirmation has not been processed for scheduling agreement &2 |
| 102 | Material not found for scheduling agreement &2 |
| 103 | Vendor not found for scheduling agreement &2 |
| 104 | Plant not found for scheduling agreement &2 |
| 105 | Scheduling agreement &2 not found |
| 106 | liveCache: error in RRP_COMMIT, scheduling agreement &2 |
| 107 | Confirmation not allowed for scheduling agreement &2 |
| 108 | liveCache: error in CMDS_ACKN_TO_LC, scheduling agreement &2 |
| 109 | Select one scheduling agreement at a time for processing |
| 110 | Sales unit &1 is not an ISO code |
| 111 | An unknown error occurred during confirmation receipt |
| 112 | External procurement relationship &1 &2 could not be locked |