Customization step for classic to extended classic

Hi,
Currently I have implemented classic scenario in SRM 7.0 with ECC in back-end. Now I am planing to implement extended classic scenario. In the same time we are planning to continue the classic scenario for some product category. In breif: Purchase order will be either in SRM or ECC base on product category. Please guide me let me the necessary customization setting for implementing the abover scenario.
Thanks
Regards,
Jennifer

HI,
Please activate extended classic in SRM
SPRO: Cross-Application Basic Settings->Activate Extended Classic Scenario
SPRO: Business Add-Ins->Control Extended Classic Scenario (here you can control if you need PO in SRM or ERP)
Number range, tranaction types to be configured according for SRM and ERP
Regards
Sam

Similar Messages

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

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

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

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

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

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

Customization step for in New Plant in production planning.

Dear Experts,
Thanks for your continues support from SCN.
My company having one of the production process unit.
Already some plants (1000 ) are assign the process order customization. But currently include one additional plant ( 1001) for process manufacturing.
Basically create order type, production scheduler, production scheduling profile these are all the main thing, other wise what are all the assignment to be ensure , create and followed.Kindly send me the customization step for each assignment in our new plant.
( order creation to end of the account settlement itself)
I am waiting for your valuable feedback.

Hi Anil,
if all master data configuration is over in the new plant, you can proceed to crteate the required cofiguration for new plant.
if your production process is similar across all plants then you can simply copy all the required things from your old plants, or if the process is different in the new plant you have to configure the required settings.
as you asked what are required settings apart from Basically create order type, production scheduler, production scheduling profile these are all the main thing,
apart from above things. actually the configuration is depends on your Production process which you Follow in your business. as standard process starts from Configuration od SOP And Transfering Demand To MRP and Running MRP then executing the results of mrp in this case we need to configure SOP And MRP Settings First then remaining Production process configuration.
can you give the details of your PRoduction process then we can discuss the sequence of required configuration.
Thanks&Regards,
Venkat.

Impacts for switching from Extended Classic to Classic in production

Hi,
Has anyone involved project that customer has switched from Extended Classic to Classic in production system?
SRM 4.0 is live in Extended Classic now.
Customer is going to upgrade and switch their production system to SRM 7.0 Classic.
Main process is
PS -> MM PR -> SRM Sourcing -> SRM PO (Extended) -> SUS PO -> SUS PO Response
GR, Service Entry and Invoice are handled in ERP
I see an issue if we switch SRM-SUS to MM-SUS, SUS PO is created before switch and PO Response is created after switch.
Do you have any lessens and learned topics for switching Extended Classic to Classic? Which documents have to be take care?
Regards,
Masa

I'm also interested in the same question. We plan on going from 5 Extended Classic to 7.1 Classic.

Partner functions OA and IP missing for Vendor in Extended classic PO

As part of current Classic scenario, we have maintained OA (Ordering Address) and PI (Invoicing Party) for a vendor in R/3. We have also maintained different ordering addresses for multiple plants in the Vendor master: Partner functions screen --> Alternative data.
I would like to acheive the same functionality in Extended Classic scenario. We have replicated the vendors from R/3 to SRM. After activating Extended Classic scenario, we see only VN as the partner function in R/3 PO.
Q1. How can we enable OA and PI partner functions in R/3 PO (Extended Classic) ?
Q2. How can we enable different ordering addresses for multiple plants in R/3 PO (Extended Classic) ?

