/SAPAPO/CMDS_EDIBAPI - CMDS-SD: message class for BAPI , EDI inbound processing
The following messages are stored in message class /SAPAPO/CMDS_EDIBAPI: CMDS-SD: message class for BAPI , EDI inbound processing.
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 |
|---|---|
| 002 | No control profile exists for scheduling agreement &1 |
| 003 | Could not read movement data |
| 004 | Could not find movement data for scheduling agreement &1 |
| 006 | Could not update movement data for scheduling agreement & |
| 007 | Schedule line &1 with delivery schedule ID &2 already exists |
| 008 | Schedule line not created, error in delivery schedule ID |
| 009 | Could not create schedule line &1 because of missing delivery schedule |
| 010 | Error when creating schedule lines &1 |
| 011 | LiveCache: no scheduling agreement number available |
| 012 | LiveCache: scheduling agreement &1 not selected |
| 013 | LiveCache: Idoc has an unknown delivery schedule type &1 |
| 014 | Could not create delivery schedule |
| 015 | Cannot process delivery schedule for the current scheduling agreement &1 |
| 016 | Could not create delivery schedule |
| 017 | Could not select a scheduling agreement |
| 018 | No unique scheduling agreement could be determined |
| 019 | Scheduling agreement: no processing, missing document number or item |
| 020 | Scheduling agreement is currently locked by another user |
| 021 | Error when attempting to lock the current scheduling agreement |
| 022 | Error when attempting to lock the scheduling agreement |
| 023 | Could not determine scheduling agreement &1 |
| 024 | Cannot process delivery schedule for the current scheduling agreement &1 |
| 025 | There are no old schedule lines available for transfer |
| 026 | Delivery schedule with the ID &1 already exists |
| 027 | ID for processing the schedule lines does not exist |
| 028 | Could not read schedule lines |
| 029 | Scheduling agreement &1 is not active |
| 030 | Processing and current del. schedule number in the database are identical |
| 031 | Idoc del. schedule number &1 is identical to the old del. schedule number |
| 032 | IDoc already scheduled in scheduling agreement &1 |
| 033 | Old delivery schedule number &2 <> current delivery schedule number &3 |
| 034 | Termination within the Live-Cache processing |
| 035 | IDoc &1 could not be saved in the corresponding tables |
| 036 | Planned cumulative quantity: Schedule line has been added or increased |
| 037 | Planned cumulative qty: Schedule line qty/qties has (have) been reduced |
| 038 | The cumulative issued quantity should not be negative |
| 039 | The release for scheduling agreement &1 &2 does not contain a release no. |
| 040 | The release for sched. agreement &1 &2 does not contain a release date |
| 041 | Scheduling agreement &1: IDoc processing terminated with an error |
| 042 | The received quantity is bigger than the cumulative delivery quantity |
| 043 | The received quantity is bigger than the cumulative qty of goods issued |