Shopping Carts from Classic to Extended Classic

We are contemplating to move from Classic 5.0 to Extended Classic 5.0 scenario, would like to know on the Shopping Carts created in Classic scenario behave when copied into new carts in ECS?
Will all the previously created shopping carts be available in ECS?
Can user copy/edit/approve the previously created shopping carts which are yet to be approved in Classic scenario?
Will Buyer be able to create PO in ECS for the shopping carts which are in approved status in Classic scenario?
Thanks
KB

Dear Kiran,
as the scenario is determined only in the SC transfer, you won't have problem neiter with the approval of the existing SCs, nor with the copy of the old SCs.
The SCs which were created before the change and have already the status transfered (I1111) will stay the classic scenario, the rest will be (after the change) extended.
Kind regards,
Peter

Similar Messages

Switch from classic to Extended Classic Scenario- Impact

Hello,
We are proposing to switch from Classic to Extended Classic Scenario.
We are on SRM_SERVER 550,Sp7 and SAP 4.7 backend.
We want to know if this is technically feasible to switch and have less/no impact on existing transactional data and master data.
Main concerns are: Existing open Shopping carts and PO's.
We are also modifying the WF by including buyer completion WF.
Will the carts created in classic scenario and 'awaiting approval' work similarly in ECS?
Can we copy old carts (created in classic scenario) into new ones in ECS?
Are there any other issues like the ones above which people have come across?
Is there any standard SAP material/Consulting note available
which gives some guidelines for switching scenarios?
Regards,
Srivatsan

Hello,
You can switch from the classic to the extended classic scenario by making the global settings in the IMG.
But it would be better if you can decide if only a particular set of categories need ECS.
If you wish to have both the scenarios,the deciding factor is the product category.
You can also activate a BADI for the control of ECS despite the above Global settings.
Reward if answer is helpful,
Thanks & Regards,
Nagarajan

Migration from Classic to Extended Classic

Hi all,
I would be grateful if you could let me know what is technically involved in migrating from classic to extended classic. We are using SRM 4.
I would also like to know how long this would take and any cost information and an impact on any current master data and new data that would need to be set up.
Many thanks.
Jeff.

Hi,
Pls see the foll thread:
Switching between Classic and exended classic
Related threads:
Classic / Extended Classic Scenario for Shopping Cart
Switch from Extended to Classic ?
Change from ECS to Classic Scenario
BR,
Disha.
Pls reward points for useful answers.

Switching scenario from classic to extended classic

Hello Folks,
Hope everyone is well.
I would like to switch our scenario from classic to extended classic. I have set the flag in table V_BBP_EXTPO_GL - Extended classic scenario active.
Now when I try to create a Shopping Cart I get the followng errors.
No organizational data exists on item level -
Vendor 0000401968 not intended for purch. org
I have looked at all my config and cannot see anything obvious.
Any help would be greatly appreciated.
Thanks
Dave

Hello Dave and Vadim,
Attention, prior to the new possibility to use backend purch groups for Extended Classic Scenario, this erroneous solution was commonly implemented.
DO NOT define a local purchasing organization & group. In that case, you will have to:
- complete all the supplier purchasing views for this local Purch org
- define new org IDs and responsibilities
- can not use same purchaser user ID for both org IDs !!
To avoid this, you simply have to implement the BADI to determine the Purch Group. In this BADI, you can copy/paste the standard code of Purch Group determination (find the function module), and just get rid of the logical system in this determination. So backend purch group become eligible.
Kind regards
Christophe

Technical Scenario Switch: From Standalone To Extended Classic

Hello,
Currently we are preparing the system to change the technical scenario from standalone to extended classic (SRM 4.0)
While the Customizing steps are clear, it isn´t so clear how the data that already exist in the system will behave after the scenario switch.
Before the scenario switch, the purchasing department is closing all open SRM local purchase orders.
Someone has already done this kind of scenario switch?
What were the problems you encounter?
Regards.

