Extended Classic vs Standalone

Hi,
1. Can i choose between Extended Classic vs Standalone, I might sound stupid, still i want to hear from this forum.
2. Per my understanding, i can choose to be fully classic by activating Activate Extended Classic Scenario or Partly Classic and ECS by BADI BBP_EXTLOCALPO_BADI.
3. Here, BADI BBP_DETERMINE_LOGSYS will help to what and how. As i understood this will help in case of multiple backends.
4. I have done Decoupled where partly Classic and partly Standalone.
4. If I want to partly ECS nnd partly Standalone, can i do with combination of BADI BBP_DETERMINE_LOGSYS and BADI BBP_EXTLOCALPO_BADI without activating Activate Extended Classic Scenario.  
Thanks,
Jay

Hi,
1 & 2- 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
3- 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)
4- 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 abble to create PR or reservations in R/3.
Regards.
Vadim.

Similar Messages

  • 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
    <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
    Do let me know.
    Regards
    - Atul

  • 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

  • Extended Classic Scenario

    Referring to note 963000, we are about to install SRM 5.0 as AddOn to
    Ecc ERP 2005. In SRM we would like to implement the "Exteded Classic
    Scenario", meaning the procurement process will take place locally in
    EBP and a copy of data is replicated to the beckend system (ECC).
    Is the "Exteded Classic Scenario" compatible with the "SRM as add-on"
    installation? Note 963000 sais "The following scenarios are released
    within SRM AddOn: ... Self service procurement (classic deplyment)":
    does that mean that only the "Classic scenario" (meaning only Shopping
    cart on EBP, the rest of the purchasing process on backend) is
    available?

    HEllo,
    Only self-service scenario is supported. Means classic, extended classic and standalone.
    HTH
    Gordan
    Message was edited by: Gordan Flego
    Message was edited by: Gordan Flego

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

  • Completion workflow in extended classic scenario

    Hi gurus,
    We use extended classic scenario with SRM Server 5.5.
    In ppoma, each purch org and purch groups has the local and the backend. Vendors are replicated to backend purch org and then also to the local purch org.
    I have seen that in classic scenario purchasers should be assigned to the local purch org. however, completion workflow only determine the agent (purchaser) if it is in the backend purch org.
    The problem is that then this purchasers cannot manage any business partner.
    How can I solve it?
    I have seen other clients that the completion workflow determine the agents in the local purch org...
    Many thanks!!!
    Regards
    Patrícia

    Hi,
    In the Extended classic scenario, local purchasing organisation and purchasing groups are required to create shopping carts and purchase orders. in this scenario, when
    the vendors are replicated from the SAP back-end using BBPGETVD,BBPUPDVD program or vendor-synchronization programs, the vendor update in SRM is only for the R/3 purchasing organizations. because the local purchasing organisations are required in SRM for the Extended Classic or standalone scenario, these replicated vendors needs to be extended to the local purchasing organisations.
    organizations can use Tx. BBP_UPDATE_PORG for extending the vendors to the local purchasing organiztion.
    see OSS Note 390546 for more info.
    Regards
    vasanth

  • 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

  • Source List Required in Extended Classic

    Hi,
    We have a requirement wherein a Source List is required which contains the R3 contract. Now, when a PO is created in SRM, the source should pick up the contract based on the vendor list and the contract number and then this should also update the contract in the backend.
    My questions are:
    1. Vendor list cannot be maintained in a Extended Classic Scenario (as far as i know, it is the functionality of Standalone scenario. Can this be done in ECS? If yes, how?
    2. Once a PO is created in SRM by referring a R3 contract, can the contract be updated in R3? If yes, how?
    I would appreciate a quick response as this issue has become hot. Sorry about that!!

    Hi
    <u>1) Yes it is possible. Try BBP_SOS_BADI in SE18.</u>
    Refer to these links.
    <b>http://help.sap.com/saphelp_srm50/helpdata/en/6c/26d53bd2176b35e10000000a11402f/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/6d/0f343e47fd6b2ee10000000a114084/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/26/1a5da42ae0ab46836ea5e7f3a903b7/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/75/c65d3a0eb60365e10000000a11402f/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/38/4cc5376848616ae10000009b38f889/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/53/c49840893d2b54e10000000a1550b0/frameset.htm</b>
    2) I am not sure. I will get back soon.
    Regards
    - Atul

  • PO Output in Extended Classic using 3rd party

    Hi All,
    Would really appreciate if anyone can pls help us out.
    We are on SRM 5.0 in extended classic scenario. The client wants to output the PO to some of the vendors in XML but they don't have either XI or BC.
    The questions is -
    a) Is it possible to send PO to the vendor in SRM in XML without XI or BC.
    b)If possible  to send PO without XI or BC (The client currently have a 3rd party tool which converts the PO from R/3 to EDI format.).what are the special config required in SRM.
    Thanks in advance.
    Jay

    Hi,
    See these related threads:
    <b>Re: PO to Vendors</b>
    Output Purchase Order from SRM / EBP as File (without XI)
    Re: Exporting PO from standalone
    Re: SRM 4.0 Send PO to XI
    Re: How to define a new "send medium" for a vendor?
    Re: PO format (smartform):   PDF vs HTML ?
    Purchase orders output format.
    Re: Data transfer from EBP to external systems
    Re: Replicating PO from non-SAP backend to SRM
    Re: Data transfer from EBP to external systems
    related links:
    http://help.sap.com/saphelp_srm50/helpdata/en/84/0783f35c1e11d2b403006094b92d37/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/cd/0e343e47fd6b2ee10000000a114084/frameset.htm
    BR,
    Disha.
    <b>Pls reward points for useful answers.</b>

  • 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

  • POR transferred into MM(Backend) system in Extended Classic Scenario

    I am working on standard EBP-SUS Extended Classic Scenario. We have SRM Server 7.0 SP9 
    As we are successfully send PO from EBP to SUS.
    Issue : On working to Purchase Order Response,i am getting POR sent by SUS to EBP but we are not getting it replicated to MM.
    Our Concerns about is it need extra configuration required or need to have apply some note to getting replicated POR in MM from EBP or have to configure some XI Scenario to replicate POR from SRM EBP to MM.
    As we know that Extended Classic Scenario supports till Purchase Order Response still we are not getting Purchase Order Response in MM.
    Please tell us, Provided Solution will  be really appreaciated.
    Thanks.
    Regards,
    Pawan Keshwani

    hi,
    Pls see the foll notes:
    Note 576349 - Terms of payment in the ECS
    Note 541934 - Modification note: Copying base date from T052
    Note 953999 - ECS: Terms of Payment values not in PO header
    <b>Note 940453 - Backend payment term data not updated in the extended PO
    Note 945018 - Incoterms data not transferred to the back end</b>
    BR,
    Disha.
    Pls reward points for useful answers.

  • How to close extended classic PO in ECC...

    Hi Friends...
    We are in SRM 7.02 and ECC 6.05 in Extended Classic Scenario. One PO had been created for 1 Quantity 3 years ago. There was no GR/IR document posted against that PO. Now that PO had been archieved from SRM. But still PO is available in ECC with open quantity and also its appearing in the open PO report. Now requester wanted, the PO to be closed in ECC and shouldnot appear in the open PO list.
    How to handle this situation.. How to close the extended classic PO in ECC at this scenario. As PO not available in SRM, we can not do anything from SRM side.
    Your inputs are appreciated....
    Regards
    Sivakumar Kandasamy

    Hi Sivakumar,
    If you mean how to archive PO in MM side, please refer to the following info:
    ====
    In ECC system, if you want to archive a MM PO, please use transaction
    SARA->archive object MM_EKKO.
    456129 FAQ: Archiving in purchasing
    401318 Archiving: Additional information
    ====
    If you want to delete this ECC PO, please use BAPI_PO_CHANGE and
    refer to the following test data:
    Parameters:    PURCHASEORDER      =  XXXXXXXXX
    Parameters:    POITEM
    PO_ITEM                        = 00010
    DELETE_IND                     = X
    Parameters:    POITEMX
    PO_ITEM                        = 00010
    PO_ITEMX                       = X
    DELETE_IND                     = X
    You also need to run BAPI_TRANSACTION_COMMIT after BAPI_PO_CHANGE for updating the change.
    Regards,
    Ivy

  • 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

  • Error while changing PO in SRM extended classic Version 5.0

    Hi Guys,
    we are facing issue while changing PO in SRM , this is extended classic with version 5.0.
    The system status is active() is error message and PO remains unchanged. Kindly help to resolve this issue. we have an approval for even PO if a user changes the qty in the PO then it calls the approval WF logic.
    Thanks
    Srujank

    Hello Srujan,
    Go through the following thread:
    Re: PO status change
    Hope it helps.
    Thanks,
    Neelima

  • 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 - <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 )
    FOLLOW ON DOCUMENT NOT CREATED ( ERROR IN PROCESS)</u>
    Hope this will help.
    Regards
    - Atul

