IDOC no

MSG Type
Partner Number

Status of IDOC - check under we02

KU - Customer
Direction - 2 (Inbound)
Message Type - defines structure of an IDOC
Basic Type - version of the msg type used
Extension - To add additional fields in the standard msg type (if business insists)
Its basically customizing the Basic msg type.

Control Record - defines envelope of IDOC

IDOC in SAP is used to transfer data only.
Logical System - is client

port details of receipient indicates where exactly the order is getting posted.

Status: 1-50 is for Outbound

and 51-

64, 30 and 03 - imp status of IDOCS

Status 64 - the Inbound IDOC is not processed

EASSO - Europe

Message Type -> Logical message

To search IDOC number from ICN number

we02 - EDI - Transfer File reference (Interchange Control Number)
date - you can find from Webmethod

outbound - 03, 06 and 30 status are imp

06 - Successfully Processed by Webmethods

SAP - SAP Queue (Transactional RFc Queue)

/nsm58 - to check the status of IDOCs in Queue (Transactional RFC)

Filter data based on date and timestamp
Now to check the specific IDOC, retrieve the transaction ID from IDOC
Go to we02 - open IDOC - double click status 30 and go to Sts Tab
you will find the Transaction Id under parameter 1 only for failed cases.

--> Retrieve Transaction ID from IDOC (we02) and search in sm58 record.

B408

IDOC status 64 - Inbound IDOC is created and is waiting to be processed (due to

some error/missing values)

To check if any background jobs are running because of which the status is stuck
in status 64
Go to /owe20 - KU - Search your partner
Under Inbound Parameters, you can find if the IDOC is being triggered by a
background job.
To identify the background Job use tcode z799
Enter Variant - RBDAPP01 and execute
Search your Partner and if you get more than one entry, look for your doc type
under these
 Copy the Job name - Ex: ZRBDAP_RO50STK
say Ctrl+Y, Ctrl+C and Ctrl+V and search in sm37

Tcode - sm37 - to check job status

Enter Job name and under user name - *
Select the Date, since when IDOC has been failing/is created
If the status of Job is Finished, it is running as expected.

Note - If a Job in sm37 executes for > 2 mins, it must be reported.

As the job is successful, check if there is any data issue

look for user - EOD_CCP
(To find the username, you can find a successful idoc and check whats the next
status after 64. Identif user)
Double click against the various dumps and errors
Search IDOC_DATA there and look for your IDOC - see details of your error.
Error - ConvT_No_Number (trying to convert infinity into a number)
Now go to your data/IDOC and find where is infinity
for this, go to IDOC- SAY print IDOC - FIND Infinity