SAP ABAP Message Class BUP_RELATIONS (BPR: Message Class for Relationship Segments)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SRV-BP (Application Component) Business Partner Foundation
⤷
S_BUPA_IPI (Package) SAP Business Partner: Internal Programming Interface (Basis)
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-BP (Application Component) Business Partner Foundation⤷
S_BUPA_IPI (Package) SAP Business Partner: Internal Programming Interface (Basis) 
Attributes
| Message class |  |
BUP_RELATIONS |
| Short Description |  |
BPR: Message Class for Relationship Segments |
| Changed On |  |
20110908 |
| Last Changed At |  |
153055 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 2 | 001 |
Changing key fields except for &1 is not permitted | The short text describes the object sufficiently | |
| 3 | 002 |
Change mode &1 not permitted | The short text describes the object sufficiently | |
| 4 | 003 |
Field &1 cannot be changed | The short text describes the object sufficiently | |
| 5 | 004 |
Field &1 has to be filled when creating entry | The short text describes the object sufficiently | |
| 6 | 005 |
Several changes to a relationship not permitted in one round trip | The short text describes the object sufficiently | |
| 7 | 006 |
Time period has errors; there are gaps | The short text describes the object sufficiently | |
| 8 | 007 |
Time period has errors; there is overlapping | The short text describes the object sufficiently | |
| 9 | 008 |
Error in lock arguments when locking relationships | The short text describes the object sufficiently | |
| 10 | 009 |
No relationships for locking transferred | The short text describes the object sufficiently | |
| 11 | 010 |
Invalid lock mode &1 selected | The short text describes the object sufficiently | |
| 12 | 011 |
Error when retrieving relationship messages | The short text describes the object sufficiently | |
| 13 | 012 |
Error when retrieving messages; initial source ID | The short text describes the object sufficiently | |
| 14 | 013 |
Lock error; ENQUEUE_EBU_BUT050 triggers return code &1 | The short text describes the object sufficiently | |
| 15 | 014 |
You are currently locking &1 between BP &2 and BP &3 | The short text describes the object sufficiently | |
| 16 | 015 |
&1 between BP &2 and BP &3 is currently being processed by &4 | The short text describes the object sufficiently | |
| 17 | 016 |
&1 between BP &2 and BP &3 cannot be locked | The short text describes the object sufficiently | |
| 18 | 017 |
No relationships transferred for unlocking | The short text describes the object sufficiently | |
| 19 | 018 |
Error in lock arguments when unlocking relationships | The short text describes the object sufficiently | |
| 20 | 019 |
Initial relationship category is not allowed | The short text describes the object sufficiently | |
| 21 | 020 |
Could not remove lock for relationship internally (multiple locks) | The short text describes the object sufficiently | |
| 22 | 021 |
Internal unlock: Some partial locks could not be removed | The short text describes the object sufficiently | |
| 23 | 022 |
Business partner &1 does not exist | The short text describes the object sufficiently | |
| 24 | 023 |
From-date &1 is not valid | The short text describes the object sufficiently | |
| 25 | 024 |
To-date &1 is not valid | The short text describes the object sufficiently | |
| 26 | 025 |
Specify both business partners | The short text describes the object sufficiently | |
| 27 | 026 |
Invalid edit mode &1 | The short text describes the object sufficiently | |
| 28 | 027 |
Invalid value &1 as indicator for direction of a relationship | The short text describes the object sufficiently | |
| 29 | 028 |
Combination relship direction &1 and relship category &2 not permitted | The short text describes the object sufficiently | |
| 30 | 029 |
&1 between BP &2 and BP &3 was already maintained in another direction | The short text describes the object sufficiently | |
| 31 | 030 |
Maintaining a &1 using this segment (RELT) is not permitted | The short text describes the object sufficiently | |
| 32 | 031 |
Only relationships of type &2 can be maintained using segment &1 | The short text describes the object sufficiently | |
| 33 | 032 |
Only shareholder relationships can be maintained via the segment RELS | The short text describes the object sufficiently | |
| 34 | 033 |
Invalid data for creating a business partner relationship | The short text describes the object sufficiently | |
| 35 | 034 |
Invalid data for changing a business partner relationship | The short text describes the object sufficiently | |
| 36 | 035 |
Invalid data for deleting a business partner relationship | The short text describes the object sufficiently | |
| 37 | 036 |
Invalid field &1 in the CHANGED_FIELDS change table | The short text describes the object sufficiently | |
| 38 | 037 |
Error when transferring the fields from the table CHANGED_FIELDS | The short text describes the object sufficiently | |
| 39 | 038 |
Cannot update: Relationship between &1 and &2 already exists in timeframe | The short text describes the object sufficiently | |
| 40 | 039 |
Fatal error in the segment Relationships (source ID: &1) | The short text describes the object sufficiently | |
| 41 | 040 |
Fatal error in the segment Contact Person Relationship (source ID: &1) | The short text describes the object sufficiently | |
| 42 | 041 |
Fatal error in the segment Shareholder Relationship (source ID &1) | The short text describes the object sufficiently | |
| 43 | 042 |
Fatal error in the segment Relationship Addresses (source ID: &1) | The short text describes the object sufficiently | |
| 44 | 043 |
Error when replacing the temporary relationship numbers in the segment &1 | The short text describes the object sufficiently | |
| 45 | 044 |
Business partner cat. is not designated for this relationship cat. (TBZ9) | The short text describes the object sufficiently | |
| 46 | 045 |
Internal error when reading partner data via the segment CENTRAL_DATA | The short text describes the object sufficiently | |
| 47 | 046 |
Selected relships between temp. BP IDs already set in opposite direction | The short text describes the object sufficiently | |
| 48 | 047 |
The record that is to be changed does not exist | The short text describes the object sufficiently | |
| 49 | 048 |
The record you want to create already exists | The short text describes the object sufficiently | |
| 50 | 049 |
The record you want to delete does not exist | The short text describes the object sufficiently | |
| 51 | 050 |
Initial import &1 | The short text describes the object sufficiently | |
| 52 | 051 |
You are not authorized to display partner relationships | The short text describes the object sufficiently | |
| 53 | 052 |
Relationship direction &1 not permitted | The short text describes the object sufficiently | |
| 54 | 053 |
Only one standard address permitted | The short text describes the object sufficiently | |
| 55 | 054 |
One address must be flagged as the standard address | The short text describes the object sufficiently | |
| 56 | 055 |
Incorrect call; field &1 is not filled | The short text describes the object sufficiently | |
| 57 | 056 |
The standard indicator cannot be maintained (TBZ9) for a &1 | The short text describes the object sufficiently | |
| 58 | 057 |
The standard indicator cannot be maintained for time constraint type &1 | The short text describes the object sufficiently | |
| 59 | 058 |
More than one standard relationship not permitted for same point in time | The short text describes the object sufficiently | |
| 60 | 059 |
Time constraint category does not allow any of the differnt validity per. | The short text describes the object sufficiently | |
| 61 | 060 |
Another relationship already exists between &1 and &2 at this time | The short text describes the object sufficiently | |
| 62 | 061 |
The relationship between &1 and &2 to be deleted does not exist | The short text describes the object sufficiently | |
| 63 | 062 |
The relationship between partner &1 and &2 to be changed does not exist | The short text describes the object sufficiently | |
| 64 | 063 |
Relationship type &1 is not provided for relationship type &2 (&3) | The short text describes the object sufficiently | |
| 65 | 064 |
Key is not unique | The short text describes the object sufficiently | |
| 66 | 065 |
&1 cannot be deleted; error when deleting workplace address | The short text describes the object sufficiently | |
| 67 | 066 |
Workplace addresses still assigned were deleted | The short text describes the object sufficiently | |
| 68 | 067 |
Relationship of type &1 between &2 and &3 does not exist | The short text describes the object sufficiently | |
| 69 | 068 |
Relationship of type &1 between &2 and &3 does not exist at present | The short text describes the object sufficiently | |
| 70 | 069 |
Relationship of type &1 between &2 and &3 to be deleted is not available | The short text describes the object sufficiently | |
| 71 | 070 |
Relationship of type &1 between &2 and &3 to be changed does not exist | The short text describes the object sufficiently | |
| 72 | 071 |
Relship of cat. &1 already exists for point in time between &2 and &3 | The short text describes the object sufficiently | |
| 73 | 072 |
You are not authorized to display partner relationships | The short text describes the object sufficiently | |
| 74 | 073 |
Import contains errors; no data suitable for rel. number was transferred | The short text describes the object sufficiently | |
| 75 | 074 |
Special checks of &1 skipped due to severe errors | The short text describes the object sufficiently | |
| 76 | 075 |
Validity end of period has been increased from &1 to &2 | The short text describes the object sufficiently | |
| 77 | 076 |
Validity end of period has been reduced from &1 to &2 | The short text describes the object sufficiently | |
| 78 | 077 |
Time period from &1 to &2 has been deleted | The short text describes the object sufficiently | |
| 79 | 078 |
Validity start of period has been increased from &1 to &2 | The short text describes the object sufficiently | |
| 80 | 079 |
Validity start of period has been shortened from &1 to &2 | The short text describes the object sufficiently | |
| 81 | 080 |
Period from &1 to &2 has been divided | The short text describes the object sufficiently | |
| 82 | 081 |
Relationship address has been indicated as the standard address | The short text describes the object sufficiently | |
| 83 | 082 |
Indicator "Standard Address" has been deleted | The short text describes the object sufficiently | |
| 84 | 083 |
Incorrect call; fill either &1 or &2 | The short text describes the object sufficiently | |
| 85 | 084 |
No relationship addresses provided for relationship type &1 | The short text describes the object sufficiently | |
| 86 | 085 |
Key date must be filled for reading relationships | The short text describes the object sufficiently | |
| 87 | 086 |
Key date must be filled for reading relationships of category &1 | The short text describes the object sufficiently | |
| 88 | 087 |
Key date must be filled for reading shareholding relationships | The short text describes the object sufficiently | |
| 89 | 088 |
Relationship type (RELTYP) must be specified for this read access | The short text describes the object sufficiently | |
| 90 | 089 |
Not possible to restore locks for further processing | The short text describes the object sufficiently | |
| 91 | 090 |
Relationship address &1, &2, &3 does not exist | The short text describes the object sufficiently | |
| 92 | 091 |
No relationship address exists for business partners &1 and &2 | The short text describes the object sufficiently | |
| 93 | 092 |
Business partner &1 must be from the category organization or group | The short text describes the object sufficiently | |
| 94 | 093 |
BP &1 not maintained in the required role &2 for all points in time | The short text describes the object sufficiently | |
| 95 | 094 |
Not possible to maintain spec. attributes for CP rel. between persons | The short text describes the object sufficiently | |
| 96 | 095 |
Required BP category is not assigned to the business partner &1 | The short text describes the object sufficiently | |
| 97 | 096 |
Error while accessing test data container &1 | The short text describes the object sufficiently | |
| 98 | 097 |
Data required for add. processing of unit test is not persistent | The short text describes the object sufficiently | |
| 99 | 098 |
None of the data used for the unit test is in database table &1 | The short text describes the object sufficiently | |
| 100 | 099 |
Customizing of rel cat. does not correspond to expected settings (tab &1) | The short text describes the object sufficiently | |
| 101 | 100 |
There are more data records than expected in database &1 | The short text describes the object sufficiently | |
| 102 | 101 |
Internal error; exception &1 occurred | The short text describes the object sufficiently | |
| 103 | 102 |
Not possible to lock the partners required for the unit test | The short text describes the object sufficiently | |
| 104 | 103 |
Not possible to lock the relationships required for the unit test | The short text describes the object sufficiently | |
| 105 | 104 |
BAS interface could not be intialized | The short text describes the object sufficiently | |
| 106 | 105 |
Error during automatic formatting of CHANGED_FIELDS | The short text describes the object sufficiently | |
| 107 | 106 |
Error when determining the sort sequence for the later ASSERT | The short text describes the object sufficiently | |
| 108 | 107 |
You are not authorized to display and maintain business partner rels | The short text describes the object sufficiently | |
| 109 | 108 |
BP &1 not maintained in the required roles for all points in time | The short text describes the object sufficiently | |
| 110 | 109 |
Workplace address in connection with rel. type &1 is no longer supported | The short text describes the object sufficiently | |
| 111 | 110 |
Fatal error in service performer relationship segment (source ID: &1) | The short text describes the object sufficiently | |
| 112 | 111 |
Fatal error in segment &1 (source ID: &2) | The short text describes the object sufficiently | |
| 113 | 112 |
Time-dependent rel.attr. not allowed in conn. with time constraint cat &1 | The short text describes the object sufficiently | |
| 114 | 113 |
Number of rels in the set is not checked in conn. with undirected rel. | The short text describes the object sufficiently | |
| 115 | 114 |
Check of enhanced relationships not allowed using this segment (RELT) | The short text describes the object sufficiently | |
| 116 | 115 |
Business hours still assigned were deleted | The short text describes the object sufficiently | |
| 117 | 116 |
&1 cannot be deleted; error while deleting business hours | The short text describes the object sufficiently | |
| 118 | 117 |
OP_HOURS interface could not be initialized | The short text describes the object sufficiently | |
| 119 | 118 |
Initial value not allowed as indicator of the direction of a rel. | The short text describes the object sufficiently | |
| 120 | 119 |
Error in unit test: Could not create temporary partner | The short text describes the object sufficiently | |
| 121 | 120 |
Reading relationships for key date only possible in READ_ONLY edit mode | The short text describes the object sufficiently | |
| 122 | 121 |
Invalid data for creating a business partner relationship address | The short text describes the object sufficiently | |
| 123 | 122 |
Invalid data for changing a business partner relationship address | The short text describes the object sufficiently | |
| 124 | 123 |
Invalid data for deleting a business partner relationship address | The short text describes the object sufficiently | |
| 125 | 124 |
Time restriction of relationship addresses is not possible (&1) | The short text describes the object sufficiently | |
| 126 | 125 |
Multiple changes to a relationship address in a round trip not permitted | The short text describes the object sufficiently | |
| 127 | 126 |
Only category &2 relnship addresses can be maintained using segment &1 | The short text describes the object sufficiently | |
| 128 | 127 |
Incorrect call; please fill &1 and &2 | The short text describes the object sufficiently | |
| 129 | 128 |
Time-dep. rel. attributes not permitted for rel. cat. &1 and direction &2 | The short text describes the object sufficiently | |
| 130 | 129 |
Time-dependent attribute &1 cannot be maintained using segment &2 | The short text describes the object sufficiently | |
| 131 | 130 |
Function OBSOLETE - adjust calls | The short text describes the object sufficiently | |
| 132 | 131 |
Time-dependent relship attributes not permitted for relship category &1 | The short text describes the object sufficiently | |
| 133 | 132 |
Rel. between &1 and &2 does not exist; time-dep. rel.attrib. not possible | The short text describes the object sufficiently | |
| 134 | 133 |
Cannot change 'From' date of the first time-dependent relship data record | The short text describes the object sufficiently | |
| 135 | 134 |
Cannot change 'To' date of the first time-dependent relship data record | The short text describes the object sufficiently | |
| 136 | 135 |
Validity of time-dep. relship attrib. restricted by validity of relship | The short text describes the object sufficiently | |
| 137 | 136 |
Last data record time-dependent relationship attributes cannot be deleted | The short text describes the object sufficiently | |
| 138 | 137 |
Several relship validities not possible in conjunction with rel. attrib. | The short text describes the object sufficiently | |
| 139 | 138 |
Validity of associated time-dep. relship attributes has been shortened | The short text describes the object sufficiently | |
| 140 | 139 |
Associated time-dependent relationship attributes &1-&2 have been deleted | The short text describes the object sufficiently | |
| 141 | 140 |
Associated time-dependent relationship attributes &1-&2 have been created | The short text describes the object sufficiently | |
| 142 | 141 |
Validity of associated time-dependent rel. attributes has been extended | The short text describes the object sufficiently | |
| 143 | 142 |
Validity of associated time-dep. relship attributes has been adjusted | The short text describes the object sufficiently | |
| 144 | 143 |
First time-dependent relationship data record must not be deleted | The short text describes the object sufficiently | |
| 145 | 144 |
Last time-dependent relationship data record must not be deleted | The short text describes the object sufficiently | |
| 146 | 145 |
Multiple changes to time-dep. relship record not permitted (roundtrip) | The short text describes the object sufficiently | |
| 147 | 146 |
Standard flag for relationships (&1) has been set | The short text describes the object sufficiently | |
| 148 | 147 |
Cross-relationship network checks skipped due to sever error | The short text describes the object sufficiently | |
| 149 | 148 |
Enter a specific address when creating second workplace address | The short text describes the object sufficiently | |
| 150 | 149 |
Obsolete rel. cat. &1; read with intention to change no longer permitted | The short text describes the object sufficiently | |
| 151 | 150 |
Obsolete relship category &1; create/change/delete no longer permitted | The short text describes the object sufficiently | |
| 152 | 151 |
Registration of test data container with relship customizing not possible | The short text describes the object sufficiently | |
| 153 | 152 |
Not possible to determine system informationen / software component | The short text describes the object sufficiently | |
| 154 | 153 |
Sum of person references read does not match expected number | The short text describes the object sufficiently | |
| 155 | 154 |
Program may only be executed in systems with software component &1 | The short text describes the object sufficiently | |
| 156 | 155 |
Program must not be executed in systems with software component &1 | The short text describes the object sufficiently | |
| 157 | 156 |
Creation of CTDF data not possible: BP already exists (&1) | The short text describes the object sufficiently | |
| 158 | 157 |
Creation of CTDF data incomplete: Rejected changes (&1, &2) | The short text describes the object sufficiently | |
| 159 | 158 |
Termination when creating CTDF data: Error when saving (&1, &2) | The short text describes the object sufficiently | |
| 160 | 159 |
Common Test Data Framework data created and saved successfully (&1, &2) | The short text describes the object sufficiently | |
| 161 | 160 |
Deletion of CTDF data not complete: Rejected changes (&1, &2) | The short text describes the object sufficiently | |
| 162 | 161 |
Termination when deleting CTDF Data: Error when saving (&1, &2) | The short text describes the object sufficiently | |
| 163 | 162 |
CTDF Data successfully initialized/deleted (&1, &2) | The short text describes the object sufficiently | |
| 164 | 163 |
DO access cannot be initialized | The short text describes the object sufficiently | |
| 165 | 164 |
Address key in CHANGED_FIELDS with address defaulting not permitted | The short text describes the object sufficiently | |
| 166 | 165 |
Transferred address keys and CHANGED_FIELDS do not match (&1) | The short text describes the object sufficiently | |
| 167 | 166 |
Specify validity when creating time-dependent relationship data | The short text describes the object sufficiently | |
| 168 | 167 |
No input data for test variant &1; unit test will be skipped | The short text describes the object sufficiently | |
| 169 | 168 |
Reading rel.ship data with BEFORE_IMAGE only in edit mode READ_ONLY | The short text describes the object sufficiently | |
| 170 | 169 |
Relationship category (RELTYP) needs to be specified to access data | The short text describes the object sufficiently | |
| 171 | 170 |
Obsolete relationship category &1; access for modification not permitted | The short text describes the object sufficiently | |
| 172 | 171 |
&1 between BP &2 and BP &3 cannot be locked (shared lock BP &4) | The short text describes the object sufficiently | |
| 173 | 172 |
BP &1 does not exist; shared lock for relationship not possible | The short text describes the object sufficiently | |
| 174 | 173 |
Authorization f. BP maint. missing; shared lock f. rel.ship not possible | The short text describes the object sufficiently | |
| 175 | 174 |
BP &1 already has max. no. of rel.ships possible for rel.ship category &2 | Space: object requires documentation | |
| 176 | 175 |
Max. no of relationships (&1) of category &2 exceeded in relationship set | Space: object requires documentation | |
| 177 | 176 |
&1: Error in TEARDOWN due to locks for non-existing relationships | The short text describes the object sufficiently | |
| 178 | 177 |
&1 between BP &2 and BP &3 has been changed in parallel session | The short text describes the object sufficiently |
History
| Last changed on/by | |
20110908 | SAP |
| SAP Release Created in | 710 |
