Add Attachments Scenario

You can use this scenario to load any supported type of attachment.

Creating a Run

Proceed as follows to create a run:

  1. Start transaction /DVD/RMX.

  2. Select Execute Data Ingestion.

  3. In the form, fill out the fields Run ID and Description.

  4. Click Create.

  5. In the pop-up, select the option NOFEX Run.

  6. Click Confirm. The setup wizard is displayed.

  7. In the first screen, enter the logical system and the name of the RFC connection and select Add attachments.

  8. Click Continue.

  9. Define the attachment setup for the desired business object(s):

    1. Find the business object and click Create.

    2. Fill the pop-up with the select options.

  10. Click Continue.

  11. Check and adjust the parameters.

  12. Click Save.

  13. Default parameters usually do not require any change. You can find more information in the section SNP Outboard™ Datafridge Settings.

The process tree has been created.

 

Process Tree Tasks

Go through the tasks one by one. Only start the next task if you have already finished the previous one. You can manually refresh the process tree by clicking the Refresh button.

Run the task Set mapping for line items to edit the configuration in /DVD/RMX_GLFATMP only in specific cases. This is for example the case if you have loaded line item attachments. In this case, you need to attach them to the main record. Usually, this means deleting only some suffixes from the object number.

First, build a list of attachments on the source system. It collects a list of all attachments that fulfill conditions into the SNP Glue cluster. Then load this list into the table /DVD/RMX_OBJATT. A list of attachments is used to generate load tasks. The attachment content is loaded directly via RFC. During the attachment load, the hash calculated from the attachment data is also saved.

If there are any corrupted or non-accessible attachments, the corresponding task will finish with a warning status. You can check the logs directly in the task handler process tree. The task Attachment cleanup will clear the attachment list and delete records for non-loaded attachments.

The validation task compares hashes calculated on the source system during the attachment load with hashes calculated from attachments on the target storage.

If you use the default parameter GLFEX_ATT_ADD_MANDT=X as recommended, MANDT should be stored at the beginning of the field Object Number (OBJNO) in /DVD/RMX_OBJATT. Moreover, a correctly stored target file path (TARGET_FNAME) in /DVD/RMX_OBJATT uses “\” as a delimiter in file systems for Windows servers and “\” for Linux servers.

 

Attachment Relink

If attachments are stored on an external SAP content server, you do not need to move to another target location. You can use the Relink option to store the location information of attachments in SNP Outboard™ Datafridge. Before the attachment load, you need to register the repository on the control system and then set the parameter ATTACHMENT_RELINK to X. Attachments from the external content server stay there, and SNP Outboard™ Datafridge will be able to display and manage them there.

 

Supported Attachment Types

The following types of attachments are supported:

  • GOS attachments: The main table is SRGBTBREL. For instance, attachments can be selected by the Object Type (SAP_OBJECT) and Relationship type (RELTYPE) field from these tables in the setup.

  • BDS attachments: The setup is in BDS_LOCL. The attachment metadata is located in many different tables. For example, attachments can be selected by the Object Type (SAP_OBJECT) field from these tables in the setup.

  • Archive Links: The attachment lists are located in the tables TOA01, TOA02, TOA03, TOAHR and TOADL.

  • DMS attachments: Information is stored in DMS_PH_CD1, DMS_PH_HD1, DMS_DOC2LOIO. Select a convenient business object to add attachments based on the Object field (DOKOB) in the table DRAD.