Configuring Invoice Integration in the SAP System

Maintaining Parameters for Invoice integration

Objective

After completing this lesson, you will be able to configure the parameters required for integrating invoices within the SAP system.

Maintaining Parameters for Invoice integration

SAP Ariba Procurement solutions integrate with SAP ERP or SAP S/4HANA via the SAP Integration Suite, managed gateway for spend management and SAP Business Network, unifying procurement ecosystems for faster sourcing, stronger supplier engagement, and smarter business outcomes.

Maintaining parameters in the SAP Integration Suite, managed gateway for spend management and SAP Business Network, AddOn is crucial. These parameters control data flow, transformation, and synchronization between the SAP backend and SAP Ariba systems, ensuring the accurate exchange of procurement documents such as Purchase Orders (POs), Goods Receipts (GRs), and Invoices. They shape document behavior, structure, and content during integration. In the managed gateway add-on, these parameters define transaction document selection, processing, filtering, and transmission from SAP Ariba to SAP ERP or SAP S/4HANA. They allow tailored integration behavior without custom development.

The Managed Gateway for Spend&Network AddOn parameters include PO-Based Invoices and Non-PO-Based Invoices. All parameters are optional; maintain them based on requirements.

Parameters for PO-Based Invoices:

  • INVOICE_PUSH: Defines the wait time before processing a second or subsequent Invoice when the first one is still being processed. However, this wait time is applied only once. If the processing of the first Invoice exceeds the configured wait time, the second one may still fail due to the ongoing lock.

  • ETE_TAX_SPLIT_ENABLE: Enables splitting tax amounts at the individual invoice line level when an External Tax Engine (ETE) is used, instead of handling taxes only at the header/summary level.

  • ENABLE_INV_ITERATION: Adds flexibility by allowing multiple retry attempts (iterations). If the first Invoice holds the lock beyond the initial wait time defined by the INVOICE_PUSH parameter, the system retries the operation the configured number of times, reducing the chance that the second Invoice fails due to lock conflicts.

  • UNCLR_DWNPMNT_SPLIND: Specifies the Special G/L indicator for uncleared vendor down payment that must be considered during invoice posting and clearing in the backend SAP system. It’s necessary when processing an invoice against an existing vendor down payment. It enables the backend SAP ERP or SAP S/4HANA system to correctly identify uncleared vendor down payments during invoice posting. You can configure a custom Special G/L indicator based on the finance team’s down-payment processing configuration in the SAP system.

Parameters for Non-PO-Based Invoices:

  • ASSET_TR_TYP_FI_NONPO: Defines the default Asset Transaction Type for posting asset-related non-PO invoices from SAP Ariba Procurement solutions. The value is from the A074 table. Ensures SAP Asset Accounting correctly classifies, processes, and records asset acquisitions, enabling successful invoice posting, accurate asset valuation, and proper financial reporting.

  • P2P_INVOICE_ENABLED: Enables or disables SAP Ariba enhancements for non-PO (FI) invoices. The SAP Ariba-provided enhancement helps customers manage withholding taxes on non-PO invoices.

  • NONPO_INV_PRECISION: Applicable for SAP Ariba Procurement solutions. Set the parameter to X (True) to use the amount with precision values from non-PO invoices in SAP Ariba Procurement solutions, instead of calculating it in the SAP ERP or SAP S/4HANA system.

Follow these steps to maintain the parameters for the Invoice in the Managed Gateway for Spend&Network AddOn SPRO:

  1. Using the transaction code SPRO, navigate to Integration with Other SAP Components>Managed Gateway for Spend&Network for Buyer>SAP Ariba Procurement Integration>Application Specific Settings>Invoice>Maintain Parameters for Invoice.

    Screenshot for step 1.
  2. On the Parameters – page, select the Modify button. Screenshot of step 2.
  3. On the Parameters – page, maintain the parameters based on your business requirements.
  4. Once all the necessary parameters are maintained, select the Save button.

    For guidance, refer to the table provided in this lesson. The parameter values shown in the table and in the screenshot are for illustration purposes only.

    Screenshots of steps 3 and 4.

