Electronic Document Format
It is used for the electronic transmission and processing of sales and service invoices as well as sales and service credit memos. This documentation explains its usage within the Document Sending Profile, as well as the relevant technical components for export and dispatch processing via codeunits.
The following section provides a detailed explanation of the fields within the Electronic Document Format:
-
Code: This is entered in the "Format" field within the Document Sending Profile. This code specifies which format is used for transmitting the document.
-
Description:
-
Usage: This entry is important for correctly categorizing and processing the documents.
-
Codeunit-ID: This specifies the codeunit that is responsible, depending on its configuration, for storing and processing data, which is later transmitted as part of the electronic dispatch.
-
Dispatch Codeunit IDThis specifies the codeunit responsible for sending the document data stored in the buffer.
The following section explains the key codeunits in more detail:
|
Codeunit-ID |
Codeunit-Name |
Description |
|---|---|---|
|
5518587 |
BRAG eDoc Buff.Export Endp. |
Used in the export process. Once a document is released in the system for transmission, the CU collects the relevant data. This intermediate storage is then passed on to the next CU 5518588, which handles the actual dispatch. |
|
5518588 |
BRAG eDoc Buff.Delivery EndP. |
This CU handles the actual transmission. It processes the document data stored in the export buffer and ensures that the data is securely sent to the recipient (e.g., clearing house). |
|
1610 |
Exp. Sales Inv. PEPPOL BIS3.0 |
Exports sales invoices according to the PEPPOL BIS3.0 standard. This codeunit creates a compliant XML file for electronic invoices that can be sent via the PEPPOL network. |
|
1611 |
Exp. Sales CrM. PEPPOL BIS3.0 |
Exports sales credit memos according to the PEPPOL BIS3.0 standard. This codeunit processes credit memos and generates a PEPPOL-compliant document. |
|
1612 |
Exp. Serv.Inv. PEPPOL BIS3.0 |
Exports service invoices according to the PEPPOL BIS3.0 standard. Used for creating invoices in the service sector. |
|
1613 |
Exp. Serv.CrM. PEPPOL BIS3.0 |
Exports service credit memos according to the PEPPOL BIS3.0 standard. Similar to sales documents, but for services. |
|
1620 |
PEPPOL Validation |
Performs validation of PEPPOL documents to ensure they comply with BIS3.0 standards. This ensures that the XML documents are correctly structured and contain all necessary data. |
|
1621 |
PEPPOL Service Validation |
Performs additional validations at the service level to ensure the compliance of PEPPOL documents in the service domain. It checks for service-specific requirements. |
Codeunit 5518587 BRAG eDoc Buff.Export Endp. and 5518588 BRAG eDoc Buff.Delivery EndP. are always used in combination.
Document Sending Profiles
It is a configuration that determines the method and format in which documents such as invoices, credit notes, and more are sent to recipients. This applies to both sending via email and other electronic means such as the eDoc format.
eDoc Endpoints
It is a defined technical interface point through which electronic documents (eDocs) are exported or imported. This interface functions as a "bridge" between the ERP system and external systems, such as customer systems, authorities, clearinghouses, or third-party providers. The eDoc endpoint handles the transfer of documents.
The following fields are described in more detail:
-
Code: Is used in the eDoc customer endpoint. It defines, in combination with the eDoc profile and possibly a specific debtor, which endpoint is used.
-
Description:
-
Active: Indicates whether the eDoc endpoint is active. If true, the endpoint is active and usable; if false, it is deactivated.
-
eDoc Endpoint: The name of the endpoint that describes the type of format.
-
Endpoint: The URL of the eDoc endpoint through which documents are electronically sent/received. This can be a web service or API URL.
-
Authentication Type: Method of authentication used for accessing the endpoint. Basic, APIToken(500), or APIToken(1000).
-
Number of Auth Parameters: Number of parameters required for authentication, varies depending on the authentication type.
-
Number of URL Parameters: Number of parameters that must be passed in the URL, varies depending on the authentication type.
-
Number of HTTP Header Parameters: Number of HTTP header parameters required depending on the authentication type.
-
Last Incoming Transmission: Date of the last successful transmission received via this endpoint. Used to monitor system activity.
More Detailed Explanation
Authentication Type: Access to the endpoint can be protected by various authentication methods, such as simple username/password (Basic) or using API tokens. The token length (500 or 1000 characters) is also specified.
Number of Parameters: Depending on the authentication type, the number of parameters in the URL, HTTP headers, or for authentication may vary.
eDoc Customer Endpoints
It is an important configuration that enables sending electronic documents specifically to debtors. Customer endpoints define which customer is connected with which eDoc endpoint and eDoc profile to control the exchange of documents in electronic format.
The customer endpoint describes the connection of a specific customer or group of customers with a specific eDoc endpoint and an eDoc profile. This configuration determines through which endpoint and in which format documents are electronically sent to a customer.
Fields of the customer endpoint:
Customer ID: Optional field to specify a specific customer. If this field is not filled, the configuration applies to all debtors.
Profile Code: Defines the type of eDoc to be transmitted. This profile determines the format and structure of the document.
Endpoint: Used to transmit the document. The endpoint contains the URL and other technical details that control the sending.
Record-Exportbuffer
tbd.