Reverting to classic scenario in SRM7.1, from PPS and extended classic

Hello Experts,
Recently we have moved from SRM7 to SRM 7.01, in which we can have PPS without Extended classic scenario.
As business wants classic scenario, How can we make the system as classic , in which PPS and extended classic is activated.
any badi is available for this? Please help.
Regards,
Raju

Raju,
Basically you have few points to keep in mind. (yes you need to activate the SPRO config for extended classic, apart from this).
1. switch between extended classic and classic is actually defined by the backend logical system of the document. if thats SRM itself then it follows the path of extended classic or if it is ECC then it follows classic.
because its basically creating a follow on document and that explains the scenario.
2. it also depends on what object are you expecting to be created. from a SC many documents can be created.
a. PO in SRM
b. PO in ECC
c. PR in ECC
d. Reservation in ECC
- so, if you can define at any point that where is your document to be created and what is to be created you can control the flow.
Now to do this. if you have few options.
Option1:
1. set the object types(2) for product categories (config, backend document type).
2. implement BBP_EXTLOCALPO_BADI to switch off extended classic
Options 2:
1. in doc change badi, change the backend destination to ECC
2. in Badi BBP_TARGET_OBJTYPE pass the object type you want your follow on document to be.
hope this explains

Similar Messages

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

Classic Scenanio and Extended Classic Scenario

Hi all,
I would implement on the same system 2 different scenario:
1. Classic Scenario for self service procurement
2. Extended Classic Scenario for the following business scenario:
a. PR from ECC is transfered into Sourcing Cockpit with Plan Driven Scenario
b. buyer convert the SC created in Sourcing Cockpit into a GOA or a PO that are transfered to ECC.
Can coexist this different scenario?
Can I address this different scenario only with organizational differences?
Thanks
Bye
Marco

Hi Marco,
I see 2 quick ways to realise your requirement.
The first is to create an attribute in t77omattr for a position and maintain that attribute in the organisational model. This attribute could just be filled with an X for example.
Then you have to implement BADI BBP_EXTLOCALPO_BADI and retrieve the attribute you created with FM BBP_READ_ATTRIBUTES (use sy-uname to retrieve the attribute for the current user).
The 2nd is to create a Z-table with the user-ids that you want to use the local (or ECS) scenario. Then again in BADI BBP_EXTLOCALPO_BADI you have to write the logic to retrieve and compare this.
Keep in mind that these are user-based distinctions and not based on scenario.

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

Difference between Classic Scenario and Extended Classic Scenario

Hi Expers,
I need your help again........:-)
I just want to know what is the differne between classic and Extended Classic Scenario.
Points will be rewarded
Thank you
sam

Hi Sam,
(explaination frm a previous thread)
Difference between scenarios
WIth classic scenario, the SC following document is to be created in your R/3 backend(s). Thus you can get an PO, a PR or a stock reservation in R/3.
With extended classic the following document is to be found in SRM itself. Thus from a SC item you can get a complete PO, an incomplete PO or depending on your customizing a Sourcing cockpit (now called Sourcing Application) requirement. Additional FM are called when you tick the box "Enable Extended classic" in the IMG activity, enabling you to get a local PD.
If you need to get a stock reservation in R/3 with extended classic, you will have to switch back to classic scenario for the particular category or product with a dedicated BADI ("Control extended classic ").
Be aware that with extended classic, the PO created in R/3 is not exactly a replication. That is a "copy" with that crucial difference that the SRM PO will use a different Purchase Organization that of R/3. It enables you to centralize your purchasing. In SRM you can create a "local" Purch. Org for EMEA zone for instance while in R/3 that is rare you can purchasing above a country (because in the backend you have to produce legal documents related to one company). Those "local" (=SRM) Purch. Org. are required to enable extended classic and it makes simpler Contract management for instance (in classic scenario contracts may need to be replicated to your R/3 back end and adjusted for each back end and each Purch Org in R/3, and even for each plants).
In a nutshell with extended classic you have a PO in SRM, and this PO is assigned to a different Purch Org that of R/3. Purch Org in R/3 are determined on the basis of the "LOcation" (R/3 plant you have replicated from your backent into SRM).
Extended classic is required for service purchasing when you want your requesters to be able to adjust the PO price while they can not access R3. In extended classic, PO is issued from SRM and not from R3.
Please check this too:
http://help.sap.com/saphelp_srm40/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/content.htm
BR,
Disha.

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

