Local contract and classic scenario

Hi all
A question regarding contracts - and interpretation...
On help.sap.com the following is stated:
<i>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>
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

Similar Messages

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

Partial quantity of Material in Extended and Classic Scenarios

Does it possible to pass partial quantity of Material into Extended and Classic Scenario ;for instance we have 100 qty for a material & out of them 60 qty goes to Extended PO and 40 qty goes to Classic in backend system .
If yes so how & what criteria would be ?

Hi Lalit,
Until now we did not use both classic and extended classic for one organization.
Are you using that or you just have a doubt??
Regards,
Satish

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

Local Contract and GOA

Hi,
In which technical scenario we can use
1)GOA
2)Local Contract
3)Both.
THANKS,
Venky

1)GOA -
In classic for all your source of supply as distributed contract for your PR,PO and SC
IN ECS only for backend direct materials . this can be used only in backends but this only for your backend.
2)Local Contract only ECS
3)Both.-Yes
Local contract for srm procurement
GOA for backend .
br
muthu

Customizing for extended and classic scenarios

Hi,
I know what is the difference between classic and extended classic scenarios.
But i want to know what is the difference in the customizing.
I understand that there is a badi that decides on the product categories and also there is a customizing for assigning product categories to back end systems.
I want to know what is the significance of this customizing?
Regards
abaper sap

Hi Abaper
in spro
activate extended classic scenario determines the technical scenario as ECS.
and your PO created in SRM system so it is a leading system in SRM.
your PO messages are created in SRM and sent it suppliers from here not from ECC.
all PO transaction type must be defined in SRM system.
you can go EBP_SUS scenario if customer interested.
like many..
Here in ECS , you can use local contracts....
br
muthu

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

Limit SC and Classic scenario

Hi Guru's,
Just want to clarify if it's possible to create limit SC and directly createa BE limit PO without using Ext. Classic Scenario?
Thanks in advance,
Thomas

Hi Michael,
We are currently using a SRM 4.0 and we do NOT use ECS.
My problem is that we normaly only give access to BBPSC02 to our users and I do not see the limit position here.
Another thig is that when I create a limit position,the PO is not created because the sloc is missing.
We use the new BAPI_CREATE1 to create the POin BE.
/Thomas

External requirements and Classical scenario

Hi experts
Is there some restriction concerning the use of external requirements in Classical scenario?
Is there some some sap note about it?
Thanks
Nilson

Hi Nilson,
Pls refer Note 505030 - Restrictions for the integration of external requirements.
Regards,
Prashant
Do reward points for helpful answers

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

Consume local contracts with extended claissc scenario

Hello,
We are implementing SRM 7 stack 10 with ECS. We are connected to one R3 4.7 backend.
Since local PO will be replicated to the backend, is that possible to consume local contracts with that scenario?
Could there be a problem with the GR if there is no contract in R3?
At the moment we can not manage to consume SRM contracts.
Thanks in advance

Hi ,
There can be various reasons why a local contract is not populated as a source of supply for requirements in extended classic. Ideally, local contract are always porposed as a source of supply unless
1. company codes are not identical.
2. Purchase organization of requirement does not match with any of the released authorized purchase organization.
3. product ID or product category are identical.
4. Delivery Plant mentioned in the requirement should not excluded in the contract and so on.
Check all the points and see if the contract is eligible enough to get popped as a source of supply.
Thanks and regards,
Ranjan

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

SRM PPS using classic scenario

Hi SRM Experts,
I am exploring the possibility of implementing PPS in SRM 7 using the classic scenario.
Please let me know if it is possible and how can it be achieved.
Earlier threads mention that PPS is only available using extended classic.
Thanks.
Regards,
Amish

Hi Amish ,
PSS scenario is not supported for classic scenario ,
changes in procurement process of SRM 7.0
        - 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

Why Extended Classic Scenario

Hello
I understand the difference between Extended Classic and Classic Scenario with the follow on document creation. But, I need to understand the business benifits of implementing Extended Classic Scenario as opposed to Classic Scenario in SRM. In what business scenario do one suggest Extended Classic.
Appreciate every answer
Thanks
Vijay

Hi Vijay,
The most important thing to consider when choosing the implementation scenario is to consider which system will support the different steps of the procurement process.
In case of the classic scenario, after creation of the request (shopping cart) in SRM, the remaining process steps will be handled / supported in the back-end system (ECC). Goods receipt can be executed in both systems. This would be a good choice if the organization has already an operational back-end system and the users from the purchasing department are already familiar (and happy) with all the MM functionality. SRM will only function as a support tool for administrating the purchasing needs of the end-users in the organization.
In case of the extended-classic implementation scenario the complete purchasing process will be supported in the SRM system (most organizations prefer to use the back-end system for invoice verification). Thus requesters, purchasers, goods recipients etc. all will use the SRM system to support their respective activities. This would be the preferred scenario in case both MM (ECC) and SRM are new to the organisation and will be implemented together.
SRM offers the different users a nicer user interface as opposed to the R/3 screens. Also the (strategic) sourcing capabilities of SRM can only be used when implementing the extended classic scenario. Same for the Suplier Enablement business scenariou2019s. Most are only supported when extended classic is active.
So depending on the intentions of the organization a choice can be made. SRM only as a tool for administrating the decentralized request from the end users in the organization: Classic scenario will suffice. SRM as a tool to support the complete purchasing process, from sourcing till evaluation - Extended classic will be the correct choice.
Regards,
Skander

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

Local contract and classic scenario

Similar Messages

Maybe you are looking for