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

Similar Messages

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

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

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

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

Can anybody explain how to configure the Centralized contract in SRM 7

Hi All,
Can anybody explain how to configure the Centralized contract management in SRM 7 with ECC EHP4 ?what are all that need to be perform in PI system.
Thank you,
praveen

Hello,
PI will be required here. You can also refer the config guides maintained at the belwo mentioned location.
Goto URL http://service.sap.com/srm-inst and then navigate to SAP SRM --> SAP SRM Server 7.0 -> Configuration Guides for SAP SRM 7.0
Best Regards,
Rahul

Benefits of implementing Central Contracts in SRM 7.

Dear Experts,
Picture the following:
- Classic Scenario.
- One ECC 6 EHP 4 Back end.
I'm currently exploring the benefits of implementing Central Contracts against using only Purchasing Contracts in ECC and replicating them to SRM for use in the Shopping Carts.
So my question is why would you implement central contracts in SRM instead of just replicating these contracts from ECC? What benefits would you get out of having central contracts in place against having only Purchasing Contracts in ECC?
Thanks for your input.

adding to Manju one point .
- Procurement department(PURCHASER) can use web interface to create / manage contracts rather GUI interface and quick contract creation / maintenance
- Approval mechanism simplified with less efforts.
- Different ways to create a contract from SRM
Copy an existing contract
Use an existing template
Upload an external file
Upload a contract from the catalog
Muthuraman
1.You can use this business process to access SAP SRM contract features, such as contract hierarchies, discount across contract hierarchies, and grouping logic, when determining source of supply in SAP ERP.
2.You can create a central contract in SAP SRM, and it can then be used as source of supply in both SAP SRM and SAP ERP. Relevant data is sent to SAP ERP for a source of supply determination, and a specific type of contract or scheduling agreement can be created there.
3.While determining a source of supply, you can access central contracts directly.
4.The price is determined in SAP SRM before the SAP ERP purchase order (PO) is sent to the supplier.
5.You can create and change central contracts and renegotiate existing contracts directly with a supplier, or through the creation of an RFx. You can automatically assign a contract as a source of supply, or it can be listed as one of numerous potential source of supply contracts. A strategic purchaser can create a contract whenever they anticipate a long-term relationship with a supplier.
6.Contract management enables purchasers from various parts of the company at different locations to take advantage of the terms of globally-negotiated contracts for specific product categories. You can provide users with specific levels of authorization to contracts, and you can categorize documents as confidential.
6.You can distribute central contracts to release-authorized purchasing organizations, and these organizations can then use them as source of supply in the appropriate SAP ERP system. Hierarchies can be used to organize, structure, display, and search for contracts.
7.If you use SAP NetWeaver Business Intelligence (SAP BI), you can view various consolidated reports of contract management. For example, you can view aggregated value released against all contracts in a contract hierarchy.

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 7.0 Central Contracts Excel upload

Hello All,
We are implementing SRM7.0 implementing Central Contracts ,want to use the Contract upload function using the excel file , not able to see the button or link to do the same .
Am i missing something.
Pl. help.
Cheers,
Sid

Hello Jay,
I would like to import central contract to SRM 7.0 via excel file. When I click the import button after edit functionality and choose the file path from the computer and push the upload, button, I got an error message saying File type of specified file C:\Users\Administrator\Desktop\Contract.xls not supported . Therefore, the excel file cannot be imported to the SRM system. When I also try to import tablimited format of .txt files, I got same error message and unfortunately I cannot achieve central contracts to be imported. How can I solve this issue? Should I check some customizing settings or something?
Many thanks for your guidence,
Mehmet Gullu

Distributing Central Contract from SRM to ECC

