Idoc Monitoring (Inbound & Outbound Status codes)

Hi ,
In a scenario...whr IDOC has to be send to XI to file.....
and idoc is sent to XI ...if an error occurs ...wht is the process to troubleshoot...wht r the various reasons codes ? in a reverse way ..an IDOC needs to send to R/3 and an error occurs..wht is the process to trouble shoot....pls give a brief note on various idoc status ???
Best Regards,
Kir@n ; )

Main Tools
XI Runtime Workbench
Transactions:
●     IDX1
●     IDX5
●     SXMB_MONI
●     SM58
●     SM21
Analysis
For an overview of analysis steps see a very good link to troubleshoot
[http://help.sap.com/saphelp_nw04/helpdata/en/05/d5fc3f8fc2c542e10000000a1550b0/frameset.htm]

Similar Messages

Idoc inbound error status code 56

Hi,
   when i am sending custom idoc from source system to destination , idoc sent successfully from source system .But in the receiver system idoc status code is 56 ( idoc with errors added) .
partner profile also available in the receiver system. How to solve the error.can any one pls give me the solution.
                                                                                Regards,
                                                                                Suhash.

Hi,
Check this link..[IDOC Status code 56 !!   |IDOC Status code 56 !!]
[Re: Status 56 - IDOC with errors added   |Status 56 - IDOC with errors added]
Edited by: Avinash Kodarapu on Mar 19, 2009 4:55 PM

IDOC Processing Inbound / Outbound

Hi Experts !!
As part of EDI Inbound processing our process is as follows.
1. EDI 850 files are created by EDI sub-system ( Sitting in differerent Environment ) and those file are trasfered to 'INBOX' folder on R/3 server using FTP file server.
2. A batch job ( for ex: EDI850_ORDERS ) executes every 15 minutes to process the files from 'INBOX' folder using the Custom ABAP program ZWRAP_RSEINB00. The program uses standard SAP inbound EDI file processing program 'RSEINB00' to process the file and try posting it into SAP. If the file is successfully posted then the file is deleted.
Here in this case client's requirement is once idoc file is processed archive the Idoc file from INBOX folder to 850_ARCHIVE folder on Application Server itself and NOT delete the file.
We have suggested that
Our Approach: As FTP is already in place, FTP the the files from EDI Substem to R/3 (INBOX) as well as on ARCHIVE folder even before IDOCs are processed so as to make sure Archival process is in place.
Client's Approach: Client suggests to Archival be handled from SAP and NOT through FTP.
Keeping performance and architecture in view kindly suggest which will the right approach.
Is it good to handle it from FTP / SAP !?
Or is there any other better approach to handle this!!? Please advice !!!!
Similarly Archival is required in case of Outbound as well for (810) !! suggestions appreciated !!
Thanks in advance,
Ramesh.
Edited by: Ramesh Kajuru on Aug 5, 2010 3:43 AM
Edited by: Ramesh Kajuru on Aug 5, 2010 5:45 AM
Edited by: Thomas Zloch on Aug 5, 2010 12:50 PM

Ramesh,
the client approch will be best and he will know which files are processed sucessfully.
if I remember correctly there is an FM which will do the same job as the program(I hope you can find with in the standard code).
call that FM in your Z program and read file 1 by 1 and once FM executed sucessfully move the file to archive directory.
IDOC_INBOUND_FROM_FILE. This is the FM I am refering. if still find the delete file code in this make a copy of it and remove that logic.
Regds,
Edited by: Suresh Reddy Avutu on Aug 5, 2010 2:26 PM

TSW Nomination Status codes

Hi,
In case of TSW Nominations items, there are 3 status active, inactive and deactive. The active and inactive status is stored in table OIJNOMST.
But is it possble to get the Deactivated status for a particluar nomination item by means of some function module table, etc???
Any pointers would be helpful.
Regards,
Mansi

Statuses of IDOCs---
See table TEDS1 for all status codes via SE16 in SAP. Outbound ALE Status Codes
Successful Transmission:
03 - Successful outbound transmission
12 - Dispatch OK
IDoc being processed:
01 - IDoc created
30 - IDoc ready for dispatch (ALE service) (Program RSEOUT00 needs to be executed)
ALE Error Messages:
02 - Error passing data to port
04 - Error within control information on EDI subsystem
05 - Error during translation
25 - Processing despite syntax errors (outbound)
29 - Error in ALE service
32 - Resubmit edited intermediate document (DO NOT USE)
Syntax Error Messages:
26 - Error during syntax check of IDoc (outbound) Inbound ALE Status Codes
IDoc Processed Successfully:
50 - IDoc added
53 - Successful posting
IDoc ready for processing:
64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.
Errors in IDoc Processing:
51 - Error - application document not posted
56 - IDoc with errors added (You should never see this error code)
60 - Error during syntax check of IDoc (inbound)
61 - Processing despite syntax error (inbound)
63 - Error passing IDoc to application
65 - Error in ALE service - indicates partner profiles are incorrect
69 - IDoc was edited
Reward points if useful.

Monitoring inbound processing and Sync/ Async communication on PI7.11

Hi All,
I am new to PI. We have following two requirements to be done on PI 7.11
1)     Monitoring inbound processing (Txn Code SWF_INB_MON)
2)     Monitoring Sync/ Async communication (Txn Code SXMS_SAMON)
Kindly let me know how should I proceed or what document should I follow or any scenario is to be configured.

