WE19 IDOC test tool in reverse to create a file

Hello gurus
Is there a way to use WE19 to "create" a file from an existing IDOC?
Thanks

I have an inbound order IDOC viewable in WE05.
I want to load it into WE19. No problem, I know how to do that.
Then, I want to save it on my app server as a plain ASCII file. In other words, a file that would look like one sent from an external system.
Does that help explain it?
Thanks

Similar Messages

WE19 (iDoc Test Tool) and case sensitive content

Hi experts,
I am not able to send case sensitive content via WE19. When I change a value of an existing iDoc (via WE19) all values of the segment are converted to uppercase (independent of the domain).
To reproduce:
1) Open transaction WE19
2) Use any existing iDoc as template
3) Open any segment
4) Fill any field with a lowercase text
5) Press ENTER
6) Re-open the segment and check changed field. -> The value is converted to upper case
This (translate to upper case) happens only on the segment that has been edited in WE19.
In my opinion, the transaction WE19 is not usable because it is not possible to edit/change case-sensitive values. In our customer setting we need to send case-sensitive data in iDocs to the receiver.
Question: Is there any other transaction to read an existing iDoc, change the data case sensitive and send it to the receiver.
Thanks in advance.
Björn

Hi,
yes - this is a "strange" behaviour ;o)
Only other solution I know you need an IDoc in status 51 for:
- go to bd87
- select the IDoc in status 51
- navigate to the needed data record
- double click it
- menu => display => change
- insert your data
After saving the status will be reset and you can process the IDoc in BD87.
I am not sure this will work for each IDoc and element - but you may give it a try.
For converting an existing to status 51 you can use this report: RC1_IDOC_SET_STATUS
Regards,
Kai

MPR Test Tool TC 2.2 - complains on files we have not installed

Hi,
After completing the MPR test tool guide the report states that I must provide valid file information for a number of filer located in
C:\Windows\System32\DriverStore\FileRepository\
We do not provide any drivers and we do not touch that folder with our application. Where does this complaint come from?
Some examples:
C:\Windows\System32\DriverStore\FileRepository\dc21x4vm.inf_amd64_a0b21378e23f5730\dc21x4vm.sys does not have a valid "Product name" property.
C:\Windows\System32\DriverStore\FileRepository\netwew00.inf_amd64_50a18d1774b14883\NETwew00.sys does not have a valid "Product Version" property.
C:\Windows\System32\DriverStore\FileRepository\netwew02.inf_amd64_877ffc2f8ce60cba\NETwew02.sys does not have a valid "Product Version" property.
C:\Windows\System32\DriverStore\FileRepository\netwlv64.inf_amd64_ddb4c4b2338036aa\netwlv64.sys does not have a valid "Product Version" property.
C:\Windows\System32\DriverStore\FileRepository\netwns64.inf_amd64_8df4062f3184ac15\NETwNs64.sys does not have a valid "Product Version" property.
C:\Windows\System32\DriverStore\FileRepository\netwsw00.inf_amd64_efdfa3e93099506a\Netwsw00.sys does not have a valid "Product Version" property.
C:\Windows\System32\DriverStore\FileRepository\prncacl1.inf_amd64_fe6ab4bfc0d78cd5\CNN08CL1FX.dll does not have a valid "Company name" property.
C:\Windows\System32\DriverStore\FileRepository\prncacl1.inf_amd64_fe6ab4bfc0d78cd5\CNN08CL1FX.dll does not have a valid "Product name" property.
C:\Windows\System32\DriverStore\FileRepository\prncacl1.inf_amd64_fe6ab4bfc0d78cd5\CNN08CL1FX.dll does not have a valid "Product Version" property.
C:\Windows\System32\DriverStore\FileRepository\prncacl2.inf_amd64_f23666aacaa6943f\CNN08CL2FX.dll does not have a valid "Company name" property.
C:\Windows\System32\DriverStore\FileRepository\prncacl2.inf_amd64_f23666aacaa6943f\CNN08CL2FX.dll does not have a valid "Product name" property.
C:\Windows\System32\DriverStore\FileRepository\prncacl2.inf_amd64_f23666aacaa6943f\CNN08CL2FX.dll does not have a valid "Product Version" property.
C:\Windows\System32\DriverStore\FileRepository\prndlcl1.inf_amd64_f5611618bf8581ba\amd64\dedrvor.dll does not have a valid "Company name" property.
C:\Windows\System32\DriverStore\FileRepository\prndlcl1.inf_amd64_f5611618bf8581ba\amd64\dedrvor.dll does not have a valid "Product name" property.
C:\Windows\System32\DriverStore\FileRepository\prndlcl1.inf_amd64_f5611618bf8581ba\amd64\dedrvpj.dll does not have a valid "Company name" property.
Best regards
Tobias

