Contract Management in Classic Scenario

Hi All,
I have a question around contract management in SRM when using the classic scenario.
Is it possible to utilise the global outline agreement functionality in SRM with the classic scenario and then distrbiute the contracts to the backend thus making use of the intrageted sourcing options in SRM and using cFolders for supplier colbaooration?
When the contracts are genarted in ECC are these then available as sources of supply in SRM by assiging the contract number to a vendor list?
And once final question, is the price info from the backend contract that is assigned in the evndor list passed into the shopping cart item data when the contract is assigned as the source of supply?
Cheers
Chris

Hi Dinesh,
thanks for the respone, this definately helps with the question of using Global Outline Agreements with the classic scenario.
There is still one question outstanding though and that is
If a backend contract is assigned in a vendor list is the contract price taken into account when the source of supply is assigned?
Cheers
Chris
Edited by: Chris March on Jul 15, 2008 9:33 AM

Similar Messages

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

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

Central Contract, MDM Catalog, and classic scenario

Dear SAP experts,
We are in SRM 7.01 with backend ECC 6.05 deploying classic scenario. We are using Central Contract Management in which we negotiate contract in SRM and later distribute it to ECC. We also plan to use SRM-MDM Catalog.
We notice that if we are using classic scenaro, the contract that is used as reference is the contract number in ECC (the one distributed from SRM). So at first we assume that if we want to push the contract data to MDM, we should have pushed the ECC Contract number. However we find out that actually SAP block the ECC Contract coming as distribution from SRM to go to MDM.
Our second option is to use distribution of contract from SRM to catalog. It does using SRM contract number. We create SC and then we pull the catalog item from the catalog (which contain SRM contract number) and then we order. However we end up with 'error in process' in which the system try to create a PR instead in the ECC (meaning that the contract number cannot be read).
We're puzzled with this. How can we use the combination of central contract, MDM catalog and classic scenario? Can we use the combination?
Best regards,
John

Maria
If you want the contracts to be in SRM and do not want them to send to Backend, then check this out.
Create a Vendor list for those items in SRM by assigning the local contracts to the vendors.Activate Vendor list for sourcing.
Then local contract data should pick as SOS from the vendor list.
If you can create contracts in Backend for stock material then SC would pick the backend contract as SOS in classic scenario.
Let me know if the above works or not.
PS : Reward points if helpful.
Regards
Jagadish

Contract Creation in SRM 7.0 classic scenario

Hi All,
We are using SRM 7.0 Classic scenario with ECC 6.0 EHP 4 and CLM 2. We are creating contracts in SAP CLM and pushing into as Global outline agreement.
Question is -
1) Can we create contracts in SRM 7.0 Classic scenario ?
2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
What are the mandatory fields required to transfer the CLM contracts contracts to ECC outline agreement - I know ,Vendor, Purchase org, Pur grp, company code are required - is product catagory is also a mandatory field.
Rgds/Pawan

Hi Pawan,
Please find the answered for your questions:
Question is -
1) Can we create contracts in SRM 7.0 Classic scenario ?
Mitesh: Yes we can very well create in Classic Scenario as well in SRM 7.0.SC can be pushed to SOCO based on the Prod Category configuration in SPRO.From SOCO PO, Contract and RFX can be created for SC.
2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
Mitesh: I dont think we can use ECC outline agreement as source of supply in SRM while creating SC.Contract replication in SRM 7.0 with EHP 4 ECC is eSOA based and ONLY Outbound to SRM (inbound to ECC).Contract cannot be replicated from ECC to SRM.
3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
+Mitesh: Standard intergeration of CLM/ESO to SRM 7.0 is very much there in roadmap for future releases of SRM/ESO.+
+As of now there is a consulting solution available to integerate ECC and ESO/CLM.+
+This logic can be leveraged to integrate ESO/CLM to SMR 7.0 (or lower version) requiring Developement effort from SRM functional,SRM technical,PI, Basis,ESO and java consultants.+
+Such contracts can be forced to be used as Source of Supply or alternatively replicated to ECC Via standard repliation scenario.+
Hope this helps.
Regards,
Mitesh

PI setting for transferring Contract from SRM to ECC - Classic scenario

Dear Experts
SRM 702
ECC 6.0 EHP6
SRM - Classic scenario
Need to understand PI setting for transferring Contract from SRM to ECC, as currently document Central Contract document getting created in SRM, but it is not getting transfer to ECC
No XML message getting triggered in ECC systm as well
can you help me in this
if any additional information needed, pls revert
Regards
Prashant K

