23.07.2014 Views

EDI format specifications Version 2.0, Revision 4 - APRA

EDI format specifications Version 2.0, Revision 4 - APRA

EDI format specifications Version 2.0, Revision 4 - APRA

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Specifications: Common Royalty Distribution: <strong>EDI</strong> <strong>format</strong> <strong>specifications</strong> <strong>Version</strong> <strong>2.0</strong>, <strong>Revision</strong> 4<br />

4. Royalty Grand Total Transaction (RGT). This is an optional single-record<br />

transaction (which may later be classified mandatory) that reports accumulations<br />

of the royalty amounts contained within the file. This record, if present, must be<br />

within its own GRH/GRT pair and should be the last transaction group in the file,<br />

immediately before the TRL Trailer record.<br />

5. CRD Acknowledgement Transaction (ACK). This transaction is an optional<br />

acknowledgement that may be sent by the recipient (back) to the submitter, to<br />

fulfil either or both of the following purposes:<br />

• Indicate the success or failure of validation of the reported transactions and<br />

in<strong>format</strong>ion records;<br />

• Notify the submitter of the International Standard Work Code (ISWC)<br />

numbers assigned to the works by the recipient. This will allow the<br />

submitter to record the ISWC identifiers and use them to identify works in<br />

subsequent CRD reports to the recipient.<br />

2.2 - File Level Validations<br />

The following validations are relevant to the CRD file.<br />

1. The File (HDR, TLR) and Group (GRH, GRT) header and trailer records must<br />

conform to the CIS <strong>EDI</strong> standards (see SR06-2010-R5 “CIS Guidelines of<br />

Electronic Data Interchange, <strong>Version</strong> <strong>2.0</strong>”.)<br />

2. A CRD file containing acknowledgement records must not contain any other<br />

types of transactions.<br />

3. Metadata may not follow exploitation. That is, the metadata transactions<br />

(“Society Distribution Notification Transaction” and “Musical Work Notification<br />

Transaction”) must precede exploitation (“Musical Work Exploitation Notification<br />

Transaction”) transactions.<br />

2.3 - A note about society identifiers<br />

The CRD <strong>format</strong> provides ample space in which to report society identifiers allocated to<br />

musical works, audio-visual works, recordings, etc.<br />

All society identifier columns in CRD are alpha-numeric and as such, values should be<br />

supplied left-aligned in the columns, with trailing spaces. This is very important to those<br />

receiving societies that record other societies’ identifiers for reference purposes.<br />

Your identifiers should appear in CRD exactly as they did in the “E”, “F” and “M” file <strong>format</strong>s.<br />

CRD09-1005R4 10/80

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!