project QadFinancials > class BJournalEntry > API query SelectPosting (optimised)

Description

SelectJournalEntry = select query
use this query in case you want to lookup a journal entry
this query should only be used by UI-components!!!!


query filter (table tFilter)


tcBusinessFieldNametcDataTypetcOperator
iiCompanyIdi
tJournal.JournalCodec=,>=,>,<>,<=,<,begins,can-do,matches
tJournal.JournalControlc=,>=,>,<>,<=,<,begins,can-do,matches
tJournal.JournalTypeCodec=,>=,>,<>,<=,<,begins,can-do,matches
tLayer.LayerCodec=,>=,>,<>,<=,<,begins,can-do,matches
tLayer.LayerTypeCodec=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingAddGLNbri=,>=,>,<>,<=,<
tPosting.PostingAddGLNbrDatet=,>=,>,<>,<=,<
tPosting.PostingApproveCommentsc=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingApprovedDatet=,>=,>,<>,<=,<
tPosting.PostingApprovedTimei=,>=,>,<>,<=,<
tPosting.PostingApproveStatusc=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingAutoReversalTypec=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingBankImpRefc=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingBatchNumberc=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingBusinessRelationTxtc=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingCreationDatet=,>=,>,<>,<=,<
tPosting.PostingCreationTimeStringc=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingDatet=,>=,>,<>,<=,<
tPosting.PostingInvoiceReferenceTxtc=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingIsAutoReversall=,<>
tPosting.PostingIsReplacementl=,<>
tPosting.PostingIsReversingl=,<>
tPosting.PostingMirrorRefc=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingOriginatorReferencec=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingOriginDaybookCodec=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingOriginDaybookNumberc=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingOriginDocumentc=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingOriginDocumentTypec=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingOriginIsExternall=,<>
tPosting.PostingOriginReferencec=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingOriginTransTypec=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingPeriodi=,>=,>,<>,<=,<
tPosting.PostingSecondTextc=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingSystemDatet=,>=,>,<>,<=,<
tPosting.PostingTextc=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingVerifiedDatet=,>=,>,<>,<=,<
tPosting.PostingVerifiedTimei=,>=,>,<>,<=,<
tPosting.PostingVerifyCommentsc=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingVerifyStatusc=,>=,>,<>,<=,<,begins,can-do,matches
tPosting.PostingVoucheri=,>=,>,<>,<=,<
tPosting.PostingYeari=,>=,>,<>,<=,<
tPosting.PostingYearPeriodi=,>=,>,<>,<=,<
tUsr2.UsrLoginc=,>=,>,<>,<=,<,begins,can-do,matches
tUsr1.UsrLoginc=,>=,>,<>,<=,<,begins,can-do,matches
tUsr3.UsrLoginc=,>=,>,<>,<=,<,begins,can-do,matches


Parameters (internal)


iiCompanyIdintegerCompany id


query condition


  each Posting where
Posting.Company_Id = iiCompanyId AND

      first Journal (inner-join) where
Journal.SharedSet_Id = vi_JOURNAL_sharedset(iiCompanyId) AND
Journal.Journal_ID = Posting.Journal_ID AND

          first Layer (inner-join) where
Layer.Layer_ID = Journal.Layer_ID AND

      first Usr1 (conditional-join) where
Usr1.Usr_ID = Posting.LastVerifiedUsr_ID AND

      first Usr2 (conditional-join) where
Usr2.Usr_ID = Posting.LastApprovedUsr_ID AND

      first Usr3 (inner-join) where
Usr3.Usr_ID = Posting.CreatorUsr_ID AND


query resultset tqSelectPosting