Hi all,
Any binaries showing in the C:\Windows\System32\DriverStore\ directories are a result of Remote Desktop redirection. These will not show if RDS redirection is turned off.
After investigating the files, if purely 3rd party to your code, a waiver may be filed.
In this case only, it is not necessary to include owner names, only to include the files are not owned by your product and are all located in subdirectories of C:\Windows\System32\DriverStore\.
Hope this helps,
-Logo

Conext Sensitive Help Test Tool Not Working

I have been trying to test my map files with the context-sensitive test tool, but am unable to get it working. I am running TCS 3.5 on Windows XP Pro.
I created a map files for Java in the project file and then created several test links with Map IDs. I am working with an offline WebHelp system on my C drive. I open the CSH Test Tool and located the index_csh.htm file for the WebHelp help system and then choose the Map Number. But when I click "Show Help," nothing appears. The hourglass comes up for a brief instant, as if it's going to load the page, but then nothing happens.
Can anyone help?
Thanks in advance.
Douglas

Hi, William:
Your C# API allowed me to successfully test. Thanks.
However, I was reading a bit more of the information on your site, and am still unclear why the deafult RH CSH Tester would not work. I was only using map numbers. Very frustrating.
I also had a few other questions, since this is the first time I'm creating a mapping file in RH:
- Is there any way to batch test? Or, if the icons appear blue (indicating they are correctly linked) in the Edit Map IDs dialogue box, can I just use your C# API to test a few and assume that they others are also working?
- Is this API set to open up the pages in IE by default? Mine is doing that, but I wasn't sure if it was your app or my computer settings. I'm in an corporate environment where we are supposed to use IE as the default browser, although I have FF installed, too. It keeps opening an IE window with a security message that says JavaScript is not supported and I have to click the bar at the top to allow ActiveX controls to work. I'm pretty sure that last part is a security setting I can't change here, but not so sure about the default browser choice.
-I haven't downloaded your API testers in other languages. Are they all the same with the difference just being language preference for the person testing it, or do some of them offer more functionality?
Thanks for sharing your great tool!
Douglas

Unable to create PDF file

I have just upgraded to Adobe X Standard and noticed I can no longer created PDF files. When I try convert any Word/Excel file to PDF I get an error "Your file could not be printed due to an error on Adobe PDF on e02"
I have tried to remove office and Adobe X Standard then install Office 2010 Professional and then Adobe X Standard 10.1.1 I have installed all updates for office.
My computer is running Windows 7 64bit with Office 32bit.
This happens when trying to print to PDF or save as PDF getting the same error.

Hi I dont think this is a permissions issue I just created a new WINDOWS PROFILE this fixed the issue the user already was a admin on the computer. The issue was trying to save/print any file to PDF to either network or local to computer. Once the new profile was made I was able to test and could once again create pdf files. There must have been something in the old profile causing the issue and the new profile fixed the issue it was a last thing to to try as had tried everything I could think of.

Unable to create PDF - file could not be printed

I am having a problem with a user who is unable to create a pdf using Adobe Standard 8
The error messages is as follows:
your file could not be printed due to an error on adobe pdf on Ne 04
http://i45.photobucket.com/albums/f97/bsucards/584872418744_adobe.jpg
I have tried to uninstall Adobe Standard 8 and reinstall and do all the updates
I have uninstalled Adobe Reader 9 and downgraded it to Adobe Reader 8
I have reinstalled Office XP
I have created a new profile for this user
The only way I can get it to work is to make the user an admin, which is not an option. We have other users in the company using this version of Adobe without any problems

