Incomplete Idoc received in SAP R/3

Hi XI Gurus
I am working on a File to Idoc scenario and stuck because of a strange issue.
The output Idoc structure sent from XI and as viewed in IDX5 / SXMB_MONI is as below
<?xml version="1.0" encoding="UTF-8"?>
<ACC_DOCUMENT01>
     <IDOC BEGIN="1">
          <EDI_DC40 SEGMENT="1">
               <SNDPRT>LI_SND</SNDPRT>
               <SNDPFC>LF_SND</SNDPFC>
               <SNDPRN>0000000100</SNDPRN>
          </EDI_DC40>
          <E1BPACHE09 SEGMENT="1">
               <OBJ_TYPE>BKPFF</OBJ_TYPE>
               <OBJ_KEY>PR2000627830002007</OBJ_KEY>
               <OBJ_SYS>T47CLNT800</OBJ_SYS>
               <BUS_ACT>RFBU</BUS_ACT>
               <USERNAME>lovein</USERNAME>
               <COMP_CODE>3000</COMP_CODE>
               <DOC_DATE>2007-09-11T05:18:52-07:00</DOC_DATE>
               <PSTNG_DATE>2007-09-11T05:18:52-07:00</PSTNG_DATE>
               <DOC_TYPE>SA</DOC_TYPE>
          </E1BPACHE09>
          <E1BPACCAHD/>
          <E1BPACGL09>
               <ITEMNO_ACC>1</ITEMNO_ACC>
               <GL_ACCOUNT/>
               <ACCT_TYPE>S</ACCT_TYPE>
               <DOC_TYPE>SA</DOC_TYPE>
               <COMP_CODE>3000</COMP_CODE>
               <PSTNG_DATE>2007-09-11T05:18:52-07:00</PSTNG_DATE>
               <VENDOR_NO/>
          </E1BPACGL09>
          <E1BPACAP09>
               <ITEMNO_ACC>00001</ITEMNO_ACC>
               <VENDOR_NO/>
               <COMP_CODE>3000</COMP_CODE>
               <PYMT_METH>ach</PYMT_METH>
          </E1BPACAP09>
          <E1BPACCR09>
               <ITEMNO_ACC>1</ITEMNO_ACC>
               <CURR_TYPE>00</CURR_TYPE>
               <CURRENCY>USD</CURRENCY>
               <CURRENCY_ISO>USD</CURRENCY_ISO>
               <AMT_DOCCUR>-30000</AMT_DOCCUR>
          </E1BPACCR09>
          <E1BPACCR09>
               <ITEMNO_ACC>Constant</ITEMNO_ACC>
               <CURR_TYPE>00</CURR_TYPE>
               <CURRENCY>USD</CURRENCY>
               <CURRENCY_ISO>USD</CURRENCY_ISO>
               <AMT_DOCCUR>0</AMT_DOCCUR>
          </E1BPACCR09>
          <E1BPACCR09>
               <ITEMNO_ACC>Constant</ITEMNO_ACC>
               <CURR_TYPE>00</CURR_TYPE>
               <CURRENCY>USD</CURRENCY>
               <CURRENCY_ISO>USD</CURRENCY_ISO>
               <AMT_DOCCUR>30000.00</AMT_DOCCUR>
          </E1BPACCR09>
     </IDOC>
</ACC_DOCUMENT01>
But the Idoc received in SAP R/3 as viewed in Transaction WE02 or table EDID4 has only one node E1BPACHE09
and because rest of the nodes are missing SAP R/3 fails to process the Idoc .
Any help to analyse the issue will be highly appreciated.
Thanx
Lovein

Hi Lovein,
What you can do is:
1. Go to SXMB_MONI and take the output xml.
2. Now go to your mapping under TEST tab and test the above mentioned output xml and see what is the output, i mean are you able to see all the desired output as per you mapping or not.
3. If not then probabily you will get an error message, then try to find out the solution in your mapping only.
4. If you are not able to do that, kindly send the error message, which you got in mapping.
I hope this will solve your issue.
Regards,
Sarvesh
****Reward points, if found helpful. 

