Central contract distribution in two backend ERP system

Hello All,
I am implementing SRM 7.0 Contract management (SAPKIBKV07) with two backend ERP system.
We have a requirement where we will create a Global contract in SRM system. Upon distribution based on purchase organisation this contract should get distributed to two different backend system.
Q-1) Is this a standard featutre available with Contract management or de we need set up some configuration. If yes,  then please let me know the details.
Q-2) Again here the master data for both the backend system is not synchronised hence if a Global contract in created in SRM system and distributed to two different countries then each contract in ERP should have the region specific vendor code ?
How this functionality can be achieved.
Thanks,
Yatin

Hello All,
Has anyone implemented contract management with two different backend system and with different master data set up
Thanks,
Yatin

Similar Messages

  • SRM 7.0 Central Contract- Distribution to backend failure

    Hello experts,
    We are implementing SRM 7.0 Central contracts scenario with PI.
    The Contracts get created and Released but the problem is that the Distribution to backend fails. The Status in BBP_PD shows 'Distribution Incorrect' and the RZ20 gives an error 'Backend data cannot be read'.
    We checked all the configuration settings (including the PI settings) and everything seems to be in order.
    Would appreciate if someone could throw some light on the potential cause of the problem.
    Thanks
    Raman.

    Message must have created . check all SRM outbound transactions .but PI could not catch them.
    Note 1284369 - User attributes check in Contract distribution via services - what is your SP level in SRM 700.
    The sap stratergy in earlier version
    table in ECC BBPD_CTR_IDOCREF with message 019-This will result in setting the GOA status to 'Distribution Incorrect'.
    so SAP might have tried the same way in CCTR as well, Once message are created and this message number like IDOC number updated in ECC table for the further refrence .so like wise SRM trying to communicate the same to ECC but it would have failed.
    do you remeber when GOA idoc fails this table we will have reference number and reprocessing idoc.
    like any reference of your input must register in one ECC table but there may have this table or some other reference table.
    /SAPSRM/CL_CH_SOA_MAP_CTR_OUT  CLASS DO SOME trick and see what is happening here
    Muthu

  • Central Contract Distribution - line items creates many contract in the BE

    Hi SRM Gurus,
    We are in SRM 7 ECC 6 Ehp 4 PPS.  Ext Classic.
    First of all, CCTR - Central Contract can't be distributed as per SAP for PPS impl. 
    But we have a workaround. 
    We made snote 1354971 read with 1423994 implemented. Made the process work.
    Means Assign distribution on the item level was enabled and Distribution reached BE.
    But when we have multiple line items in the Central Contract, and we assign distribution, it creates one contract per line item in the Backend which is really absurd.  Which means if you have 100 line items, its creating 100 contracts.  When we do the call-off against this central contract, we have multiple contracts.
    Gurus, Can you guys throw some light on this entire issue.
    with regards,
    Freemind

    We are having nearly exactly your scenario and CCTR works fine with 1 distributed contract containing multiple items. Check if all the items are distributed to the same purchasing org and location. If all is the same, debug BBP_PD_CTR_TRANSFER with your SRM contract GUID to see when and how multiple contracts get created in ECC.

  • Central contract distribution trough IDOC - including new partner

    Hi,
    I created a partner in SRM for use with a specific central contract that I am distributing the ECC through an IDOC, the contract in backend is configured with this partner as mandatory, but if I process manually the data in the IDOC in ECC, document is not created, message error is that new partner missing.
    Any ideas how can I add a partner in this process?
    I'm working with SRM 7.0 and ECC 6.0
    Regards,
    José Luis D.

    To trace where your issue might be, it is helpful to find out the following:
    1) in table BBP_BACKEND_DEST, get the SYS_TYPE value for your backend system (LOGSYS = your backend system)
    2) in table BBP_FUNCTION_MAP, get the function name for OBJECT = BUS2000113 and METHOD = TransferFromData and TYPE = <your value from step 1>
    If you are going through IDOC processing, likely the Function would be "B46B_CTR_TRANSFER". In that case, set a session breakpoint in that function module. Then test run FM BBP_PD_CTR_TRANSFER with your contract GUID as input parameter and IV_SAVE_DB = "X". Execute until the breakpoint and start tracing the problem. This should help you identify the source of the error.

  • 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

  • Central contract distribution in PPS

    Hi All,
    With reference to this forum link, it is possible to distribute central contracts in PPS to ECC.
    http://forums.sdn.sap.com/thread.jspa?threadID=1915922
    I want to enable the assign distribution button. Pls help me with entries what to maintain in this table.
    /SAPSRM/V_MDA_HC
    Thanks and Regards,
    Abdul Raheem

    closing thread

  • Un-encumber Funds in Backend ERP System

    Hi,
    This applies to an SRM 5.0 extended classic system linked to a ECC6 backend.
    We have some corrupt and complete POs in our SRM system for which we would like to un-encumber  the associated funds in the backend system.
    Since these POs are complete and in error, we though that we could release the funds by updating the POs in the backend system using BAPI_PO_CHANGE.
    I set/updated the PO item's 'NO_MORE_GR' and 'FINAL_INV' fields in the backend system but the funds are still allocated when viewed via KSB2.
    Anyone have any idea as to what other fields need to be set in order to unencumber the funds?
    Regards,
    Jerry

    Hi
    <b>See related links -></b>
    Note 820274 FMJ2: Message ME664 is misleading
    Note 582221 FAQ: BAPIs for purchase orders
    800784 Closing commitment: Problems with MM version management
    770583 FMMC: Documents with errors are updated in FM 
    Note 962773 Assign new precommitments and commitments to PO's
    943487 Rule-based distribution inactive in batch processes/BAPI
    565099 New BAPIs for the purchase requisition object (BUS2105)
    Note 606083 ECS: Field transfer of purchase order to R/3 Backend system
    Hope this will definitely help. Do let me know.
    Regards
    - Atul

  • IBase integration to backend ERP system

    Hi! We have set up configuration in CRM to create an installed base and create/assign objects to it (part of object family). Now, I noticed in SMW01 that some BDocs are generated and am curious what is the purpose of this? Does it create a product and function location (if it relates to the ibase in CRM) in ECC?
    Can someone shed some lights on this as I am totally new to this iBase thing?
    Cheers!
    SF

    Hi SF,
    usually equipments are created in ECC and transfered to CRM. When changing the object in CRM a delta load is performed and the changes are send back to ECC. That is reason why the bdocs are created.
    Please find more information using sap help:
    http://help.sap.com/saphelp_crm60/helpdata/en/46/cc79505ec61525e10000000a114a6b/content.htm
    best regards,
    Johannes

  • 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

  • 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 release in ME35K

    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.
    Manjunath and Reagan

    Hi
    Are the contract originated in SRM ?
    In CCTR contract, all approval process happened in SRM web front itself.
    Do you want to make approval process again in ECC ?
    After approval of CCTR , the contract ventured from SRM to ECC and this contract is available as source of supply for SRm as well as ECC.
    Muthu

  • Central contrcact distribution with WSRM with SRM 7.01 (EHP1)

    Hi Gurus,
    We are implementing Central contract distribution with SRM 7.01 and ECC 6 EHP 5 backends.
    Can we use WSRM for Point-to-Point Communication for contract distribution? As the current customer does not have PI I am happy to avoid implementing PI.
    Thanks in advance.

    Hello Naveen,
    Find the error details:
    We have followed the steps for peer to peer service configuration as per note1268336 for synchronous service QUERYCODELIST for our XI independent scenario for contract management.
    As per the steps for peer to peer for settings,we are done with the configuration in SRM side i.e. provider system  and configured the QUERYCODELIST service.
    Now while doing the same on ECC side(BDE) i.e.  Consumer system when we are maintaining this service and creating Logical port,We get pop up to enter the details.
    Once we enter the details and click on APPLY setting button we are getting this error which Muthu as mentioned.
    "SRT Framework exception: Error in WSDL access: Exception occurred in communication framework:Error in HTTP Framework:404Connection Failed"
    I have configured this in the past for some other project once where similar error(it was 402 or 403) was coming since WSDL node was not active under SRT in SRM but this time we have checked it and all the required services are also active.
    Can you help to check further on this.
    Regards.
    Paresh.

  • Central Contract SRM

    I have an issue, when I create central contract in SRM. The Select System is empty. No values is there on the screen.
    Even though I try to create contract I have the error message "No customizing entry for SRDCLNT600 in table BBP_BACKEND_DEST"
    We have SRM 7.0 , ECC 6.0 EHP4.
    Regards,
    Lya

    Hi,
    Are you just setting up the system or has it been working already ?
    Pl check your "Define Backend Systems" set-up in IMG. There might be some problem here.
    Best regards,
    Ramki

  • 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

  • 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

Maybe you are looking for