Show TOC

Process documentationDIMa Data Alignment Between ERP and the OR Data Collector

 

The outgoing royalties data collector receives information on billed values and quantities from IPM-relevant product sales in the following transactions:

  1. Sales and Distribution (SD)

  2. Payment transactions in Financial Accounting (FI)

  3. Revenue recognition runs in the Accrual Engine.

You can use the Data Integrity Manager (DIMa) to check whether data from the processes referred to above in ERP has been transferred to the OR data collector correctly. If data is not consistent in both systems, you can start an automatic download from the SAP backend to the data collector.

Two types of check are supported: Header alignment and Detailed alignment (see process description below).

Constraints

Payment transactions that were entered in FI and whose clearing was subsequently reversed, are set to zero in the data collector. These documents are not selected in the SAP backend, and are not therefore available for alignment.

Prerequisites

Alignment only works if the CRM System, in which the DIMa and the OR data collector run, is identical.

Process

The Data Integrity Manager (DIMa) is based on middleware adapter objects, and selects data from the SAP backend using an extractor. Data selected in this manner is made available in CRM for alignment purposes.

To start the data alignment, use the transaction SDIMA (Program CRW_DIMA_RESULTS). A separate DIMA object is available for each transaction:

  • IPM-BEA-PRDSLS for product sales in SD

  • IPM-BEA-FIPAYM for payments in FI

  • IPM-BEA-ACECNF for revenue recognition

Header Alignment

To restrict the data selection, you can transfer a filter value to the DIMa object. Possible filter values are:

  • For product sales: Billing document number, billing type and billing creation date.

  • For incoming payments: Company code, document number, fiscal year, document type, creation date and billing document number. The document information refers to the FI document associated with the billing document, and not to the payment document transferred.

  • For the revenue recognition run: Transaction type, transaction number, item number and key date for the accrual run.

The result of the header alignment shows whether the SAP backend contains SD billing documents or values for whch revenue recognition has been performed.

Detailed Alignment

In addition to the data compared in the header alignment, the product, rights attributes and assigned data values (table CRMD_IPM_BVAL) including the quantity and value are aligned here. A detailed alignment can only be started for documents that exist in both systems. Data records are only defined as being identical if these values are identical.

The result of the detailed alignment displays which items are identical in both systems and which are different.

If there are differences between the two systems, you can start an alignment directly by transferring the ERP data to the CRM System again.