Similar Messages

  • Receiving IDocs from non-SAP system ...

    Hello guys,
    I have problem with implementing IDoc-XI-IDoc scenario. The sender system is a subsystem (non-SAP system) sending IDocs but XI is not able to receive them. I thing the IDoc metadata can not be found.
    Logical system name of the sender is IF6020DEV. I registered the system in SLD. In Integration Directory I imported the Bussines System IF6020DEV to my scenario and I created communication channel of type Sender IDoc Adapter in it.
    In IDX2 I created new port called IF6020DEV and I copied needed metadata into the port. But it doesn't work. Probably I don't do it right because I'm beginner with SAP XI.
    Could you give me any advice how to configure XI for receiving IDocs from non-SAP system?
    Thank you in advance!
    Regards
    Zbynek

    Thank you very much. The issue described in refered discussion is almost same issue what I'm solving. Unfortunetally the described solution dosn't work for me.
    The sender system still returns following error. I know you probably won't understand it because you don't know the subsystem, but maybe you could get some idea what is wrong.
    05/29/09 16:09:19.482 idoup2 Logon...
    05/29/09 16:09:19.482 idoup2 RfcOpenEx (TRACE=1 CLIENT=110 USER=xxxxxx LANG=D LCHECK=1 GWHOST=xxxxxx GWSERV=3361 ASHOST=xxxxxxx SYSNR=61 PASSWD=<password>)
    05/29/09 16:09:19.529 idoup2 Logon RfcOpenEx result=1
    05/29/09 16:09:19.607 idoup2 Call to (IDOC_INBOUND_ASYNCHRONOUS) failed (3)
    05/29/09 16:09:19.607 idoup2 Handle=1
    05/29/09 16:09:19.607 idoup2 key............:
    05/29/09 16:09:19.607 idoup2 status.........:
    05/29/09 16:09:19.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
    05/29/09 16:09:19.607 idoup2 internal status:
    05/29/09 16:09:19.607 idoup2 idoc_upload failed with rc=(3), try(2)
    05/29/09 16:09:20.607 idoup2 key............:IDoc-Adapter Eingang: Der Absend
    05/29/09 16:09:20.607 idoup2 status.........:EXCEPTION SYSTEM_FAILURE RAISED
    05/29/09 16:09:20.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
    05/29/09 16:09:20.607 idoup2 internal status:
    05/29/09 16:09:20.607 idoup2 idoc_upload failed with rc=(18), try(1)
    05/29/09 16:09:21.607 idoup2 Logoff...

  • HOWTO: Process IDocs To non-SAP receiver

    Hi Experts!
    Today our SAP R/3 sent the IDoc LOIPRO to non-SAP external system, called O2P.
    Now, we would like to send this IDoc (LOIPRO) to XI, and the XI sends the IDoc to the non-SAP external system.
    Then, our scenario will be:
    Step 1. The IDoc LOIPRO is sent from SAP R/3 to XI
    Step 2. Inside the XI, this message is routing and mapping to the
    IDoc LOIPRO too.
    Step 3. The XI sends the IDoc LOIPRO to the O2P (non-SAP external system).
    Well, until Step 2, everything is OK.
    But, we are having troubles to create an IDoc Adapter receiver to O2P (external system), because the O2P is a non-SAP system.
    So, how can we create the communication channel IDoc Adapter, if the receiver isn't a R/3 system ?
    All information will be welcome.
    Thanks a lot,
    Honorato

    HI,
    You can achieve this by dealing with the Native IDOC structure via Integration server for Non-sap systems.
    In this case you can use the IDOC adapter to receive the IDOCs to Non-SAP system. Its like treating the receiver Non-SAP system as an SAP system only. For this Non-SAP system should be compatible enough and SAP certified to accept the IDOC structures..
    Refer similar kind of discussions and reference docs.
    Sending and Receiving IDOC from SAP to Non SAP system
    http://help.sap.com/saphelp_nw04/helpdata/en/52/16abc2543311d1891c0000e8322f96/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6524507d11d18ee90000e8366fc2/frameset.htm
    Thanks
    swarup

  • SAP Sending IDOCs to DOTNET IDOC Receiver

    We are setting up a DOTNET IDOC Receiver to receive IDOC's from our SAP system. While doing a proof of concept today, we tested the case of SAP trying to send the IDOC while the DOTNET IDOC Receiver was not available (I had turned it off). The IDOC status in SAP reported that it had been sent (03). If I turned on the IDOC Receiver (using the sample program), it received the IDOC's with no trouble and the IDOC status in SAP reported sent also.
    Questions: Does anyone know why SAP thinks it has sent the IDOC yet when we do a test connection from WE20 it fails?
    We need to insure that all IDOC's from SAP have been sent to the IDOC receiver -- any suggestions on how to insure this transfer has taken place?

    Hi,
    The Spell Checker made some changes in my last response and I have to change the changes:
    The status Sent (03) just means that the IDOC has been sent from the ALE/IDOC layer to the communication layer (tRFC). If the IDOC receiver is not available, the sent IDOC will stay in the RFC outbound queue (SM58). If the receiver become available again, the RFC engine will send the IDOC from the tRFC queue to the receiver. After receiving the IDOC, the receiver will in turn send back a confirmation to the tRFC outbound queue. Up to this moment, the status of the IDOC in ALE/IDOC is still 03. Sometime later, a pre-scheduled ABAP report (RBDMOIND)will check the tRFC queue and update the IDOC's status to "Confirmed" (12) if the IDOC has been removed from the tRFC outbound queue. There are also other means can be used to update the final status of the IDOC.
    For details about IDOC processing inside SAP, please refer to the related documents.
    Hope it somehow helps,
    Guangwei

  • Idoc  b/w sap(r/3) and non sap system .

    hi gurus,
    how i pass an outbound idoc  b/w sap(r/3) and non sap system .
    which  function module we will use in this scenerio for inbound and outbound idoc both
    please guide me  with an example .

    Hi Pawan,
    Non SAP system should have RFC adapter in order to receive and send Idocs from/to SAP.
    If this is not your case, you should us a Integrator Middelware with RFC and standard adapters like SAP Exchange Infrastructure.
    If for example, your non SAP system is able to process data from flat files you can build next interface: SAP send Idocs to middleware that receive them using RFC adapter, middelware maps Idocs into flat file and send it to a one of non SAP system folder using FTP adapter. Non sap system triggers the flat file into its applications.
    Reward points if useful.
    Roger

  • IDOC generation in SAP R/3

    Hi,
    I want to know how to generate the IDOC for MATMAS??
    Regards
    suman

    Follow this simple procedure
    1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
    Create File Port (WE21) for outbound file.
    Maintain Distribution Model (BD64) for sender ->receiver system.
    Create Partner Profile (WE20) for logical system.
    You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s).
    _ Then you can FTP the file(s) to receiver system.
    2) Upload the flat file as an IDOC on the inbound sytem
    which is Client2(RECIEVER).
    Create File Port (WE21) for inbound file.
    Maintain Distribution Model (BD64) for receiver -> sender system.
    Create Partner Profile (WE20) for logical system.
    You can use this program RSEINB00 to upload IDoc MATMAS file(s).
    INBOUND IDOC PROCESSING:
    Firstly attach your idoc to a process code.
    In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
    Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
    1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
    2. Set Function Modules as Inbound: - Transaction BD51
    3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
    4. Create process codes : Transaction WE42, and link the z-function module.
    5. Create partner profile: transaction WE20 and attach the message type and process code.
    6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
    Try the Trasaction WE19 for testing your inbound and outbound IDOCs
    links that will help you
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    ALE/ IDOC/ XML
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
    http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
    IDOC Convertion
    /people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
    cheers
    sharad
    Edited by: sharad narayan on Apr 16, 2008 1:23 PM

  • Sending IDoc from Non-SAP system to XI

    Dear all,
       We have a non sap system which needs to send IDoc to XI, Please could you answer my following four questions
    1. What should be the values for the following fields in the IDoc control record
    e.g. RCVPRN = <logical system name of XI>
    SNDPOR
    SNDPRT
    SNDPRN
    RCVPRT
    RCVPOR
    2. How does XI decide which port(idx1) to be used when it receives an idoc
    3. The third party system is a non sap one, so it does not have a client no, so I would assume, I need to use another SAP system as a meta data provider, in that case, how would i tell XI to use that port when it receives IDocs from the non-SAP system ?
    4. In what step does XI use the logical system name of the Business system(in SLD)?
    Thanks in advance
    cheers
    danus
    Edited by: Chidambaram Danus on Jan 25, 2008 2:21 PM

    Hi
    there is bit wrong interpretation of the statement
    If the sender system is a non-SAP system, the sender service is identified from the logical system name of the sender port.
    If the sender system is nonSAP it indicates taht the data is coming to XI from non sap systems such as file, database, webservice etc. to XI and from XI it will pass to sap as IDOC inbound.
    For this you need to create the logical system in SAP (receiver) and pass on that value to IDOC header.
    You could maintain it in the Business service used for Sender system (nonSAP). here it will be available in the tabs ---> History.
    note : IDOC is the concept of data container in SAP, you will not be able to have the IDOCs in non sap systems...
    Thanks
    Swarup
    Edited by: Swarup Sawant on Jan 25, 2008 2:54 PM

  • A problem about IDOC Receiver

    Hi, everybody.
    This time, I'm developing a IDOC Receiver though the SAPIDocReceiver class. With the dotnet Connector manual from SAP, the receiver side on dotnet is easy to develop. But how to configure the SAP R/3 to send IDOC to the dotnet side, I can't find the clear steps in the manual.
    So I searched some material about how to configure IDOC, and hope it will be useful to my work. But most of them mainly focus on how to configure a IDOC transformation between SAP system but not NON-SAP system.
    So what I want to ask is IS there some difference with the two configuration, I mean the SAP to SAP one and the SAP to NON-SAP one. I guess the difference should be have. Are the necessary configure step like create a logic system, allocate logical systems to clients and so on also necessary under the NON-SAP case? I think some of the configure actions is different in this two case. Can anyone give me some clear steps or tell me where I can get them?
    thanks to all.

    Hi,
    for testing purposes you can do the following:
    (1) via SM59 create the RFC destination for your dotnet application
    (2) via WE21 create a trfc-port pointing to the RFC destination created in (1)
    (3) via SM30 maintain view V_TBDLS to create a new logical system for your dotnet application for example DOTNET (and maybe for the SAP client you are testing with - here the name could be for example <SID>CLNT<CLIENT>)
    (4) via SCC4 assign the logical system to the SAP client (for example <SID>CLNT<CLIENT>) only if not already maintained.
    (5) In WE20 create a partner profile for logical system created for the dotnet application in step (3)
    (6) In WE20 add outbound parameters for the message type (for example MATMAS) and idoc type (MATMAS03) you want to send. As partner port use the trfc-port of step (2)
    (7) In WE19 create an IDoc via basic type (the idoc type used in step (6), for example MATMAS03) and maintain the following fields in the control record EDIDC:
    <b>recipient port</b> the port created in step (2)
    <b>recipient partner number</b> the logical system name of the dotnet application created in (2)
    <b>recipient partner type</b>'LS'
    <b>sender port</b> SAP<SID>, where SID is the SAP system id
    <b>sender partner number</b> the logical system name the SAP client maintained in step step (4)
    <b>sender partner type</b>'LS'
    <b>message type</b> the message type used in step (6), for example MATMAS
    In the other segments E1* you can fill in whatever you like
    Hit the push button "Standard outbound processing"
    (8) you can check if the IDoc has been sucessfully created by BD87. If an error has occurred in the receiving application or there is any other error you can also see it here. Maybe the IDoc is not passed to the receiver, then you can process the IDoc also from here.
    This is how you can create your test environment. If you want to get the IDoc created form the SAP application it depends on the application how to do that!
    Best regards,
       Willy

  • Problems in IDOC receiver communication channel

    Hi,
    I am trying to build an interface to get data from 3rd party legacy system using JDBC and post the data into ECC using IDOCS. I have IDOC built in ECC, I am able to import the metadata in IDX2 after creating port in IDX1. But after building the whole interface, I dont see the IDOC receiver communication channel which has to post IDOCS in the ECC 6.0 system.
    Please assist.
    Rgds
    Kishore

    OK in that case, we are getting the following error in the Message monitoring:
    <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code>
      <SAP:P1>-BS_AVN_TO_FILE_JDBCSERVER</SAP:P1>
      <SAP:P2>-BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:AdditionalText>
      <SAP:Stack>Problem occurred in receiver agreement for sender -BS_AVN_TO_FILE_JDBCSERVER to receiver -BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY: No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:Stack
    Please check and assist.
    Rgds
    Kishore

  • Overwrite MESTYP in IDoc Receiver Adapter PI 7.1 SP8

    Hi all,
    can anybody tell me, how i can overwrite the MESTYP field in Idoc Receiver Adapter in PI 7.1 SP 8
    BR,
    Martin

    If you would have read the link you posted, you would have seen that "Apply Control Record Values from Payload indicator" in the receiver IDoc adapter, only overwrites the following fields:
    MESCOD
    MESCFT
    TEST
    EXPRSS
    STD
    STDVRS
    STDMES
    SNDSAD
    SNDLAD
    RCVSAD
    RCVLAD
    REFINT
    REFGRP
    REFMES
    STATUS
    DIRECT
    OUTMOD
    CREDAT
    CRETIM
    Sorry but it seems that this forum just get's spammed with answers based on superficial knowledge just in order to increase the count on your answers.
    Hopefully SAP-Forum admins quickly implements a quality control for forum answers!

  • Sender IDOC adapter for SAP 3.1H system & XI 7.0

    We are on XI 7.0 and XI would receive a IDOC message from SAP 3.1H system.
    I need to import IDOC's in imported objects in integration repository but I cannot see any IDOC under the IDOC node. I am able to see the RFC's. Do we need to do extra steps with SAP 3.1H version for IDOC adapter?
    Thanks in advance for help!
    Mrudula

    Ahmad,
    This thread is for sender RFC adapter. I am able to see the all the RFC's but not IDOC's from Integration repository for imported objects from SAP 3.1H version.
    Thanks!
    Mrudula

  • *IDOC INBOUND ( NON SAP system - SAP system )*

    I am transferring IDOC  INBOUND ( NON SAP system ->> SAP system ) by calling SAP standard funtc module IDOC_INBOUND_SINGLE using SAP JCo.
    In which I am passing all necessary information in Control Record regarding sender and receiver port/IDOC/segment etc.
    BUT help me to clarify my doubt that if i am calling a function and i am able to access SAP FM, then why i have to specify the SAP port/RFC connection at RECEIVER end in WE21.
    Whats the Significance if i am calling the FM from same SAP system and configuring the port explicitly in WE21.*
    If i don't Specify in we02 i am getting error as EDI : RECEIVER PORT in CONTROL RECORD is INVALID

    Dear Sree,
    For Basic understanding of IDOC read : saptechnical - Step-by Step ALE IDOC guide ( all necessary TCodes available here )
    Kindly let me know your data flow .
    In short :
    As per my scenario the data flow is from  non SAP to SAP  i,.e. Inbound processing.
    At my non SAP  i am calling SAP standard function IDOC_INBOUND_SINGLE using SAP Jco 2.1.
    You have to fill all Control Structure EDI_DC40 ( port etc. ) and Table parameter EDI_DD40 ( segment etc. )
    Read IDOC status and error in WE02.
    Goodluck.
    - Aakash

  • Idoc Receiver - Header Data does not update

    Hi there
    I have an Idoc receiver in a scenario where I send a Idoc from a file to the R/3 system. My config is all fine but the Idoc status in we19 shows red. My Header data for the idoc is incorrect. The idoc is WALREQ01. In my Message Mapping Im setting the SDNPOR, SDNPRT, SDNPRN, RCVPOR, RCVPRN to the correct values and the I activate the scenario but in we19 it still shows the incorrect idoc header. It does however change the idoc segment data, just not the header. Is there maybe some other place I have to set the Idoc header data?
    Thanx,
    Jan

    Hi Jan,
    From help.sap:
    Apply Control Record Values from Payload
    If you set the indicator, the conversion of communication parties to the IDoc partner is only possible for systems that are not logical systems.
    If you do not set the indicator, all combinations of communication parties and services are handled as services without party.
    If the IDoc XML structure contains a control record during outbound processing on the Integration Server, it is rejected and created again by the IDoc adapter. If you want to include additional values in the control record, set the indicator and provide an appropriate mapping for the values. See also: Fields of the IDoc Control Record
    http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/content.htm
    Carlos

  • Stop IDOC receiver channel

    Hi folks,
    I have what seems like a simple question about IDOC receiver channels, but I have yet to find an elegant answer.
    My scenario is a Non-SAP system with an http sender through XI to an R/3 IDOC receiver. My R/3 system will go down for upgrade for a 2 day period but the external system will continue to send messages.
    I suspect the IDOCs will queue in XI while R/3 is down because the RFC destination is unreachable, but I would like to stop attempts to send while the R/3 system is down.
    I know about availability times for other channels but this technique is not available for IDOC. Is there some way of scheduling the IDOC distribution from XI so that no attempt to send to R/3 is made during the outage ???
    Thanks in advance,
    Guy

    Thanks Karthik,
    That's exactly what I did to demonstrate what might happen (used the wrong password). The message went into error, I reset the password and re-processed and all was fine.
    It just seems to me that there should be a cleaner way - maybe something in QOut scheduling ??
    Thanks,
    Guy

  • Stop generation of Inbound IDOC from Non - SAP

    Hi Experts,
    I have a requirement to update data base PA0105 for Email. The Email is coming for external system (Non SAP), which contains 1 employee in 1 IDoc. If SAP has valid email and same has been passed for external system to SAP via Inbound IDoc, it should not update PA0105. Hence, I am deleting the IDOC segments in Exit "ZXHALU07", before RBDAPP01 is getting called. As per the requirement its working fine.
    Question: Is there any way to stop generating the IDOC. If the email ID were same, then IDoc should not generate in SAP.  Please provide your valuable reply.  Thanks.
    Regards,
    Ganesh R K.

    Hi All,
    Scenario:
    Need to Create Inbound IDOC in SAP system and receive it from Non Sap system.
    Problem:
    IDOC is successfully dispatched from Non Sap system(Sender Side) but, it is not received to SAP system(Receiver Side).
    At receiver side(in SAP system) all configuration settings are fine (RFC destination is tested with no errors, partner profile are given with the inbound parameters, function module is successfully tested with no errors, distribution model is created etc).
    In receiving system(SAP) no IDOCs are generated in We02 after sending the IDOC from Non Sap side.
    Can any one please suggest me the reason for the above mentioned problem?
    Thank you,
    Swetha.C

Maybe you are looking for

  • HT204053 using same apple id for store purchases and different icloud on each device

    I have an apple  itunes id that ive had for years.  I bought my kids an ipad mini each and want to use the same apple itunes id on them  BUT a different icloud because i have used up all my own icloud, they should have their own right?  How to get di

  • Email Functionality on Click of button

    Dear All, I have a requirement whereby I have to trigger an email once my Adobe a custom button is clicked. It should also be saved in the local system ( which of course, it does ). Please provide some leads on this. How do I put a custom 'Email' but

  • New Field not Showing up in Report, part II.

    I had this issue with another report, and I was told that I hadn't brought my new field down all the way through to the final Select.  With this report, I thought I had done just that, but the new field is still not showing up.  I have pasted the cod

  • Comp not recognizing nano; no library

    my computer crashed a few weeks ago and all my files were lost and today i installed itunes again and plugged in my nano but i can't delete any songs from it and i can't play any songs from it. my library is completly empty. how can i get all my musi

  • IW32 Operations problem

    Hi Experts,   I got a requirement of smartform in whuch user want OPERATIONS and its corresponding COMPONENTS to be displayedfor a particular service order in IW32 or IW33.In our system material is not maintained for all operations.But the user wants