FACTS 7.7 GL Detail Posting- wanting more detail

Hi,

We have a request to look into options for posting to general ledger in even more detail than by document.

This particular site would like to post entries at the document line item level.

Get's a little cloudy because not everything on a document is line level. The AR and Tax and Freight (anything outside the line items would still be posted at the document level).

Asking if anyone has a FACTS integrated solution.

Thank you,

Lawson user experience 10.1.0 Presentation Open Discussion and Dem.mp4

Find more posts tagged with

Comments

Cheng Ruan

Hi Cain,

Could you provide an example of what they seek? Back in the 80s when I was an end user, we captured revenue by product so some posting was at the line level. Today, using multiple warehouses on an order, one could hit branch specific inventory and cost of goods accounts as well.

Legacy Contributor

Hi Ralph,

What they are after is for every line on a document ( say invoice for now) they want an individual posting to the general ledger.

If there were 10 lines on the invoice- they want to see 10 detail entries to sales, inventory and cost of sales. Regardless of GL account- they want each line item to show up as a GL transaction. Even if 4 out of the 10 lines are posting to the same GL accounts- they want to see 4 entries to the GL.

Seems like an aweful lot of detail but they are providing GL activity to their parent company and the parent company's system reports in that detail ( SAP ) so they are asking for the same/similar information.

Some how the sales register determines what document lines can consolidate to the GL posting based on what GL account is going to be hit- maybe that consolidation could be turned off so to speak and treat each line on the document as if it were posting to a unique GL account.

Thanks for replying. If you have some ideas I would love to hear them.

Cain

sjacquin

Cain,
This should be a fairly simply task for one of your programmers. The 6200 block of SOR311 posts to a g/l distribution file. Adding the S/O line number to the key should generate a single post per line item. The trick will be to *not* do this for AR, tax, etc. I would get Tim to add a flag to the "pre_update_soglds" program which indicates that the standard post should not occur. Then, the custom routine can post the postings you wish with a line # added to the key. You can tell what posting is occuring based on the value of the variable I. You might consider just using the line # "000" for postings that are not line specific to keep the key structure consistent and *always* skip the standard post. Just off the cuff.

Michael

Cheng Ruan

Choose option "3 - Print and Post in Detail" for GL Distribution in SO to GL Posting F/M - or better still, upgrade them to 7.7 where detail posting is always performed. That should get them pretty close.

Ralph

Eddy Vittini

Cain,

Michael brings up an excellent point about using the custom hook feature of SOR311 "pre_update_soglds", but there is already the embedded feature of "skipping" the standard post, just return the variable "X" as a zero and the standard post will just "return".

If this is version 7.7, the SMGLDD has 4 entity data pieces of the key and the standard posting only uses the first 2 leaving entity_key3$ and entity_key4$ available to be manipulated for your own benefit.

Bob Fitzgibbon

Copyright © 2025 Infor. All rights reserved.