Central Contract Creation

Dear All,
I have created Purchase Org " POR1" and assigned the same to Comp Code & Plant( I have only two plant & One Comp Code)
Also created Pur Org "CPOR" and it is assined as Ref Pur Org to "POR"1..
CPOR was not assigned to Any Comp Code & Plant..
Vendor was Created for Both POR1 & CPOR..
and Conditions at plant level feild is maintained as Blank for the Plant in OMF0 trxn..
When I try to Create a Contract with doc type 'DC" & Pur org "CPOR"..
System is throwing Error by message number 06 794..
" No plant that could release against the contract item exists"
Could you all plz let me know the solution for the same..

chk assignment of ref purch org to plant in ox17 ; because if 5 diff purch orgs ( all having diff plants ) have one ref purch org . In that case which plant will system pick fr release order??
Edited by: rajat kaushik on Apr 2, 2009 8:30 AM

Similar Messages

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

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

Multiple contract creation in ECC from a single GOA

Hi Experts,
I am working on a solution regarding to GOA in SRM - Contract in ECC creation and i am wondering about the following scenario:
Create 1 GOA in SRM 5.0 for a central/global purchasing organization and when the appropriate BADI going to transfer it into ECC, it creates contracts for all company codes.
At my current client they use GOA but until now they created 1 GOA for a specific p.org and the BADI transferred (and created) contract in ECC for the specific company code (they donu2019t have kind of central/global purch organization unit in ppoma). In the future they would like to create GOAs which are usable for all companies, but instead of creating (and changing) them manually (N GOA in SRM for N contract in ECC) they want to have an automatism.
Does any of you have any experience on this? That would be really good if you can share with me some high level overview about concept.
Thanks in advance for your help!
Best Regards,
Attila