field namedata typedb fielddescription
ttPostingAddGLNbrDatedatePosting.PostingAddGLNbrDateAdditional GL Numbering Date
tcPostingApproveStatusCalccharactercalculated
tcPostingBankImpRefcharacterPosting.PostingBankImpRefBank Importing Reference
tcPostingBatchNumbercharacterPosting.PostingBatchNumberSome 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.
ttPostingCreationDatedatePosting.PostingCreationDateCreation Date
tcPostingCreationTimeStringcharacterPosting.PostingCreationTimeStringSeconds since midnight in HH:MM:SS
tcPostingMirrorRefcharacterPosting.PostingMirrorRefWhen 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.
tcPostingSecondTextcharacterPosting.PostingSecondTextSecond Description
ttPostingSystemDatedatePosting.PostingSystemDateThe 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.
tcPostingVerifyStatusCalccharactercalculated
tcPostingOriginatorReferencecharacterPosting.PostingOriginatorReferenceOriginal 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.
tcPostingVerifyStatuscharacterPosting.PostingVerifyStatusChina 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".
tcJournalControlcharacterJournal.JournalControlA type of daybook control: Financial/Operational/External-used to clearly separate postings based on their source.
tcJournalTypeCodecharacterJournal.JournalTypeCodeA daybook type code.
api annotation:Value for this field defaults to "Journal Entries".
tcLastVerifiercharacterUsr1.UsrLoginLogin
tcLastApprovercharacterUsr2.UsrLoginLogin
tcCreatorcharacterUsr3.UsrLoginLogin
tcPostingApproveCommentscharacterPosting.PostingApproveCommentsWhen running the process of approval, the approver can add some comments on the transaction.
api annotation:Value for this field defaults to blank.
tcPostingVerifyCommentscharacterPosting.PostingVerifyCommentsWhen running the process of verification, the verifier can add some comments on the transaction.
api annotation:Value for this field defaults to blank.
tiPostingVerifiedTimeintegerPosting.PostingVerifiedTimeLast 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.
tiPostingAddGLNbrintegerPosting.PostingAddGLNbrWhen 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.
ttPostingApprovedDatedatePosting.PostingApprovedDateThe date on which this posting was last approved.
api annotation:Value for this field defaults to blank.
tiPostingApprovedTimeintegerPosting.PostingApprovedTimeLast 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.
tcPostingApproveStatuscharacterPosting.PostingApproveStatusChina 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".
tcPostingAutoReversalTypecharacterPosting.PostingAutoReversalTypeIf 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.
ttPostingVerifiedDatedatePosting.PostingVerifiedDateThe date when this posting is last verified.
api annotation:Value for this field defaults to blank.
tlPostingIsAutoReversallogicalPosting.PostingIsAutoReversalIndicate whether the posting leads to an automatic reversal.
api annotation:Value for this field defaults to "false".
tlPostingIsReplacementlogicalPosting.PostingIsReplacementIndicate 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".
tlPostingIsReversinglogicalPosting.PostingIsReversingIndicate whether the posting is a reversal of an existing posting.
api annotation:Value for this field defaults to "false".
tcPostingInvoiceReferenceTxtcharacterPosting.PostingInvoiceReferenceTxtWhen 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
tiCompany_IDintegerPosting.Company_IDLink to Company
tiPostingYearPeriodintegerPosting.PostingYearPeriodThe 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.
tcLayerCodecharacterLayer.LayerCodeLayer Code
tiJournal_IDintegerPosting.Journal_IDDaybook Code
tiPostingPeriodintegerPosting.PostingPeriodThe GL period for the posting. The period must be open.
tiPostingYearintegerPosting.PostingYearThe GL calendar year for the posting.
tcJournalCodecharacterJournal.JournalCodeA daybook code (maximum eight characters).
tiPostingVoucherintegerPosting.PostingVoucherVoucher 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.
ttPostingDatedatePosting.PostingDateThe 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).
tcPostingTextcharacterPosting.PostingTextFree text describing the posting.
api annotation:Value for this field defaults to blank
tcLayerTypeCodeCalccharactercalculated
tcLayerTypeCodecharacterLayer.LayerTypeCodeLayer Type
tiPosting_IDintegerPosting.Posting_IDRecord ID
tcPostingBusinessRelationTxtcharacterPosting.PostingBusinessRelationTxtWhen 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.
tlPostingOriginIsExternallogicalPosting.PostingOriginIsExternalIndicate 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.
tcPostingOriginReferencecharacterPosting.PostingOriginReferenceGL 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
tcPostingOriginDocumentcharacterPosting.PostingOriginDocumentTransaction History Number (Inventory or Operations) or Invoice Number (Sales Order)
MfgPro equivalent: glt_doc
tcPostingOriginDocumentTypecharacterPosting.PostingOriginDocumentTypeDocument Type (I for Invoice, OP for Work Orders)
MfgPro equivalent: glt_doc_type
tcPostingOriginTransTypecharacterPosting.PostingOriginTransTypeSystem 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
tcPostingOriginDaybookCodecharacterPosting.PostingOriginDaybookCodeDaybook Code (normally this corresponds with our JournalCode)
MfgPro equivalent: glt_dy_code
tcPostingOriginDaybookNumbercharacterPosting.PostingOriginDaybookNumberDaybook Number (normally this corresponds with our PostingVoucher)
MfgPro equivalent: glt_dy_num
PostingCustomcharactercalculatedcustom fields
JournalCustomcharactercalculatedcustom fields
LayerCustomcharactercalculatedcustom fields
Usr1Customcharactercalculatedcustom fields
Usr2Customcharactercalculatedcustom fields
Usr3Customcharactercalculatedcustom fields
ti_sequenceintegercalculatedprimary index
tc_rowidcharactercalculated = rowid(Posting),rowid(Journal),rowid(Layer),rowid(Usr1),rowid(Usr2),rowid(Usr3)


