OpenText - Ariba Network Integration With Ariba CIG

OpenText™ Vendor Invoice Management for SAP® Solutions
OpenText™ Vendor Invoice Management

for SAP® Solutions
White Paper
Ariba Network Integration with Ariba CIG
www.opentext.com/contact
Copyright © 2018 Open Text SA or Open Text ULC (in Canada).
All rights reserved. Trademarks owned by Open Text SA or Open Text ULC (in Canada).
The Information Company™
Contents
1 Introduction ...................................................................................................... 3
2 Installation ........................................................................................................ 4
3 Configuration ................................................................................................... 5
3.1 Configuring inbound processing (InvoiceDetailRequest) .......................... 5
3.2 Configuring outbound processing (StatusUpdateRequest) ....................... 6
3.3 Known Issues ............................................................................................ 8
3.3.1 Non-PO invoices.............................................................................. 8
3.3.2 PO credit memos ............................................................................. 8
About OpenText ................................................................................................ 8
1 Introduction
OpenText Vendor Invoice Management (VIM) supports Ariba Network integration already
for some time. The integration options available and supported by VIM until now were:
• SAP Business Suite Adapter for Ariba

• Ariba Cloud Integration (CI) adapter or its predecessor, Ariba Network Adapter,
with NetWeaver PI
Ariba Cloud Integration Gateway is a new integration option supported by VIM now.
The minimum VIM release and SP levels are VIM 7.5 SP5 with OpenText Business
Center (BC) 16.0 update 1, and VIM 16.3 with Business Center 16.3.
Notes:
Support of freight and handling costs with delivered mapping requires a minimum of VIM
7.5 SP8 or VIM 16.3 SP2 with Business Center 16.3.2. You can still implement that on
older versions by using a custom mapping function.
Currently, the following scenarios are supported with Ariba Cloud Integration Gateway
(CIG):
• Inbound Invoice. This includes standard invoice, credit memo and non-PO
invoices.
• Outbound Invoice Status Update.
• Both SAP ERP and S/4HANA are supported. SAP Ariba CIG component ARBCI1
is required. For details on specific SAP Basis, SAP_APPL or S4CORE versions,
see the VIM and Business Center documentation.
Comments and attachments are currently not supported. For more information on current
limitations, see section 3.3 “Known Issues.”
To implement Ariba Network integration with VIM through CIG, OpenText recommends
that you get the integration working without VIM first, with inbound IDOCs posted by
standard SAP modules and outbound status updates sent back. To achieve this, you can
follow the documentation provided with CIG by SAP. Then you can proceed to add VIM
into the flow.
Note: SAP provides reports integrated into SPRO transaction, which create necessary
entries in SAP IDOC configuration tables. To connect CIG and VIM, you will have to
change the IDOC configuration created by the reports. If the configuration reports are run
again by some reason, you will have to redo the necessary configuration for VIM.
The following sections assume that the standard integration is configured to work without
VIM and they describe the additional steps to perform.
The content of this document will be integrated into VIM documentation (Installation and
Configuration guides) with the release of VIM 7.5 SP8 and VIM 16.3 SP2.
2 Installation
Because of dependencies on the SAP ARBCI1 and ARBCI2 components, OpenText
delivers the necessary objects as a separate set of transport files. You find the transport
files on Open Text My Support.
The delivery of the transport files is provided with VIM 7.5 SP7. Integration is supported
by other versions as described in the previous section. You can use the provided
transport files with the mentioned older VIM versions and SPs.
To import the transport files:
1. On My Support, access My Support > PATCHES > Vendor Invoice Management

> Vendor Invoice Management – Ariba Network CIG Integration.
2. Download the transport files provided through the link “VIM Ariba CIG Transport
Files” (file VIM-Ariba-CIG.zip.)
3. Perform the import.
Importing Notes:
1. When importing the customizing transport on systems with Business Center

16.3.1 or lower, two import errors are shown because of truncated values of
key fields for freight and handling costs mapping. As explained above, this
mapping is not supported on older VIM/BC support packages. Ignore these
errors.
2. The customizing transport creates or updates an entry in the BC Inbound
“Registration Idoc” node with the following parameters:
• Partner number = space
• Partner type = LS
• Partner role = LS
• Message type = INVOIC
• Test = X
Before performing the import, verify whether you already have such an entry.
Save the values of non-key fields to restore them after import. The
corresponding IDOC mapping entries are created for development object
ARBCIG_INVOIC.
Transport list:
TWRK900575 – workbench objects for outbound invoice status update.
TWRK900607 – customizing, CIG IDOC mapping for incoming invoice request.
After the import, perform additional configuration steps as described in the next sections.
3 Configuration
3.1 Configuring inbound processing
(InvoiceDetailRequest)
The inbound invoice IDOCs need to be processed by BC Inbound and then routed into
VIM. The first configuration steps to perform are the following:
To switch the standard IDOC processing to BC Inbound:
1. In transaction WE20, create a process code for partner profile.