Hi,
Let me correct if i am right:
- Central Contract -> new concept of SRM 7.0. 1 contract which is visible and usable from ECC and SRM as well. (not available in SRM 5.0 - agree)
- GOA -> it exist in SRM 5.0 for sure! (we are currenlty using it for ECC procurement).
The solution what you are mentioned is good...but as you said only for SRM 70...we are in SRM 5.0 and we need solution for here. Do you have any idea?
Currently i am thinking about a new solution based on "standard" functionalities: if a GOA need to be created for mulitple company, it has to be populated in Header distribution (all company will have the same contract header). It item detail all the required information need to be poupulate in SRM (i.e.: item 1 for p.org1/comp.cod1; item 2 for p.org2/comp.cod2).
When this is done, the BADI need to check the informatoin in SRM GOA and create contract according to that -> in this case 1GOA is created, but the 2 items for totally different p.org/comp.code, the BADI needs to create 2 different contract in ECC (i would like to avoid using reference purchasing organization in ECC!
Thanks in advance!
Best Regards,
Attila

SRM 7.01 Backend Contracts creation with XI/PI ESOA Service

Hello, we are implementing SRM 7.01 PPS with Extended Classic Scenario. We need to create contracts backend contracts ( ECC) from RFX RESPONSE at SRM. As we have ECC 6.0 EHP 5 we have to use Esoa services. The problem is that we have set up PI but no contract is created at ECC ( not even in SRM) when we pressed button " create contracts" from rfx response even thought the message at SRM is " contracts XXXXXX created" I think we are missing some customizing in ECC.
We have already implemented badi BBP_DETERMINE_LOGSYS
I read note 1268821 who explains that we have to activate business function LOG_MM_P2PSE_1 in ECC but I think this only apply for "CENTRAL CONTRACTS" and we dont want to use central contracts. We just want to creates contracts at ECC from rfx response in SRM. I couldn´t find any documentation about this, just for Central Contracts or backend contracts creation (through idocs) . Any idea?
Thanks in advance for your help!
Best Regards
Liam

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!

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.

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

SRM Central Contract

Hi,
We have created successfully Central contracts and distributed to ECC 6.0. I have created Central contract for central purchasing org A as 45xxxxxx and distributed contract for purchasing org B as 54xxxxxx
I have created purchase order for purchasing org B in SRM. Can I use distributed contract for purchasing org B in SRM?
Do I have always go for PO creation for purchasing Org A in SRM?
Thanks
Ravi

Hi Ravikumar,
You donot need to distribute back your ECC contract to SRM system.
The concept of central contract is to use one contract to be used across system landscape.
You can assign local purchasing organization as well as backend purchasing organization to a central contract for distribution. For backend purchasing orgs, the system will create individual contracts for the backend porg. Any consumption of backend contract will keep the central contract in sync. For local SRM porg, it will not create separate contract. It can directly use the central contract in SRM.
So, the answer to your question is big yes. However, it will be relevant only if you are working with extended classic scenario. In classic scneario, the local contract will not be populated for consumption.
I hope, it helps you.
Thanks and regards,
Ranjan

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

Create Central Contract from Requisition

Dear SAPers,
Is there anyway I could do this: I want to create centrally-agreed contract with reference from PR/RFQ.
Yes, I know that..
- I cannot change nor delete the plant in contract
- The plant data is locked during contract creation (if using PR reference)
I've been explaining this to my client, but they still want to create contract from PR (plant specific), that can be released to many plants.
In standar SAP process, I know this requirement cannot be made. But..
- Is there any custom I can make?
- Can I override the error message (plant doesn't match with contract) at PO creation?
- If can override it (which I can't. I tried to cange it in SPRO purchasing message setting), is there any effect? (in accounting, maybe?)
Please share your comments.
Thanks,
Bayu

Hi,
Please check the below link
[http://help.sap.com/saphelp_470/helpdata/en/75/ee0f0c55c811d189900000e8322d00/content.htm]
Hope it will be useful.
Thanks & Regards,

Sch Agr with Central Contracts

Hi Gurus,
Need some inputs:
We are implementing classic SRM 7 with BE ECC6 Eph4.
Did anyone work on distributing the central contracts to BE as Sch Agr.
1. Any lessons learned, challenges. etc.
2. Heard there are issues with Multiple line items?
3. Will the scheduling agr release information get updated in the central contracts? Reason for asking this we would like to trigger the central contract alerts.
Any info is appreciated. Thanks

Processing Delivery Schedules
You can use this business process to process delivery schedules. Scheduling agreements are a form of purchase agreement for which the delivery of the total quantity is over a certain time period in a delivery schedule, consisting of lines indicating the individual quantities with their corresponding planned delivery dates. Scheduling agreements support the following procurement forms:
Standard
Subcontracting
Consignment
Stock transfer
Scheduling agreement releases are issued to the supplier, requesting delivery of the required materials on the dates shown. A creation profile determines which event triggers the creation of a scheduling agreement release, how the delivery dates are displayed (aggregation and release horizon), and whether backlogs and immediate requirements are determined. A tolerance check can be carried out for releases that are created due to changes to the overall delivery schedule in the system.
Scheduling agreement processing is heavily integrated with planning functions. The scheduling agreement releases can result directly from a planning run without requiring further involvement of a purchaser. Before you can use scheduling agreements, you must maintain the source list, including the MRP indicator for relevant items.
Suppliers can issue confirmations (order responses) to the relevant purchasing organization indicating their compliance or noncompliance with the scheduled delivery dates.
You can work with or without release documentation for scheduling agreements.
With release documentation
The schedule lines in the system have internal character and are not transmitted to the supplier until you explicitly create a scheduling agreement release. This may take one of two forms:
Forecast (FRC) delivery schedule
Just-in-time (JIT) delivery schedule
All scheduling agreement releases are stored in the system. Thus you can monitor the scheduling agreement releases, or compare selected scheduling agreement releases with each other.
Without release documentation
The schedule lines are immediately transmitted to the supplier.
Process
The following business process runs in SAP SRM:
Create/process scheduling agreements
Release scheduling agreements
Transmit and monitor scheduling agreements
Process delivery schedules and releases
Transmit and monitor delivery schedules
Administrate scheduling agreements
Monitor/view list display of scheduling agreements
http://help.sap.com/saphelp_srm70/helpdata/en/79/d5962a003a4865b21cf3cdf42cf75b/frameset.htm

FPM Modification - Central Contract

Hi all,
we have a requirement where, we need to change the initial screen of CCTR, launching.
Actually we have 2 places from where CCTR's can be created from Portal.
1. From Left Pane under Create Document-> Create Contract.
2. Just above the table display of contracts, we have an option for creating Contracts button, and upon click of ths button, a drop down appears with Create Contract. Below is the screen shot of the same
When we go with First option, a pop up appears to select the type of Contract and Backend System and then we need to click on create button.
This will take to main Contract Create Screen.
But when we follow the second way, it directly opens CCTR creation screen.
Now our requirement is, when user follow's first process, he should be able to see directly CCTR Creation screen without intermedate pop where we select CCTR and backend system.
Can anyone provide some pointers on this.
I tried modifying Application ID's and Config ID but no resutl.
Your help is highly appreciated.
Regards,
Pavan Kumar

Hi Sankar,
Sorry for delay in reponding.
I have already read the bolg mentioned by you, which says how to add new tab and change the name of the exisiting Tab.
But here my question was different.
Actually we are having 2 different WDCC's:
1. /SAPSRM/WDCC_FPM_OIF_PRSEL_PTYP : This will be called when, user clicks on Left Side of portal under create Documents section for Contracts.
2. WDCC: /SAPSRM/WDCC_FPM_CTR_PURCH which has all tabs will be called from the POWL table which will be displayed at the Bottom of the screen.
When we click on the Central Contract, the main screen will open. Which has the WDCC, mentioned in point 2. ( /SAPSRM/WDCC_FPM_CTR_PURCH )
Please let me know if it is possible to bypass the WDCC: /SAPSRM/WDCC_FPM_OIF_PRSEL_PTYP and move directly to /SAPSRM/WDCC_FPM_CTR_PURCH .
I hope I have clearly explained my issue.
Regards,
Pavan Kumar.

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á

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

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

Central Contract Creation

Similar Messages

Maybe you are looking for