Central Contract sent to Supplier

Hi,
I am working in SRM 7.02,
Creating a Central contract in SRM system and distributing the same to ECC system.
I want to sent the contract to Supplier through mail as RFx ..What are the configuration that needed???
Is there any setting need to be done..
Kindly guide me...

Dear Martin,
Thanks for the response.
But when i click process output button in the contract -> Output.
The below error message is displayed 'Output could not be created; contact your system administrator'.
And is there any way to send automatically to vendor, once the contract is released fully.
Regards,
Tamil.

Similar Messages

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

SRM 7.0 Call offs against Central contracts

Hello,
We are implementing Central contracts in extended classic scenario.We found that when call offs are done in srm by creating a PO in SRM with central contract as Source of supply, the Central contract fields in PO Line item does not get populated when the PO is transferred to ECC.Nor does the Release value get updated against the Backend contract (as seen in ME33K) though the release value is getting in SRM Central Contract document.This makes the release values in ECC Contract document out of sync with the value in SRM contract document.
Has any one faced this issue? Is this because of a missed setting or Is this a bug or is this the way it works?
Thanks
RamanAK.

Hi
give more details of the CCTR contract USAGE in the existing landscape
i could remember the PCTR behaviors in the ECS mode..
Actually contract information will not be transfered in the PO line when replicate to ECC since this contract is local.
the release values are available only in SRM front end ( total value of contract as well as each line of contract vs PO released).
Did you distribute the contract to backend system as well ?
so now your contract is available for both system
i.e ECS - shopping cart - SRM
and ECC purchase request as well - ECC
Are you enjoying the contract in the both systems?
Earlier GOA release values are updated in SRM via BLAREL idoc technology
but now adays in CCTR interfaces
PurchaseorderErpcontractReleaseNotificationOut - ECC
PurchaseorderErpcontractReleaseNotificationin - SRM
The release value synchronisation continous challenges to the BUYER .
So please clarify with SAP how SRM PO release value and ECC PO release value sync in the ECC purchasing contract.
dOUBLE CHECK
PurchaseorderErpcontractReleaseNotificationOut - ECC
PurchaseorderErpcontractReleaseNotificationin - SRM

Central contract information from SRM to ECC

Hi everybody,
I´m working with an integrated landscape (SRM 7 with ECC 6), and i´m configuring the central contract, but i have a doubt about the information that is sent from SRM to ECC (the leading system about the contract is SRM). The contract description written in SRM is sent to the contract created in MM?????
Thanks for all.

Hi, do you mean the texts in contract item ?
This text transfer functionality was delievered in SRM 7.0 and it was linked to ERP 6.0 EHP4.
For contracts overview, please check link: http://help.sap.com/saphelp_srm50/helpdata/en/43/05c0c685da6e72e10000000a422035/frameset.htm
Regards
Lauren

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

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

Purchase Order - Retrieve net price from Central contract (SRM or ECC)

Hi,
I'm doing a test by creating a PO referencing a Central Contract, which is made in SRM. When creating the PO, at this moment the net prices is retrieved from SRM.
Question: Is it possible to retrieve the net price from the copied contract which is in the Local ECC system?
(Customizing in ECC) SPRO -->Integration with Other mySAP.com Components >Supplier Relationship Management>Central Contract-->Price Calculation
The value what is at this moment: SRM Pricing Immediate
Should the value be: 1 SRM Pricing Immediately Only for Hierarchy Contract Item
Regards,
Alexander

Check for existing screen layout name from below settings -
Goto SPRO -> IMG Settings -> Materials Management -> Purchasing -> Purchase Order -> Define Document Types
Check for Field selection key against the PO Type.
Then goto below setting -
SPRO -> IMG Settings -> Materials Management -> Purchasing -> Purchase Order -> Define screen layout at document level
Select the screen layout / Field selection key in this setting and modify the field selection group Quantity and price. Make Price and price unit as display only as per your requirement.

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

Updation of central contract

Hi all,
We have a SRM 7.0 system with ERP 6.0 as the backend. I have created a central contract for an item - A with vendor - B in SRM and distributed it to a purchasing organisation (3002) through assign distribution functionality.
Now when i create a shopping cart for item A , the central contract appears as a source of supply and i can proceed with ordering of this item. But the problem i am facing is that the central contract is not getting updated in the backend ie the quantity does not decrease after buying the item - A.
Pl let me know if any message types need to be defined for updation to be posssible.
Thanks.

Hi Nikhil,
How did you fix this issue? I've created a central contract in SRM 7.01 and distributed successfully to ERP. When i created the PO in SRM, SRM contract release values is not updated in SRM.Or when i created PO in ERP using SRM contract as SOS, that PO is not updating SRM release values.
Regards,
Gigies

Central contracts on SUS

Hi Friends,
Can anyone suggest me any possible way to share the central contracts information with SUS suppliers.
Regards,
Prashant

Hi Prasant
I believe supplier can see their release values of contract.
i think it must connect with BW reports
SUS-BW combinations
I believe your requirement is to create a contract in SRM or ECC and want to transfer to Suppliers right.
we can send via email/fax/ print.
but for eg. for PO -supplier action is required like ASN/POR/GR and INV.
but in contract no information can perform by the supplier on contract. Just supplier has to monitor to release value in the contract and call for negotiate to renew the contract.
BR
Muthu

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

Central Contract/Purchasing Contract

Hi All,
What is the difference between Central contract and Purchasing contract in SRM 7.0
Also , can we dispaly the central contract in ECC using the transaction code Me33k .
Thanks,
Ashish

Hi,
Purhasing contracts are contracts created in SRM only and never accesed in ERP system. This contract can be used as source of supply in SRM only.
Central contracts are the contracts created in SRM and then distributed to ERP system and YES you can access this contract with me33k. Here the SRM contract and ERP distributed contracts will have the same document number. This contract can be used as source of supply in both ERP and SRM system.
Please note that SRM central contract is the main document where you can make changes and the same contract is displayed in ERP with minimal data.
Regards
Sam

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

Central Contract sent to Supplier

Similar Messages

Maybe you are looking for