Modules:IDL Journal Entries
Introduction
Journal entry is a logging of transcriptions into items accounting journal. The journal entry can consist of several items, each of which is either a debit or a credit.
Input file definition
| Field name | Type | Nullable | Description | Accepted values | Comment |
|---|---|---|---|---|---|
| Organization | String(40) | No | Indicates the organization to be used when processing documents. | [Organization search key] | Organization used for creating the Accounting Combination |
| TransactionalOrg | String(40) | No | Indicates the organization to be used when processing transactional documents. | [Organization search key] | |
| JournalHeader | String(255) | No | Journal entry name. | Used for grouping Journal Lines in the same Journal. | |
| JournalLine | String(255) | No | More information about the journal entry line. | ||
| Currency | String(60) | No* | Indicates the currency to be used when processing this document. | [Currency ISO code] | |
| Accounting Schema | String(60) | No* | An Accounting Schema defines the rules used in accounting such as costing method, currency and calendar. | [Accounting schema name] | |
| GLCategory | String(60) | No* | The General Ledger Category is an optional, user defined method of grouping journal lines. | [GL Category name] | |
| AccountingDate | Date | No | The date this transaction is recorded on in the general ledger. This date also indicates which accounting period within the fiscal year this transaction will be part of. | yyyy-MM-dd or yyyy-MM-dd HH:mm:ss format | The date must belong to a opened period of the TransactionalOrg calendar. |
| Opening | Boolean | Yes | A flag indicating this is an opening entry. | {TRUE, FALSE} | |
| Alias | String(40) | Version <= 1.1.3: No
Version >= 1.1.4: Yes | Allows you to define a alternate method for referring to a full account combination. | [Accounting Combination alias] | Version <= 1.1.3: If it does not exists any accounting combination with this alias, a new accounting combination will be created with this alias, account, product, business partner, project, campaign, sales region.
1.1.4 <= Version <= 1.1.9 or 3.0.0 <= Version <= 3.0.1: If it does not exist any accounting combination with the values of {Alias, Account, Product, Business Partner, Project, Campaign, Sales Region} fields (even if they are null), a new accounting combination will be created with specified {Alias, Account, Product, Business Partner, Project, Campaign, Sales Region} values. Version >= 1.1.10 or Version >= 3.0.2: not used. |
| Account | String(40) | Version <= 1.1.3: Yes
Version >= 1.1.4: No | The (natural) account used. | [Element Value search key] | Must be an SUB-Account.
1.1.4 <= Version <= 1.1.9 or 3.0.0 <= Version <= 3.0.1: If it does not exist any accounting combination with the values of {Alias, Account, Product, Business Partner, Project, Campaign, Sales Region} fields (even if they are null), a new accounting combination will be created with specified {Alias, Account, Product, Business Partner, Project, Campaign, Sales Region} values. Version >= 1.1.10 or Version >= 3.0.2: If it does not exist any accounting combination with the values of {TransactionalOrg, Account} fields, a new accounting combination will be created with specified {TransactionalOrg, Account} values. |
| Product | String(40) | Yes | Identifies an item which is either purchased or sold in this organization. | [Product search key] | 1.1.4 <= Version <= 1.1.9 or 3.0.0 <= Version <= 3.0.1: If it does not exist any accounting combination with the values of {Alias, Account, Product, Business Partner, Project, Campaign, Sales Region} fields (even if they are null), a new accounting combination will be created with specified {Alias, Account, Product, Business Partner, Project, Campaign, Sales Region} values.
Version >= 1.1.10 or Version >= 3.0.2: from 2.50MP32 and 3.0MP2 the Product field (accounting dimension) has been included in GL Journal Lines tab. |
| BusinessPartner | String(40) | Yes | Is anyone with whom you transact. This can include a customer, vendor, employee or any combination of these. | [Business Partner search key] | 1.1.4 <= Version <= 1.1.9 or 3.0.0 <= Version <= 3.0.1: If it does not exist any accounting combination with the values of {Alias, Account, Product, Business Partner, Project, Campaign, Sales Region} fields (even if they are null), a new accounting combination will be created with specified {Alias, Account, Product, Business Partner, Project, Campaign, Sales Region} values.
Version >= 1.1.10 or Version >= 3.0.2: from 2.50MP32 and 3.0MP2 the Business Partner field (accounting dimension) has been included in GL Journal Lines tab. |
| Project | String(40) | Yes | Identifier of a project defined within the Project. | [Project search key] | 1.1.4 <= Version <= 1.1.9 or 3.0.0 <= Version <= 3.0.1: If it does not exist any accounting combination with the values of {Alias, Account, Product, Business Partner, Project, Campaign, Sales Region} fields (even if they are null), a new accounting combination will be created with specified {Alias, Account, Product, Business Partner, Project, Campaign, Sales Region} values.
Version >= 1.1.10 or Version >= 3.0.2: from 2.50MP32 and 3.0MP2 the Project field (accounting dimension) has been included in GL Journal Lines tab. |
| Campaign | String(40) | Yes | The Marketing Campaign defines the parameters for a Campaign. | [Campaign search key] | 1.1.4 <= Version <= 1.1.9 or 3.0.0 <= Version <= 3.0.1: If it does not exist any accounting combination with the values of {Alias, Account, Product, Business Partner, Project, Campaign, Sales Region} fields (even if they are null), a new accounting combination will be created with specified {Alias, Account, Product, Business Partner, Project, Campaign, Sales Region} values.
Version >= 1.1.10 or Version >= 3.0.2: from 2.50MP32 and 3.0MP2 the Sales Campaign field (accounting dimension) has been included in GL Journal Lines tab. |
| SalesRegion | String(40) | Yes | The Sales Region indicates a specific area of sales coverage. | [Sales Region search key] | 1.1.4 <= Version <= 1.1.9 or 3.0.0 <= Version <= 3.0.1: If it does not exist any accounting combination with the values of {Alias, Account, Product, Business Partner, Project, Campaign, Sales Region} fields (even if they are null), a new accounting combination will be created with specified {Alias, Account, Product, Business Partner, Project, Campaign, Sales Region} values.
Version >= 1.1.10 or Version >= 3.0.2: from 2.50MP32 and 3.0MP2 the Sales Region field (accounting dimension) has been included in GL Journal Lines tab. |
| DebitAmount | Numeric | Yes | Indicates the transaction amount converted to this organization's accounting currency. | ||
| CreditAmount | Numeric | Yes | Indicates the transaction amount converted to this organization's accounting currency. | ||
| Tax | String(125) | Yes | Identifies the different taxes used for each tax category. | [Tax name] | |
| Withholding | String(60) | Yes | Identifies the rules governing the withholding of amounts. | [Withholding name] | |
| Activity | String(40) | Yes | Defines tasks that are performed in Activity Based Costing. | [Activity search key] | Important!!!: new column added in IDL version 1.1.10 and 3.0.2
Version >= 1.1.10 or Version >= 3.0.2: from 2.50MP32 and 3.0MP2 the Activity field (accounting dimension) has been included in GL Journal Lines tab. |
* This fields can be NULL if they have a default value associated.
Default Value definition
| Field name | Type | Accepted values | Examples |
|---|---|---|---|
| Organization | String(40) | [search_key] column from [AD_Org] table | |
| TransactionalOrg | String(40) | [search_key] column from [AD_Org] table | |
| BatchDescription | String(255) | Initial Data Load batch | |
| Currency | String(3) | [iso_code] column from [c_currency] table | EUR, USD, GBP, ... |
| AccountingSchema | String(60) | [name] column from [c_acctschema] table | IDL US/A/Euro, SmallBazaar US/A/Euro, Accounting Test US/A/US Dollar
|
| GLCategory | String(60) | [name] column from [gl_category] table | Manual, None, Inventory, ... |