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.

Similar Messages

  • Freight is not updated in R/3 in the Extended Classic scenario

    Friends,
    Freight is not updated in R/3 in the Extended Classic scenario.
    Once a PO is ordered, if a freight condition in SRM is applied, it does not get updated in R/3.
    We have created a condition for Freight (Value and Percentage)in Create
    Payment Conditions using the following menu path:
    spro
    --> Supplier Relationship Management
    --> SRM Server
    --> Cross-Application Basic Settings
    --> Pricing
    --> Process Payment Conditions
    When creating a Purchase Order in SRM in the "Item Data" tab, there is
    a"Pricing" option. Choose "Pricing" and select "Add Further Conditions"
    from the drop down menu. Here Freight is available. Add Freight and
    the PO record in SRM is updated with the Freight Condition. However,
    upon ordering, the Freight condition does not transfer to the PO
    recordin R/3.
    We've heard this can be achieved by enhancement: only ie by implementing
    set of BADIs..  But does anyone know WHICH BADIs we need?  Or how we could find out?  Thanks.

    Hi
    <b> You can either of these BADIs to handlwe the scenario.</b>
    BBP_CREATE_BE_PO_NEW Exit while creating a purchase order in the backend system
    BBP_CREATE_PO_BACK   OLD Exit while creating a PO in the backend system     
    BBP_ECS_PO_OUT_BADI  ECS: PO Transfer to Logistics Backend                  
    BBP_EXTLOCALPO_BADI  Control Extended Classic Scenario  
    Hope this will help.
    Please reward suitable points.
    Regards
    - Atul

  • Transfer of SC into PO in Extended classic scenario

    Hi
    Can anybody provide me with the ABAP call stack ( I mean the program logic) on how the SC is converted to PO and transferred to the R/3 system in the case of extended classic scenario. I know that the SC after the approval process is over a method called "setrelease" of object bus2121 is executed. I tried to debug his method but could not found out the exact logic.
    Thanks
    sankar

    Hi Sankar,
    You will find the answer here :
    https://forums.sdn.sap.com/click.jspa?searchID=59712&messageID=2679107
    kind regards,
    Yann

  • SUS / no goods receipt doc to backend  in extended classic scenario?

    Hello
        have you any find  a solution for problem
        in SRM/SUS and goods receipt in extended classic scenario. Gr remains  only in SRM not going to backend...
    Brg Harri
    Message was edited by: Harri Harkonen
    Message was edited by: Harri Harkonen

    Hi Christophe,
    We also have this issue. Goods Receipt from SUS is created in SRM but is not posted in backend (we have implemented extended classic scenario).
    I tried to use the BBP_DOC_SAVE_BADI to created an idoc which posts the material document in backend system (using fm IDOC_GR_CREATE).
    The goods receipt is posted in backend this way.
    Unfortunately we are not able to cancel or make a return delivery on this GR.
    I am very interest in your FM. Could you please share this, or tell me what changes you made to the GR in SRM.
    Thanks in advance.
    Rgds,
    Martijn

  • SRM 7 : Vendor record replication in backend with Extended Classic Scenario

    Hello,
    We are implementing SRM 7 with Extended Classic Scenario and Supplier Self-registration.
    Can you explain what is to be configured to get the new vendors replicated to the backend?
    Thanks in advance.

    Hi,
    It is possible to transfer suppliers to ERP system, if you use 'Supplier registration with ERP' scenario. After registration and acceptance, newly registered suppliers would appear on supplier monitor from where you can transfer them to backend system.
    Check the below link for more details:
    http://help.sap.com/saphelp_srm50/helpdata/en/cf/35074152aff323e10000000a155106/frameset.htm
    Regards,
    Sanjeev

  • 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

  • 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

  • Extended Classic Scenario not creating backend PO

    Hi All
    We are just starting with SRM (Using SRM 5.0 SRM Server 5.5) and trying to decide to use Classic or Extended Classic.
    I can get the Classic working were an approved SC creates a backend PO without any problem. However when I switch on Extended Classic the backend PO is not created from an apporved SC.
    In RZ20 my error is Shopping cart 1000000080 (PReq. ): BBP_BD 002 Buffer table not up to date and Table BBP_DOCUMENT_TAB is empty
    In config I activated the extended classic scenario as well as activating the backend purchasing groups as responsible. Under sourcing I also defined for the relevant product categories as "1 - Sourcing Never Carried out"
    Am I missing something obvious??
    Many thanks for any help.
    Daniel

    Hi Daniel,
    In reference to the info. you have provided, it looks like you have not switched to Extended Classic Scenario properly.
    Once you say you are on ECS, the P.O should get created in SRM and the copy of it should get replicated to R/3.
    As you said you have flagged both the check boxes in SPRO for ECS activation, try activating sourcing also.
    SPRO > IMG > SRM > SRM Server > Sourcing > Choose one Product category for which you want to create shopping cart and set the setting as " Sourcing Always carried out".
    Check whether the approved shopping cart is coming to Sourcing cockpit or not.And from there try to create a P.O by assigning vendor.
    Also ensure that no BADI is activated which converts ECS to Classic scenario for the Product category you have choosen.
    If this cycle woks then definitely what you require will also work.Clarifications are welcome.
    Award points for helpful answers.
    Rgds,
    Teja

  • PO attachment transfer to ECC - Extended classic scenario

    Hi all,
    We are on SRM 5.0 ECS.As standard,can the SRM PO attachments be transferred to  ECC PO?Is this possible in  ECS?If so,what are the steps?

    HI Alexander,
    The purchase order in the Extended Classic Scenario is transferred to the backend system with different Function Modules. The
    attachment transfer logic was only implemented in the Classic Scenario.
    One reason for this decision was, that the leading Purchase Order in the extended classic scenario is the local one, and in the local purchase order the attachments are available.
    At the moment it is not planned to support the attachment transfer in the Extended Classic Scenario. The transfer of attachments to backend PO is developed only for Classic Scenario.
    I am sorry that this is not the result that you wanted. This also explains why in the ECS PO transfer BADI BBP_ECS_PO_OUT_BADI does not have the parameters for attachments where as the Classic PO transfer
    BADI does (BBP_CREATE_BE_PO_NEW).
    We have some notes related to SC and POR reporting issues when transferring attachments to ECC side, but ther are related to Classic scenario:
    1400088: SC attachments transferred to ECC PR are lost on EHP upgrade
    1413792 Attachment deleted after changing purchase order
    I hope this information help you to understand this issue,
    Kind Regards,
    Rafael Rhoden

  • 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 Scenanio and Extended Classic Scenario

    Hi all,
    I would implement on the same system 2 different scenario:
    1. Classic Scenario for self service procurement
    2. Extended Classic Scenario for the following business scenario:
        a. PR from ECC is transfered into Sourcing Cockpit with Plan Driven Scenario
        b. buyer convert the SC created in Sourcing Cockpit into a GOA or a PO that are transfered to ECC.
    Can coexist this different scenario?
    Can I address this different scenario only with organizational differences?
    Thanks
    Bye
    Marco

    Hi Marco,
    I see 2 quick ways to realise your requirement.
    The first is to create an attribute in t77omattr for a position and maintain that attribute in the organisational model. This attribute could just be filled with an X for example.
    Then you have to implement BADI BBP_EXTLOCALPO_BADI and retrieve the attribute you created with FM BBP_READ_ATTRIBUTES (use sy-uname to retrieve the attribute for the current user).
    The 2nd is to create a Z-table with the user-ids that you want to use the local (or ECS) scenario. Then again in BADI BBP_EXTLOCALPO_BADI  you have to write the logic to retrieve and compare this.
    Keep in mind that these are user-based distinctions and not based on scenario.

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

  • Payment term key with limit days in Extended Classic Scenario

    Hello,
    We have an SRM 4.0 implementation (SRM Server 5.0 with Support Package
    9) using the Extended Classic Scenario.
    When a shopping cart is created, it must be approved, and then a
    purchase order is generated (first locally at SRM, and then is
    replicated to the backend).
    The problem is that the payment term key (field at header level EKKO-
    ZTERM) of the backend purchase order is empty, only in cases when we use a payment term key which have several different values for the
    field "limit days" (T052-ZTAGG in backend, BBP_PAYTERM-ZTAGG in SRM).
    Example:
         ZTERM     ZTAGG
          K180           09
          K180           19
          K180           31
    If the payment term key selected has no several values for the field "limit
    days" (one single entry), the payment term key arrives correctly at the backend purchase order.
    Example:
         ZTERM     ZTAGG
          E000           00
    In SRM table BBP_PAYTERM we have upload the backend payment terms
    (using report BBP_UPLOAD_PAYMENT_TERMS). In other threads it is said that you must copy the entries generated by the report with the logical system of the SRM system, but in extended classic scenario it seems to be not necessary.
    We have already implemented note 846009, in order to use always the backend payment term, but the error didn’t get resolved.
    We have our vendor business partners mapped to the local and backend
    purchasing organizations, but it is only necessary indicate the Payment term key for the Backend Purchasing Organization.
    Regards

    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.

  • 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

