PUR-STK – Different Inventory GL Account Based on PO Reason (Project ID?)

Hi all,

Looking for some guidance on the best-practice Epicor approach for a purchasing/inventory accounting scenario we’re working through.

The Issue

We have the same Part Number being purchased for both Production and R&D as products transition and scale. Since a part can only have one Part Class at a time, our normal PUR-STK receipt follows the Inventory/Expense GL Control tied to that Part Class. Today, we have separate DEV and PROD Part Classes, which becomes a problem when the same part can be used for either purpose.

Goal:

We want the inventory account to be driven by the purpose of the specific PO line/release, rather than changing the classification of the part.

Purchase Purpose Project ID on PO Desired Inventory GL
Production Blank Production Inventory – default Part Class control
R&D R&D Project ID Development Inventory – control associated with Project

This would give us a clean transaction-level indicator while allowing the Part Number and Part Class to remain unchanged.

What We’ve Looked At

We’ve reviewed Part Class, Product Group, Warehouse GL Controls, Project GL Controls, and the PUR-STK posting logic. Our preference is to keep Part Class as the default inventory accounting treatment, with Project ID acting as the exception for R&D purchases.

What We’re Trying to Determine

What is the best-practice Epicor method for having the Project ID on a PO line/release drive a different inventory account for a PUR-STK receipt, while a blank Project ID continues to use the normal Part Class GL Control?

We’ve looked at Project GL Controls, but it doesn’t appear that the standard PUR-STK inventory account determination automatically gives the Project control precedence over Part Class.

Has anyone accomplished this out of the box, or does this typically require a Posting Rule customization/BPM?

Ideally, we’d like to avoid duplicate Part Numbers, changing Part Classes based on use, or requiring Receiving to use different warehouses solely to drive the accounting.

Any feedback or examples of how others have handled this would be appreciated!

Thanks!
-Tanner

I am NOT a posting rule expert (my disclaimer)… but I believe that this is totally the purpose of posting rules. You can adjust the GL account based on “rules” that are defined in the posting rules. Kinetic comes with a standard set of those rules, and that is how it currently looks for the correct gl account in the Partclass… but I believe you should be able to have the posting rule adjusted so that it follows your definition instead.

Thanks for the reply.

We are trying to add a posting rule, but we are having trouble narrowing down which ABT field to use as the trigger for setting the Debit account. Could we add a custom “_c” field for this on the PO Entry/Receipt Entry screen?

The ProjectID variable didnt seem to correspond to the PO release level on the Part Tran like we thought it would.

Thanks in advance!

When a PO is linked with a Project, PE checks for GL in Project linked GL Control mapping or WIP account.

Otherwise, company, part class or part.

KR

There should be a posting hierarchy documentation for project but no such thing exists afaik.