How to trace an idoc

Hi
I want to trace an outbound iDoc after triggering. Can anyone tell
the steps what I have to take?
Regards
Praveen

Hi,
As you want to trace your outbound idoc, you might have triggered that outbound idoc from an document with the help of output, then open the document and check the output at the header level and you will find your EDI output in that document.
Select that output and click the processing log and you will get your idoc number. Take that idoc number and execute the transaction WE02 and give your idoc number and remove the dates and you can see your idoc. Check the status records of the idoc and you will know where your idoc is currently.
Thanks,
Mahesh.

Similar Messages

How to trace a idoc

Hi Experts,
Can i trace a idoc in SAP.
In the current scenario,idoc file is created when so ever invoice is generated in sap and then it is saved at a destination folder.
Is there any way by which i can check which Idoc has been created for a particular invoice and can i open the idoc file from SAp and save it on my system as xml file.
Thanks in advance
Abhishek

Hi
Try BDM2 transaction.
Regards
Deepa

How to trace an Inbound R3 IDoc by seeing application document

Hi all,
How to trace an Inbound IDoc number by seeing application document in R3.
sometimes 'Services from object' also we could'nt able to trace out the IDoc.
'Services from object' option sometimes appears in blank status with no IDoc.
Any possible tracing options?

HI Chitra,
You can findout the Idoc number in R/3 System by using the tr.code WE05 or WE02.
Go throgh the following blog for message monitoring.
/people/alessandro.guarneri/blog/2006/02/14/super-message-monitor-for-sap-xi
Regards
Goli Sridhar

How to trace idoc in receiving system

Hi
We are sending an idoc from solution manager to an SAP system. I have the idoc number in the solution manger.
Using this, how can we trace this idoc in the receiving system?
Many Thanks
Sridhar

hi!
Define the logical system names in both the systems.
Logical system names :SAP001
SAP002
SAP001 FOR 001 CLIENT
SAP002 FOR 002 CLIENT
These two logical system definitions should be present in both the systems.
Assign the logical systems to the client. (in both the systems)
Assign SAP001 to 001 CLIENT
Assign SAP002 to 002 CLIENT
you can See these in transaction SALE.
After this define the rfc DESTINATION IN sm59. (in both the systems)
In 001 client create the RFC destination name SAP002
In the tab log on security, give the user name and password and client of the 002 client and save it.
Similarly do the reverse in the 002 Client.
In 001 client create the port.(Transaction WE21)
Specify the RFC destination name as SAP002.
Now you can define the ports, (both the systems)
Create the partner profile for partner(ie gve logical system name of partner) , so give as SAP002.
partner profile in both the systems.
Now create the distribution model in BD64 and goto edit>model view>distribute.
The same model view will be visible n distributed to the partner system also..which in this case is sap002.
U may trigger the idoc from we19 and chk its status in we05.
try if it helps n kindly reward points.

How to Read an IDOC

Hi Experts,
Can any one explain me about IDOC, and how to read it once it is created.
Regards
Venu

