Configuring SAP ERP

Objective

After completing this lesson, you will be able to describe the configuration tasks required in SAP ERP system for Purchase Order Collaboration process

Purchase Order

Purchase order collaboration involves configuring the following documents in SAP ERP:

  • Purchase Order
  • Order Confirmation
  • Ship Notice
  • Receipt
  • Invoice

Purchase Order

To configure Purchase Orders for Purchase Order Collaboration, complete the following tasks:

  1. Define message output for Purchase Order
  2. Maintain parameters for Purchase Order
  3. Configure implicit enhancement for Change and Cancel Orders
  4. Implement a customer exit for Purchase Order

Define message output for purchase order

Message output is a technique to control output of an application like Purchase Order generation as print/mail/EDI output. Purchase Orders created by buyers are transmitted to suppliers via SAP Business Network as IDocs and for that Purchase Order message output configuration is required

Simulation

In this simulation, you will learn how to define message output control for purchase orders

Maintain Parameters for Purchase Order

The parameters that must be set up for Purchase Order Collaboration are listed in following table. To set up these parameters , navigate to the following SPRO path: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration>Application Specific Settings>Purchase Order>Maintain Parameters for Purchase Order.

Variable NameField NameNumberLowDescription

ORDER_ENABLED

Leave Blank0000

To enable, enter X. To disable, leave blank.

Enable or disable the SAP Ariba provided enhancements for Purchase Orders.

REGIO_DESC_ENABLEDLeave Blank

Leave Blank0000

To enable, enter X. To disable, leave blank.

Enable this parameter to populate Region Description in the IDoc segment.

CSC_COPY_SUPPLIER_PARVW

Leave Blank0000

YS or YL for example.

Required for multi-tier Purchase Orders. Use this parameter to send more than one copy of the Purchase Order or Receipt.

DELIVER_TO_PARVW

Leave Blank0000

YS or YL for example.

Mention the Partner function to fetch the Parter details.

ARIBA_SRVMAPKEY

Leave Blank0000

To enable, enter X. To disable, leave blank.

Required for service Purchase Orders that have Service Line Number and use the Service Map Key activated in the SAP ERP system.

PRINT_REL_CHK_ENABLED

Leave Blank0000

To enable, enter X. To disable, leave blank.

Enable or disable the output relevant field check for Purchase Order.

HANDLING_UNITS

Leave Blank0000

To enable, enter X. To disable, leave blank.

Enable or disable the to send isHUMandatory or send blank in purchase order.

Configure Implicit Enhancement for Change and Cancel Orders

This process allows users to configure implicit enhancements for change and cancel orders.

Step 1: Navigate to the program

To configure Implicit Enhancement for change and cancel orders, complete the following steps:

1. Run the transaction code SE38, The ABAP Editor: Initial Screen displays.

2. In the Program field, enter LEINMF0Q and choose Display

Step 2: Select the program

3. In the popup select the SAPLEINM

Step 3: Create Implement Enhancement

4. Choose Enhance and again select SAPLEINM in the popup.

5. Put cursor at the start of lesen-beleg form and right click and choose Enhancement Implementation>Create.

6. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement Implementation and click Create Enhancement Implementation. Provide name and description for the enhancement and press Enter.

Step 4: Implement required code/include

7. In the package popup, specify your Z or Y package, press Enter, and save the package to a transport request.

8. Enter the following: INCLUDE ARBCIG_ORDER_REQUEST_LEINMF0Q IF FOUND.

9. Activate and Save the enhancement.

Implement Customer Exit for Purchase Orders

This process allows users to implement customer exit for Purchase Orders.

To implement a customer exit for purchase orders, complete the following steps.

Step 1: Create a new project

1. Run transaction code SPRO.

2. Choose SAP Reference IMG.

3. Navigate to: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration>Application Specific Settings>Purchase Order>Implement a Customer Exit for Purchase Order.

4. Create a new project. For example, ZMMIDOC.

5. Choose Create.

Step 2: Add a user exit

6. Click Enhancement Assignments and then enter the user exit name MM06E001 and click Enter.

7. Click Components.

Step 3: Implement the required enhancements (1 of 2)

8. Double-click the enhancement name EXIT_SAPLEINM_002. In the new screen that appears, double-click INCLUDE ZXM06U02.

9. Copy and paste the following code: INCLUDE ARBCIG_ORDER_REQUEST_002 IF FOUND.