Hi I dont think this is a permissions issue I just created a new WINDOWS PROFILE this fixed the issue the user already was a admin on the computer. The issue was trying to save/print any file to PDF to either network or local to computer. Once the new profile was made I was able to test and could once again create pdf files. There must have been something in the old profile causing the issue and the new profile fixed the issue it was a last thing to to try as had tried everything I could think of.

How to create UTL file from on Unix server

Hi,
I have created a stored procedure in Oracle (8.0.6) which will create a flat file using UTL_File. The oracle server is running on unix system.
When I am executing the PL/SQL procedure from Unix's Sql Plus, it is creating the file properly. When I try to execute the same from a windows client using SQL Plus / PLSQL Developer, It is not creating the file.
Any input is worh.
also, pls find below the code I am using.
P_Dir = ' /apps/ullcis/dev/data'
P_File = 'test.log'
dbms_output.put_line('In Create Log File ');
l_file_handle := UTL_FILE.FOPEN(P_Dir,P_File, 'w');
dbms_output.put_line('Opened in Write');
UTL_FILE.PUT_LINE (l_file_handle,'sample text');
UTL_File.fflush(l_file_handle);
UTL_FILE.FCLOSE (l_file_handle);
Regards
Sam

I'm writing to unix file path not onto the windows client.And i have permission in that unix direcotry to create a file.The above code does well if invoked from sql prompt of unix but it does not create file, if i invoke from sqlplus in windows client. Any help ...?
Thanks

Creating a file in append mode

Hi All,
I have a requirement where in i need to create a flat file in append mode . The requirement is as follows :
- In a week , SAP sends certain number of IDOCs to XI . For the first IDOC that comes in ,XI has create a file and later for the rest of the IDOCs ,XI just has to append the file contents .
- During the End of the week , the target system picks this file for processing.
My file structure is as follows:
Header
seg1
seg2
seg2
seg3
seg3
seg1
seg2
seg2
seg3
seg3
Trailer.
So ,while creating a file in append mode , is there any way apart from creating one more interface to pick the finally created file , i can make sure that the file gets written in the above format without header and trailer getting repeated.
Regards
Vinay P.

Hi, Vinay
If you don't want to use a new interface, you can use a operating system command in your target communication channel..
The OS script must:
pick up only one header line and move it to a temporal file. For example, with UNIX command you can do that with
grep "criteria" file | head -1 > temporal_file
pick up each detail line and move it to the temporal file.
pick up only the last trailer line and move it to the temporal file
Rename temporal file to final flat file.
Regards,
Carme.

WE19 - Test tool for IDOC processing