Hi,
    1. Start inbound processing monitoring with transaction SWF_INB_MON or SWF_INB_ADM.
           Note that you require administrator authorization for transaction SWF_INB_ADM
    2. You can monitor the throughput of the inbound processing either on the basis of individual process system or system-wide. In this way you can display the throughput figures in any discrete time range, right down to seconds. A similar display for message packages allows you to monitor inbound processing with the same detail."
     3. You can display runtime information about individual messages, for example, the total runtime of a message in inbound processing or just the runtime of a specific section of the inbound processing. For monitoring individual messages click on "Display Message Packages".
regards,
ganesh.

Recommended Status Codes usage for Inbound & Outbound IDocs

Hi,
Can someone tell what status codes do we use when we go for a Custom Posting Program or Selection Program?
I assume we use 51 for Posting Program (not 56) and
26 for a Z-Selection Program (Not 37 or any other Code).
Please let me know what is recommended and which status codes most of the people use while Custom Development.
Thanks and Regards,
Venkat.

Hi,
Outbound IDOC Status Codes
The following table describes outbound IDOC status codes that generate Tivoli Enterprise Console events:
Outbound IDOCs
Code Error Event Severity SAP Meaning
02 Yes Error Error passing data to port
03 No Error if transaction SM58 indicates an RFC transmission error Data pass to port OK
04 Yes Error Control information of EDI subsystem
05 Yes Error Translation
06 No Harmless Translation
07 Yes Error Syntax check
08 No Harmless Syntax check
09 Yes Error Interchange handling
10 No Harmless Interchange handling
11 Yes Error Dispatch
12, 13, 14 No Harmless OK
15 Yes Warning Interchange acknowledgement negative
16 No Harmless Functional acknowledgement
17 Yes Warning Functional acknowledgement negative
18 No Harmless Triggering EDI subsystem
20 Yes Error Triggering EDI subsystem
22 No Harmless Dispatch OK, acknowledgement still due
23 Yes Error Retransmission
24 No Harmless Control information of EDI subsystem
25 Yes Warning Processing despite syntax error
26 Yes Error Syntax check
27 Yes Error ALE error
29 Yes Error Error in ALE services
30 No Harmless Ready for dispatch (ALE)
31 No Harmless IDOC is marked for deletion
33 No Harmless Original of an IDOC which was edited
34 Yes Error Error in control record of IDOC
36 Yes Error Timeout error; electronic signature not performed
37 Yes Error IDOC added incorrectly
38 No Harmless IDOC archived
39 No Harmless Receive confirmed
40 Yes Error Application document not created in target system
41 No Harmless Application document created in target document
Inbound IDOC Status Codes
The following table describes the inbound IDOC status codes that generate Tivoli Enterprise Console events:
Inbound IDOCs
Code Error Event Severity SAP Meaning
51, 52 Yes Error Posting error
53 No Harmless Posting successful
54 Yes Error Error during formal application check
55 No Harmless Formal application check
56 Yes Error IDOC with error added
60 Yes Error Syntax error
61 Yes Warning Processing despite syntax error
62 No Harmless IDOC passed to application
63 Yes Error Error passing IDOC to application
64 No Harmless IDOC ready to be passed to application
65 Yes Error ALE error
68 No Harmless IDOC is marked for deletion
70 No Harmless Original of an IDOC which was edited
73 No Harmless IDOC archived
Regards,
Raj.

Outbound IDoc Error: Status Code 37 'Sender Port' is invalid

Hi
I have an Error when the Outbound IDoc is triggered.
It shows that 'Sender Port in Control Record is invalid'.
Status Code: 37.
I know that there are some issues with the Sender Port Definition.
Please help me out to solve this problem using some checkpoints at each and every step.
Reward Points Assured.
Regards,
Baburaj

