File Structure. The population of Data Flow files in different use cases is provided in the Online RGMA Data Flow Catalogue as different variations. • Files have been developed with consistent sets of data. This allows RGMA Data Flows to be made up of Data Groups so that changes can be limited to specific Data Groups, rather than being separately applied to each of the RGMA Data Flows. • The Data Groups are the records which are included in the RGMA Data Flow formats. The diagram below illustrates the file structure which consists of: o A header record o Transaction records (followed by a number of associated detail records) o A trailer record. Record Identifer Transaction type Record Identifer Header Transaction TRANSACTION Transaction Trailer Record RECORD Record Data Item Value Data Item Value Data Item Value Separator • Complete Data Groups are used in the definition of the records. The Data Groups include Data Items which, though not required as part of the minimum data, could be used to satisfy commercial arrangements, and to provide extra Data Items which can be populated for exception processing and updates. The use of standard Data Groups means any change can be applied once to the formats, and only the business rules need to be adjusted in the different uses thus minimising the impact of change. The overhead of RGMA Data Flows allowing for data which some organisations will not use, is minimised by having variable length fields and not using field separators which are in the standard set of characters. • Files have a core which can be used by all Market Participants. This allows Suppliers to change their MAM with minimal changes to their records and means of communication, while allowing for commercial additions to the core data resulting in Market Participants being able to provide tailored functionality. • The file will be as one stream of data with the defined codes providing delimiters between Data Items and Data Groups. Any spaces between data and delimiters will be significant. • There is no identified requirement for record sequence numbers, but record sequencing within a transaction is significant.
Appears in 2 contracts
Sources: Supply Point Administration Agreement, Supply Point Administration Agreement