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

Similar Messages

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:

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

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

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

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

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.

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.

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

SRM 7.0 EhP 1 central contracts with service lines

Hi,
I have a question concerning the use of SRM 7.0 EhP1 central contracts with service line items. I know that for SRM EhP 1 you would require EhP 5 in ECC. However, since my organisation just went to EhP 4 last weekend I am wondering if there's any option to use services in central contracts without going to EhP 5 in ECC.
Kind regards,
Bastiaan

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

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

When creating PO in ECC central contract not displayed automatically

Hi,
I'm testing if the central Contracts are displayed automatically when creating a PO (ME21N). The contract has been created in SRM. In ECC the contract is saved in table CC_DB_VIEW.
Is it possible that the contract is automatically assigned to the PO, when entering the vendor and material. For PIR this works fine.
Regards,
Alexander

Hi,
Create Contract Release Order Thru ME25.
Follow the steps from this document:
http://help.sap.com/saphelp_470/helpdata/en/75/ee0f4d55c811d189900000e8322d00/content.htm
Reetesh
Edited by: Reetesh Tiwary on Nov 17, 2011 3:52 PM

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

Similar Messages

Maybe you are looking for