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

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

  • 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

  • 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

  • Central Contract in Classic Scenario

    Hi Friends,
    I have done the central contract scenario in Ex classic  where Local contract will be distributed to ECC .
    Can we use the central contract concept in Classic Scenario and is there any limitation based on scenario.
    As in classic the documents are created in ECC , so for central contract also there will be no local contract ???
    Can anyone please help me to understand the same.
    Thanks
    IS

    Hello,
    Yes, this concept can be used in classic scenario as well.
    You can use them as source of supply, since in classic scenario ECC contracts are considered as soruce of supply. Therefore, replicated contracts will be proposed as SOS for shopping carts.
    Regards,
    Ricardo

  • Central contract Workflow attributes

    Hello,
    As per my understanding we can activate the workflow on any contract attributes/ fields(for central contract) like prices, product category etc.
    We can activate u201C1-stepu2019 standard bc set u201C/SAPSRM/C_CT_600_001_SP04u201D and can determined workflow agent based on any attributes like u201CProduct categoriesu201D ,price etc
    Or we can use BADI Implementation u201CBADI /SAPSRM/BD_WF_RESP_RESOLVERu201D for Agent determined based on attribute store in customized table
    Please correct me if my understanding is wrong
    However we need your valuable inputs on below
    1)     List of central contract ( CCTR ) attributes/fields on which we can activate the workflow.
    2)     List of central contract ( CCTR ) attributes/fields on which we can activate the workflow without any badi implementation ( without any coding ). As a part of standard configuration.
    Best Regards
    EPR_SRM_MDM

    HI,
    I suppose you plan to use process controlled workflow.
    If yes then you can check the tcode BRF and try to create a expression of type formula interpreter.
    In the this expression navigate to formula editor and here you can find all the attritutes you can trigger for any business object.
    For agent dertermination SAP has already delivered many agent determination method.. If a process level and click on the F4 feature available for field Resolver Name to find all the predelivered methods.
    You can check the service market place http://service.sap.com for Workflow Guide SAP SRM 7.0
    Path:
    service markerplace -> Release & Upgrade info -> Installation & Upgrade Guides-> select SRM 7.0
    Regards
    Sam

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

  • Badis for PO and Central Contract in SRM 7.0 in classic

    Hi everyone,
    I need you help. We are working in a implementation of SRM7.0 with ECC 6.0 Ehp 4 in a classic scenario. We want to know which badis we can use in order to change the purchasing group of the PO an Central Contract when their are transfered to ECC.
    BR,
    Ivá

    Hi Muthu,
    We are wondering if it is posible the following:
    - An user wants to create PO form SRM. This PO in SRM has the Purchasing group XXX, but (for any reason) we need when this PO is send to ECC, the system changes the purchasing group to YYY.
    BR
    Ivá

  • 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

  • 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

  • Net price zero for SRM service central contract in SAP ECC

    Hi
    Net price in backend ECC is showing as zero for SRM service central contrracts, all other price fieids are fine expect net prices. We have no issues for material contract.
    Does any one had similar issue of net price zero? I have tested this scenrio in couple of SRM 7 landscpape all are with similar behaviour. Is it standard?
    Your response is highly appreciated.
    Regard
    Prashanth K Saralaya

    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

  • Central Contract for various company code

    Is it possible to create a central contract for several company code & to Generate Contract release order to a particular company code.

    Hi Chandra
    U can Go for centrally agreed contract
    Contract items can relate to a single plant or to all plants covered by a purchasing organization (centrally agreed contract).   
    All the plants of a purchasing organization can order against a centrally agreed contract.   
    An enterprise working with a central purchasing organization covering several plants can negotiate better conditions at a high level.  
    Centrally agreed contracts can be entered into with a vendor’s entire corporate group. The individual contract release orders can be issued to different individual companies belonging to the vendor corporate group. This is made possible by the partner functionality.  
    You can stipulate that certain plants are to be supplied by certain companies belonging to the vendor corporate group.
    Vishal...

  • Creating Central Contract using Reference Purchasing Org

    Hi,
    We are using two type of purchasing organization:
    a.Global Purchasing Organization - It is not assigned to any company code or plant.
    b.Country Purchasing organization u2013 It is assigned to Global Purchasing Organization. This cross-plant country specific purchasing organization is to procure materials for several plants independent to a company code. We have assigned the purchasing organization to the plant and not to a specific company code.
    Global purchasing organization has been setup a reference purchasing organization to be able to create central contracts that is independent of company code and plant.
    However whenever we create the central contract using the reference purchasing organization, the system will not proceed unless we define a company code. Please let me know how we can avoid the Pop up message u201CThe Purchasing organization XXXX has not been assigned to a company code. Please enter a company code.u201D
    Please note that neither Global nor Country purchasing organization is assigned to company code. The company code will be determined only from Plant.
    Please help.
    Regards,
    AG

    Hi.
    In your case, both the Purchase organizations ( Global Purchase Organization & Country Purchase Organization ) are not assigned to the company code. But Country Purchase Organization is assigned to the plants from the different company codes and Global Purchase Organization is not assigned to any plant also.
    In this case, If you are creating central contract with the Global Purchase Organization , you will get error. Becuase Global Purchase Organization is not assigned to any company code or plant.
    If you are creating central contract with the Country Purchase Organization, system will allow. Because this purchase organization is assigned to the plants from the different company codes. Based on this plant, system will identify company code.
    So, conclusion is Purchase organization is must be assgined to the plants. This setting is mandatory in order to indentify company code which is giving in the Purchase document. But the assignment of company code to the purchase organization is optional.
    So, assign plants to the Global Purchase Organization and try to create central contracts. It will work.
    Regards
    KRK

Maybe you are looking for