Issue in RFC communication between ECC and PI

Hi Experts,
We are upgrading our systems from SAP R/3 to SAP ECC. We have couple of synchronous interfaces between SAP ECC <-> SAP PI <->Webservices.
In R/3 these interfaces are working as expected and passing the data in correct format to PI. But same RFC in ECC is not passing correct data to SAP PI.
Our design is : ECC creates an IDOC and then from the port program it calls the RFC to send data to PI. I tried debugging this port program and until the RFC data is correct in the tables, but as soon as RFC hands over data to PI, data is getting messed up.
Below is the example.
Data in RFC : has data like this
TES_TRANS_NO     MATERIAL     UNIT     QUANTITY     SHIP_DATE
1003                         MMT-XXX     EA          1                    20140722
But when data comes to PI it is something like this:
<?xml version="1.0" encoding="UTF-8" ?>
- <rfc:ZIDXF_WS_ORDER_STATUS xmlns:rfc="urn:sap-com:document:sap:rfc:functions"> 
<ORDER>1003</ORDER>  
- <ITEM> 
- <item> 
<TES_TRANS_NO>1003</TES_TRANS_NO>  
<MATERIAL>EA 1 20140722</MATERIAL>  
<UNIT_MEASURE />  
<QUANTITY />  
<SHIP_DATE />  
</item>
</ITEM>
</rfc:ZIDXF_WS_ORDER_STATUS>
Material number is not being mapped and all other remaining fields are being concatenated somehow and being mapped to Material.
Please help if anyone has any ideas.
Thanks,
Sameer

Issue resolved:
RFC Destination was Non-Unicode in R/3, for ECC we changed it to Unicode (As PI system is unicode), and it worked.
Thanks everyone.
Sameer

