SAP XI/PI – Invoice Attachment Transfer from ARIBA to VIM

The documents that are connected to the invoice in the Ariba Network system should be transferred to the VIM system via PI Integration as part of the Ariba Supplier Invoice process. From there, the attachment can be viewed from the VIM workspace transaction /OPT/VIM_WP.

Only Ariba network PDF invoices are accepted by VIM, allowing them to accurately supply goods, materials, and services. Beginning with Ariba cloud integration version CI9, Ariba supports BASE64-encoded data and has included a document transfer feature.

PI Mappings and UDF’s Used:

PI mappings for attachment fields in IDOC

Below UDF’s are used in PI Mappings

1. GETATTACHMENTATTRIBUTES

2. GETATTACHMENTCONTENT

3. SPLITATTACHMENTCONTENT

S/4HANA Setting up:

The comprehensive setup instructions needed to activate the document transfer feature are listed below.

Step 1: Create custom document types beginning with Z in t-code OAC2, as indicated below.

Step 2: Next, link these custom document types to the business entity using t-code OAC3.

Type of Object: /OPT/V1001
Type of Document: Z_DOC
Link Condition: X
Link Condition: X
CA Storage System (It is “MA” according to guidelines; client-to-client variations may occur. Basis designed the storage system name as CA.)
url: TOA01
Retention as of: Null or blank

The aforementioned procedures will be carried out by BASIS, although BASIS needs feedback from the technical team.

Step 3: Ariba offers a single standard IDOC extension/ARBA/INVOICE for handling invoice attachments.

Set up WE81’s extension/ARBA/INVOICE against the INVOIC message type.

Improving the VIM Class to Manage ARIBA Documents:

As can be seen below, a Registration ID was formed in VIM against the IDoc once it had been successfully generated.

If the VIM process code is set in the WE20 partner profile, the same registration ID (ex:344) ought to show up in the VIM inbound work place tcode /OTX/PF03_WP.

After submitting the registration ID on tcode /OTX/PF03_WP, a DP document will be generated in the VIM workspace.

Standard Ariba document archiving can be triggered via the VIM class /OTX/PS03_CL_VIM_MODULE_IDOPDF method PROCESS_MODULE. This method can also be used to archive bespoke documents attached from the Ariba network.

Reading attachment content from IDOC and manually putting it in the CA content repository is how all Ariba invoices are automatically generated, following the same procedure as ordinary Ariba documents.

You can access the ARIBA documents that are connected here. Only PDF documents are supported by VIM.

Please feel free to ask questions in the space provided below if you need any help understanding any of the tutorial’s sections. We make an effort to respond to every question.

Please share your thoughts.

Let’s Web Dynpro. Part IV

Related Posts

Attachments for SAP XI/PI – ARIBA Invoices sent via PI to S/4HANA

Integration with SAP systems has never been more intriguing, especially with Ariba, Workday, Concur, Successfactors, Fieldglass, Hybris, and other satellite cloud solution vendors banging on doors every day. 🙂 I…

11 Steps to Include a New Field in an Already-Existing SAP LSMW Batch Input Recording

Alright. Why in the world do we care about LSMW in this paper when S/4HANA migration cockpit should ideally replace it? 🔥🎥 The simple answer is that not all people…

Leave a Reply

Your email address will not be published. Required fields are marked *

You Missed

SAP XI/PI – Invoice Attachment Transfer from ARIBA to VIM

  • By Varad
  • November 8, 2024
  • 3 views
SAP XI/PI – Invoice Attachment Transfer from ARIBA to VIM

11 Steps to Include a New Field in an Already-Existing SAP LSMW Batch Input Recording

  • By Varad
  • November 6, 2024
  • 3 views

Part 23 of ABAP for SAP HANA. How Can AMDP Be Used to Access Database Schema Dynamically?

  • By Varad
  • November 4, 2024
  • 3 views

S/4HANA VDM 1 Employing CDS Virtual Data Model for Embedded Analytics

  • By Varad
  • November 1, 2024
  • 5 views