Central contract in SRM 7.0 with ECC 6.0

Hi
We are using SRM 7.0 with ECC 6.0
When we create contract in SRM 7.0 & Trying to distribute to Backend as Contract, It is showing error in BBP_PD as below
HEADER I1015 Awaiting Approval
HEADER I1021 Created
HEADER I1038 Complete
HEADER I1141 Released
HEADER I1180 Document Completed
HEADER I1193 In Distribution
HEADER I1195 Distribution Incorrect
0000000001 I1143 Item is Active
Badi BBP_DETERMINE_LOGSY is activated to define backend system
No IDOC is also generated.
No errors in MOnitor also
Not sure what is message type needs to define & what else is needed
Regards,
NNK

HI
Need to do following
1. Keep conidtion types in ECC & SRM same for contract.
2. Also Add message types BLAORD & COND_A manually in ECC in WE20.
Then only it works
Regards,
NNK

Similar Messages

  • 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

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

  • ECC - Central contract via SRM - condition Item button does not work

    Hi,
    After the creation of a central contract via SRM, I checked if all the condition types are taken over to contract in ECC.
    When selecting the item line and clicking on the condition button, it works correctly. After going back, to the main screen where the items are displayed I click once again on the condition button. Now it does not show anything, nothing happens.
    I have been looking for an OSS Note but couldn't find any. May you an OSS Note that I can use to solve this issue.
    Regards,
    Alexander

    hi Alexander,
    Do you get any error message.Can you check the konp and konh tables if entries exist
    regards,
    Lalita

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

  • SAP SRM 7.0 with ECC EHP 4 components to execute scenario

    Hi All,
    I am new to SAP SRM 7.0.Could you please let me know that what are all the components needs to be in place to execute the technical scenarios and business scenarios.I had an hands on experience on SAP SRM 5.0 with ECC 6.0 backend.
    Some where i read that there are lot of configuration  changes when we integrate SRM 7 with ECC EHP 4.Do we need to have PI 7  for executing Centralized contract and plan driven procurement scenario?Please guide me to have some exposure towards higher version.Thank you in advance.
    Best Regards,
    praveen

    Hello,
    You can refer the INSTALLATION AND UPGRADE INFORMATION , Master guides etc maintained at the below mentioned location which will answer all your query's here.
    Goto URL http://service.sap.com/srm-inst and then navigate to SAP SRM --> SAP SRM Server 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.

  • Facing problem in creation Central contract in SRM 7.0 System

    HI Experts,
    We have implemented Classic scenario in P2P business application.
    We are facing problem in creation Central contract in SRM system as we using SRM 7.0 .
    Error show  Application error in back-end system  (SAP SRM outline agreement* & Differing time interval
    Status show Document complited ->Distribution Incorrect >Created>Complate > Released.
    Please Reply
    Sharad

    Hi Sharad
    some mapping error with ECC and SRM
    expand the COND /BLOARD . you must get some clue - in bd87 51 error code
    did you map pricing condition type with ECC and SRM?
    kindly check BADI mapping in SRM
    Muthu

  • SRM 7 ehp1 with ECC 6 ehp5?

    Gurus,
    Is it mandatory to use SRM 7 ehp1 with ECC 6 ehp5? Our client has ECC 6 ehp 4 and is now upgrading from SRM 4 to SRM 7 ehp1. Can you share some links where I can confirm if SRM 7 ehp1 with ECC 6 ehp5 is mandatory?
    Also pl let me know what is the difference between shopping cart creation in SRM 4.0 and SRM 7.0 ehp1. SAP says they have changed something and made it more user friendly. Is it different from normal SRM 7 (without the ehp component?)
    Regards,
    John

    Hi,
    There are 3 ways of sending PO from SRM to ECC
    1.Via - RFC ( by setting the system landscape to a lesser version ) it will not have any side effects just that it used RFC connections instead of ESOA
    2.Via PI - by setting  the landscape to the current version and configure the relevant XML services in the SOAMANGER
    3. via Non PI Web Services- by setting the landscape to current version . This time the webservices are configured in SRM system itself.
    I have configured transfer of Contracts from SRM 7.01 to ECC 6.5 EHP5 as Contract/ Scheduling Agreement to the backend with Non PI Web Services(via XML). This way we didnt have to install PI at the client place which saved them a lot.
    I have written a blog on how to transfer central contracts from srm to ecc using web services but without PI , please find the link below and hope it is helpful.
    http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/06/13/transfer-of-central-contract-from-srm-to-ecc-using-web-services-without-pi
    Regards,
    Naveen

  • Central Contract in SRM 7

    Hi Experts,
    We are on SRM 7 Ehp1.
    ECC Ehp4
    Need a clarification on Central Contract of SRM.
    When we create and distribute the Central contract to backend, the price is shown as Zero in Backend.
    When the PO is created in backend, from where will the price be picked. Is it SRM?
    Is this correct?
    Thanks
    Aditya

    Hi,
    Are you creating service contracts?
    When we worked on Hierarchy contract we used MDM to get hold of those. As there were several issues in distribution.
    1. Basic Contract can contain line items.
    2. This is where we have used MDM to store contracts & used accordingly.
    You can distribute parent contract (with child contracts) as of I fell. Give a shot & let us know the ensues.
    Regards,
    yaniVy
    reward if helps

  • 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

  • SRM 7.01 with ECC 6.0 EHP 7.0

    Hi Guys,
    Does anyone have an idea on SRM 7.01 compatibility with ECC 6.0 EHP 7.0. Any things needs to be taken care from SRM side after an upgrade to EHP 7 in ECC side.
    Please share your experience.
    Thanks for your reply in advance.

    Hi Imran,
    It is compatible, But still for confirmation please see the product availability matrix.
    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/support/pam/pam.html?smpsrv=https%3A%2F%2Fwebsmp203.sap-ag.de#pvnr=01200615320900003495&ts=4&pt=t%7Co
    Best regards,
    Rohit

  • Contract Replication SRM 7.0 for ECC 6.0

    I am in the version 7.0 of SRM and I need to send the contract PCTR of SRM for ECC 6.0. 
    - Connections SM59 is well; 
    - Attribute CT_PROC_TY of the structure is well; 
    - Transaction Types and Number Screech is well; 
    - IDOCs BLAORD y defined COND_A in WE20 is well; 
    Did I forget something? 
    All creates the contract and I try to distribute the same, the mistake below it is exhibited: 
    " Could not determines back-end system goes contract " 
    Determination of Back End is well. 
    Some idea?
    Rgs,
    Pedro

    Hi, Pedro:
    It is SRM Extended Classic mode?
    You want to transfer the contract to ECC？
    Please check the ECC and SRM both sides of the scope of the contract number.
    Sarah

  • 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 -- Sch Agreements error in SRM7 -- ECC6 Eph4

    Hello,
    While creating a central contract in SRM7 and distribution to BE ECC6 Eph4. I am getting a condition mapping error in the IDOC.
    Central contracts to contract in BE uses PI
    Central Contracts to Sch Agreement in BE is IDOC.
    I see an erro " Errors occured in Mapping operation for conditions data" When i check the FM META_CTR_CHECK .
    Mapping conditions are maintained in the ECC
    SPRO--> Integration with Other SAP components > Central Contracts> Maintain Conditions.
    The same settings work in the development system. I see an entry with 003 Message number in table BBPD_CTR_IDOCREF.
    Any help is appreciated. Thanks

    Hi Netaji,
    I know this has been closed for sometime now, I thought I should tell you that you can send central contract from SRM 7.01 to ECC 6.0 Ehp4 and above using non PI webservices.
    Please find the link below just for your information
    http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/06/13/transfer-of-central-contract-from-srm-to-ecc-using-web-services-without-pi
    Regards,
    Naveen

Maybe you are looking for