Hi,
IDOCS:
IDocs are SAPs file format to exchange data with a foreign system.
IDocs are an ASCII file format to exchange data between computers; the format is chosen arbitrarily .
IDocs are similar to segmented files; they are not a description language like ANSI X.12, EDIFACT or XML.
The IDoc contents are processed by function modules, which can be assigned in customizing.
IDocs are structured ASCII files (or a virtual equivalent). They are the file format used by SAP R/3 to exchange data with foreign systems.
IDocs are simple ASCII data streams. When they are stored to a disk file, the IDocs
are simple flat files with lines of text, where the lines are structured into data fields.
The typical structured file has records, each record starting with a leading string that identifies the record type. Their specification is stored in the data dictionary.
IDocs is the acronym for Interchange Document. This indicates a set of (electronic)
information which builds a logical entity. An IDoc is e.g. all the data of a single
customer in your customer master data file, or the IDoc is all the data of a single
invoice.
IDoc data is usually exchanged between systems and partners that are completely
independent. Therefore, the data should be transmitted in a format that can easily be
corrected by the computer operators. It is therefore mandatory to post the data in a
human readable form.
Nowadays, this means that data is coded in ASCII format, including numbers which
are sent as a string of figures 0 to 9. Such data can easily be read with any text editor on any computer, be it a PC, Macintosh, UNIX System, S/390 or any internet
browser.
The information which is exchanged by IDocs is called a message and the IDoc is
the physical representation of such a message. The name messages for the
information sent via IDocs is used in the same ways as other EDI standards. .
Everybody who has ever dealt with interface programming, will find IDocs very
much like the hierarchical data files used in traditional data exchange.
International standards like the ODETTE or VDA formats are designed in the same
way as IDocs are.
Other EDI standards like XML, ANSI X.12 or EDIFACT/UN are based on a data
description language. They differ principally from the IDocs concept, because they
use a programming language syntax (e.g. like Postscript or HTML) to embed the DATA.
The IDoc process is a straight forward communication scenario. A communication is
requested, then data is retrieved, wrapped and sent to the destination in a predefined format and envelope.
An R/3 application creates data and updates the database appropriately. An
application can be a transaction, a stand-alone ABAP Report or any tool that can
update a database within R/3.
If the application thinks that data needs to be distributed to a foreign system, it
triggers the IDoc mechanism, usually by leaving a descriptive message record in the
message table NAST.
The application then either directly calls the IDoc engine or a collector job
eventually picks up all due IDoc messages and determines what to do with them.
If the engine believes that data is ready to be sent to a partner system, then it
determines the function module which can collect and wrap the required IDoc data
into an IDoc.
In IDoc customising, you specify the name of the function module to use. This can
either be one which is predefined by R/3 standard or a user-written one.
When the IDoc is created it is stored in an R/3 table and from there it is sent to the foreign system.
If the foreign system requires a special conversion, e.g. to XML, EDIFACT or X.12
then this job needs to be done by an external converter, like the Seeburger ELKE
system. These converters are not part of R/3.
If you have to decide on a converter solution, we strongly recommend using a plain
PC based solution. Conversion usually requires a lot of fine tuning which stands
and falls with the quality of the provided tools.
DIFFERENCE B/W IDOC AND BDC:
IDOC's are intermediary documents into which the data will be transferred and then this idoc's gets transferred to sap or non-sap system.
ALE is used to create link between 2 systems. So without the linking the data cannot be uploaded or downloaded.
BAPI, LSMW and BDC are used to transfer data b/w systems.
BDC is used to transfer data b/w only sap systems.
LSMW is used to transfer data b/w sap and non-sap systems.
ale Idoc: Idoc is a part of ALE. it is applicable only if the external system and the sending system have the same format. ALE uses Internationally Standardized formats. Also it is facilitating Asynchronous data communication and safest data communication. If you got errors also you can correct it and send it again.
lsmw: It the legacy data transfer. which is used for bulk data transfers. It uses BAPI, IDoc, BDc internally....
bapi: SAP Provided way of data transfer. if the BAPi suits for our business bettere to go for bapi. it too uses internationally standardized data format Business Objects concept.
idocs
1.We will see the status of the IDOC in We02 or We05.
2.In that There are three records.
a.Data record
b.status record.
c.Control record.
3.If u click on data record you can see the data ,which is transfering it.
Details about IDOC:
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
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
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
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
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
http://sap-img.com/abap/reads-an-existing-idoc-and-dispays-the-contents-in-a-spreadsheet-format.htm
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
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
IDOC Creation....
http://www.erpgenie.com/sap/sapedi/idoc_abap.htm
You can view the definition of any IDoc data structure directly with transaction WE30.
u cn use function module 'FIELD_POSITION_IN_SEGMENT_GET' to extract data from idocs.
You can view the idoc through we02 or we05. In that there are three types
status records gives the status of that idoc in differenttimes
data records gives the data in that idoc
control records gives the date, time and creater of that idoc.
I think its helps you.
Thanks and Regards,
D.Revathi.

Dataloss in network... How to trace it..?

