DDEX Standard

Skip to end of metadata
Go to start of metadata

6.4.1 Introduction

 The main portion of a Sales Report Messages created in accordance with this standard is organised in Blocks. Each Block contains all the information about the “item of trade” that allows the Message Recipient to identify the content used, followed by the usage, revenue or sales information.

All Records of a Block are contiguously provided in the Sales Report Message created in accordance with this standard; it is not permitted to "interlace" Blocks.

6.4.2 BlockIDs

All Blocks contain a BlockID Cell. The first Block in the Sales Report Messages shall have a BlockID containing the value 1, the next Block shall  have a BlockID containing the value 2, etc. 

This mechanism allows all Records in a Block to be associated with one another. If, for instance, a Block contains a Head Release, a number or Resources and a few Sub-Releases, the BlockID can be used to link the Sub-Releases to the Head Release. Together with the ReleaseRecord Cell, the BlockID also allows to unambiguously link a Sub-Release to its containing Resources.

6.4.4 Linking Sales/Usage Records to Release and Resource Records

In cases where a Block can contain more than one Release or Resource that might have been used or transacted, the Sales/Usage Record needs to indicate the Release (or Resource) it provides Usages, Revenues or Sales for. This is effected by providing the content of the ReleaseReference Cell (or ResourceReference Cell) of the used Release (or Resource) in the TransactedRelease Cell (or TransactedResource Cell) of a Sales/Usage Record.

 6.4.5 Linking Blocks to Summary Records

All Blocks contain Records that report Usages, Revenues or Sales.[1] It is essential for a Message Recipient to be able determine to which Summary Record such Usage/Revenue/Sales Records contribute. To allow this, all Summary Records contain a SummaryRecordId Cell that Usage/Revenue/Sales Records can point to. Figure 4 shows an excerpt from a Sales Report Message in which two different types of exploitation (see Clause 6.5 for details) are being reported with respect to two different Releases (reported in Records of Type RE01).

Figure 4 – Linking Blocks to Summary Records (Example)

[1] In some profiles it may be valid to send Blocks without any such Records.


  • No labels