Finance | Project Operations, Human Resources, ...

Relation between Free text invoice (CustInvoiceTrans) to GeneralJournalEntry table

(0) Share

Report

Posted on by Sathish Sivakumar

3,732

Hello,

Can anyone please let me know what is the relation between the Free text invoice (Custinvoicetrans) to GeneraljournalEntry table?

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

real_ashwin 1,229 on at

Like (0)

Report
Copy link

Link copied!

Open AOT and check each table to see the relation tab if they are mentioned.

Anyway I joined them differently you can first join GeneralJournalEntry gje to GeneralJournalAccountEntry gjae using gje.Recid=gjae.GeneralJournalEntry

Then join GeneralJournalEntry gje and CustInvoiceTrans cit using gje.subledgervoucher=cit.invoiceid and gje.subledgervoucherdataareaid=vij.dataareaid

Was this reply helpful? Yes No
OsmanIstanbul 2,818 on at

Like (0)

Report
Copy link

Link copied!

Hi,

there is not such a relationship between these two tables. and question has some incorrect informations: free text invoices' table is custinvoicetable. its line table is custinvoiceline. please check your question and elaborate further.

Regards.

Was this reply helpful? Yes No
Suggested answer

greengrimms 1,400 on at

Like (0)

Report
Copy link

Link copied!

Hi Satish,

I wish there was an easy way to relate transactional data with ledger entries, but the truth is there is no direct 1:1 relation between any of these tables.

What you can do to get a good match is first search for CustInvoiceJour (header) using the following fields:

Then relate the fields LedgerVoucher from CustInvoiceJour with SubledgerVoucher on the GeneralJournalEntry + DefaultDimension from CustInvoiceTrans with LedgerDimension from GeneralJournalAccountEntry (using LedgerDimensionFacade::getDefaultDimensionFromLedgerDimension() in order to get a match between both fields) + LineAmount from CustInvoiceTrans and abs(AccountingCurrencyAmount) from GJAE.

This of course cannot be translated easily into an x++ query, since it uses x++ functions that don't translate to SQL, but it's the best approximation I could find.

Hope that helps.

Was this reply helpful? Yes No