5.3.6 CDD1 – Record for data discrepancies

This is the Record used to communicate data about data discrepancies that a licensee has detected in a CDM Statement previously received from a licensor and is used in a CDM message created in accordance with theNotification of Data Discrepancies profile

If the data discrepancy in the CDM Statement being reported relates to a claim detail Record which has a direct impact on a summary Record, there is no requirement to also report the consequential data discrepancy on the summary Record.

Cell Name

Field Definition

Data Type

M/O/C?

Example

1

RecordType

The type of the Record which shall always contain CDD1.

Fixed string

M

CDD1

2

DataDiscrepancyId

The proprietary identifier of the data discrepancy, which is allocated by the licensee and which enables any communication about a CDM Statement to reference directly back to an individual claim detail Record.

The DataDiscrepancyId taken together with the MessageId in the CDMH.01 Record shall be globally and perpetually unique.

String

M

43DF

3

ClaimId

The proprietary identifier of the claim in a right share, which was allocated by the licensor, in a CDM Statement to which the CDM Notification of Data Discrepancies is a response.

The ClaimId taken together with the SenderPartyId and MessageId in the CDMH.01 Record of the CDM Statement shall be globally and perpetually unique.

A value in the ClaimId Cell is mandatory if the discrepancy pertains to a specific claim.

String

C

2345

4

SummaryRecordId

The identifier, which shall be specific to the CDM Notification of Data Discrepancy, of the summary Record for which this claim detail discrepancy Record provides details.

Each summary Record referenced through this SummaryRecordId provides values for the CommercialModel, UseType, Territory and ServiceDescription Cells to which the data discrepancies reported in this Record apply.

String

M

34

5

DiscrepancyType

A value describing the type of the data discrepancy.

AVS: Discrepancy Type

M

SalesDataIncorrect

6

Discrepancy RecordType

A value identifying the type of Record in which a data discrepancy has been detected.

For example, for a data discrepancy detected in a claim details with financial data Record the value in the DiscrepancyRecordType Cell should be either CD01.01 or CR01 as the case may be.

String

M

CD01

7

Discrepancy Description

A string describing the data discrepancy detected by the licensee.

This text, together with the value in the DiscrepancyType Cell, is intended to provide the licensor that is analysing the CDM Notification of Data Discrepancies, an explanation of the nature of the data discrepancy that the licensee has detected.

String

M

Number is inconsistent with sales report.

8

DiscrepancyCellName

The name of the Cell within the Record identified in the DiscrepancyRecordType Cell which identifies where the data discrepancy was detected.

For example, in the CR01 Record the data discrepancy could be located in the BlendedShareClaimedForMechAndPerf Cell which would then be the value in this DiscrepancyCellName Cell.

String

M

Usages

9

Discrepancy RecordId

The unique identifier of the Record in the CDM Statement in which a data discrepancy has been detected.

Depending on the nature of the identifier used to uniquely identify a Record, the type of identifier used in this Cell will vary as follows:

  • For CDMH.01 and SRFO Records the MessageId shall be used;

  • For the CS01 and CS02.01 Records the SummaryRecordId shall be used;

  • For the CR01 or CR02 Records the ClaimId shall be used; and

  • For the CX01 Record the AuxiliaryRecordId shall be used.

If it is not possible to provide a value in the DiscrepancyRecordId or if the identifier is not unique, this Cell shall be left empty.

String

C

4

10

Discrepancy
RecordLine

The cardinal number of the Record in which a data discrepancy has been detected.

When counting the Records in a CDM Statement to provide this data, the CDMH.01 and SRFO Records as well as empty Records as described in with Clause 7.5 of Part 1: Architecture of the CDM standard and Records to be ignored as described in Clause 7.7 of Part 1: Architecture of the CDM standard shall be included. 

Providing a value in the DiscrepancyRecordLine Cell is a “last resort” and should only be provided if no unique DiscrepancyRecordId can be provided.

Integer

C

2345

11

ActionTaken

A description of the action taken by the licensee with respect of the claim in a right share and/or associated amount due as a result of detection of the data discrepancy.

The values to be used in this Cell, and indeed whether the Cell should be used at all is determined by the bilateral agreement between the licensee and the licensor.

String

C

ClaimOrInvoiceAccepted

12

ValueFound

The value in the CDM Statement received by the licensee which the licensee considers to be a data discrepancy. 

If the relevant Cell in the CDM Statement identified in this Record did not contain any value, this Cell shall remain empty.

String

C

105

13

ValueExpected

The value in the CDM Statement received by the licensee that the licensee would have expected in the relevant Cell identified in this Record. 

A value in the ValueExpected Cell is mandatory if the licensee has knowledge of a value it expected in the discrepant Cell.

String

C

110

14

RoyaltyImpact InCurrencyOf Invoicing

The aggregate amounts of all the ClaimedAmount Cells in all claim detail Records and the ClaimedAmountDelta Cells in all claim detail Records in the CDM Statement sent by the licensor, that are affected by the data discrepancy in the currency of invoicing used in the CDM Statement. If the relevant CDM Statement did not contain values in the ClaimedAmount and/or ClaimedAmountDelta Cells in the relevant Records this Cell shall remain empty.

A value in the RoyaltyImpactInCurrencyOfInvoicing Cell shall not be provided if the impact is unquantifiable.

Decimal

C

123.43