Hi
Before talking about de-activating ECS or not in this BADI, this scenario must first be activated.
This is done via the customizing point "Activate ECS": just flag the check-box, and all you classic items (i.e. those for which a backend has been determined) become extended classic.
Here is the SRM - IMG path:
SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
You can then fine-tune the scenario by using the BADI BBP_EXTLOCALPO_BADI.
Note- The BADI BBP_EXTLOCAL_PO_BADI can be used to activate the classic scenario based on the proguct categories .
You can choose to have the 3 scenarios working on the same SRM system depending on product category (standard) or any other business rule through the BADI BBP_EXTLOCALPO_BADI. The BADI is mandatory if you want the Classic and the Extended Classic to work together
Exactly, this BADI allow you to implement your own business rule for backend determination in a multiple Backends environment (Standard customizing is only based on Product categories)
As soon as you use BADI BBP_EXTLOCALPO_BADI , you don't have to use the ECS scenario activation customizing point (the rule is overwritten with the BADI result). The BADI BBP_DETERMINE_LOGSYS will only help in your case, if you have several Backend where to create PO documents.
PS: be aware that in ECS scenario you will no longer be able to create PR or reservations in R/3.
Other related links ->
Classic Scenanio and Extended Classic Scenario
Extended Classic vs Standalone
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Classic / Extended Classic Scenario for Shopping Cart
Do let me know.
Regards
- Atul

How to debug a failed shopping cart transfer to ECC in classic mode

Hello,
I am using SRM 5 in classic mode, connected to ECC 6.0.
I have an error message in the administrator monitor that tells me a transfer a shopping cart to ECC has failed.
"Shopping cart 1000000123: Error creating the follow-on document"
(Message is BBP_PU 367)
This is located in the "local errors" section of the administrator monitor.
The follow on doucment will be a PO in ECC.
This message does not tell me the cause of the problem therefore I need to retrnsmit the cart and debug to find the error message that is being returned from ECC.
I have browsed the forum and there are various answers about debugging but but have not found exact instructions on how to debug, and it is now always clear on whether the instructions apply to classic or extended classic.
I have seen reference to the method in note 539978 that creates test data with FBGENDAT for the ECC BAPI. However this method does not seem suitable for a production system because it will interfere with all shopping carts being transferred while the shoppign cart with the problem is being debugged.
Therefore I would like to debug in SRM just for the shoppign cart with the problem.
Hopefully this thread will become the defintiive poitn of reference for debuggin a classic shopping cart transfer to ECC in SRM 5.
I propose to use function module BBP_PD_SC_TRANSFER to transfer the shopping cart again by entering the shopping cart GUID.
Question 1) Can this error message be returned by checks in SRM before the BAPI is called in ECC? If so, where do I place a breakpoint to find the error determined by the checks in SRM?
Question 2) If the system is getting as far as calling the BAPI in ECC, is it possbile to find the error message passed back from ECC by this approach, given that the actual transfer is carried out by the spooler?
Question 3) If this approach is valid, in which method/function module do I need to place a breakpoint, at which statement is the error message passed back to SRM from ECC?
Your help would be appreciated,
Reagrds

Hi Paul,
a small correction to Dishas comment:
The class CL_BBP_BS_ADAPTER_PO_CRT_470_1 is used for the backend release 4.7, so it is not relevant for you. Instead of this, you have to take the CL_BBP_BS_ADAPTER_PO_CRT_ERP10 and method CREATE_DOCUMENT. This is the last step, before the SRM calls the backend system.
From the alert "local errors" I suppose, that there is an error in the SRM customizing (in case the error message comes from the backend system, you get the message into the "Backend Application error").
Typical customizing error, when e.g. the number range of the purchase REQUISITION is not correctly customized (in case the prerequisits for a PO are not fulfilled, the system tried to create a purchase requisition). See the note 1173815 regarding this problem.
Back to your questions:
The activating of the FBGENDAT was a good idea, but I would give here two hints:
- I case of production system you can use only the "Mode B".
- Activate the FBGENDAT only for a short term:
-- at first set the breakpoint in the method CREATE_DOCUMENT (as above described)
-- execute the BBP_PD_SC_TRANSFER
-- you will be stopped at the breakpoint.
-- Now you can activate the FBGENDAT in the backend
-- go on with F8 in the debugger in the SRM system
-- >>> test data will be filled in the backend system (BAPI_PO_CREATE1)
-- deactivate the FBGENDAT
You can do this in one min. and the worst what can happen is that you have 2-3 test data in the BAPI_PO_CREATE1 additionally to the erronous SC.
Question 1) Can this error message be returned by checks in SRM before the BAPI is called in ECC? If so, where do I place a breakpoint to find the error determined by the checks in SRM?
- Maybe... Places for setting breakpoints
-- FM "BBP_PD_MSG_ADD"
-- System command "RAISE"
-- FM "META_BAPI_DISPATCH" (typical problem, see above, and also the note 1173815)
Question 2) If the system is getting as far as calling the BAPI in ECC, is it possible to find the error message passed back from ECC by this approach, given that the actual transfer is carried out by the spooler?
- Yes, you can find the message in the:
-- Test data of the BAPI_PO_CREATE1, if you have activated the FBGENDAT
-- In the method CREATE_DOCUMENT if you "comes back" from the RFC call from the backend
Question 3) If this approach is valid, in which method/function module do I need to place a breakpoint, at which statement is the error message passed back to SRM from ECC?
- see above, CL_BBP_BS_ADAPTER_PO_CRT_ERP10 method CREATE_DOCUMENT
Kind regards,
Peter

