WB2_SE_TRO - Message Class for Trading Order Services
The following messages are stored in message class WB2_SE_TRO: Message Class for Trading Order Services.
It is part of development package WB2_SE_XI_PROXY in software component LO-GT. This development package consists of objects that can be grouped under "Trading Contract Proxies".
It is part of development package WB2_SE_XI_PROXY in software component LO-GT. This development package consists of objects that can be grouped under "Trading Contract Proxies".
Message Nr ▲ | Message Text |
---|---|
000 | & records selected |
001 | No trading order specified |
002 | Wrong action code (Delete) for create/change service |
003 | Content of field &1 is too long; only &2 characters are allowed |
004 | Action code &1 (&2) is not supported for &3; use create or change |
005 | Action code &1 (&2) on each level: no action was done |
006 | Action code &1 for &2 contradicts action code &3 for &4 |
007 | Action code &1 (&2) is not supported; it was used for &3 |
008 | Parameter &1 and parameter &2 must have the same value |
009 | BusinessDocumentTypeCode &1 cannot be mapped to category of causing doc. |
010 | Category &1 of causing doc. cannot be mapped to BusinessDocumentTypeCode |
011 | Mapping of expenses: PriceSpecificationElementTypeCode is initial |
012 | Mapping of expenses: at least one field is initial: |
013 | field: &1, value: &2; field: &3, value: &4 |
014 | Trading Order &1, condition key &2: more than 99 condition items |
015 | Only one-dimensional scales are supported; current dimension: &1 |
016 | Neither currency &1 nor &2 match the local currency &3 of the document |
017 | Neither currency &1 nor &2 match the sales-side currency &3 of the doc |
018 | Neither currency &1 nor &2 match the purchase-side currency &3 of the doc |
019 | Outbound proxy &1 could not be processed because of error |
020 | Action code &1 is not valid; it was used for &2 |
021 | Exactly-once request cannot be locked: &1 (error code &2) |
022 | At least one selection condition must be maintained |
023 | PlantID (&1) and LocationInternalID (&2) must have the same values |
024 | UoM must be the same on item (&1) and schedule line level (&2) |
025 | Conversion error: &1 &2 ( &3 ) to external format |
026 | ValueGroup &1 is not definite for ConfigurationPropertyValuation &2 |
027 | No trading order specified: add the ID to the payload |
028 | Item &1: Different sales currencies on header and item level (&2, &3) |
029 | Home currency could not be determined; see long text |
030 | Neither the sales org nor the purchasing org are maintained |
031 | Create service: Action code &1 not allowed. |
032 | Item &1: Sales currency on header level needed to map sales item currency |
033 | Negative value is not allowed as tolerance. Current value: &1. |
034 | &1 is not supported for &2 action code &3 |
035 | &1: &2 is not a valid code value |
036 | Ordinal number value &1 is not in supported range between &2 and &3 |
037 | &1: no value mapping is defined for internal value &2 |
038 | |
039 | Internal ID of commodity future item with external ID &1 not found (&2) |
040 | Internal ID of price component with external ID &1 not found (&2) |
041 | Internal ID of PPE is not numeric. |
042 | Trading contract application does not support field &1, check interface |