MDG_BS_SUPPL_CHECK - MDG: messages for check of supplier data
The following messages are stored in message class MDG_BS_SUPPL_CHECK: MDG: messages for check of supplier data.
It is part of development package MDG_BS_ECC_SUPPLIER_ACCESS in software component CA-MDG-APP-SUP. This development package consists of objects that can be grouped under "Access to Vendor Master Data for MDGS".
It is part of development package MDG_BS_ECC_SUPPLIER_ACCESS in software component CA-MDG-APP-SUP. This development package consists of objects that can be grouped under "Access to Vendor Master Data for MDGS".
Message Nr ▲ | Message Text |
|---|---|
| 010 | Enter a VAT registration number |
| 011 | Enter an appropriate tax type and tax number |
| 012 | Enter an appropriate tax type and tax number |
| 013 | Enter an appropriate tax type and tax number |
| 014 | Enter an appropriate tax type and tax number |
| 015 | Enter an appropriate tax type and tax number |
| 016 | Enter an appropriate tax type and tax number |
| 017 | Purchasing organization &1 already exists |
| 018 | Company code &1 already exists |
| 020 | Enter a relevant role for the creation of supplier master data |
| 021 | BP grouping &1 does not correspond with account group &2 |
| 022 | CVI Customizing does not allow to create a supplier for BP grouping &1 |
| 023 | Account group &1 is not usable for Vendor Like UI |
| 030 | Role &1 requires company code data |
| 031 | Role &1 requires company code data |
| 032 | Role &1 requires purchasing organization data |
| 033 | Role &1 requires purchasing organization data |
| 034 | Purchasing organization data are not allowed for role &1 |
| 040 | Inconsistent key mapping for supplier &1; update not possible |
| 041 | Key mapping for supplier &1 cannot be updated |
| 042 | Inconsistent key mapping for partner &1; update not possible |
| 050 | Enter ID for new CVI BP role category |
| 051 | Enter title for new CVI BP role category |
| 052 | BP role category already exists; enter a different ID |
| 053 | BP role categ. title already exists; enter a different title |
| 070 | Dunning area &1 already exists for company code &2 |
| 071 | Tax type &1 already exists for company code &2 |
| 072 | Tax category &1 already exists |
| 073 | No dunning data exists for the company code &1 |
| 080 | For POrg &1 alternative data with plant &2 and subrange &3 already exists |
| 090 | Subrange &1 already exists |
| 091 | Description in language &1 for subrange &2 already exists |
| 092 | Subrange &1 does not exist |
| 093 | Alternative purch. data with subrange &1 still exists in purch. org. &2 |
| 094 | Creation of alternative purch. data on subrange level is not permitted |
| 095 | Creation of alternative purch. data on plant level is not permitted |
| 096 | Initial plant level relevance not permitted, alt.purch.data entries exist |
| 097 | Initial VSR-level relevance not permitted; alt.purch.data entries exist |
| 100 | Supplier &1 is marked for deletion |
| 101 | Supplier &1 is marked for deletion in company code &2 |
| 102 | Supplier &1 is marked for deletion in purchase organization &2 |
| 104 | No relevant switch active in client &1 |
| 110 | Switch &1 is active in client &2 |
| 111 | Switch &1 is active in client &2; no relevant change request found |
| 112 | Switch &1 is active in client &2; no relevant process found |
| 200 | Document &1 &2 &3 &4 does not exist |
| 201 | Multiple documents not allowed for &1 &2 of type &3 |
| 300 | Activation of business function &1 is not permitted |