Classic scenario & Extended classic scenario

Hi Experts ,
I am new to SRM , Is it possible to combine both classic scenario & Extended classic scenario . if it possible , then how to achieve this .
Regards
Vel.

Hi Vel
I suggest that instead of checking the possibility of implementing any combined scenario's like how you have asked ( Classic+Extended classic scenario).
You need to map the Business requirement and how the Business teams wanted to handle the PO ,GR etc and accordingly you have to plan for implementation scenario. You can' customise the standard SRM delivered options for these scenario . I t is advisable to either go for Classic or Extended classic.   But combination of Classic & stand alone scenario is possible.
for your ready reference i have given below capabilities of all scenarios, which you may already know..
Key implementation scenarios
u2022     Classic
o     Implement EBP and one or more ERP system . All shopping carts refer to MM process in your ERP backend, your   ERP is the leading system. GR (Confirmations and invoices can be entered in Enterprise Buyer or ERP back end system
u2022     Extended classic
o     Purchase order is created locally within EBP system , if the data in the shopping cart is insufficient to generate a complete purchase order. The data is supplemented manually within the enterprise buyer system EB is the leading system , GR,IV can be done in both EBP and ERP system.
u2022     Decoupled
o     Combination of classic and standalone scenario ,some items are locally handled, some items are transferred to the ERP back end system
o     We are able to send PO from both the system.
u2022     Standalone
o     Your SC items create local procurement only, this means all the follow on doc like GR,IV will be done at EB system only.
o     Only commitment & invoice posting will be done at ERP backend
You can get the final Business requirement and plan.
Regards
Narahari

Material price to be defaulted in shopping carts from Contracts in ECC

Hi Guys,
We are having a scenario wherein we need to get the price in shopping cart from contracts in ECC.In our case for a material only one contract exists for a given time frame in the ECC.We are working on classic scenario in SRM 5.5 as an add on to ECC.Any help to get this working will be highly appreciated.
Thanks in advance.
Regards,
Pawan.

Hi Pawan,
As long as you dont have the Configuration Step "Sourcing Via Vendor List activated", all contracts that you have created for a material will automatically show up in the source of supply as the proposed SOS. This and Info records are displayed on the SOS tab on the SRM Shopping cart via an RFC call that Standard SRM Does.
Pls try out a scenario:
1.) Create a contract for a material in ECC
2.) Replicate the material in SRM
3.) Create a Shopping cart in SRM with that material
4.) you will automatically see the contract beoing displayed on the SOS.
Following are the pricing priority in SRM.
Price Determination in EBP
Priorities
1.) Manual price (only if field is open for input)
2.) Contract
3.) Catalog
4.) Price from product linkage or from product
So as long as you dont have a manual price for the Shopping cart, the price will be adopted from the contract. i would suggest for materials with contracts, update the s/c price with the BBP_DOC_CHANGE_BADI at the time of submission with an RFC call to ECC to obtain the right proce from the contract.
Hope this info helps !!
Pls assign points, if answer helps you
Sundeep

BADI for Classic and Extended Classic Scenario

Hi,
   Please   provide list of Reports and BADI's for
       Classic and Extended Classic Scenario.
Thanks,
Srini

