The AS4-System can be used to deliver Mako-Edifact messages and to deliver Schedule Messages via AS4. Transporting Schedule Messages needs additional configuration. The process has additional requirements.
This chapter will handle the following topics:
- Requirements
- Comparison with Mako-Edifact
- Preparation & Maintenance
- Monitoring
- Pathswitch
- Quality Goals
Requirements
Schedule Documents must be delivered by AS4.
Outbound:
Inbound:
Hint for Support:
Comparison with Mako-Edifact
All requirements for AS4-Mako-Edifact-messages hold for AS4-schedule-messages. Both can be processed by a combination of the systems AEP-AS4 & AEP-B2B. There are higher Quality requirements for schedule Messages.
An AS4-Schedule-Message contains a Schedule-Document as attachment, not an Edifact. A Schedule-Document is an XML-file. Usually schedule-documents and mako-edifacts are handled by different backends.
A different AS4-Service-Id is used for Schedule-Messages: https://www.bdew.de/as4/communication/services/FP.
AS4-Schedule-Messages contain additional headers (“Part Properties”). Their content is derived from the Schedule-Document (extracted by B2B).
Preparation & Maintenance
This section guides the schedule installation and configuration. Configuration of EIC-MPID-Mapping and of the Schedule Formats might require change in the future.
Installation & Configuration
The AS4-schedule-system does not require a separate installation. Instead, the existing AS4-B2B-System can be used.
However, additional configuration is required, compare AS4 Schedule Customizing in B2B.
EIC-MPID-Mapping
The AS4-schedule-system requires an EIC-MPID-Mapping, because Schedule-Documents contain EIC but not MPID; however, an MPID is required to determine the recipient’s AS4-address and certificate.
The mapping must be maintained via B2B Extension EIC_MPID_MAPPING. An administrator must keep it updated, because the mapping can change sometimes. For more details compare AS4 Schedule Customizing in B2B.
New market partners must be added here (However in most cases this extension contains just the fixed four ÜNBs of the german market and the tenants.)
Schedule Formats
To support schedule-formats, they must be configured in B2B. They are configured via Extension DIALECT. We support these 13 formats:
- Schedule 2.3, 5.0, 5.2
- SRQ 1.0, 4.0
- ACK: 2.3, 7.0
- CNF: 2.3, 5.0, 5.1
- ANO: 2.3, 5.0, 5.2
If more formats must be supported, they must be added in the DIALECT extension. For more details compare AS4 Schedule Customizing in B2B.
Monitoring
B2B Message Monitor can be used for Monitoring of AS4-Schedule-Messages.
If schedule-messages are the only XML-Messages processed by your B2B, you can filter for xml to find them. You can also filter for the schedule types: Schedule / SRQ / ACK / CNF / ANO.
- System & Partner columns display the mapped MPID.
- The Reference-No is derived from the Schedule-Document.
- Type will be one of the following: Schedule / SRQ / ACK / CNF / ANO.
- Our Standard Customizing provides the channels OUT_SCHEDULE & IN_SCHEDULE.
Pathswitch
BDEW does not require Pathswitch anymore after the 1st of April 2024. AS4-Schedule however will start on the 1st of October 2024. Thus, there is no need for Pathswitch (but it is still supported by AEP). New relations can be activated immediately if both market partners agree.
Quality Goals
Since Schedule-Messages have a high financial impact already on the next day, their successfully delivery in time is crucial. Therefore, the AS4 Architecture supports redundancy and scalability. B2B-Message-Monitor can be used to monitor & restart the delivery of schedule-messages. B2B supports the delivery of Error-Notifications via Mail. Within our cloud we use further monitoring tools to ensure the AS4-Message-Delivery.
24-7 Support
Due to the high criticality of schedule-messages, Arvato ca grant 24-7 support to the customer.
Prioritization
If you want to prioritize schedule-messages over electricity-edifact-messages, it holds:
- B2B supports prioritization of B2B queue entries & of outbox entries.