Hi,
We are using SRM 7.0 with ECC 6.0 in backend (no EHP). We're setting up a central contract with IDOCs. From what I read we have made the configuration:
in SRM:
- Assign attribute CT_PROC_TY = CCTR
- Connfigure new condition type PB00 which is the same with ECC price for contract
- activate the BADI BBP_DETERMINE_LOGSYS and coding it so for contract it will always go to backend (in method CONTRACT_LOGSYS_DETERMINE)
- I have activated BADI BBP_CTR_BE_CREATE but writing no code, as there no need for me to do mapping
in ECC:
- Activate inbound IDOC type BLAORD and COND_A and assign it to the logical system of SRM
Then I create the contract in SRM. but:
1. When creating contract, in item overview, i cannot tick 'distribution' indicator. Not sure what is the function
2. In item detail, tab distribution, I cannot put create release-purchasing org. Even when using search help it is not giving any value
Actually dont really understand the usefull of the indicator above, so I let it be empty, then I release the contract
The contract then not appear in ECC. I have checked SMQ1/SMQ2 nothing. Even in WE05 in ECC nothing. The only thing I see is in SLG1 where I see error triggered by user WF-BATCH with message "No recipient found"
Do i miss something in here? Any help will be very appreciated.
Josh

Hi Josh,
Central contract is only possible in SRM 7.0 with ECC 6.0 EHP 4. You can use local contracts or GOA.
Regards.

SRM 7.0 EhP 1 central contracts with service lines

Hi,
I have a question concerning the use of SRM 7.0 EhP1 central contracts with service line items. I know that for SRM EhP 1 you would require EhP 5 in ECC. However, since my organisation just went to EhP 4 last weekend I am wondering if there's any option to use services in central contracts without going to EhP 5 in ECC.
Kind regards,
Bastiaan

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

SRM 7.01 Central Contract: Email Notification when contract is distributed

Dear all,
I lwould like to know if it exists a standard functionality for distribution notification and how it is customizable.
The scenario:
I create my central contract in SRM and i would like to be able to send email alert to the back end user (Local Contract Manager for example) when the contract has been distributed correctly. Does the user need to be is the SRM Organisational Structure?
Can i use the event schema like expiring contract notifications?
Thank you for your help.
Best Regards,
Jennifer

The first interface that try to get out from SRM was " PurchasingContractERPRequest_Out_V1", thus based on this interface we made the configuration on PI. So, after pressing button " create contract" on srm if we execute tx SXI_MONITOR in SRM we found the interface " PurchasingContractERPRequest_Out_V1" and in the backend system ( ECC) at tv SXI_MONITOR we found interface PurchasingContractERPRequest_In_V1 for this contract with black and white flag ( processed successfully) but no contract created in ECC not even SRM.
Anyway we have checked that inbound proxy is executed but we dont see any contract created
Is this the right Interface? We are missing something?
Best regads and thanks again for your help!

SRM 7.0 Central Contract-For Centralized Purchasing Scenario

Hello Experts
Is it possible to set up a corporate (read Centralized) Purchasing strategy, where in One Central purchasing organization creates and manages Central contracts for various Plants assigned to different company codes using SRM 7.0 with ECC Backend?
Tried to set this scenario up by assigning Purchase organization directly to Plants (in ECC) but the Contracts were failing during replication in ECC.
Any inputs on this are appreciated.
Thanks
Raman.
Note: Contracts went through successfully in ECC after assigning the Purchasing organization to Company code.

Hi,
Please check this.
SPRO -> Enterprise structure -> Assignment ->
Logistics - General -> Assign Plant to company code.
Assign plant to company code
In the IMG activity "Assignment Plant - Company Code" you assign each plant to a company code.
A plant can only belong to one company code.
Note
Complete functionality of the system can only be ensured if the plants assigned to a company code are only those situated in the same country as the company code.
It is therefore recommended that you also create a company code for each country in which a plant is situated.
Examples
Only then are tax postings created when transferring stock between plants in different countries.
The taxation procedure and Intrastat declaration are supported only for the country of the company code.
Requirements
Before you can assign plants to company codes, you must define the valuation control.
You may change the valuation control in the production system only after contacting your SAP consultant. Changes may cause inconsistencies in documents.
Actions
Assign your plants to company codes.
Regards,
Masa

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 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

Central contract functionality in SRM 7.0?

Similar Messages

Maybe you are looking for