Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Note
Community interest groups have now moved from Yammer to Microsoft Viva Engage. To join a Viva Engage community and take part in the latest discussions, fill out the Request access to Finance and Operations Viva Engage Community form and choose the community you want to join.
You can design Electronic reporting (ER) formats that the application uses to generate outgoing electronic documents. You can also design ER formats that parse incoming electronic documents and use the content in those documents to update application data.
By using this functionality, you can use a single ER format to generate outgoing electronic documents and then update the application data. Use this feature in the following scenarios:
- To prevent repeated usage of application data in subsequent processes, mark an application’s data immediately after you use it to generate electronic documents. For example, mark payment transactions as already processed immediately after you include them in a generated payment message.
- To store the processing details of electronic documents that you generate by using ER logic. For example, a unique payment message identification that is generated by using the ER expression. The expression is based on information entered in the ER dialog box when the ER format is run to generate documents.
To learn more about this feature, watch the set of ER Generate documents with application data update Task guides (part of the 7.5.4.3 Acquire/Develop IT service/solution components (10677) business process). The guides walk you through the details of Intrastat reporting and archiving. The following files are required to complete certain steps in these Task guides. Download and save these files to your local machine.