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

Similar Messages

  • 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

  • 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

  • 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

  • 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

  • Central Contract, MDM Catalog, and classic scenario

    Dear SAP experts,
    We are in SRM 7.01 with backend ECC 6.05 deploying classic scenario. We are using Central Contract Management in which we negotiate contract in SRM and later distribute it to ECC. We also plan to use SRM-MDM Catalog.
    We notice that if we are using classic scenaro, the contract that is used as reference is the contract number in ECC (the one distributed from SRM). So at first we assume that if we want to push the contract data to MDM, we should have pushed the ECC Contract number. However we find out that actually SAP block the ECC Contract coming as distribution from SRM to go to MDM.
    Our second option is to use distribution of contract from SRM to catalog. It does using SRM contract number. We create SC and then we pull the catalog item from the catalog (which contain SRM contract number) and then we order. However we end up with 'error in process' in which the system try to create a PR instead in the ECC (meaning that the contract number cannot be read).
    We're puzzled with this. How can we use the combination of central contract, MDM catalog and classic scenario? Can we use the combination?
    Best regards,
    John

    Maria
    If you want the contracts to be in SRM and do not want them to send to Backend, then check this out.
    Create a Vendor list for those items in SRM by assigning the local contracts to the vendors.Activate Vendor list for sourcing.
    Then local contract data should pick as SOS from the vendor list.
    If you can create contracts in Backend for stock material then SC would pick the backend contract as SOS in classic scenario.
    Let me know if the above works or not.
    PS : Reward points if helpful.
    Regards
    Jagadish

  • SRM 7 - Centralised Contract Management SAP XI inbound/outbound interfaces

    Hi there,
    We are busy implementing SRM 7 and I would like to get "centralised contract management" working between SRM 7 and the ECC backend/s (via SAP PI).
    Could you please let me know what the correct SAP PI CONTENT to load is? And what the correct service interfaces I need to use for this scenario as well as what "software component version" and "namespace" I can find them in?
    Any guide on the details of this specific scenario?
    Thanks for the help, much appreciated
    Lynton

    Note 1268821 - SRM 7.0 / ERP 6.04: Config. of Central Contract Management
    Settings in PI
    =================
    For CCM scenario to work, PI set up is required for the following asynchronous enterprise services.
    (Namespace; Software Component Version; Interface:)
    http://sap.com/xi/SRM/SE/Global; SRM SERVER 7.0; PurchasingContractSRMReplicationRequest_Out
    http://sap.com/xi/APPL/Global2; SAP APPL 6.04; PurchasingContractSRMReplicationRequest_In
    http://sap.com/xi/APPL/Global2; SAP APPL 6.04; PurchasingContractSRMReplicationConfirmation_Out
    http://sap.com/xi/SRM/SE/Global; SRM SERVER 7.0; PurchasingContractSRMReplicationConfirmation_In
    http://sap.com/xi/APPL/Global2; SAP APPL 6.04; PurchaseOrderERPContractReleaseNotification_Out
    http://sap.com/xi/SRM/SE/Global; SRM SERVER 7.0; PurchaseOrderERPContractReleaseNotification_In
    Settings in SAP Enterprise Portal
    =================
    Please refer to paragraph Settings in the Enterprise Portal in note 1263876.
    Notes to be implemented
    =================
    Notes 1262480, 1252865, 1263470, 1260829

  • Configurations needed for distributing central contract to backend system

    Dear Gurus,
    I have configured central contract and getting approved in the local SRM system. Now, I need to distribute the central contract to the backend system. I have already get the PI interfaces configured using the integration scenario Central contract management.
    Now, I assign the backend POrg as well as the target values for the backend contract and try to release the central contract. The central contract is getting released. However, no contract is getting created in the backend system.
    I donot see any XML messages generated in the SRM system (SXMB_MONI).
    Do I need to maintain some settings in the SRM system to enable the distribution of contract to the backend system?
    Thansk and regards,
    Ranjan

    Hi,
    When one creates Local Contract; there is one option named 'Distribute' on contract screen.On drop down; one mention back end system. After clicking on it; contract has been created in ECC.
    If contract is not getting generated in back end; refer SAP Note: 609222.
    Check whether you find any error/information message in Txn BBP_CTR_MON.
    SRM Settings:
    1. Implement BBP_DETERMINE_LOGSYS: Determines whether contract is to be created in SRM or ECC.
    2. Assign transaction type to attribute CT_PROC_TY in Org Structure.
    3. Check whether have maintained message type BLAREL, COND_A, BLAORD.
    4. Assign role SAP_BBP_STAL_START_PURCHASER to process contracts.
    Helpful SAP Notes: 641919, 646903
    Regards,
    yaniVy
    reward if helps

  • Central Contract Release Orders

    Hi,
    I've done all the necessary steps for central contract management and my contracts are distributing successfully to ERP.
    This is contract is used in both SRM and ERP as a source of supply.
    But my issues is, when i create contract release order in SRM for the contract i've distibuted to ERP it doesn't update the contract in ERP with the contract release order create in SRM. Or if a Contract release order is created in ERP it does update SRM.
    What BADI or a program i can use to achieve update contract both ways? Or is it a standard functionality not to update the contract in both system?
    Regards,
    Gigies

    I am not sure as I have to test this in system but i found this some where which needs to be checked.
    Section 3: Default Transaction Types
    If there are multiple transaction types determined, then the default entry in the transaction type dropdown box is set to 'space'. If there is only one entry found for the user then this will be displayed as the default entry in the dropdown box. Here is the code section where it happens: /SAPSRM/CL_CH_WD_DOM_SOCO_GAF3, /SAPSRM/IF_CLL_MAPPER~REFRESH:

  • SRM 701 - Central Contract via XI, no backend ECC contract created

    Hi All,
    We are trying to implement the SRM Central Contract Management scenario in SRM701 and ECC 604 using XI/PI and we are finding that the XML message is getting generated OK, passed through XI/PI OK and is successfully processed in ECC, however, no backend contract is created.  The SRM number range against the ECC contract document is incrementing every time we send a message but no data is getting committed to the tables.  I have seen a few threads on here with others having experienced a similar problem, however, I can't anywhere see what the resolution was.
    We are pretty sure all the config is correct as we have tried changing the entry in BBP_BACKEND_DEST for SYS_TYPE to ERP_2.0 and passed the data successfully via RFC and IDOC, but we are not having any success when the SYS_TYPE is ERP_4.0 and using XI.
    Please can anyone out there help?!
    Thanks a lot...

    Hi prashant
    I never tried service . but you can see this below symptom for you.I extensively worked on Material contracts.
    Are you creating contract from Process contract or Via RFQ
    Note 1272305 - Total value wrongly calculated in Contract Service lines
    Symptom
    We create a Service contract in the R/3 Backend from RFQ. During the transfer we calculate the gross price based on the quantity,price and price unit. (ie) The field ESLL-BRTWR is filled with following formula in the idoc processing. ls_e1edc20-BRTWR
              = ( is_item-price * is_item-quantity ) / is_item-price_unit.
    AS total value of the service lines is calculated based on the field NETWR which is passed as blank from SRM, during recalculation total value when we change the gross price of one of the service lines in r/3, it is required to fill this field
    till PI values are brought correctly till posting to ECC. ?
    Note 1123292 - Net Price wrongly calculated in plug-in MAP_BLAORD_SERVICES
    my experience in GOA
    Note:-
    2 set stream of DATA comes from SRM as BLOARD and COND_A ..
    Even some times when we reprocess failed IDOCS in BD87 in ECC ( comes contract data from SRM as GOA and failed due to some data validation in ECC). now data issue was fixed at Material master level. and
    if we forget to reprocess COND_A - BLOARD creates a successfull GOA but net price shows as ZERO for each material and when you post the COND_A data and correct price will be updated in ECC contract. so kindly check price data reaches or not not or price calculation failed in ECC.
    Muthu

  • SRM - Contract management - product category - SRM 5.0

    Hello,
    The product category was set as mandatory field in the contract management.
    By creating a contract or modifying an existing one, a product category must be selected.
    When I'm connected in English, i can use product category search function, and all the product category are populated.
    I'm so able to select a product category in the contract
    But when I'm connected in French, it is impossible to use the search function because no values are populated.
    I already check the transaction COMM_HIERARCHY, but English and French are already set.
    Thank you for help.

    1. GOA+LOcal contract = Central contratct.pls coreect me
    :- Basically Central Contracts are created in SRM and copied to ECC. Then after you can refer that contract as GOA.
    2. When the central contract is created in SRM is it dcistributed as Contract or Scheduling agreeemtn in ECC.
    :- It's distributed as Contract.
    3. Also, in SRM 7.0 is it possible to create contract directly in ecc from the sourcing cockpit.
    :- No; it's not possible. You have to create contract in SRM first then you can distribute it to ECC.

Maybe you are looking for