Similar Messages

  • Communication between ECC and CRM

    Hello,
    I am in phase of showing communication between SAP CRM 5.0 and ECC 6.0.
    I am struggling with finding some simple transactions which are common in both, with which I can show correct connectivity between ECC and CRM.
       I need to save some data from CRM and access the same via transaction within ECC, save some data via ECC and access it via CRM. I already established RFC link between ECC and CRM.
    Probably communication between SD module of ECC with CRM.
    Can you please help me out with this, a clue/correct direction will be of very helpful. Basically I want to know, what transaction I can use for same.
    Any help is really appreciated.
    Thanks
    -Vishal

    Hi Glenn,
          I followed all steps in document mentioned above. In the end during execution of transaction I selected appropriate source and destination, when I click start transfer objects, it gets stuck in waiting phase.
    Among those steps I was not able to perform step#10. Creating Subscriptions for OLTP. My ERP is not displaying this option under subscription wizard. Should it be reason for not starting transfer ? I also do not see ERP logon screen when I select transfer.
    My another question is when transfer will complete, where I'll be able to see transferred objects within ERP database ?
    Thanks
    -Vishal

  • Best communication between ECC and PI

    Hi All
    SAP is planning to adapt Enterprise Service Architecture (ESA) in the journey towards Service Oriented Architecture (SOA).
    We are working on new implementation project. We have many asynchrounous scenarios. We would like to configure acknowledgements and also like to handle errors effectively.
    Could you please suggest which communication between ECC and PI  is preferrable?
    (Webservices, IDoc, BAPI or RFC)
    Thanks
    Sai

    IDoc, BAPI , rfc - all can be used for seamless communication between ECC and PI. It is totallu dependant on the application and way information is exchanged. For master and transactional data idoc are prefered as for the acknowledgements supported by it. Not sure how effeciently we can handle system and appl ack incase of bapi/rfc. but at the same time idoc will be a drawback for sync comunication where rfc/bapi is preferd. It is SOA or ESA the concepts build in SAP are targeted to serve the enterprise needs where idoc,bapi/rfc are used for servicing the business unit objectives

  • Optimize the performance of the RFC call between ECC and CRM

    Hi,
    We are planning to extract sales orders, sales activites and service orders to dispaly it on the  PDF factsheet of the account.
    As of now, the PDF factsheet takes a long time to retrieve the data from ECC to CRM. Can you please suggest us on ways to  optimize the performance of the RFC call between ECC and CRM.
    Thanks in advance,
    Vamsi.

    Hello,
    [SAP Note 636906 |https://service.sap.com/sap/support/notes/636906]is quite useful here.
    Many times, the performance is poor due to function module CRM_CCKPT_EXPORTSUMMARY. This function module gets the customer number, the sales organization and the fact sheet view. If in CRM customizing, you use complete view (001), then all the views in ERP including all the info blocks will be retrieved, which will cause performance issue.
    To solve the issue, please use a limited view to retrieve the data from ERP - especially a view, which does not contain info block 013.
    Hope it helps
    Joaquin

  • Communication between ECC and SCM via XI

    I am trying to set up the scenario 'Purchase_Order_Processing' between
    ECC and SCM using XI. The SCM content for XI has been loaded into XI
    and this scenario is included in the content.
    We are running the following:
    ECC - Version 5.0 - 640 SP level 12
    XI - Version 3.0 - 640 SP Level 14
    SCM - 4.10 - 640 SP Level 12
    The connectivity between the systems has been set up as described in the configuration guides. On sending an IDOC (basic type ORDERS05) into XI I get the following error message 'Http server code 500 reason Internal Server Errorexplanation Error during parsing of SOAP header'.
    The Error XML is as follows:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!-- Call Adapter
    -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
    SOAP:mustUnderstand="">
    <SAP:Category>XIAdapter</SAP:Category>
    <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
    <SAP:P1>500</SAP:P1>
    <SAP:P2>Internal Server Error</SAP:P2>
    <SAP:P3>Error during parsing of SOAP header</SAP:P3>
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>Http server code 500 reason Internal Server Error
    explanation Error during parsing of SOAP header</SAP:Stack>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    Any assistance would be much appreciated.

    Sravya,
    Yes this an IDOC to http scenario. There was no dump at the receiver end. I've found out what was causing the problem - I was using an adapter type of HTTP. It should have been of type 'XI'. I've altered this and it works. Hopefully this will resolve your problem Vinod.
    Richard

  • Steps involved in setting up communication between CRM and R3 / ECC

    Hi all,
    Can you please tell what are the steps involved in setting up communication between CRM and R3 or ECC.
    I know that initially logical systems, RFC connections and other technical settings need to be done by Basis consultants.
    From a functional consultants viewpoint, what all config settings need to be done so that data transfer between the systems can take place?
    Thanks in advance.

    Hi,
    There are a series of steps that are to be done...
    These include creating sites and subscription in CRM, setting up filters, and number ranges....
    All these are in the connectivity guide C71 and replication guide B09.
    Refer C71 first and then B09. These would suffice.
    You can get these both in the follwoing reference:
    http://help.sap.com/bp_crmv340/CRM_DE/index.htm
    If you dont get, then gimme your email id, i shall forward these docs to you.
    Kindly reward with points in case helpful
    Sharif.

  • Any SAP Note for RFC Error between BI and ECC 5.0

    Hi..
    the RFC Destination between BI and ECC 5.0 is giving errors.
    Plz let me know if there is any Support pack  or any solution to fix this error.
    thanks..

    Hi,
    pls find the RFC connection details
    1 Prerequisites
    1.1 User Roles
    Use
    With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
    Technical name Description File name for upload
    B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
    B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
    C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
    B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
    Procedure
    Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
    2 Local Settings
    This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
    2.1 SAP R/3
    2.1.1 Define Client Administration (SAP R/3)
    Use
    This activity allows you to change Customizing settings.
    Prerequisites
    You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
    Procedure
    Run the following activity:
    SAP R/3 Role Menu Define Client Administration (SAP R/3)
    Transaction Code SCC4
    SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    Then carry out the following steps:
    1. Choose Display  Change.
    2. Confirm the warning message Caution: The table is cross client.
    3. Select your SAP R/3 client and choose Details.
    4. In the Change View Clients: Details screen, activate the following settings:
    u2022 Automatic recording of changes
    u2022 Changes to Repository and cross-client Customizing allowed
    u2022 eCATT and CATT allowed.
    5. Save.
    6. Go back to the SAP Easy Access menu.
    2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
    Use
    The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
    1. Define the systems as logical systems.
    2. Assign the logical system for the SAP R/3 System to a client.
    This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
    Logical systems are defined cross-client.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
    Transaction Code SPRO
    SAP R/3
    IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
    2. Choose New entries.
    3. In the column Log System, enter a name for the logical system that you want to create.
    4. In the column Name, enter a description of the logical system.
    Log. System Name
    where XXX is the system name
    and NNN is the client.
    5. Save your entries.
    A transport request for Workbench appears.
    6. Select an existing request or create a new request, if necessary.
    A transport request for Customizing appears.
    7. Select an existing request or create a new request, if necessary.
    2.1.3 Assigning Logical System to Client
    Use
    The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Assign Logical System to Client
    Transaction Code SCC4
    SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    2. Choose Display ® Change.
    3. Confirm the warning message The table is cross client.
    4. Select your R/3 client and choose Details.
    5. Enter the name of the logical system of your SAP R/3 client.
    6. Save and confirm the warning message Be careful when changing the logical system.
    7. Choose Back twice.
    2.1.4 Creating an RFC User (SAP R/3)
    Use
    To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
    The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Creating an RFC User (SAP R/3)
    Transaction Code SU01
    SAP R/3 Menu Tools  Administration  User Maintenance  Users
    2. In the User field, enter RFCUSER.
    3. Choose Create.
    4. On the Maintain User screen, enter the following data on the Tab entry screens:
    Address
    Last Name
    Function
    Logon data
    User type System
    Password LOGIN
    Profile
    Profiles SAP_ALL
    SAP_NEW
    S_BI-WX_RFC
    Defaults
    Logon Language EN
    5. Save your entries.
    2.3 SAP BW
    2.3.1 Define Client Administration
    Use
    This activity defines changes and transports of the client-dependent and client-independent objects.
    Procedure
    1. To perform this activity, choose one of the following navigation options:
    SAP BW Role Menu Local Settings ® Define Client Administration
    Transaction Code SCC4
    SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    2. Switch to change mode.
    3. Select your client.
    4. Choose details.
    5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
    6. In field Client Role enter Customizing
    7. Check the settings for changes and transport of client-specific objects and client-independent object changes
    If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
    Result
    Client administration has been defined to support the installation using Best Practices.
    2.3.2 Defining a Logical System for SAP BW (SAP BW)
    Use
    In this step, you define the logical systems in your distributed system.
    Prerequisites
    Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
    Transaction Code SPRO
    IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
    1. A dialog box informs you that the table is cross-client. Choose Continue.
    2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
    3. On the New Entries: Overview of Added Entries screen enter the following data:
    Field name Description R/O/C User action and values Note
    Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
    Name Textual Description of the Logical System Enter a clear description for the logical BW system
    4. Choose Save.
    If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
    If you want to continue with the next activity, do not leave the transaction.
    Result
    You have created a Logical System Name for your SAP BW client.
    2.3.3 Assigning Logical System to Client (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW
    Role Menu Assigning Logical System to Client (SAP BW)
    Transaction Code SCC4
    SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    1. In the view Display View "Clients": Overview, choose Display.  Change
    2. Confirm the message.
    3. Select your BW client.
    4. Choose Details.
    5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
    6. Save the entries and go back.
    2.3.4 Opening Administrator Workbench
    Procedure
    To carry out the activity, choose one of the following navigation options
    SAP BW Modeling  Administrator Workbench: Modeling
    Transaction Code RSA1
    1. In the Replicate Metadata dialog box, choose Only Activate.
    2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
    2.3.5 Creating an RFC-User (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW Role Menu Creating RFC User
    Transaction Code SU01
    SAP BW Menu Tools  Administration  User Maintenance  Users
    Then carry out the following steps:
    1. On the User Maintenance: Initial Screen screen:
    a. Enter the following data:
    Field Entry
    User RFCUSER
    b. Choose Create.
    2. On the Maintain User screen:
    a. Choose the Address tab.
    b. Enter the following data:
    Field Entry
    Last Name RFCUSER
    Function Default-User for RFC connection
    c. Choose the Logon data tab.
    d. Enter the following data:
    Field Entry
    Password LOGIN
    User type System
    e. Choose the Profiles tab.
    f. Enter the following data:
    Field Entry
    Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
    g. Choose Save.
    Do not change the password of this user as it is used in RFC connections.
    2.3.6 Define RFC-USER as default (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options
    SAP BW Role Menu Define RFC-USER as default (SAP BW)
    Transaction Code RSA1
    SAP BW Menu Modeling  Administrator Workbench: Modeling
    1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
    2. In the Global Settings/Customizing dialog box choose Glob. Settings.
    3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
    a. Choose Display  Change.
    b. Enter RFCUSER in the BW User ALE field.
    c. Choose Save.
    Hope this helps in solving u r problem
    Regards
    Ramakrishna Kamurthy

  • Short dump Error during VM container communication between ABAP and JAVA.

    Hello All,
    Can anybody please help with resolving the following issue:
    Short dump is displayed, when I try to insert CRM product (type: material) in the document (opportunity). This CRM product was created in CRM directly.
    When I try to insert ECC migrated material, everything works fine.
    Here is the details of dump:
    Short text
        Error during VM container communication between ABAP and JAVA
    Information on where terminated
        Termination occurred in the ABAP program "SAPLPRC_INT" - in "GET_PRICING_PROCEDURE_INFO".
        The main program was "SAPMHTTP ". In the source code you have the termination point in line 100 of the (Include) program "LPRC_INTF35".
    Thank you!

    hi Willie,
         this is the dump, and i have used the t-code sm52 . the VMC is not active.
    |Short Text                                                                                        |
    |    Error during VM Container communication between ABAP and JAVA.                                |
    |What happened?                                                                                    |
    |    The current program had to be terminated because of an                                        |
    |    error when installing the R/3 System.                                                         |
    |    Error in the RFC layer.                                                                       |
    |What can you do?                                                                                  |
    |    Note which actions and entries caused the error to occur.                                     |
    |                                                                                                  |
    |    Consult your SAP administrator.                                                               |
    |                                                                                                  |
    |    Using transaction ST22 for ABAP dump analysis, you can view, manage,                          |
    |    and retain termination messages for longer periods.                                           |
    |Error analysis                                                                                    |
    |    An error has occurred in the RFC layer during communication between                           |
    |    JAVA and the ABAP stack. This prevents data from being passed correctly                       |
    |    between the two stacks.                                                                       |
    |                                                                                                  |
    |    Message    = TH_VMC_SERV_NOT_ACTIVE                                                           |
    |    Return code = -1007                                                                           |
    |    Pointer    = "000007DD348F6138"                                                               |
    |How to correct the error                                                                          |
    |    Check whether the VMC is active on your application server. To do this,                       |
    |    run transaction SM52. If the VMC is not active, contact your SAP                              |
    |    administrator.                                                                                |
    Regards
    Charles

  • Communication between SAP and 3rd Party Systems using IDOC HTTP XML Interfa

    Hi
    i am try do
    Communication between SAP and 3rd Party Systems using IDOC HTTP XML Interface
    With The help of SDN Contribution
    link----
    ( have look on it)
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4943f2b7-0a01-0010-37af-faff35b2f08c
    I am getting error in
    Partner system as HTTPLOG and "Execute" to check the results
    Error is --  Port could not be created
    RFC destination HTTPLOG Not specified for system HTTPLOG
    any 1 have any idea  if plzzzzzzzz...........
    Thank u
    Ram

    Hello .
      we are also in  process of implementing the same
    could you share the knowledge pl?
    1)is it a separate add on with ALE to saphr
       or using ECC ??
    2)can u share the configuration part ??
    we are trying it on webas as addon 3.0 .

  • Issue in CIF data between ECC to APO

    Hi Experts,
    We have ECC and APO system in our landscape. we have configured CIF and transferred data between ECC and APO however after ECC system refresh CIF configuration is not working. we verified and reconfigured the CIF configuration but still no luck.
    strange thing is, while sending the data for e.g vendor from ECC to APO, there is no error reported. It displays successful in both qRFC trace files but the transferred data is nt reflecting in APO system.
    There is no system run time error, no errors in system log (SM21), no logs in SLG1 application log, no erros in qRFC trace files.
    we have enabled RFC user trace but can't conclude the issue. could you please anyone let me know where we can check the error log or how to resolve this?
    Outbund Queue logs from ECC:
    QTYPE :OUTBOUND/S                                     
    DATE       TIME     CLIENT     USER            QDATE      QTIME    BJOB       QEVENT        
            TID                              ORGTID                        QSTATE               
        DEST                                    ERRMESS                                         
    20.03.2015 17:44:56 300             20.03.2015 17:44:56 N          N             
            0A1A01720F70550C0F4019E7                                       SENDING
        <SID>CLNT300                                                                              
    LUWCNT   QNAME                    FNAM                          
    00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND       
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                                          QTYPE :OUTBOUND/S                                     
    DATE       TIME     EXETIME  CLIENT  USER            QDATE      QTIME    BJOB    QEVENT     
            TID                              ORGTID                        QSTATE               
        DEST                                    ERRMESS                                         
    20.03.2015 17:44:57 00:00:01 300          20.03.2015 17:44:56 N       N          
            0A1A01720F70550C0F4019E7                                       CONFIRMD
        <SID>CLNT300                                                                              
    LUWCNT   QNAME                    FNAM                          
    00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND       
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                                          QTYPE :OUTBOUND/S                                     
    DATE       TIME     CLIENT     USER            QDATE      QTIME    BJOB       QEVENT        
            TID                              ORGTID                        QSTATE               
        DEST                                    ERRMESS                                         
    20.03.2015 17:44:57 300             20.03.2015 17:44:56 N          N             
            0A1A01720F70550C0F4019E8                                       SENDING
        <SID>CLNT300                                                                              
    LUWCNT   QNAME                    FNAM                          
    00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT         
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                                          QTYPE :OUTBOUND/S                                     
    DATE       TIME     EXETIME  CLIENT  USER            QDATE      QTIME    BJOB    QEVENT     
            TID                              ORGTID                        QSTATE               
        DEST                                    ERRMESS                                         
    20.03.2015 17:44:57 00:00:00 300          20.03.2015 17:44:56 N       N          
            0A1A01720F70550C0F4019E8                                       CONFIRMD
        <SID>CLNT300                                                                              
    LUWCNT   QNAME                    FNAM                          
    00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT         
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Inbound Queue trace log from APO:
    QTYPE :INBOUND                                       
    DATE       TIME     CLIENT     USER            QDATE      QTIME    BJOB       QEVENT        
            TID                              ORGTID                        QSTATE               
        DEST                                    ERRMESS                                         
    20.03.2015 17:39:48 300                20.03.2015 17:44:56 N          N             
            0A1A01720F70550C0F4019E7                                       SENDED 
        <SID>CLNT300                                                                              
    LUWCNT   QNAME                    FNAM                          
    00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND       
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                                           QTYPE :INBOUND                                       
    DATE       TIME     EXETIME  CLIENT  USER            QDATE      QTIME    BJOB    QEVENT     
            TID                              ORGTID                        QSTATE               
        DEST                                    ERRMESS                                         
    20.03.2015 17:39:48 17:39:48 300             20.03.2015 17:44:56 N       N          
            0A1A01720F70550C0F4019E7                                       FINISH 
        <SID>CLNT300                                                                              
    LUWCNT   QNAME                    FNAM                          
    00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND       
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                                           QTYPE :INBOUND                                       
    DATE       TIME     CLIENT     USER            QDATE      QTIME    BJOB       QEVENT        
            TID                              ORGTID                        QSTATE               
        DEST                                    ERRMESS                                         
    20.03.2015 17:39:48 300                20.03.2015 17:44:56 N          N             
            0A1A01720F70550C0F4019E8                                       SENDED 
        <SID>CLNT300                                                                              
    LUWCNT   QNAME                    FNAM                          
    00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT         
                                           QTYPE :INBOUND                                       
    DATE       TIME     EXETIME  CLIENT  USER            QDATE      QTIME    BJOB    QEVENT     
            TID                              ORGTID                        QSTATE               
        DEST                                    ERRMESS                                         
    20.03.2015 17:39:48 17:39:48 300             20.03.2015 17:44:56 N       N          
            0A1A01720F70550C0F4019E8                                       FINISH 
        <SID>CLNT300                                                                              
    LUWCNT   QNAME                    FNAM                          
    00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT         
                                           QTYPE :INBOUND                                       
    DATE       TIME     EXETIME  CLIENT  USER            QDATE      QTIME    BJOB    QEVENT     
            TID                              ORGTID                        QSTATE               
        DEST                                    ERRMESS                                         
    20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N          
            0A1A019D23F8550C0E0C2559         0A1A01720F70550C0F4019E7      RUNNING
        <SID>CLNT300                                                                              
    LUWCNT   QNAME                    FNAM                          
    00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND       
                                           QTYPE :INBOUND                                       
    DATE       TIME     EXETIME  CLIENT  USER            QDATE      QTIME    BJOB    QEVENT     
            TID                              ORGTID                        QSTATE               
        DEST                                    ERRMESS                                         
    20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N          
            0A1A019D23F8550C0E0C2559         0A1A01720F70550C0F4019E7      FINISH 
        <SID>CLNT300                                                                              
    LUWCNT   QNAME                    FNAM                          
    00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND       
                                           QTYPE :INBOUND                                       
    DATE       TIME     EXETIME  CLIENT  USER            QDATE      QTIME    BJOB    QEVENT     
            TID                              ORGTID                        QSTATE               
        DEST                                    ERRMESS                                         
    20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N          
            0A1A019D23F8550C0E0C2559         0A1A01720F70550C0F4019E7      CONFIRMD
        <SID>CLNT300                                                                              
    LUWCNT   QNAME                    FNAM                          
    00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND       
                                           QTYPE :INBOUND                                       
    DATE       TIME     EXETIME  CLIENT  USER            QDATE      QTIME    BJOB    QEVENT     
            TID                              ORGTID                        QSTATE               
        DEST                                    ERRMESS                                         
    20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N          
            0A1A019D23F8550C0E0C255A         0A1A01720F70550C0F4019E8      RUNNING
        <SID>CLNT300                                                                              
    LUWCNT   QNAME                    FNAM                          
    00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT         
                                           QTYPE :INBOUND                                       
    DATE       TIME     EXETIME  CLIENT  USER            QDATE      QTIME    BJOB    QEVENT     
            TID                              ORGTID                        QSTATE               
        DEST                                    ERRMESS                                         
    20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N          
            0A1A019D23F8550C0E0C255A         0A1A01720F70550C0F4019E8      FINISH 
        <SID>CLNT300                                                                              
    LUWCNT   QNAME                    FNAM                          
    00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT         
                                           QTYPE :INBOUND                                       
    DATE       TIME     EXETIME  CLIENT  USER            QDATE      QTIME    BJOB    QEVENT     
            TID                              ORGTID                        QSTATE               
        DEST                                    ERRMESS                                         
    20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N          
            0A1A019D23F8550C0E0C255A         0A1A01720F70550C0F4019E8      CONFIRMD
        <SID>CLNT300                                                                              
    LUWCNT   QNAME                    FNAM                          
    00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT         
    Thanks and regards,
    Pradeep

    Hello Pardeep,
    Please check the setting of SMQS and SMQR for CF and client registration
    these entries, the field 'TYPE' is set to 'R'.
    QIN scheduler may be available for every client if you are working in this client with registered inbound queues.
    Choose Edit->Activate scheduler from the menu (available in both SMQR and SMQS)
    During processing in dialog work processes, the system uses a parallel RFC to restart the registered inbound queues. For this, you can use transaction RZ12 to specify a group of application servers and dialog work processes that are allowed to use a QIN scheduler. You must use transaction SMQR to assign the group name to the relevant QIN scheduler.
    Different parameters in SMQR are explained in note 1579728. The explanation for SMQS is similar
    Also try the report RSQIWKEX
    Best Regards,
    R.Brahmankar

  • Communication between CRM and ERP for E-commerce scenario

    Question more on lines of system architecture design.
    We are planning to implement CRM E-commerce and wanted to find out more detail about the communication between CRM and ERP systems. Do they need to communicate in real time for this application, or is it mainly initial and delta loads? Is the amount of data exchanged huge ( necessitating both systems to be on the same network, or can they be on separate geographical locations )?
    We also understand that E-commerce can also be done only using ERP. How does that differ from the CRM version?

    Hey Sanket,
    Q 1 . Do CRM and ECC need to communicate in real time for Ecommerce application, or is it mainly initial and delta loads
    Ans. CRM and ECC communicate using RFC connections which further uses TCP/IP as the protocol.The communication can be both  real time { delta loads} or offline {initial download}.
    Q2 .Is the amount of data exchanged huge ( necessitating both systems to be on the same network, or can they be on separate geographical locations )?
    Ans. The amount of data can be huge hence its preferable that both systems to be on the same network.
    Q 3. We also understand that E-commerce can also be done only using ERP. How does that differ from the CRM version
    Ans.Theres no difference functionally  but technically the application connects to the ECC system using JCO to execute all the RFC enabled function modules.
    Warm Regards,
    Sumit

  • Error during VM container communication between ABAP and JAVA

    Hello,
    While creation of SC, I am getting error "Error during VM container communication between ABAP and JAVA"
    Based on earlier responses in this forum, I checked following activity.
    1. T Code - BBP_CND_CHECK_CUST
    Result - IPC Pricing is Active and IPC is now running in VMC
    2. Run Report - RSVMCRT_HEALTH_CHECK
    Result - The Java component is deactivated
    3. As per OSS note 854170, Profile parameters were existed as below
    a) vmcj/enable - on
    b) vmcj/option/maxJavaHeap = 200M
    So, How to get Java component activated?
    Thanks,
    Rahul Mandale

    Thanks Markus,
    For SM53, I am getting resulets as " Java is not active on this application server - Message no. SVMCRT011"
    Can you suggest, what I need to do for it? I can't use SRM Shopping cart because of it. thanks in advance, Rahul
    and dev_w0 trace ....
    trc file: "dev_w0", trc level: 1, release: "700"
    ACTIVE TRACE LEVEL           1
    ACTIVE TRACE COMPONENTS      all, MJ

    B Wed Aug 31 15:45:40 2011
    B  create_con (con_name=R/3)
    B  Loading DB library 'D:\usr\sap\CUS\DVEBMGS04\exe\dboraslib.dll' ...
    B  Library 'D:\usr\sap\CUS\DVEBMGS04\exe\dboraslib.dll' loaded
    B  Version of 'D:\usr\sap\CUS\DVEBMGS04\exe\dboraslib.dll' is "700.08", patchlevel (0.46)
    B  New connection 0 created
    M sysno      04
    M sid        CUS
    M systemid   560 (PC with Windows NT)
    M relno      7000
    M patchlevel 0
    M patchno    52
    M intno      20050900
    M make:      multithreaded, Unicode, optimized
    M pid        456
    M
    M  kernel runs with dp version 210000(ext=109000) (@(#) DPLIB-INT-VERSION-210000-UC)
    M  length of sys_adm_ext is 572 bytes
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 456) [dpxxdisp.c   1293]
    I  MtxInit: 30000 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
    M  DpShMCreate: sizeof(wp_adm)          18304     (1408)
    M  DpShMCreate: sizeof(tm_adm)          3954072     (19672)
    M  DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
    M  DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
    M  DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
    M  DpShMCreate: sizeof(comm_adm)          528064     (1048)
    M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    M  DpShMCreate: sizeof(file_adm)          0     (72)
    M  DpShMCreate: sizeof(vmc_adm)          0     (1452)
    M  DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
    M  DpShMCreate: sizeof(gw_adm)     48
    M  DpShMCreate: SHM_DP_ADM_KEY          (addr: 05C00040, size: 4613144)
    M  DpShMCreate: allocated sys_adm at 05C00040
    M  DpShMCreate: allocated wp_adm at 05C01E28
    M  DpShMCreate: allocated tm_adm_list at 05C065A8
    M  DpShMCreate: allocated tm_adm at 05C065D8
    M  DpShMCreate: allocated wp_ca_adm at 05FCBB70
    M  DpShMCreate: allocated appc_ca_adm at 05FD1930
    M  DpShMCreate: allocated comm_adm at 05FD3870
    M  DpShMCreate: system runs without file table
    M  DpShMCreate: allocated vmc_adm_list at 06054730
    M  DpShMCreate: allocated gw_adm at 06054770
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated ca_info at 060547A0
    M  DpShMCreate: allocated wall_adm at 060547A8
    X  EmInit: MmSetImplementation( 2 ).
    X  MM diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  Using implementation flat
    M  <EsNT> Memory Reset disabled as NT default
    X  ES initialized.

    M Wed Aug 31 15:45:41 2011
    M  ThInit: running on host crmsys

    M Wed Aug 31 15:45:42 2011
    M  calling db_connect ...
    C  Prepending D:\usr\sap\CUS\DVEBMGS04\exe to Path.

    C Wed Aug 31 15:45:47 2011
    C  Client NLS settings: AMERICAN_AMERICA.UTF8
    C  Logon as OPS$-user to get SAPSR3's password
    C  Connecting as /@CRM on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
    C  Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
    C    0 UTF8                                                      1   0619F158   061A46F4   061A3F7C
    C  Attaching to DB Server CRM (con_hdl=0,svchp=061A3EC8,svrhp=061B5794)
    C  Starting user session (con_hdl=0,svchp=061A3EC8,srvhp=061B5794,usrhp=061CA558)

    C Wed Aug 31 15:45:48 2011
    C  Now '/@CRM' is connected (con_hdl 0, nls_hdl 0).
    C  Got SAPSR3's password from OPS$-user
    C  Disconnecting from connection 0 ...
    C  Closing user session (con_hdl=0,svchp=061A3EC8,usrhp=061CA558)
    C  Now I'm disconnected from ORACLE
    C  Connecting as SAPSR3/<pwd>@CRM on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
    C  Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
    C    0 UTF8                                                      1   0619F158   061A46F4   061A3F7C
    C  Starting user session (con_hdl=0,svchp=061A3EC8,srvhp=061B5794,usrhp=061CA558)
    C  Now 'SAPSR3/<pwd>@CRM' is connected (con_hdl 0, nls_hdl 0).
    C  Database NLS settings: AMERICAN_AMERICA.UTF8
    C  Database instance CRM is running on CRMSYS with ORACLE version 10.2.0.1.0 since 20110831

    B Wed Aug 31 15:45:49 2011
    B  Connection 0 opened (DBSL handle 0)
    B  Wp  Hdl ConName          ConId     ConState     TX  PRM RCT TIM MAX OPT Date     Time   DBHost         
    B  000 000 R/3              000000000 ACTIVE       NO  YES NO  000 255 255 20110831 154542 CRMSYS         
    M  db_connect o.k.
    M  ICT: exclude compression: .zip,.cs,.rar,.arj,.z,.gz,.tar,.lzh,.cab,.hqx,.ace,.jar,.ear,.war,.css,.pdf,.js,.gzip,.uue,.bz2,.iso,.sda,.sar,.gif

    I Wed Aug 31 15:46:12 2011
    I  MtxInit: 0 0 0
    M  SHM_PRES_BUF               (addr: 0A7C0040, size: 4400000)
    M  SHM_ROLL_AREA          (addr: 788A0040, size: 61440000)
    M  SHM_PAGING_AREA          (addr: 0AC00040, size: 32768000)
    M  SHM_ROLL_ADM               (addr: 0CB50040, size: 615040)
    M  SHM_PAGING_ADM          (addr: 0CBF0040, size: 525344)
    M  ThCreateNoBuffer          allocated 544152 bytes for 1000 entries at 0CC80040
    M  ThCreateNoBuffer          index size: 3000 elems
    M  ThCreateVBAdm          allocated 12160 bytes (50 server) at 0CD10040
    X  EmInit: MmSetImplementation( 2 ).
    X  MM diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  Using implementation flat
    X  ES initialized.
    B  db_con_shm_ini:  WP_ID = 0, WP_CNT = 13, CON_ID = -1
    B  dbtbxbuf: Buffer TABL  (addr: 10E700C8, size: 30000000, end: 12B0C448)
    B  dbtbxbuf: Buffer TABLP (addr: 12B100C8, size: 10240000, end: 134D40C8)
    B  dbexpbuf: Buffer EIBUF (addr: 0FBA00D0, size: 4194304, end: 0FFA00D0)
    B  dbexpbuf: Buffer ESM   (addr: 134E00D0, size: 4194304, end: 138E00D0)
    B  dbexpbuf: Buffer CUA   (addr: 138F00D0, size: 3072000, end: 13BDE0D0)
    B  dbexpbuf: Buffer OTR   (addr: 13BE00D0, size: 4194304, end: 13FE00D0)
    M  rdisp/reinitialize_code_page -> 0
    M  icm/accept_remote_trace_level -> 0
    M  rdisp/no_hooks_for_sqlbreak -> 0
    M  CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

    S Wed Aug 31 15:46:15 2011
    S  *** init spool environment
    S  initialize debug system
    T  Stack direction is downwards.
    T  debug control: prepare exclude for printer trace
    T  new memory block 1946AA80

    S Wed Aug 31 15:46:16 2011
    S  spool kernel/ddic check: Ok
    S  using table TSP02FX for frontend printing
    S  1 spool work process(es) found
    S  frontend print via spool service enabled
    S  printer list size is 150
    S  printer type list size is 50
    S  queue size (profile)   = 300
    S  hostspool list size = 3000
    S  option list size is 30
    S      found processing queue enabled
    S  found spool memory service RSPO-RCLOCKS at 1D6D00A8
    S  doing lock recovery
    S  setting server cache root
    S  found spool memory service RSPO-SERVERCACHE at 1D6D0430
    S    using messages for server info
    S  size of spec char cache entry: 297028 bytes (timeout 100 sec)
    S  size of open spool request entry: 2132 bytes
    S  immediate print option for implicitely closed spool requests is disabled

    A Wed Aug 31 15:46:18 2011

    A  -PXA--
    A  PXA INITIALIZATION
    A  PXA: Fragment Size too small: 73 MB, reducing # of fragments
    A  System page size: 4kb, total admin_size: 5132kb, dir_size: 5076kb.
    A  Attached to PXA (address 688A0040, size 150000K)
    A  abap/pxa = shared protect gen_remote
    A  PXA INITIALIZATION FINISHED
    A  -PXA--


    A Wed Aug 31 15:46:20 2011
    A  ABAP ShmAdm attached (addr=57A40000 leng=20955136 end=58E3C000)
    A  >> Shm MMADM area (addr=57EB5E58 leng=126176 end=57ED4B38)
    A  >> Shm MMDAT area (addr=57ED5000 leng=16150528 end=58E3C000)
    A  RFC Destination> destination crmsys_CUS_04 host crmsys system CUS systnr 4 (crmsys_CUS_04)

    A Wed Aug 31 15:46:21 2011
    A  RFC Options> H=crmsys,S=04,d=2,
    A  RFC FRFC> fallback activ but this is not a central instance.
    A   
    A  RFC rfc/signon_error_log = -1
    A  RFC rfc/dump_connection_info = 0
    A  RFC rfc/dump_client_info = 0
    A  RFC rfc/cp_convert/ignore_error = 1
    A  RFC rfc/cp_convert/conversion_char = 23
    A  RFC rfc/wan_compress/threshold = 251
    A  RFC rfc/recorder_pcs not set, use defaule value: 2
    A  RFC rfc/delta_trc_level not set, use default value: 0
    A  RFC rfc/no_uuid_check not set, use default value: 0
    A  RFC rfc/bc_ignore_thcmaccp_retcode not set, use default value: 0
    A  RFC Method> initialize RemObjDriver for ABAP Objects
    M  ThrCreateShObjects          allocated 13730 bytes at 0FFB0040

    N Wed Aug 31 15:46:22 2011
    N  SsfSapSecin: putenv(SECUDIR=D:\usr\sap\CUS\DVEBMGS04\sec): ok

    N  =================================================
    N  === SSF INITIALIZATION:
    N  ===...SSF Security Toolkit name SAPSECULIB .
    N  ===...SSF trace level is 0 .
    N  ===...SSF library is D:\usr\sap\CUS\DVEBMGS04\exe\sapsecu.dll .
    N  ===...SSF hash algorithm is SHA1 .
    N  ===...SSF symmetric encryption algorithm is DES-CBC .
    N  ===...sucessfully completed.
    N  =================================================

    N Wed Aug 31 15:46:23 2011
    N  MskiInitLogonTicketCacheHandle: Logon Ticket cache pointer retrieved from shared memory.
    N  MskiInitLogonTicketCacheHandle: Workprocess runs with Logon Ticket cache.
    M  JrfcVmcRegisterNativesDriver o.k.
    W  =================================================
    W  === ipl_Init() called
    B    dbtran INFO (init_connection '<DEFAULT>' [ORACLE:700.08]):
    B     max_blocking_factor =  15,  max_in_blocking_factor      =   5,
    B     min_blocking_factor =  10,  min_in_blocking_factor      =   5,
    B     prefer_union_all    =   0,  prefer_join                 =   0,
    B     prefer_fix_blocking =   0,  prefer_in_itab_opt          =   1,
    B     convert AVG         =   0,  alias table FUPD            =   0,
    B     escape_as_literal   =   1,  opt GE LE to BETWEEN        =   0,
    B     select *            =0x0f,  character encoding          = STD / <none>:-,
    B     use_hints           = abap->1, dbif->0x1, upto->2147483647, rule_in->0,
    B                           rule_fae->0, concat_fae->0, concat_fae_or->0

    W Wed Aug 31 15:46:24 2011
    W    ITS Plugin: Path dw_gui
    W    ITS Plugin: Description ITS Plugin - ITS rendering DLL
    W    ITS Plugin: sizeof(SAP_UC) 2
    W    ITS Plugin: Release: 700, [7000.0.52.20050900]
    W    ITS Plugin: Int.version, [32]
    W    ITS Plugin: Feature set: [10]
    W    ===... Calling itsp_Init in external dll ===>
    W  === ipl_Init() returns 0, ITSPE_OK: OK
    W  =================================================
    E  Enqueue Info: rdisp/wp_no_enq=1, rdisp/enqname=<empty>, assume crmsys_CUS_04
    E  Replication is disabled
    E  EnqCcInitialize: local lock table initialization o.k.
    E  EnqId_SuppressIpc: local EnqId initialization o.k.
    E  EnqCcInitialize: local enqueue client init o.k.

    B Wed Aug 31 15:46:48 2011
    B  table logging switched off for all clients

    M Wed Aug 31 15:47:55 2011
    M  SecAudit(RsauShmInit): WP attached to existing shared memory.
    M  SecAudit(RsauShmInit): addr of SCSA........... = 05BD0040
    M  SecAudit(RsauShmInit): addr of RSAUSHM........ = 05BD07A8
    M  SecAudit(RsauShmInit): addr of RSAUSLOTINFO... = 05BD07E0
    M  SecAudit(RsauShmInit): addr of RSAUSLOTS...... = 05BD07EC

    A Wed Aug 31 15:48:44 2011
    A  RFC FRFC> fallback on the central gateway crmsys sapgw04 activ

    B Wed Aug 31 15:49:47 2011
    B  dbmyclu : info : my major identification is 3232288873, minor one 4.
    B  dbmyclu : info : Time Reference is 1.12.2001 00:00:00h GMT.
    B  dbmyclu : info : my initial uuid is D98FA690E8AA314D9B69930868792664.
    B  dbmyclu : info : current optimistic cluster level: 0
    B  dbmyclu : info : pessimistic reads set to 2.

  • Data Inconsistency for 0EMPLOYEE between ECC and BI

    Hi,
    We do a full load to 0EMPLOYEE using 0EMPLOYEE_ATTR from ECC. There were records deleted for lot of employees (some action types) in ECC. This has caused data inconsistency for 0EMPLOYEE master data (time-dependent) between ECC and BI. In BI we have more records for these employees (Additional records have time-dependent range that were deleted from ECC but still exist in BI). These employee records are already being used in lot of InfoProviders. Is there an efficient way to fix this issue? One of the solution is to delete data from all InfoProviders and then delete from Master data for 0EMPLOYEE, but the deletion of employee records can happen quite often, so we don't want to take this route. Also, I tried to re-organize master data attributes for 0EMPLOYEE through process chain, but that didn't work either.
    Message was edited by:
            Ripel Desai

    Hi Ripel,
    I share your pain. This is one of the real pains of Time-Dependant master data in BW. I have been in your exact position and the only way round the issue for me was to clear out all the cubes that used 0EMPLOYEE and then delete and re-load 0EMPLOYEE data.
    I know this responce doesn't help you but at least you are not alone.
    Regards,
    Pete
    http://www.teklink.co.uk

  • Internal error in communication between configuration and sales document

    Hi,
    While i am doing VA32 i got this message  plz advise me..
    Internal error in communication between configuration and sales document
    in the form GET_CONFIG_MODE
    bit urgent  issue..
    Regards,
    San Rao.

    Hi
    Pls check the OSS note 836097, which can solve your problem.
    In my experience, I can tell you something
    When configuration is done, the configuration object is stored in VBAP-CUOBJ for the item. For this CUOBJ, you can find the configuration in the tcode CUTABLEINFO or in tables IBIB, IBIN, IBEXTINST, IBINOBS,IBINOWN,IBST,IBSTREF,IBINVALUES.
    If for the order if VBAP-CUOBJ is not available, then it will not be able to get the configuration. The error message in this case is V1 854 of message class V1.
    You can search for some other OSS notes also using this error message and the form name.
    Also refer to 173726, 174333,175372 and 173664

  • Is in PI7.1 possible asynchronous communication between SOAP and ABAPProxy?

    Hi,
    when method execute_asynchronous has disapeared since XI/PI 7.1, is
    there still way how to use ABAP proxy in asynchronous way?
    We need to build asynchronous connection SOAP->PI->ABAP_Proxy.
    In PI, both interfaces are defined as asynchronous (outbound for SOAP and
    inbound for ABAP Proxy).
    Despite of this fact, when message is sent, it is processed
    synchronous way.
    I have set breakpoint in my implementation of method for ABAP Proxy
    message processing. When message is sent and breakpoint is reached,
    whole connection stays open (between SOAP and PI and between PI and
    ABAP Proxy) and waits for processing method (the breakpointed one) to
    return. Only when processing method returns, is connection finelly
    closed.
    If i understand it correctly, this is synchronous behavior. In
    asynchronous behavior, as i understand it, should be connection
    between PI and ABAP Proxy of application server closed immediately
    after message has been delivered. This mean before my processing
    method is even called.
    The same could be said about SOAP and PI communication. Connection
    should be closed immediately after PI has received message. From
    definition of asynchronous communication of PI is obvious, that PI
    should receive message correctly and close connection to sender system
    even when receiver is unreachable. It should deliver message later
    when, receiver system is back on line. So why it keeps connection to
    sender system open while it waits for receiver?
    Why is this happening, when both interfaces are defined as
    asynchronous? Could be the reason for this, if APPLICATION
    ACKNOWLEDGEMENT is set on by default? If so, how can i change it
    to SYSTEM ACKNOWLEDGEMENT, or disable it at all?
    Or is this kind of asynchronous communication even possible since
    XI/PI 7.1 ?
    Processing of message we are sending can take some time, so we dont
    want connection pending open while waiting for finish of
    processing. Thats the reason why we have chose asynchronous model to
    use.

    Quote from How to Use the J2EE SOAP Adapter:
    "If you select Best Effort, the Web service client will receive a response
    message in the SOAP body. Otherwise, the Web service client will not receive a
    response message if no error occurs."
    "if no error occurs" - that is the problem. In either case he still
    waits if some error occure or not. I dont want it. Once PI has
    received message, I want the connection with sender to be closed. If
    there will be error in communication between PI and reciever, I want
    to see it only in PI log. That mean no notification to sender to be
    send about that error.
    Is that possible?

Maybe you are looking for