Hi,
In SRM there will be a number of BADI's are Available, We can utilize them according to the requirements
As per the request few important BAID are provided below..
Workflows
1). BBP_CHNG_AGNT_ALLOW:          Allow / Allow Change/Add Approver
This BADI is implemented not to allow users to change the approvers in the workflow.
2). BBP_WFL_SECUR_BADI:          Overwrites the authorization level of the approver
This BADI controls the restart of the workflow
Purchasing Related
1). BBP_PGRP_FIND:               Shopping Cart: Determine Responsible Purchasing Group(s)
This determines the responsible purchasing group for the shopping carts.
Shopping Cart Related
1). BBP_SC_MODIFY_UI:          BADI to Change Shopping Cart Layout
2). BBP_GROUP_LOC_PO:          Exit Grouping of Items for Local Purchase Orders
This splits local PO if more than one contract in a PO.
3). BBP_TARGET_OBJECTS:          Exit while determining target objects in backend
4). BBP_WF_LIST:               Change Worklists and Search Results Lists
This is used to restrict the search results for the user.
5). BBP_CTR_BE_CREATE:          Exit when Creating a Contract in the Backend System
6). BBP_CREATE_PO_BACK:          Exit while creating a purchase order in the backend system
This BADI is used to add the shopping carts attachments to the PO and also to make adjustments in payment terms, currency etcu2026
7). BBP_DOC_CHECK_BADI:     General BAdI in Cross-Check for Message Returns
8). BBP_DOC_CHANGE_BADI:     BAdI for Changing EBP Purchasing Documents
9). BBP_ECS_PO_OUT_BADI:     ECS: PO Transfer to Logistics Backend
Thanks
prasad .s

Conversion of classic to extended classic

hi,
i wanted to convert from classic to extended classic scenario.so what can i do to that?already activated simplified pricing.now how can i activate the ipc pricing?do i need to implement any BADI for po pricing conditions and for organization structure maintenance.kindly help me to solve my issue?
thanks,
chakri

Hello,
Check the following URL. It provides some information about pricing and IPC:
http://help.sap.com/saphelp_srm40/helpdata/en/72/f40f3c98ddaa4ce10000000a11402f/frameset.htm
Additionally, 637562 can be helpful.
Kind regards,
Ricardo

Creation of Shopping cart from CPPR

Hi,
While creating shopping cart from Collective processing, we have implemented BBP_DOC_CHECK_BADI for validations. Now, after this BADI, in the standard process the messages are being appended in the /SAPSRM/IF_SOA_MSG_HNDL~GET_ERROR_CODE. The creation is failing in Quality system but it is successful in Development system. Can you please tell me reason for difference in Error Handling process in both the systems.
The messages are getting cleared in Development system in BBP_PDH_MSG_INTERNAL_SAVE while in Quality system, it is not getting cleared. I found a parameter IV_METHOD in this FM and the sequence of calling this FM with IV_METHOD is differing for both. Are there any SAP notes?
In Brief,the error message from the BBP_DOC_CHECK_BADI Implemention are being cleared in Development system and not getting cleared in the Quality system.
Please provide me some points to resolve this.
Thanks inadvance,
Deepthi
Edited by: Deepthi B on Sep 29, 2010 1:02 PM

Hi Dennis,
I really appreciate for quick response. Please input your feedback on the below situation:
We are currently using the shopping Cart DSO along with PO Account Assignment DSO for reporting (on Multiprovider). Due to heavy load and constant change in user requirements there have been performance issues in the past. Now the end users want separate reports on Shopping Cart and PO Account Assignment. So I came with up the idea of building the Cube on top of Shopping Cart DSO and then built separate Report.
Present situation of the report:
Variable Entry:
Created on Date, Cost Centers, Internal Orders, Purchase Group, SC Created By, Goods Recipient, Requestor, Vendor
Some of the Characteristics we are using in report:
Shopping Cart Date, Shopping Cart Number, Purchase Order Number, SC Created By, SC Requestor, Goods Recipient, Purchasing Group, Controlling Area, Cost Center, Chart of Accounts, G/L Accounts, Order, Vendor, PO Line item Number, SC Item Number, SC Status, Shopping Cart Name & many custom fields pulled from the SRM system.
Please let me know for this scenario the good practice (Reporting on DSO or CUBE)
Thanks,
SAPBWI

Error When Create Shopping Cart from catalog SRM

Hi all,
Currently, I have problem need your help.
I tried to create an shopping cart from catalog. But I don't know how the G_L_ACCT was lost.
The information about account like this:
Now, I want to know where this data is selected. Would you please help me for this issue.
Extra Information: Acc_cat = 'A'.

