Impact of activating IPC in classic scenario

Hi All,
We are in the process of implementing SAP SRM Bidding application and we are into SAP SRM 7.01 version with SP012.
We are running in classic scenario.
In case of bidding, in responsee comparison screen - the base price will be displayed along with freight price as net price. For eg base price is 100 and freight is 2% the net price would be 102 and the same is displayed in the std SAP SRM bid comparison screen. However when we implement the bidding engine to our client system, the bid comparison screen net price displays only the base price and freightht is not taken intoaccount. On analysis we found IPC is not activated and only Classic Light pricing is active. We believe this issue would resolve if we activate IPC.
Can anyone please suggest what would be the impact if we activate the IPC for classic scenario?
Your earlier response would behighly appreciated.
regards
Sundar

Hi Sundar,
Activating IPC is always suggested in SRM, simplified pricing(classic light) is actual the exception scenario as far as I know.
You always have the option to change from simplified pricing to normal pricing using IPC. You can change from IPC pricing back to simplified pricing as well.
Regards,
Vidya

Similar Messages

Changing the Global Control of Extended Classic Scenario

Hi,
We are implementing a duplicate scenario, where for a certain product category we will use classic scenario (Only contracts on SRM) and for the others ext. classic scenario (contracts,requisitions and PO's on SRM). I activated the ext classic scenario by flaging it on the customizing. I also read in the documentation that we have to use BBP_EXTLOCALPO_BADI in order to determine which category will be handled in which scenario.
Did anybody had experience on this and provide the important points while implementing such a scenario?
Thank you in advance,
If you need to forward details, [email protected]
Message was edited by:
Gaia K.

Hi,
Well that quite simple
As you have done it just activate ECS scenario and activate the badi to change to classic scenario with you custom rules (product category...).
As soon as you get the ECS scenario configured, evrything will be ok for classic scenario.
Kind regards,
Yann

Extended Classic Scenario not creating backend PO

Hi All
We are just starting with SRM (Using SRM 5.0 SRM Server 5.5) and trying to decide to use Classic or Extended Classic.
I can get the Classic working were an approved SC creates a backend PO without any problem. However when I switch on Extended Classic the backend PO is not created from an apporved SC.
In RZ20 my error is Shopping cart 1000000080 (PReq. ): BBP_BD 002 Buffer table not up to date and Table BBP_DOCUMENT_TAB is empty
In config I activated the extended classic scenario as well as activating the backend purchasing groups as responsible. Under sourcing I also defined for the relevant product categories as "1 - Sourcing Never Carried out"
Am I missing something obvious??
Many thanks for any help.
Daniel

Hi Daniel,
In reference to the info. you have provided, it looks like you have not switched to Extended Classic Scenario properly.
Once you say you are on ECS, the P.O should get created in SRM and the copy of it should get replicated to R/3.
As you said you have flagged both the check boxes in SPRO for ECS activation, try activating sourcing also.
SPRO > IMG > SRM > SRM Server > Sourcing > Choose one Product category for which you want to create shopping cart and set the setting as " Sourcing Always carried out".
Check whether the approved shopping cart is coming to Sourcing cockpit or not.And from there try to create a P.O by assigning vendor.
Also ensure that no BADI is activated which converts ECS to Classic scenario for the Product category you have choosen.
If this cycle woks then definitely what you require will also work.Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

How to activate classic scenario?

Dear experts,
What are the generic settings required to activate classic scenario?Are there other settings required other than below?
1. If extended classic scenario is not activated in global mode:
a. Replicate product categories from ERP backend to SRM system.
b. Define an ERP backend system as the target system for the product categories.
c. Define backend Objects for the product categories (based on Purchasing group and source system).
Does any additional settings required for classic scenario?
2. If there is global activation of extended classic scenario?
a. In such cases, We need to take care of BAdi 'BBP_EXT_LOC_PO' and 'BBP_Det_Logsys'.
Do we need any other additional settings?
Thanks in advance,
Ranjan

Classic scenario is the default scenario unless you have activated the Extended Classic. If you do not need Extended classic then you do not need to activate the Extended Classic and deal with BADI's BBP_EXTLOCALPO_BADI, BBP_TARGET_OBJECTS,BBP_TARGET_OBJTYPE.
If the need is only to implement Classic Scenario accross the board then the steps are good to start with.
Regards,
Surya

Classic scenario - Sourcing

Hi,
I read that in a classical scenario, purchasers do not have to added to the purchase group in the org structure.
The purchase group mereley exists to transfer the P Ggp value to the backend system.
In this case if courcing is activated in the classical scenario, there would be no purchaser responsible for the backend PGrp.
To who will the request be forwarded?
Thanks,
Vignesh

Hi
one purchaser might be repsonsible for one product category .
you might entered responsiblity TAb for purchase group
under this you have responsible product category
whenever no source of supply is there , it goes to purchaser of responsible product category.- if you do soucing configuration.
simply when you see purchase group in the basic data click one binocular , you get purchaser name of pg .
br
muthu

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

IPC 4.0 in Classic Scenario

Hi All,
We need to bring in Material Master picing (moving average prices) from R/3. These prices should default when we use the "Internal Products" feature in Shopping Cart. Will this get affected if we drop IPC?
We are working on SRM 4.0 and are thinking of dropping the IPC 4.0 and use the BADI (Simplified pricing) to achieve our pricing functionality.
In classic scenario i am aware the IPC is not needed. CAn somebody explain to me the pros and cons of dropping the IPC from our system landscape in a classic scenario and also is it possible to achieve the "moving average price" requirement mentioned above without the IPC??
Can somebody throw light on this matter. There is a program to get the backend prices? Would that be sufficient to bring the moving average price when run as a background job?
Thanks
Sundeep

Hi Sundeep,
1- As you already know it, IPC is not mandatory for classic scenario
2- EBP_GET_BACKEND_PRICES is the program you are looking for (get prices from backend).
3- In R/3, price can be different per plant.
4- As far as i know, you cannot use badi to achieve this feature in SRM 4.0, as price tables are not included in the badi.IPC could handle this.
6- If PIR or backend contracts cover your requirement, you don't need IPC.
If you want to handle your own specific logic, IPC can help you to achieve it.
Kind regards
Yann

Conditions in Classic Scenario without IPC?

Hi !
I would like to know if possible to work with conditions in SRM without the IPC. Is it possible?
There will be like 4 or 5 conditions, like freight and other purchase costs.
My SRM version is 5.5. We are using the classic scenario (purchase order is being create only in ECC not in SRM).
Thanks in advance.
Rodrigo

can you please share how this has been resolved and we have similar scenario and trying to find solution
Vijay

Selective activation of classic scenario

Dear Experts,
One of my client has globally activated extended classic scenario. Now, they want to activate classic scenario for one particular product category. How they will achieve that?
Which BAdi they need to take care? Is BBP_Determine_logsys is enough?
thanks and regards,
Ranjan

Hi, we have implemented BBP_EXTLOCALPO_BADI, and when we create PO from SOCO everything works fine.
But when we create PO from vendor Bid, with "Create PO" button the BADI BBP_EXTLOCALPO_BADI doesn´t execute.
Can you help me please?
Thanks in advance.
Best Regards.

SRM 7.0 Unable to create PO - Classic Scenario.

Hello,
We are able to successfully create the below scenario.
PR in ECC --> Get PR in SRM --> Start Collective processing -> Transfer to Central System (SC is created for the PR @ this time) --> Create RFx --> Rfx Response --> Create PO. (PO is created in ERP, Classic Scenario)
We are able to get the PR & we are able to create SC successfully and the PR/ SC is available in Sourcing cocpit.
Able to create RFx --> Rfx Response.
Now once the RFx Response is Accepted --> We go for creating PO.
Classic Scenario.
The error is due to pricing - debugged and checked as mentioned in my earlier message.
IPC pricing is switched off and the BADI for simple pricing is activated.
Error : " Message A BBP_PD 396 cannot be processed in plugin mode HTTP "
But this is due to pricing is what i guess.
Error is raised in FM "BBP_PDPRC_UPDATE".
Kindly Suggest.
Unable to Create PO
Regards.
Edited by: Purshothaman P on Jul 6, 2010 1:50 PM

Hi,
Please check and run the following reports (se38): BBP_CND_CUSTOMIZING_CHECK & RSVMCRT_HEALTH_CHECK and post back the results.
Note for BBP_CND_CUSTOMIZING_CHECK also run 'Simulation of Pricing with Manual Price' (scroll down after executing the report initially).
Also the badi information you activated tells us a lot. Although i take it that you executed and read everything that's included in the transaction information. The following sentence gives a prety doubtfull feeling for the CPPR scenario to work for your configuration:
SAP recommends using this BAdI only in exceptional cases and only after checking thoroughly if it is compatible with the Business Scenarios used.
Note: From what i've just read IPC has to be disabled, certain badi's etc. need to be disabled. And VMC (sap basis) has to be configured. Please view: [http://help.sap.com/SCENARIOS_BUS2008/helpdata/EN/9C/F90B7CB34A4889935D1733C6756D5B/content.htm]
Could you also please check and provide whether 'normal' SRM classic scenarios like: SC -> PO do run within your system. Also the error and information you have provided is very little.
Kind regards,
Tim

Convert classic in extended classic scenario

hai,
i wanted to convert classis scenario into extended classic scenario.what are all the steps that i needed to be follow.does it require any implementation of badi?how the po will be sent to the r3 in display mode?
could anyone give the solution
Edited by: chakradhar nannapaneni on May 11, 2009 12:45 PM

Hi,
1.     Activate the extended classic scenario
When the extended classic scenario is set, SRM generates a local purchase order for each item in the shopping cart. All follow-on documents are created in the backend system as well as locally in the SRM
2.     Activate IPC pricing
Since SRM 3.5 IPC (Internet Pricing Configurator) pricing is mandatory for extended classic implementations.
In the classic scenario you can replace the IPC by the simplified pricing
IMG SRM: Sap Implementation Guide  Supplier Relationship Management SRM Server  Cross-Application Basic Settings  Activate Extended Classic Scenario
IMG SRM: Sap Implementation Guide  Supplier Relationship Management SRM Server  Business Add-ins for SRM Pricing
Check whether the BAdIs relevant for the pricing are activated correctly and filled with the correct coding:
BAdI                                     I            PC Pricing (Extended)          Simplified Pricing (Classic)
BAdI: BBP_PRICEDATA_READ
Implementation:. BBP_PRODUCT_PRICE                     Not active         Active
*BAdI: PRODUCT_UPDATE2
Implementation. IPC_UPD_PROD_BUFFER2     Active         Not active
Regards,
Abraham

Pricing in Extended Classic Scenario.

Dear SRM Experts,
System: SRM Server5.5.
Technical Scenario: Extended Classic Scenario.
I have done base line configuration in SRM server. IPC ia active.
[A]
What configuration need to be done for pricing i.e CALCULATION SCHEMA in Ext.Classic Scenario?
""" I have maintained Number Ranges """""""

Also what configguration needs to be done for IV?
"""I have maintained Number Ranges for local Invoices"""
[C]
How will accounting entries be made in R/3......do i need to maintain any attributes or any configuration?
I will reward points for all helpful answer.
Best Regards,
ANIL RAJPAL.

Hi Anil,
The majore part of pricing is in SD or CRM area right and for that they are using IPC, in SRM we are also using the IPC for the pricing which we need to pull from R/3 and used in SRM system.
For Configuring the IPC u need to config following settings.
1) IPC should be up and running.
2) Go in SPRO-> SRM server-> Cross Application Settings-> Pricing->Process Condition Types->Process Calculation Schema->Process Condition Groups->Check Technical and Customizing Settings for Conditions.
These are the basic setting u need to do for running IPC.
BR
Vijay Mittal
Please award the points if it solve ur query.

Conversion of classic scenario into extended classic

hai,
i have configured classic scenario.now i wanted to convert classic into extended classic.what are all the things i need to do?do i need to close all of my shopping carts?do i need to implement any badi?what are all the modifications i have to do in organization structure and attributes?do i run any reports for extended classic scenario?could any one help me to find out the solution.
thanks and regards
chakradhar

Hello Chakradhar,
These pointers will help.
A. Activate the extended classic scenario
SRM: Sap Implementation Guide  Supplier Relationship Management SRM Server  Cross-Application Basic Settings  Activate Extended Classic Scenario
B. Activate IPC pricing
C. BAdIs relevant for the pricing are activated correctly BBP_PRICEDATA_READ; PRODUCT_UPDATE2
D. SRM-SRM server-Technical basic settings-Define backend system for product categeries- SRM system as target system
E. Number Ranges
Check your business requirements, one of the good idea will be to switch the extended classic scenario only for a particular set of categories need ECS. you can have both scenarios,with deciding factor as product category.
Thanks
Ashutosh

Backened documents are not getting updated in Classic Scenario

Hi,
We are using SRM 7.0 version and we are working on classic scenario where the shopping cart - RFX - Contract are created in SRM and the PO - GR - IR are created in ECC. The blackened documents which are created in ECC PO - GR and IR these documents are not getting updated in SRM system.
Is there any business functions to be activated.

Hi Sunil,
You manually run report ""BBP_GET_STATUS_2" after PO is created in MM. Then check if the follow-on-docs are updated in SC.
If it is working fine after you manully run report, you will have to properly set time to run this report automatically.
Best Regards,
Anu
Edited by: Anuradha UG on May 18, 2010 8:09 PM

PO error - extended classic scenario

Hi Guys,
I'm using SRM 5.0 with extended classic scenario...
During creation of the purchase order locally (in SRM) I got the "error in process" status.
My means of T-code RZ20 I got the following info to ithis error:
context:B2B Procurement
object name:Purchase Order
short name: Backend application errors
status: Active
Alert text: PO 700..1: Call of a method or kernel Method that has not been implemented
using Transaction BBP_PD I got the following status:
Status: I1080
Description: in transfer to execution system
Do you have any idea what should I do in order to resolve this outstanding issue?
many thanks in advance for your help.
regards,
Piotrek

Hi
Go to transaction - SPAM to get all the required Patch levels and other required system version details.
Meanwhile, try the following SAP OSS Notes as well ->
Note 508972 - Error during transfer of extended purchase orders
Note 881650 - Duplicate transfer/output of the purchase order
PO status in " error In Process ".
Error in Transfer Process (Urgent )
FOLLOW ON DOCUMENT NOT CREATED ( ERROR IN PROCESS)
Hope this will help.
Regards
- Atul

Impact of activating IPC in classic scenario

Similar Messages

Maybe you are looking for