| field name | data type | description |
|---|---|---|
| PostingLine_ID | integer | |
| Company_ID | integer | |
| PostingLineMaster_ID | integer | |
| PostingLineTransaction_ID | integer | |
| Posting_ID | integer | |
| CostCentre_ID | integer | |
| Currency_ID | integer | |
| Division_ID | integer | |
| GL_ID | integer | |
| Project_ID | integer | |
| IntercoBusinessRelation_ID | integer | |
| Period_ID | integer | |
| CrossCompany_ID | integer | |
| CrossCompanyPosting_ID | integer | |
| CrossCompanyPostingLine_ID | integer | |
| PostingLineSequence | integer | |
| PostingLineText | character | |
| api annotation: | Value for this field defaults to blank. Note: if a new record is created through the user interface, the default value is as same as the value of "PostingText" of tPosting. | |
| PostingLineDebitLC | decimal(4) | |
| api annotation: | Partial Update = yes - it will get a default value depending on the value of PostingLineDebitTC, PostingLineExchangeRate and PostingLineRateScale. BC Amount = TC Amount * Exchange rate (TC/BC) * Scale Factor (TC/BC). If Partial Update = false, enter the correct value into this field. | |
| PostingLineDebitTC | decimal(4) | |
| PostingLineDebitCC | decimal(4) | |
| api annotation: | Partial Update = yes - it will get a default value depending on the value of PostingLineDebitTC, PostingLineCCRate & PostingLineCCScale. SC Amount = TC Amount * Exchange rate (TC/SC) * Scale Factor (TC/SC). If Partial Update is false, enter the correct value for this field. | |
| PostingLineDebitPC | decimal(4) | |
| api annotation: | This field is obsolete. | |
| PostingLineCreditLC | decimal(4) | |
| api annotation: | Partial Update = yes - it will get a default value depends on the value of PostingLineCreditTC, PostingLineExchangeRate & PostingLineRateScale. BC Amount = TC Amount * Exchange rate (TC/BC) * Scale Factor (TC/BC). If Partial Update is false, enter a value for this field. | |
| PostingLineCreditTC | decimal(4) | |
| PostingLineCreditCC | decimal(4) | |
| api annotation: | Partial Update = yes - it will get a default value depending on the value of PostingLinCreditTC, PostingLineCCRate & PostingLineCCScale. SC Amount = TC Amount * Exchange rate (TC/SC) * Scale Factor (TC/SC). If Partial Update is false, you should enter the correct value for this field | |
| PostingLineCreditPC | decimal(4) | |
| api annotation: | This field is obsolete and can be left blank. | |
| PostingLineIsProjPosting | logical | |
| PostingLineQTY | decimal(10) | |
| api annotation: | Value for this field defaults to 0.0000. | |
| PostingLineProjectText | character | |
| api annotation: | Value for this field defaults to blank. | |
| PostingLineCostCentreText | character | |
| api annotation: | Value for this field defaults to blank. | |
| PostingLineSafText | character | |
| api annotation: | Value for this field defaults to blank. | |
| PostingLineExchangeRate | decimal(10) | |
| api annotation: | Default value for this field depends on the exchang erate shared set specified for the current domain. | |
| PostingLineRateScale | decimal(10) | |
| api annotation: | The default value is 1. | |
| PostingLineCCRate | decimal(10) | The exchange rate used to convert between transaction (TC) and statutory(SC) amounts. |
| api annotation: | Default value for this field depends on the exchangerate shared set specified for the current domain. | |
| PostingLineCCScale | decimal(10) | A decimal number that must be multiplied by the exchange rate to get the real exchange rate. Its format is 9999999.9999999 and it was introduced to extend the accuracy of the exchange rate. |
| api annotation: | The default value is 1. | |
| PostingYearPeriod | integer | The GL calendar year/period for the journal entry. |
| api annotation: | In Create mode, it will get be defaulted to the value for the field PostingYearPeriod of tPosting. | |
| PostingDate | date | Posting Date. |
| api annotation: | If this field is blank, it gets a default value equal to the value of PostingDate in tPosting. | |
| PostingLineCrossExternRef | character | Ext Reference (Cross-Cy) - must be filled when create a cross-company posting. |
| api annotation: | Value for this field defaults to blank. | |
| PostingLineOriginLineNbr | integer | Equivalent to PostingLineSequence, however there is a difference in format and the value may differ in a number of specific cases. MfgPro Equivalent: glt_line |
| api annotation: | Value for this field defaults to 0. | |
| PostingLineMirrorRef | character | This holds a reference number to link the source and mirror postinglines together. --> Source account 1 and mirror account 1 will have the same reference. --> Source account 2 and mirror account 2 will also have the same reference (but different from source and mirror account 1). |
| api annotation: | Value for this field defaults to blank. | |
| PostingLineMirrorType | character | SOURCE or MIRROR (Depending if the posting line uses the source account or the mirror account). |
| api annotation: | Value for this field defaults to blank. | |
| PostingLineAddGLNbr | integer | |
| PostingLineGrossIncAccRef | character | |
| PostingLineAddGLNbrDate | date | |
| PostingLineLegalDocNbr | character | |
| tcProjectDescription | character | |
| tcGLCode | character | The GL account used in this posting line. |
| api annotation: | This GL account must be active and from the shared set of the entity. The same GL account can appear twice or more in the same posting. GL accounts used in the postings must be of type 'Manual'. When the GL account is an open item account, the postings on the account are stored as individual items with a balance. Each posting on this account type results either from the creation of a new open item ('INITIAL") or a change in the balance of an existing open item ("MOVEMENT"). | |
| tlPostingLineIsLocalCurrency | logical | This flag indicates that the currency for the posting line is the base currency. This is set automatically. |
| tiVatPostID | integer | VAT post ID |
| tcGLDescription | character | |
| tlGLIsAutomaticAccount | logical | |
| tcGLTypeCode | character | |
| api annotation: | GL accounts used in the postings must be of type "Manual". When the account is an open item account, then the postings on the account are stored as individual items with a balance. Each possting on this account type results from either the creation of a new open item ("INITIAL") or a change in the balance of an existing open item ("MOVEMENT"). | |
| tcUnitCode | character | |
| tcAllocationType | character | Type of the open item posting. For example, a new item or a link to an existing item. |
| api annotation: | Each posting line for an open item account must contain either: Information for the creation of a new open item. tcAllocationType = "INITIAL", tcAllocationKey = a new mnemonic (reference to an open item). Or a reference to an existing posting on the same account . tcAllocationType = "MOVEMENT" tcAllocationKey = an existing reference to an open item. | |
| tcAllocationKey | character | Reference key to an open item. |
| api annotation: | Each posting line for an open item account must contain either: Information for the creation of a new open item. tcAllocationType = "INITIAL", tcAllocationKey = a new mnemonic (reference to an open item). Or a reference to an existing posting on the same account . tcAllocationType = "MOVEMENT" tcAllocationKey = an existing reference to an open item. | |
| tcAllocationPostingLine | character | |
| tcIntercoBusinessRelationCode | character | When the GL is an intercompany account (Intercompany Account box checked), then an intercompany business relation must be entered on the posting line. |
| api annotation: | When the field tcIntercoBusinessRelationCode is blank and the GL has a default business relation specified, this default is used. When the account is a fixed intercompany account (Fixed Intercompany box checked), the default intercompany business relation is the only valid value. | |
| tcCurrencyCode | character | The currency code of this posting line. |
| api annotation: | If a tcCurrencyCode is supplied for a local currency posting, this currency must be the local currency of the current entity. When the posting account is a single currency account, then the posting line must contain the currency in tcCurrencyCode. When a posting is in the local currency of the entity, the TC amount must equal the LC value. | |
| tcDivisionCode | character | The sub-account code of the GL account used in this posting line. |
| api annotation: | When the account is defined with sub-account analysis, then a sub-account must be entered on the posting line. If so, then this field defaults to the sub-account found in the account definition. The account and sub-account combination must be allowed by the COA mask. | |
| tcCostCentreCode | character | The cost center code of the account used in this posting line. |
| api annotation: | When the account is defined with cost center analysis, a cost center code must be entered on the posting line. The field defaults to the cost center in the account definition (if specified). The account and cost center combination must be allowed by the COA mask. If the posting account allows dual analysis, then both cost center and project analysis must be specified on the posting line. If left blank, the default values found in the account definition are used. | |
| tcProjectCode | character | The project code of the account used in this posting line. |
| api annotation: | When the account is defined with project analysis, a project code must be entered on the posting line. The field defaults to the project in the account definition (if specified). The account and project combination must be allowed by the COA mask. If the posting account allows dual analysis, then both cost center and project analysis must be specified on the posting line. If left blank, the default values found in the account definition are used. | |
| tlGLIsDebitAccount | logical | |
| tcCrossCompanyCurrencyCode | character | CrossCompanyCurrencyCode |
| tcCrossCompanyGLCode | character | |
| api annotation: | Cross-company is a special type of intercompany. When the data of the other company is also in the same database, you can create a cross-company posting that generates a second posting in that other company's accounting. Both postings balance each other and are also linked to each other. So cross-company postings are pairs of postings where one posting is in one entity and the other posting is in another entity. Both postings are linked to each other with reference fields. | |
| tcCrossCompanyIntercoCode | character | |
| tcCrossCompanyCode | character | |
| tcDivisionDescription | character | |
| tlLinkedCrCyDaemonReqExists | logical | This calculated field is set to True when the posting is a cross-company posting and is created by the cross-company daemon, otherwise its value is set to false, and no logic is applied to calculate the field value for modified records |
| tcCostCentreDescription | character | |
| tlSkipCOAValForPeriodCosting | logical | |
| CustomShort0 | character | |
| CustomShort1 | character | |
| CustomShort2 | character | |
| CustomShort3 | character | |
| CustomShort4 | character | |
| CustomShort5 | character | |
| CustomShort6 | character | |
| CustomShort7 | character | |
| CustomShort8 | character | |
| CustomShort9 | character | |
| CustomCombo0 | character | |
| CustomCombo1 | character | |
| CustomCombo2 | character | |
| CustomCombo3 | character | |
| CustomCombo4 | character | |
| CustomCombo5 | character | |
| CustomCombo6 | character | |
| CustomCombo7 | character | |
| CustomCombo8 | character | |
| CustomCombo9 | character | |
| CustomLong0 | character | |
| CustomLong1 | character | |
| CustomNote | character | |
| CustomDate0 | date | |
| CustomDate1 | date | |
| CustomDate2 | date | |
| CustomDate3 | date | |
| CustomDate4 | date | |
| CustomInteger0 | integer | |
| CustomInteger1 | integer | |
| CustomInteger2 | integer | |
| CustomInteger3 | integer | |
| CustomInteger4 | integer | |
| CustomDecimal0 | decimal(4) | |
| CustomDecimal1 | decimal(4) | |
| CustomDecimal2 | decimal(4) | |
| CustomDecimal3 | decimal(4) | |
| CustomDecimal4 | decimal(4) | |
| CustomShort10 | character | |
| CustomShort11 | character | |
| CustomShort12 | character | |
| CustomShort13 | character | |
| CustomShort14 | character | |
| CustomShort15 | character | |
| CustomShort16 | character | |
| CustomShort17 | character | |
| CustomShort18 | character | |
| CustomShort19 | character | |
| CustomCombo10 | character | |
| CustomCombo11 | character | |
| CustomCombo12 | character | |
| CustomCombo13 | character | |
| CustomCombo14 | character | |
| CustomDecimal5 | decimal(4) | |
| CustomDecimal6 | decimal(4) | |
| CustomDecimal7 | decimal(4) | |
| CustomDecimal8 | decimal(4) | |
| CustomDecimal9 | decimal(4) | |
| CustomDate5 | date | |
| CustomDate6 | date | |
| CustomDate7 | date | |
| CustomDate8 | date | |
| CustomDate9 | date | |
| LastModifiedDate | date | |
| LastModifiedTime | integer | |
| LastModifiedUser | character | |
| QADC01 | character | unused QAD reserved field |
| QADC02 | character | unused QAD reserved field |
| QADT01 | date | unused QAD reserved field |
| QADD01 | decimal(10) | unused QAD reserved field |
| tc_Rowid | character | |
| tc_ParentRowid | character | |
| tc_Status | character |
QadFinancials