Message Number list used by SAP ABAP Class CL_BUPA_BPUPTRC (Business Partner ERP Update Request Confirmation)
SAP ABAP Class CL_BUPA_BPUPTRC (Business Partner ERP Update Request Confirmation) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | BSBP_ESAMAP - 000 | Node mapping was called for a non-existent node | |
2 | Message Number | BUPA_ESOA - 001 | Either InternalID or UUID of business parnter must be provided. | |
3 | Message Number | BUPA_ESOA - 002 | Update was based on outdated data, update aborted. | |
4 | Message Number | BUPA_ESOA - 003 | Business partner cannot be identfied by internal ID '&1'. | |
5 | Message Number | BUPA_ESOA - 004 | Business partner cannot be identfied by UUD '&1'. | |
6 | Message Number | BUPA_ESOA - 005 | Service operation succeeds. | |
7 | Message Number | BUPA_ESOA - 010 | Exception: &1 | |
8 | Message Number | BUPA_ESOA - 010 | Exception: &1 | |
9 | Message Number | BUPA_ESOA - 021 | UUID &1 for element &2 does not comply to required pattern | |
10 | Message Number | BUPA_ESOA - 023 | Internal error in exactly-once processing (message UUID &1) | |
11 | Message Number | BUPA_ESOA - 024 | Exactly-once request timed out (message UUID &1) | |
12 | Message Number | BUPA_ESOA - 025 | Exactly-once request cannot be locked: &1 (error code: &2) | |
13 | Message Number | BUPA_ESOA - 028 | Exactly-once request cannot be locked: &1 (error code: &2) | |
14 | Message Number | BUPA_ESOA - 038 | Field &1 is required |