62

When posting an hour journal via Project management and accounting > Journals > Hour AND Project management and accounting > Journals > Dynamics 365 for Project Service Automation integration journal, the data displayed in the existing columns available in Accounting Source Explorer is insufficient for performing a detailed ledger/subledger analysis.


The columns Document, Document date, Account entry description, Destination company, Party number, Party name, Activity number, Category name, and Line property are all available in the ASE, but they do not contain data when the transaction is originating from an hour or PSA journal entry.


For instance, while the originating document (the hour journal) contains key columns such as Document, Document date, Account entry description, Destination company, Party number, Party name, Activity number, Category name, and Line property, the data from these fields is not carried over into the Accounting Source Explorer, resulting in a lack of traceability and detail.


This creates challenges when posting standard hour journals in F&O and also shows the limitations of the Project Operations non/stocked product. As an out-of-the-box integration between CE and F&O, its maturity is brought into question, as all transactions flowing from CE to F&O are processed as journals which would actually mean that all hour transactions would lack the necessary detail for analysis from a subledger perspective through the Accounting Source Explorer.


With this idea, we want to retrieve the data from the columns mentioned above into the Accounting Source Explorer, no matter what the originating document is.



Category: General Ledger
STATUS DETAILS
New