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

Similar Messages

  • 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

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

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

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

  • 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

  • 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

  • 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,
    <b>Attention</b>, prior to the new possibility to use backend purch groups for Extended Classic Scenario, this erroneous solution was commonly implemented.
    <b>DO NOT</b> 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

  • 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 Withholding tax

    Hi,
    Can anybody explain me what is the differance between classic and extended withholding tax.
    Rds,
    javed

    Hi
    Text from SAP documentation
    SAP provides you with two procedures for processing withholding tax:
    "Standard" and extended withholding tax.
    "Standard" withholding tax is the procedure that has always been supported by the system. It offers you the following features:
    Withholding tax for accounts payable
    Withholding tax calculation during payment
    Withholding tax code per vendor line item
    Extended withholding tax provides the following additional features:
    Multiple withholding taxes per customer or vendor line item
    Withholding tax calculation for partial payments
    Thank You,

  • Defination of Classic and Extended Withholding Tax

    Hi Gurus,
    Can anyone please explain the defination and exact use of Classic and Extended Withholding Tax difference.
    Thanks in advance.
    Regards,
    Dev Mahendra

    hello,
    "Standard" withholding tax is the procedure that has always been supported by the system. It offers you the following features:
        Withholding tax for accounts payable
        Withholding tax calculation during payment
        Withholding tax code per vendor line item
    Extended withholding tax provides the following additional features:
       Multiple withholding taxes per customer or vendor line item
       Withholding tax calculation for partial payments
    Regards,
    Sankar

  • 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

Maybe you are looking for

  • How to I get my contacts from the iCloud  to my new phone

    I am having problems with my new iphone5 the lady in the shop saved all my contacts on the iCloud and said I could get them once I have started up my new phone.does anyone know how I can get my contacts from the iCloud to new iPhone. Thanks

  • My workbook charts are not working dynamically

    Hi All, I am displaying a chart in the workbook that will display according the query values. Once I save it, the problem is that if the values in the query change, it is not adjusting the chart accordingly. Example, I am listing data for each month

  • Unable to connect OID server during 9iAS Install

    Hye, I've got a server with a 9iDB and 9iAS Infrastructure. Everything seems to work fine. I try to install 9iAS on another computer, but I can't continue the install because the installation process can't connect the OID server on the first computer

  • Where can i download official 64 bit version even if it is beta etc

    Where can i download official 64 bit version even if it is beta etc I am using win 8.1 64 bit and i can say that every application i develop as 64 bit on c# works better on this os so i want to try out 64 bit firefox as well

  • Time since last charged doesn't work

    Does anyone else have this problem ---  under general in settings, under the title Time since last charge....there is usage and stand by. After both of those it just has this -    I've contacted apple, they ran a thing to see if it was the battery an