Understanding Initiating File Processing
The Inbound File Processing page runs the Application Engine process PTIB_INFILE that initiates the file-to-message processing. The file-to-message processing function reads the file rowset and publishes it as a message.
If an index file exists when the inbound conversion process runs, the application engine program loads the list of files to be converted into a parameter table and completes a commit. The application engine program uses the list of files within the parameter table to restart the processing if a particular flat file fails. If a single data file is provided, then the rowset processing immediately begins.
The file publish process goes through each of the rowsets of the file layout and copies them into the message row sets.
If the audit action (AUDIT_ACTN) exists in the file, it is copied to the PSCAMA record. If the audit action does not exist in the file, the publishing process uses the default value that is specified in the file layout field property.
The Inbound File Loader utility publishes a new message when one of the following exists:
-
The size of the data in the service operation exceeds the value of the Maximum Message Size field set in the PeopleTools Options page.
To view the value in the field, select .
-
A new file layout is detected.
-
End of file is reached.
The application engine program completes a commit every time a message is published from a file. After conversion, the flat file remains in the parameter table with a status of Processed.
Note:
The file layout should exactly match the message layout (excluding the PSCAMA record) and should use the same character set as that used by the file: either American National Standards Institute or Unicode.