This paper covers a number of issues related to SuperStream message packaging and relationship with error handling. The purpose of this paper is to clarify areas of ambiguity or design Grant issues that will allow all parties to proceed and thereby reduce 28/03/13 Doherty interoperability issues when integration testing commences. (Qvalent) Update see note 18/04/13 - GUIDANCE ON AS4 ‘ebMS Message Structure’ NOW AVAILABLE Recommendation The Technical Architecture sub-group endorses the following decision and guidance Decision Endorse principles outlined below link the Event XML to a payload part by: Make location variables (Location.Instance.Identifier, Location.Path.Text) optional to enable business errors will be reported using the Parameters variables Principles In relation to reporting business errors: A single Event XML aligns message as intended (identification of the error utilises the part ID and format 08/03/13 Philip Hind should be agreed by industry we will surface examples – in the meeting) or A single Event XML aligns with a single transactions within the XBRL payload (progressive) Change impact Consequential action for the ATO would include: Publish and advisory change note Make the changes to schedule 6 Code Management’ to make location variables optional Provide additional guidance on error handling in the inter-op guide (example plus principles) The TA group considers that the small number of changes to the legislative instrument (schedule 6) is justified and can be managed within the rollover implementation lead time. A draft recommendation paper on Error Handling’ ‘Message 22/03/13 Ty Winmill has been written for review by Technical Architecture Group members.
28/03/13 Grant Doherty (Qvalent) This paper covers a number of issues related to SuperStream message packaging and relationship with error handling. The purpose of this paper is to clarify areas of ambiguity or design issues that will allow all parties to proceed and thereby reduce interoperability issues when integration testing commences. Update see note 18/04/13 - GUIDANCE ON ‘ebMS AS4 Message Structure’ NOW AVAILABLE 08/03/13 Philip Hind Recommendation The Technical Architecture sub-group endorses the following decision and guidance Decision Endorse principles outlined below link the Event XML to a payload part by: Make location variables (Location.Instance.Identifier, Location.Path.Text) optional to enable business errors will be reported using the Parameters variables Principles In relation to reporting business errors: A single Event XML aligns message as intended (identification of the error utilises the part ID and format should be agreed by industry – we will surface examples in the meeting) or A single Event XML aligns with a single transactions within the XBRL payload (progressive) Change impact Consequential action for the ATO would include: Publish and advisory change note Make the changes to schedule 6 Code Management’ to make location variables optional Provide additional guidance on error handling in the inter-op guide (example plus principles) The TA group considers that the small number of changes to the legislative instrument (schedule 6) is justified and can be managed within the rollover implementation lead time. 22/03/13 Ty Winmill A draft recommendation paper on ‘Message Error Handling’ has been written for review by Technical Architecture members. Group
Technical_architecture_sub-group_discussion.docx