Message Number list used by SAP ABAP Class CL_BUP_RELY (General Relationship Addresses)
SAP ABAP Class CL_BUP_RELY (General Relationship Addresses) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | BUP_RELATIONS - 124 | Time restriction of relationship addresses is not possible (&1) | |
2 | Message Number | BUP_RELATIONS - 083 | Incorrect call; fill either &1 or &2 | |
3 | Message Number | BUP_RELATIONS - 084 | No relationship addresses provided for relationship type &1 | |
4 | Message Number | BUP_RELATIONS - 090 | Relationship address &1, &2, &3 does not exist | |
5 | Message Number | BUP_RELATIONS - 091 | No relationship address exists for business partners &1 and &2 | |
6 | Message Number | BUP_RELATIONS - 097 | Data required for add. processing of unit test is not persistent | |
7 | Message Number | BUP_RELATIONS - 106 | Error when determining the sort sequence for the later ASSERT | |
8 | Message Number | BUP_RELATIONS - 121 | Invalid data for creating a business partner relationship address | |
9 | Message Number | BUP_RELATIONS - 122 | Invalid data for changing a business partner relationship address | |
10 | Message Number | BUP_RELATIONS - 123 | Invalid data for deleting a business partner relationship address | |
11 | Message Number | BUP_RELATIONS - 073 | Import contains errors; no data suitable for rel. number was transferred | |
12 | Message Number | BUP_RELATIONS - 125 | Multiple changes to a relationship address in a round trip not permitted | |
13 | Message Number | BUP_RELATIONS - 126 | Only category &2 relnship addresses can be maintained using segment &1 | |
14 | Message Number | BUP_RELATIONS - 127 | Incorrect call; please fill &1 and &2 | |
15 | Message Number | BUP_RELATIONS - 148 | Enter a specific address when creating second workplace address | |
16 | Message Number | BUP_RELATIONS - 164 | Address key in CHANGED_FIELDS with address defaulting not permitted | |
17 | Message Number | BUP_RELATIONS - 165 | Transferred address keys and CHANGED_FIELDS do not match (&1) | |
18 | Message Number | BUP_RELATIONS - 167 | No input data for test variant &1; unit test will be skipped | |
19 | Message Number | BUP_RELATIONS - 168 | Reading rel.ship data with BEFORE_IMAGE only in edit mode READ_ONLY | |
20 | Message Number | BUP_RELATIONS - 036 | Invalid field &1 in the CHANGED_FIELDS change table | |
21 | Message Number | BUP_RELATIONS - 003 | Field &1 cannot be changed | |
22 | Message Number | BUP_RELATIONS - 004 | Field &1 has to be filled when creating entry | |
23 | Message Number | BUP_RELATIONS - 011 | Error when retrieving relationship messages | |
24 | Message Number | BUP_RELATIONS - 012 | Error when retrieving messages; initial source ID | |
25 | Message Number | BUP_RELATIONS - 019 | Initial relationship category is not allowed | |
26 | Message Number | BUP_RELATIONS - 026 | Invalid edit mode &1 | |
27 | Message Number | BUP_RELATIONS - 027 | Invalid value &1 as indicator for direction of a relationship | |
28 | Message Number | BUP_RELATIONS - 031 | Only relationships of type &2 can be maintained using segment &1 | |
29 | Message Number | BUP_RELATIONS - 002 | Change mode &1 not permitted | |
30 | Message Number | BUP_RELATIONS - 036 | Invalid field &1 in the CHANGED_FIELDS change table | |
31 | Message Number | BUP_RELATIONS - 047 | The record that is to be changed does not exist | |
32 | Message Number | BUP_RELATIONS - 048 | The record you want to create already exists | |
33 | Message Number | BUP_RELATIONS - 049 | The record you want to delete does not exist | |
34 | Message Number | BUP_RELATIONS - 052 | Relationship direction &1 not permitted | |
35 | Message Number | BUP_RELATIONS - 055 | Incorrect call; field &1 is not filled | |
36 | Message Number | BUP_RELATIONS - 055 | Incorrect call; field &1 is not filled | |
37 | Message Number | BUP_RELATIONS - 064 | Key is not unique |