Idoc 64 Status processing

Hi,
The inbound idoc is generated with status 64-IDoc ready to be transferred to application. But not posted. How to process this to get the status 53-Application document posted.
I tried in WE14, there it shows the message as "No IDoc is ready for processing".
pls do the needful.
rgds,
balu

run BD87 or prog RBDAPP01

Similar Messages

IDoc-to-File: Status=processed succesfully but file is not always delivered

Hi Experts,
I have a problem with a IDoc-to-File scenario. I generate an IDoc and send it to the XI-System. Afterwards a XML-file is created which should be transmitted to a filesystem or to a ftp server (I tested with both). In the SXMB_MONI the Message has the Status "Processed Succesfully" and the Acknowledgement-Status "Still awaiting acknowledgement". The problem is that not all files arrive the destination succesfully. sometimes they arrive and sometimes not. and always the same status in the sxmb_moni.
if a message not arrived the destination, in the message monitoring in the runtime workbench there is the status "To Be Delivered". If one Message has the status "To Be Delivered" the following messages get this status too.
the communication-channel-monitoring says that "the communication channel is correctly configured and started"
Can you help me? I don't know where the problem is. could it be that the adapter-engine has some problems?
Thanks and best regards
Christopher

hi,
I clicked on details in the message monitoring but the fields "error category" and "error code" are empty. Then I checked the audit log in the message monitoring. there are the following three entries
2008-01-28 14:08:56 Success Message successfully received by messaging system.
2008-01-28 14:08:56 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-01-28 14:08:57 Success Message successfully put into the queue.
and here the audit log of a message which could be transmitted correctly:
2008-01-28 10:33:10 Success Message successfully received by messaging system.
2008-01-28 10:33:10 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-01-28 10:33:10 Success Message successfully put into the queue.
2008-01-28 10:33:10 Success The message was successfully retrieved from the receive queue.
2008-01-28 10:33:10 Success The message status set to DLNG.
2008-01-28 10:33:10 Success Delivering to channel: FILEPORT_TO_PICC
2008-01-28 10:33:10 Success MP: entering
2008-01-28 10:33:10 Success MP: processing local module localejbs/CallSapAdapter
2008-01-28 10:33:10 Success File adapter receiver: processing started; QoS required: ExactlyOnce
2008-01-28 10:33:10 Success File adapter receiver channel FILEPORT_TO_PICC: start processing: party " ", service "X22_PICC"
2008-01-28 10:33:10 Success Write to file "/tmp/xi/PICC/INV_5075_4000102108_20070109_103310.XML" as binary, size 410 bytes
2008-01-28 10:33:10 Success File processing complete
2008-01-28 10:33:10 Success MP: leaving
2008-01-28 10:33:10 Success The message was successfully delivered to the application using connection File_http://sap.com/xi/XI/System.
2008-01-28 10:33:10 Success The message status set to DLVD.
2008-01-28 10:33:10 Success Acknowledgement creation triggered for type: AckNotSupported
2008-01-28 10:33:10 Success Acknowledgement sent successfully for type: AckNotSupported
can you say me where the problem is?
thanks and regards
chris

How to process Idoc status file within Sap?

Hi All,
We would like to process received status file to update the sent IDOC's. Our current setup is that we send/push the Outbound Idoc to external EDI sub system and pull the status file for processed Idoc from external EDI system to our R/3 server.
Sap Documentation explains the scenario, where this process is triggered from external system using startrfc program, whereas our scenario is to trigger the status update process, once the file is pulled to our system from unix using edi_status_incoming function module.
Your anwers are much appreciated.
Kind Regards,
Sandhya

Hi Sandhya,
Once the Idocs are sent to the EDI Subsystem, the SAP will have the status that the Idoc has reached the partner sub system. I hope, the workflow should be able to trigger back the status file to the SAP System after the Idoc is processed at the EDI Subsystem.
Please check with the workflow that is attached.
Else, if this is using the FM or Message Control, then check the configuration under MN04.
I'm also trying to find the solution for the same.
Regards,
-Syed.