Can we use both Stand alone and Extended classic in one SRM system

Hi All,
Our client is now using Stand alone SRM system with back-end R/3 FI-CO system. Now they want to go Extended classic scenario for few product categories.
         Would it be possible to use both in one SRM system? If possible could you please provide what are the sequential steps to do this?
             Thanks in advance.
Regards,
Ram

Hi Ramesh,
How did you end up solving your problem, as i have the same scenario. Did you use this BADI (
SRM Server->Business Add-Ins->Control Extended Classic Scenario->Activate Extended Classic Scenario)? Based on my reading, it seems this BADI is relevant to switch between extended classic and classic scenarios.
From what i understand, we can control the standalone scenario via the define backend system configuration (SAP SRM -> SRM Server -> Technical Basic Settings -> Define Backend System for Product Category). In my scenario, I have one set of product categories, so i will likely need to implement this BADI (BBP_DETERMINE_LOGSYS, method:   DETERMINE_LOGSYS - SAP SRM -> SRM Server -> Business Add-Ins ->Shopping Carts and Requirement Items -> Determine Backend System / Company Code) in order to determine the correct backend system based on company/plant for example.
Did you then leave the extended classic scenario activated (IMG --> Supplier Relationship Management -> SRM Server-> Cross-Application Basic Settings->
Activate Extended Classic Scenario)?
Or how did you achieve both standalone and extended classic using one SRM server?
cheers,
AD

SRM standalone and extended classic

Hi Experts,
Configuration: ECC 6.0 (with Ehp4 installed - (not activated)
SRM 7.0
Just want to seek confirmation of my understanding re: SRM implementation scenarios. Is it possible to have a extended classic and standalone setup using the same SRM server with same client? Both will have the same product categories. These will be for two separate entities/companies.
Thanks in advance.
Regards.

Hi Mike,
How did you end up solving your problem, as i have the same scenario. Did you use this BADI (
SRM Server->Business Add-Ins->Control Extended Classic Scenario->Activate Extended Classic Scenario)? Based on my reading, it seems this BADI is relevant to switch between extended classic and classic scenarios.
From what i understand, we can control the standalone scenario via the define backend system configuration (SAP SRM -> SRM Server -> Technical Basic Settings -> Define Backend System for Product Category). In your scenario, you have one set of product categories, just like mine, so i assume you had to implement this BADI (BBP_DETERMINE_LOGSYS, method: DETERMINE_LOGSYS - SAP SRM -> SRM Server -> Business Add-Ins ->Shopping Carts and Requirement Items -> Determine Backend System / Company Code) in order to determine the correct backend system based on company/plant for example.
Did you then leave the extended classic scenario activated *
MG --> Supplier Relationship Management -> SRM Server-> Cross-Application Basic Settings->
Activate Extended Classic Scenario)?
Or how did you achieve both standalone and extended classic using one SRM server?
cheers,
AD

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

Is B/E ECC SoS in Local SRM PO in Classic Scenario Possible ( SRM7.0) ?

Hi Experts,
We are configuring SRM7.0 with ECC6 ( Ehp4) having Classic Scenario .
Our Ultimate Aim is - To maintain SoS in ONE system only (i.e. ECC) & use the same SoS in both ECC & SRM system, for all documents ( ECC PR, ECC PO, RM S/C, Local SRM POu2026etc )
In Classic Scenario, B/E ECC SoS ( Supplier Contract & Pur. Info Record) are proposing in S/C ( Indirect Mat.) , but these B/E SoS NOT proposing while creating u201CLocal SRM POu201D which is by default Ext. Classic.
We are exploring new CCTR functionality ....but seems complicated and requiered PI...
1.By doing any enhancement , can we pull B/E ECC Contract and Pur. Info Record as a SoS while creating u201CLocal SRM POu201D ?, If it is possible , then we are ready to do any enhnacement and I'll be most happy
2. Which BADi is used while creating Local SRM PO ?
Can anyone suggest/confirm please.
Thanks
NAP

