| field name | data type | description |
|---|---|---|
| tcOriginalStatus | character | |
| tcOriginalComments | character | |
| ttOriginalAddGLNbrDate | date | |
| tlPostingSelected | logical | |
| tcCreator | character | |
| tcApprover | character | |
| tcVerifier | character | |
| Posting_ID | integer | |
| Company_ID | integer | |
| Journal_ID | integer | |
| ReportingJournal_ID | integer | |
| Period_ID | integer | |
| PeriodMark_ID | integer | |
| CreatorUsr_ID | integer | |
| LastVerifiedUsr_ID | integer | |
| LastApprovedUsr_ID | integer | |
| AutoReversalPosting_ID | integer | |
| PostingVoucher | integer | Voucher is a sequential number that uniquely identifies the journal entry (within the combination of an entity and a daybook code). |
| api annotation: | In create mode,enter 0 in this field - the voucher number is generated by the system. In Modify/Delete, the correct voucher number must be entered because this identifies the record. | |
| PostingDate | date | The accounting date on which the journal entry is posted. The posting date must be a valid calendar date and must be within the GL calendar year (PostingYear) and period (PostingPeriod). |
| PostingSystemDate | date | The system date of the posting corresponding to "PostingDate". |
| api annotation: | In Create mode, when Partial Update = yes - this field gets a default value which is the current date of the system. | |
| PostingValueDate | date | The value date (used for banking entries). |
| PostingText | character | Free text describing the posting. |
| api annotation: | Value for this field defaults to blank | |
| PostingSecondText | character | |
| PostingBusinessRelationTxt | character | When the posting is a transaction linked to a business relation (for example, an invoice posting), this field contains the Business Relation Name. Used for information purposes on reports and browses. |
| api annotation: | Value for this field defaults to blank. | |
| PostingInvoiceReferenceTxt | character | When the posting is part of an invoice posting, then this field contains the invoice number (Year/Daybook/Voucher extended with supplier invoice Reference in case of a supplier invoice). Used for information purpose on reports and browsers. |
| api annotation: | Value for this field defaults to blank | |
| PostingParentText | character | Contains the description field from the parent object that triggered the posting. When the posting is an invoice posting, this field contains the invoice description. When the posting is a banking entry posting, the description of the bank statement line is copied to this field, etc. Used for information purposes on reports and browses. |
| api annotation: | Value for this field defaults to blank. | |
| PostingPeriod | integer | The GL period for the posting. The period must be open. |
| PostingYear | integer | The GL calendar year for the posting. |
| PostingYearPeriod | integer | The GL calendar year/period for the posting. This field is determined by "PostingPeriod" and "PostingYear". |
| api annotation: | If Partial Update is true, the value defaults using PostingPeriod and PostingYear. | |
| PostingOriginIsExternal | logical | Indicate whether the posting is from an External Origin. When creating cross company postings, set this to true. |
| api annotation: | Value for this field defaults to false. | |
| PostingOriginReference | character | GL Reference Number. Format is ZZYYMMDD999999 where ZZ = module (IC, SO, WO) YY = Year, MM = Month, DD = Day, 999999 = Running Journal Number. MfgPro equivalent: glt_ref |
| PostingOriginDocument | character | Transaction History Number (Inventory or Operations) or Invoice Number (Sales Order) MfgPro equivalent: glt_doc |
| PostingOriginDocumentType | character | Document Type (I for Invoice, OP for Work Orders) MfgPro equivalent: glt_doc_type |
| PostingOriginTransType | character | System generated code used to identify a transaction (IC for Inventory, WO for Work Orders, SO for Sales Orders, FA for Fixed Assets) MfgPro equivalent: glt_tr_type |
| PostingOriginDaybookCode | character | Daybook Code (normally this corresponds with our JournalCode) MfgPro equivalent: glt_dy_code |
| PostingOriginDaybookNumber | character | Daybook Number (normally this corresponds with our PostingVoucher) MfgPro equivalent: glt_dy_num |
| PostingBatchNumber | character | Some financial input programs allow you to enter a batch number and to keep a control total on the screen of all the transactions entered with the same batch number. |
| api annotation: | Not applicable for application integration. | |
| PostingOriginAddressCode | character | For invoices created with Invoice Post and Print, the address code of the bill-to customer is stored in this field. |
| PostingOriginatorReference | character | Original Posting Reference. this field must contain the key values of the refered posting, if this posting is a manual reversal or replacement of an existing posting. |
| api annotation: | Value for this field defaults to blank. | |
| PostingIsReplacement | logical | Indicate whether the posting is a replacement of an existing posting. |
| api annotation: | Value for this field defaults to "false". For reversal postings, either automatic or manual - this value defaults to "true". | |
| PostingIsReversing | logical | Indicate whether the posting is a reversal of an existing posting. |
| api annotation: | Value for this field defaults to "false". | |
| PostingIsReversingBySign | logical | Indicate whether the mathematical inversion - inverse the mathematic sign of the amounts (+ => - and - => +) - has been applied. |
| api annotation: | Value for this field defaults to "false". | |
| PostingIsZeroValueAllowed | logical | Indicate whether zero values are allowed in the posting lines. |
| api annotation: | Value for this field defaults to "false". | |
| PostingIsSkipAutoAssignLC | logical | When a LC field (Base Currency Amount field of PostingLine) is left zero, but the TC field (transaction currency amount) is not zero, then the posting component automatically calculates the corresponding value for the LC field. With some postings, this behavior is not wanted and can be suppressed by setting this flag to "true". |
| api annotation: | Value for this field defaults to "false". | |
| PostingAddGLNbr | integer | When additional GL numbering is enabled for an entity, all postings for this entity are assigned a continuous, uninterrupted incremental sequence numbers as the value for this field. |
| api annotation: | When additional GL numbering is not enabled for the current entity, value for this field defaults to 0. | |
| PostingAddGLNbrDate | date | |
| PostingAddGLNbrRevDate | date | |
| PostingVerifyStatus | character | China Financial Regulation requires that all GL transactions be verified as well as approved. This field holds the verification status. |
| api annotation: | Value for this field defaults to "INITIAL". | |
| PostingVerifyComments | character | When running the process of verification, the verifier can add some comments on the transaction. |
| api annotation: | Value for this field defaults to blank. | |
| PostingVerifiedDate | date | The date when this posting is last verified. |
| api annotation: | Value for this field defaults to blank. | |
| PostingVerifiedTime | integer | Last Verified Time. |
| api annotation: | System generates a default value for this field depending on when this posting was last verified. The combination of "PostingVerifiedDate" and "PostingVerifiedTime" uniquely identify the time at which this posting was last verified. | |
| PostingApproveStatus | character | China Financial Regulation requires that all the GL transactions must be verified as well as approved. This field holds the Approval status. |
| api annotation: | Value for this field defaults to "INITIAL". | |
| PostingApproveComments | character | When running the process of approval, the approver can add some comments on the transaction. |
| api annotation: | Value for this field defaults to blank. | |
| PostingApprovedDate | date | The date on which this posting was last approved. |
| api annotation: | Value for this field defaults to blank. | |
| PostingApprovedTime | integer | Last Approved Time. |
| api annotation: | The system generates default values for this field, depending on when this posting was last approved. The combination of "PostingApprovedDate" and "PostingApprovedTime" uniquely identify the time at which this posting was last approved. | |
| PostingMirrorRef | character | When Mirror Accounting is activated, postings that are mirrored get a reference to their paired posting. The reference contains year, daybook and voucher. |
| api annotation: | Value for this field defaults to blank. | |
| PostingIsAutoReversal | logical | Indicate whether the posting leads to an automatic reversal. |
| api annotation: | Value for this field defaults to "false". | |
| PostingAutoReversalType | character | If this posting is involved in automatic reversal activity of posting, value of this field will indicate whether this posting is the original one or the reversing one. It is calculated by the system. |
| api annotation: | If the flag PostingIsAutoReversal is "true", the field value defaults to "ORIGINAL ENTRY" for the original posting, and to "REVERSING ENTRY" for the reversing posting. | |
| PostingAutoReversalDate | date | Automatic Reversal Date. |
| api annotation: | When the flag PostingIsAutoReversal is "true" - If partialupdate="false", complete this field manually with a date in a later period than the one of the original entry; If partialupdate="true", value of this field will default to the first day of the next period. | |
| PostingBankImpRef | character | |
| PostingIsCorrection | logical | Indicates whether the posting is part of a correction action. |
| api annotation: | Value for this field defaults to "false". | |
| ObsoleteClosing_ID | integer | |
| PostingCreationDate | date | |
| PostingCreationTimeString | character | Seconds since midnight in HH:MM:SS |
| tcLocalCurrency | character | Local currency code |
| api annotation: | ? | |
| tcStatutoryCurrency | character | Statutory Currency. |
| tcTemplateCode | character | Template Code. A code which identifies a template. |
| api annotation: | Value for this field defaults to null. If the flag "tlSaveAsTemplate" is on, you should enter a string in this field as the posting template code. | |
| tlSaveAsTemplate | logical | Indicate whether to save the posting lines of this journal entry as a template. |
| api annotation: | Value for this field defaults to "false". | |
| tiSharedCompanyId | integer | ID of the CompanyShared record. |
| tiYearForNbr | integer | Year used for additional GL numbering. |
| tlIsAddGLNbr | logical | Additional GL Numbering Enabled. Indicate whether additional GL numbering is required. |
| tiOriginVoucher | integer | Original Voucher - just a calculated field used by the software as temporary storage during execution of the logic. |
| tiOriginPostingId | integer | Original Posting ID? |
| tcJournalCode | character | The daybook code of this posting. |
| api annotation: | The daybook must be an active daybook in the shared set for the current entity. When the accounting layer linked to the daybook tcJournalCode is not of type "Official", some GL types are not allowed, e.g. DEBTORCONTROL, CREDITORCONTROL, VAT. When the accounting layer linked to the daybook tcJournalCode is of type "TRANSIENT"; then the GL type cannot be OPENITEM and INVENTORY. | |
| tcLayerTypeCode | character | The layer type of the used daybook. |
| api annotation: | Default value for this field depends on the daybook used. | |
| tcJournalTypeCode | character | The daybook type of the daybook used. |
| api annotation: | For journal entries, this field defaults to "JOURNAL ENTRY". In other types of transactions (e.g. banking entry/invoices etc), this field must be set to the correct journal type. | |
| tiLayer_ID | integer | ID of the posting daybook layer. |
| tcUsrLogin | character | The creator of the posting. |
| tcPeriodTypeCode | character | Type code of the GL period 'normal', 'correction', 'closing'. |
| tcReportingJournalCode | character | For AR and AP transactions, it is possible to have additional daybooks under which a posting should be classified during tax reporting. |
| api annotation: | For AP/AR transactions, this field defaults to the journal code of the posting. Otherwise, it remains blank. | |
| tlJournalAccessAllowed | logical | Used to determine whether a user has access to modify a posting |
| 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 | |
| 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