Skip to main content

Celonis Product Documentation

Data Transformations Overview

The following section will detail some of the reasoning behind different transformations in the AR connector and what should be considered when implementing. The transformations should be run in the order of the prefix and in the order that follows. Please refer to the Data Pool Overview for more details on each job.

Following are the transformations in jobs C1 - AR Credit Application Full Load Job and C2 - AR Credit Application Delta Job.

  1. Create Table - External Rating (Credit): Creates an External Rating table and store the rating data. We have to write the transformation to insert the data into this table if the source system is giving us. This data will be used to calculate the credit score of a customer.

  2. Create Table - Account Credit Management (Credit): Create a table called ACCOUNT_CREDIT_MANAGEMENT, where we store customers' credit details.

  3. Insert Records - Account Credit Management (Credit): Insert credit data from the SAP KNKK table into the ACCOUNT_CREDIT_MANAGEMENT table.

  4. Create Table - Orders (Credit): Create a table called ORDERS to store open orders in the SAP source system.

  5. Insert Records - Orders (Credit): Insert Open Orders data from the SAP S066 table into the ORDERS table.

  6. Create Table - Billing Credit (Credit): Create a table called BILLING_CREDIT to store Open deliveries/billing documents in the SAP source system.

  7. Insert Records - Billing Credit (Credit): Insert Open deliveries/billing documents from the SAP S067 table into the BILLING_CREDIT table.

  8. Create Table - Credit Control Area (Credit): Create a table called CREDIT_CONTROL_AREAS to store Credit control areas in the SAP source system.

  9. Insert Records - Credit Control Area (Credit): Insert Credit control areas from SAP T014 table into the CREDIT_CONTROL_AREAS table.

  10. Create Table - Sold To Account Detail (Credit): Create a table called SOLD_TO_ACCOUNT_DETAIL to store Billing Document: Header Data in the SAP source system.

  11. Insert Records - Sold To Account Detail (Credit): Insert Billing Document: Header Data from SAP VBRK table into SOLD_TO_ACCOUNT_DETAIL table.

  12. Create View - Credit Limit Change History (Credit): Create a view to store the history of credit limit change in the SAP source system. We will fetch the history from CDHDR/CDPOS table for column KLIMK of table KNKK.

  13. Create View - SHORT_TERM_INC (Credit): We are calculating short-term increments for the credit limit that is needed for each customer. We will get data in the following sequence:

    1. We will get the Open Orders created between the last credit limit change and the 6th of next month. E.g., If today is 15-Aug, we will consider Open orders between the last credit limit change and the 6th Sep.

    2. We will get receivables for each Account and group them by Credit Control Area for each due day based on the agreed Payment Term.

    3. Now we will get the difference between Open orders credit sales values (from a.) and Due Receivable (from b.), which will be a Short Term Increment for Credit Limit that system would suggest.

  14. Create View - T014 (Credit): Create a view to store Credit control area data from SAP T014 table.

  15. Create Table - CREDIT_ACTIVITY (Credit): Creating a table to store credit activity from SAP Source System.

  16. Add Credit Activity - Create Invoice (Credit): Captures Invoice creation activity based on the TRANSACTION.INVOICE_DATE field.

  17. Add Credit Activity - Change Payment Terms (full): Captures the following activities at invoice level from this transformation:

    1. Change Payment Method

    2. Change Payment Term

    3. Change Baseline Date

    4. Change Item Text

    5. Cash Discount Percentage 1

    6. Cash Discount Percentage 2

    7. Cash discount days 1

    8. Cash discount days 2

    9. Cash discount days 3

    10. Change Dunning Level

  18. Add Credit Activity - Cash Discount Due Date Passed (full): Captures Invoice Activity where the Cash Discount Due Date has passed.

  19. Add Credit Activity - Due Date Passed (full): Captures Invoice Due Date past activity based on the TRANSACTION.DUE_DATE field.

  20. Add Credit Activity - Dunning Blocks (full): Captures activity at the Invoice level for the following events:

    1. Set Dunning Block

    2. Change Dunning Block

    3. Remove Dunning Block

  21. Add Credit Activity - Overdue Notices (full): Captures the following activities of a Sent Overdue Notice for all invoices.

    1. Send first Overdue Notice

    2. Send second Overdue Notice

    3. Send third Overdue Notice

    4. Send fourth Overdue Notice

    5. Send fifth Overdue Notice

    6. Send sixth Overdue Notice

    7. Send seventh Overdue Notice

    8. Send eighth Overdue Notice

    9. Send ninth Overdue Notice

  22. Add Credit Activity - Cancel Invoice (full): Captures Invoice cancel activity.

  23. Add Credit Activity - Clear Invoice (full): Captures activities related to when an invoice was cleared.