Fully approve and release the contract. It will trigger the XML Message.
Go to https://websmp203.sap-ag.de/~form/handler?_APP=00200682500000002672&_EVENT=DISPLAY&_SCENARIO=01100035870000000122&_HIER_… and download the configuration guide & check the PI setting and required Software Components in PI.

Local contract and classic scenario

Hi all
A question regarding contracts - and interpretation...
On help.sap.com the following is stated:
SAP Enterprise Buyer, as the central purchasing system, saves the contract data and uses it for local purchase orders and purchase orders of the extended classic scenario.
I interpret this as, if one is using the classic scenario it's not possible to operate with local contracts in the SRM system. Can anyone confirm this?
And if so - any workarounds?
Our dilemma is that we have an extended classic scenario. Some materials are stock materials, and for these materials we are using a BAdi to switch off the extended classic scenario. No contract data is now added to the shopping cart, which I think is due to the classic scenario.
Thanks for your help in advance
;o)
Maria

Maria
If you want the contracts to be in SRM and do not want them to send to Backend, then check this out.
Create a Vendor list for those items in SRM by assigning the local contracts to the vendors.Activate Vendor list for sourcing.
Then local contract data should pick as SOS from the vendor list.
If you can create contracts in Backend for stock material then SC would pick the backend contract as SOS in classic scenario.
Let me know if the above works or not.
PS : Reward points if helpful.
Regards
Jagadish

Classic scenario, where to create Contract and product category

Hello All,
We are using SRM4.0 ( Classic scenario) with non-sap backend system.
We need to attach contract in Shopping cart in SRM.
My questions are:
1. In which system ( EBP or non-sap backed), we need to create contract? and how to create it?
2. In which system( EBP or non-sap backend), we need to define product or product category? and how to create it?
Regards
Neelesh

Neelesh
When you replicate product categories from any backend system, they get created in SRM and update the value of logical system with the backend from which it replicated.
You can only create Product category in standalone. You can try to create the same for classic but maintain log syst value with the correct backend. This is not advisable.
PS : Reward points if helpful.
Regards
Jagadish

Contracts in Classic Scenario

In Classic Scenario SRM 5.0 with ECC 6.0, how can I create an ECC Contract with a requirement from the Purchaser's Worklist ? Do I use the Global Outline Agreement? If so, what are the config steps ? Full points assured. Thx.
Raja

Hi You can create a GOA in SRM and distribute a contracts in Backend .
Basic configuration
(1) Define a transaction type GCTR
(2) No range internally in EBP and Externally in R/3,
(3) Idoc settings sending to r/3 like BLAORD, COND_A
(4) You must have a role to create a GOA as SAP_BBP_STAL_STRAT_PUR-
CHASER.
(5) You may need to map all condition type in SRM and R/3.
(6) Refer this notes 646903 - Global outline agreement: Tips and tricks
You can refer some related links...
http://help.sap.com/saphelp_srm50/helpdata/en/42/f93dfd975f3ee6e10000000a1553f7/frameset.htm
http://help.sap.com/saphelp_srm30/helpdata/en/7d/0a093f7c392e5ae10000000a114084/content.htm
Re: SRM GOA [BLAREL ]
regards
Muthu

Manage direct procurement in classic scenario

Hi Experts,
We are on SRM 701
Classic Scenario
can anyone let me know how we can manage direct procurement in classic scenario?
i want to kept goods in storage location and i cant do that because of account assignment tap in SC and as i know account assignment is mandatory to create a Sc
Regards
Elham

Hello Elham,
As suggested Account Assignment should always be used and one cannot skip it for creating the Shopping Cart. If you are having Classic Scenario then your PO would be in backend system directly which you can manage through dummy account assignment as guided you in your previous post. Just get in touch with your Finance Team and ask them to make a Dummy Profit Center/Cost Center which you can use while creating SC for your local Storage
Thanks
Gaurav Gautam

Contract preference over PIR in SOS in Classic Scenario

Dear all,
We are in Classic Scenario, SRM 4.0 (SRM Server 5.0) SP9 with R/3 4.6C backend
When a Material has a contract and a PIR in the backend, if the material is added from catalog in the Shopping Cart, both Purchase Info Record and backend Contract are found as Source of Supply and then apparently no priority exist then no automatic Source of Supply is defined (user must select one to have one assigned).
At the opposite doing the same in ME51N in backend selects contract automaticaly (when Sourcing determination is flagged).
What we want is that if a Contract and a PIR are found for the material in the SC then the contract is taken automatically as preferred Source of Supply like in ME51N.
Any idea? Is that a bug? Or what can we change? BADI?
Thanks a lot
RD