Hi Baburaj Manickam
Good
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
Good Luck and Reward me for the same
Thanks
Ashok.N

WE-19 Inbound Idoc Process - Status Code 51

Hi,
I generated Outbound idoc COND_A successfully to send it out to XI. I used same Idoc again in WE19 and changed partner details and tried Inbound Processing. Its giving me error code 51 ("ISO Currency USD can not be converted unambiguously to SAP currency for E1KOMG" )
Any Idea how to fix this error. basically I did not changed anything.
Message was edited by: Ram Krish

Appana,
Thank you very much for your reply.
I did setup all parameters as Iam getting this Idoc as an Inbound to R3 as well. Thsi Idoc will be both Outbound and Inbound to R3.
I successfully sent this Idoc to XI. and then as I wanted to test the same Idoc for inbound, I changed Paramters according to my setup.
Sequence of status are
74 - created with test transaction
50 - Idoc added
64 - Idoc ready to be transferred to Application
62 - Idoc Passed to Application
51 - ISO currency USD can not be converted unambiguously to SAP currency for KOMG
I looked at several fields in E1KOMG segment and changed one of the currency field to USD which didn't help to fix this error.
I really appreciate any help to fix this error.

Inbound IDOC error - status code 52- application document not fully posted

Hi,
In Inbound IDOC, the status code is 52 ---> Application document is not fully posted(satus of the inbound idoc is in yello colour). I want to reprocess this idoc in BD87 t.code in order to convert the yellow colour to green colour. Before reprocessing the IDOC, i need to rectify the problem and then reprocess the idoc in bd87. am i correct? if yes, what i need to do to solve the error --->application document not fully posted. Please guide me friends.
Thanks in advance.
Regards,
Sri

HI
If you are FM to process the inbound IDOC,
possibilities are like below .
Reason 1 :
In partner profiles, check is it trigger immediately or not ? for particular partner profile which u r using .
reason 2 :
If you are using BDC code to update the data .if any screen contains error then also you will get the status in yellow .
reason 3 :
Have you tried with TCODE BD87 , might be it is processing error also .
i have worked on same probelm so if u r not solved with the issue after trying above 3 reasons .
reply me back .

IDOC Status code 56 !!

Hi Friends,
 I am getting status code 56 for an Inbound IDOC. I have defined the partner profile for the Legacy system. Still I am getting status 56 with the following description.
Text
 EDI: Partner profile inbound not available
 Diagnosis
 An inbound partner profile could not be found with the following key:
 /DEVCLNT900/LS//FKK_EBS_TOI_COPA////
 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.
Thank U for Ur time.
Senthil

Hi Senthil,
Here is the procedure to test.
Create segments WE31
Create IDOC types using segments in: WE30 (BASIC type)
Create Message type: WE81
now link between message type and basic type: WE82
create process codes: WE42
now link process codes to direction of delivery inbox or outbox with messege type: WE64.
make an entry of your FM in: BD51
now link between FM, Basic TYpe, Messg.Type: WE57.
create port: WE21
create partner profile: WE20
 partner no.: SAP_DEV
 partn.type: LS
 Under Post processing:
 type: US
 agent: name of agent
 lang.: EN
 outbound partrs.
 message type:---
 Inbound partnrs.
 message type:ZLOCAL_STAFF / HRMD_A
 under Classification:
 partner class: ALE
 partn.status: A
 Message type: ZLOCAL_STAFF
Hope this helps.
Regards,
Vivek
<<removed_by_moderator>>
Edited by: Vijay Babu Dudla on May 19, 2009 7:09 AM

37 Status code in IDoc to File Scenario

Hi Experts,
I developed Idoc to file scenario, in the PI side all the design time and configuration objects are good .
while I am testing from SAP backend system (All required configuration steps are also good).
I was send the Vendor information details (CREMAS05) by using the Transaction code WE19 , after that I was test with IDoc list by using Transaction code WE05(IDoc list) I am getting status code 37 . what might be the problem.
please help me.
Thanks in advance,
Regards,
Sudeepth.

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

Outbound Status in the Monitor

In SXMB_MONI when i check for messags status there are several messages struck with Outbound status = Message Scheduled on outbound status
MY scenario is Idoc - XI/BPM - File . I'm collecting all Idocs in BPM before sending out to file.
Any idea what I have to do.
I did checked in SMQ2 and all queues are empty now.
Thankx

