Multi-Event-Log Connectors for SAP ECC P2P-AP and O2C-AR
This documentation covers content, reasoning, and general concepts behind 2 process connectors in the Marketplace:
Multi-Event-Log Order-to-Cash & Accounts-Receivable (SAP ECC)
Multi-Event-Log Purchase-to-Pay & Accounts-Payable (SAP ECC)
Context
The 2 connectors are unifying the content of our four most popular process connectors
SAP ECC - Order-to-Cash (O2C)
SAP ECC - Accounts-Receivable (AR)
SAP ECC - Purchase-to-Pay (P2P)
SAP ECC - Accounts-Payable (AR)
The reasoning behind it is that O2C and AR as well as P2P and AP are closely interconnected processes and therefore often combined with each other. Combining them into one Data Model allows you to analyze the full end-to-end process. With the 2 ready-to-use connectors, we are simplifying the set-up and implementation effort.
Concepts
The benefits of the connectors can be tied to 3 key concepts which are applied throughout the templates.
Multi-Event-Log: The templates make full use of our Multi-Event Log capabilities to provide end-to-end process insights. Every event has been assigned to an individual activity table and case table based on where the event logically takes place. Activities were even differentiated on header & item level (e.g. Event-log for Purchase Order Headers and Event-log for Purchase Order Items). The single activity tables are merged together at a data model level using the event log auto-merge functionality. This allows you to analyze the process either individually by looking at the single event logs or jointly by looking at the combined activity table.
P2P-AP
O2C-AR
# of Activities (events)
26
29
# of Activity Tables (event logs)
8
1
Object Modularization: The connector was modularized in a way that makes it easy to enable/disable certain parts based on your needs. An Object contains at least one Activity Table and has its dedicated Data Job that can be executed independently from the others. In addition, full support of the Replication Cockpit (Real-Time Extractions & Real-Time Transformations) is included. As Data Jobs can be enabled and disabled, tailoring the connectors to specific business use cases is now by far simplified.
The picture below gives an overview, of how the defined Objects are organized into separated Data Jobs.
Simplification of Transformations: By introducing Multi-Event-Log and the modularization approach, the transformations could be simplified significantly. Several joins and filters were removed from the transformations and moved into the Data Model.
Content
The following objects are included:
MEL Process | "Source" Process | Object |
|---|---|---|
P2P-AP | AP | Credit Memo (Payable) |
P2P-AP | AR | Invoice (Payable) |
P2P-AP | P2P | Purchasing Contract |
P2P-AP | P2P | Purchase Orders |
P2P-AP | P2P | Purchase Requisitions |
P2P-AP | P2P | Quality Inspection |
O2C-AR | AR | Credit Memo (Receivable) |
O2C-AR | AR | Invoice (Receivable) |
O2C-AR | O2C | Delivery |
O2C-AR | O2C | Billing |
O2C-AR | O2C | Quotation |
O2C-AR | O2C | Sales Order |
O2C-AR | O2C | Shipment |
Data Model P2P-AP
Data Model O2C-AR
