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?
Regards,
Srivatsan

Srivatsan,
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
Rgs,
Pedro Marques

Similar Messages

  • Question on Purchasing documents in extended classic scenario

    Hi friends
    How to create local purchasing documents i.e po,confirmations,invoice, in extended classic scenario
    Please let me know the path
    regards
    venkat reddy

    Hi Venkat,
    The user interface and the process is same for local documents. However the result of document posting (either backend or local) depends on the setting in SPRO --> SRM --> Technical basic Settings --> Define backend system for product category.
    Here you can define the target system as the system of document posting. If the terget system specified here is your SRM system, then it will create local documents in SRM.
    Regards,
    Prashant
    Do reward points for helpful answers

  • 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 - no backend PO created

    I try to activate the extended classic scenario. It's not activated in customizing, tried to do it only with BADI implementation for special material groups. We are able to create POs in SRM but transfer to backend doesn't work.
    I get following error messages in application monitor as backend application errors:
    No instance of object type PurchaseOrder has been created. External reference:  
    PO header data still faulty  
    Document number 100000093 not within defined inter val  
    What's going wrong here?
    Hubert

    Hello,
    Check if you have set up the customizing as below:                                                                               
    Extended classic scenario:                                                                               
    a) at SRM side:                                                                               
    - To assign the transaction type to the extended classic scenario you have to maintain the transaction type name (= the R/3 PO document type) to the attribute DP_PROC_TY (in contradiction to BSA in classic scenario) in PPOMA_BBP of the responsible Purchazing group.                                           
    - Create a number range for a local PO.                                                                
    - Assign the local PO number range as a internal numer range to the transaction type.                                                                               
    b) at R/3 side:                                                                               
    - Enter the Number Range (corresponding to the SRM number range PO) and flag it as an external number range (trx. OMH6 Number Range for Purchasing Documents)                                                                               
    - Maintain the document type corresponding to the SRM transaction type and assign the R/3 number range for POs as "NoRge Ext" (field V_T161-NUMKE) (trx. Document type within Purchase Order Customizing)                                                                               
    - Make sure that the SRM and R/3 number ranges match are exactly the same.
    Kind regards,
    Ricardo

  • Reservation with Extended classic scenario

    Hi ;o)
    I'm working at a costumer were we have extended classic scenario. We want to be able to make reservations in the backend if the item is on stock, and we have seen in a solution matrix from SAP that this should be possible.
    The configuration for reservations should be done according to the guides - but no reservations is created when ordering a stock material.
    I was searching on the developer network, and came across a topic, where it was stated that reservations could only be made with classic scenario (or using a BAdI where you switch the extended on and off depending on product category). Do any of you know if this is really a fact?
    Thanks in advance
    Maria Hvenegaard, Denmark

    Hi
    Read this first.
    <u>You can use BBP_CREATE_RES_BACK BADI using Se18 Transaction.
    This BADI You can find in SPRO -> Supplier Rel. Mngmt. -> SRM Server -> Business Add-Ins -> Follow-on document generation -> Reservation in Backend System</u>
    <u>If you want to create reservation, you have first to switch from ECS to classic scenario through BBP_EXTLOCALPO_BADI then you have to implement BBP_TARGET_OBJTYPE badi to determine the criteria to create a reservation in your backend.</u>
    <u>We need to maintian the customising setings in SPRO Transaction.
    Define objects in Back end systems. Maintain the document type EC or ECPO for Purchase Orders and not for creating reservations. Maintain number ranges (RS) and align the same to R/3 or backend systems. In setting up the org plan in the PPOMA_BBP Transaction, the attribute for resevation - Attribute BWA should be maintained too, if reservations are to be created in the backend system.
    Movement Type Accounting Object
    201 Cost Center
    221 WBS-Element
    231 Sales Order
    241 Asset
    Example :
    logicalsystemname\201</u>
    <u><b>Maintain the following Settings in the IMG using SPRO Transaction.</b>
    1.For internal Procurement > 1.Always Reservation for Material types Subjected to inv Mgmt
    2.For External Procurement >1.Always purchase Requisition.
    Note -> The plant that you use to create the shopping cart might not be extended to handle inventory management. Select a right plant which is extended to inventory management and you will see a reservation being created.</u>
    Be aware that:
    - with the classic scenario you can create PR, PO and/or Reservations in R/3, but there is no local purchasing document (except the SC), so all functions around the local PO will not be possible.
    - with the extended classic scenario, you can only create PO in the backend, but a local PO exists in SRM.
    Concerning GR, it is possible to make it in SRM for both scenario
    Hope this will help.
    Please reward suitable points, incase it suits your requirements.
    Regards
    - Atul

  • SRM: Extended Classic scenario: Request your help.

    Hi Guru's,
    We are implementing the EXTENDED CLASSIC SCENARIO in our project. kindly request your help.
    in our project the SRM box is :  G3OSBSR102.
    R/3 backend Box is :   RCHSBR3142.
    Now when i create a shopping cart it should create the Purchase order In SRM( G3OSBSR102) and also copy the created purcahse order in teh backend system : RCHSBR3142.
    The issue here is which Logical system should be populated in the field at item level when creating the shopping cart :BE_LOG_SYSTEM.
    1) In this field: BE_LOG_SYSTEM.
    If i populate the SRM local: G3OSBSR102., then it will consider the Business object type as : BUS2201and creates the local Po but while transfering this local created document(PO) to R/3 system is loosing the Logical system at the item level of the PO.
    If i populate this field at the item level via DEBUGG mode then system is sucessfull in transferring the document to R/3.
    2)  In this field: BE_LOG_SYSTEM.
    If i populate the SRM local: RCHSBR3142, then it will consider the Business object type as : BUS2012 and creates the purchase order in R/3 system and will not create teh local purchase order.
    Kindly request your help for any further settings if i did miss.Appreciate your help in this regards.
    Many Thanks,
    Prasad NN.

    Dear Prasad,
    To work on Extended Classic Scenario, you just have to maintain the following configuration in SPRO:
    >SAP Supplier Relationship Management
    >SRM Server
      >Cross-Application Basic Settings
       >Activate Extended Classic Scenario
    Check the flag "Extended Classic Scenario Active".
    You dont have to manipulate "BE_LOG_SYSTEM" field to choose your scenario.
    Regards
    Thiago Salvador

  • SR_ Extended Classic Scenario : Request your help please

    Hi Guru's,
    We are implementing the EXTENDED CLASSIC SCENARIO in our project. kindly request your help.
    in our project the SRM box is : G3OSBSR102.
    R/3 backend Box is : RCHSBR3142.
    Now when i create a shopping cart it should create the Purchase order In SRM( G3OSBSR102) and also copy the created purcahse order in teh backend system : RCHSBR3142.
    The issue here is which Logical system should be populated in the field at item level when creating the shopping cart :BE_LOG_SYSTEM.
    1) In this field: BE_LOG_SYSTEM.
    If i populate the SRM local: G3OSBSR102., then it will consider the Business object type as : BUS2201and creates the local Po but while transfering this local created document(PO) to R/3 system is loosing the Logical system at the item level of the PO.
    If i populate this field at the item level via DEBUGG mode then system is sucessfull in transferring the document to R/3.
    2) In this field: BE_LOG_SYSTEM.
    If i populate the SRM local: RCHSBR3142, then it will consider the Business object type as : BUS2012 and creates the purchase order in R/3 system and will not create teh local purchase order.
    Kindly request your help for any further settings if i did miss.Appreciate your help in this regards.
    Many Thanks,
    Prasad NN.

    Hi ,
    Go to SPRO
    There is a node - Activate Extended Classic scenario
    Do the config.
    Regards
    G.Ganesh Kumar

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

  • Extended Classic Scenario-Replication of Local PO to R/3 fails

    Hi,
    In the Extended Classic Scenario (SRM4.0/ECC5.0),we are creating Purchase Order from the Sourcing Cockpit. Local PO is getting created , but is not getting replicated to Backend R/3.
    After debugging through BBP_PD_PO_TRANSFER_EXEC , noticed that all the PO data is available when BBP_PO_INBOUND is called .But the PO number is missing when the BAPI_PO_CREATE1 is called. Because of this , system is searching for internal number assignment and since only external number is assigned for the document type , it is giving error.
    Can anyone suggest if we are missing anything.
    Regards
    garugu

    Hello,
    this is strange, because in ECS the local PO gets an ID, and this ID is used during the transfer to R/3.
    Debug BBP_PD_PO_TRANSFER_EXEC once again to see where this ID is cleared.
    To you have activated the BADI BBP_ECS_PO_OUT_BADI to transfer data to R/3 ?
    Be carefull, some BADI need to populate all export parameters/tables (E_*) otherwise the inbound data is considered as erased.
    Where is the ID disappearing ? in SRM just before calling R/3, or in R/3 ? In that case look at user-exit or BADI is R/3.
    Rgds
    Christophe

  • Status I1113 missing in SC in Extended classic scenario using TA BBP_POC

    Hi all,
    I am using SRM in extended classic scenario (ECS) (SRM Server 5.5) SP09.
    1. Scenario (without any problems)
    Shopping carts have been succesfully replicated from R/3 with standard report
    BBP_EXTREQ_TRANSFER.
    transfered to Sourcing Cockpit.
    No problems at all using standard Sourcing Cockpit -> POs are replicated to R/3, status correctly transfered into Shopping Carts (Status I1113 after creating a PO out of SC).
    2. Scenario (problems concerning Status I1113 in SC)
    Shopping carts have been succesfully replicated from R/3 with standard report
    BBP_EXTREQ_TRANSFER.
    transfered to Sourcing Cockpit.
    Shopping carts are manually transfered into a local PO by using standard transaction BBP_POC (create PO) -> function "Add shopping cart item" within item data
    Local PO is created without any problem, sucessfully replicated to R/3 and if I start the Monitor for shopping carts I get all the detailed information (follow on documents) -> PO number etc.
    Problem: If I use TA BBP_POC and add these shopping carts to PO positions, the status I1113 is not written to SC after executing BBP_GET_STATUS_2 and CLEAN_REQREQ_UP .
    The SC remains in Status I1106 (Shopping Cart ordered) / I1129 (approved)
    I cant find any entries in table BBP_DOCUMENT_TAB and the shopping carts have been removed from SoCo after creating a PO out of it...
    Does anybody uses Transaction BBP_POC in ECS and adds Shopping Carts to POs?
    Any Idea why the status for these SCs is just I1106 "Shopping Cart ordered" but status I1113 "Follow-on Document Created" is missing/not updated?
    Best regards,
    Andreas

    Hi
    <b>Please go through the SAP OSS Notes below -></b>
    Note 1053433 Extended classic: Incorrect status shown in check status
    Note 730239 Check status: Missing Backend reference
    Note 819094 shopping cart monitor:Update status after resubmit shop.cart
    Note 825761 Report program for shopp. cart status update after resubmit
    Note 768164 Multiple SCs via SoCo are processed incorrectly
    Note 729967 Shoppng cart:Status I1111,no follow-on docs->analysis report
    Note 728536 Shopping cart: Follow-on docs => analysis-/correction report
    Note 704941 EBP 3.0: Status error in SC extractor
    Note 486246 Incorrect shopping carts offered for confirmation
    <u>Do let me know.</u>
    Regards
    - Atul

  • ASN in Extended Classic Scenario with SUS

    Hi SRMer?
    Is it possible to create an ASN in SUS with Extended Classic Scenario (ECS)?
    OSS note 543544 mention that the scenario is limited for document types Purchase Order, Purchase Order Response and Change Order. Confirmations and invoices are not possible. There is no indication on ASNs.
    Any help will be appreciated.
    Regards.

    Hi
    Please go through these links ->
    SUS-MM Confirmation without ASN
    Re: Details on ASN
    The specified item was not found.
    SUS  ASN - mandatory field
    ASN Confirmation not created,
    Clarifications on EBP-SUS and MM-SUS Scenario
    Re: SUS-MM scenario with "POR (order ack.)" and ASN for free text
    Creating custom field in ASN screen of SRM SUS
    SUS Invoice
    Regards
    - Atul

  • Tolerances in SRM extended classic scenario

    Hi all,
    I have a question regarding tolerances in extended classic scenario and I hope that somebody could help me.
    We use extended classic scenario. The tolerance group is attached to TOG attribute in PPOMA_BBP, tolerance key is DQ.
    We also tried to use tolerance key CF, but it seems as if CF is not applicable for GR?
    However, whenever we try to confirm more than PO quantity, we get an error message. “PO Ordered quantity exceeded by 1 EA“
    It seems so that SRM has a ‘double’ tolerance check
    • one in SRM against defined tolerance (via attribute TOG)
    • one in R/3 against the PO tolerance
    Now my question: Is this the expected behaviour or a bug? We do not want to maintain two tolerances. And furthermore most of the time we have PO’s without a material master. Are there any possibilities to skip the PO tolerance check?
    Thanks for your help,
    Martina
    Edited by: Martina A. on Jan 15, 2008 1:13 PM

    Hi
    Depending on the SRM version you are using, Please go through the links, which will definitely help ->
    Condition Type SRM - ECC
    Tolerance in SRM and ECC (BE R/3)
    Tolerance
    Re: SC Budget check without SAP Fund Mgmt
    TOG parameter and tolerance checks better understanding
    Setting EKPO-UNTTO with BAPI_PO_Create
    Re: SRM: many confirmation for PO
    Please maintain the "TOG" attribute in PPOMABBP transaction in SRM.._
    Do let me know.
    Regards
    - Atul

  • 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

  • STO in a SRM Extended classic Scenario

    Hi All,
       Although I have implemented STO process in a classic scenario, I have not implemented or not sure if possible in a Extended Classic Scenario. Please advise on how STO could be implemented in SRM 7.0 ECS scenario. Will award appropriately.
    Regards
    Rao.

    Hi,
    STO is not a supported PO type for classic or ECS.
    Since you have managed to do with the classic earlier, the logic would be pretty similar in my opinion. Both will called to the BAPI_PO_CREATE1 eventually and i also believe you have made data adjustment in the SRM/ERP BADI before the classic PO data is used for the document creation.
    Likewise for ECS PO, we have BADI for the ECS PO too.  By adjusting the necessary data before document creation, you should achive the same end result.
    However there is a major difference between classic and ECS PO - the latter cannot be edited in the ERP at all if that is a requirement which you have done in the earlier PO.
    Regards.
    YS

Maybe you are looking for