It is possible to disregard inforecords for sourcing purposes in R/3. If you do so EBP will automatically disregard inforecords as well. This approach consistently removes info-records as sources of supply in both, R/3 and EBP. here's how:
1. run cmod transaction in R/3 and create your project
2. Assign enhancement LMEQR001 to your project
3. In component EXIT_SAPLMEQR_001 there is include
ZXM06U52 and you need to enter some code in this include. Here is an example how to remove ALL inforecords:
INCLUDE ZXM06U52 *
loop at t_sources.
if not t_sources-infnr is initial.
delete t_sources index sy-tabix.
endif.
endloop.
Note: BBP_SOS_BADI can only be used for customizing the searches of local sources of supply: local contracts, vendor lists and or vendor interlinkages

GOA + Local Contract distribution to R/3 in Extended Classic Scenario

Dear SRM Gurus,
System Information: SRM Server 5.5 EBP5.5
Technical Scenario: Extended Classic Scenario.
Q1) We have created a Global Outline Agreement in EBP. We want this to be distributed to R/3.
But when we click on distribute, it does not get distriduted to R/3 ??? Is there any IDOC to be maintained----wich one ??
Please guide me as to how can we go ahead with this.
Best Regards,
ANIL RAJPAL.

Hi Anil,
The IDOC to be maintained is: BLAREL
For detail information you can visit the links.
http://help.sap.com/saphelp_srm50/helpdata/en/00/f5c93f4d903b1ce10000000a114084/content.htm
https://websmp104.sap-ag.de/~sapidb/011000358700002529571998/blarel02_d.htm
Also you can have look at notes:
643823
953269
671764
641919
Pls let me what all configuration you have done for GOA functionality so that I can suggest you something specific.
Best Regards,
Amit
Do reward the points if ans is helpful!!!

Info Record Not Appearing for all materials in classic scenario.

HI ALL,
 I am working on Classic Scenario and all the follow-on documents are getting created properly. But the problem is With SOS. Currently i am able to view the info record for only one of my material, I am also referring backend contracts through vendor list. The contracts are visible in SOS.
 Can somebody pls put a light as to why for other materials the info records is not displayed in SOS, is there a report which has to be run to get the info record into SRM from ECC. If not then how does the system bring these contracts and info record from ECC to SRM.
 I am working on SRM 5.0 and ECC 5.0.
THANKS AND REGARDS
Debu

Hi
Please read this as well.
You have created sources of supply. These could be:
-> Contract items in Enterprise Buyer
-> Vendor-specific prices
For this, you have created Product Linkages in the SRM System with vendor-specific prices via the SAP Menu Master Data -> Products -> Process Products.
-> Entries in the vendor list of Enterprise Buyer
In Customizing you have assigned product categories to which the system is to automatically group requirements and you have scheduled report BP_SC_TRANSFER_GROUPED to run periodically.
For more information, see the Supplier Relationship Management Implementation Guide (IMG): SRM Server -> Sourcing -> Define Interactive Sourcing for Product Categories.
Sourcing is completely integrated with the global availability check in SAP APO and executes a vendor search. You can activate third-party order processing in the check instructions by choosing how you want the system to start sourcing and which sourcing method you want to use for it. There are two different options here:
○ If you want the products to be delivered exclusively by external vendors, the system performs sourcing directly at the external vendors without evaluating internal locations. For this, SAP APO requires corresponding purchasing records, delivery plans and contracts that are transferred from SAP ECC.
○ If you only want to have products delivered by external vendors occasionally, that is to say, if you are unable to deliver the product from your own warehouse stock, choose an ATP profile in which both internal and external vendors are evaluated. In this case, the external vendor is treated like an internal location in SAP APO, and is integrated into location determination in the rule-based availability check.
You can also choose the vendor manually. If you have already specified a vendor as the source of supply in SAP CRM, SAP SCM does not carry out any further sourcing. In this case, SAP SCM merely checks the validity of this vendor and confirms the requirement in its full amount if the vendor is valid.
For more information, see SAP Library for SAP SCM at SAP Advanced Planning and Optimization (SAP APO) -> Global Available-to-Promise (Global ATP) -> Advanced Availability Check Methods -> Third-Party Order Processing in the Global ATP -> Sourcing in Third-Party Order Processing.
Refer these links for more details ->
Assignment of Existing Sources of Supply
http://help.sap.com/saphelp_srm50/helpdata/en/25/40f23a53cd0e04e10000000a11402f/content.htm
http://help.sap.com/saphelp_srm50/helpdata/en/55/4af548688211d4977e0004ac962ee6/frameset.htm
http://help.sap.com/saphelp_crm50/helpdata/en/fa/84944279c0c66ae10000000a155106/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/18/db183d30805c59e10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/63/36f2323326da4da25d9d0a06f550a0/frameset.htm
Processing Contracts
http://help.sap.com/saphelp_srm50/helpdata/en/43/0f234a9e242a8be10000000a1553f6/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/5a/4cc5376848616ae10000009b38f889/frameset.htm
See alsoSAP Note 519794 EBP: Replication of Materials exclusively for Purchasing
SAP Note 505030 (Restrictions for the integration of external requirements).
Regards
- Atul

