Configuration steps for Extended Classic Scenario

[Former Member]

Hi All,

Could you please let me know what are the configuration steps required for extended classic scenario.

Thanks in advance

[Former Member · Accepted solution]

Hello,

You can activate extended classic scenario by following configuration:

SPRO - Cross application basic settings - Activate extended classic scenario - Flag this node.

You will find this useful.

https://wiki.sdn.sap.com/wiki/display/SRM/ConfigurationGuidesSRM+5.0

More information : http://service.sap.com/ibc-srm

Thanks

Ashutosh

[Former Member · Accepted solution]

Hi,

Important Settings that Determine the Extended Classic Scenario

The following settings are required for the extended classic scenario:

u2022 At least one backend materials management system and accounting system is connected to the SAP SRM system and defined in the configuration setting Define Backend Systems.

u2022 Product categories from the backend procurement system are replicated and used in the SAP SRM system.

u2022 The target system for each product category is the backend system in the configuration setting Define Backend Systems for Product Category. Optionally, BADI BBP_DETERMINE_LOGSYS is implemented to determine the backend system.

u2022 The extended classic scenario is activated in the configuration setting Activate Extended Classic Scenario. Alternatively, BAdI BBP_EXTLOCALPO_BADI is implemented to control the extended classic scenario based on customer defined rules.

u2022 If the backend system is an SAP R/3 version lower than 4.6B, you must define local purchasing organizations and purchasing groups.

u2022 If the backend system is an SAP R/3 version 4.6B or higher, you need to map the purchasing group used in the purchase order to the backend purchase group in one of the following ways:

u2022 Use a backend purchasing organization and purchasing group in the shopping cart and purchase order.

u2022 Use BAdI BBP_PGRP_FIND to determine a backend purchasing group in the shopping cart.

u2022 If a local (created in SAP SRM without reference to a backend system) purchasing group and purchasing organization are used, then a valid backend purchasing group is assigned to the RFC user that created the backend purchase order. This assignment is made in the backend system using user parameter EKG in Transaction code SU01.

u2022 Implement the user exit of the BAPIs BAPI_PO_CREATE1 (EXIT_SAPL2012_001 and EXIT_SAPL2012_003), and BAPI_PO_CHANGE (EXIT_SAPL2012_002 and EXIT_SAPL2012_004) to determine the purchasing group with a customer- specific logic.

This is for your additional information.

Hope this helps.

Regards,

Vikas