Purpose The purpose of this document is to specify the data formats and the rules of data exchange between AEMO and STTM Market Participants in the context of the Short Term Trading Market (STTM). [...] Registered Facility The facility allocation required by Rule 420 meaning The the quantity of natural gas that is taken Service Allocation to be delivered to or withdrawn from the hub by the trading right holder on a gas day using the registered facility service to which the trading right relates. [...] If the file is found to be valid during the primary validation, the STTM market system will proceed to validate the data within the file and AEMO | 3 March 2025 Page 50 of 66 STTM Participant Build Pack provide a Transaction Acknowledgement back to the submitter indicating whether the file passed data validation or not. [...] If the file is found to be valid during the primary validation, the STTM system will proceed to validate the data within the file and provide a Transaction Acknowledgement back to the submitter indicating whether the file passed data validation or not. [...] 4511 Invalid MSV – the Submitter Type is ‘shipper from the hub’ and the counter-party is a ‘shipper from the hub’ and the quantity is negative AEMO | 3 March 2025 Page 58 of 66 STTM Participant Build Pack Error Error Description Code 4512 Invalid MSV – the Submitter Type is ‘shipper from the hub’ and the counter party is a ‘shipper to the hub’ 4513 Invalid MSV – the Submitter Type is ‘shipper to t.
Authors
- Pages
- 66
- Published in
- Australia
Table of Contents
- Approved for distribution and use by 1
- Disclaimer 2
- Purpose 2
- No substitute 2
- No warranty 2
- Limitation of liability 2
- Copyright 2
- Trademark Notices 2
- Distribution 2
- Documents made obsolete 2
- Further information 2
- Contents 3
- Tables 4
- Figures 4
- Current version release details 6
- 1. Introduction 7
- 1.1. Purpose 7
- 1.2. Audience 7
- 1.3. Scope 7
- 1.4. Related documents 7
- 1.5. Exclusions 7
- 1.6. Definitions acronyms and abbreviations 8
- 1.7. Overview and structure 8
- 2. Rules and procedures 10
- 2.1. Data provision 10
- 2.2. Inconsistencies 11
- 3. Interfaces 12
- 3.1. Overview 12
- 3.2. Option 1 Direct data entry using browser 13
- 3.3. Option 2 Data loading using CSV file to browser 14
- 3.4. Option 3 CSV file upload using FTP 16
- 3.5. Option 4 CSV file upload using HTTPS 18
- 3.6. Transaction processing using S - WEXIE 18
- 3.7. Overview of STTM Interfaces 19
- 3.8. Supported browsers 20
- 3.9. Transactions 20
- 3.10. Timing requirements 21
- 3.11. Cutoff time for inclusion in Schedule or Settlement 21
- 3.12. Authentication requirements 22
- 3.13. Default File Transfer and Acknowledgement Protocol 22
- 3.14. SWEXIE flow control management 23
- 3.15. Folder structure on FTP server 23
- 4. Transactions and acknowledgements 25
- 4.1. General requirements 25
- 4.2. BidOffer 34
- 4.3. Price Taker Bid 42
- 4.4. Facility Hub Capacity 43
- 4.5. Facility Allocation 44
- 4.6. Registered Facility Service Allocation 45
- 4.7. MOS Step Allocation 47
- 4.8. Market Schedule Variation Data 48
- 4.9. Data Confirmation 49
- 4.10. Deemed STTM Distribution System Allocation 50
- 4.11. Pipeline CTM Data 52
- 4.12. Message Acknowledgement 54
- 4.13. Transaction Acknowledgement 55
- 4.14. Transaction Summary Table 56
- 4.15. Error handling 56
- 4.16. Error codes 56
- Version release history 64
