SAP ABAP Message Class BS_SOA_COMMON (Common/generic messages for business suite service enabling)
Basic Data
Hierarchy
☛
SAP_BS_FND (Software Component) SAP Business Suite Foundation
⤷
CA-SOA (Application Component) Enterprise SOA
⤷
BS_SOA_REUSE_COMMON_OBJECTS (Package) Business Suite SOA: Reuseable Tools and Objects
⤷
⤷
Attributes
| Message class | BS_SOA_COMMON | |
| Short Description | Common/generic messages for business suite service enabling | |
| Changed On | 20110908 | |
| Last Changed At | 164655 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Attribute & is not supported | Space: object requires documentation | ||
| 2 | UUID &1 for element &2 does not comply to required pattern | The short text describes the object sufficiently | ||
| 3 | No records returned for &1 &2 | The short text describes the object sufficiently | ||
| 4 | Either &1 or &2 has to be entered | The short text describes the object sufficiently | ||
| 5 | The input order type &1 is not corresponding to the order &2 | The short text describes the object sufficiently | ||
| 6 | The input request type &1 is not corresponding to the request &2 | The short text describes the object sufficiently | ||
| 7 | & & & & | The short text describes the object sufficiently | ||
| 8 | XI message GUID cannot be derived | The short text describes the object sufficiently | ||
| 9 | The short text describes the object sufficiently | |||
| 10 | Message UUID is empty and message ID has invalid format | The short text describes the object sufficiently | ||
| 11 | Exactly-once request cannot be locked: &1 (error code: &2) | The short text describes the object sufficiently | ||
| 12 | Exactly-once request timed out (message UUID &1) | The short text describes the object sufficiently | ||
| 13 | Internal error in exactly-once processing (message UUID &1) | The short text describes the object sufficiently | ||
| 14 | Internal error storing response for request message UUID &1 | The short text describes the object sufficiently | ||
| 15 | Alteast one value has to be entered in the input parameters | The short text describes the object sufficiently | ||
| 16 | IDP framework is not instanciated during & | The short text describes the object sufficiently | ||
| 17 | Message header node is missing within the request | The short text describes the object sufficiently | ||
| 18 | The element & is missing in the message | The short text describes the object sufficiently | ||
| 19 | Excatly-once cannot be guaranteed due to missing message header UUID | The short text describes the object sufficiently | ||
| 20 | Log node is missing within the conformation | The short text describes the object sufficiently | ||
| 21 | Error while creating confirmation message: &1 | The short text describes the object sufficiently | ||
| 22 | No input data provided, error while calling API for &1. | The short text describes the object sufficiently | ||
| 23 | Element ProcessingResultCode is missing within the conformation | The short text describes the object sufficiently | ||
| 24 | System error initializing idempotency framework: &1 | The short text describes the object sufficiently | ||
| 25 | Error in the customer Inbound BADI implementation: &1 | The short text describes the object sufficiently | ||
| 26 | Error in the customer Outbound BADI implementation: &1 | The short text describes the object sufficiently | ||
| 27 | System error in the ForwardError Handling: &1 | The short text describes the object sufficiently | ||
| 28 | Value & is not allowed for the element ProcessingResultCode | The short text describes the object sufficiently | ||
| 29 | No input data for service operation &1 provided | The short text describes the object sufficiently | ||
| 30 | Error in the customer Application BADI implementation: &1 | The short text describes the object sufficiently | ||
| 31 | *** Message classes FEH*** | The short text describes the object sufficiently | ||
| 32 | Error in Retry process: No application data provided | The short text describes the object sufficiently | ||
| 33 | Error in Retry process: &1 | The short text describes the object sufficiently | ||
| 34 | User &1 has no authorization for object &2 field &3 value &4: check SU53 | The short text describes the object sufficiently | ||
| 35 | Function Module &1 could not be executed, exception: &2 | The short text describes the object sufficiently | ||
| 36 | Please provide a valid value for all mandatory parameters | The short text describes the object sufficiently | ||
| 37 | No input data provided, error while calling API. | The short text describes the object sufficiently | ||
| 38 | &1 returned with sy-subrc = &2 | The short text describes the object sufficiently | ||
| 39 | Switch &1 is switched off in client &2 | Space: object requires documentation | ||
| 40 | Business Object for Context &1 cannot be locked | The short text describes the object sufficiently | ||
| 41 | A message is missing for sequencing object &1 and context &2 | Space: object requires documentation | ||
| 42 | Exception &1 occured in &2, line &3. Error: &4 | The short text describes the object sufficiently | ||
| 43 | Either CorrelationID or MessageID must be specified. | The short text describes the object sufficiently | ||
| 44 | Postprocessing order is locked for dialog processing | The short text describes the object sufficiently | ||
| 45 | Postprocessing order is locked by automatic resubmission | The short text describes the object sufficiently | ||
| 46 | &1 operation for table &2 failed | The short text describes the object sufficiently | ||
| 47 | Unknown update indicator &1 for update of table &2 | The short text describes the object sufficiently | ||
| 48 | Postprocessing Order could not be restarted | The short text describes the object sufficiently | ||
| 49 | Path &1 is not valid within the passed message structure | The short text describes the object sufficiently | ||
| 50 | The business document message header could not be assigned | The short text describes the object sufficiently | ||
| 51 | Field &1 is not found within the specified path for the sequence fields | The short text describes the object sufficiently | ||
| 52 | bgRFC is not configured yet. Execute report RBS_SOA_IAS_SETUP_BGRFC. | Space: object requires documentation | ||
| 53 | Outbound Message &1 not found | The short text describes the object sufficiently | ||
| 54 | BADI Implementation(BS_SOA_INAPPSEQ_REC) for Filter ObjectType &1 Missing | The short text describes the object sufficiently | ||
| 55 | Connectivity type &1 is not implemented | The short text describes the object sufficiently | ||
| 56 | *** Message Container *** | The short text describes the object sufficiently | ||
| 57 | Error category & contains more than the allowed 15 characters | The short text describes the object sufficiently | ||
| 58 | The main error message & must have have the type 'E' instead of type & | The short text describes the object sufficiently | ||
| 59 | The main error message is already set | The short text describes the object sufficiently | ||
| 60 | *** DateTime conversion *** | The short text describes the object sufficiently | ||
| 61 | Content &1 is not compliant with &2 DateTime pattern | The short text describes the object sufficiently | ||
| 62 | Wrong call of method &1: either provide Date and Time or a Timestamp | The short text describes the object sufficiently | ||
| 63 | Pattern type &1 for DateTime is unknown | The short text describes the object sufficiently | ||
| 64 | Time zone &1 is not defined | The short text describes the object sufficiently | ||
| 65 | Invalid content for conversion between timestamp and date / time | The short text describes the object sufficiently |
History
| Last changed on/by | 20110908 | SAP | |
| SAP Release Created in | 701 |