Hi:
As we know WE19 is the test tool, and it has downside that it translates everything into upper case.
Even SAP has a note for it, stating that it is not going to change. but it gets changed everything in upper case .
In Our requirement; some fields` value in lower case (or partially lower case) are required by using this tool, it converts these into upper case and hence our process does get failed.
Let me know if any exit or bapi or some other solution for it.
<REMOVED BY MODERATOR>
Thanks in advance.
Regards
Shashi
Edited by: Alvaro Tejada Galindo on Apr 22, 2008 4:07 PM

Hi,
Do I understand that correct that SAP says in a note that the data will not be converted to upper case in WE19, but it is getting converted anyway?
In this case I would definitely raise an OSS message because according to SAP WE19 is not supposed to change the entries into upper case.
If I misunderstood your comment then the only possibility would be to hook into one of the user exits. Every IDOC that is created uses a function module that processes the IDOC and passes the data to the application. The user exit you can use depends on which IDOC type you are using. The import function modules start with IDOC_INPUT_*. Once you find out which function is used just look into the coding to identify the user exits. Use an exit at the beginning to convert the data before it is passed to the application.
Hope that helps,
Michael

Error while using Test tool -WE19

Hi All,
When I am trying to use Test tool for IDOC processing ( WE19) in R/3 System for any Basic Type ,for example: PEXR2002 and select the Standard Outbound Processing, I am getting the message as Port does not exist in the table of port descriptions.
Is this error something where port configuration is missing or some standard error.
Please provide your inputs.
Regards
Pragya Dubey

Hello Dubey,
Check it once u r configaration..
Step by Step Procedure..
Create the tRFC port definition
Refer to the following steps to create the tRFC port definition.
1. SAP transaction code: WE21 Type /nwe21 on the SAP input window and press the
Enter key.
2. Highlight Transactional RFC.
3. Click the Port pull-down menu, which is located in the upper left corner of the SAP
screen. Click Create (or press F7).
4. Select the own port name radio button.
5. Type a port name such as ALEport. If you use a port name different from this, update
Table 2 at the beginning of this chapter for future reference.
6. Click the green check icon to continue.
7. Fill in the description field with tRFC port (You are free to write anything you want here).
8. Fill in the RFC destination field with ALESERVER. This must match the name you used on the previous RFC Destination step. If the name you enter here does not exist, the
system will flag an error and you will need to provide an existing RFC destination.
9. Make sure that IDoc record types SAP Release 4.x is selected.
10. Click on save.
Thanks,
Satya Kumar
Reward points if it is useful..

Inbound idoc testing via partner profile

i want to test inbound idoc testing via partner profile.
the problem is i its generating idoc no and giving a message like
"idoc no 12453152.. is saved but cannot or shd not be processed".
what does that mean ..
how shd i veiw properties of partner p[rofiles

i am getting thid message from we 19 ..
in that i am creating a sales order...
i am clicking on startinboung button on application tools bar.
this is an information pop up window ..
if i press f1 on that ..
help says that ...may be you cannot process the idoc immediatly...
check for partner profiles

Idoc Testing! Need help!

Hi!
 (Please give answers specific to my question & pls read below)
 i want to test idoc outbound as well as inbound.
First Consider inbound,
 I ve read previous posted threads it was mentioned goto>we19> give idoc no
I want to know what is idoc no how we get idoc no for the idoc.

Then i know the steps...
Now Outbound,
How to test outbound idoc -- i want to know how my posting program has correctly generated idoc to ale layer.
I want this in complete detail.
 Thanks!
 Rahul.

Hi Rahul,
idoc structure
http://www.sapbrainsonline.com/ARTICLES/TECHNICAL/idoc/SAP_IDOC_structure_introduction.html
What is Idoc?
I give overview of IDoc terminology and how IDocs work in an enterprise will clarify the process
SAPs presence in the IT world is justified by a central premise: It turns a companys many individual systems into one, big supersystem. More than a linking together of applications, SAPs implementation causes a redirection of the flow of information through a company and its partner companies that enhances the potential of its business functions.
This flow of information is enabled by a core element in SAP technology: the Intermediate Document, or IDoc. Technically, the IDoc is an example of Electronic Data Interchange (EDI). Unlike conventional EDI, IDocs are not based on a descriptive language.
The IDoc concept borrows the best features of EDI and combines them with the best features of conventional transaction file formats. The result is a lean data transport mechanism that is the engine of SAP data flow, tying together applications, databases, companies, and networks. Here is a look at the makeup of IDocs within the application architecture.
Form and content: IDoc terminology
As is often the case with proprietary technologies, SAP assigns specific, object-oriented meanings to familiar terms. When referring to IDocs, the term document refers to a set of data comprising a functional group of records with a business identity. (For example, all the data in a purchase order, or all the profile information of a supplier in a supplier master record.)
A message refers to the contents of a specific implementation of an IDoc; its a logical reference. This differs from a reference to the IDoc itself, which specifies the messages physical representation. Think of it this way: If youre watching a parade pass by, the mayor waving to the crowd from his limousine is the message, and the mayors limousine (which is specific to the mayor) is the IDoc. Youre building a logical object, and the IDoc is both its container and the vehicle that moves it.
The IDoc control record
Each IDoc has a single control record, always the first record in the set. The structure of this record describes the content of the data records that will follow and provides administrative information, such as the IDocs functional category (Message Type/IDoc Type), as well as its origin (Sender) and destination (Receiver) as in conventional EDI (see Figure A).
Figure A
IDOC number Sender Receiver Port Message type IDoc type
1234567890 R3NYC R3LA FILE INVOICES INVOICE01
This cover slip format informs the receiving system of the IDocs purpose, and the receiving system uses it to determine the correct processing algorithm for handling the arriving IDoc.
Data records
The data records following the control record are structured alike, including two sections: a segment information section and a data section.
In the first part of a data record, the segment information section describes the structure of the data that follows, for the benefit of the IDoc processor. There is a segment name (like an EDI segment identifier) that corresponds to a data dictionary structure to which the IDoc processor has access. The remaining information is useful for foreign systems, such as a partner companys Oracle system, which has no such data dictionary.
The second part of the record is the data itself, a storage area of 1,000 characters.
Status records
If youve ever ordered a package from a faraway location and tracked its progress using the Internet-based tracking utilities now provided by most major parcel carriers, youre familiar with the list of stops and transfer points through which a package passes on its way to you.
This collection of records is exactly what youll see in an IDoc that has begun its work. Following the data records in an IDoc, status records accumulate as an IDoc makes its way from one point in a process to another.
Typically, an IDoc will acquire several of these records as its does its job. They are simple records, consisting of a status code (there are more than 70 codes, covering a broad range of conditions and errors), a date/time stamp, and some additional status information fields for system audit purposes. In addition, as errors occur in the processing of an IDoc, status records (see Figure B) are used to record these errors and the date/time of their occurrence.
Figure B
(Display Status Record)
IDoc number 0000000000123456
Direction 1 Outbound
Status information
 38 IDoc archived
(additional descriptive text)
Log time
 Date 6-30-02
 Time 14:35:21
Portion of IDoc status display
IDoc Base
IDocs, as data formatting tools, enable the easy sharing of data between databases and applications within a company as well as being an efficient data courier between companies. Typically in SAP, a database of IDoc definitions exists, to which any application may have access.
This IDoc Base gives all the applications and processes in your company domain the capacity to send, receive, and process a document in a contextually appropriate way, without doing anything to the data. For example, a purchase order IDoc can filter through every process it touches, passing from system to system, accumulating status records to track its progress.
Every department using the data can use it appropriately without any cumbersome intermediate processes, because each department draws its key to interpreting the IDoc from the same source.
Multiple messages
One cumbersome feature of conventional EDI is the embedding of more than one functional record type in a document. The unwieldy X-12 888 Item Maintenance transaction set is an example: It purports to handle so many different configurations of product master data that it is horrifically difficult to integrate into an existing system.
IDocs, on the other hand, handle multiple messages with ease. Given the centralized IDoc interpretation that SAP provides to all its parts, its no problem to define an IDoc that will contain more than one message, that is, more than one data record type.
A customer master IDoc, for example, may contain customer profile information records for a customer with many locations. But it may also contain location-specific pricing information records for that customer in the same document. This is an incredibly efficient way of bundling related records, particularly when passing large amounts of complex information from system to system (see Figure C).
Figure C
CONTROL RECORD
DATA RECORD - CUST PROFILE LOC #1
DATA RECORD - CUST PROFILE LOC #2
DATA RECORD - CUST PROFILE LOC #3
DATA RECORD - CUST DISCOUNT STRUCTURE LOC #1
DATA RECORD - CUST DISCOUNT STRUCTURE LOC #2
DATA RECORD - CUST DISCOUNT STRUCTURE LOC #3
STATUS RECORD
STATUS RECORD
STATUS RECORD
Records in a multiple-message IDoc
Final thought
There is no mastering SAP without mastering its workhorse, the IDoc. ERP environments utilizing SAP and similar platforms are made necessary in the first place by the increasing demands of ever more integrated business relationships. IDoc technology addresses this trend with a simple but powerful design philosophy: Data is no longer something to be stored; its something to be moved.
And
These links give u complete details abt idocs testing
Test Tool
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b80f643d711d1893e0000e8323c4f/content.htm
Status Monitor for ALE Messages
http://help.sap.com/saphelp_nw04/helpdata/en/d4/0d67e4d85511d2a6080060087832f8/content.htm
Regards ,
Kumar.

Are testing tool effective

Hi,
I am trying to test my scenario using 2 available method of testing. I deliberately put a wrong data and tested in message mapping.
As expected, my mapping fails in test tab of message mapping. Now i took the same payload ( whcih has wrong data) & used it in Runtime workbench ( Integration engine- Test Message) & also in ID in Tools-Test Configuration
To my surprise, the messages are triggered without error and i can see sucess flag. However when I see the XML payload it has wrong data. My Question is why these tool did not recognized what message mapping test found. How effect are those tools considering that they simulate the pipeline steps.
Regards,

When you do a mapping test, the only thing that you are testing is the mapping, independently of interfases.
When I want to test any interface, I:
1) Log on into R/3. Look for an existing IDOC in TC WE02 with status 03 (data passed to port OK). When I found one, I write the idoc number and then I go to TC WE19 and I test it there; just put the idoc number in textbox "existing idoc" and press F8, when you go to next screen, press F7 and put there the amount of Idocs that you want to reprocess. Then, log on into XI and go to TC SXI_MONITOR and see if the xml generated by the idoc you reprocess was sent ok.
2) Log on into IR and in message mapping go to test; test it putting information in the outbound idoc or xml or rfc. When the mapping result is ok, save that xml.
Then, I use a http page that basis guys give to me long time ago, where I have only to put:
Server Host (your server host, like srv-xxx-adm for example)
Server Port (in this case, I test it with server 8000 and not 50000)
Client (your mdt in SAP R3)
Quality of Service (sync., async. or exactly once in order)
Sender Service (your sender service; you can found it in ID)
Sender Interface (your message interface in IR)
Sender Namespace (your namespace in IR)
Then, you can upload the xml and logon with a username and password, and the xml will be sent.
And like in 1), you must log on into XI and go to TC SXI_MONITOR and see if the xml generated by the idoc you reprocess was sent ok.
3) Some guys from other systems are using a program called xmlspy to send xml from any system throw xi to sap or from sap throw xi to any system. The only thing that I have to do is to send them the empty xml I got from message mapping in IR, so they can fill it with information and send it. Then, just look at it in sxi_monitor transaction code in xi.
I dont use the other test tools because last guy in xi here told me not to use it (he didnt explain me why).
I hope this could be helpful for you.

Using WE19 IDOC

Hello Friends,
Using WE19 How to send data .
How to create Port and Partner No. for both Sender and Port
message type : Debmas in Control Records Field.
Please instead of links give procedure .
With Regards,
Raju.

Hi,
>>Using WE19 How to send data .
Give the IDoc number to be triggered and click on the Execute Button or Press F8.
>>How to create Port and Partner No. for both Sender and Port
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.
Regards
Santhosh
Remember to set the thread to solved when you have received a solution

HTTP to File Scenario: execute Test Tool (html) but any received message?

Hi all,
I have configured the HTTP to File scenario in SAP XI 7.0. When i execute the Test Tool (HTTP_Client_Adapter.html), i don't see any message in the XI Server. I don't know the Test Tool which i used for the test work correctly, because when i clicked on 'Send' button, i don't get any message in the XI Server?
The Configuration Scenario is OK when executing the Configuration Test in ID.
Could you please tell me how i can know the Test Tool is execute correctly?
The Test Tool which i used in the link below:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/66dadc6e-0a01-0010-9ea9-bb6d8ca48cc8
Thanks a lot in advance,
Vinh Vo

HI,
In XI You can go to RWB (from XI server homepage)->Comp Monitoring -> Display All ->Int Server-> Int Engine
In the bottom, you find 3 tabs, select the test message tab to post messages.
Pls note that, when you need to test, you should have created the scenario in IR/ID (and u can use the details of Receiver Determination ID) to fill in the details.
You can refer this:
/message/266750#266750 [original link is broken]

WE19 IDOC test tool in reverse to create a file

Similar Messages

Maybe you are looking for