BS_SOA_COMMON - Common/generic messages for business suite service enabling
The following messages are stored in message class BS_SOA_COMMON: Common/generic messages for business suite service enabling.
It is part of development package BS_SOA_REUSE_COMMON_OBJECTS in software component CA-SOA. This development package consists of objects that can be grouped under "Business Suite SOA: Reuseable Tools and Objects".
It is part of development package BS_SOA_REUSE_COMMON_OBJECTS in software component CA-SOA. This development package consists of objects that can be grouped under "Business Suite SOA: Reuseable Tools and Objects".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Attribute & is not supported |
| 001 | UUID &1 for element &2 does not comply to required pattern |
| 002 | No records returned for &1 &2 |
| 003 | Either &1 or &2 has to be entered |
| 004 | The input order type &1 is not corresponding to the order &2 |
| 005 | The input request type &1 is not corresponding to the request &2 |
| 006 | & & & & |
| 007 | XI message GUID cannot be derived |
| 008 | |
| 009 | Message UUID is empty and message ID has invalid format |
| 010 | Exactly-once request cannot be locked: &1 (error code: &2) |
| 011 | Exactly-once request timed out (message UUID &1) |
| 012 | Internal error in exactly-once processing (message UUID &1) |
| 013 | Internal error storing response for request message UUID &1 |
| 014 | Alteast one value has to be entered in the input parameters |
| 015 | IDP framework is not instanciated during & |
| 016 | Message header node is missing within the request |
| 017 | The element & is missing in the message |
| 018 | Excatly-once cannot be guaranteed due to missing message header UUID |
| 019 | Log node is missing within the conformation |
| 020 | Error while creating confirmation message: &1 |
| 021 | No input data provided, error while calling API for &1. |
| 022 | Element ProcessingResultCode is missing within the conformation |
| 023 | System error initializing idempotency framework: &1 |
| 024 | Error in the customer Inbound BADI implementation: &1 |
| 025 | Error in the customer Outbound BADI implementation: &1 |
| 026 | System error in the ForwardError Handling: &1 |
| 027 | Value & is not allowed for the element ProcessingResultCode |
| 028 | No input data for service operation &1 provided |
| 029 | Error in the customer Application BADI implementation: &1 |
| 030 | *** Message classes FEH*** |
| 031 | Error in Retry process: No application data provided |
| 032 | Error in Retry process: &1 |
| 040 | User &1 has no authorization for object &2 field &3 value &4: check SU53 |
| 041 | Function Module &1 could not be executed, exception: &2 |
| 042 | Please provide a valid value for all mandatory parameters |
| 045 | No input data provided, error while calling API. |
| 046 | &1 returned with sy-subrc = &2 |
| 050 | Switch &1 is switched off in client &2 |
| 051 | Business Object for Context &1 cannot be locked |
| 060 | A message is missing for sequencing object &1 and context &2 |
| 061 | Exception &1 occured in &2, line &3. Error: &4 |
| 062 | Either CorrelationID or MessageID must be specified. |
| 063 | Postprocessing order is locked for dialog processing |
| 064 | Postprocessing order is locked by automatic resubmission |
| 065 | &1 operation for table &2 failed |
| 066 | Unknown update indicator &1 for update of table &2 |
| 067 | Postprocessing Order could not be restarted |
| 068 | Path &1 is not valid within the passed message structure |
| 069 | The business document message header could not be assigned |
| 070 | Field &1 is not found within the specified path for the sequence fields |
| 071 | bgRFC is not configured yet. Execute report RBS_SOA_IAS_SETUP_BGRFC. |
| 072 | Outbound Message &1 not found |
| 073 | BADI Implementation(BS_SOA_INAPPSEQ_REC) for Filter ObjectType &1 Missing |
| 074 | Connectivity type &1 is not implemented |
| 090 | *** Message Container *** |
| 091 | Error category & contains more than the allowed 15 characters |
| 092 | The main error message & must have have the type 'E' instead of type & |
| 093 | The main error message is already set |
| 110 | *** DateTime conversion *** |
| 111 | Content &1 is not compliant with &2 DateTime pattern |
| 112 | Wrong call of method &1: either provide Date and Time or a Timestamp |
| 113 | Pattern type &1 for DateTime is unknown |
| 114 | Time zone &1 is not defined |
| 115 | Invalid content for conversion between timestamp and date / time |