Maximo List Archive

This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.



Purchase Requestion - GL Account Codes & Locations

From: mike.pycroft (2017-06-13 15:40)

When you create a PR and add lines the gl account defaults to the gl account linked to the location record. We tend to use a project account code for our engineering actives. So they will enter there project account code in the default section of the PR line screen and then add a new line. When they add a location the account code they used is overwritten by the location default account code. Does anyone know if there is away to suppressing this functionality?

I know that you can enter the location & project code in the defaults and it will work OK. I have tried that approach with the engineers but they argue that they ordering parts for multiple locations.

Thanks


From: maximal (2017-06-13 19:02)

You can write an automation script to push the GL onto the line, but you'll probably need to remove the field class on the line in order to do that effectively.
If you think about it, you are confusing the accounting mechanism a little. You want to debit a specific GL, but which GL is getting the credit? Is the location a receiver? That's tricky without making it a storeroom.

It sounds like you want to squish a two-step process into one step, i.e. write a PR / PO to order things for multiple location use with one GL to capture the costs, ignoring the location GLs. I'm not sure how traceable that would be if you did accomplish it.

We write multiple workorders for assets or locations, and override the default GL with the project GL. Orders are placed against the project GL, and yes, we ditched the field class on PR and PO and replaced it with automation scripts to pull the workorder GL (if the workorder is on the line). This makes the order clear.

-C