FKKDPB - Datenschutz: Pr�fungen zu gesperrten Gesch�ftspartner
The following messages are stored in message class FKKDPB: Datenschutz: Pr�fungen zu gesperrten Gesch�ftspartner.
It is part of development package FKK_PRIVACY in software component FI-CA. This development package consists of objects that can be grouped under "FI-CA: Data Privacy for Personal Data".
It is part of development package FKK_PRIVACY in software component FI-CA. This development package consists of objects that can be grouped under "FI-CA: Data Privacy for Personal Data".
Message Nr ▲ | Message Text |
---|---|
001 | Business partner &1 is blocked to protect personal data |
002 | Business partner &1 is blocked: correspondence not possible |
003 | Business partner &1 is blocked: no new security deposits possible |
004 | Business partner &1 is blocked: postings not possible |
005 | Business partner &1 is blocked: no changes possible |
006 | Guarantor &1 for security deposit &2 is blocked |
007 | Business partner &1 is blocked: not possible to create the mandate |
008 | Business partner &2 is blocked: it is not possible to change mandate &1 |
009 | Business partner &1 is blocked: entering new master data is not possible |
010 | Business partner &1 is blocked: interest calculation not possible |
011 | Business partner &2 is blocked: not possible to display mandate &1 |
012 | Business partner &1 is blocked: changing is not possible |
013 | Business partner &1 is blocked: display not possible |
014 | Business partner &1 for collective bill &2 is blocked |
015 | Business partner &1 for last recipient account &2 is blocked |
016 | Business partner &1 is blocked: displaying contacts is not possible |
017 | Bus. partner &1 blocked; deleting posting/clearing lock is not possible |
018 | To protect personal data, the system does not display all of the data |
019 | Business partner &1 is blocked; you cannot change the contacts |
020 | Business partner &1 for clearing account &2 is blocked |
021 | Bus. partner &1 is blocked: displaying clarification case not possible |
100 | Incorrect call: different usage of update |
101 | Incorrect call of &1 |