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

Similar Messages

  • 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

  • SRM PO replication to backend ECC (Extended Classic Scenario)

    I would like to have inputs on this scenario, as which BADI we need to use and what we need to do exactly to replicate PO from SRM 5.5 to ECC 6.0.
    Thanx and Regards

    Hi,
    just try out the following:
    If you activate the BAdi, make sure to take over all Import params into your Export params!
    Otherwise data may be lost!
    Here is an example:
    *-- data declaration
    Data:  wa_longext like line of ct_longtextt,
              wa_item like line of et_item,
              zw_index type sy-index,
              zw_counter type ec_counter.
    *-- take over all import data to exp params
    es_header = is_header.
    et_item[] = it_item[].
    et_partner[] = it_partner[].
    et_account [] = it_account[].
    et_orgdata[] = it_orgdata[].
    *-- Change data
    *--  modify given vendor longtexts (ITXT) for example with a standard text
    *-- for all positions
    clear zw_index.
    Loop at ct_longtext into wa_longtext.
    zw_index = zw_index + 1.
    if wa_longtext-tdid eq 'ITXT' ." Vendor Text
    wa_longtext-tdline = 'Here your Text'.
    modify ct_longtext from wa_longtext index zw_index.
    endif.
    endloop.
    *-- or if you would like to add a line of text to a position
    *-- loop over positions and read text for vendor text
    loop at et_item into wa_item.
    clear zw_counter.
    loop at ct_longtext into wa_longtext
    where  guid = wa_item-guid
    and     tdid = 'ITXT'
    and tdspras = '???'." -> your language (E= English, D= German...)
    endloop.
    *-- if position contains vendor texts already, you know the counter index
    *-- add 1 to counter to get the "new" index for your new line
    zw_counter = wa_longtext-counter + 1.
    wa_longtext-guid = wa_item-guid. "to combine the text with the SC position
    wa_longtext-tdid = 'ITXT'.
    wa_longtext-tdspras = '??'.
    wa_longtext-counter = zw_counter.
    wa_longtext-tdline = 'Your Text'.
    append wa_longtext to ct_longtext.
    endloop.
    This is just an example which I have coded right now.
    Hopefully without any syntax errors.
    Of course you have to adopt this coding to your requirements.
    Best regards
    Andreas

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

  • Material PO confirmation at supplier side (SUS) not taking place in SRM SUS Extended classic scenario

    We have configured extended classic scenario SRM with SUS, and all functions are working fine. However, at the time of PO confirmation of material item at the Supplier side (SUS), the material line item disappears when we click on the Create Confirmation button in SUS. The functionality is working fine for Service Items. The total value of PO is also displayed correctly in the Items overview section.
    Please provide some help in solving this issue.

    Hello,
    This is the correct behaviour of SUS - confirmations can only be created for service items which in turn create service entry sheets (Trx: ML81N in ECC).  And accepting the SES in ML81N will generate GR posting.
    For material items, you have to create ASN which will in turn create inbound delivery in ECC which you can post and will generate goods movement documents.
    So basically, for service items you create confirmation and for materials you create ASN.
    Regards,
    Prasanna

  • 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

  • Can we use the Extended Classic Scenario with MM-SUS

    HI, expert :
        In extended classic scenario ,the PO created in SRM system ,and then replicated into the MM system .You  can't change it  in MM system .
        So, in this situation ,I want to know the MM-SUS can be  suitable or not ?The PO can transfer from ECC  to SUS ?
       If I use the decoupled  scenario  ,which one I can select ?MM-SUS or EBP -sus ?
       BR !
      Alex!

    Hi Alex,
    as noted by Bill, in MM-SUS is the extended classic not possible at all.
    By default it's also not supported in the SRM-SUS. Please see the note 543544. If you would like to activate this, you need to pay a consulting fee for SAP:
    "Please note that the full scenario can be enabled by a consulting solution, compare OSS note 700350."                                  
    Regards,
    Peter

  • Use the MM-SUS in Extended Classic Scenario

    HI,my experts :
        The standard function doesn't support the MM-SUS in Extended Classic Scenario .Now I may have two questions about it .
      1、  I have one ECC system .I need handle the invice in the ECC system .In other word ,the invoice rcreated in the SUS should transfer to the MM system .But in EBP-SUS ,the invoice is transfered to the SRM system .What can I do now ?
      2、 If  I  want to use the decoupled scenario ,some POs are create in EBP ,and others are created in MM .Now ,which sus I should select ? EBP-SUS  or MM-SUS?
       Or some detail document about it .
      BR!
       Alex!
    Edited by: Alex on May 25, 2010 9:17 AM

    Khan has explained most of the things.
    The external web service I meant is actually OPI catalog which you need to maintain.
    The same has to be entered in the attribute CAT of the EBP purchaser.
    To maintain the call structure of this catalog
    Get the URL from SE80->BSP appln->ros_prescreen->controller->main.do
    then give the client no of yr ROS client
    the RFC user user ID from EBP to ROS
    it's password
    sap-sessioncmd=open
    sap-language=sy-langu
    the operational purchaser role in EBP (sap_EC_BBP_OP_PURCHASER) should be linked with
    the same in ROS via role menu->business partner->screen supplier->right click->change details
    ->sap-client=ROS client no
    The administrator & op purchaser should be present in ROS org structure also
    & should have same userID & password as EBP
    you have to define the vendor root, the root of the purchasing organization and the currency in
    table BBP_MARKETP_INFO in the SRM System (Enterprise Buyer client).
    BR
    Dinesh

  • 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

  • Output(print out) in SRM for backend PO in Classic scenario

    Hello,
    My requirement is to take print out for the backend PO created thru shopping cart in classic scenario.
    i know for extended classic scenario Actions works as in that case PO is created locally and then replicated.
    But in the classic Scenario where the PO is in backend, can we take print out in SRM becasue the detials of that Po is available in SRM to in Fllow up documents in SRM 5.0.
    is there any standard way available to achieve that.
    Thanks
    Robin

    Hi Sarabjeet,
    It does not make sense to print PO from SRM in classic scenario because there is no PO in SRM at all !
    In classic scenario, PO is created only in the backend.
    Only shopping cart is created in SRM.
    Kind regards,
    Yann

  • 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

  • SUS-MM vs SUS-EBP (Extended CLassic Scenario)

    Hi!
    We have an extended classic scenario already up and running between ERP->EBP system without XI usage.
    Now it is necessary to configure SUS integration for ASN creation purpose. As I can see SAP has 2 standard configuration guides: one for SUS-MM and another one for SUS-EBP, but they are not fully relevant for ECS.
    Could anybody tell me please from what system EBP or ERP it is better to send PO to SUS system when we are using extended classic scenario? And what are advantages/disadvantages of this?
    Thanks and Regards,
    Siarhei

    Hi Dinesh!
    Thank you for your answer! It is clear that leading PO is in EBP, but why I can't use ORDERS and ORDCHG IDOCs to transfer PO and PO chnages to SUS?
    One other question: do you know whether Configuration Guide for ECS exsits (like SUS-MM and SUS-EBP documents)?
    BR,
    SIarhei
    Edited by: Siarhei Tsikhanenka on Apr 4, 2008 9:56 AM

  • 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

  • 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

  • Output from backend in extended classic

    Hi Experts,
    In extended classic scenario it is possible to sent the output from backend?
    Does anyone know have to activate this, and how to deactivate the output control from SRM.
    Proces as I want it:
    - Creates a shopping cart in SRM.
    - Creates a PO in SRM on behalf of the shopping cart, no output.
    - The PO from SRM is replicated to R/3.
    - The PO is sent to vendor fra R/3.
    Best regards
    Kim Oster

    yes franz is correct. we can do this from consulting note which he mentioned.
    PO Output messages for ECS PO's
    br
    muthu

Maybe you are looking for