Transmission of price sheet A of MSB from MSB to NB and LF — NB view
The MSB transmits its electronic price sheet A to the NB or LF if the NB or LF does not have the electronic price sheet A or if at least one price component of price sheet A has changed.
Process flow from the perspective of the NB
Process steps
Price sheet A of the MSB
NB MSBCheck identifiers
- 27002 — Price sheets for MSB services · AS4
Flow
Message from MSB · AS4
Write endpoint
- Transaction created — Create process data
POST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created — Create process data
2 Price sheet A of the MSB
MSB LF
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 27002 — Price sheets for MSB services · AS4
Process information
Wording of the consolidated version, profile ch. 3.4.1, p. 93.
Preconditions
The EDIFACT communication between MSB and NB or LF is established, and the NB or LF does not have the current or updated price sheet A of the MSB.
Results
- Towards NB the following applies: the billing via the use case „Billing of services of price sheet A of MSB“ can be carried out towards NB, provided that NB has, via the
- Use case “Order placement of a configuration from NB or LF to MSB” has ordered a chargeable configuration and the order placement was confirmed by MSB or
- Use case “Control command from NB or LF to MSB” has instructed a chargeable control command and the instruction was confirmed by MSB. Note: if price sheet A of MSB states criteria for the instructed control command specifying when the control command is chargeable, these criteria must also be met.
- Towards LF the following applies: the billing via the use case „Billing of services of price sheet A of MSB“ can be carried out towards LF, provided that LF has, via the
- Use case “Order placement of a configuration from NB or LF to MSB” has ordered a chargeable configuration and the order placement was confirmed by MSB or
- Use case “Control command from NB or LF to MSB” has ordered a chargeable control command and the order placement was confirmed by MSB. Note: if price sheet A of MSB states criteria for the ordered control command specifying when the control command is chargeable, these criteria must also be met.
- Towards NB the following applies: the billing via the use case „Billing of services of price sheet A of MSB“ can be carried out towards NB, provided that NB has, via the
Error case
Result in the error case
In the error cases, price sheet A of the MSB is transmitted again.
Error cases
- Price sheet contains an error
- Price sheet was not transmitted in the current version
- Price sheet was not transmitted in full
- Price sheet does not begin at 00:00 of a calendar day.
First message
MSB sends “Price sheet A of the MSB” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The NB and LF have price sheet A of the MSB.
Other views of the process
The same process through the eyes of the other parties involved: the same steps, each read from their point of view.
Notes on this page
The steps are the possible messages of this process, not a sequence — the source lists neither conditions nor alternatives. The small box on the step names the own view on the left: with ← it receives, with → it sends. Collapsed steps run between other market partners.
The connector table lists no write call for these steps. Derived from the process flow: the process begins for the own role with their message, so the transaction is created.
Applies to: 1