What is the Successfull processed IDOC status number?

Hi Experts
What is the Successfull processed IDOC status number?
arjent Please.
Thanks in advance
Sekhar

Hi Chandra,
Below are IDoc Process Codes
For outboud Idocs:
1 IDoc created
2 Error passing data to port
3 Data passed to port OK
4 Error within control information of EDI subsystem
5 Error during translation
6 Translation OK
7 Error during syntax check
8 Syntax check OK
9 Error during interchange handling
10 Interchange handling OK
11 Error during dispatch
12 Dispatch OK
13 Retransmission OK
14 Interchange Acknowledgement positive
15 Interchange Acknowledgement negative
16 Functional Acknowledgement positive
17 Functional Acknowledgement negative
18 Triggering EDI subsystem OK
19 Data transfer for test OK
20 Error triggering EDI subsystem
21 Error passing data for test
22 Dispatch OK, acknowledgement still due
23 Error during retransmission
24 Control information of EDI subsystem OK
25 Processing despite syntax error (outbound)
26 Error during syntax check of IDoc (outbound)
27 Error in dispatch level (ALE service)
28 Not used
29 Error in ALE service
30 IDoc ready for dispatch (ALE service)
31 Error - no further processing
32 IDoc was edited
33 Original of an IDoc which was edited
34 Error in control record of IDoc
35 IDoc reloaded from archive
36 Electronic signature not performed (timeout)
37 IDoc added incorrectly
38 IDoc archived
39 IDoc is in the receiving system (ALE service)
40 Application document not created in receiving system
41 Application document created in receiving system
42 IDoc was created by test transaction
50 IDoc added
For Inound Idocs
51 Error: Application document not posted
52 Application document not fully posted
53 Application document posted
54 Error during formal application check
55 Formal application check OK
56 IDoc with errors added
57 Test IDoc: Error during application check
58 IDoc-Copy from an R/2 connection
59 Not used
60 Error during syntax check of IDoc (inbound)
61 Processing despite syntax error (inbound)
62 IDoc passed to application
63 Error passing IDoc to application
64 IDoc ready to be transferred to application
65 Error in ALE service
66 IDoc is waiting for predecessor IDoc (serialization)
67 Not used
68 Error - no further processing
69 IDoc was edited
70 Original of an IDoc which was edited
71 IDoc reloaded from archive
72 Not used, only R/2
73 IDoc archived
74 IDoc was created by test transaction
Regards,
Satish

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

IDOC status at 30, but in we05 it is 03

Hello Gurus!!
My program generates an IDOC and as soon as the idoc is generated it the status is 03 then i have todo something else.
Within the program when i am cheking the status is 30 but actually in transaction we05 the status is 03.
I have cheked the partner profiles and transfer_idocs_immeadiately has already been selected.
I have already gone thru the forum but no valid solution was given,
There is no need to change any ALE configurations / port configurations because everything just work fine. It is only that within the program i am not able to catch the status 03. the proram is not waiting untill the idoc status is 03. it is capturing only the status 30.
Is there any thing that i can do within the program? should i capture the idoc number and then check the idoc status from EDID4?
Please answer o this questions ASAP.
Regards.

Initially when you create the outbound idocs then status is 30. then you have to run the program RSEOUT00 to process the idoc then after the processing the status changes to 03.
But the Program RSEOUT00 is optional. In the partner profile (WE20) If you select the option 'Collect Idocs', then you have to schedule the program RSEOUT00 to process the Idocs otherwise if you have choose the option 'Transfer idoc immediately', you don't need to do anything.
Thanks,
Srinivas

IDOC STATUS 29 to 68

