Digital Sales Report Message Suite: Part 1 - Architecture
Hide navigation
Digital Sales Report Message Suite: Part 1 - Architecture
1 Introduction
2 Organisation of the document
3 Normative References
4 Terms and abbreviations
4.1 Terms and definitions
4.2 Abbreviations
5 Choreography
6 Structure of Sales/Usage Reports
6.1 Introduction
6.2 Scope of Sales/Usage Reports
6.3 Single-file Sales/Usage Reports
6.4 Multi-file Sales/Usage Reports
6.6 Identification and linking of Blocks
6.6.1 Introduction
6.6.2 BlockIDs
6.6.3 Linking sales and/or usage Records to release and resource Records
6.6.4 Linking Blocks to summary Records
6.7 Identification and linking Single Record Block Variant Records
6.5 Multi-file Sales/Usage Reports relating to the same transaction
7 Technical details
7.1 Baseline format
7.2 Character coding
7.3 Delimiters
7.4 Primitive data types
7.5 Empty Records
7.6 Empty Cells
7.7 Records to be ignored
7.8 Mandatory cells where no data is available
7.9 Deprecated Cells
7.10 Unknown Records
7.11 Communicating decimals and integers
7.12 Maximum Cell size
7.13 Maximum file size
7.14 Allowed-value sets
7.15 User defined values
7.16 Referencing Records
7.17 Version
7.18 Aiding human readability
7.19 Reporting no Sales and/or Usage
8 Transfer of Sales/Usage Reports
8.1 File naming convention
8.2 Sample File Names (informative)
8.3 Choreography for sending and acknowledging Sales/Usage Reports
8.4 Sample cloud-based server organisation (informative)
Annex A Release Notes (informative)
Show navigation
6.6 Identification and linking of Blocks
Children macro unable to render for apps.
Search
x