XI integration objects for Extended Classic Scenario

Hi!
We are implementing XI inetgration for ECS. The process is that PO is sent to XI from EBP, and then SO created in SUS. Also ASN is created in SUS and then sent to ERP system.
Could you please tell me what integration objects (*.TPT files) should be imported to XI for this purpose? The links to this files on Service Market Place will be very helpful.
P.S. We are running SRM Server 5.5 and R/3 4.6C.
Best Regards,
Siarhei

https://websmp205.sap-ag.de/swdc ---> Download ->Support Packages and Patches->Entry by Application Group --->SAP Content ->ESR Content(XI Content)->XI CONTENT SRM SERVER ---> XI CONTENT SRM SERVER 5.5
this is the path

Similar Messages

  • 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

  • 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

  • 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

  • Partner functions in EBP for extended Classic Scenario

    Hello Guru's,
    I have a few questions on handling partner functions in SRM 5.0 extended classic PO..
    We are planning to use a freight vendor partner as one of the partner functions. The PO raised should go to both the parties from SRM.
    Is the output handled in SRM or do we have to use the copied PO on R/3 to send it over to the freight vendor.
    Could someone throw in some points.
    Thanks
    Manoj

    Hi
    I think, we cannot send PO output to multiple partners (vendors) at one point of time.
    You need to use the 'repeated output' check box in the 'output' tab of PO in SRM to send the PO to other partners.
    Rgds
    Reddy

  • OPEN purchase order for Extended classic scenario

    Hello All,
    I want to is there any way to find out Open PO in SAP SRM
    like ME2* reports in MM
    Can I extract the report via CRMD_ORDERADM* tables?
    Thanks
    Raman

    Hi,
    You can try the foll:
    1st way is to look into the standard tables in the SRM system
    CRMD_ORDERADM_H (Header Data)
    and
    CRMD_ORDERADM_I (Item Data)
    for the Business object type - BUS2201 (Purchase Orders)
    2nd way is using BBP_PD Transaction for the Business object type - BUS2201 (Purchase Orders) (The transaction calls the same tables to fetch the details)
    3rd way using the standard function modules - BBP_PO_GET_DETAIL / BBP_PD_PO_GETLIST ,In the FM "BBP_PD_PO_GETLIST " ,you have the import parameter "I_IV_OPEN",try to use that for reteriveing the list of open Po's.
    BR,
    Disha.
    Do reward points for  useful answers.

  • PO Output in ERP for Extended Classic Scenario

    Hi!
    We have ECS up and running and now we would like to transfer PO to SUS, but not from EBP system. We would like to do this from ERP system because ASN creation from SUS functionality is really needed for us.
    So, we have configured ERP system for message output (for message type NEU), but when PO is created in ERP system output is not created.
    Could you please help me to solve this isssue?
    Thanks and Regards,
    Siarhei

    Hi,
    Which SRM version are you working on??
    There is a Consulting note 883693 might help - we use it to allow EDI output of our catalog POs in R/3.
    The note 883693   in which the steps are explained to use R/3 output when using ECS, however this is only valid for SRM 4.0 (SRM_SERVER 5.0).So it wont be helpful for you if  you are on release SRM 5.0.
    Another workaround would be to implement the BADI BBP_PO_INBOUND_BADI in ECC.In ECC BAdi BBP_PO_INBOUND_BADI, method BBP_MAP_BEFORE_BAPI ,you and write  custom code to generate output for SRM copy PO .
    Hope this helps .
    BR,
    Disha.
    Do reward points for  useful answers.

  • Organization structure in extended classic scenario

    Hi All
    I  am trying to configure extended classic scenario on SAP SRM 7.0.  I have made the following settings for the same:
    1. In SPRO->SRM Server-> Technical Basic Settings -> Define backend system from product category, I have specified target system as SRM system and not ECD system
    2. In SPRO->SRM Server->Cross Application Basic Settings-> Activate Extended Classic Scenario, I have selected all the options including "Back end purchasing group responsible"
    I have a few doubts.
    1. In organization Structure (PPOMA_BBP) Comapny code is corresponding to company code in back end but do I have to create local purchasing organization and local purchasing group i.e. in Functions-> Corresponds  I'll have to leave blank. plz suggest
    2. Also is IPC configuration mandatory for extended classic scenario
    Plz give your suggestion on above mentioned issue
    Regards
    Pawan Keshwani
    Edited by: pawankeshwani on Mar 18, 2011 8:33 AM

    Hi Pawan,
    No you should mention Purch Org & Purch Grp also wrt your backend (ECC).
    IPC need not be configured separately from SRM 5.0 onwards. To ascertain if IPC is working fine just run the report : RSVMCRT_HEALTH_CHECK. You should see 4 success messages. Else get in touch with Basis to enable Virtual Machine Container (VMC)
    Regards,
    Nikhil

  • Extended classic scenario to Classic scenarioc in SRM.??

    someone pls tell me how to change from Extended classic scenario to Classic scenarion while creating in shopping cart...?
    I am using BADI "BBP_EXTLOCALPO_BADI" change to classic scenarion from extending classic..but i got confused about source code..So i request any one can help me for suitable source code..

    Hi
    Do you mean to say that you have set up Extended Classic Scenario but you want to change it to Classic Scenario?... If this is the case, remove the activation in COnfiguration for Extended classic scenario and deactivate BADIs you ve implemented for Extended Classic
    OR
    Do you want to change it to Classic only for the Document user is creating.--> Read the indicator or data from SC and decide whether the document has to be in Classic or Extended classic SCenario.... The BADI will either have Extended classic = X or NOT.... so there is no parameter for classic Scen... Depending on your requirements, implement the ext. classic badi to SET it or NOT set it...
    Regards
    Virender SIngh

  • Pricing conditions in extended classic scenario

    Hello friends,
    I have a question about pricing conditions. There is a condition in R/3 where the price can be redetermined based on the G/R date. Is it to do something similiar in SRM. I mean redetermine the price at the time of confirmation.
    Thanks any help will be appreciated.

    Hello Chakradhar,
    IPC is required for extended classic scenario. Reach out to your basis practitioner, he should be able to perform this.
    Helpful links
    Re: IPC Configuration in Functional perspective.
    Re: IPC Configuration
    Hope this helps.
    Thanks
    Ashutosh

  • Configuration of Service procurement for Extend Classic

    Hi SRM Gurus,
    Can anyone send me the configuration documents for configuration of service procurement for extend classic scenario.
    I have referred to SRM Enterprise Buyer 5.0 Configuration (SRM 210) and SAP Library. But both of these doesn't talk about the configuration steps involved in that.
    Any documents, leads and help would be highly appreciated. My email id is [email protected]
    Thanks
    Ramgopal Verma

    Hi,
    In plant Y, you have to maintain Spl.procurement key in material master. In MRP 2 view assign External procurement & spl.procurement kery 40.
    In the plant X, create material master as inhouse production in MRP 2 view.
    Have to maintain BOM & Routing in plant X.
    Configure in SPRO> MRP> Planning> Define spl.procurement key.
    In this assign Issue plant as X.
    Run MRP for plant Y. System create Stock transport req in plant Y.
    Convert this req into stock transport order.
    In plant X, dependent req will create.
    Use MB1B mvt type 301for single level stock transport.
    For multi level stock transport use MB1B 303 - issue & 305 -receive mvt.
    Regards,
    Dharma

  • 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

Maybe you are looking for