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

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

  • 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

  • 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

  • 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

  • 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

  • SRM PO Pricing condition from SRM to ECC -Extended Classic Sceanrio

    Dear SRM experts,
    We have created couple of conditions in SRM7.0 and ECC 6.0 as per requirement. When we create PO in SRM and If we add any condition in SRM PO, PO is getting transferred with netprice(including condition amount).
    We would like to see conditions also in ECC which are there in SRM.
    For ex:
    I have created SRM PO with net price 30 and having freight amount(15) in that PO with Fregiht condition type but when it comes to ECC PO net price is changing from 30 to 45.
    We would like to see net price as 30 and 15 as Fregiht condition.
    Overall I can say that Is it possible to pass conditions from SRM to ECC in Extended classic scenario.
    Thanks
    Ravi

    Hi,
    the challenge lies in synchnizing the conditions and ensuring that price returned by IPC in SRM matches the price in the backend.
    Please see thread
    Pricing Conditions
    Regards
    Azad

  • SRM Extended Classic Scenario

    HI,
    Please let me know in the extended classic scenario when the PO is created in SRM does the same PO  number gets created in the backend system.Also is the PO created in the Backend system can be opened in transaction ME21N or it can be viewed only in ME22N transaction.
    Thanks,
    Manu

    While configuring consultant has to maintain the same number range in both systems. This way the PO number created in SRM system remains the same as in backend ECC system.
    This PO is only readable in backend system. Only ME23.. transactions can be used to view this. If user is allowed to modiify this PO in backend system it will lead to inconsistency between the systems.

  • 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

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

  • 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

  • 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

  • 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

  • Use of Purchase info records in SRM SC in Extended Classic scenario

    Hi All,
    We have implemented SRM 7.13 with Extended classic scenario. If we have Purchase info record in SAP ECC for the material, it gets populated in SRM SC in Source of supply Tab but the price of Purchase info record does not get updated in the SC line item.
    Can anyone let me know which configurations is required to fetch the Purchase info record price or we need to have a customization to achieve this.
    Thanks,
    Ankur

    HI Ankur
    when you say the price did not get updated did you check the sequence which is used for price determination ?
    1. User entry
    2. Contracts
    3.  Info record
    If still you think it is an issue please check the report  EBP_GET_BACKEND_PRICES and let me know if your problem gets fixed?
    Regards
    Vinita

  • 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

Maybe you are looking for

  • Error "mzm.nvyhpxhw.pkg could not be extracted" when downloading bioshock from app store

    Hi guys, I was trying to download bioshock the game from the app store and it gets about 75% through and then gets an error message "mzm.nvyhpxhw.pkg could not be extracted". I have tried many times and the same thing keeps on happening, what should

  • [HELP] Installing Windows 7 on MBP by USB using Boot Camp

    Hello! Im using boot camp to try to Install windows 7 on my MBP. The problem is my cd/dvd driver is broken and I cant use DVD to boot from. I tryed to install by USB but when Im about to restart and boot try to boot the windows that I installed on th

  • Error when starting up tomcat

    When I try to statup Tomcat i get this error Cannot find the file "-Dsun.io.useCanonCaches=flase"( or one of its components ). Make sure both the path and filename are correct and that all required libraries are available. Any help would be much appr

  • How to revert file associations in Win8 back to CS6?

    I have tried out CC. I am not convinced of its merits and worth the money, so I let the subscription end.No problem. I have CS6. But how can I revert file associations for example for .PNG or .JPG files back to PS CS6, instead of PS CC? Everytime I c

  • Can I change color of all objects at ones ?

    Hello guys I understand that's very fundamental question, and I promise I search the forum prior to posting, but perhaps it's my bad english and wrong phrasing, that leads to poor results. So if that has been discuss, please kindly don't waste your t