Extended Classic Scenario, BADI for PO creation in R/3

Hi,
We are using the extended classic scenario. When the PO gets replicated from SRM to R/3, right now the field CATALOGID is not being transmitted to the backend R/3 system.
1) What BADI should I implement (and the method) to transmit the CATALOGID to R/3?
2) After implementing the BADI, do I also have to change the BAPI?
3) Is the BAPI used to transfer data from SRM to R/3, BAPI_PO_CREATE?
Thanks and Regards,
Peter

Hi Peter,
1-You can use BBP_ECS_PO_OUT_BADI for ECS scenario.
Since the R3 PO does not have field for catalog id, the EKKO- BEDNR (Tracking Number) field can been used for example to store this information. In this BADI all the items are identified and their tracking number field is populated with a catalogue id value.
2-If you use the tracking number field, no use of R/3 BADI is required.
3-BAPI_PO_CREATE1
Please check my answers in this post :
catalogid field not going in R3 backend
Kind regards
Yann
Message was edited by: Yann Bouillut
Message was edited by: Yann Bouillut

Similar Messages

  • 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

  • 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.
    Regards,
    Sandeep Parab

    Thanks Pierre,
    My Sourcing requirement is working as desired with following code in BADI BBP_SRC_DETERMINE (method DETERMINE_SOURCING).
    method IF_EX_BBP_SRC_DETERMINE~DETERMINE_SOURCING.
    DATA: w_header TYPE BBP_PDS_SC_HEADER_D.
    CALL FUNCTION 'BBP_PD_SC_GETDETAIL'
      EXPORTING
        I_GUID = HEADER_BBP_GUID
      IMPORTING
        E_HEADER = w_header  .
    IF sy-subrc = 0.
      IF w_header-subtype = 'ER'.
        SOURCING = 'X'.
      ELSE.
        SOURCING = ' '.
      ENDIF.
    ENDIF.
    endmethod.
    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.
    method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
    IF ITEM_DATA-EXT_DEMID = ' '.
      BBP_EXTPO_GL = ' '.   for classic
    ELSE.
      BBP_EXTPO_GL = 'X'.   for extended classic
    ENDIF.
    endmethod.
    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.
    Regards,
    Sandeep Parab.

  • 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

    Hi,
    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.
    Regards,
    Vikas

  • PO output for Extended classic Scenario from the R/3 backend

    Hi,
    1) Does the PO output (ignoring the config maintained in SRM server 5.5 for the output) through R/3 backend is standard or it is mandatory to give local outputs from SRM only incase of Extended classic scenario?
    Regards,
    DV

    Hi Anil,
    We are working on extended classic scenario with SRM 5.0 & ECC6.0.
    Please explain how we can take "PO output for Extended classic Scenario from the R/3 backend ". 
    Please send the related document to [email protected]
    Thanks in advance
    Ashutosh

  • ASN for extended classic scenario

    Hello all,
    we have SRM with extended classic scenario (EBP-MM),
    is it possible to use ASN (shipping notification) functionality in our system ?
    Kind regards,
    Arthur

    Hi
    ASN can be created by the vendor in SUS system for that XI mapping is required. ASn can be created in SUS by any vendor users. I guess it's not possible with ECS.
    Please check the SAP Consulting Note 1026638 GR Output Integration with MM-SUS Scenario for R/3 <= 47
    You need to have functional background for this:
    To create an ASN against PO or SA release:
    1. you need to compulsarily put how much qty you are sending against the reqd. qty(shown by PO / SA )
    2. dispatch vehicle no. (optional)
    3. road challan no. (optional)
    4. one more optional entry ( sorry I forgot)
    Useful related pointers ->
    Re: how does the GR get into SUS---MM-SUS Sceanario
    ASN in Extended Classic Scenario with SUS
    SUS ASN & Invoice
    The specified item was not found.
    Do let me know.
    Regards
    - Atul

  • Attachment transfer of PO from SRM to Back end for extended classic scenario

    Hi Experts,
         We are using the SRM 7.0 with EHP 701 and ECC 6 , we have a SRM requirement where we need to transfer the attachment of a PO to back end ECC. I tried to implement the note 1594966 , but it doesn't work . we are using Extended classic scenario. Please suggest some SAP notes or the procedure to be followed to achieve this.
    Thanks ,
    Aishwarya.M

    As far as I am aware this functionality of transferring attachment is not supported in Ext classic scneario  
    http://scn.sap.com/thread/1873708
    Also  I suggest you should debug and see if its sending attachment from SRM if yes then
    could be something missing at ECC side , To debug use this
    http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=340264144
     You may also check in SXI_monitor and see if attachment is being recieved and sent from SRM and ECC respectively
    Are you configuring this for the 1 st time or its an error which u encountered?
    You must raise a NOte to SAP for the same till a solution is found .
    This one is another which you can check ..
    http://wiki.scn.sap.com/wiki/display/SRM/Transfering+shopping+cart+attachments+to+the+backend+system

  • PO approval process in ECC for extended classic scenario

    Hi All,
    At this moment we are using SAP ECC for procure to pay process. In the existing system set up, our ECC purchase order goes for approval via SAP enterprise portal(EP). We are planing to implement SRM 7.0 Extended classic scenario, so that user can take the advantage of creating PO in their web portal. We don't want to disturb our existing ECC PO approval process at this point of time.  
    So our requirement is :
    User will create PO in SRM. Same PO will replicated in ECC and the PO will goes for approval in in ECC and the PO output will generate in ECC. Can it me possible in extended classic scenario ?
    Thanks in advance.
    Regards,
    Jennifer
    Edited by: Jennifer Batty on Aug 8, 2011 5:08 PM

    Hi Jennifer,
    Since SRM PO will be leading PO in extended classic scenario, why donot you design the process controlled workflow in line with the existing release strategy that you are using for ECC PO?
    Thanks and regards,
    Ranjan
    Ranjan Sutradhar

  • Number range for extended classic scenario

    Hi,
    we've activated extended classic scenario for some defined categories (material groups), other will use classic scenario as before. It works, we are able to craete POs in both ways. I've tried to use the same number range for backend POs and for local POs. I've set the same number for both ranges but only the one which is used is getting updated. Is it possible to syncronize these ranges so backend POs will all be created in the same range?
    Regards
    Hubert

    Hi Hubert,
    Not the best practice that you are following. it might work for some time  but will fail for most of the time . The maintenance is going to be huge and you could expect problem with these.
    I would suggest not to think on the solution of same number range itself.
    Thanks
    Iftekhar Alam

  • Purchase Order Creation, Extended Classic Scenario

    Can someone please explain the different databse tables affected during the creation of a Purchase Order.
    Also, is there a transaction with which we can create PO in Extended classic scenario?

    hi,
    below are the tables effected while creation of PO:
    CRMD_ORDERADM_H
    CRMD_ORDERADM_I
    BBP_PDIGP
    BBP_PDBEI
    BBP_PDISB
    BBP_PDISS
    BBP_PDSDLN
    BBP_PDACC
    BBP_PDTAX
    BBP_PDATT
    BBP_PDORG
    BBP_PDWGT
    BBP_PDDYN
    BBP_PDEXR
    PRCD_ITEM
    PRCD_COND
    PRCD_COND
    BBP_PDDEP
    CRMD_PARTNER
    as far as your second question is concerned normally we will be creating a PO in SRM/EBP in web browser and it will replicate to the backend ERP.
    regards
    IGA

  • P-card  process available for SRM 5.0 extended classic scenario

    Hello,
    I didn't find the information, so I'm posting this message.
    Is  the p-card functionality available for the extended classic scenario in SRM 5.0 ?

    Hi,
    Use of Procurement Cards are supported in Extended calssic scenario from SRM 2007 ..onwards
    HTH
    Rajesh

  • MM-SUS for the extended classic scenario

    Hi,
    I have done SUS-MM for the classic scenario.
    Did anyone implement SUS-MM  for the extended classic scenario ?
    Did you face any problem or will it be same as 'classic' scenario ?
    Please help
    Thanks
    Pranav

    There shouldn't be any problem especially when the scenarios are concerned. Since the PO's moves from MM-SUS.
    Regards, IA

  • Sharing attachment documents (e.g. for P.O.) in extended classic scenario

    Dear SAP SRM gurus
    in the SAP SRM extended classic scenarios (rel. 7.0) attachments of Purchase Order can be viewed also in the backend SAP ECC 6.0  as per SAP Notes n. 1582690 and 1057932 . But I am not sure if attachments are phiysically transmitted from SAP SRM to ECC or only document url is passed even though, as per SAP note n.1357551 it seems that only url is passed.
    My customer wants to know if there is the possibility of not replicating them.
    Any suggestions will be appreciated.
    Many thanks in advance
    Best regards
    Gianluigi Brenna
    Edited by: GIANLUIGI BRENNA on Jul 29, 2011 2:56 PM
    Edited by: GIANLUIGI BRENNA on Jul 29, 2011 3:08 PM

    Hello,
    In extended classic scenario the attachments arent transferred to ECC as the source document is in SRM. The document in ECC is only a copy and it cant be modified also.
    If we have to transfer attachments, then probably implicit enhancements to standard logic might be needed.
    Regards,
    Prasanna

  • Extended Classic Scenario  - how does the integration work ?

    Hi,
    Apologies for asking a basic question, but we are looking at requirements for integrating SRM with R/3 using the extended classic scenario and I need to understand how the integration actually works ?  How is the data transferred between the 2 systems ?  Does it use BADI's, idocs etc ?
    Many thanks,
    fiona

    Hi Olaf,
    I just wanted to give some precision on what you said (in the thread How to "see" PO in EBP ? also)
    The Extended classic scenario only refers to the local PO creation replicated in R/3.
    In this scenario, in the R/3 PO only the data not managed/sent from the SRM are available for modification (which depends on the SRM version you use)
    The "PR transfer from R/3" is called "Plan driven procurement", and in this scenario only RFC is used, the qRFC are only used for BDocs of the CRM Middleware.
    Regards.
    Vadim

  • Extended classic scenario local PO

    Hi All ,
    Need some inputs on the extended classic scenario local PO.
    There is couple of functionality which we need to do for the PO. I mean when the PO gets created automatically after shopping cart completely approved
    We can change the same PO from the process purchase order also.
    But if I want to map couple of the fields, when PO is getting created automatically how can do that one. And I donu2019t want map these fields when the PO is from the getting changed process purchase order also.
    I am using the BADI, BBP_DOC_CHANGE_BADI (PO_CHANGE Method) to map these fields.
    The thing is here , this BADI will call even for the automatic PO creation and also for changing the PO .
    Currently when I noticed PO gets created automatically by the user id u201CWF_BATCH u201C , So I am using the same the logic like .
    If sy-uname = WF_BATCH
    Do the mapping part
    Endif,
    But I donu2019t think so; this logic will work all the times.
    Please can anyone give me some pointer for the same, it will be really helpful for me .
    Seeking your help on this
    Thank you,

    Hi Latha,
    This is a bit tricky one. Yes you are vry correct, the logic is not that fool proof, as the PO can be subjected to so many changes back & forth; even approvals can be done after a change is completed etc.
    The other alternative is to go ahead the document version. You can use the function module BBP_PD_PO_GETDETAIL and the table E_VERSION will contain all the versions of the PO. This should differentiate the change & initial PO verions.
    Hope you can build your logic based on this; this is a better logic on par with the existing one.
    Regards
    Kathirvel

Maybe you are looking for