ECC to PO connectivity

Hi All,
Can you please provide me the steps (like NWA....) to connect ECC and PI java only systems for IDOC /RFC scenarios.
--> ECC to PO Java only
--> PO Java Only to ECC
I have already searched the Forum..but no clarity on steps except new--Program ID.
Please provide me details steps needs to be configured in PO-NWA and ECC.
Thanks you.
Regards,Prasanth

Did you check this?
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5050119d-9c47-3110-eab0-d90ebd211e69?QuickLink=index&…
Michal's PI tips: How do you activate ABAP Proxies with AEX  - simplified version

Similar Messages

  • Error while connecting to ECC using JCO3 connection

    Hi,
    I am getting an error when using JCO3 for connection. I have specified the connection string and created the destination object.
    I get a null pointer exception while setting the import parameter for the RFC. the error is as shown below.
    java.lang.NullPointerException:
    while trying to invoke the method
    com.sap.conn.jco.JCoFunction.getImportParameterList() of a null object loaded
    from local variable 'function'
    the sample code is as follows:-
    destination =JCoDestinationManager.getDestination("ECC destinaton");
    function = destination.getRepository().getFunction("RFC name");
    function.getImportParameterList().setValue("import parameter name", import parameter value);
    function.execute(destination);
    the errror occurs at the line highlighted in red.
    Quick response appreciated.

    Hi,
    part of the ABAP Transports from the SAP Integration Kit are also specific authorization objects. Take a look at the Installation guide for the SAP Integration Kit in the appendix.
    Ingo

  • SAP Upgrade from 4.7 to ECC 6.0 connected to BW 7.0 Best Practices

    We are upgrading SAP R/3 4.7 to ECC 6.0.  We have been running live in a BW 7.0 environment. We have done some enhancements for 2LIS_11_VAITM -  Sales Document Item Data  and 2LIS_13_VDITM - Billing Document Item Data datasources.   We currently have a test instance that has been upgraded to ECC6.0.
    What are the best business practices for testing BW to insure data transfer and enhancements are working correctly?
    Eg. Should we connect the ECC6 instance to BWD and test there OR upgrade R/3 TST that is connected BWD  and test there OR Upgrade QAS and test in BWQ.
    Thanks in advance . . .
    Edited by: RWC on May 4, 2011 6:26 PM

    Hi RWC,
    the plug-in will change slightly, you may notice differences in the screens of RSA2 and others after the upgrade.
    Regarding best practices: In a recent upgrade our project team decided to create a parallel landscape with a new, additional Dev and QA on the R/3 side.
    We connected these new systems to a BW Sandbox and the BW QA.
    We identified all datasources, transfer rules and infopackages in use in production and recorded them with related objects onto transports in BW Dev. Before the import into BW Sandbox and BW QA we adjusted the system name conversion table to convert from old R/3 Dev to new R/3 Dev in order set up all the required connections for testing with the upgraded R/3 systems.
    After the go LIVE of the upgrade we renamed the old R/3 Dev system in BW Dev and ran BDLS to convert everything (speak to your Basis team). That way we made sure not to lose any Development and we got rid of the old R/3 Dev system.
    Take a look at this post for issues we encountered during this project and test everything you load in production.
    Re: Impact on BI 7.0 due to ECC 5.0 to ECC 6.0 Upgrade
    Best,
    Ralf

  • Http RFC destination for ECC to PI Connection Error

    Hi,
    While doing the proxy runtime configuration http RFC destination for ECC to PI .
    I configure the RFC destination as  below ---
    Target Host --  PI Host 
    Service No  -- 50000
    Path Prefix --- /sap/XI/engine/?type=entry
    Login  Security Details
    User Id -- PI user id
    Password --- PI password
    While doing the Connection Test , I got the error "ICM_HTTP_CONNECTION_FAILED"
    I checked  T-code in ECC system SMICM  and ICM is in green status and I checked the services are activated in SICF transaction.
    Please let me know how to resolve this issue.
    regards,
    Rohit

    Hi Rahul,
    I checked  all service are activated in SMICM  and I configured the FQDN also.
    Now  I cofigured the Service No  --- 8000(http port no of PI) instead of 50000(J2EEport no of )
    Target Host --- hostname
    and did a Connection test...then I am getting a status as "http reponse 500" and status text as "empty http request received".
    pls let me know is it correct configured or not.
    regards,
    Rohit

  • ECC To BI Connection Problem

    Dear All
    I have done the following steps to create a RFC connection between ECC and BI.
    Step 1: Define Logical System in R/3
    Step 2: Assigning Logical System to Client
    Step 3: Setting Up an RFC Destination
    Step 4: Distributing Data Model
    Message Types Involved in Process of Data Loading
    Step 5: Generating Partner Profile
    Step 6: Maintaining Message types in T-Code WE20
      while creating the RFC connection in BI the inbound and outbound parameters for BI7CLNT001 and ERPCLNT800 are automatically comes and its working fine.
    But in ECC(did the same steps) the inbound and out bound parameters are not coming.
    I am getting these error while checking the source system u201CSource system ERPCLNT800 is inactiveu201D, u201CCheck failed for RFC connection ERPCLNT800 ; check destinationu201D.
    Experts please help me to resolve this issue.
    Thanks

    Thanks for Your Response.....
    I did the Restore info source Process but it shows there is nothing to restore..
    unfortunately we don't have a basis consultant to resolve this..... plz help me to resolve this...........
    Thanks

  • ECC and SCM connection

    Hi folks,
    i would like to see ECC and SCM scenarios connected by CIF, how ever HU2(ECC) and HU8 (SCM) systems are not interconnected. let us know whom do we need to contact in this regard.
    Thanks in Advance ...

    Hi Amit,
    The ES (emphasis on Enterprise Service or Web Service) Workplace Systems are actually setup for customers or consultants to test drive SAP delivered Enterprise Services, so it stands to reason that integration between these systems would be using web services / SAP Enterprise services for the most part.
    Trying to contact someone to configure CIF / ALE integration between HU2 and HU8 is not going to work for you.
    Regards, Trevor

  • Error while testing ECC and Portal-Connect to SAP gateway failed

    Dear Experts,
    While testing ABAP connection in Portal i am getting below error.

    Dear All,
    My error is rectified with below thread.
    SLDCHECK: Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMIT'...
    Hi,
    You need to create an RFC to the SLDCHECK:
    1. In your web browser, enter the URL of SAP NetWeaver Administrator using the following pattern:
    http://<host>:<port>/nwa
    2. Choose Configuration Management u2192 Infrastructure u2192 Jco RFC Provider.
    3. Choose Create.
    4. Enter the connection and transport parameters as required.
    Field
    Description
    Program ID
    We recommend that you use the following pattern: SLDAPI_<SAPSID>, where SAPSID is the system identifier of the AS Java system.
    Gateway host
    Gateway service
    If your AS Java is an add-on installation to an ABAP system, use the gateway of the ABAP system. You can look up the gateway parameters of an ABAP system using transaction SMGW.
    If your AS Java is a standalone installation, we recommend using a gateway on the Central Services Instance host. As of SAP NetWeaver 7.1, usage type AS Java that comprises SLD also contains an SAP RFC Gateway.
    Server Count (1..20)
    Enter 3.
    5. Choose Next.
    6. Enter logon data to the ABAP repository. You can either use an existing RFC destination from SAP NetWeaver Administrator u2192 Configuration Management u2192 Security u2192 Destinations or you specify the ABAP repository explicitly. The destination should point preferably to an AS ABAP close to SLD. If SLD is running on an AS Java standalone installation, the calling AS ABAP can be used instead. We recommend to create and use an RFC destination instead of explicitly specifying the connect parameters here. In both cases, the following parameters are required
    Field
    Description
    System Landscape Directory 15
    User Manual 03.04.2008
    Application Server Host
    System Number
    Client
    Language
    User
    Password
    Enter the logon data for the AS ABAP system. You must specify an existing user with appropriate authorizations for RFC.
    If you are running a system with both usage types AS ABAP and AS Java, use the logon data for this system.
    If your AS Java is a standalone installation, use the logon data for the calling ABAP system.
    7. Choose Next.
    8. Leave the default values in the next steps.
    9. Create the Jco RFC destination by choosing Finish.
    Result
    The Jco RFC destination creates a number of u201CServer Countu201D RFC server threads on your AS Java. These RFC servers register at the RFC Gateway specified. You may configure multiple ABAP systems to connect to these RFC servers. In this case, the Server Count should be increased when TIME_OUT exceptions are observed.
    Creating an RFC Destination for the SLD ABAP API on the AS ABAP Side
    Use
    If you want to configure an ABAP application to access data in the SLD through the SLD ABAP API, you have to create an RFC destination on the ABAP system side.
    Prerequisites
    An RFC destination for the SLD ABAP API is created on the AS Java side.
    Procedure
    1. Call transaction SM59.
    2. Select TCP/IP connections and choose Create.
    3. In the RFC Destination field, enter SAPSLDAPI.
    4. On the Technical Settings tab page, select the Registered Server Program indicator.
    5. In the Program ID field, enter the same program ID as the one you entered when you created an RFC destination for the SLD ABAP API on the AS Java side. We recommend that you use the following pattern: SLDAPI_<SAPSID>, where SAPSID is the system identifier of the AS Java system.
    6. Choose MDMP & Unicode and select the Unicode indicator.
    7. Choose Save.
    8. Test the RFC destination by choosing Connection Test.
    If the display shows the response times, you have configured the RFC destination correctly.

  • ECC and CRm Connectivity

    Hey all,
    I've been working according the best practices
    CRM Replication
    Building Block Configuration Guide
    to connect an IDES CRM 4 to and IDES R3.
    After many problems the connection between the systems is working and data is replicating,
    but there are some problems because those are IDES systems and there is already data in the systems I get some errors, that I don't know how to deal with.
    In Tx. SMW01 I can see the following errors:
    1. For the MATERIAL queue:
      a. EAN 2348789098765432 does not correspond to the GTIN format and cannot be transferred
      b. Plant 1000 is not assigned to any location
    2. For the Customer_Main queue:
    Customer number 403740 is already assigned to a business partner
    Technical error occurred (4)
    3. For the sales queue:
       Processing of document with Guid 4B683CC54CC25C498F0113CC4A211F16 is canceled
       Business transaction type SO does not exist
       Validation error occurred: Module CRM_DOWNLOAD_BTMBDOC_VAL, BDoc type BUS_TRANS_MSG.
    How can I fix those errors, its look like customizing errors...
    Thanks alot
    Natti.

    Hi,
    Any update onthe above issue. I am also facing the same problem.
    Regards,
    Khan

  • Connect one SAP ECC 6.0 source system to 2 SAP BW system

    Hi!
    I copied SAP BW system (e.g. BW1 --> BW2).
    My source SAP BW system "BW1" was connected to SAP source system "MM5" (tcode RSA1).
    Now I would like to connect my new SAP BW system "BW2" also to this SAP source system "MM5".
    When I do so I get the following error:
    Connection cannot be used.
    Connection BA is used in the MM5:400
    source system as a connection BW1CLNT001 to BW
    Do you want to delete this connection in the source system?
    Question:
    Can one SAP ECC system be connected to 2 SAP BW system?
    If yes, what are the steps to do this?
    Thank you!

    Thank you very much!
    The question still is how to proceed with the following dialog screen/warning?
    Connection cannot be used.
    Connection BA is used in the MM5:400
    source system as a connection BW1CLNT001 to BW
    Do you want to delete this connection in the source system?
    YES or NO
    Thank you!

  • ECC System Refresh  - impacts IDOC connections to PI

    All,
    Whenever we refresh ECC QA system with prod, we have to do all the ale/IDOC settings all over again in ECC QA to connect to QA PI.
    Can you please list the tables that are used for We20, We21, BD64, SM59 so that BASIS can take a backup of these tables before refresh and apply the backup once the system refresh is complete.
    Thanks. 

    Hi Vicky,
    Partner profile (WE20) is store in below tables
    EDPP1: General partner profile
    EDP12: Partner profile outbound, additional data NAST
    EDP13: Partner profile outbound
    EDP21: Partner profile inbound
    regards,
    Harish

  • PI connections to Load Balancer on ECC

    Hi All,
    I have a doubt regarding PI connections to ECC.
    Where can we check how does PI connect to ECC.
    What is url or host name and port it is using.
    what is the protocol.
    also if there is a load balancer used for ECC. How should PI connect to it.
    Thanks

    Hi Prabhu,
    --> If you want to know whether the ECC system is connected your PI system or not.
    -->If you want to import the interfaces like RFC and IDOC from your ECC into PI system we need to have connection from PI to ECC.
    -->Its quite simple while creating the name space select the radibutton import of rfc and idoc from the sap systems permitted and maintain the required parameters and under imported objects try to import the RFC or IDOC if the connection is established with ECC from PI list of IDOCs and RFC's will be displayed.
    -->other wise it throws connection to ECC is not established.
    -->It does not matter whether we are sending the IDOC or receiving the IDOC from ECC.Because the connection is not dependent on these factors.
    -->For connection with  ECC port is not required.But in the case of Idoc scenario it is required.
    Thanks

  • Provider Webservice in Backend ECC system (NW 7.0, Enp1) and PI /XI 7.0,

    Hello
    Our backend ECC is on EnhP4 (there by NW 7.0, EnhP1), As I understand, since NW 7.0, SP 14, webservices runtime has been changed significantly to support asynchronous webservices (through WS-RM).
    This ECC system is connected to our PI 7.0 system. In the back end ECC system, when I create ABAP server proxy for a synchronous interface from SPROXY, the generated proxy is also visible as a service in SOAMANAGER. However, when I do the same for asynchronous interface, the service is not visible in SOAMANAGER.
    Is this an expected behavior? Does this mean, we can only expose 'out side in' approach webservices in synchronous mode if the ESR is of version 7.0? The reason I say this is when I connect the same ECC system a PI 7.1 system, I am able to expose asynchronous services that are generated out of SPROXY.
    The intent here is to design the interfaces in XI 7.0, expose them as web service in ECC and consume the webservice using another EAI tool that supports WS-RM.
    Any help will be appreciated.
    Thanks
    KK

    Stefan
    Thanks. Your answer makes sense with what we are observing. Do you know if this is documented somewhere in help documentation or some note.
    On another note what doesn't make sense to me is why this limitation? Not sure what I am missing. Doesn't the webservice runtime in NW 7.0 support WS-RM from SP14. Why should it be dependent on the version of PI in case of point to point webservice. Unless you say we can use WS-RM in back end NW 7.0 through PI 7.1's WS adapter only.
    For me this sounds like a limitation on the NW 7.0/SP14 side. What do you think?
    KK
    Edited by: Krishnakumar Ramamoorthy on May 31, 2009 5:50 PM

  • Connect to SAP gateway failed Connect_PM  TYPE=B

    Hi experts,
    I get the following error when i ping through JCO destinations on portals.
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM  TYPE=B MSHOST=imtsapdev01 GROUP=CLUST R3NAME=DMI MSSERV=sapmsDMI PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       partner '127.0.0.1:3310' not reached TIME        Tue Jan 27 16:39:54 2009 RELEASE     700 COMPONENT   NI (network interface) VERSION     38 RC          -10 MODULE      nixxi.cpp LINE        2823 DETAIL      NiPConnect2 SYSTEM CALL connect ERRNO       10061 ERRNO TEXT  WSAECONNREFUSED: Connection refused COUNTER     1
    However my JCO destinations were working perfectly until recently. I checked on the logon group. I have one called CLUST, which i use for this purpose.
    I have also checked both service files and they have the following for the ECC server im connecting to.
    3610 because its system number 10 i am connecting to.
    sapmsDMI 3610/tcp
    From the JCE destinations screen i cannot even ping the server. I can though when i log on to the server through remote desktop.
    thanks and regards
    dilanke
    as a reply to nishants posts.
    goto rz70
    give hostname -->
    service --> sapgw00 (sapgw(instance number)
    execute it
    click on yes
    check rfc call (success or failed)
    I have done this. i left hostname as "blank" gave service as "sapgw10"
    The following is what i  got as the output.
        0: IMTSAPDEV01_DMI_10                        : Execute program: SLDRFC
        0: IMTSAPDEV01_DMI_10                        : Execute program: SLDMSGSRV
        0: IMTSAPDEV01_DMI_10                        : Execute program: SLDIPSERV
        0: IMTSAPDEV01_DMI_10                        : Execute program: SLDINSTSP
        0: IMTSAPDEV01_DMI_10                        : Execute program: SLDINSTSC
        0: IMTSAPDEV01_DMI_10                        : Execute program: SLDGWSRV
        0: IMTSAPDEV01_DMI_10                        : Execute program: SLDDBSYS
        0: IMTSAPDEV01_DMI_10                        : Execute program: SLDCOMPSYS
        0: IMTSAPDEV01_DMI_10                        : Execute program: SLDCLIENT
        0: IMTSAPDEV01_DMI_10                        : Execute program: SLDBCSYS
        0: IMTSAPDEV01_DMI_10                        : Execute program: SLDAPPL_SERV
        0: IMTSAPDEV01_DMI_10                        : Execute program: SLDASSOC
        0: IMTSAPDEV01_DMI_10                        : Collection of SLD data finished
        0: IMTSAPDEV01_DMI_10                        : Data collected successfully
        0: IMTSAPDEV01_DMI_10                        : RFC data prepared
        0: IMTSAPDEV01_DMI_10                        : Used RFC destination: SLD_NUC
        0: IMTSAPDEV01_DMI_10                        : RFC call failed: Error opening an RFC connection.
        0: IMTSAPDEV01_DMI_10                        : Existing periodic jobs removed. Number: 1
        0: IMTSAPDEV01_DMI_10                        : Program scheduled: 20090127 184357
        1: IMTSAPDEV01_DMI_10                        : Event-controlled job already exists; scheduling not necessary
    so i guess its not successful. when i look at rz70 of a server where this works correctly its not succsessful either
    if it is success then technical system name will be in sld
    to restart sld --> /sld --> administration --> stop server --> restart server
    or check in VA --> SLD data supplier value --> Runtime
    I checked this and i do not see aa problem. you have configuration status as valid and send reult as Success
    Services file is locted on OS level of R3 system--> Goto --> Start --> Run -> (type)Drivers(enter) --> etc -> (here is services file)
    check ur r/3 server entry is there or not,
    I have the followng in the service file for the server
    sapmsDMI 3610/tcp
    if not add it

    Hi Experts,
    when ilook at the remote gateway properties in SMGW this is what i see on the R/3 server. ive looked at my other system which i can connect to and there isnt much of a difference in the parameters. How can test this to see if it works?
                                                                                    Details of remote gateway                                                                               
    entry                         = 0                                            
      state                         = CONNECTED                                    
      local                         = 1                                            
      system type                   = REMOTE_GATEWAY                               
      client                        = FALSE                                        
      wait for frag write           = 0                                            
      suspended                     = 0                                            
      read/write socket             = 4                                            
      HANDLE                        = 4                                            
      TIME                          = Sun Oct 19 18:54:14 2008                     
      SOCKET                        = 1352                                         
      STAT                          = NI_CONNECTED                                 
      TYPE                          = STREAM IPv4                                  
      OUT                           = 48225 messages 48225 bytes                   
      IN                            = 1 messages 64 bytes                          
      LOCAL                         = 127.0.0.1:3310                               
      REMOTE                        = 127.0.0.1:1297                               
      OPTIONS                       =                                              
      connect                       = Sun Oct 19 18:52:17 2008                     
      last request                  = Thu Jan 29 13:09:58 2009                     
      conversation no               = 0                                            
    thanks and regards,
    dilanke

  • Enterprise Project Connection 2.0 - Architecture

    Hi,
    We are implementing EPC 2.0 to link between Oracle Primavera & SAP PM for turnaround scheduling. We have 1 ECC instance that used by different users from our offices around the globe. I couldn't find here SAP Enterprise Project Connection 2.0 – SAP Help Portal Page information about the architecture recommendation. For example, which is better :
    Having 1 single EPC instance close to the ECC that is connected to 1 Primavera DB and the Primavera clients in all the regions access this DB that is colocated with ECC & EPC ? or
    Having 3 EPCs, 3 Primavera DBs (in each region) and all these are connected to the single ECC instance.
    Performance wise which is better ? is the 2nd option valid  (many EPCs to 1 ECC) ?
    We couldn't find answers to this.
    Any help is appreciated.
    Regards,

    Hello Debasis,
    Post EPC installation,you need to perform configuration of EPC through portal.You can see it listed under configuration--> configuration scenarios-->EPC.
    During configuration you will be asked to define path of you primavera installation and a user on that system with sufficient permissions. This user is called APS user.
    Try to do a mock configuration run on sandbox/dev system and then you can follow the guide.
    Regards,
    Hetal

  • Classic Scenarion with MM-SUS (SUS-ECC-SRM/EBP)

    Hi SRM Gurus,
    We are going for SRM Classic Scenario with MM-SUS . SRM 7.0 with ECC 6.0 (Ehp4).
    Here ECC will be connected to SRM and SUS ,i..e SUS-ECC-SRM.
    I learnt that Classic deployment supports MM-SUS scenario. It means that , every document created in ECC or SRM(EBP) need to replicate in other 2 systems. I have concerns about this replication in 2 another systems.
    1. PO-S/C in SRM , creates classic PO in ECC Is this PO sends to SUS ?
    2. Confirmation-Is Confirmation done in ECC/SUS/SRM replicates in another 2 systems ?
    3. Invoice-Is Invoice done in ECC/SUS/SRM replicates in another 2 systems ?
    Can anyone please confirm /suggest , whether this happens or not ?
    Regards
    NAP

    Narendra
    I learnt that Classic deployment supports MM-SUS scenario. It means that , every document created in ECC or SRM(EBP) need to replicate in other 2 systems. I have concerns about this replication in 2 another systems. - EVERY DOCUMENT IS NOT CREATED IN 2 OTHER SYSTEMS. SRM PO GOES TO ECC AS CLASSIC PO. THIS CLASSIC PO IS SENT TO SUS WHERE IT CREATES A SALES ORDER FOR VENDOR. SO ITS NOT REALLY EVERY DOCUMENT IN TWO OTHER SYSTEMS
    1. PO-S/C in SRM , creates classic PO in ECC Is this PO sends to SUS ? - ECC PO WILL BE SENT TO SUS. SRM-ECC INTERFACE REMAINS SAME HERE. THERE IS NO COMMUNICATION BETWEEN SRM AND SUS
    2. Confirmation-Is Confirmation done in ECC/SUS/SRM replicates in another 2 systems ? - CONFIRMATION CAN BE DONE EITHER IN SUS(RECOMMENDED), OR IN SRM, OR IN ECC. CONFIRMATION CREATED IN SRM AND SUS WILL RESULT IN CREATION OF GOODS MOVEMENT IN ECC. GOODS MOVEMENT CREATED IN ECC WILL BE ONLY UPDATED AS A  KIND OF FOLLOW ON DOCUMENT IN SUS AND SRM
    3. Invoice-Is Invoice done in ECC/SUS/SRM replicates in another 2 systems ? - INVOICECAN BE DONE EITHER IN SUS(RECOMMENDED), OR IN SRM, OR IN ECC. INVOICE CREATED IN SRM AND SUS WILL RESULT IN CREATION OF MM INVOICE IN ECC. INVOICE CREATED IN ECC WILL BE ONLY UPDATED AS A  KIND OF FOLLOW ON DOCUMENT IN SUS AND SRM
    I hope it clears your doubts....
    Regards
    virender Singh

Maybe you are looking for