OPS_SE_SHP_SC - Messages for Delivery Services
The following messages are stored in message class OPS_SE_SHP_SC: Messages for Delivery Services.
It is part of development package OPS_SE_SHP_XI_PROXY in software component LE-SHP-GF-ES. This development package consists of objects that can be grouped under "Web Service Proxies Delivery".
It is part of development package OPS_SE_SHP_XI_PROXY in software component LE-SHP-GF-ES. This development package consists of objects that can be grouped under "Web Service Proxies Delivery".
Message Nr ▲ | Message Text |
---|---|
000 | Delivery &1 cannot be processed with this service |
001 | Cannot refer to both complete sales order and single sales order item |
002 | Message ID is &1 |
003 | Exception &1 occured in &2 |
004 | Synchronous output processing failed |
005 | Failed to process output &1 during delivery deletion |
006 | Domain &1 value &2 not found in language &3 |
007 | Partner function &1 not found |
008 | Value &1 of &2 not supported |
009 | &1 was received with ID &2 |
010 | No number range interval for delivery group type &1 |
011 | No number in delivery group number range interval &1 |
012 | No inbound delivery could be created |
013 | Open interval not supported as selection criteria for &1 |
014 | Supplier &1 not found in referenced purchase order |
015 | Inbound delivery could not be determined |
016 | No purchase order item referenced by delivery &1 &2 |
017 | No external identification of delivery note |
018 | No data available for message creation |
019 | No processing class found |
020 | Purchase order &1 not found |
021 | Reason &1 for POD difference not found |
022 | Incompatible types &1 and &2 when mapping component &3 to &4 |
023 | &1 is not a structure |
024 | No supplier confirmation found for purchase order &1 &2 |
025 | Error occured while converting from ESA-Service intervals to ABAP ranges. |
026 | &1/&2 Order/Itemnumber does not exist. |
027 | Inbound Delivery &1 was confirmed |
028 | Inbound Delivery &1 could not be confirmed |
114 | BusinessTransactionDocument &1 is not of type &2 |
130 | Field & required |
131 | Fill mandatory field &1 |
132 | Filling &1 or &2 makes the other mandatory |