Digital Sales Report Message Suite: Part 1 - Architecture
Hide navigation
Digital Sales Report Message Suite: Part 1 - Architecture
1 Introduction
2 Scope
2.1 Introduction
2.2 Organisation of the Document
2.3 Release Notes (informative)
3 Normative References
4 Terms and Abbreviations
4.1 Terms and Definitions
4.2 Abbreviations
5 Choreography
5.1 Message Choreography
5.2 Multiple Linked Sales Report Messages
6 Structure
6.1 Introduction
6.2 Single-File Sales Report Messages
6.3 Multi-file Sales Report Messages
6.4 Blocks for Reporting Usage, Revenue or Sales
6.4.1 Introduction
6.4.2 BlockIDs
6.4.3 Linking sales and/or usage data Records to Release and Resource Records
6.4.4 Linking Blocks to Summary Records
6.5 Scope of Sales/Usage Report Messages
6.6 Technical Details
6.6.1 Baseline Format
6.6.2 Character Coding
6.6.3 Delimiters
6.6.4 Communicating Delimiters
6.6.5 Primitive Data Types
6.6.6 Splitting Sales/Usage Report Messages
6.6.7 Empty Records
6.6.8 Empty Cells
6.6.9 Records to be Ignored
6.6.10 Unknown Records
6.6.11 Communicating Decimals and Integers
6.6.12 Maximum Cell Size
6.6.13 Maximum File Size
6.6.14 Allowed Values
6.6.15 Linking Records
6.6.16 Version
6.6.17 Aiding Human Readability
6.6.18 Reporting no Sales or Usages
7 Profiles
8 Transfer of Sales Report Messages
8.1 File Naming Convention
8.2 Sample File Names (informative)
8.3 Choreography for sending and acknowledging Sales/Usage Report Messages
8.4 Sample SFTP Server Organisation (informative)
Show navigation
5 Choreography
5.1 Message Choreography
5.2 Multiple Linked Sales Report Messages
Search
x