Mapping the dunning process in master data application
Project duration: 7 months
Brief description
Mapping of the dunning process in the master data application. The dunning run is triggered as usual in SAP. The data is then transferred via an IDOC interface to the master data system, where the data is validated and used for generating documents. Individual documents and collective documents (advice notes) can be printed or sent to the recipient by e-mail.
Supplement
The customer's master data application is based on a three-layer, service-oriented architecture (.Net-based thin client, application server, MS SQL 2008). Communication with SAP takes place with the help of BizTalk, which receives the information per IDOC, converts it to an in-house XML schema, and forwards it to the system. Development is performed in C# based on the .Net 3.5 framework. Moreover, the Microsoft Reporting Services are used to create the documents.
Subject description
For all outstanding receivables, the customer has agreed a period of payment that must be adhered to. If it is not adhered to, an internal 3-step dunning procedure is initiated, for which only the 1st and last (2nd) steps are mapped here. The third step is an internal step which is outsourced if necessary. Up to now, reminders are generated from SAP and then sent as a paper document. The documents should preferably be sent by e-mail rather than printed. The dunning process is the starting point for this. The data is generated manually by triggering the dunning process in SAP and then forwarded automatically via an interface to the master data system, where it is processed fully automatically. The data is validated against the invoice and discount requirements which were also created in this system. Then the reminder documents (individual documents and collective documents) are created, and sent by e-mail directly to the recipient stored in the system.