Hi all,
Customer request is change idoc status from 29 to 68.
68 = no further processing inbound side
31 = no further processing outbound side
if i change status of idoc from 29 to 68 using Fn module IDOC_STATUS_WRITE_TO_DATABASE
Data of idoc is vanishing.
I observed that if i change status of idoc from 29 to 31 then there is no data loss in idoc with same Fn module.
Is there any way to change idoc status from 29 to 68 without losing the Idoc data.
anyway for both 68 & 31 meanings are same , but customer requires 29 to 68.
if u have any idea please suggest me.

Hi Suneel,
If the program does't exits then try this ...
DATA: L_EDIDC_TAB       LIKE EDIDC      OCCURS 1 WITH HEADER LINE,
      L_IDOC_STATUS_TAB LIKE BDIDOCSTAT OCCURS 1 WITH HEADERLINE,
      L_IDOC_CONTROL    LIKE EDIDC.
    L_IDOC_STATUS_TAB-DOCNUM = <your IDoc number>.
    L_IDOC_STATUS_TAB-STATUS = '68'.
    APPEND L_IDOC_STATUS_TAB.
    CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
         EXPORTING
              IDOC_NUMBER               = L_EDIDC_TAB-DOCNUM
         IMPORTING
              IDOC_CONTROL              = L_IDOC_CONTROL
         TABLES
              IDOC_STATUS               = L_IDOC_STATUS_TAB
         EXCEPTIONS
              IDOC_FOREIGN_LOCK         = 1
              IDOC_NOT_FOUND            = 2
              IDOC_STATUS_RECORDS_EMPTY = 3
              IDOC_STATUS_INVALID       = 4
              DB_ERROR                  = 5
              OTHERS                    = 6.
Regards,
Ferry Lianto

IDOC status 03 but no XML generated

Hi Experts,
I am facing a problem related to idoc i.e. I am getting idoc status 03, still no XML created at the server directory.
Scenario is: A custom idoc is created with a z report which selects data & send idoc as an XML file in the server directory
IDOC (the first \ represents root as it is a unix server, 2nd \ is a saparator nd then IDOC is a folder to save XML files). Folder IDOC is having all permission(777). When i send idoc using the report is fives status 30 & after that when process it through BD87 it gives a status message 03.
I checked the partner profile, port etc. Even in port access test is OK.
I even tried putting directory as //IDOC , /IDOC but then no access possible error came. only work with
IDOC & gives status message 03.
But no idoc is reaching at the other end i.e.
IDOC.
Can anyone tell me how to fix this problem. Is the problem at SAP end of Unix end.
Regards,
Nik

Hi,
Check the Port configuration.In this case mostly problem form port configrations only.
Check Directory,Outbound file paramters in the port configuration.
Thanks,
radha.

IDOC Status, Tracking in SAP PI/PO Single Stack

Hi All,
My PO version: 7.4, SP4. I am not sure my questions below are still a limitation in current PI/PO single stack systems, and hence requesting your help for the same.
1) Is there a way we can track outbound idocs in SAP PI/PO single stack similar to PI abap stack IDX5? ( Note:- I couldn't find any option in IDOC monitoring in single stack SAP PO 7.4, SP4)
2) IDOC status is always 0 in SAP PO 7.4 single stack IDOC monitoring. I am not sure if this status is just specific to my PO system. Any setting needs to be applied?
ps: Please post only relevant answers/solutions
Thanks,
Praveen Gujjeti
Message was edited by: Praveen Gujjeti