Maybe you are looking for

  • What happened to the " street view " function in the maps app in iOS6?

    What happened to the "street view" function in the maps app of iOS6?

  • Getting OTF spool into internal table

    Hi experts ! I am trying to get an OTF spool into an internal table (in order to send it to a web application). I use FM CONVERT_OTFSPOOLJOB_2_PDF :     PARAMETERS : p_spoolid LIKE tsp01-rqident.     DATA : lt_numbytes TYPE i,            lt_pdf TYPE

  • Release SO many times

    Hi all, The scenario is after booking sales order, i go to release sales order to run concurrent in order to get the move order number.Then release complete and i got the move order number. But I can release sales order again and again.Is this normal

  • UR/MR Redemption Value, Data Points please!

    While considering the merits of a CSP or EDP card, we are often faced with an "average cpp" for each point system.  The general consensus is that a UR point is worth 2.4 cpp while an MR point is worth 1.8 cpp.  I am hoping that people with experience

  • .configure gives an error

    Hi all, I'm trying to compile BerkeleyDB-C 4.7.25 on Linux but .configure gives me an error I don't know how to fix. uname -s -p -m -i -o -v Linux #1 SMP Wed May 27 17:14:37 EDT 2009 i686 i686 i386 GNU/Linux more /etc/redhat-release Fedora release 11