| # Post Imported Journal Transactions (tfgld2215m000) Use this session to import data files as a journal transaction into the general ledger. Before importing the data into the general ledger, it must be loaded into the ERP Enterprise Import tables, which you can accomplish by using the Exchange module. A sample exchange scheme called JVIMPRT has been delivered to the demo company. In this session you can import the data from the import tables with the help of the identification number into the general ledger. Enter a range of file-identification numbers, which must be included in the imported batch. The identification numbers must already exist in the Exchange module. A report that shows any problems incurred while attempting the import, or verifying the success of the import, will be printed. Note If the import is successful or partially successful, a transaction batch is created. This batch can then be edited in the Transactions (tfgld1101m000) session and subsequently finalized in the Finalization Run (tfgld1110m000) session. If the import is unsuccessful, the errors must be corrected and the ASCII file reloaded by the Exchange module. If the entire batch fails, the same identification number can be used in the corrected file. If the import is partially successful, a new identification number must be used for the corrected batch because the original identification number is already associated with the first partially imported batch. Note To prevent journal transactions with an incorrect or empty ledger account from blocking a successful import, ensure that in the Company Parameters (tfgld0503m000) session, on the External Journals tab, a suspense account is specified. Related topics Journal import Selection Range Identification Number Enter a range of identification numbers of the file to be imported. The identification number is a unique code used to ensure that a file is imported only once. The number is provided in the ASCII file. Note Import of a file can be attempted only once. If the import is successful or partially successful, you must change the identification number before importing the remainder. If the attempt to import a batch fails, you can use the same identification number. Identification Number The identification number of the contents of the ASCII file. The number is provided in the ASCII file. Note If the batch was partially successful, you must change the identification number before importing the remainder. If the batch completely failed, you can use the same identifcation number. Error Report If this check box is selected, ERP Enterprise prints a report of any errors that occur. Audit If this check box is selected, ERP Enterprise... Remove Document Lines If this check box is selected, journal transactions that were already processed are removed from the selected range. Batch Identification Identification Number The identification number of the contents of the ASCII file. The number is provided in the ASCII file. Note If the batch was partially successful, you must change the identification number before importing the remainder. If the batch completely failed, you can use the same identifcation number. Batch The batch that contains the transactions. Document Number The identification of a transaction. The document code is a combination of: Transaction-type code Series number Sequence number |