Extended Classic Scenario - SHC: Buffer table not up to date

Hello all,
I'm working in SRM_SERVER 550, SAPKIBKT11, and having issues using BACKEND PURCHASING ORGANISATIONS and the Extended Classic Scenario.
According to SAP note 944918 the following indicator should not be required to be set:
Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Activate Extended Classic Scenario --> extended classic scenario active.
I did set the Backend Purch. Grps Responsible indicator, and I did create organizational units specifically for the backend purch. grps.
We need to set the main part of all SHCs to ECS, but when I do set the indicator in customizing to "extended classic scenario = active", I get a dump in my web environment: 'buffer table not up to date'.
What is causing this failure in my SHC?
I tried to implement BAdI "BBP_EXTLOCALPO_BADI" (method DETERMINE_EXTPO) like described below here: without the line bbp_extpo_gl-bbpexpo = 'X'., I can continue and create the SHCs. Problem is though: all SHCs will get marked as Classic Scenario. So, to make sure the SHCs will always get marked as ECS, I have added this line in the BAdI. Unfortunately this immediately results in the 'buffer table not up to date' error in the SHC itself, as soon as I try to open the details of the new item.
Hope you help me out here?? It doesn't seem to be related to the BAdI, but somehow the system doesn't allow me to mark SHC items as ECS.
Thanks & Regards,
Berend Oosterhoff
SRM Consultant Accenture Technology Solutions - The Netherlands.
BAdI BBP_EXTLOCALPO_BADI:
method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
data definition----------------------------------------------------*
DATA:    wa_mattype     TYPE BAPIMATDOA,
           wa_char18      TYPE MATNR,
           attrib_tab     TYPE TABLE OF bbp_attributes,
           wa_attrib_tab TYPE bbp_attributes,
           wa_value       TYPE om_attrval,
           wa_product_id TYPE comt_product_id.
    bbp_extpo_gl-bbpexpo = 'X'.
from here I did the specific selection for the SC, but that's not relevant here.

Hi Prashant,
Thanks for your quick reply!
Note 1085700 is about Short Dumps when creating or changing a contract. I am trying to create a Shopping Cart, without a reference to a contract. BAdI BBP_DOC_CHANGE_BADI is not active in our system.
Any other thoughts?
Regards,
Berend

SRM 7 PPS Classic Scenario with Plan Driven Procurement?

Hello experts, I want to know if the combination of SRM 7 PPS Classic Scenario with Plan Driven Procurement is possible? or if there any limitation to consider? Our client needs to create purchase requisition in ERP -> send this purchase requisitions to SRM (as shopping carts) create bids - > quotations - > create contract from accepted quotations and then from the contract we need to create purchase order but this one must be created in ERP (classic scenario) Someone has experimented the same situation? Best regards and thanks for your Help.
Liam

Hi Lima ,
Classic scenario wont support PPS .
        - Stand alone and classic scenario not supported
        - Shopping cart renamed to Purchase Requisition
        - Shopping cart generate (pre)commitment in funds management
        - Contract can create Funds Reservation (Earmarked Funds) in Funds Management as a Guarantee
        - Goods Receipt and Invoice created in ERP
        - Mixed PO: PO with lines that works like contract lines, a PO can be created from these lines
        - PO created from contracts or mixed-PO is named call-off PO. Only is a new name, is a "normal" SRM      PO
        - Goods receipt possible in SRM only in "easy" cases
Thanks & Regards
Pradeep Kumar Dondeti

Contract Management in Classic Scenario

Similar Messages

Maybe you are looking for