Implementing eAM with PJM and Project...

2842389 28 posts since Jan 19, 2015

Implementing eAM with PJM and Project Costing Aug 2, 2016 3:33 PM
Organization was previously defined for eAM with Default Cost Group set to Inventory, which is used across all
other orgs. Now setting up PJM with minimal eAM setups done previously; have checked 'Project Cost Collect
Enabled' for eAM org. Setup a project, using Average Costing. Is it necessary to setup a completely new org
to have the correct Default Cost Group at the Org Parameter for that Average Cost Group that will be used for
WO costs to transfer to projects? Is there a specific rule of what default setting issued for the Average Cost for
the projects--so we wouldn't have to create a new organization for that Average Cost so it would transfer all the
costs correctly for the project into PA, FA and GL?

Paula

S_Senthilkumar 868 posts since Jan 24, 2014

Re: Implementing eAM with PJM and Project Costing Aug 4, 2016 8:05 AM
Hi,

Is it necessary to setup a completely new org to have the correct Default Cost Group at the Org Parameter for
that Average Cost Group that will be used for WO costs to transfer to projects?
Is there a specific rule of what default setting issued for the Average Cost for the projects?

You need to complete project manufacturing module set up for both question. You can try for the existing org
and any issues need to check since your case is the unique.

2842389 28 posts since Jan 19, 2015

Re: Implementing eAM with PJM and Project Costing Aug 5, 2016 12:59 PM
in response to S_Senthilkumar
We have PJM that we're setting up. We also have eAM that is in production, but not being used to the full
functionality and we're implementing with PJM and Cost Collections so that costs are passed to PA for Capital
asset projects on Work Orders. We have PA up/running for long time, but are expanding the functionality.
When the org was setup initially for eAM, they did not assign an Average Cost Default Group---and we have
changed to average costing for this org. (12.1.3) So the Default Cost Group currently assigned to that eAM
org.

Do we need to 're-create' a new eAM org, to include PJM setups, to use Average Cost for those asset
projects? We created a new average cost group for projects and assign that to the individual project at setup,

1
Implementing eAM with PJM and Project...

but I didn't know if the Default Cost Group at the org level would affect costs getting passed to PA/GL based on
this.

Thanks,
Paula

Marcia Lucas-Oracle 149 posts since Jan 15, 2013

Re: Implementing eAM with PJM and Project Costing Aug 5, 2016 9:18 PM
in response to S_Senthilkumar
Please review Project Manufacturing Implementation Notes (Doc ID 101440.1)

This Note is very helpful, for implementing PJM x Cost Management (Discrete)

S_Senthilkumar 868 posts since Jan 24, 2014

Re: Implementing eAM with PJM and Project Costing Aug 8, 2016 10:28 AM
in response to 2842389
Review your PJM set up and if required you need to create new org for EAM.

Earlier what is the cost used for EAM org?

2842389 28 posts since Jan 19, 2015

Re: Implementing eAM with PJM and Project Costing Aug 9, 2016 1:48 PM
in response to S_Senthilkumar
Ok, I confirmed with some scripts that the Default Cost Group is indeed, Average Costing. However, that is
also the default cost group assigned to all orgs. Is it a best practice to create a separate Average Cost Group
for eAM/PJM? I'm thinking we could assign that cost group to the new projects that get setup going forward, as
we don't want to have to setup new eAM org---we have transactions against that org.

Thank you.