About the B2B schema
This is the Business As defined in the NERL.-to-Business schema supporting sending and receiving of B2B Business-to-Business. Generic term used to refer to defined business-to-business interactions between participants; excludes interactions between a participant and market systems such as MSATS. transactions, for example:
- Customer and Site Details The elements of data identified in any of the notification transactions detailed in the B2B Procedures: Customer and Site Details Notification Process. See B2B Procedures: Customer and Site Details Notification Process. (CUST)
- Meter Data Process The overall process for the provision of metering data to a participant by an MDP. Requests by the appropriate participant for provision of missing metering data from an MDP, or the querying of the validity of any metering data supplied by an MDP. Has 3 component processes: Meter Data Notification Process, Provide Meter Data Process, and Meter Data Verification Process, see B2B Procedures: Meter Data Process. (MTRD)
- One Way Notification A B2B Procedure defining the standard processes and transaction data requirements for one way messaging transactions between market participants. It provides a process where participants can send messages to other participants for multiple NMIs in a single transaction. (OWNP)
- Site The physical location of the connection point, see B2B Procedures: Customer and Site Details and Service Orders Process. Access (SITE)
- Service Order A request to perform specified work, see B2B Procedures: Service Order Process. (SORD)
For details about B2B transactions, B2B Procedures.
The B2B e-Hub An electronic information exchange platform facilitating B2B Communications. supports all aseXML schema Specification to describe the structure of an aseXML message. versions. For example, you can send any B2B file in any published schema version, not just current or superseded. If the recipient cannot process a particular schema version, the recipient must respond to the file with a negative acknowledgement (a rejection).
If sending participants use a B2B schema lower than current or superseded, they must have an agreement in place with the receiving participant so the file is not rejected.
B2B schema change process
