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.

Similar Messages

Extended classic scenario triggered on company code

Good morning,
I have a system with SRM 5.0. I would like to have both classic and extended classic scenario, I know that it is possible to activate extended classic only for a product category with BADI BBP_EXTLOCALPO_BADI , but my question is: Is it possible to activate it for a company code? If yes, is it with the same BADI ?
Thanks in advance
Charlotte

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
Re: Classic Scenanio and Extended Classic Scenario
Re: Switching from Classic to Extended Classic
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Change from ECS to Classic Scenario
Re: Changing the Global Control of Extended Classic Scenario
Re: Technical Scenario Switch: From Standalone To Extended Classic
Do let me know.
Regards
- Atul

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

Extended classic scenario and printout in ERP

Hi,
we want to use extended classic scenario but the printout of the PO should happen in the backend system. PO is already created in the ERP system but I can't change it (as designed). How is it possible to create the printout from the backend?
Thanks
Hubert

Hi Hubert
This consulting note is for triggering Output of PO from ECC instead of SRM. Printing can happen from ECC if you can switch off PO Output form SRM and start triggering the same from ECC as per consulting note.
Try working with this FM In SRM BBP_OUTPUT_PO_PRINT_REMOTE for printing the PO, if PO Output is still required to be triggered from SRM.
Regards
Virender Singh

Extended Classic Scenario PPOMA_Purchasing Org and Group

Hi gurus,
We are working with SRM 5.5 and we are having problems with the assignments for the Purchasing organization and Purchasing groups in the PPOMA.
In the documentation it says we should have one box for the R3 Purchasing Organization (flagged and referred to the backend POrg) and one for the Local Purchasing Organization (flagged but NOT referred to the backend POrg). The same for the Purchasing Groups, the one under R3 POrg will be flagged and referred to the PGroup in R3 and the one under the Local POrg will have the flag but it will not be referred to the backend PGroup.
Afterwards, in the attributes for the Local POrg and Local PGroup, with the attributes PURCH_ORGX and PURCH_GRPX the local and the R3 POrg and PGroup will be assigned each other.
The purchasers will be located in the Local PGroup. The R3 POrg and PGroup will never have users assigned.
The problem is that all the workflow is only working if the "Local" POrg and Group have the backend purchasing organization and purch group assigned in the Function Tab. This means that the 2 boxes for R3 are no longer necessary. In the documentation it says that this version of SRM needs both boxes for the POrgs and the 2 boxes for the PGroups. We have flagged the Extended Classic Scenario.
Any help on this? It's because of the version?
Many thanks and regards,
I will give Points!

Hi Ana
PURCH_GRP     Purchasing group     Number of an organizational unit that is indicated as local purchasing group in the organizational plan.
This attribute is simulated. You define an organizational unit as company on the Function tab.
PURCH_GRPX     R/3 purchasing group     Number of an organizational unit that is indicated as the R/3 purchasing group in the organizational plan. The value contains the ID and the associated backend system of a backend purchasing group.
This attribute is simulated. You define the ID and the associated system on the Function tab.
PURCH_ORG      Purchasing organization     Number of an organizational unit that is indicated as local purchasing organization in the organizational plan.
This attribute is simulated. You define an organizational unit as purchasing organization on the Function tab.
PURCH_ORGX     R/3 purchasing organization     Number of an organizational unit that is indicated as the R/3 purchasing organization in the organizational plan.
This attribute is simulated. You define the ID and the associated system on the Function tab.
can you elaborate more?
in ECS also we can map the backend purchase organisation/ purchase group for purchasing activity.
there might be a resposibilty tab for the backend purchase group might be mapped the responsible purchaser list (dept).plz check it up
regards
Muthu
regards
Muthu

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.

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

How differentiate POs classic scenario and POs extended classic scenario?

Hi Gurus,
Is possible determine that some POs are generated in SRM system and send to R3 (Extended classic scenario) and other POs only to send from SRM to R3 system (classic scenario) in the same system?
How we can differentiate which POs should be sent to R3 (classic scenario) and which not? Is possible use type of document for example? Could you explain me if exists standard process?
The objective is determining the following: Is necessary differentiating POs created in SRM of importation and should be sent to R3 system (classic scenario), and in case of local POs (not importation) is necessary extended classic scenario.
I have understood that there is a scenario that includes the Classic and Extended Classic, I think is called Decoupled scenario.
Thanks for your help!!

Hello,
Yes this is possible.
You can do it automatically based on the product category. You must define the back-end system you wish to use for each product category by making the relevant settings in Customizing for SAP SRM under SRM Server --> Technical Basic Settings --> Define Backend System for Product Category
Check the online documentation here: http://help.sap.com/saphelp_srm701/helpdata/en/f3/6f505050404ce99151722a79a2c089/frameset.htm
You can also use Business Add-In BBP_EXTLOCALPO_BADI to overwrite settings made in Activate Extended Classic Scenario and implement more rues for the scenario determination, e.g. based on the purchasing organization for manually created PO's.
First you set you system to Activate Extended Classic Scenario : SPRO --> SAP Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
Then you set exceptions in the BAdI.
Regards
Franck

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

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

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

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

Error while creating Manual Service PO in Extended Classic Scenario

Hi Experts,
Extended Classic scenario (SRM 7.0 with ECC 6.0) While Creating Manual Service PO in SRM i am getting the below mentioned error messages. Can any one suggest what could be the problem.
Error Msgs:
1. Backend Error:In case of account assignment, please enter acc. assignment data for item
2. Backend Error:Purchase order still contains faulty items
Regards,
Mohan

Hi,
Yes i given all CC and GL information properly in Purchase Order Document for Service.. Still finding the error for Service PO alone.
Pl do the needful
Regards,
Mohan

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

PO text transfer to Back-end in case of Extended Classic Scenario in SRM 4.

Dear experts,
My system is in SRM 4.0 in Extended Classic Scenario. We use in the PO internal note text and vendor But thses texts are not transfered to Back-end.
Is it normal?
Do I need to customize something?
Can it be achieved by BADi? How then?
OR is it only possible from SRM 5.0?
Thanks in advance
RD

Yes you can do this. Implement BADI BBP_CREATE_BE_PO_NEW, Refer parameter IS_SC_DOCUMENT>LONGTEXT, and CS_PO_DOCUMENT>IT_PO_ITEM_TEXT. Map the exact text-id of the R/3.
Note: if this BADI is not present, use BBP_CREATE_PO_BACK
Regards, IA

Classic Scenanio and Extended Classic Scenario

Similar Messages

Maybe you are looking for