Step 4: Implement the required enhancements (2 of 2)

10. Go back and double-click the enhancement name EXIT_SAPLEINM_011. In the new screen that appears, double click INCLUDE ZXM06U33.

11. Copy and paste the following code: INCLUDE ARBCIG_ORDER_REQUEST_011 IF FOUND.

12. Save and go back to Project Management of SAP Enhancements screen and activate the project.

Order Confirmation

To configure Order Confirmation for Purchase Order Collaboration, complete the following tasks:

  1. Maintain parameters for Order Confirmations
  2. Implement customer exit to process comments and rejected line items
  3. Enable attachments for Order Confirmations

Maintain Parameters for Order Confirmations

The parameters that must be set up for Order Confirmations are listed in the following table.

Variable NameField NameNumberLowDescription

OC_ENABLED

Leave Blank0000

To enable, enter X. To disable, leave blank.

Enable or disable the SAP Ariba provided enhancements for order confirmation

To setup these parameters, for order confirmation functionality in Purchase Order Collaboration, navigate to the following SPRO path: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration>Application Specific Settings>Order Confirmation>Maintain Parameters for Order Confirmation.

Implement Customer Exit to Process Comments and Rejected Line Item

The steps to implement a customer exit to process comments and rejected line item are similar to the steps describe for a customer exit for Purchase Orders.

The values required to implement a customer exit to process comments and rejected line items are listed in the following table:

ProjectEnhancementUser ExitIncludeCode

As per naming convention, for ex. ZMMIDOC

MM06E001

EXIT_SAPLEINM_007

ZXM06U19

INCLUDE ARBCIG_INCL_ORDER_CONFIRM_01 IF FOUND.

  

EXIT_SAPLEINM_008

ZXM06U20

INCLUDE ARBCIG_INCL_ORDER_CONFIRM_02 IF FOUND.

To maintain these values, navigate to the following SPRO Path: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration>Application Specific Settings>Order Confirmation>Implement a Customer Exit to Process Comments and Rejected Line Item.

Enable Attachments for Order Confirmations

This step is optional and only required if customer would like to use attachments with order confirmations. The values needed to enable this option are listed in the following tables.

Object Category

Object Type

Event

Receiver Type

Receiver Call

Class Name

BOR Object

IDOCORDRSP

INPUTSUCCESS

ARBCIG_ORDERSP

Method

CL_ARBCIG_INB_IDOC_SUCS_EVENT

Interface Name

Method Name

Event Delivery

Behavior Upon Error Feedback

Receiver Status

BI_EVENT_HANDLER_STATIC

ON_EVENT

Using tRFC (Default)

System defaults

No errors

To maintain these values, navigate to the following SPRO Path: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration>Application Specific Settings>Order Confirmation>Enable Attachments for Order Confirmation.

Ship Notice

To configure Ship Notice, complete the following tasks:

  1. Maintain Carrier Details for Vendors
  2. Configure Advance Ship Notice to Receive Ship Notices with Zero Quantities

Maintain Carrier Details for Vendors

For customers that like to use carrier codes during the Purchase Order collaboration, specially while using Advance Ship Notices, this configuration is required. To configure carrier details for vendors, create new entry/entries. Navigate to the following SPRO Path: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration>Application Specific Settings>Advance Ship Notice>Maintain Carrier Details for Vendors.

Configure Advance Ship Notice to Receive Ship Notices with Zero Quantities

To configure the ship notice as part of Purchase Order Collaboration to receive ship notices with zero quantities go to SPRO path: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration>Application Specific Settings>Advance Ship Notice>Configure Advance Ship Notice to Receive Ship Notices with Zero Quantities. In the list of item categories select ELN. If required, choose Position and in the Another Entry popup. enter ELN. For the ELN row, make sure the Relevant for Picking is unchecked.

Receipt

To configure the Receipt, complete the following tasks:

  1. Define Message Output Control for Returns and Corrections
  2. Maintain Parameters for Receipt Request
  3. Configure User Profile Parameters to Activate Collective Slip after Receipt

Define Message Output Control for Returns and Corrections

In this simulation, you learn how to define message output control for Receipt Request. To practice defining message output control for Receipt Request, run this simulation.

Maintain Parameters for Receipt Request

To trigger receipt request messages, maintain all relevant movement types in Purchase Order Collaboration. To maintain these movement types, navigate to the following SPRO path: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration>Application Specific Settings>Receipt Request>Maintain Parameters for Order Confirmation.

