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

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

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

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

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

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

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

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

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

Payment term key with limit days in Extended Classic Scenario

Hello,
We have an SRM 4.0 implementation (SRM Server 5.0 with Support Package
9) using the Extended Classic Scenario.
When a shopping cart is created, it must be approved, and then a
purchase order is generated (first locally at SRM, and then is
replicated to the backend).
The problem is that the payment term key (field at header level EKKO-
ZTERM) of the backend purchase order is empty, only in cases when we use a payment term key which have several different values for the
field "limit days" (T052-ZTAGG in backend, BBP_PAYTERM-ZTAGG in SRM).
Example:
 ZTERM ZTAGG
 K180 09
 K180 19
 K180 31
If the payment term key selected has no several values for the field "limit
days" (one single entry), the payment term key arrives correctly at the backend purchase order.
Example:
 ZTERM ZTAGG
 E000 00
In SRM table BBP_PAYTERM we have upload the backend payment terms
(using report BBP_UPLOAD_PAYMENT_TERMS). In other threads it is said that you must copy the entries generated by the report with the logical system of the SRM system, but in extended classic scenario it seems to be not necessary.
We have already implemented note 846009, in order to use always the backend payment term, but the error didnt get resolved.
We have our vendor business partners mapped to the local and backend
purchasing organizations, but it is only necessary indicate the Payment term key for the Backend Purchasing Organization.
Regards

hi,
Pls see the foll notes:
Note 576349 - Terms of payment in the ECS
Note 541934 - Modification note: Copying base date from T052
Note 953999 - ECS: Terms of Payment values not in PO header
Note 940453 - Backend payment term data not updated in the extended PO
Note 945018 - Incoterms data not transferred to the back end
BR,
Disha.
Pls reward points for useful answers.

Tax calculation in backend and in SRM (classic and standalone scenario)

Hello,
I have an issue regarding calculation of tax. 2 scenarios are used in common: classic and standalone. One node of Organizational structure is using classic scenario, another node is using standalone. So I have 2 Accounting Systems defined (one for each node).
Requirement is:
- For classic scenario, setting the tax calculation in backend
- For standalone scenario, setting the tax calculation to no tax calculation
Problem is that I can not customize the system this way. I do not know any mean to set 2 ways for tax calculation. Would you have any idea to do this?
Thanks,
Patrick

Hi
Please go through this ->
http://help.sap.com/saphelp_srm50/helpdata/en/f4/8b1d40bb37e569e10000000a155106/frameset.htm
Note 848164 SUS3.0: FAQ: Logic of Tax calculation within SUS
958273 FAQ: Taxes in SRM-SUS
999896 EBP tax codes not correctly mapped to back-end tax codes.
908659 Follow-up note for Note 509594
931198 Missing Tax Code in Limit Shopping Cart
430202 Delivery address in shopping cart in BAPIEKPOC
931198 Missing Tax Code in Limit Shopping Cart
881086 Country-specific tax calculation
703292 TAX. Input/Output tax in SAP Supplier Self-Services with TTE
513250 ERS. Tax calculation with the new 3.0 function
390861 Transferring tax table for ERS from backend system
Note 657146 Enhancement for US tax calulation: Functions
510142 EDI-Customizing: Tax code tax-exempted transactions
317040 MR08: Message M8267
49436 MR44: No message if the tax amount is different
Note 84127 Tax Jurisdiction Code for EDI/ALE and Intercompany
Also Try BBP_DET_TAX_BADI.
Regards
- Atul

Limit items on extended classic scenario.

Hi everybody.
We are working in SRM 4.0 with extended classic scenario.
We are testing limit items (not service items), but I can not understand the limit item functionality.
In SC, we can assign contracts form limit items. But when we create PO from the SC, there is not any relationship between PO and contract. Moreover when I create a PO (limit item) from null, I can not assign any contract (field is not available).
In the other hand, in SC (limit item), I can select Follow-Up Actions as Confirmation and Invoice or Invoice. If I select Confirmation and Invoice, when I create a PO, ECC return me a message error, because in ECC, good receives are not allowed for PO with limit item category.
So, I have some questions:
1. Can I use limit items in PO with contract reference?
2. If yes, how can I do it? If not, what is the tab contracts functionality in SC with limit items?
3. What is the functionality to allow confirmations in SC with limit items?
4. Is there any documentation about limit item functionality?
Thanks and regards.
Raúl Moncada.

Hello,
As far as I know, this is a technical limitation. A work around would affect other functionalities.
Note 1358679 corrected such issue.
Regards,
Ricardo

SC with Limit Item using Extended Classic Scenario?

Hello,
Can we implement SC with Limit Item using Extended Classic Scenario.
I mention that we replicate the Product Categories from R/3 backend.
We have tried to create a SC with Limit item, but the data on Quantity, Price and Tax is not picked up at PO level.
Regards,
Shaiek

Hi
Please try out this.
For the time-being,
Try de-activating all the custom BADI Implementations and check, what is happening, in the standard SRM system. How does it behave incase of limit item ?
Incase it works fine, without any Custom Implementation active in the system, I suspect there is something wrong in your current deactivated BADI Implementation.
Since i don't have access to your system , Please paste the code here.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Limit shopping carts in extended classic scenario

How can we implement limit shopping carts in extended classic scenario. Has anyone done it? Thanks in advance

Hi
Which SRM version are you using ? It's possible to implement limit items concept in ECS Scenario.
What exactly you are looking for ?
Please have a look to the following links as well.
http://help.sap.com/saphelp_srm50/helpdata/en/40/654d216f12754e9decdaf4d360bc1c/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/d1/77623c44696069e10000000a11405a/frameset.htm
Few SAP OSS Notes to refer in this case.
Note 712702 ECS shopping cart with several limits
Note 724261 Limit: Error during creation of local purchase order
Note 694442 Limit SC: Customer fields not transferred to backend PO
Note 690000 Limit SC: Customer fields not transferred in Backend PO
Note 699255 Internal note and vendor text for LimitPO and LimitPReq
Note 501977 Error with limit SC: "Unit measure has no ISO code"
Note 520514 Limit, BBP_PD148: No account assignment details were adopted
Note 514727 Limit: Contracts are not displayed in the status
Note 516444 Account assignment check in the shopping cart with limit
Note 515500 Limit:'Confirmation and invoice' indicator not transferred
Note 515695 Invoice entry for limit shopping carts not possible
Regards
- Atul

Limit SC and Classic scenario

Similar Messages

Maybe you are looking for