Hi,
Though this question is related to SAP XI and SMICM trace, I feel this question can also be answered by people in WebAs General, so i am posting this in this forum.
In my current scenario where SAP XI system pushes data to another system(ABC system) using HTTPS connection. I have set up an RFC destination of Type G to connect to the external system.
When i do a Test connection, i see in SMICM log file, i found that connection established, request message written into ABC system.When response is being written i could find BINDUMP of content denied in the SMICM log file. What does that exactly mean..?
Also When i contacted the other party--ABC, they have told that they could not see any messages in their system.
XI shows successfully processed and ABC system did not receive the message... So where did the data go?? I have no clue :-(( Need your inputs in this regard. How to trace if the message has been successfully posted by XI. Below is the SMICM log file.
[Thr 5880] IcmConnConnect: direct connect to www2.ABC.com:443
[Thr 5880] nihsl-getHostAddr: found hostname '.www2.ABC.com' in cache
[Thr 5880] nihsi-getHostAddr: hostname '.www2.ABC.com' = addr 16.256.48.91
[Thr 5880] nihsi-getServNo: servicename '443' = port 01.BB/0443
[Thr 5880] NiCreateHandle: state hdl 23 / socket -1 NI_INITIAL
[Thr 5880] NiIBlockMode: switch off block-mode for hdl 23 / socket -1
[Thr 5880] NiLowLevCon: connect to: host 16.256.48.91, port 01.BB/0443, fam 2 (low adr..high adr)
[Thr 4532] [Thr 4532] NiISelect: fds in write-mask: [Thr 5880] NiIInitSocket: set default settings for socket 65268
[Thr 5880] NiISocket: hdl 23 got socket 65268
[Thr 5880] NiPBlockMode: set socket 65268 to NONBLOCK mode
[Thr 4532]
[Thr 5880] NiPConnect: connect in progress
[Thr 5880] SiPeekPendConn: connection of socket 65268 established
[Thr 5880] NiLowLevCon: took local port 10.1B/4123
[Thr 5880] nilh-localCheck: using local address list
[Thr 5880] NiSetStat: state hdl 23 NI_CONNECTED
[Thr 5880] ->> SapSSLSessionInit(&sssl_hdl=015BC3DC, role=1 (CLIENT), auth_type=3 (USE_CLIENT_CERT))
[Thr 5880] <<- SapSSLSessionInit()==SAP_O_K
[Thr 5880] in: args = "role=1 (CLIENT), auth_type=3 (USE_CLIENT_CERT)"
[Thr 5880] out: sssl_hdl = 19193D20
[Thr 5880] ->> SapSSLSetNiHdl(sssl_hdl=19193D20, ni_hdl=23)
[Thr 5880] IcmPlCheckRetVal: Next status: WRITE_REQUEST(3)
[Thr 5880] IcmConnRollInWP: no need to roll in WP status: ROLLED IN
[Thr 5880] MPI<12ee>0#7 GetInbuf 5 1489e0 2179 (1) -> 6
[Thr 5880] NiPBlockMode: set socket 65268 to NONBLOCK mode
[Thr 5880] NiPSockGetStatus: socket 65268 ok, no data pending
[Thr 5880] NiPBlockMode: set socket 65268 to BLOCK mode
[Thr 5880] IcmReadFromPartner(id=0/4693): fe-nihdl timeout
[Thr 5880] PlugInHandleServData: role: 2, status: 3, content-length: 0/0
buf_len: 2127, buf_offset: 0, buf_status: 6
[Thr 5880] HttpParseRequestHeader: content length: 1805
[Thr 5880] HttpParseRequestHeader: no transfer-encoding set
[Thr 5880] HttpParseRequestHeader: Version: 1000
[Thr 5880] HttpParseRequestHeader: Keep-Alive: 0
[Thr 5880] IcmPlCheckRetVal: Next status: READ_RESPONSE(2)
[Thr 5880] IcmHandleNetWrite(id=0/4693): HandleServData returned: 2
[Thr 5880] BINDUMP of content denied
[Thr 5880] IcmWriteToConn(id=0/4693): prepared to write data to partner (len = 2127)
[Thr 5880] ->> SapSSLWrite(sssl_hdl=19193D20, buf=061F8A74, len=2127, timeout=2000, &writelen=123EFF24)
[Thr 5880] <<- SapSSLWrite(sssl_hdl=19193D20)==SAP_O_K
[Thr 5880] result = "written= 2127 of 2127 (all)"
[Thr 5880] IcmWriteToConn(id=0/4693): wrote data to partner (len = 2127)
[Thr 5880] MPI<12ee>0#8 FreeInbuf#1 0 1489e0 0 -> 0
[Thr 5880] IcmConnRollInWP: no need to roll in WP status: ROLLED IN
[Thr 5880] IcmReadFromConn(id=0/4693): request new MPI (0/0)
[Thr 5880] MPI<12ed>1#4 GetOutbuf -1 1489e0 65536 (0) -> 061F8A40 0
[Thr 5880] ->> SapSSLRead(sssl_hdl=19193D20, buf=061F8A74, maxlen=65483, timeout=500, &readlen=123EFEE8)
[Thr 5880] Fri Dec 02 08:59:10 2005
[Thr 5880] <<- SapSSLRead(sssl_hdl=19193D20)==SAP_O_K
[Thr 5880] result = "max=65483, received=8036"
[Thr 5880] IcmReadFromConn(id=0/4693): read 8036 bytes(timeout 500)
[Thr 5880] BINDUMP of content denied
[Thr 5880] PlugInHandleNetData: role: 2, status: 1, content-length: 0/-1
buf_len: 8036, buf_offset: 0, buf_status: 0
[Thr 5880] PlugInHandleNetData: read response header
[Thr 5880] HttpParseResponseHeader: no transfer-encoding set
[Thr 5880] HttpParseResponseHeader: Version: 1000
[Thr 5880] HttpParseResponseHeader: Keep-Alive: 0
[Thr 5880] PlugInHandleNetData: more data to read
[Thr 5880] PlugInHandleNetData: need more data (7936/12484)
[Thr 5880] IcmPlCheckRetVal: Next status: READ_RESPONSE(2)
[Thr 5880] IcmHandleNetRead(id=0/4693): read_len: 8036, HandleNetData returned: 2
[Thr 5880] IcmHandleNetRead(id=0/4693): status 2 -> 2
[Thr 5880] ->> SapSSLReadPending(sssl_hdl=19193D20, &pendlen=123EFF1C)
[Thr 5880] <<- SapSSLReadPending(sssl_hdl=19193D20)==SAP_O_K
[Thr 5880] out: pendlen = 0
[Thr 5880] IcmHandleNetRead(id=0/4693): pending SSL data: 0, rollout=1
[Thr 5880] nihsl-getHostAddr: found hostname 'localhost' in cache
[Thr 5880] nihsi-getHostAddr: hostname 'localhost' = addr 127.0.0.1
[Thr 5880] NiIDgSend: re-connect dgram to: host 127.0.0.1, port FD.E6/64998, fam 2 (low adr..high adr)
[Thr 5880] IcmConnRollOut: connection (id=0/4693) rolled out:
[Thr 5880] CONNECTION (id=0/4693):
used: 1, role: 2, stateful: 0
NI_HDL: 23, protocol: 2
host: www2.ABC.com:443
status: READ_RESPONSE
connect time: 02.12.2005 08:59:08
WP-status: ROLLED IN (Context: 0, Role: 2)
tid: 15, mode: 0, uid: 746, roll-reason: ICM_ROLL_NONE
MPI request: <12ee> MPI response: <12ed>
request_buf_size: 2127 response_buf_size: 65484
request_buf_used: 2127 response_buf_used: 8036
request_buf_offset: 0 response_buf_offset: 0
[Thr 4852] NiBufSelect: Postprocessing...
[Thr 4852] NiBufSelect: returning 1 clients
[Thr 4852] NiSelNext: returning hdl 5, r--, 00000000, rest 0 entries (0164FEF0)
[Thr 5880] IcmWorkerThread: Thread 6: Waiting for event
[Thr 4852] NiIPeek: peek successful for hdl -1 / socket 65588 (r)
[Thr 4852] NiIDgReceive - WAKEUP DGRAM received from:
host 127.0.0.1, port 07.B0/1968, fam 2 (low adr..high adr)
[Thr 4852] NiIPeek: peek for hdl -1 / socket 65588 timed out (r; 0)
[Thr 4852] IcmWatchDogThread: dg received
[Thr 4852] IcmWatchDogUpdateRollQueue(id=0/4693): insert fe-nihdl 23, flags=1
[Thr 4852] NiSelSet: hdl 23, r-, 01679D50
[Thr 4852] IcmWatchDogThread: check ni handles (timeout=10000)
[Thr 4852] NiBufSelect: Preprocessing...
[Thr 4852] NiISelect: timeout 10000 ms
[Thr 4852] NiISelect: maximum fd=65757
[Thr 4852] NiISelect: fds in read-mask: [Thr 4852]
[Thr 4852] NiISelect: fds in write-mask: [Thr 4852]
[Thr 4852] NiBufSelect: Postprocessing...
[Thr 4852] NiBufSelect: returning 1 clients
[Thr 4852] NiSelNext: returning hdl 23, r--, 01679D50, rest 0 entries (0164FF00)
[Thr 4852] IcmWatchDogThread(id=0/4693): nihdl 23 - data received(read)
[Thr 4852] NiSelClear: removed hdl 23 from selectset
[Thr 4852] IcmQueueAppend: Queuelen: 1
[Thr 4852] IcmCreateRequest: Appended request 8369
[Thr 4852] IcmConnRollIn: connection (id=0/4693) rolled back to status: READ_RESPONSE
[Thr 4852] IcmWatchDogThread: check ni handles (timeout=10000)
[Thr 4852] NiBufSelect: Preprocessing...
[Thr 4852] NiISelect: timeout 10000 ms
[Thr 4852] NiISelect: maximum fd=65757
[Thr 4852] NiISelect: fds in read-mask: [Thr 4152] IcmWorkerThread: worker 3 got the semaphore
[Thr 4152] REQUEST:
Type: READ_RESPONSE Index = 8368
[Thr 4152] CONNECTION (id=0/4693):
used: 1, role: 2, stateful: 0
NI_HDL: 23, protocol: 2
host: www2.ABC.com:443
status: READ_RESPONSE
connect time: 02.12.2005 08:59:08
WP-status: ROLLED IN (Context: 0, Role: 2)
tid: 15, mode: 0, uid: 746, roll-reason: ICM_ROLL_NONE
MPI request: <12ee> MPI response: <12ed>
request_buf_size: 2127 response_buf_size: 65484
request_buf_used: 2127 response_buf_used: 8036
request_buf_offset: 0 response_buf_offset: 0
[Thr 4152] ->> SapSSLRead(sssl_hdl=19193D20, buf=061FA9D8, maxlen=57447, timeout=500, &readlen=10BEFEE8)
[Thr 4852]
[Thr 4852] NiISelect: fds in write-mask: [Thr 4852]
[Thr 4152] <<- SapSSLRead(sssl_hdl=19193D20)==SAP_O_K
[Thr 4152] result = "max=57447, received=4548"
[Thr 4152] IcmReadFromConn(id=0/4693): read 12584 bytes(timeout 500)
[Thr 4152] BINDUMP of content denied
[Thr 4152] PlugInHandleNetData: role: 2, status: 2, content-length: 7936/12484
buf_len: 12584, buf_offset: 8036, buf_status: 0
[Thr 4152] PlugInHandleNetData: read response body (len=12484/12484)
[Thr 4152] PlugInHandleNetData: response completely read(EOS=0)
[Thr 4152] IcmFlushBuf: Flushing 12584 Bytes, buf_status: 6
[Thr 4152] flush buffer with mpi buffer id 1
[Thr 4152] MPI<12ed>1#5 FlushOutbuf l1 1 1 1489e0 12636 6 -> 061F8A20 0
[Thr 4152] IcmConnRollInWP: no need to roll in WP status: ROLLED IN
[Thr 4152] PlugInHandleNetData: close connection
[Thr 4152] IcmPlCheckRetVal: Plugin retval: PLUGIN_RET_CLOSE (-702)
[Thr 4152] IcmHandleNetRead(id=0/4693): read_len: 4548, HandleNetData returned: -702
[Thr 4152] IcmConnRollInWP: no need to roll in WP status: ROLLED IN
[Thr 4152] PlugInStopConn: role: 2, error: 0, write_err: 1
[Thr 4152] ->> SapSSLSessionDone(&sssl_hdl=015BC3DC)
[Thr 4152] <<- SapSSLSessionDone(sssl_hdl=19193D20)==SAP_O_K
[Thr 4152] NiICloseHandle: shutdown and close hdl 23 / socket 65268
[Thr 4152] IcmConnClose: Connection 0/4693 closed
[Thr 4152] IcmConnFreeContext: context 0 released
[Thr 4152] IcmServDecrRefCount: intersrv.afdb.local:443 - serv_ref_count: 1
[Thr 4152] IcmWorkerThread: Thread 3: Waiting for event
Cheers,
Siva Maranani

SMICM with trave level3 is the only way(i know) to trace whether the message has left XI server or not.

How to send vendor IDOC data from SAP R/3 to XI.

Hi experts,
I have developed the IDOC to FILE scenario for Vendor Master Upload. I want to place flat file in local folder with in XI or Outside of XI. (Using NFS or FTP protocol in FILE adapter). My First quesstion is How to setup Folder with in XI ro Out side XI?
And also I want to push the IDOC from SAP r/3 to test the scenario. Both XI and R/3 systems are configured to exchange data.
How to Push Vendor IDOC from SAP R/3 to XI? (we can send XML directly to XI; but the R/3 kernal should be moe than 6.20).
Thanks in Advance.....

Hi,
>>My First quesstion is How to setup Folder with in XI ro Out side XI?
Its a normal way to creation of folders in Os level . u can create the folder in XI Server or on the FTP Server.
ALE Settings
Steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
IDoc-XI-File scenario
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Posting the IDOC from R/3 to XI
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
REgards
Seshagiri

How to trace an error

Dear all,
How to trace a purticular error ?
from metalink
Diagnose the issue by running the following trace
alter system set events '1775 trace name ERRORSTACK level 3';
Redo the import and reproduce the error. The trace file should be in the
USER_DUMP_DEST directory.
alter system set events '1775 trace name errorstack off';
Trace file will show something like the following:
ksedmp: internal or fatal error
ORA-01775: looping chain of synonyms
Current SQL statement for this session:
SELECT COUNT(*) FROM SYS_IMPORT_TABLE_01
I am getting the same ora 01775 error. But when I am tracing, I am not getting any result in my udump. Is there any other setting do I have to make to get the trace file?
Thanks

Your question can not be answered.
Not only you don't include a version (this seems to be too difficult for most posters here), but you also include ambiguous sentences like 'When I am tracing'.
This results in the question 'did you issue the alter system command and was it successful?'
As far as I am aware the syntax is
alter system set events='<errornum> trace name errorstack level 3';
There are no other 'settings'
The only other solution is to set up an afterserver error trigger.
Works like a charm, 8i onwards.
You uncover way too many things you don't even want to know!
Sybrand Bakker
Senior Oracle DBA

How to trace purchase order number with respect to Purchase requestion numb

Hi friends,
Can u please help me how to Trace purchase order number with respect to purchase Requetuion number. Is there any standard report available in R/3

Hi Vamsi,
Thats what!!!
Goto SE16 - EBAN - Give PR number in the iput screen.
In the output screen you will have to do field selection from Menu - Settings - formatlist - choose fields.
There you choose Purchase Order.
So the output will display for you POs for the PR that you entered.
Regards,
Vishal

How to trace production order history

Hi,
how to trace production order history, with all information like some addtion and deletion of components in production order.
I need the history like how we are doing ECM in master data history.
Regards,
S.Suresh.
Edited by: suresh subramanian on Jul 16, 2008 7:31 AM

Dear Suresh,
Please refer the link,[http://help.sap.com/saphelp_46c/helpdata/en/35/ce8d378d0302cae10000009b38f9b7/frameset.htm]
Regards,
R.Brahmankar

How to cancel an idoc in status 64

How to cancel an idoc in status 64

Hi Manju,
If you have table updation access then
Go to SE16 --> Table EDIDC --> Give your "IDoc number" --> change the status from 64 to "73 IDoc archived".
Or you can ask to your ABAPer to do that.
Hope it helps,
Regards,
MT

How to trace a USER in oracle?

Hi Sir,
I have a rquirement that I need to Trace a session created through the Application. The only data I have is that I know the application will connect to a Database schema and nothing else. How is it possilbe that I can create a trace file for it.
Also is it possilble, that i can trace complete user. how to find all the trace as it create number of process inturn number of trace, how do I find it and combine. I read the documentation but can't understand it clearly?
Any help will be great.

sanora600 wrote:
Aman, thanks for replying. This is the problem, they have not implemented dbms_application_info.
That is the reason I want to know how to trace user(all session of a schema) and combine all the session generated trace(something like trcsess) and then generate tkprof. I am on Oracle 10g.Well, first off, users connect to databases, they don't connect to schemas. And as a follow on, users have sessions, schemas don't.
That said, you might investigate a logon trigger that initiates a 1046 trace. Something like this:
-- create a logon trigger for capturing extended trace data
-- NOTE: must be run as SYS
-- NOTE: Be sure to change both occurances of the target username
-- ('user = xxx' and 'TRACEFILE_IDENTIFIER=') to the
-- correct value for the session you want to trace.
create or replace trigger logon_trigger
after logon on database
begin
if (user = 'SCOTT' ) then
execute immediate 'ALTER SESSION SET TRACEFILE_IDENTIFIER=''SCOTT_APP''';
execute immediate 'alter session set timed_statistics=true';
execute immediate 'ALTER SESSION SET EVENTS ''10046 TRACE NAME CONTEXT FOREVER, LEVEL 12''';
end if;
exception
when others then
null;
end;
end;
Of course, you can play around with the 'if' condition, and delete or disable the trigger when it is no longer needed. The resulting trace file can be run through tkprof.
Edited by: EdStevens on Dec 19, 2008 9:03 AM

How to Trigger an IDOC from SAP R/3 to two systems at a time

Hi experts,
Can any one please tell me How to Trigger an IDOC from SAP R/3 to two XI systems at a time.
My current production R/3 system sends a DELVRY03 IDOC to Production XI system ( Name : XIP) .
I would like to route the same IDOC from production R/3 system to my Quality XI System ( Name XIQ) .
Problem is production R/3 system triggers an IDOC once. We need to write a logic to route the same to two different systems
Can any one tell me how can we do that ?
Regards
Ram.

Hello Ram,
Do you have connectivity between your production & XIQ?
What does "connectivity" mean?
1. RFC destination is maintained.
2. Port defined for the RFC destination.
If no, create these. (Search in SDN for details).
If yes, proceed:
1. Define the logical system for XIQ.(BD54)
2. Define the same as your partner profile. (WE20). Add the message type SYNCH with the port for XIQ.(This is imp)
3. Create a distribution model view with sender as "your production" & receiver as XIQ.
3.1. Add the messages which you want to distribute.
3.2 Generate Partner profiles.
No coding is reqd. for this.
BR,
Suhas

How to tigger SISCSO01 Idoc for sales order confirmation

Hello Experts,
I have a requirement where in I need to send the sales order confirmation as an IDoc. I need to use SISCSO01 IDoc type for that.
Can any please tell me how to configure SAP to trigger this IDoc when ever a sales order is confirmed.
In which T-Code is this sales order confirmation is done? and how to trigger the IDoc?
Thanks,
Suma

Hi Suma,
We need to maintan BD64 and WE20 with the Idoc SISCSO01 type. This is will automatically trigger the Idoc when we create a sales order.
You need to matain NACE for tiggering the IDoc. For that use BA00 in output types and configure program RSNASTED, from rotine as ALE_PROCESSING. In default values give transmission medium as ALE and parter function as SP.
Then come back to NACE-Condtion records and maintain meduim as A and date as 4.
Please reward if helpfull.
Thanks,
Srikanth

How to generate Outbound idoc for Material Reservation

Hi Experts,
I want to send outbound IDoc when a material reservation is created with tcode MB21.
I have been working on this issue and finding the solution in SCN for a week...
I found some messages similar to this but I could not find out the correct way how to do that.
At this moment, I configured BD64/WE20 referring the following topic which seems to be feasible solution but could not find any outbound IDocs created, unfortunately.
Implement ALE_RESERVATION_CREATE
I appreciate if someone can help me how to create outbound IDoc with MB21 or advice some possibility of missing configuration or steps.
Best Regards,
Kenji

Hi;
Have been able to find the solution to create the IDoc MRESCR after entering a reservation?
I am in the same situation and I do not see the IDoc output in the BD87.
It would be nice if you share the solution.
Thanks in advance

How to trace an idoc

Similar Messages

Maybe you are looking for