SRM 7.0 and SAP PI ( or SAP XI )

[Former Member]

Dear Gurus

since i'm going to work on an upgrade project from SAP SRM 4.0 to SRM 7.0 i'd like to have more clarifications about the following questions:

a) It is mandatory to have an SAP PI istance using SAP SRM 7.0. with the SELF SERVICE PROCUREMENT - CLASSIC SCENARIO

b) It is possibile to upgrade from 4.0 to 7.0 in only 1 step without the middle steps: from 4.0 to 5.0 and from 5.0 to 7.0?

Thanks a lot .

Luigi

[Former Member · Accepted solution]

Hello,

A: No it's not mandatory and hearing your scenario it wouldnt be needed either. Though do note that if you are planning to implement the Catalog Content Management scenario you might need it.

B: Yes it's possible. There is an upgrade guide saying exactly the same (that this is posible). You can find it at http://service.sap.com/srm-inst -> Here there should be an upgrade master guide but it's not there atm. Might be in re-working? But i know/remember that 3.0 needs to be upgraded 2-step but 4.0 does not need this.

Kind regards,

Tim

[Former Member]

Not mandatory -a) It is mandatory to have an SAP PI istance using SAP SRM 7.0. with the SELF SERVICE PROCUREMENT - CLASSIC SCENARIO

upon your business requirement - for example PDP with EHP4 in ECC and CCTR - you may definetly require XI.

you can visit service.sap.com/pim

product index matrix.

Muthu

[Former Member]

Hi Muthu,

I disagree we run an SAP SRM 7.0 and SAP ECC 6.0 EHP4 set-up and we can run everything without the use of PI/XI. In addition SAP promised additional non-pi/xi features for SRM EHP1. Also note that as of now with an ECC EHP4 back-end you can run the CCTR scenario in the preffered method using SOA this is without the use of any XI/PI.

Take a look at: Note 1263876 - SAP SRM: Configuration of Procure-to-Pay Scenario

For the MDM integration 'publish to catalog' you would (still) need XI/PI. Also note that with a non-ECC EHP4 back-end you would need XI/PI for CCTR and CCPR.

Kind regards,

Tim

[Former Member]

Hi Tim

I study i come back to you.

Muthu

[Former Member]

Muthu,

i am with you man...

I am on SRM7 eph 4 and PI is mandatory for central contracts.

1. Central contracts --> Contract in ECC (PI)

2. Central Contracts --> Sch Agr in ECC (IDOC)

The note 1263876 relates to CPPR not CCTR

Thanks

Netaji Gummadi

[Former Member]

Let me understand this:

So you are doing central contracts without PI? Can you confirm this.

Thanks

Netaji

[Former Member]

Hello,

Yes indeed i am. Im in the process of configuration but there for i know it's possible. I could provide additional notes/information.

Same applies to CPPR. You would need XI/PI with a lower then ECC 6.0 EHP4 back-end. If you have a ECC 6.0 EHP4 back-end you can go with SOA.

Ontopic: The Self Service Procurement scenario does not require XI/PI: nonsene to say it requires PI. Even without an ECC 6.0 EHP4 back-end PI would only be required for certain specific functions.

Kind regards,

Tim

Edited by: T. Schuffelen on May 14, 2010 7:44 PM

[Former Member]

Thanks Tim for the update.

Right now i am in the middle of realization and using PI for CCTR . Interested to see this work without PI, that would be great.

However i am having issues with Self service procurement. Cant send the SC to backend, looks like it is looking for PI could be a bug.

Will keep you updated. Thanks

[Former Member]

Hi TIm

I rephrase my answer,

In PDP -Plan driven procurement

PR to SC - XI -Required. now a days (SRM 700 with ECC 6.0 EHP4) we may not use Transfer Job to transfer PR to SC.

In CCTR

SRM Contract to ECC Contract XI required.earlier SAP used IDOC technology.

I might hastly writtem Self service procurement .You are correct.

I would appreciate if you give more on SOA technology and mechanism how contracts are distributed to backend system using SOA.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2055a6b4-2fb0-2c10-86a8-f1f92eabf...

Muthu

[Former Member]

HI All:

We are now live with SRM 7.0 SP2 on Classic Scenario with:

- SRM-MDM 3.0 (Netweaver 7.1)

- Self-Service Procurement

- Plan Driven Procurement

- PI is not in our scope.

So, to summarize the PI is not mandatory, but would be easier on PDP and SRM-MDM to have PI. On PDP the BBP_REQ_TRANSFER is still available and we did use this.

PLEASE make a note of this:

In the System Landscape configuration you can't define that your backend is ERP_4.0. You need to define it ERP_2.0 because of the following:

ERP_4.0 /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP

ERP_2.0 CL_BBP_BS_ADAPTER_PO_CRT_ERP10

Contracting is not in our scope so I can't talk about this part.

Just would like to share

Mike

Edited by: SRM 1025 on May 17, 2010 2:42 PM

[Former Member]

Thanks for the valuable inputs. i will re-study and come back to you.

muthu

[Former Member]

Hello,

I have a response from SAP that PI is mandate if the Backend landscape is maitained as ERP_4.0.

It was also mentioned that you should see a SAP Note soon with this info.

Thanks

[Former Member]

Hello Tim,

I can confirm with ERP_4.0 you need PI in classic to send a SC --> PO if item data complete

SAP:

I have checked this subject with other expert colleagues. It is true          

in the "Master Guide - SAP Supplier Relationship Management powered by        

SAP Document version: 1.2 . 03/12/2010 Material number: 50098575"

This not clearly specify the use of PI in case you are using an ECC 6.0       

EHP4.

2.8.3 Business Scenarios                                                      

-> 3.1 Self-Service Procurement (Classic /Extended Classic)                   

 -> 3.1.3 Technical System Landscape                                          

    3.1.4 Implementation Sequence

Install SAP Process Integration.           

===============================                                               

The use of SAP Process Integration is optional but it is required for         

outbound XML-based messaging or for connecting non-SAP planning or            

execution systems.

So,

As per SRM 7.0 system concept, if you are connecting the SRM 7.0 to an        

ECC EHP4 backend (it means ERP_4.0 system type in SRM) the driver             

used determines the communication with backend through XML for certain        

follow-on documents due to this reason it is presupposed the implicitly       

PI usage.     

Please refer to the SAP note 1286936 - PI configuration for SRM -       

additional info. You will notice the PI requirement for the             

Procurement Classic scenario.

You require the following recipient communication channels:             

 - SRM: PI recipient channel                                            

 - SUS: PI recipient channel                                            

 - ERP: PI recipient channel                                            

 - ERP: IDoc recipient channel                                          

Roles of the technical user in the SRM system:                          

 - SAP_XI_APPL_SERV_USER                                                

 - /SAPSRM/EMPLOYEE

I must inform in case of ECC EHP 4.0 the use of PI is mandatory.

However, on your on risk and keeping in mind that this is kind of a     

modification, you could change the backend sys-type in table            

BBP_BACKEND_DEST back to as i have mentioned before.

A further option would be to create an implementation in the BADI       

BBP_DRIVER_DETERMINE, to call a customer own driver during the transfer 

of documents to the backend.

Kindly get in touch with you local SAP Consulting team in order to            

consider these options.

Sorry if we are unable to provide a better answer than this one, but          

this is the system design.

P.s. I have suggested to include this information in a SAP note / config      

guides about SRM 7.0 x ECC 6.0 EHP4.  

[Former Member]

Hello Netaji,

An update: The CCTR scenario, although with EHP4 you need/should configure SOA calls via transaction SOAMANAGER, it seems that XI/PI for document exchange is still required. The SOA calls are used for search help purposes?, or atleast they do not cover the complete scenario as of now. SRM 7.0 EHP1 should however cover CCTR functionallity without the need of XI/PI. (due june 2010)

In respons and after looking into the ERP_2.0 / ERP_4.0 you discussed I have to conclude that they do not differ that much and i can't really understand why you/SAP were saying that XI/PI/XML is used as of setting the ERP_4.0 in the BBP_BACKEND_DEST table. I've looked into BBP_FUNCTION_MAP and the only differences are:

- BBP_SAPXML1_CTR_REPLICATION

- /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP

I've also changed and configured the ERP_4.0 setting and ran 4 scenario's and everything is replicated as it where with the ERP_2.0 setting (PO/Confirmation/Return delivery etc.)

Kind regards,

Tim

[Former Member]

Tim -

Interesting that you could run the scenarios with ERP_4 as backend definition. I am sure there is something else which is different in your system.

Is the backend business function activated for Central Contracts? Thanks

[Former Member]

Hi Nethaji

I dont was disturb your new thead ..

5. Customizing of conditions mapping

The logic of condition mapping between SRM central contracts and ERP replicated contracts is as follows:

First the system checks the conditions mapping as defined in Customizing.

If no mapping condition has been defined in Customizing the system checks whether an ERP condition with the same ID exists.

If no mapping condition has been defined in Customizing the SRM condition won't be replicated.

The conditions mapping between SRM central contract conditions and ERP replicated contract conditions can be customized here:

IMG -->Integration with Other mySAP.com Components --> Supplier Relationship Managment -->Central Contract -->Assignment of Conditions

--

9. Condition Groups in SRM

For Central contracts, the condition groups 01HD, 01CO and 0100 would be relavent for creating new contracts. For migrated contracts that existed aleady as GOA, the old condition groups 01CH, 01CP and 01CC would be supported but any fresh contract will use only the condition gruops 01HD, 01CO and 0100.

--

sap says abaove on CCTR

Muthu

[Former Member]

Hi Tim,

We have in the situation, Does PI required to implement the below scenario.

We have SRM 7.0 and ECC 6.0 EHP 4.0.

1. External Requirement from ECC, Transfer all the PR to SRM for sourcing and central contracts.

2. Central contracts in SRM and distributed to ECC for creating Release Order in ECC.

Above both scenario are possible implement without XI. Because all the configuration guides suggest PI/XI.

[Former Member]

Hi Tim,

We have in the situation, Does PI required to implement the below scenario.

We have SRM 7.0 and ECC 6.0 EHP 4.0.

1. External Requirement from ECC, Transfer all the PR to SRM for sourcing and central contracts.

2. Central contracts in SRM and distributed to ECC for creating Release Order in ECC.

Above both scenario are possible implement without XI. Because all the configuration guides suggest PI/XI.

[Former Member]

1. External Requirement from ECC, Transfer all the PR to SRM for sourcing and central contracts.

--You can still use old transfer program without PI/XI for PDP scenario same as in SRM50. But with this you cannot transfer PRs with service hierarchies. We did this in one of my SRM70 project. It works fine. But later we moved to PI/XI for service hierarchies functionality and for CPPR functionality.

--Without XI/PI you cannot use the CPPR functionality to transfer PR to SRM sourcing from Portal using Harmonized purchaser role. for this you need to set up XI/PI.

2. Central contracts in SRM and distributed to ECC for creating Release Order in ECC.

--For Central contract distribution PI/XI is must only when you distribute contracts to the backend suste. If you just create a central contract in SRM and do not distribute to backend system then you do not need XI/PI. But if you want to distribute this central contract to backend system as a Purchase contract then XI/PI is must. Once you create PO release against this contract in ECC that will be updated back to central contra ct in SRM via XI/PI.

--But you can distribute Scheduling agreement to backend through IDocs same as in earlier versions. For this PI/XI is not required.

--Central contract is just Outline agreements same as in older versions of SRM. If you distribute it to backend then you can use it as a source of supply in both systems (ECC and SRM). SRM only send part of contract data instead of entire central contract to backend system. So record of system will be SRM for Central contract. If you dont ditribute then you can use it only in SRM sourcing in ECS.

Thanks,

Jagadish

[Former Member]

Hi

How do you transfer PR from ECC to SRM using XI . What transaction you execute in ECC

Jigar