SAP Accounting Consulting

Symptom

The Health Check Data Flow Verifcation (DFV) is indicating deviations with message “DFV has detected differences in the data flow between BOs”.
In detail deviations between CRM sales or service orders’ parties or locations and the corresponding SCM customer requirements’ parties or locations are reported.
The following deviations are possible:
Different ship-to locations: the ship-to location – either the referred party identifier or address host UUID – in CRM is different than in SCM.
Example:Ship-to Location SCM: Reference to party ID MC9785Ship-to Location CRM: Reference to party ID MC6049
In the DFV for this issue the text “Locations with role code.. .differ” may appear.
Missing party type code: for a party, for example the seller, the party type code is missing in CRM whereas it is available in SCM
In the DFV for this issue the text “Parties with role code…differ” may appear.
Missing leading zeros for numeric party identifiers: for a party with a numeric party ID, for example the vendor, the amount of leading zeros in CRM and SCM is different.
Example:Party ID SCM: 000000000000000000000000000000000000000000000000000000009000Party ID CRM: 00000000000000009000

In the DFV for this issue the text “Parties with role code… differ” may appear.

The deviations do not necessarily cause business process inconsistencies; however DFV is recognizing and indicating these deviations.

Other terms

Party Processing; DFV; Health Check

Reason and Prerequisites

DFV is indicating issues regarding parties and locations, especially for the ship-to location. The ship-to location shall always have a reference to the product recipient party. However, in erroneous documents the item’s ship-to location is different than the product recipient party.
In other use cases some technical fields, which are not visible in the UI, like the party type code for example, have not been filled correctly.

Solution

Apply the related hotfix for FP2.0 SP0 and SP1.
Afterwards, in order to correct errors listed above, please start in the backend system with transaction SE38 the report AP_CRM_TOOL_PAPR_LOC_REPAIR with default settings.
Only change the following parameters if necessary:
Document Selection: Business ObjectDefault value is 114 (Sales Order); enter another CRM BO, for example 117 (Service Order), only if the DFV result is listing errors for another BODocument Selection: Select options “Select via DFV ID” or “Select via BTD ID”In case you have a DFV result ID listing the above errors use the option “Select via DFV ID” and enter the result ID in field “Data Flow Verfication ID”In case you don’t have a DFV result ID and/or you want to check a given list of Business Transaction Document IDs, mark the option “Select via BTD ID” and enter the document IDs in the field “Document ID”.General Options: Test RunWhen you start the report the first time leave this flag marked with ‘X’. Then the report won’t do any database updates.
In case in the subsequent log no erroneous records are listed, the report won’t solve the issue that you are investigating.If errors are listed, start the report a second time with initial flag “Test Run” in order correct the database.

Procedure to correct data:
Execute the report in test mode first. This can take a few minutes depending on the data volume.
A short log of the result is shown when the report is finished.
The log contains roughly the following sections:
Number of selected party recordsRepair party numeric IDNumber of selected location recordsRepair party location typeRepair location reference to product recipient partyReconciliation message CRM->SCMDetailed Log with Business Transaction Document IDs

In case the report detects errors, the number of found records is listed under “Number of erroneous records:” in the respective sections.
In case at least 1 error is found start the report in “database mode” by unsetting option “Test Run”.
The report corrects the database in CRM Party Processing.
Afterwards restart the DFV result:
Trigger repeat check for the detected differencesIf differences remain and the customer agrees, trigger the reconciliation message for the detected differences. (trigger reconciliation from Application Management Workcenter)Trigger repeat check for the detected differences

The listed party/location errors should disappear. Otherwise there must be another error reason; then forward the incident to get support from development.