Dear Melynessa: normally you should not get this error message when flagging "Order as Direct Material" in SRM 7.0.
Please, check in your backend ECC6 if "Value updating" flag has been selected or not for the material type of your SC material ID under the IMG path "Logistic - General --> Material Master --> Basic Settings --> Materual Types --> Define Attributes of Material Types"
If field "Value updating" for material type is not flagged then, when creating a PReq or PO in SAP ECC6, you will get always an error message asking you for an account assignment.
Due to the circumstance above, in SRM, materials ID belonging to non-valuated material types should not be ordered as direct (flag order as direct is available always when you enter a material ID, even when it is non-valuated). If you flag the field "Order as Direct" for a non-valuated material, standard SRM system doesn't issue any error message. So, maybe, there is BAdi in your SRM system checking the "Value updating" for material type and avoiding "Order as Direct Material" flag being selected when it is a non-valuated material
Hope it helps.
regards
Valentí

Shopping cart from catalog in sourcing cockpit

Hi experts
I have a doubt when I create a shopping cart from a catalog it's going to sourcing cockpit of the buyer I am in SRM 5.5 ECS, I have configuted in customizing for soucing option 5 Aut Grouping . Sourcing for itens whithout assigned souce,
It must send for soucing cockpit only itens without source.
Someone knows how to solve it?
Thanks
Nilson

Hi
Which SRM version are you using ?
This is correct.. It's standard functionality... For every shopping cart, created from catalogs, the SOS (Source of supply) - Vendor will always be available.. (Until and unless you have activated any other Active BADI) and once the Shopping cart is complete and is ordered... It will directly by pass the buyer and will directly go the Approver for Approval, if required.. Otherwise, Back-end document (PO, Pur Req.. etc ) will get created...
Do let me know.. Incase you still face any issues.
Regards
- Atul

Classic and extended Classic.....

Hi Guru's
Can we have classic and extended classic together..If yes what settings need to be done and how based on what system will diffrentiate the follow on documents creation.
Thanks in Adv.
IS

Yes, this can be achieved. By default you have to activate Extended Classic Scenario in the system. But using the BADI BBP_EXTLOCALPO_BADI, you can switch to Classic Scenario based on your requirement.
For more details please check documentation here in your SRM system
SAP Implementation Guide ->
Supplier Relationship Management ->
SRM Server ->
   Business Add-Ins (BAdIs) ->
    Control Extended Classic Scenario ->
     Activate Extended Classic Scenario
Regards
Kathirvel

Delete Shopping cart from Sourcing cockpit?

Hello,
Someone know if I can mark for delete or inactivate a shopping cart from the Sourcing cockpit?
Regards,
Marta

Hello Shiv,
Thank you very much for your help.
I do not see the boton ACTION
In Tran SOCO - Carry out sourcing - In the worklist view there are two zones:
1. Overview of Requirements.
Description
Category Quantity
Requester
Name of Vendor
Requirement Contract
Bid Invitation
Info rec.
Auction
Manufacturer Part Number
Manufacturer
ACTIONS
There is a drop list called Display. But I can not select data here. The drop list is empty. So I can not select from there.
I select the SC's from the view "Find" and then Actions colum disappear.
2. Work Area
Propose Sources of Supply
Create Purchase Order
Submit to Grouping
Create AUCTION.
Create Bid Invitation
Create Contract
Hold
Remove From Work Area.
In the work area I do not see ACTION button
Can you help?
Cheers,
Marta

Approval of shopping carts from the past

Hello,
We have the following situation:
A approval-user (manager) has in his approval list (BBPSC07) shopping carts to be approved from months September and October 2008. These shopping carts are in the past (actual date 30.10).
The user can enter into the approval details of the shopping carts from months October but cannot do this with the shopping carts from September!
What could be a reason fro this behaviour of the system?
Thanks for any clues,
Aart

Hi Masa,
Im talking about the approval overview screen where one can press a button "details" of the approval, or "accept" or "reject" a shopping cart.
Pressing the detail button does no lead us to the shopping cart positions to be approved or rejected in the case of shopping cart dates before the month of Octobre.
From october onwards the overview is working fine!
What could be a reason for this behaviour?
thanks for any clue.
Aart

Shopping Carts from Classic to Extended Classic

Similar Messages

Maybe you are looking for