Maybe you are looking for

  • Jrockit 1.5.0 not working in mandrake 2005 AMD64 kernel 2.6

    hi, i tried to install jrockit-jdk1.5.0-linux-em64t.tar.gz on a Mandrake 2005 limited edition AMD64 . The processor was Athlon 3000+ RAM 512MB. The Kernel was 2.6 Then i tried to run the java command and no response. the command line just hangs or si

  • Service Order IV

    Hi Gurus.. I have created a Service order with GR-Non valuated.At the time of IV i ma getting a error Account determination for MSL WRX 0003 is not Possible. MSL - Chart of Accounts WRX-GRIR Clearing Transaction event key. 0003 is my Account modifier

  • Reattempt of insert after a ORA-0001 unique constraint violation

    Hi, I'm inserting into a table. The primary key on this table is made up of the user id and a one-up transaction number. Unfortunately, I cannot change the design of this table. Because I have to query the table to get the next transaction number bef

  • File not visible

    Hello..        I have scenario like file-file... I'm unable to see the file in the target directory...even though receiver adapter process the message. There is no error in SXMB_MONI it gives the successfull flag... please let me know what might be t

  • Fuzzy Exclamation Point when I pick a picture

    Hi. I just upgraded to a MBP 15 inch from a G5 iMAC running Tiger 10.4.11. I moved my iPHoto library to an external hard drive, then moved that to the MBP. After openning the iPhoto 09 on the MBP, the library seemed nicely intact. when I look at albu