Did you check all the steps in BPM during runtime ? Is all the steps are showing green in the Graphical View of workflow instance.. I think some of the steps are having problem..
Also which collectPattern you used in the design ? Is the end condition is satisfied ?
Go to Transaction SWEQADM ( to check if the event queue background job is running.
If everything looks ok, test the syntax for the BPM in the Repsotiory, re-import into the directory and re-run the scenario..
If it goes into qRFC monitor when you click on PE in SXMB_MONI, then I think BPM is not triggered ..
Check did you configure correct Receiver Determinations ?
i.e Idoc ->BPM
BPM->Target
Also test with one idoc first..Also make sure that Idoc data is coming to XI correctly. Check the Sender Interface, Sender Service, Reciever Interface and Service in SXMB_MONI so that you can understand which is message has come to integration server etc..
Regards,
Moorthy

Inbound IDOC Mass processing - No status message

Hi Friends,
I am updating a database table using inbound IDOC. But in batch job when XI passes multiple IDOCS,
for some IDOCs there is no status message even though i coded for status message.
If i rerun IDOC in BD87 then it work fine.
please help.
regards,
madan

Hi Madan,
Since you are loading multiple idoc to the system due to high load in the production system data is not commiting properly. So use external commit work statement in you code. this will reduce the performance but logic will work.
COMMIT WORK [AND WAIT].
Effect
The statement COMMIT WORK completes the current SAP LUW and opens a new one, storing all change requests for the current SAP LUW in the process. In this case, COMMIT WORK performs the following actions:
It executes all subroutines registered using PERFORM ON COMMIT.
The sequence is based on the order of registration or according to the priority specified using the LEVEL addition. Execution of the following statements is not permitted in a subroutine of this type:
PERFORM ... ON COMMIT|ROLLBACK
COMMIT WORK
ROLLBACK WORK
The statement CALL FUNCTION ... IN UPDATE TASK can be executed.
Triggering an internal event for the Persistence Service of the Object Services.
If event handlers are registered by the Persistence Service, these collect the changes to the objects managed by the Persistence Service and transfer them via CALL FUNCTION ... IN UPDATE TASK to a specific update function module that is registered as the last update module.
This executes all high-priority (VB1) update function modules in the order of their registration and in a common database LUW. If you do not specify the addition AND WAIT, the program does not wait until the update work process has executed it (asynchronous updating), but instead is resumed immediately after COMMIT WORK. However, if the addition AND WAIT is specified, program processing after COMMIT WORK will not continue until the update work process has executed the high-priority update function modules (synchronous updating).
When all high-priority update function modules are completed successfully, the statement executes the low-priority (VB2) update function modules in the order of registration together in a common database LUW.
After the execution of high-priority update function modules, the individual function modules registered using CALL FUNCTION ...IN BACKGROUND TASK|UNIT are executed in a separate database LUW for each destination.
Within an update function module started using COMMIT WORK, the execution of statements that lead to a database commit is not permitted. In particular, the following are forbidden:
Thanks,
Raghav

ALE/Idoc (inbound & outbound)

Hi,
Can any one help me by providing simple sample code for creation of ALE/Idoc (inbound & outbound). Where I need do understand flow cycling of outbound from one client to other inbound client. Waiting for replay. My email-ID is [email protected]
Regards,
Lokesh.K

Hi,
have you seen these documentation sections?
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/78/2174b051ce11d189570000e829fbbd/frameset.htm">Implementing Inbound Processing</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/78/2177bc51ce11d189570000e829fbbd/frameset.htm">Implementing Outbound Processing</a>
Hope they'll help.

IDOC(Inbound/Outbound) - SAP(ABAP)

Hi Everybody,
i m new to iDOC programing .I know to create logical sytem,rfc destination,port, partner profile ,idoctype,messagetype integration idoctype into msgtyp but i don't know hw to develop program for both creation of outbound idoc and inbound idoc.Could u guide me with small example of each one .
i m waiting for ur reply...........
Thx and Regds in Adv.
Prabhas

Hi Prabhas,
Check the following sample FMs:
IDOC_INPUT_ORDERS
IDOC_OUTPUT_ORDERS
Check the Tcode WE41 & WE42 to find the FM attached to the Process code.
For BAPI programming Tcode - BAPI
BAPI programming guide:
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
BAPI user guide:
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
For creating a RFC - SE37
RFC is a remote-enabled Function Module.
Create a function module with attributes Remote-enabled.
RFC programming in ABAP:
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf
hope this helps!
best regards,
Thangesh

Idoc Monitoring (Inbound & Outbound Status codes)

Similar Messages

Maybe you are looking for