Hi All,
As per SAP help: Comparison of IDoc Adapter (IE) and IDoc Adapter (AAE) - SAP NetWeaver PI Reference Documentation - SAP Library idoc status and tracking not supported in current PO versions. May be SAP will add this feature in upcoming PO versions
Auditing, Monitoring ,and Tracing Functions
Attribute/Feature
IDoc Adapter (IE)
IDoc Adapter (AAE)
ALE Audit
Supported
Supported
IDoc tracing
Supported (transaction IDX5)
Not supported
IDoc monitoring
Transaction IDX5
Integration with channel monitor and message monitor (as part of Advanced Adapter Engine monitor)
Status tracking -SYSTAT
(analysis and further processing of messages that have not been processed)
Not supported
Not supported
RFC monitoring
Supported
Not supported
Message persistence in the IDoc adapter
Supported
Message correlation information can be stored in IDoc adapter.
Not supported.
Message is persisted in messaging system with correlation data persisted in adapter.
Regards,
Praveen Gujjeti

Need to change the Idoc Status based on the Text in the Idoc

Hi All,
I have developed Idoc--SOAP Sync Process Scenario Using BPM and Works Perfectly.
I have used STATUS.SYSTAT01 Idoc to capture the Response that is comming from the Webservice.
I have mapped the response Text( Success or Fail) to one of the field in the Response Idoc, this is perfect.
Requirement:
1) If the Response Idoc Field receives Success Text means the Idoc Status shld be in Green Status.
2) If the Respnse Idoc Field Receives FAIL means the Idoc Status shld be in RED Status.
How can i Do this. please suggest me......
Regards

Hi Santhosh,
YES, I have to Capture the Response from Webservice in SAP R/3 by using STATUS.SYSTAT01 Idoc.
I have mapped the response from webservice to the one of the field in the Idoc.
If this field contains Success as text means the Idoc Status in We05 shld be 53 else it shld be 56
With out changing the FM code, can we use any other process to achieve this???
@ Mario
Can u please Allobarate your views more based on my requirement
Regards

IDOC status not changed

SAP support
I am not able to change the IDOC status...
I have also processed the IDOCs many times..
Guidance required...
Kamal

Dear Kamal
Please check your entry in SM12 an delete it and again reprocess it with the help of Tcode Bd87
Thanks
Amit Shivhare

File -- XI -- IDoc ( IDoc Status 56)

Iam trying to post IDoc(cremas03) with File --> XI --> Idoc Scenario.
I got message processed successful in SXMB_MONI.
However on ECC5.0(R/3) I got Idoc status 56.
EDI: Partner profile inbound not available
Message no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/T20CLNT400/LS//CREMAS////
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST    test flag
Procedure
Please check the inbound partner profiles.
Execute function
On IDOC Display (We02) I found following info:
Technical Short Info
Direction : 2
current status: 56
Basic type: cremas03
Message type: cremas
Partner No: T20CLNT400
On Idoc control Record:
Typeinfo tab:
Basic Type: CREMAS03
Message Type: CREMAS
Partner Tab:
Recipient
Port:   (Spaces)
Partner No: ID3CLNT550
Partner Type: LS
Sender
Port: SAPSXI
Partner No: T20CLNT400
Partner type: LS
Tech Info:
Sap rel : 640
On Partner Profiles:(WE20)
ID3CLNT550 ( in this case receiver) was defined as Logical Sytem and Inbound message type CREMAS
Would someone please guide me what to do as Iam learner of XI.
Thanks a lot

Here it is.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>400</SAP:MANDT>
<SAP:DOCREL>640</SAP:DOCREL>
<SAP:DOCNUM>0000000000046232</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>CREMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPSXI</SAP:SNDPOR>
<SAP:SNDPRN>T20CLNT400</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPECC</SAP:RCVPOR>
<SAP:RCVPRN>ID3CLNT550</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS />
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY>BAA624009F6311DA8AD3003048805A88</SAP:ARCKEY>
</SAP:IDocOutbound>
Following data was defined in receiver system, Client 550
Inbound parameters:( With we20)
PartnerNo: ID3CLNT550
Type: LS
Inbound parameters:
Partner Role : LS
Message Type: CREMAS
Process Code : CRE1
Trigger immediately
PartnerNo: ID3CLNT550
Partner Type: LS
Inbound parametrs:
Partner role:   <---- blank here ..does this matter ?
Message Type: CREMAS
Process Code: CRE1
Trigger immediately