Configure User Profile Parameters to Activate Collective Slip after Receipt

For receipt request message, while posting receipts the collective slip flag/function needs to be used by users. For all relevant users in receiving, setting up user profile parameter to activate collective slip after receipt would default the collective slip while creating & posting receipts in buyer ERP systems.

To configure User Profile Parameters to activate collective slip after receipt, navigate to the following SPRO path: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration>Application Specific Settings>Receipt Request>Configure User Profile Parameters to Activate Collective Slip after Receipt.

On Maintain User Profile screen add NDR as parameter id and value X.

Invoice

To configure the Receipt, complete the following tasks:

  1. Maintain Parameters for Invoice.
  2. Maintain SAP Company Code for Each of the Partners.
  3. Maintain Tax Code between the External System and the SAP Tax Codes.
  4. Maintain the Posting Keys and Document Types for Each Company Code.
  5. Implement Customer Exit for Invoices with Service Type Line Items.
  6. Maintain Event Type Linkages for Invoices.
  7. Map cXML Partner to ERP Invoicing party.

Maintain Parameters for Invoice

The parameters that must be maintained for Invoices are listed in the table below. To set up these parameters, navigate to the following SPRO path: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration>Application Specific Settings>Invoice>Maintain Parameters for Invoice.

Variable NameField NameNumberLow
INVOICE_ENABLEDLeave Blank0000To enable, enter X. To disable, leave blank.
INVOICE_PARK_NO_ACC
INV_HDR_PRK_NOSES_POGRX_ENBLI

Maintain SAP Company Code for Each of the Partners

Buyers need to map external company codes to company codes used in SAP. This step is needed to setup EDI profile for invoice processing. To map company codes, navigate to the following SPRO path: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration Application Specific Settings>Invoice>Maintain SAP Company Code for Each of the Partners

Maintain Tax Code between the External System and the SAP Tax Codes

Buyers need to map external tax codes to tax code used in SAP System. To map tax codes, navigate to the following SPRO path: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration>Application Specific Settings>Invoice>Maintain Tax Code between the External System and the SAP Tax Codes.

Click on New Entries and input Partner Type, PartnerNo, Tax Type, Tax Rate, Country and Tax Code.

Maintain the Posting Keys and Document Types for Each Company Code

When an invoice is created by a Supplier in SAP Business Network, it is sent to the Buyer SAP ERP system as an IDoc and getting processed.For this, Buyers need to maintain Posting Keys & Document Types for each company code. To maintain these, navigate to the following SPRO path: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration>Application Specific Settings>Invoice>Maintain Posting Keys and Document Types for Each Company Code.

Implement Customer Exit for Invoices with Service Type Line Items

The steps to implement customer exit to process invoices with service type line items are similar to the steps described for a customer exit for Purchase Order.

The values required to implement a customer exit to process Invoices with service type line items are listed in the following table. SPRO Path: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration> Application Specific Settings>Invoice>Implement Customer Exit for invoices with Service Type Line Items.

ProjectEnhancementUser ExitIncludeCode
ZMRMHMRMH0002EXIT_SAPLMRMH_011ZXM08U22INCLUDE ARBCIG_INCL_INCOMING_INVOICE01 IF FOUND.
EXIT_SAPLMRMH_014ZXM08U25INCLUDE ARBCIG_INCL_INCOMING_INVOICE03 IF FOUND.

To implement customer exit with these values, navigate to the following SPRO Path: Integration with Other SAP Components> SAP Ariba Cloud Integration Gateway>Ariba Network Integration>Application Specific Settings>Invoice>Implement Customer Exit for invoices with Service Type Line Items.

Maintain Event Type Linkages for Invoices

To enable attachments and comments for invoices, Buyers need to maintain event type linkages. To maintain these values, navigate to the following SPRO path: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration>Application Specific Settings>Invoice>Maintain Event Type Linkages for Invoices.

Map cXML Partner to ERP Invoicing party

Buyer may wish to post an incoming invoice to Supplier other than the Supplier listed on the Purchase Order. To specify a different invoicing party for incoming cXML Invoices, navigate to the following SPRO path: Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Ariba Network Integration>Application Specific Settings>Invoice>Maintain cXML Partner to ERP Invoicing Party.

Log in to track your progress & complete quizzes