In this article, we will cover:
- What an IDoc is
- How SAP ECC IDoc Integration extension can help you
- The IDOC types it supports
- How to activate the extension
- How the extension operates
What is IDoc?
IDoc (Intermediate Document) is a structured data format used in SAP to exchange information between different components and systems. Think of it as container for business transactions, allowing you to send and receive data within SAP applications. Many SAP systems rely on the IDoc framework, supporting various interface types like file-based, Remote Function Calls (RFC), and more.
How SAP ECC IDoc Integration extension helps you
The extension simplifies data integration by converting your documents directly into the IDoc format.
Supported IDoc types
This extension is versatile and supports any IDoc type. If you have an XSD definition or internal documentation for your specific type, we can assist in creating the necessary mapping. Reach out to our support team for guidance – support@rossum.ai.
Setting up the extension
Here’s how to set up the extension in a few easy steps:
Step 1: Activate the extension
To activate the extension, follow these steps in the Rossum application:
- Click on the “Extensions” tab at the top
- Select “Rossum Store” to access available extensions
- Choose the “SAP ECC IDoc Integration” extension
- Click “Try extension”
Step 2: Specify queues
In “Rossum Store Extension Settings,” scroll down to “Queues” and select the queues where you want to use the extension. Be sure to save your changes after selecting the queues.
Step 3: Enable logging (recommended)
You have the option to save the request and response JSON objects into extension logs. While the step is not mandatory, we recommend it for better tracking
Step 4: Save changes
Save the changes you have made.
The extension’s “Configuration” is prepared by the Rossum team, so you do not need to make any changes here. If you have questions, do not hesitate to contact our support team.
How the extension operates
The extension uses a configuration mapping, initially set for the INVOIC02 IDoc document type. However, we can quickly create a mapping for any type if you provide the XSD definition for your specific IDoc.
The extension is triggered by the annotation_content.initialize and annotation_content.updated events.
To find the URL of the IDoc generated from your document, you have a few options:
Make change to the annotation content
The URL will appear in a blue pop-up at the bottom of the validation screen whenever you make changes to the annotation content (e.g., updating values, moving bounding boxes, etc.).
Generate URL using a button
To view the URL without making changes, you can add a button to the queue schema. To do this, go to “Queue settings,” click on “Fields to capture,” and add a new field with the following configuration:
- Label: Choose your button label
- ID: Select a button ID
- Data type: Button
- Visible: Enabled (to make the button visible)
- Export: Decide if the button should be included in exported records (recommended setting is Disabled)
- Popup URL: Leave this field empty
Once the button is added, it will be visible on the validation screen, and you can click on it to generate the URL.
Check the extension logs
Extension logs also store the IDoc URL. You can check it by going to “Extensions” and then “Logs,” where you can select the relevant extension from the list. The URL is visible in the “Message” section.
While this extension allows you to view and potentially save your IDoc file, it may not be sufficient for full-scale automation. To enable automatic file saving to S3, SFTP, your API or any other system our team can tailor the extension to meet your specific needs.
