Maintaining the Mapping Setting for Purchase Order/SA/SAR Outbound​

Objective

After completing this lesson, you will be able to maintain the entries at the Company Code level to control sending your accounting and organization data to the supplier.

Maintaining the Mapping Settings for Purchase Order/SA/SAR Outbound

When integrating Purchase Orders from SAP ERP or SAP S/4HANA (on-premise) to the SAP Business Network via the Managed Gateway, organizations must ascertain whether and how to share accounting information such as GL accounts, cost centers, WBS elements, etc., with suppliers.​

Accounting data is internal and sensitive, typically used only within your organization for budgeting, internal reporting, and compliance with internal financial policies. Suppliers generally do not require this data, so it’s often excluded unless there is a business use case for sharing it,such as service purchase orders needing time/material reconciliation, or if there is a contractual or compliance requirement.​

For instance, a service purchase order for IT consulting necessitates that the supplier track hours billed against specific WBS elements. In this scenario, the WBS Element may be exposed, but the G/L Account and Cost Center remain internal.​

As a best practice, you should always:​

  • Review Business Needs: Include accounting info only if the supplier needs it to fulfill or invoice the purchase order correctly.​
  • Minimize Exposure: Limit accounting info to what's essential; never expose sensitive financial structures.​
  • Audit and Document: Clearly document what is being shared and why, for compliance and change tracking.​
  • Use Controlled Mapping: Apply condition-based mapping logic via BAdIs or mapping tables.​

When a purchase order is created with an account assignment category, it should be filtered out to transfer account assignment details based on the company code. By default, accounting data will be sent to the SAP Business Network supplier, regardless of the company code.​

If any company wishes not to send accounting data, an entry should be maintained for that company code. In the case of the Invoice Management solution, an entry needs to be maintained based on the company code for not sending the accounting data.​

Follow these steps to maintain the entries for Controlling Sending Your Accounting Information to the Supplier:​​​

  1. Using the transaction code SPRO, navigate to Integration with Other SAP Components>Managed Gateway for Spend&Network for Buyer>SAP Business Network Integration>Application Specific Settings>Purchase Order.​Image of step 1.
  2. Expand the Purchase Order section and select IMG-Activity for Mapping Setting for Purchase Order/SA/SAR Outbound.Image of step 2.
  3. On the Change View "Further mapping setting for purchase order outbound": Ov screen, select New Entries.Image of step 3.
  4. Maintain the following values:
    1. Company Code: Enter the company code. For example, 3000.
    2. Do not send Account Assignment Data: Check the box if you do not want to send your accounting data to the supplier.
    3. Do not Send Additional Data for SAP Ariba Invoice Management: (For SAP Ariba Invoice Management customers only) Check the box if you do not want to send the company code-related data to the supplier.
  5. Once the entries for all the desired company codes are maintained, choose Save.Image of steps 4 and 5.

Summary

In this lesson, we explored how organizations can manage the sharing of accounting information, like GL Accounts, Cost Centers, and WBS Elements, during the integration of Purchase Orders from SAP ERP or SAP S/4HANA to the SAP Business Network using the Managed Gateway Add-On.​

Key points covered include:​

  1. Sensitivity of Accounting Data: Accounting information is internal and sensitive, typically used for budgeting and compliance. It should be shared with suppliers only if required for specific business needs or contractual obligations.​
  2. Best Practices:​
    • Review Business Needs: Determine if suppliers need accounting information to correctly fulfill or invoice the Purchase Order.​
    • Minimize Exposure: Limit sharing to essential data; avoid exposing sensitive financial structures.​
    • Audit and Document: Record what data is shared and why, ensuring compliance and tracking changes.​
    • Use Controlled Mapping: Apply condition-based logic using BAdIs or mapping tables to manage data sharing.​
  3. Entry Maintenance: To control accounting data sharing:​
    • Use transaction code SPRO to configure settings.​

    • Maintain entries for company codes where accounting data should not be shared.​

By following these practices and steps, you can protect sensitive accounting information while ensuring effective collaboration with suppliers through the SAP Business Network. This approach supports operational integrity and compliance while fulfilling business requirements.