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

<u>Before talking about de-activating ECS or not in this BADI, this scenario must first be activated.</u>
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:
<b>SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.</b>
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 .
<u>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</u>
<u>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)</u>
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.
<u><b>PS: be aware that in ECS scenario you will no longer be able to create PR or reservations in R/3.</b></u>
<u>Other related links -></u>
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.
- Atul

Similar Messages

  • No GR on Confirmation Approval in Extended Classic Scenario

    Hi all gurus out there,
    We are trying to implement confirmation approval workflow in our SRM system. Our SRM version is SRM 3.0 or EBP 4.0 and we are operating in extended classic scenario.
    We implement the approval workflow WS10400002 (1-step approval) and WS10400010 (no approval). WS10400002 is used in situation when an administrator does the confirmation and will go to the requestor for approval. Here, when the requestor approves the confirmation, the status is updated correctly to 'Approved' but no goods receipt is triggered by the system. We looked at the workflow and found that there is no task/activity to do the post goods receipt in the backend system.
    Can someone please confirm whether these are the correct workflows that I should be using and that it is not a bug? I just want to make sure it is not as a result of a standard limitation before going back to SAP.
    Siow Fong

    Hi Guys,
    I checked with SAP on this and found out that the standard codes would have created the goods receipt. This creation is no longer coded in the workflow itself (like the old workflow used to be). The reason why it was not working for us was a piece of code being added that prevented the creation of the goods receipt.
    Siow Fong

  • Organization structure in extended classic scenario

    Hi All
    I  am trying to configure extended classic scenario on SAP SRM 7.0.  I have made the following settings for the same:
    1. In SPRO->SRM Server-> Technical Basic Settings -> Define backend system from product category, I have specified target system as SRM system and not ECD system
    2. In SPRO->SRM Server->Cross Application Basic Settings-> Activate Extended Classic Scenario, I have selected all the options including "Back end purchasing group responsible"
    I have a few doubts.
    1. In organization Structure (PPOMA_BBP) Comapny code is corresponding to company code in back end but do I have to create local purchasing organization and local purchasing group i.e. in Functions-> Corresponds  I'll have to leave blank. plz suggest
    2. Also is IPC configuration mandatory for extended classic scenario
    Plz give your suggestion on above mentioned issue
    Pawan Keshwani
    Edited by: pawankeshwani on Mar 18, 2011 8:33 AM

    Hi Pawan,
    No you should mention Purch Org & Purch Grp also wrt your backend (ECC).
    IPC need not be configured separately from SRM 5.0 onwards. To ascertain if IPC is working fine just run the report : RSVMCRT_HEALTH_CHECK. You should see 4 success messages. Else get in touch with Basis to enable Virtual Machine Container (VMC)

  • Tolerance key DQ in extended Classic scenario give Backen error message

    Dear all,
    I am using SRM 7.0, SP 9 
    Extended Classic Scenario.
    I created a tolerance group and attached it to my user via TOG attribute in PPOMA_BBP. Tolerance key is DQ with $1000 and upper percentage 5%.
    I also set up the ECC tolerances:
    - Purchasing Value key with Tol. Overdelivery = 5.0 (in SPRO --> MM --> Purchasing --> Material Master --> Define Purchasing Value Keys)
    And assigned that Purchasing Value Key to the material group I am using (via SPRO --> MM --> Purchasing --> Material Master --> Entry Aids for Items Without a Material Master)
    - And I even set up tolerance key B1 (for error message) for my Company Code (in Spro -> MM --> IM and PI --> GR --> Set tolerance limits) with a upper limit of 5%
    And even with this set up I still get the error message
    u201CBackend Purchase Order quantity exceeded by 1 EAu201D
    when I try to post a Confirmation with an overdelivery, even if the over delivery is only 0.1% of the total quantity 1000.
    What Configuration am I missing?

    Dear Rahul,
    Thanks for you input
    Let me give you an example of the behaviour:
    in PPOMA_BBP TOG assigned to user has : DQ with $1000 and upper percentage 5%.
    User orders a PO  with quantity=1000, price $100;
    No additional tolerances assigned in the PO itself
    User tries to enter confirmation with quantity 1001 (so qty variance converted to currency amount results in $100 over delivery) So the confirmation is under both the 5% and the $1000 limit.
    In that case I donu2019t receive an error message from the SRM, but the error message u201CBackend Purchase Order quantity exceeded by 1 EAu201D from ECC still prevents me from posting the Confirmation. And this is the problem I havenu2019t been able to solve so far.
    So I want the TOG tolerance to be used. And I am also happy with the absolute limit always having priority over percentage limit...
    But I am trying to find a way to get rid of the back end message (with assigning a tolerance to the PO itself as the will get rid of the absolute limit see my previous post.)

  • 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.

    Go to transaction - <b>SPAM</b> to get all the required Patch levels and other required system version details.
    <b>Meanwhile, try the following SAP OSS Notes as well -></b>
    <u>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 )
    Hope this will help.
    - Atul

  • Classic / Extended Classic Scenario for Shopping Cart

    Dear Friends,
    We are working on two different business scenarios with same Product type, Product and Product Category where we would like to control Extended Classic Scenario.
    1. Self Service procurement to be executed in Classic Scenario as the follow-on document (Purchase Requisition) should be created in backed ECC system.
    2. Plan Driven Procurement cycle where External requirement is transferred from backend ECC to SRM keeping Extended Classic scenario active so that system creates Shopping cart in SRM.
    So which condition should I use to control the “Classic / Extended Classic Scenario” in BADI BBP_EXTLOCALPO_BADI method DETERMINE_EXTPO.
    Sandeep Parab

    Thanks Pierre,
    My Sourcing requirement is working as desired with following code in BADI BBP_SRC_DETERMINE (method DETERMINE_SOURCING).
        E_HEADER = w_header  .
    IF sy-subrc = 0.
      IF w_header-subtype = 'ER'.
        SOURCING = 'X'.
        SOURCING = ' '.
    However I’m not able to control the Classic and Extended Classic Scenario even after introducing field EXT_DEMID in structure BBPS_EXTPO_BADI in badi BBP_EXTLOCALPO_BADI and method DETERMINE_EXTPO.
      BBP_EXTPO_GL = ' '.   for classic
      BBP_EXTPO_GL = 'X'.   for extended classic
    No idea y this is not working … to my knowledge it should work…
    What do you think ? this this code and badi actiation im not able to perform SSP in classic mode and sourcing with extended classic mode.
    Sandeep Parab.

  • Extended classic scenario and printout in ERP

    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?

    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.
    Virender Singh

  • Extended classic scenario to Classic scenarioc in SRM.??

    someone pls tell me how to change from Extended classic scenario to Classic scenarion while creating in shopping cart...?
    I am using BADI "BBP_EXTLOCALPO_BADI" change to classic scenarion from extending classic..but i got confused about source code..So i request any one can help me for suitable source code..

    Do you mean to say that you have set up Extended Classic Scenario but you want to change it to Classic Scenario?... If this is the case, remove the activation in COnfiguration for Extended classic scenario and deactivate BADIs you ve implemented for Extended Classic
    Do you want to change it to Classic only for the Document user is creating.--> Read the indicator or data from SC and decide whether the document has to be in Classic or Extended classic SCenario.... The BADI will either have Extended classic = X or NOT.... so there is no parameter for classic Scen... Depending on your requirements, implement the ext. classic badi to SET it or NOT set it...
    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

  • Configuration steps for Extended Classic Scenario

    Hi All,
    Could you please let me know what are the configuration steps required for extended classic scenario.
    Thanks in advance

    Important Settings that Determine the Extended Classic Scenario
    The following settings are required for the extended classic scenario:
    u2022 At least one backend materials management system and accounting system is connected to the SAP SRM system and defined in the configuration setting Define Backend Systems.
    u2022 Product categories from the backend procurement system are replicated and used in the SAP SRM system.
    u2022 The target system for each product category is the backend system in the configuration setting Define Backend Systems for Product Category. Optionally, BADI BBP_DETERMINE_LOGSYS is implemented to determine the backend system.
    u2022 The extended classic scenario is activated in the configuration setting Activate Extended Classic Scenario. Alternatively, BAdI BBP_EXTLOCALPO_BADI is implemented to control the extended classic scenario based on customer defined rules.
    u2022 If the backend system is an SAP R/3 version lower than 4.6B, you must define local purchasing organizations and purchasing groups.
    u2022 If the backend system is an SAP R/3 version 4.6B or higher, you need to map the purchasing group used in the purchase order to the backend purchase group in one of the following ways:
    u2022 Use a backend purchasing organization and purchasing group in the shopping cart and purchase order.
    u2022 Use BAdI BBP_PGRP_FIND to determine a backend purchasing group in the shopping cart.
    u2022 If a local (created in SAP SRM without reference to a backend system) purchasing group and purchasing organization are used, then a valid backend purchasing group is assigned to the RFC user that created the backend purchase order. This assignment is made in the backend system using user parameter EKG in Transaction code SU01.
    u2022 Implement the user exit of the BAPIs BAPI_PO_CREATE1 (EXIT_SAPL2012_001 and EXIT_SAPL2012_003), and BAPI_PO_CHANGE (EXIT_SAPL2012_002 and EXIT_SAPL2012_004) to determine the purchasing group with a customer- specific logic.
    This is for your additional information.
    Hope this helps.

  • SC with Limit Item using Extended Classic Scenario?

    Can we implement SC with Limit Item using Extended Classic Scenario.
    I mention that we replicate the Product Categories from R/3 backend.
    We have tried to create a SC with Limit item, but the data on Quantity, Price and Tax is not picked up at PO level.

    Please try out this.
    For the time-being,
    Try de-activating all the custom BADI Implementations and check, what is happening, in the standard SRM system. How does it behave incase of limit item ?
    Incase it works fine, without any Custom Implementation active in the system, I suspect there is something wrong in your current deactivated BADI Implementation.
    Since i don't have access to your system , Please paste the code here.
    Hope this will help.
    Please reward suitable points.
    - Atul

  • Activate extended classic scenario

    Hello, when I try to activate extended classic scenario to create contracts in SRM and then transfer them to R/3 I have these options:
    Extended local PO
    BE Purch Grps Resp.
    Back-end check reqd
    Back-end errors, show as error msg
    Which options may I have to select?
    Thanks in advance

    I think Rosa's requirement is to create a manual and local contract in SRM.  Indeed you mentioned an excellent  BADi, but my understanding is this badi gets called from the sourcing application.  I am not sure whether this gets called from the SRM local contract.  This is the help documentation I am pasting here.  It would be wonderful if this works.  See the highlighted "importing parameters" part of the following pasted one.
    Thank you,
    Determine Target System of Contract
    With method CONTRACT_LOGSYS_DETERMINE, you can control the target system determination for contracts.
    In the standard, the Sourcing application and SAP Bidding Engine create contracts locally in SAP Enterprise Buyer . With this method, you can create a contract in the backend system instead.
    You are using a backend system with Release 4.6B or higher.
    You have created the logical system in activity Define Logical System
    The BAdI takes this data from requirements in SAP Bidding Engine (bid) or from requirements in the Sourcing application.
    Header structures
    Item structures
    Business partner data such as vendor or location
    Organizational data
    In the method you can overwrite the following field:
    Name of the system in which a contract is to be created.
    If this field remains empty or contains the name of the local system, then the contract is created locally.
    If this field contains the name of a backend system, then the contract is created there.
    When coding the method, use the delivered sample coding as a guide.
    See also
    BAdI Determine Backend System / Company Code

  • 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

    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:

  • Limit shopping carts in extended classic scenario

    How can we implement limit shopping carts in extended classic scenario. Has anyone done it? Thanks in advance

    Which SRM version are you using ? It's possible to implement limit items concept in ECS Scenario.
    What exactly you are looking for ?
    Please have  a look to the following links as well.
    <b>Few SAP OSS Notes to refer in this case.</b>
    <u>Note 712702 ECS shopping cart with several limits
    Note 724261 Limit: Error during creation of local purchase order
    Note 694442 Limit SC: Customer fields not transferred to backend PO
    Note 690000 Limit SC: Customer fields not transferred in Backend PO
    Note 699255 Internal note and vendor text for LimitPO and LimitPReq
    Note 501977 Error with limit SC: "Unit measure has no ISO code"
    Note 520514 Limit, BBP_PD148: No account assignment details were adopted
    Note 514727 Limit: Contracts are not displayed in the status
    Note 516444 Account assignment check in the shopping cart with limit
    Note 515500 Limit:'Confirmation and invoice' indicator not transferred
    Note 515695 Invoice entry for limit shopping carts not possible</u>
    - Atul

  • Multiple PO document types/transaction types in Extended Classic scenario

    Hi All,
    We are on SRM_SERVER 550, Extended Classic Scenario.
    We have a requirement where we need to create multiple PO document types (based on certain criteria).
    I have noticed that in standard, there are only 2 transaction types provided for SRM PO - ECPO and ECDP.
    We need more document types and these should be triggerred automatically after SC is approved.
    I understand that we need to maintain all the PO transaction types in SRM, number ranges in SRM then maintain the same transaction types as PO document types in R/3 and same number ranges in R/3.
    I also understand that the change for document type needs to be done in BBP_DOC_CHANGE_BADI.
    I have 2 specific questions:
    1. We need to maintain attribute BSA for the users. Here we need to mention the document type and source system. What should be the source system mained in attribute BSA for ECS? Should it be the SRM system or R/3 system?
    2. In BBP_DOC_CHANGE_BADI to change the PO document type/transaction type in ECS scenario, which field should be changed? Should it be ET_ITEM- BE_DOC_TYPE?

    To create new transaction type:
    Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Define Transaction Types
    To create new number range:
    Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Number Ranges --> SRM Server Number Ranges --> Define Number Range for Local Purchase Orders
    You can define to create automatic PO when a SC was created in: Supplier Relationship Management --> SRM Server --> Sourcing --> Define Sourcing for Product Categories
    Pedro Marques

Maybe you are looking for

  • How to find out what kind of type a file is?

    hi there! does andbody know if it is possible to find out if a file is a picture? Example: i have a file, with no extension. How can i know, if this file is a gif or a JPG? thanx for your help! jules

  • Click on table scrollbar

    Hi i've a problem i have an event structure with a table when i click into a cell a dialog box ask me some values and it works properly. When i've several values into table 2 scrollbars are visible and the click on the scrollbars arrows (and on bars)

  • Save the angle of motion

    Hi, i am new in programming. I have been assigned a task to program a kinect in C# for detecting angle of motion with indicator that show on the screen and save data. I have no idea how i can do it because I m weak in this.

  • Workflow for Reversing Invoice (FB08)

    Hi Gurus,               We are configuring Payment Release workflow for our project.               I am using the standard Workflow WS00400012  for the same and its working fine.               In the above mentioned workflow, if the payment release i

  • Spry accordian

    i have set up a basic accordian on a web page with 2 panels. however, when i run it, the panels do not open and close. also, when i've seen accordians working on the web, they usually have an arrow to open and close the panels. mine doesn't have thes