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

Similar Messages

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

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

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

SRM Central Contract Management with Service Hierarchy

Hello Gurus !
Is it possible to use the export/import functionality (with the business function SRM_CONT_IMPR_2) for changing/adding the service hierarchies in SRM Central Contract? I see the SAP note that the hierarchies are not supported for Purchase Order.
Any idea?
Thanks in advance
Regards
Raj

Hi Raj,
it's not supported for contracts either.
Regards,
Zsofi

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 details & link with operational contract

Hi guys,
I want to get all the detail of CENTRAL contarct and the In need to get the corresponding operational contract also...
Please let me know whether there is any F.M. or Class or table where I can get these details.
regards,
Prabhu

Please rephrase your questions
The Contracts are distributed to backend system and Linkages are made betwwen SRM and Backend contracts. once distributed contracts are reached later clean jobs build a linkages between backend business Object contract with SRM contract
see
Linkages division in BBP_PD
header as well as item
Header Links:
and item links

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

SRM -- MDM -- ECC integration for central contract management for SRM 7.0

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

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

Unable to create service central contract items

Hi Experts
We are in SRM 7 EHP 2 ECC 6 EHP 6
We are unable to create Central Contract with Service.
There is no "Outline" or "Service" on drop down from ADD LINE in Central Contract.
Please help urgently.
Thanks
Ajit

Hi Ajit,
Please check if hierarchy template HIER_SE is assigned to this contract transaction type in the following customizing.
spro -> SRM Server -> Cross-Application Basic Settings -> Service Procurement Activate Service Procurement
Also SM34: /SAPPSSRM/VC_HT -> Assign to Transaction Type
Best regards,
Wendy

Sch Agr with Central Contracts

Similar Messages

Maybe you are looking for