When your Idoc changes have been tested on the development environment, you may come to the conclusion that the Idoc used on development could be very useful on the test system. Use the test tool to create an inbound Idoc file for your inbound Idoc... The nature of Idoc processing is of course to get your data from system to system, however this doesn't mean you can put your Idoc on a memory stick and jab it into the next system. Here's what you can do to get test Idocs across different systems - and you will notice that it's pretty solid in setup - for good reason (security).

1. Find the (inbound) Idoc you want to distribute and feed it to transaction WE19
2. Display the Idoc and press button "Inbound file" - this will post your inbound Idoc as a file, as if it was just presented to the system from the outside world. Do note: this really is outbound processing for an inbound file ! Make sure you tick the "Start IDoc inbound processing of file immediately" off - as we are not interested in processing the Idoc on this system
3. The file name you need to enter here is a Unix file, so don't call it C:\idoc01.txt (which is a legal Unix filename). If you just enter the filename (without path) the file containing the Idoc will be stored in the "default SAP directory".
4. Check transaction AL11 and look for DIR_HOME, this directory should now have the file you've entered.
5. You can add several Idoc's to the same file, just make sure you don't mix message types
6. By now you'll need help from the network people: the file needs to be moved (copied) to DIR_HOME directory of the the target system. Transactions CG3Z and CG3Y can be very useful here too
7. Once on the target system, start transaction WE19 again and now fill in the "File as template" option, where the filename is the same as picked above...
8. The file will be picked up and used as template, you can still do changes like alter port names or actual data !

• Prev
• Next