Prerequisites
Several General Ledger file import processes enable you to submit the file from the web page and then run the import processes on a batch server. One-time setup activities exist that you must perform to prepare your system for these tasks. These file import processes depend on the setup described in this table:
|
Process |
Process Object Name |
|---|---|
|
Flat file journal import. |
GL_JRNL_IMP |
|
Flat file ledger import. |
GL_LED_IMP |
|
Spreadsheet journal batch import. |
GL_EXCL_BATC |
|
Commitment Control budget journal import. |
KK_JRNL_IMP |
|
FACTS II Load MAF data. |
GL_F2_MAF |
The storage location of the file attachment is defined by the URL definition GL_FILE_IMPORT . By default, it points to a database record. You might want to change the storage location of the file attachment to another location, such as an FTP server. This is optional. Please refer to the File Attachment Architecture documentation for more details. To change this URL definition, select
You must define an environmental variable, PS_FILEDIR . This variable defines the temporary flat file location on the process scheduler that runs the file import process. If you have a Unix or OS390 process scheduler, you define this in the psconfig.sh file. If you have an NT process scheduler, you define this in the control panel. Please refer to the GetFile PeopleCode reference for more details or contact your system administrator.
See PeopleTools: PeopleCode Developer's Guide, "Using File Attachments and PeopleCode”.
PeopleTools: PeopleCode Language Reference, "PeopleCode Built-in Functions".