Technical Specification Views
      Back to home
      1. Knowledge Base
      2. Reporting Services
      3. Technical Specification Views

      How do I navigate the various Airtable views?

      This article walks through how to understand the source of a TR field and the target of an RS (Reporting Services) KDM field

      Understanding the Technical Specification and Airtable Views

      For comprehensive access, please refer to the Airtable base (link) that includes all relevant views across jurisdictions. Below is an explanation of key views and field naming conventions to help you navigate the data effectively:

      Key Views and Field Naming Conventions

      1. Reporting Services - "Jurisdiction" Hub KDM "Message Type" Submittable:

      • This view is particularly helpful for understanding the fields required for submission for each jurisdiction and message type.
      • It includes all fields necessary for a particular message type submission.
      • Example: link

      A note on Field naming:

      KOR Field names may differ from regulatory terms to enable streamlined submission processes across jurisdictions & reporting workflows.

      For example, Counterparty Level Fields are labeled as "My Entity" and "Other Entity" rather than Counterparty 1 and 2. This naming ensures the message can be transformed appropriately for both self-reporting and delegated reporting.

      This table (link) defines the "Hub to Reg KDM" labels - meaning what the level of translation between a KOR field and regulatory field is. 

      2. Transformation from Hub to Regulatory Message Fields:

      To understand how Hub message fields map to regulatory message fields, refer to:
      • Reporting Services - "Jurisdiction" Hub KDM "Message Type": Contains all fields for submission, including those auto-set by KOR.
      • Reporting Services - "Jurisdiction" Reg KDM "Message Type": Lists all fields generated on the regulatory message for a specific jurisdiction and message type.

      Regulatory Output Field Mapping:

      • Output Submitted to KOR TR:
        • Regulatory message field names are mapped one-to-one with output message field names.
      • Output Submitted to Another Repository:
        • A separate column displays the repository-specific field names for easy reference.

      This structure ensures clarity in understanding and managing your reporting requirements. Please reach out if further clarification is needed.

      Jurisdiction specific pages with links to relevant Airtable views: