ERP release for Central Contract Management with SRM 7.0 EhP 1

Hi all,
i would like to have clarification with ERP and SRM release combinations regarding SRM 7.0 EhP1.
Indeed, the "Software Component Matrix for SAP SRM 7.0 EHP1", for Operational Contract Management, tells 'EHP 5 for SAP ERP 6.0 required'.
Moreover, in RKT dealing with SRM EhP1 delta overview, ERP 6.0 with EhP5 is mandatory for an upgrade to SRM7.01.
Nevertheless, i would like to have confirmation regarding this point.
We do not want to use PI to execute the Enterprise Services for CCM. So, we intend to switch BF SRM_WSRM_1 on.
But on the ERP side (EhP5), the only BF dealing with Contract Management is LOG_MM_P2PSE_2 which description is about Service Procurement (and more exactly for item hierarchies).
Does it mean we can use SRM 7.01 with ERP 6.0 EhP4 and without PI but only if we do not use Central Contracts with service hierarchies ?
Thank you for your help.
Regards.
Laurent.

Hi Laurent,
Yes.
When Central contract was designed in SRM 7.0 with ERP EhP4, it was designed with no service hierarchy. But in SRM 7.01 Central contral was enhanced to handle service hierarchy and it works with ERP EhP5. The problem is when we have SRM 7.01 and ERP EhP4. To handle this complication SRM 7.01 was designed to send flat service lines to EhP4 and lower release even though Central contract in SRM has service hierarchy. So while transfering to ERP EhP4 system in standard, all outlines are not consider for transfer and only service lines (Functional items) are transferred to ERP. To do so user needs to maintain the backend destination information of the connected backend system in table BBP_BACKEND_DEST via SM30 transaction with correct system type (for EhP4 system it will be ERP_4.0 and for EhP5 ERP_5.0). SAP Standard program checks this while XML generation for transfer and if system type is ERP_4.0 system it removes all outlines from temp table before generating the XML data. When it is done, ERP has only service lines in its XML and it does the manupulation to create the replication of central contract.
Master Guide (Including Upgrade Information) - SAP SRM 7.01 states:
"The use of SAP NetWeaver PI is optional but it is required for outbound XML-based messaging or for connecting non-SAP planning or execution systems."
So service hierarchy is possible in SRM 7.01 and ECC 6.04 but only with PI. For other CCM functionalities, SRM 7.01 and ECC 6.04 without PI works fine.
Best regards,
Christian Zeuch

Similar Messages

SRM, MDM, ECC integration for central contract management.

Hi there,
I am questioned by a client with respect to the possibility of the following scenario -
1. There are several SAP back end systems in place.
2. SRM 7.0 will be implemented as single sourcing system.
3. The SAP back end systems carry different material master codes for the same material and this will remain the same and no cleaning effort to have a unique code across all systems is going to be done.
4. If we use MDM in the mix - will it be possible for the SRM system to act as a central contracting solution and create a central contract with the unique material code in MDM.
5. On distribution of this contract across to individual SAP back end system the back end should map the MDM code to correct material code in that respective system.
Any insights with respect to if this is possible with some enhancements or not at all possible will be highly appreciated.
Thanks and Regards,
Shantanu Joshi

Hello Shantanu Joshi
Your business scenario is standart MDM functionality
More about how it works you can read from:
MDM overview
and standart help links (see scenarios part):
http://help.sap.com/saphelp_mdm550/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm
http://help.sap.com/saphelp_nwmdm71/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm
Regards
Kanstantsin

SRM -- MDM -- ECC integration for central contract management for SRM 7.0

Hi there,
I am questioned by a client with respect to the possibility of the following scenario -
1. There are several SAP back end systems in place.
2. SRM 7.0 will be implemented as single sourcing system.
3. The SAP back end systems carry different material master codes for the same material and this will remain the same and no cleaning effort to have a unique code across all systems is going to be done.
4. If we use MDM in the mix - will it be possible for the SRM system to act as a central contracting solution and create a central contract with the unique material code in MDM.
5. On distribution of this contract across to individual SAP back end system the back end should map the MDM code to correct material code in that respective system.
Any insights with respect to if this is possible with some enhancements or not at all possible will be highly appreciated.
Thanks and Regards,
Shantanu Joshi

Hello Shantanu Joshi
Your business scenario is standart MDM functionality
More about how it works you can read from:
MDM overview
and standart help links (see scenarios part):
http://help.sap.com/saphelp_mdm550/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm
http://help.sap.com/saphelp_nwmdm71/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm
Regards
Kanstantsin

SRM Central Contract Management with Service Hierarchy

Hello Gurus !
Is it possible to use the export/import functionality (with the business function SRM_CONT_IMPR_2) for changing/adding the service hierarchies in SRM Central Contract? I see the SAP note that the hierarchies are not supported for Purchase Order.
Any idea?
Thanks in advance
Regards
Raj

Hi Raj,
it's not supported for contracts either.
Regards,
Zsofi

Badis for Central Contract Replication from SRM to ECC

hi
experts
i am working on a scenario of replicating the central contract from SRM 0.7 to ECC via XI/PI
let me know what are the Badis to be implemented in ECC for the Same
looking forward for your reply

Hi,
You do not need any Badi in ECC to distribute central contract to your backend system.
if your ECC system is on ECC 6.0 enpk 4.0 or more,
you can directly distribute your central contract from SRM to ECC system using standard ESOA services.
Thanks and regards,
Ranjan

Central Contract Management in case of Classic Scenario

Hi,
At our current implementation, requirement is to implement both Service procurement(with hierarchy) and Central Conract Management. I was exploring the possibility of utilizing Central Contract Management with Classic scenario.
Will the Central Contracts created in this fashion be available in Sourcing Cockpit for the buyer to select against Purchase Requisitions? Will the Central Contract be visible at all in SRM in this case ?
Please respond only with reference to Classic scenario.
Thanks,
Abhilash

Yes the Central Contract will be available in the Sourcing Cockpit, both local and classic scenario's. Yes the Central Contracts will be available for the creation of Purchase Requisitions in R/3 and to assign SOS in R/3.
Do know that for SRM 7.0 PI is required for setting up Central Contracts. This is promised to change with the release of EHP1 for SRM (due june 2010).
Kind regards,
Tim

Setup Central Contract Management SRM 7.01 with differing release versions

Hello experts,
OSS note 1268821 explains how to configure the central contract management between a SRM 7.0 and an ERP 6.04. So far so good, but how should it be handled if there are differing release versions such as ERP 6.04 and ERP 6.03? I guess that a technical split (xml services/ ALE distribution) is necessary?
Assuming that there are some backends with differing release versions and in some cases with differing master data (not supported by central master data client) would you always go via PI? Independent of release version, technology and master data.
Could you give some further detailed informations how to configure such a scenario? What has to be done to transfer existing contracts from an ERP 6.04 into SRM CM component (migration concept)?
Thanks!!!
KR Thorsten

Hi Thorsten
The minimal ECC version is 6.0 EHP4, Central Contracts require certain business functions in ECC to be activated and as these are included within ECC EHP4 you won't have these available in lower version. Therefore you won't be able to operate central contracts in such an ECC system.
You would either have to go with patching these systems or go with GOA's for these systems.
Operating central contracts via PI or SOA i believe provide almost similar functionality. SOA however requires an SRM EHP1 system and ECC EHP5 back-end to operate whilst central contracts configured via PI can be operated onwards from an SRM 7.0 and EHP4 system.
I can't help you on your migration issue, maybe someone else can.
Kind regards,
Tim

SRM 7.0 / ERP 6.04: Config. of Central Contract Management

Hello,
I want to configure the newly introduced integrated Procure-to-Pay Scenario Central Contract Management.
I found SAP Note number 1268821 where all tasks are described in order to implement the previous scenario.
For correct implementation, business function "Purchasing - SAP SRM Integration" (LOG_MM_P2PSE_1) activation is required in the ERP Systems.
When I run SFW5 t-code in order to activate the previous business function, SAP system gives an alert message.
What are the consequences of this business function activation ??
Thank you
Michele

Hi Michele,
I don't think there will be any consequences, we had certain warning messages aswell when we activated the business functions in ECC 6. Reading the warning messages we could conclude it wasn't any serious problem.
Details on functionalities included in a business function can be viewed here: [http://help.sap.com/erp2005_ehp_04_sp/helpdata/en/42/fbded750e61febe10000000a422035/frameset.htm] -> Business Functions (SAP Enhancement Package 4 for SAP ERP 6.0) -> Business Functions in SAP ERP -> Logistics -> Materials Management -> Procurement - SRM Integration
Kind regards,
Tim

Central contract functionality in SRM 7.0?

Dear Experts,
I would like to have few clarifications about central contract functionality in SRM 7.0.
As per understanding, from SRM 7.0, there is no two separate documents like local contract and GOA (global outline agreement--contract for backend ERP systems). Now, SRM have only one document -Central contract to be used in sourcing for various backend systems as well as the SRM system itself.
Now, my question is as below:
Since the central contract is released into various backend ERP systems, do the backend requisitions needed to be transferred to SRM system to use the central contract as a source of supply . or the backend requisitions can be assigned to the central contract in the ERP system systems itself (without sending it to SRM system ) and released to suppliers?
Your inputs will be highly appreciated.
Thanks and regards,
Ranjan

Hi,
From ERP 6.0 EhP4, ERP transactions can look at SRM central contracts.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/52/43df4725704c6393a49a4d671e0f59/frameset.htm
Regards,
Masa

Central Contract Management

Dear SAP Experts,
I have a few questions regarding our implementation of SRM and ECC.
FYI, we are planning to use SRM 7.01 and ECC 6.05 as backend.
We’re planning to utilize Central Contract Management functionality in SRM, where we negotiate the price in SRM then we distribute the contract to ECC. In ECC we create PR, which have reference to this contract (contract number in SRM is different with ECC). So this PR will have assigned source of supply, is it possible for us then to create PO automatically from tcode ME59? The reason we ask this because we see in documentation that every PO in ECC created with reference to contact in SRM, ECC will need to check first the current price in the SRM contract, so we would like to confirm whether it is working if we use ME59 (we plan to use ME59 as background job and unfortunately we don’t have the testing system yet to verify this).
We’re planning to have PR created in ECC. However we would like to utilize MDM catalog as well. Is it possible that during PR creation we can select items from the catalog?
We’re planning to have implement SRM 7.01 in 2 waves. In first wave we will only use Self Service Procurement and Strategic Sourcing (using classic deployment where the leading PO is in ECC). However in the second wave, we’re planning to implement SUS (Supplier Collaboration). In SUS, we would like to activate the business function, so the vendor will response RFx and participate in auction from SUS itself. The question is…is it possible for us to have it planned like this? For example, in first wave, the RFx and auction will use SRM server itself, however in the second wave, we will switch it to SUS. Our concern is that the switch will happen to the productive server already. Is this okay?
Thanks
Varian

Hi,
When you distribute the central contract to ECC system, it creates a new contract in ECC system.
When you create PR, you can assign this contract as source of supply.
Then automatic PO creation if your settings for automatic PO is maintained.
In ECC 6.04 also catalog integration is possible. So for your version 6.05 there is absolutely no problem. The same OCI interface parameters have to be maintained in MM system for catalog.
Your two stage implementation is absolutely possible.
With Regards,
Malay

Looking for a file manager with copy queue

Hey,
I'm looking for a file manager with a file-copy-queue feature.
It is useful when browsing mounted samba shares, and you find something you want to copy.
You'll then start copying the files, and then spot another useful folder. You start copying that as well
and suddenly you got 5 different file copies processing at the same time, which decreases the copy speed.
I also miss the feature when transfering files from my external harddrives.
If there is a lot of FM's with this feature, I prefer one without kde-dependencies, as I am using xfce.

Ranguvar wrote:If MC really does have that as a feature, it's once again proved itself _the_ graphical (sorta) file manager.
sorry for misinformed.
mc has a background job option while copying, it is not exactly a queue like functionality, but simulating to be a queue, and you can stop/resume a background job.

Help with Infomaker tool for editing Contract Manager Template

I am new to Primavera Contract Manager (11i) and has been assigned with a task of editing one Submittals template on the system as the person who was handling it left the company.
On doing some research I found out that it is done through the Infomaker tool and I was able to do so the test server.
But on the live server, whenever I try to open the same template using Infomaker, it will ask to select the database, once we select the database which is Oracle 10 G express, it quits even without showing any error message.
I tried creating a new user on Oracle to make sure it is not because of wrong user name and password, but what ever details we give, infomaker just quits when tried to connect to any database.
Can you kindly help me to trace out the issue?

Hi Suhas,
The rule used in workflow template WS50100021 is a standard one. So try to find out that on what basis it is fetching the agents. It could be the case that the logic specified in the rule does not fulfill your requirement.
The other reason could be that you have not specified the task as general. Please check if the agents tab is activated(green) in the task or not. If it is not you need to set the task as general.
SOLUTION : if you want to get the workitem in your own SAP Inbox for testing purpose, you can set the WFINITIATOR as agent instead of that standard rule. This setting will send the workitem in your own SAP Inbox.
Regards,
Guddan

Release of central contracts

In SRM a central contract was created and then distributed to SAP ERP ECC 6.0 Backend.
In backend system a release strategy exists for the distributed contract.
When trying to release this contract with ME35K the contract will not be found.
Checking the table EKKO the contract is there and the release strategy is correct.
Debugging transaction ME35K we found that the following statement deletes the distributed contract.
*- Check for EhP4-Switch and Central Contract
IF cl_ops_switch_check=>mm_sfws_p2pse( ) = 'X'.
DELETE xekko WHERE bstyp EQ 'K'
AND statu EQ 'K'.
The question is if there is a switch which needs to be activated or deactivated that the contract can be released by ME35K?
The switch should be: MM_SFWS_P2PSE
Or is it SAP standard that distributed central contracts cannot be released in ERP backend with ME35K?
Thanks in advance.

If you're reference the PO to a PR, than you can remove the assingment of the Contract document type to the PR document type, so the users wont be able to create the PO with reference to the Contract with the specific doc type.
SPRO->Materials ManagementPurchasingContract--Define Document Types --> Link purchase requisition - document type

Central contract information from SRM to ECC

Hi everybody,
I´m working with an integrated landscape (SRM 7 with ECC 6), and i´m configuring the central contract, but i have a doubt about the information that is sent from SRM to ECC (the leading system about the contract is SRM). The contract description written in SRM is sent to the contract created in MM?????
Thanks for all.

Hi, do you mean the texts in contract item ?
This text transfer functionality was delievered in SRM 7.0 and it was linked to ERP 6.0 EHP4.
For contracts overview, please check link: http://help.sap.com/saphelp_srm50/helpdata/en/43/05c0c685da6e72e10000000a422035/frameset.htm
Regards
Lauren

WSRM setup for Central Contract

Hi,
We want to setup SRM 7 Ehp1 system without using PI. For this WSRM setup is required for exchange of documents between SRM and ECC. I am referring to the configuration guides in service market place and OSS note # 1043195. But there are couple of settings which are not clear. Has someone worked on this before and can guide me?
Thanks,
SKN
Edited by: SKN on Jul 29, 2011 2:49 PM
Is PI independent communication using WSRM available from ECC 6 Ehp5 onwards and not in ECC 6 Ehp4?

Hi,
You do not need any Badi in ECC to distribute central contract to your backend system.
if your ECC system is on ECC 6.0 enpk 4.0 or more,
you can directly distribute your central contract from SRM to ECC system using standard ESOA services.
Thanks and regards,
Ranjan

ERP release for Central Contract Management with SRM 7.0 EhP 1

Similar Messages

Maybe you are looking for