Internal usage


unused


Sample code: how to call this query through RPCRequestService (QXtend Inbound)

define temp-table ttContext no-undo
    field propertyQualifier as character
    field propertyName as character
    field propertyValue as character
    index entityContext is primary unique
        propertyQualifier
        propertyName
    index propertyQualifier
        propertyQualifier.

define dataset dsContext for ttContext.

define variable vhContextDS as handle no-undo.
define variable vhExceptionDS as handle no-undo.
define variable vhServer as handle no-undo.
define variable vhInputDS as handle no-undo.
define variable vhInputOutputDS as handle no-undo.
define variable vhOutputDS as handle no-undo.
define variable vhParameter as handle no-undo.

/* Create context */
create ttContext.
assign ttContext.propertyName = "programName"
       ttContext.propertyValue = "BJournalEntry".
create ttContext.
assign ttContext.propertyName = "methodName"
       ttContext.propertyValue = "SelectPosting".
create ttContext.
assign ttContext.propertyName = "applicationId"
       ttContext.propertyValue = "fin".
create ttContext.
assign ttContext.propertyName = "entity"
       ttContext.propertyValue = "1000".
create ttContext.
assign ttContext.propertyName = "userName"
       ttContext.propertyValue = "mfg".
create ttContext.
assign ttContext.propertyName = "password"
       ttContext.propertyValue = "".

/* Create input dataset */
create dataset vhInputDS.
vhInputDS:read-xmlschema("file", "xml/bjournalentry.selectposting.i.xsd", ?).
vhParameter = vhInputDS:get-buffer-handle("tParameterI").
vhParameter:buffer-create().

assign vhParameter::icRange = "A"
       vhParameter::icRowid = ""
       vhParameter::iiRownum = 0
       vhParameter::iiNumber = 5 /* Number of records to read */
       vhParameter::icSortColumns = ""
       vhParameter::ilCountOnly = false
       vhParameter::ilForwardRead = true
       vhParameter::iiMaximumBrowseRecordsToCount = 0.

vhParameter = vhInputDS:get-buffer-handle("tFilter").
vhParameter:buffer-create().

assign vhParameter::<field-name-1> = <field-value-1>
       vhParameter::<field-name-2> = <field-value-2>
       ...

/* Connect the AppServer */
create server vhServer.
vhServer:connect("-URL <appserver-url>").

if not vhServer:connected()
then do:
    message "Could not connect AppServer" view-as alert-box error title "Error".
    return.
end.

/* Run */
assign vhContextDS = dataset dsContext:handle.

run program/rpcrequestservice.p on vhServer
    (input-output dataset-handle vhContextDS by-reference,
           output dataset-handle vhExceptionDS,
     input        dataset-handle vhInputDS by-reference,
     input-output dataset-handle vhInputOutputDS by-reference,
           output dataset-handle vhOutputDS).

/* Handle output however you want, in this example, we dump it to xml */
if valid-handle(vhExceptionDS)
then vhExceptionDS:write-xml("file", "Exceptions.xml", true).

if valid-handle(vhOutputDS)
then vhOutputDS:write-xml("file", "Output.xml", true).

/* Cleanup */
vhServer:disconnect().
assign vhServer = ?.

if valid-handle(vhInputDS)
then delete object vhInputDS.

if valid-handle(vhOutputDS)
then delete object vhOutputDS.

if valid-handle(vhExceptionDS)
then delete object vhExceptionDS.