Hello,
In classic scenario, only backend contracts can be used as SOS.
In extended classic, local contracts can be adopted as SOS.
If you are using classic scenario, you should distribute local contracts to ECC. Then, while creating a shopping cart in classic scenario, ECC contracts (which have been distributed) will be considered as SOS.
Regards,
Ricardo

Classic and extended classic scenario with one EBP

Hello Guys
If I have a one EBP and multiple ERP back ends. For one backend, I need to have classic and other to have extended classic scenario. How this can be fulfilled. Is it possible, if so please provide the configuration setup.
Thanks in advance.

Hello,
In BADI BBP_EXTLOCALPO_BADI method DETERMINE_EXTPO.
you can try this.
Structure Declaration
DATA: ls_item_data TYPE bbps_extpo_badi.
Moving item data to a structure
MOVE-CORRESPONDING item_data TO ls_item_data.
SELECT SINGLE LOGSYS FROM comm_product
                                 INTO lv_logsys
                                 WHERE PRODUCT_GUID = ls_item_data-PRODUCT .
If lv_logsys = 'XXXCLNT010' "backend system
      Cancelling the enhanced classical scenario
        bbp_extpo_gl-bbpexpo = space.
ELSE IF lv_logsys = 'YYYCLNT010' "backend system
      Cancelling the enhanced classical scenario
        bbp_extpo_gl-bbpexpo = ' X'.
ENDIF.
Regards,
Neelima

Output from backend in extended classic

Hi Experts,
In extended classic scenario it is possible to sent the output from backend?
Does anyone know have to activate this, and how to deactivate the output control from SRM.
Proces as I want it:
- Creates a shopping cart in SRM.
- Creates a PO in SRM on behalf of the shopping cart, no output.
- The PO from SRM is replicated to R/3.
- The PO is sent to vendor fra R/3.
Best regards
Kim Oster

yes franz is correct. we can do this from consulting note which he mentioned.
PO Output messages for ECS PO's
br
muthu

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

Difference between service procurement classic and extended classic?

I could you find any document for extended classic.
Could anybody help explain what is different between the 2 classics?
Thanks!

In the Extended Classic scenario, the entire procurement process takes place locally in EBP (SRM) and a copy of the data is replicated to the back-end system. In essence, this scenario is an extension of the Classic Scenario.
The purchase order in the back-end SAP system (ERP , R/3 System) is a read-only copy that enables goods receipt, service entry, and invoice verification in the back-end system. The back-end purchase order cannot be changed. If you wish to make any changes to the purchase order, you must do so in EBP i.e. SRM system. Once you save these changes, they are transferred to the back-end purchase order.
While in Classic Scenario , The PO is created in the backend ERP system once the SC is approved.
In brief , you can say while in extended classic scenario , the backend ERP system is a read only system and we do everything is EBP (SRM) system only. and in Classic Scenario , ERP system was used to generate the purchase orders.
Hope it clarifies and gives you a little visiblity on what is the difference between both.

Classic Scenario: follow on document from BID

Dear All,
We are trying to create a PO from an accepted BID . We can create the PO, and if we check it in the backend system, everything is OK.
Our problem is that we are trying to find in SRM, somewhere that shows us the follow on document of the Bid but we can´t find it.
It´s important to say that as soon as the PO is created, we get a message that contains the PO number. But after that, we can´t find in SRM the PO number anymore.
Is this a lack of SRM or may be another problem? Has anyone face up with this issue? If so, How it was resolved?
Thanks,
Pablo.-

I noticed that you have a very similiar Bidding scenario that we have. We can create a bid invitation in SRM and we have used the BADI - BBP_DETERMINE_LOGSYS to indicate to the system to create a purchase order in the backend system after the bid is accepted. We keep getting the following error in SM21: Purchase orders cannot be created without IPC pricing
Did you have to turn on the IPC in order to create the purchase order in R/3? We are on SRM 4.0. Also, if you have used the BBP_DETEMINE_LOGSYS Badi and have example code that might be helpful as well...thanks!

Reverting to classic scenario in SRM7.1, from PPS and extended classic

Similar Messages

Maybe you are looking for