Status IDOC

Hi All,
I have a scenario where i have an inbound IDOC coming in. I need to send a status IDOC ALEAUD back to acknowledge the reciept.
We are not using PI to post this IDOC.
Can any body please suggest how can we configure to send status IDOC back for this inbound IDOC to the sender system.
I know may be this is not a correct forum.
Thanks
-Kulwant

Does this help?
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/0b/2a6550507d11d18ee90000e8366fc2/frameset.htm

Similar Messages

  • Multiple status IDOC

    In our production system for an Inbound IDOC two outbound STATUS IDOCs were created.
    My question was, what is the setup for this outbound STATUS IDOC creation ? is there any function module is there?
    For example the inbound IDOC use message type ORDERS. Once it created how it is creating the outbound STATUS IDOC? Is it  any function module or program or any set up required for this? Please let know

    Hi, Welcome to SDN.....
    For Creating Outbound IDOCs, there are 2 options 1 is ALE and the other is EDI, since you have mentioned ORDERS(message type), it seems in your system EDI (Electronic Data Interchange) is configured which is used to as interface with customer or vendors. You can check out for these documentation also you can refer these table - EDID4, EDIDC, EDIDS.
    Cheers...
    Santosh.
    Message was edited by:
            santosh D

  • How to get the status idoc from recieveing system

    Hi All,
    In our requirement we will be sending an idoc to the recieveing system. we are planning to get the staus of the idoc.
    How can you  recieve the status of the idoc that idoc has been is saftly reached to target server.
    Can any one share the solution if you have confirgured  the same before.
    We are planning to use : Middleware.

    Hi Anil,
    If get the status 03 means your idoc successfully send to receiving system port. But in the receiving system if there any issue in processing you can't get these updated status automatically from receiving system. You know Idoc works in asynchronous mode. To get the status you need send one idoc with status (error , success ot warning) from receiving system to sending system.
    Thanks
    Subhankar.

  • Status Idoc Stat01 implementation for acknowledgement from ACH payments

    Can anyone let me know what is the process of implementing ACH acknowledgement using stat01 Idocs?

    Hi,
    This thread has been created some time ago and recieved no response. Can you please close if you feel this issue/query has been resolved in the meantime. If it has not then please provide additional information in relation to your query. By providing updates to your thread it moves you thread to the first page of thread and increases visibility and possiblity for the multiptude of experts in SDN Forums to offer their support.
    Therefore please update with more information or close thread.
    Thank you for your assistance.
    Regards,
    Brendan.
    (ERP FI/CO SDN/WIKI Moderator)
    http://wiki.sdn.sap.com/wiki/display/ERPFI/ERP+Financials

  • Request iDoc and status iDoc correlation

    Hello,
    I have a strange problem.
    In my XI 3.0, I have an iDoc2iDoc interface which used to work fine, until I installed patch level 14.
    Now, when the acknowledgement (ALEAUD) comes back into my R/3 system, the iDoc system does not recognize it as a response for a specific request iDoc I've sent, but as an ordinary inbound iDoc.
    After a short investigation, I found out that the iDoc number is not correlated, it seems like a problem in the iDoc adapter in the XI, that does not translate the iDoc number of the target system back into the iDoc number of the original system.
    Has anyone met with this kind of problem ? any solutions ?
    Thank you,
    Elad.

    Hi Anand.
    All of the partner profile and iDocs configuration are complete and correct.
    I'll try to be a bit more specific:
    Local R/3 sends iDoc MATMAS through XI 3.0 and receives ALEAUD iDoc as an applicational acknowledgement.
    For the R/3 to be able to correlate between the inbound ALEAUD and the outbound MATMAS the iDoc system uses a field containing the iDoc number.
    The problem is that ALEAUD has the number generated by the remote system and the MATMAS has the number of my local system, the XI is suposed to translate the remote iDoc number back to the local iDoc number.
    I hope it's clearer now, and that someone can help.
    Thank you,
    Elad.

  • How to update the Sent Idoc Status based on the Response From Webservice

    Hi All,
    I have to develop Idoc--SOAP Sync Process Scenario Using BPM .
    I have configured every thing using BPM and mapped
    MATMAS----SOAP Request
    SOAP Resp----STATUS.SYSTAT01
    In R/3  the Main Idoc Number(MATMAS) Status needs to be update , but it is creating the new Idoc with STATUS.SYSTAT01.
    I have used STATUS.SYSTAT01 Idoc to Update the status of the Original idoc based on the Response that is coming from webservice .
    I was posted the same thread a days ago and there Bhavesh suggested me some sugessions.
    How can we make the status of the Idoc based on some response Text
    iam unable to follow OR not able to clear my self on this.
    Please suggest me or give some over view kind of thing on this
    Regards

    Hi Suman,
    It is clearly mentioned in SAP help that "SAP Intermediate Documents (IDOCS) are EDI like documents that are asynchronous in nature."
    So Your Scenario is Asynch(receive) - Synch(WS call) -Transformation (Multimapping)- Asynch(Send to R/3).
    now go in this way:
    you can develop all the message Interfaces  of  Abstract catagory (not manditory )
    MI_AA_MATMAS   -> Abstract Asynchronous message    interface for your Matmas IDOC
    MI_AS_SOAP_ReqandResp  -> Abstarct Syncronous MI for SOAP request and response.
    MI_AA_STATUS ->Abstract Asyncronous MI for Status Idoc
    MI_AA_SOAP_Req ->  Abstarct Asyncronous MI for SOAP request .
    MI_AA_SOAP_Res ->  Abstarct Asyncronous MI for SOAP response .
    Thats all in Message interface.
    your first reciever :
    (This will receive the message asynchronously from R/3)
    create a conatainer varaiable (say preceive) and assign it message interface MI_AA_MATMAS
    Now in thw Propert TAB of this step: give this message name.
    Step2: Synchronous call :
    create container Variable psoaprequest and psoapresponse  give abstract message interface MI_AA_SOAP_Req and MI_AA_SOAP_Req  resp.
    Now in thw Propert TAB of this step:
    Synchronous Interface : MI_AS_SOAP_ReqandResp
    Request Message : psoaprequest
    Response Message: psoapresponse
    Transformation Step :
    Here you will specify Interface Mapping that will conatain Multimapping between Synch Response - MATMAs and STATUS
    Let's name it as IM_ResandMatmasToStatus
    create a container variable as pstatus and assign it abstract interface MI_AA_STATUS.
    In Property pan of this step :
    Interface mapping :IM_ResandMatmasToStatus
    Source Message :psoapresponse
                                preceive
    (IT will ask you for two source messages as IM selected in this transformation has 2 source messages)
    Target Message :pstatus
    Send step:
    Select a message as pstatus.
    thats all in IR.
    If have doubt in ID just let me know.
    Thanks
    Sunil Singh

  • IDoc Acknowledgement to JDBC status update

    Hi,
    JDBC --> XI --> SAP R/3 (IDoc ACC_DOCUMENT02)
    JDBC <-- XI <-- SAP R/3 (IDoc ALEAUD01)
    I have the following scenario... I am reading data from a database using the JDBC Adapter. The data is in the following format at source. Using the JDBC adapter I read the database for rows for which the status is blank, this is multiple documents.
    Invoice 1 Status 53
    Invoice 1 Status 53
    Invoice 1 Status 53
    Invoice 1 Status 53
    Invoice 2 Status <blank>
    Invoice 2 Status <blank>
    Invoice 2 Status <blank>
    Invoice 2 Status <blank>
    Invoice 3 Status <blank>
    Invoice 3 Status <blank>
    Using a BPM process I split the source data into multiple messages and map them to the IDoc structure. In the above example Invoice 2 & 3 would be read from the database and split into 2 individual IDocs to be posted separately into SAP.
    IDoc 1
    Invoice 2 Status <blank>
    Invoice 2 Status <blank>
    Invoice 2 Status <blank>
    Invoice 2 Status <blank>
    IDoc 2
    Invoice 3 Status <blank>
    Invoice 3 Status <blank>
    I now want to extend this scenario to include acknowledgement messages which I can use to update the status in the source system.
    I have configured the ALEAUD01 message in the destination system and scheduled the RBDSTATE program to run periodically. I can see in the XI message monitor that my messages now have aknowledgement status.
    What I would now like to do and hopefully someone can help is to use the status information being fed back from SAP in the ALEAUD01 message to update the status field for individual lines in the source table. Can anyone help with this step???
    Regards,
    Pete

    I can see the limitation of ALEAUDIT as it is handled internally in XI. Using the bespoke route I can create a copy of ALEAUDIT and a bespoke IDoc ZALEAUD01 for example, which will send the status idoc to XI.
    In BPM I can configure a receive step to receive the IDoc... But, how do I then relate the IDoc I created to the particular segment in my ALEAUD01 IDoc.
    Regards,
    Pete

  • Inbound Processing of iDoc Status Message

    Silly me - I thought this would be simple ...
    I am currently changing our bank interface from a customized ABAP solution to use more standard SAP utilities (particularly iDocs).  I have the configuration set up to use the PAYEXT message type sending PEXR2002 iDocs to a file port.  Our bank is receiving these documents and is returning an iDoc status message containing the status of each payment iDoc that they received from us.
    My problem is that I can't figure out how to get these status iDocs to update the status of the corresponding PEXR2002 iDoc.
    I am trying to execute an RFC interface to apply these status messages to my system using the following OS command:
    D:\usr\sap\VPR\SYS\exe\uc\NTAMD64\startrfc.exe -3 -d RT2 -u xxxxxx -p xxxxxx -c 220 -h SPR32K36 -s 00 -F EDI_STATUS_INCOMING -E PORT=ZFI_INT003
    The error message that I receive when this is run is:
    RFC Call/Exception: SYSTEM_FAILURE
    Group             Error Group 104
    Key                RFC_ERROR_SYSTEM_FAILURE
    Message        Status record 1 is invalid (TABNAM: 'EDI_DC40')
    The port (ZFI_INT003) is the file port that is configured for the outbound file.  in WE20, this port has the "Status File" tab set to use the logical file name where the status file is being stored on the server.  the startrfc command is connecting to the SAP system and opening the status file.  I'm not sure where I'm going wrong here. 
    Can someone please help get me pointed in the right direction?  I've obviously missed something here.
    Thanks,
    Glen

    Hi,
    call function modules:
    EDI_DOCUMENT_OPEN_FOR_PROCESS
       EDI_DOCUMENT_STATUS_SET
       EDI_DOCUMENT_CLOSE_PROCESS
    kind regards,
    HP

  • No authorization for changing Customer Centrally- Idoc in Error Status 51

    Hi Experts,
    We are implementing MDM for one of the client.
    The client  runs a  modification scenario in MDM for Customer Master.
    He modifies a customer record in MDM and this record is transfered from MDM to ECC via PI through Idocs.
    We are using standard Idocs for Customer Master which is DEBMDM
    There are 2 Idoc's generated in ECC by PI from DEBMDM as DEBMAS and ADRMAS.
    ADRMAS Idoc is succesfull in ECC and the corresponding record is modified.
    Now the issue is that the corresponding DEBMAS Idoc goes into Error 51.
    The Error details is as below:
                                                                                    No authorization for changing vendor Centrally                                                                               
    Message no. F2326                                                                               
    System Response                                                                               
    You cannot access the requested data.                                                                               
    Procedure for System Administration                                                                               
    If necessary, include an entry in the user's authorization profile for  
        the authorization object and parameters specified below.                                                                               
    Authorization object:                                                                               
    o   F_KNA1_APP                                                                               
    Parameters:                                                                               
    o   Activity: 02
        o   Application authorization : *
    We gave the respective authorization object to the RFC User ID used in PI RFC created to connect to ECC.
    Also we have given the user id  Tcode authorization like XD01/02/03.
    But this error still persists.
    Request to throw some light on this.
    Cheers
    Dhwani

    Check these threads
    [Re: IDOC STATUS - 51 " IDOC HAS TEST STATUS|IDOC STATUS - 51 " IDOC HAS TEST STATUS";
    [Error Inbound IDoc - Status 51|Error Inbound IDoc - Status 51;
    thanks
    G. Lakshmipathi

  • IDoc Status update configuration

    I need to utilize the status update process for inbound/outbound IDocs.  My EDI translator sends a status IDoc (EDIDS) that has the IDoc number and the status (nothing more).  Out EDI services are managed externaly so their only role is to place IDocs onto my SAP server.  In other words they do not use call startrfc.
    How can I implement the process of updating the status of an IDoc to indicate if there is a failure in subsytem translation, or positive acknowledgement, and so on???

    Hi Amtnbiker,
    I think your question is more BC related.
    Could you please send new thread in Basis middleware forum?
    Thanks and best regards,
    Smile

  • IDoc Status "& & & &" in IDoc posting in BD87 - ALE

    hi,
    I am integrating two R3 servers and posting the datas from HR to cProjects server.
    In Outbound I can send the IDocs and In Inbound IDocs are getting into destinations (cProjects) servers along with status "& & & &" in BD87.
    Can anyone help me to know..Where the cause of problem..
    Thanks in advance
    Regards,
    Srinivasan.R

    Hi.,
    In we02 its OK..
    Its showing ...
    Status Message for Selected IDoc                                                               
    Status Text:   IDoc: 0000000000036306 Status: IDoc ready to be transferred to application       
    T100 Text:     No filters , No conversion , No version change .                                 
    But., in place of BD87 I am getting status only "& &, &, &".
    Regards,
    Srinivasan.R

  • Soft errors/warnings are creating idocs in 51 status, and creating orders

    In our SAP 4.7 environment, inbound orders that encounter credit checks, materials in the wrong status, blocked customers, and several other issues that should just be warnings or messages rather than resulting in status 51 idocs, are hitting 51 error status, and they are creating orders in SAP as well (51 status idocs are still creating orders, and nuisance messages are creating 51 status idocs, and still creating orders). I assume someone made some programming changes years ago to cause this to happen. This is really polluting workflow and BD87, and customer service is duplicating orders as they process 51 status idocs through workflow, unaware that orders already created immediately regardless of the 51 status.
    Can anyone point me in the direction of where I can specify what warnings or errors constitute 51 status, and where I can stop 51 status idocs from creating orders until the error is repaired?
    Would it be in program RBDAPP01, or the inbound function module EDI_DATA_INCOMING?
    Any help would be appreciated. Thanks!

    Hi Kevin,
    so then it is time to check it out in WE19 debug mode. After each PERFORM in the EDIDC Loop in the FM IDOC_INPUT_ORDERS, check the control and status data, this will lead you to the point where the unexpected and/or unwanted behavior appears.
    In the LOOP AT IDOC_CONTRL, in our system line 183 you find the comment fill IDOC Status. Check if field OK is not cleared here. If OK is set although you should have errors, then it's already too late.
    But please double-check EXIT_SAPL_VEDA_004 if it changes the tables parameter didoc_status = idoc_status.
    What I did not mention yet as I think you are talking only about IDoc not about online processing, applies to both:
    Customizing SPRO, SAP Reference IMG, Sales and Distribution -> Sales -> Sales Documents -> Define variable messages:
    Here you may have entries for application area V4, Sales messages (variable messages and EDI messages). Check if you find suspicious messages set to 'W' here.
    If this is the case and table logging is switched on as it should be, you can use menu uitilities -> change logs to find out who changed what when.
    Good luck!
    Regards
    Clemens

  • IDOC status 30 even if I set transfer IDoc immediately in we20

    Hi All,
    I am creating Bommat IDocs using 'MASTER_IDOC_DISTRIBUTE'  .I am getting the 30 status instead of getting status 3.
    Even   if I set transfer IDoc immediately in we20.
    Please let me know how to resolve this.
    Thanks,
    Vinay.

    Hi Vinay parakala
    Schedule back ground job to program RSEOUT00 regularly to process the 30 status idoc....
    Your program generates the idoc ... and RSEOUT00 will process you idocs which are in 30 status...
    i hope  above info helps you
    Note: enter Message type BOMMAT in  program RSEOUT00
    Thanks
    Ramesh

  • I/B Idoc Status 56 - Reason Required

    Hi,
    We have a PI system and R/3 System. PI sending some idoc to R/3. In this case Idoc is failing and giving status message as 56. Can any one tell me reason why it is giving error like.
    Error messages are like this:
    Status Text:-  IDoc: 0000000001230201 Status: IDoc with errors added
    T001 Text  :-  EDI: Partner profile not active
    Please let me know in which system do i need to the changes and how can i do these changes.
    I am new to this concept.
    Thanks,
    Sekhar.J

    Hi Sekhar,
    From PI perspective everything is fine, you were able to create an IDOC structure and push it to R/3 system and there is also successfully created but it has failed with the error 56. It is due to invalid partner profile, check the transaction WE20 whether a partner profile has been created for that partner or not, if it is created then whether the message type is configured for that partner or not.
    The error is basically due to invalid partner profile and you need to correct that in WE20 transaction, once you correct that then you can reprocess the idoc through BD87 transaction.
    Thanks,
    Mahesh.

  • Tracking Idoc status in target system from XI

    Hi
    We have done File to IDOC Scenario succesfully i.e HR
    data  from file has been mapped to HR Idoc(HRMD_A06) .
    Now when Idoc is posted to R/3 , SXMB_MONI shows 
    successful status(Idoc posted successfully) .
    But when we check in R/3 in WE05 transaction ,though
    the idoc is present but it shows status 51/52
    with message "Idoc could not be posted" /"IDOC not
    fully posted" .
    In this case how can we track in XI  whether the Idoc
    is properly posted in the target system(i.e R/3) .
    Since XI only shows that Idoc was successfully sent
    irrespective of the status in R/3 .
    Please suggest as we are new to XI .
    Regards,
    Shikha

    Hi
    Thanks for the guide.
    we are  not sure of the steps to configure it in R/3
    system so that it sends the acknowledgement back to XI
    system. 
    When we tried to configure it as per the guide , for
    test purposes we executed the program RBDSTATE but it
    gave message "No parties are interested in the selected
    data" .
    Please guide us on this .
    Thanks
    Shikha
    Message was edited by: Shikha Jain

Maybe you are looking for