PP_ODATA_API_PRODORD - Message class for API_PRODUCTION_ORDER
The following messages are stored in message class PP_ODATA_API_PRODORD: Message class for API_PRODUCTION_ORDER.
It is part of development package ODATA_PP_API_PRODORDER_2 in software component PP-ES. This development package consists of objects that can be grouped under "OData APIs for Production Order".
It is part of development package ODATA_PP_API_PRODORDER_2 in software component PP-ES. This development package consists of objects that can be grouped under "OData APIs for Production Order".
Message Nr ▲ | Message Text |
---|---|
000 | &1: Property not allowed. |
001 | Only one item is supported. |
002 | Production order &1 could not be locked. |
003 | Order &1 could not be read. |
004 | Change of property &1 in order &2 not allowed. |
005 | Order &1 was changed. |
006 | Order &1 was not changed. |
007 | Production order &1 |
008 | Multiple changes on order &1 within one changeset not allowed |
009 | Planned order &1 |
010 | Production Order &1/&2/&3, Scheduling mode is not supported |
011 | Production Order &1/&2/&3, Scheduling status is not supported |
012 | For Production Order &1,SchedldStartDate/SchedldStartTime is required |
013 | For Production Order &1,SchedldEndTime/SchedldEndDate is required |
014 | Etag value must be in 'YYYYMMDDHHMMSS' format |
015 | Production Order &1 for Operation &2 scheduled successfully |
016 | For Production Order &1/&2/&3,SchedulingStrategy is not supported |
017 | For Production order &1, Operations identifier must be unique |
018 | No valid operations found for Production order &1 |
019 | Order &1: External- and internal WBSElement does not fit together |
102 | Process order &1 could not be locked |
103 | Process order &1 could not be read |
104 | Change of property &1 in process order &2 not allowed |
105 | Process order &1 was changed |
106 | Process order &1 was not changed |
107 | Process order &1 |
108 | Multiple changes on proc order &1 within one changeset not allowed |
109 | Order &1: |
110 | Process Order &1/&2/&3, Scheduling mode is not supported |
111 | Process Order &1/&2/&3, Scheduling status is not supported |
112 | For Process Order &1,SchedldStartDate/SchedldStartTime is required |
113 | For Process Order &1,SchedldEndTime/SchedldEndDate is required |
114 | Etag value must be in 'YYYYMMDDHHMMSS' format |
115 | Process Order &1 for Operation &2 scheduled successfully |
116 | For Process Order &1/&2/&3,SchedulingStrategy is not supported |
117 | For Process order &1, Operations identifier must be unique |
118 | No valid operations found for Process order &1 |
119 | Order &1: Status "&2" is not allowed |
120 | Order &1: Status "&2" already exists |
121 | Order &1: Status "&2" is activated |
122 | Order &1: Status "&2" isn't set; object not found |
123 | Order &1: Status "&2" isn't set; status inconsistency |
124 | Order &1: Status "&2" isn't set; wrong input |
125 | Order &1: Status "&2" isn't set, warning occurred |
126 | No Material in Order &1 found. |
127 | Order &1: Order &2 is successfully created |
128 | Provide mandatory property &1 |
129 | Value &1 of parameter &2 must not be longer than &3 characters |
130 | Order &1: No change found |
131 | Order &1: Update rejected |
132 | Order &1: Budget rejected |
133 | Different operations are not allowed in a change set |
134 | Only one operation is allowed in a change set |
135 | No eTag in Order &1 found |
136 | Order &1 hasn't been distributed yet; Status "&2" is not possible |
137 | Order &1 Operation &2 not found |
138 | Production unit of measure &1 in order &2 cannot be changed |
139 | Order &1 Operation &2 Sequence &3 not found |
140 | Order &1 is not released |
141 | Order &1: The "Delivery Completed" indicator is already set |
142 | Order &1: The "Delivery Completed" indicator is set |
143 | Provided values for UoM are not equivalent (&1: &2; ISO: &3; SAP: &4) |
144 | &1: Values for UoM do not match (ProductionUnit: &2; ISO: &3; SAP: &4) |