• Claim Detail Message Suite: Part 1 - Architecture
Hide navigation
  • Claim Detail Message Suite: Part 1 - Architecture
    • 1 Introduction
    • 2 Scope
      • 2.1 Introduction
      • 2.2 Organisation of the Document
    • 3 Normative References
    • 4 Terms and Abbreviations
      • 4.1 Terms and Definitions
      • 4.2 Abbreviations
    • 5 Choreography
      • 5.1 Post-Usage Choreography
      • 5.2 Relationship between Sales/Usage Report and Claim Detail Messages
      • 5.3 Retractions and Replacements
      • 5.4 Corrections
      • 5.5 Pre-Usage Choreography
    • 6 Structure
      • 6.1 Baseline Format
      • 6.2 Character Coding
      • 6.3 Delimiters
      • 6.4 Communicating Delimiters
      • 6.5 Primitive Data Types
      • 6.6 Empty Records
      • 6.7 Empty Cells
      • 6.8 Records to be Ignored
      • 6.9 Unknown Records
      • 6.10 Communicating Decimals and Integers
      • 6.11 Maximum Cell Size
      • 6.12 Allowed Values
      • 6.13 Linking Records
      • 6.14 Version
      • 6.15 Transfer of Claim Detail Messages and Claim Detail Discrepancy Notifications
      • 6.16 File Name Convention
      • 6.17 Aiding Human Readability
    • 7 Profiles
Show navigation

6.7 Empty Cells

It is possible to communicate empty Cells. In that case, two tab characters shall follow each other with no characters in-between.

The semantics of an empty cell is determined by the commercial relationship between a Licensor and a Licensee, unless specifically defined in this standard.

Search

    Powered by Instant Websites for Confluence