Idoc status 53

hello all,
i have received an Inbound IDOC with Error Status 53.
what could be the solution.please help me out
santosh

hi,
Status 53 is the status you want from an inbound idoc.
It tells us the idoc has processed successfully.
When you open the status log, it should tell you
"Sales order xxxx has saved successfully"
kind regards
Paul Q

How to create an IDOC Status.

Hi All,
I have a requirement to create an IDOC Status, which should be a copy of existing status.
How to accomplish the same.
Regards,
Neha

Hi Neha,
You can create the Idoc status, if it is an Inbound Idoc. Copy the Existing process code & add it to u r Inbound Partner Profile. In the process code u can create the status..Check the below code.
if gv_error_status <> 0.
        condense gt_msgv-msgv1 no-gaps.
        translate gt_msgv-msgv1 to upper case. "#EC TRANSLANG
        set extended check on.
        read table idoc_contrl index 1.
        idoc_status-status = '68'.
        idoc_status-uname = sy-uname.
        idoc_status-repid = sy-repid.
        idoc_status-routid = gv_funcname.
        idoc_status-docnum = idoc_contrl-docnum.
        idoc_status-msgv1 = gt_msgv-msgv1.
        idoc_status-msgv2 = gt_msgv-msgv2.
        append idoc_status.
        idoc_status-status = '51'.
        idoc_status-uname = sy-uname.
        idoc_status-repid = sy-repid.
        idoc_status-routid = gv_funcname.
        idoc_status-docnum = idoc_contrl-docnum.
        append idoc_status.
endif.
I hope this help you.
Regards
Rajendra

IDOC: Status (Error/Success/information)report to Sender system

How would one send a message(error/success/information) to the sending(external) system to inform them of the statuses of the messages they've sent to our SAP system?

Hi Baumann,
you have an option called Audit reporting in which you can have the status of idoc at sender side.read the following.
Setting Up Audit Reporting
In the default behavior, after an IDoc is dispatched to a destination system, the sender does not know the state of the process on the destination system. You can configure the system, however, for cross-system reporting. You must model the ALEAUD message between the systems.
Two programs enable cross-system reporting.
1)RBDSTATE. This program is scheduled to run periodically on the destination system. It reports the status of incoming IDocs to the sending system, using the ALEAUD message and ALEAUD01 IDoc. This status information is recorded separately from IDoc status information in the audit logs.
2)RBDAUD01. This program is executed on the sending system. It analyzes the audit log and displays the output as a report.
The RBDSTATE program returns the following statuses, from the receiving to the sending system.
RBDSTATE Is Run on the Receiving System
Status of IDoc in receiving system     Status reported to sending system via ALEAUD
53 (Application document posted.)     41 (Application document created in receiving system.)
51 (Error: Application document not posted.)     Status 39 (IDoc is in the receiving system.) This status is repeated each time RBDSTATE is run, as long as the IDoc remains in status 51.
68 (Error: No further processing.)     40 (Application document not created in receiving system.)
reward points if helpful,

IDOC Status 68 & 51

Hi,
There is an IDOC with status 68 (Error - no further processing) , Earlier it was in status 51 with the status text "INVALID DATE' .
How to find out for which particular date field's the error is being thrown..?? what is the approach to find out the root cause of the issue.?? the IDOC is being sent to R3 through XI.
Plz give suggestions on how to tackle the issue.
Thanks in advance,
Jai

Hi ,
The idoc Status for 59 and 51 for indound idoc is....
68 Error - no further processing
51 Application document not posted
the possible solution is checkthe Partner profile for the Idoc and Port number..
and go to T_code we20 and check the Partner.and check the Syntax in the application tool bar...
then you will come to know the problem..
Regards,
Prabhudas

Idoc 64 Status processing

Similar Messages

Maybe you are looking for