B2B schema transition timing
For details about Implementation and Release Dates, see the relevant technical specification.

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. aseXML schema Specification to describe the structure of an aseXML message. transitions can only happen after the Implementation Date when the new schema version is effective and available for selection in the drop-down list.
B2B transforms only occur between the current and superseded versions. For example, if the current B2B schema is r41 and you are on the superseded B2B schema r38 then transforms are available. If you are on a non-supported version of the B2B schema then no transforms are available and the transaction is delivered in the version it was sent.
Receiving |
Status on |
To do |
Transaction |
FTP |
API |
Transforms |
---|---|---|---|---|---|---|
r_any Current Superseded |
Ready |
|
All |
Effective immediately |
Effective immediately |
Available |
Current New superseded |
Not Ready |
|
All |
No change to receiving files |
No change to receiving files |
Available |
r_any |
Not Ready |
Before the Implementation Date:
|
All |
Effective immediately |
Effective immediately |
Available |
Old superseded |
Not Ready |
B2B supports all schema versions. Sending participants using an old superseded or lower version must have an agreement in place with the receiving participant so they do not reject the file |
All |
Effective immediately |
Effective immediately |
Unavailable |