# 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 \nSystem diagram: Übermittlung Preisblatt A des MSB vom MSB an NB und LF — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1. Preisblatt A des MSB\n\nMSB\n\nAS4\n27002\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Übermittlung Preisblatt A des MSB vom MSB an NB und LF — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nMSB\n\n\nLF\n\n\n1. Preisblatt A des MSB\nAS4 · PI 27002\n\nCreate transaction\nCreate process data\n\n2. Preisblatt A des MSB\nAS4 · PI 27002\n"} titel="NB" /> ## Process steps ### Price sheet A of the MSB
**Check identifiers** - [27002](/en/schnittstellen/202604/pruefi/PRICAT/PI_27002) — Price sheets for MSB services · AS4
**Flow**
  1. Message from **MSB** · AS4
  2. **Write endpoint** - Transaction created — [Create process data](/en/api/202604/backend-schreiben-nb/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
### Price sheet A of the MSB This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [27002](/en/schnittstellen/202604/pruefi/PRICAT/PI_27002) — Price sheets for MSB services · AS4
## Process information Wording of the consolidated version, profile ch. 3.4.1, p. 93.
  1. ### 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.
  2. ### 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.
  3. ### 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.
  4. ### 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.
  5. ### 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. - [View LF](/en/prozessdoku/202604/LF/GPKE-Teil3-uebermittlung-preisblatt-a-des-msb-vom-msb-an-nb-und-lf) — LF - [View MSB](/en/prozessdoku/202604/MSB/GPKE-Teil3-uebermittlung-preisblatt-a-des-msb-vom-msb-an-nb-und-lf) — MSB *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](#schritt-1)