2. In transaction WE42, enter the BC Inbound handler function module
/OTX/PF01_UTIL_IDOC_INPUT for the process code.
3. In transaction WE57, enable the processing of the CIG IDOC type
ARBCIG_INVOIC by the BC Inbound handler function module.
To support CIG integration, a new IDOC mapping is needed. The IDOC mappings are
maintained in the BC customizing transaction /OTX/PF00_IMG. Proceed to the following
customizing node:
OpenText provides a new IDOC mapping for CIG, delivered with a transport. If you were
following the CIG configuration guide provided by SAP, you will likely have created a new
IDOC partner with the name that corresponds to your SAP system logical system name.
The new standard mapping provided by OpenText does not refer to any specific partner
and therefore it needs to be copied to reflect your specific settings. You find those
mapping entries by the name of their development object, ARBCIG_INVOIC. Copy those
entries providing your correct target IDOC partner:
If needed, adjust the existing entries or create new ones for other fields.
Notes:
• You can enter the 4-character qualifier values for freight and handling only if you
use Business Center 16.3.2 or a later SP.
• If using your logical system name as the IDOC partner name, you will normally
have to create production and test system mapping entries already in your
development/customizing system and then transport your settings.
For further details about configuration and running of the BC inbound, refer to Business
Center Configuration Guide.
3.2 Configuring outbound processing

(StatusUpdateRequest)
When you integrate the outbound invoice status update without VIM, the status updates
will be sent into Ariba Network for posted SAP documents. Additional components
provided by OpenText allow you to send the status updates for documents that are not
posted yet but are processed in VIM (DP documents).
Note: The status updates are not sent for incoming invoices that are still being processed
in BC inbound, that is, from the time of the IDOC creation until the start of the DP
workflow. Typically, it is a short time period defined by the frequency of the background
job that runs BC inbound handler, unless the BC inbound processing stops with an error
by some reason.
The status updates are sent by the standard program provided with CIG package,
ARBCIG_INVOICESTATUS_EXPORT. OpenText provides an implementation of a BADI
called by that program to add VIM DP documents into the output. Make sure that the
BADI implementation /OPT/VIM_ARB_CIG_ISU is active in CIG customizing. Normally it
is active after you install VIM CIG integration component.
Additionally, you need to set the supplier network class to

/OPT/CL_E_SUPPLIER_NETW_ARBCIG for the Ariba Network in VIM customizing.
To set the supplier network class:
1. Proceed to the following customizing node:
2. Adjust the class name:
The VIM to Ariba status mapping (contents of other customizing nodes in the screenshot
above) normally does not need to be adjusted. If you need to do the changes in the
status mapping, see VIM Configuration Guide, section “Integrating the Ariba SAP
NetWeaver Process Integration adapter” for more details.
3.3 Known Issues

Mappings of some fields were not supported by CIG inbound logic in standard at the time
of the release of VIM integration component. Since the fields are eventually mapped into
IDOC fields, you can extend the IDOC mapping accordingly and support additional
scenarios, as soon as the support is implemented in CIG.
3.3.1 Non-PO invoices

For Non-PO invoices, the company code cannot be mapped correctly. You can
implement your own company code mapping as extension if you can define a project
specific mapping. For example, if each vendor supplies to exactly one company code.
3.3.2 PO credit memos

Currently, the PO number is not being mapped into IDOC.
About OpenText
OpenText enables the digital world, creating a better way for organizations to
work with information, on premises or in the cloud. For more information about
OpenText (NASDAQ: OTEX, TSX: OTC) visit opentext.com.

OpenText - Ariba Network Integration With Ariba CIG

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText - Ariba Network Integration With Ariba CIG

Uploaded by

Copyright:

Available Formats

OpenText™ Vendor Invoice Management for SAP® Solutions

OpenText™ Vendor Invoice Management

Ariba Network Integration with Ariba CIG

The Information Company™

• SAP Business Suite Adapter for Ariba

To import the transport files:

1. On My Support, access My Support > PATCHES > Vendor Invoice Management

1. When importing the customizing transport on systems with Business Center

TWRK900575 – workbench objects for outbound invoice status update.

TWRK900607 – customizing, CIG IDOC mapping for incoming invoice request.

To switch the standard IDOC processing to BC Inbound:

1. In transaction WE20, create a process code for partner profile.

3.2 Configuring outbound processing

Additionally, you need to set the supplier network class to

To set the supplier network class:

1. Proceed to the following customizing node:

2. Adjust the class name:

3.3 Known Issues

3.3.1 Non-PO invoices

3.3.2 PO credit memos

You might also like