Message Number list used by SAP ABAP Class CL_BUP_RELT_CHECK (BP Relationships: Checks for Segment Relationships (BUT050))
SAP ABAP Class CL_BUP_RELT_CHECK (BP Relationships: Checks for Segment Relationships (BUT050)) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | BUP_RELATIONS - 007 | Time period has errors; there is overlapping | |
2 | Message Number | BUP_RELATIONS - 175 | Max. no of relationships (&1) of category &2 exceeded in relationship set | |
3 | Message Number | BUP_RELATIONS - 174 | BP &1 already has max. no. of rel.ships possible for rel.ship category &2 | |
4 | Message Number | BUP_RELATIONS - 131 | Time-dependent relship attributes not permitted for relship category &1 | |
5 | Message Number | BUP_RELATIONS - 118 | Initial value not allowed as indicator of the direction of a rel. | |
6 | Message Number | BUP_RELATIONS - 113 | Number of rels in the set is not checked in conn. with undirected rel. | |
7 | Message Number | BUP_RELATIONS - 112 | Time-dependent rel.attr. not allowed in conn. with time constraint cat &1 | |
8 | Message Number | BUP_RELATIONS - 108 | BP &1 not maintained in the required roles for all points in time | |
9 | Message Number | BUP_RELATIONS - 095 | Required BP category is not assigned to the business partner &1 | |
10 | Message Number | BUP_RELATIONS - 093 | BP &1 not maintained in the required role &2 for all points in time | |
11 | Message Number | BUP_RELATIONS - 063 | Relationship type &1 is not provided for relationship type &2 (&3) | |
12 | Message Number | BUP_RELATIONS - 059 | Time constraint category does not allow any of the differnt validity per. | |
13 | Message Number | BUP_RELATIONS - 058 | More than one standard relationship not permitted for same point in time | |
14 | Message Number | BUP_RELATIONS - 057 | The standard indicator cannot be maintained for time constraint type &1 | |
15 | Message Number | BUP_RELATIONS - 056 | The standard indicator cannot be maintained (TBZ9) for a &1 | |
16 | Message Number | BUP_RELATIONS - 045 | Internal error when reading partner data via the segment CENTRAL_DATA | |
17 | Message Number | BUP_RELATIONS - 044 | Business partner cat. is not designated for this relationship cat. (TBZ9) | |
18 | Message Number | BUP_RELATIONS - 045 | Internal error when reading partner data via the segment CENTRAL_DATA | |
19 | Message Number | BUP_RELATIONS - 006 | Time period has errors; there are gaps | |
20 | Message Number | BUP_RELATIONS - 011 | Error when retrieving relationship messages | |
21 | Message Number | BUP_RELATIONS - 012 | Error when retrieving messages; initial source ID | |
22 | Message Number | BUP_RELATIONS - 019 | Initial relationship category is not allowed | |
23 | Message Number | BUP_RELATIONS - 019 | Initial relationship category is not allowed | |
24 | Message Number | BUP_RELATIONS - 019 | Initial relationship category is not allowed | |
25 | Message Number | BUP_RELATIONS - 019 | Initial relationship category is not allowed | |
26 | Message Number | BUP_RELATIONS - 023 | From-date &1 is not valid | |
27 | Message Number | BUP_RELATIONS - 024 | To-date &1 is not valid | |
28 | Message Number | BUP_RELATIONS - 025 | Specify both business partners | |
29 | Message Number | BUP_RELATIONS - 027 | Invalid value &1 as indicator for direction of a relationship | |
30 | Message Number | BUP_RELATIONS - 028 | Combination relship direction &1 and relship category &2 not permitted | |
31 | Message Number | BUP_RELATIONS - 044 | Business partner cat. is not designated for this relationship cat. (TBZ9) | |
32 | Message Number | BUP_RELATIONS - 019 | Initial relationship category is not allowed | |
33 | Message Number | R1 - 776 | & cannot be created between identical business partners | |
34 | Message Number | R1 - 780 | &1 has more validity intervals than were designated &2 &3 &4 | |
35 | Message Number | R1 - 810 | Spouses are the same sex | |
36 | Message Number | R1 - 811 | Spouse &1 is already married | |
37 | Message Number | R1 - 826 | Business partner &2 is already contact person for business partner &1 | |
38 | Message Number | R1 - 827 | Business partner &2 is already employee of business partner &1 | |
39 | Message Number | R1 - 829 | Business partner &1 is not an employee | |
40 | Message Number | R1 - 164 | Relationship category & does not exist | |
41 | Message Number | R1 - 832 | Relationship type & does not exist | |
42 | Message Number | R1 - 834 | Role definition type & does not exist | |
43 | Message Number | R1 - 837 | Role definition type &1 is not defined for role definition category &2 | |
44 | Message Number | R1 - 849 | Business partner &1 is not &2 or &3 | |
45 | Message Number | R1 - 247 | Business partner & is not a group | |
46 | Message Number | R1 - 246 | Business partner & is not an organization | |
47 | Message Number | R1 - 245 | Business partner & is not a person | |
48 | Message Number | R1 - 201 | Business partner &1 does not exist | |
49 | Message Number | R1 - 201 | Business partner &1 does not exist | |
50 | Message Number | R1 - 164 | Relationship category & does not exist | |
51 | Message Number | R1 - 164 | Relationship category & does not exist | |
52 | Message Number | R1 - 164 | Relationship category & does not exist | |
53 | Message Number | R1 - 164 | Relationship category & does not exist | |
54 | Message Number | R1 - 137 | 'Valid-From' date may not be greater than 'Valid-To' date | |
55 | Message Number | R1 - 137 | 'Valid-From' date may not be greater than 'Valid-To' date | |
56 | Message Number | R11 - 123 | Specify at least one number for the business partner |