cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Business Function Activation Required in SRM7.0

Former Member
0 Likes
497

Before (As Is): My client is running in SRM 5.0 (Classic Scenario) at present .

Present System: Client have provided us with upgraded development system SRM7.0 from SRM 5.0 recently.

Our To Be proposal:

We are in the business blueprint stage and as per the client scope and requirement we have proposed them for implementing "Extended Classic Scenario" in SRM7.0 system.We are also going for ESOA activation.

My Query for You:

I hope we need to activate the below mentioned business function in SRM7.0 .

Business Function Names: LOG_MM_P2PSE_1

Prior to this we need to activate few more business functions in SRM client and ECC client like:

1:ESOA_OPS01

2:LOG_MM_CI_2

3:LOG_ESOA_OPS_2

Please correct me , if I am in the right approach.What precautions needs to be taken while activating this BS.

Br's

Sushovan Mohapatra

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Likes

Hi Netahaji Gummadi

Note 1268336 - Synchronous peer-to peer Services Configuration

Note 1270081 - Trouble shooting SOA Services

Note 1286936 - PI configuration for SRM - additional information

Note 1109131 - SRM Service Enablement 6.0 Add-On; Release and Information

can you share your thoughts here?

Muthu

Former Member
0 Likes

Sushovan,

If you are going with eSOA technology with ECS then you need to activate business function LOG_MM_P2PSE_1 in ECC. There are some dependant business functions like "ERP Enterprisesearch..." which you need to activate them too. Anyway system will populate these dependant ones while you activate main one.

Along with this you need to set up service calls in XI in order to transfer docs using eSOA as below:

1. If you are using ECS then no service calls are required to set up in XI. It will be same as in SRM5.0

2.If you are using PDP using eSOA then set up service calls for "PurchaseRequest..." in XI and also activate Event linkages in ECC. If you do not want to use eSOA then you can still continue with old report in SRM50 to transfer PRs to SRM, but in that case you cannot use the new functionality CPPR in SRM using Harmonized buyer. To get this functionaliuty you have to go with eSOA.

3. If you want to use Central Contract functionality then you need to set up service calls for CentralContract..." in XI as Central contract only works with eSOA in SRM70.

Go through the config documentation for all above set up.

Thanks,

Jagadish

Former Member
0 Likes

Hey Sushovan,

You dont need to activate any eSOA function For configuring Extended Classic Scenario. All you need is configure the NUmber ranges for Local POs in SRM and Activate Extended Classic Scenario for activating this. If the conditions for Extended Classic Scenario determination are complex, then go for Extended Classic BADI.

the Scenarios you ve menttioned are activated in ECC for Service Procurement, CPPR (eSOA), which will anyway be a Classic Scenario as SRM handle Service Procurement(eSOA) , Plan Driven Procurement as Classic Scenarios

Refer to Business Scenario COnfig Guides ofr step by step details

Regards

Virender Sing

Former Member
0 Likes

Hi

ESOA is not really required in configuring Extended classic scenario.....

If you want to know about ESOA options in SRM, then go through the config guides of following scenario

1. Plan driven procurement

2. Sourcing

3. Service Procurement

These guides can be found at https://websmp204.sap-ag.de/srm-inst

Regards

Virender Sing

masa_139
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi,

Configuration Guides tells you which Business Functions should be activated.

Please check Configuration Guides in SAP Solution Manager or downloaded offline version in SAP Service Marketplace.

http://service.sap.com/srm-inst

Regards,

Masa

Former Member
0 Likes

Yes in this case I will go with masa.. The only additional information I can give here is to start with Basic Settings for SAP SRM 7.0..

Thanks!!

Bharath

Former Member
0 Likes

Note 1263876 - SAP SRM: Configuration of Procure-to-Pay Scenario - here you might get step by step

- here some useful link by mathew

Note 1478177 - Termination CX_BADI_NOT_IMPLEMENTED for MB_DOCUMENT_BADI

SAP has to take some initiaives to write a blog /wiki for new version SRM 700 vs EHP4 business function activation

to enjoy eay configurationon CPRR and CTRR etc..

here there is indeed big fight between Functional consulatant and BASIS.

basis ask functional guy what are the function needs to be implemented.

it indeed help others to do quick implementation. otherwise to understand all these things takes lot of time.

muthu