Hi
Which SRM Server are you using ?
You need to maintain Partner Functions in the SRM Server - SPRO Transaction - Configuration Settings.
Here is the Path from SPRO Transaction ->
Supplier Relationship Management -> SRM Server -> Cros Application Basic-Settings -> Define Partner Functions
Maintain Similar entries as mentioned below.
Function Function Type Usage Description Abbreviation
00000016 0013 B2B Requester RQ
00000017 0007 B2B Contact Person CP
00000018 0011 B2B Bidder BI
00000019 0012 B2B Vendor VD
00000020 0002 B2B Goods Recipient GR
00000025 0014 B2B Portal Provider PP
00000026 0008 B2B Responsible Employee RE
00000027 0017 B2B Ship-To Address DP
00000028 0003 B2B Invoice Recipient IR
00000029 0015 B2B Invoicing Party IP
00000030 0018 B2B Ship-From Address SP
00000034 0002 B2B Plant PLNT
00000038 0001 B2B Sold-to Party ORDR
00000039 0026 B2B Preferred Vendor PRVD
00000051 0019 B2B Purch. Org. Auth. For Release AREL
00000074 0025 B2B Service Agent SERV
00000075 0031 B2B Location LOCA
00000097 0034 B2B Invoicing Party Employee IPEm
Hope this will definitely help.
More details ->
For 1), see these links below ->
Partner function missing in backend PO
Re: Error in transmission while PO cration
"Multiple" partner data at PO header
Partner functions in plan driven MM-SUS
Re: Partner function not found
Number range for business partner
Re: Problem with BP. Assignment: Business partner person to user not unique
Error in creation of Employee for Business Partner
Re: enter exactly one partner of type vendor
Re: Business partner as Vendor and Invoicing Party
Partner functions in EBP for extended Classic Scenario
Classic Scenario PO has multiple OA Partner Functions for Vendor
For 2), see the pointers ->
There is an article written by Jason Didday at www.saptips.com entitled "mySAP SRM and SAP R/3 Partner Functions: Supporting OAs, VNs and IPs" that you may find useful.
In SRM, there is no standard relation betwwen plant and vendor master data.
You can use BBP_GET_VMDATA_CF BADI to add backend data in SRM while using BBPGETVD and BBPUPDVD transactions.
Replication of Ordering Address from R/3 to SRM
Re: Adding Partner Function to R/3 PO from SRM in Classic using BADI
Partner function Payee in SRM
Adding Partner Function to R/3 PO from SRM in Classic using BADI
Do let me know.
Regards
- Atul

PO created but Status showing as Awaiting for approval in extended classic

Hi Experts,
SRM 5.0 extended classic scenario,SC approved and PO created but status showing in follow on documents node in SC as awiting for approval.
Can any help in finding solution.Thanks in advance.
Thanks,
Babu

Hi Babu,
I am facing the same issue in the ECS SRM 5.0 after approving the shopping cart the PO created in EBP but the WF status is waiting and PO is not transmitted to R/3. Below is the status of SC and PO in BB_PD. Kindly suggest what could be the problem where i can analyze.
SC
                    Status         Description                    Inactiv
HEADER     I1015          Awaiting Approval              X
HEADER     I1021          Created
HEADER     I1038          Complete
HEADER     I1106          Shopping cart ordered
HEADER     I1129          Approved
0000000001 I1111          Item in Transfer Process       X
0000000001 I1113          Follow-on Document Created
0000000002 I1111          Item in Transfer Process       X
0000000002 I1113          Follow-on Document Created
PO
Stats:
           Status         Description                    Inactiv
HEADER     I1015          Awaiting Approval
HEADER     I1021          Created
HEADER     I1038          Complete
HEADER     I1180          Document Completed
Thanks,
Kannan B

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

Classic and Extended Classic implementation

Hi all,
Can Self service procurement scenario be implemented in classic as well as extended mode?What are the differences in configuration in SPRO?

Hi,
There is no much differences in terms of configuration in SRM system.
for extended classic scenarion SPRO-> SRM server-> cross applications basic setting -> activate extended classic scenario
This setting determines EBP system generates local purchase orders.
If you are implementing Ext classic scenario no need to define the step cross applicatoins -> Define objects in backend system
Using badi BBP_EXTLOCALPO_BADI you can override the setting in extended classic scenario, example: for certain product category using BADI we can create PO in back end system also ( classic scenario ).
Thanks & Regards,
Prasad.s

Classic and Extended classic scenario

Hi All,
Can we have classic scenario for Service procurement (MM-SRV) and Extended classic for direct material procurement in the same SRM system.
This is because Extended classic doesnot support service procurment where as Classic scenario supports
Does any body implemented like this. If so pls let me know Pros and cons
Abdul Raheem

Hi Laurent,
Thanks for reply.
Do we have any limitations if we go by this model like Service procurement by Classic and Direct procurement by Extended Classic.
If any thing breif on PRos and Cons of going by this model.
Abdul raheem

Customization step for classic to extended classic

Similar Messages

Maybe you are looking for