PP_ODATA_API_PLDORD - Messages for Planned Order OData API
The following messages are stored in message class PP_ODATA_API_PLDORD: Messages for Planned Order OData API.
It is part of development package ODATA_PP_PLDORDER_API in software component PP-MRP. This development package consists of objects that can be grouped under "OData APIs for Planned Order".
It is part of development package ODATA_PP_PLDORDER_API in software component PP-MRP. This development package consists of objects that can be grouped under "OData APIs for Planned Order".
Message Nr ▲ | Message Text |
---|---|
000 | MaterialProcurementCategory: Only &1 supported |
001 | MaterialProcurementType: Only &1 supported |
002 | AccountAssignmentCategory: &1 not supported |
003 | &1: Property not allowed |
004 | Planned order &1 could not be locked |
005 | Operations in change set are not supported |
006 | Multiple changes on planned order &1 within one changeset not allowed |
007 | Multiple changes on component &1 &2 within one changeset not allowed |
008 | Property PlannedOrder needs to be provided |
009 | Planned Order number from URI (&1) and request body (&2) do not match |
010 | PlannedOrder: '&1' - Order numbers with lowercase letters not supported |
011 | Planned Order &1/&2/&3/&4, Scheduling mode is not supported |
012 | Planned Order &1/&2/&3/&4, Scheduling status is not supported |
013 | For Planned Order &1,SchedldStartDate/SchedldStartTime is required |
014 | For Planned Order &1,SchedldEndTime/SchedldEndDate is required |
015 | Etag value must be in 'yyyy-mm-ddThh:mm:ss[.fffffff]Z|vii:nn' format |
016 | Planned Order &1 for Operation &2 scheduled successfully |
017 | For Planned Order &1/&2/&3/&4,SchedulingStrategy is not supported |
018 | For Planned order &1, Operations identifier must be unique |
019 | No valid operations found for Planned order &1 |