BPOB - Parnter-Objektbeziehung
The following messages are stored in message class BPOB: Parnter-Objektbeziehung.
It is part of development package FTBPOB in software component FS-BP. This development package consists of objects that can be grouped under "SAP BP FS: Partner-Object Relationship".
It is part of development package FTBPOB in software component FS-BP. This development package consists of objects that can be grouped under "SAP BP FS: Partner-Object Relationship".
Message Nr ▲ | Message Text |
---|---|
001 | No parameters have been set for the application &1 |
002 | No data found for object & & in local memory |
003 | Enter the assignment number |
004 | Function module for application &1 and event &2 is not in table TPR4 |
005 | Start of relationship & is after end of relationship & |
006 | Record not found (table &) |
007 | Partner &1 exists twice in role &2 and at time period &3 |
008 | Internal error: Assign. cat. &1; function module for event &2 is missing |
009 | No business partner was selected |
010 | No business partner role was selected |
011 | Business partner must exist in the business partner role category &1 |
012 | Cardinality of roles in role category &1 is inconsistent with Customizing |
013 | Assign the "person responsible" roles in contract processing |
014 | You can reset history mode with the pushbutton: date |
015 | Enter a role type |
016 | Role type is a required entry field for &1; default setting was applied |
017 | Role type is a required entry field for &1 |
018 | Role cannot be substituted; postings to the contract exist |
019 | Business partner &1 already exists in the FI customer role &2 |
020 | Business partner category &1 is unknown |
021 | Business partner role &1 is not intended for application category &2 |
022 | Application category &1 is not intended |
023 | No FI customer exists for the main borrower &1 |
024 | Enter a payment method for the alternative payer &1 |
025 | No assignment category has been set for the BDT application &1 |
027 | Role in role category &1 does not cover the validity area completely |