Skip to end of metadata
Go to start of metadata

Purpose

This article is to provide information about Customizing related to SRM PO

 

Overview

In this page you will know the general customizing setting for SRM PO including important badis and code suggestion.

SPRO-SAP Reference IMG

Activate Extended Classic Scenario

SAP Implementation Guide
> SAP Supplier Relationship Management
> SRM Server
> Cross-Application Basic Settings
> Activate Extended Classic Scenario

There are four check boxes available                      

  • Activate Extended Classic Scenario
    If checked then conveys that extended classic scenario is active and whether the PO will be available in ERP will depend on further conditions. If unchecked, thePO will  always remain local to SRM.
  • Back-End Purch.Groups Responsible
    If Purchasing Groups from SAP ERP are responsible. Elaborate.
  • Enable  Consistency Checks in Back-End
    This is a new feature introduced from SRM 6.0 SP04. When there are no errors thrown from the SRM then on check or order, the purchase order is simulated in ERP  for consistency checks. This is to avoid thePOgetting in the state of “Error in Process”. For example, there are instances when the SRM PO allows a date in future which is not allowed in ERP due to factory calendar etc. In such cases if the SRM PO is ordered and there is no backend consistency check then the SRM PO may go to “Error in Process” and the ERP PO may not be created. So, before ordering, the SRM can check that the SRM PO is consistent from the ERP point of view and then can decide based on the customizing (check box 4) whether to show he message as error (in this case PO can not be ordered) or show them as a arning.
  • Display Back-End Messages as Errors 
    Set whether the messages are displayed as errors or warnings.

 

BAdI of Activate Extended Classic Scenario

SAP Implementation Guide
> SAP Supplier Relationship Management
> SRM Server
> Business Add-Ins
> Control Extended Classic Scenario
> Activate Extended Classic Scenario

The global customizing for activating extended classic scenario can be overridden by a BADI for a combination of product categories, transaction types and purchasing organizations.

BADI BBP_EXTLOCALPO_BADI is used to override the customizing settings based on certain conditions.

Requirement for BADI: It may be required at times that the extended classic scenario is not required for a certain product category and the customer needs to create a classicPOin ERP. In the BAdI implementation, the indicator for this product category can be set to inactive.

It may be required that the extended classic scenario is required only for a set of combination of purchasing organization and transaction type.

Standard settings

The following methods are available in the BAdI:

  • DETERMINE_EXTPO:  to control the extended classic scenario for shopping carts. For example, you      can define whether the extended classic scenario is used for a certain      product category.         
  • DETERMINE_EXTPO_CREATE:      For purchase orders created manually in Enterprise Buyer, you can use the method DETERMINE_EXTPO_CREATE to define for which purchasing organization or transaction type the extended classic scenario is to be used. In addition, you can change the logical FI System for the purchase order.

Code Snippet:

      METHOD if_ex_bbp_extlocalpo_badi~determine_extpo_create.
      CASE sy-mandt.
       WHEN '300'.
         IF iv_trans_type = 'ECLP'.
           bbp_extpo_gl-bbpexpo = ''.
          ENDIF.
        ENDCASE.
      ENDMETHOD.

     

BBP_EXTPO_GL-BBPEXPO: If the field is empty, the request is not subject to the extended classic scenario.

Activities

Implement and activate the BAdI if you want to restrict the global activation of the extended classic scenario.

  • You can define whether the extended classic scenario is used for the following item data  of the shopping cart:
    • Product type
    • Product
    • Product category
  • For manual  purchase orders, you can define the purchasing organization and ransaction type where the extended classic scenario is used.

 

BAdI of Transfer Purchase Order Data to Logistics Backend:

SAP Implementation Guide
> SAP Supplier Relationship Management
> SRM Server
> Business Add-Ins
> Control Extended Classic Scenario
> Transfer Purchase Order Data to Logistics Backend

With the Business Add-In BBP_ECS_PO_OUT_BADI, you can override the standard and determine which data from a purchase order in the extended classic scenario is transferred to the linked logistic backend system.

This BAdi should be used carefully as any inconsistent data may lead to eitherPOgoing to “Error in process” or it will not be replicated to backend at all.

 

Defining ECS PO Number Ranges in SRM and ECC

In SRM:

SAP Implementation Guide
> Supplier Relationship Management
> SRM Server
> Cross-Application Basic Settings
> Number Ranges
> Define Number Range for Local Purchase Orders

Here you define a number range that does not collide with existing POs in ECC.

In ECC:

SAP Implementation Guide
> Material Management
> Purchasing
> Purchase req/Purchase order
> Define Number ranges

Here you define the same PO number range in SRM marked as EXTERNAL