Home » Categories » Solutions by Business Process » E-Business » XML

Path and File Names

Datafile Software

Path and File Names


Although a full path and filename must be given in the transaction definition, a batch run could well create XML files for different trading partners. It is often the case that trading partners will dictate the format of the filename of XML files to be sent to them. Also, it is helpful to be able to separate the files that are being sent to different trading partners.

Two processing commands exist that allow you to define both the path and the filename structure of output XML files for each trading partner. These are:

<?pathname path="xxxxxx$$$xxx" $$$="aaa,Dnnn-Data-Item"?>
<?filename file="xxxxxx$$$xxx" $$$="aaa,Dnnn-Data-Item"?>

The path and filenames are defined by xxxx, which can be anything legal for path and filenames. $$$ within the path and filenames gets replaced by whatever is contained in the data item Dnnn-Data-Item from the file aaa (one of the files defined by the dfd processing commands). The key to the file aaa is the current sales or purchase account as defined for the XML transaction.

There is a further wrinkle here. If there is a sequence of 9s with the filename, whether that be within the filename defined by the command, or within the data that is substituted for $$$, then the next file sequence number for that transaction replaces this sequence. The sequence number itself is maintained with the transaction definition (see above).

The XML file creation process actually creates each file with the file and pathname defined within the template itself. As each file is created, then its name is changed according to the filename command above, and the file is moved from its current location to the location as given by the pathname command.

If the pathname location doesn’t exist, the folder is created if, possible. If the file already exists, then you are asked if it’s OK to overwrite it — unless in auto-run mode, when it will give a warning message and abandon the run.

If the filename cannot be changed (probably because a file already exists with that name) then the file is left unchanged with the name and in the location as defined by the template itself.
Custom Fields
  • Release ID: Standard
Attachments Attachments
There are no attachments for this article.
Related Articles RSS Feed
Input XML File Questions
Viewed 1267 times since Mon, Jul 9, 2012
XML Application Options
Viewed 1360 times since Mon, Jul 9, 2012
Application Considerations - Customer Information
Viewed 2879 times since Tue, Jul 10, 2012
Print CrNotes Processed
Viewed 3273 times since Mon, Jul 9, 2012
addto
Viewed 1252 times since Mon, Jul 9, 2012
General Lookup File - Appendix 6
Viewed 1317 times since Tue, Jul 10, 2012
Diagnostic XML File Print - Intergrating XML Processes
Viewed 1286 times since Tue, Jul 10, 2012
copy
Viewed 1236 times since Mon, Jul 9, 2012
Namespaces
Viewed 44654 times since Tue, Jul 10, 2012
XML Transaction Types
Viewed 3749 times since Tue, Jul 10, 2012