BUP_RELATIONS - GPB: Nachrichtenklasse f�r Beziehungssegmente
The following messages are stored in message class BUP_RELATIONS: GPB: Nachrichtenklasse f�r Beziehungssegmente.
It is part of development package S_BUPA_IPI in software component BC-SRV-BP. This development package consists of objects that can be grouped under "SAP Business Partner: Internal Programming Interface (Basis)".
It is part of development package S_BUPA_IPI in software component BC-SRV-BP. This development package consists of objects that can be grouped under "SAP Business Partner: Internal Programming Interface (Basis)".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | Changing key fields except for &1 is not permitted |
| 002 | Change mode &1 not permitted |
| 003 | Field &1 cannot be changed |
| 004 | Field &1 has to be filled when creating entry |
| 005 | Multiple changes to the same relationship not permitted in one round trip |
| 006 | Time period has errors; there are gaps |
| 007 | Time period has errors; there is overlapping |
| 008 | Error in lock arguments when locking relationships |
| 009 | No relationships for locking were passed |
| 010 | Invalid lock mode &1 selected |
| 011 | Error when retrieving relationship messages |
| 012 | Error when retrieving messages; initial source ID |
| 013 | Lock error; ENQUEUE_EBU_BUT050 triggers return code &1 |
| 014 | You are currently locking &1 between BP &2 and BP &3 |
| 015 | &1 between BP &2 and BP &3 is currently being processed by &4 |
| 016 | &1 between BP &2 and BP &3 cannot be locked |
| 017 | No relationships for unlocking were passed |
| 018 | Error in lock arguments when unlocking relationships |
| 019 | Initial relationship category is not allowed |
| 020 | Could not remove lock for relationship internally (multiple locks) |
| 021 | Internal unlock: Some partial locks could not be removed |
| 022 | Business partner &1 does not exist |
| 023 | From-date &1 is not valid |
| 024 | To-date &1 is not valid |
| 025 | Specify both business partners |
| 026 | Invalid edit mode &1 |
| 027 | Invalid value &1 as indicator for direction of a relationship |
| 028 | Combination relship direction &1 and relship category &2 not permitted |
| 029 | &1 between BP &2 and BP &3 was already maintained in another direction |
| 030 | A &1 cannot be edited using this segment (RELT) |
| 031 | Only relationships of type &2 can be maintained using segment &1 |
| 032 | Only shareholder relationships can be defined using the segment RELS |
| 033 | Invalid data for creating a business partner relationship |
| 034 | Invalid data for changing a business partner relationship |
| 035 | Invalid data for deleting a business partner relationship |
| 036 | Invalid field &1 in the CHANGED_FIELDS change table |
| 037 | Error when transferring the fields from the table CHANGED_FIELDS |
| 038 | Cannot update: Relationship between &1 and &2 already exists in timeframe |
| 039 | Fatal error in the segment Relationships (source ID: &1) |
| 040 | Fatal error in the segment Contact Person Relationship (source ID: &1) |
| 041 | Fatal error in the segment Shareholder Relationship (source ID &1) |
| 042 | Fatal error in the segment Relationship Addresses (source ID: &1) |
| 043 | Error when replacing the temporary relationship numbers in the segment &1 |
| 044 | Business partner cat. is not designated for this relationship cat. (TBZ9) |
| 045 | Internal error when reading partner data using the segment CENTRAL_DATA |
| 046 | Selected relships between temp. BP IDs already set in opposite direction |
| 047 | The record that is to be changed does not exist |
| 048 | The record you want to create already exists |
| 049 | The record you want to delete does not exist |
| 050 | Initial import &1 |
| 051 | You are not authorized to display partner relationships |
| 052 | Relationship direction &1 not permitted |
| 053 | Only one standard address permitted |
| 054 | One address must be flagged as the standard address |
| 055 | Incorrect call; field &1 is not filled |
| 056 | The standard indicator cannot be maintained (TBZ9) for a &1 |
| 057 | The standard indicator cannot be maintained for time constraint type &1 |
| 058 | More than one standard relationship not permitted for same point in time |
| 059 | Time constraint category does not allow any differing validity periods |
| 060 | Another relationship already exists between &1 and &2 at this time |
| 061 | The relationship between &1 and &2 to be deleted does not exist |
| 062 | The relationship between partner &1 and &2 to be changed does not exist |
| 063 | Relationship type &1 is not provided for relationship type &2 (&3) |
| 064 | Key is not unique |
| 065 | &1 cannot be deleted; error when deleting workplace address |
| 066 | Workplace addresses still assigned were deleted |
| 067 | Relationship of type &1 between &2 and &3 does not exist |
| 068 | Relationship of type &1 between &2 and &3 does not exist at present |
| 069 | Relationship of type &1 between &2 and &3 to be deleted is not available |
| 070 | Relationship of type &1 between &2 and &3 to be changed does not exist |
| 071 | Relship of cat. &1 already exists for point in time between &2 and &3 |
| 072 | You are not authorized to display partner relationships |
| 073 | Errors in import; no data suitable for relationship number was passed |
| 074 | Special checks of &1 skipped due to severe errors |
| 075 | Validity end of period has been increased from &1 to &2 |
| 076 | Validity end of period has been reduced from &1 to &2 |
| 077 | Time period from &1 to &2 has been deleted |
| 078 | Validity start of period has been increased from &1 to &2 |
| 079 | Validity start of period has been shortened from &1 to &2 |
| 080 | Period from &1 to &2 has been divided |
| 081 | Relationship address has been indicated as the standard address |
| 082 | Indicator "Standard Address" has been deleted |
| 083 | Incorrect call; fill either &1 or &2 |
| 084 | No relationship addresses provided for relationship type &1 |
| 085 | Key date must be filled for reading relationships |
| 086 | Key date must be filled for reading relationships of category &1 |
| 087 | Key date must be filled for reading shareholding relationships |
| 088 | Relationship type (RELTYP) must be specified for this read access |
| 089 | Not possible to restore locks for further processing |
| 090 | Relationship address &1, &2, &3 does not exist |
| 091 | No relationship address exists for business partners &1 and &2 |
| 092 | Business partner &1 must be from the category organization or group |
| 093 | BP &1 not maintained in the required role &2 for all points in time |
| 094 | Not possible to maintain spec. attributes for CP rel. between persons |
| 095 | Required BP category is not assigned to the business partner &1 |
| 096 | Error while accessing test data container &1 |
| 097 | Data required for add. processing of unit test is not persistent |
| 098 | None of the data used for the unit test is in database table &1 |
| 099 | Customizing of rel cat. does not correspond to expected settings (tab &1) |
| 100 | There are more data records than expected in database &1 |
| 101 | Internal error; exception &1 was raised |
| 102 | Not possible to lock the partners required for the unit test |
| 103 | Not possible to lock the relationships required for the unit test |
| 104 | BAS interface could not be intialized |
| 105 | Error during automatic formatting of CHANGED_FIELDS |
| 106 | Error when determining the sort order for the later ASSERT |
| 107 | You are not authorized to display and maintain business partner rels |
| 108 | BP &1 not maintained in the required roles for all points in time |
| 109 | Workplace address in connection with rel. type &1 is no longer supported |
| 110 | Fatal error in service performer relationship segment (source ID: &1) |
| 111 | Fatal error in segment &1 (source ID: &2) |
| 112 | Time-dependent rel.attr. not allowed in conn. with time constraint cat &1 |
| 113 | Number of rels in the set is not checked in conn. with undirected rel. |
| 114 | Check of enhanced relationships not allowed using this segment (RELT) |
| 115 | Business hours still assigned were deleted |
| 116 | &1 cannot be deleted; error while deleting business hours |
| 117 | OP_HOURS interface could not be initialized |
| 118 | Initial value not allowed as indicator of the direction of a rel. |
| 119 | Error in unit test: Could not create temporary partner |
| 120 | Reading relationships for key date only possible in READ_ONLY edit mode |
| 121 | Invalid data for creating a business partner relationship address |
| 122 | Invalid data for changing a business partner relationship address |
| 123 | Invalid data for deleting a business partner relationship address |
| 124 | Time restriction of relationship addresses is not possible (&1) |
| 125 | Multiple changes to a relationship address in a round trip not permitted |
| 126 | Only category &2 relnship addresses can be maintained using segment &1 |
| 127 | Incorrect call; &1 and &2 not filled |
| 128 | Time-dep. rel. attributes not permitted for rel. cat. &1 and direction &2 |
| 129 | Time-dependent attribute &1 cannot be maintained using segment &2 |
| 130 | Function OBSOLETE - adjust calls |
| 131 | Time-dependent relship attributes not permitted for relship category &1 |
| 132 | Rel. between &1 and &2 does not exist; time-dep. rel.attrib. not possible |
| 133 | Cannot change 'From' date of the first time-dependent relship data record |
| 134 | Cannot change 'To' date of the first time-dependent relship data record |
| 135 | Validity of time-dep. relship attrib. restricted by validity of relship |
| 136 | Last data record time-dependent relationship attributes cannot be deleted |
| 137 | Multiple validities not possible with relationship attributes |
| 138 | Validity of associated time-dep. relship attributes has been shortened |
| 139 | Associated time-dependent relationship attributes &1-&2 have been deleted |
| 140 | Associated time-dependent relationship attributes &1-&2 have been created |
| 141 | Validity of associated time-dependent rel. attributes has been extended |
| 142 | Validity of associated time-dep. relship attributes has been adjusted |
| 143 | First time-dependent relationship data record must not be deleted |
| 144 | Last time-dependent relationship data record must not be deleted |
| 145 | Multiple changes to time-dep. relship record not permitted (roundtrip) |
| 146 | Standard flag for relationships (&1) has been set |
| 147 | Cross-relationship network checks skipped due to sever error |
| 148 | Enter a specific address when creating second workplace address |
| 149 | Obsolete rel. cat. &1; read with intention to change no longer permitted |
| 150 | Obsolete relship category &1; create/change/delete no longer permitted |
| 151 | Registration of test data container with relship customizing not possible |
| 152 | Not possible to determine system informationen / software component |
| 153 | Sum of person references read does not match expected number |
| 154 | Program may only be executed in systems with software component &1 |
| 155 | Program must not be executed in systems with software component &1 |
| 156 | Creation of CTDF data not possible: BP already exists (&1) |
| 157 | Creation of CTDF data incomplete: Rejected changes (&1, &2) |
| 158 | Termination when creating CTDF data: Error when saving (&1, &2) |
| 159 | CTDF data created and saved (&1, &2) |
| 160 | Deletion of CTDF data not complete: Rejected changes (&1, &2) |
| 161 | Termination when deleting CTDF Data: Error when saving (&1, &2) |
| 162 | CTDF data initialized/deleted (&1, &2) |
| 163 | DO access cannot be initialized |
| 164 | Address key in CHANGED_FIELDS with address defaulting not permitted |
| 165 | Passed address keys and CHANGED_FIELDS do not match (&1) |
| 166 | Specify validity when creating time-dependent relationship data |
| 167 | No input data for test variant &1; unit test will be skipped |
| 168 | Reading rel.ship data with BEFORE_IMAGE only in edit mode READ_ONLY |
| 169 | Relationship category (RELTYP) needs to be specified to access data |
| 170 | Obsolete relationship category &1; access for modification not permitted |
| 171 | &1 between BP &2 and BP &3 cannot be locked (shared lock BP &4) |
| 172 | BP &1 does not exist; shared lock for relationship not possible |
| 173 | Authorization f. BP maint. missing; shared lock f. rel.ship not possible |
| 174 | BP &1 already has max. no. of rel.ships possible for rel.ship category &2 |
| 175 | Max. no of relationships (&1) of category &2 exceeded in relationship set |
| 176 | &1: Error in TEARDOWN due to locks for nonexistent relationships |
| 177 | &1 between BP &2 and BP &3 has been changed in parallel session |