Parameters for Invoice Integration

Parameter NameDescriptionSupported values
ASSET_TR_TYP_FI_NONPOConfigure the asset transaction type if you want to use the asset accounting assignment while posting a FI-based non-PO Invoice. The transaction type value is what you added in the A074 table.

Variable Name: ASSET_TR_TYP_FI_NONPO

Field Name: Leave it blank

Number: 0000

Variant: Provide a variant for SAP Ariba Procurement solutions. For example, VSAP_P

Partition: Provide a partition for SAP Ariba Procurement solutions. For example, PSAP_P

Low: For example, 120

ENABLE_INV_ITERATIONConfigure the number of iterations for the invoice export task to prevent invoices from being locked in the SAP system.

Variable Name: ENABLE_INV_ITERATION

Field Name: Leave it blank

Number: 0000

Variant: Provide a variant for SAP Ariba Procurement solutions. For example, VSAP_P

Partition: Provide a partition for SAP Ariba Procurement solutions. For example, PSAP_P

Low: For example, 10

ETE_TAX_SPLIT_ENABLEConfigure this parameter to enable tax split at the line level for external tax engines

Variable Name: ETE_TAX_SPLIT_ENABLE

Field Name: Leave it blank

Number: 0000

Variant: Provide a variant for SAP Ariba Procurement solutions. For example, VSAP_P

Partition: Provide a partition for SAP Ariba Procurement solutions. For example, PSAP_P

Low: X (to enable) or leave it blank (to disable).

INVOICE_PUSHConfigure time-out settings (in seconds) for the invoice export task to prevent invoices from being locked in the SAP ERP system.

Variable Name: INVOICE_PUSH

Field Name: Leave it blank

Number: 0000

Variant: Provide a variant for SAP Ariba Procurement solutions. For example, VSAP_P

Partition: Provide a partition for SAP Ariba Procurement solutions. For example, PSAP_P

Low: For example, 5

NONPO_INV_PRECISIONSet this parameter to X to use the amount with precision values from the non-PO invoices in SAP Ariba Procurement solutions, instead of calculating the amount in SAP ERP or SAP S/4HANA.

Variable Name: NONPO_INV_PRECISION

Field Name: Leave it blank

Number: 0000

Variant: Provide a variant for SAP Ariba Procurement solutions. For example, VSAP_P

Partition: Provide a partition for SAP Ariba Procurement solutions. For example, PSAP_P

Low: X (to enable) or leave it blank (to disable).

P2P_INVOICE_ENABLEDEnable or disable the SAP Ariba provided enhancements for invoice.

Variable Name: P2P_INVOICE_ENABLED

Field Name: Leave it blank

Number: 0000

Variant: Provide a variant for SAP Ariba Procurement solutions. For example, VSAP_P

Partition: Provide a partition for SAP Ariba Procurement solutions. For example, PSAP_P

Low: X (to enable) or leave it blank (to disable).

UNCLR_DWNPMNT_SPLINDConfigure a custom special GL indicator to adjust the down payment during invoice creation in the SAP system, based on how the finance team has configured down-payment processing.

Variable Name: UNCLR_DWNPMNT_SPLIND

Field Name: Leave it blank

Number: 0000

Variant: Provide a variant for SAP Ariba Procurement solutions. For example, VSAP_P

Partition: Provide a partition for SAP Ariba Procurement solutions. For example, PSAP_P

Low: For example, A

Summary

This lesson focuses on the configuration of integration parameters within the SAP system to control the flow, transformation, and synchronization of invoice data with SAP Ariba Procurement solutions. Learners will explore how to maintain these settings using the Managed Gateway for Spend&Network AddOn to ensure accurate document exchange for both PO-based and non-PO-based invoices.

The content details specific parameters that address common integration challenges, such as handling system locks during high-volume invoice processing, enabling line-level tax splitting for external engines, and managing financial accounting details like asset transaction types and special G/L indicators for down payments. By the end of this lesson, implementation consultants will be able to navigate the SPRO path to tailor integration behavior to meet specific business requirements without the need for custom development.