An asset was retired in 2007 and in 2009 is now needing to be reinstated. (why? wrong asset was retired.) After the reinstatement is saved and deprcalc is run, no PDP is being created for 2009, just accumulated. Instead DPR is created for all the months after the initial retirement. Only the accumulated depreciation is being posted in 2009. My developer and I have tried resetting the asset back to the initial ADD and rerunning the processes in a variety of ways with the same results. This problem is affecting only two of the three REI I did for 2009 so the problem isn’t even consistently wrong. Suggestions on what to look at next?

I’ve seen this in the past as well. I would certainly agree with Steve – it is never a good idea to delete/purge data from the system. That creates nightmares from an audit and data integrity standpoint.

A workaround that we used for this one-off case was to create the PDP entry yourself in the GL. This option isn’t the cleanest, but it gets you where you need to be. Since you likely won’t be re-running Depreciation Close for the previous periods (the process that actually creates the period’s DPR accounting entries and sends them to GL), you won’t have to worry about double-booking depreciation.

Hi,
I’ve created an online voucher and then i’ve posted it. After that i ran the pre interface process to get the asset details in the pre interface loader table. Then i ran the payables interface process AMPS1000 to get the asset details in the INTFC_PHY_A and INTFC_FIN tables. When i reviewed the INTFC_PHY_A tables, i could not get the location field populated. Please let me know if anyone of you have faced the similar kind of issue.
Thanks in advance,
PP

I’ve encountered this issue at several clients. In the end we’ve had to develop a customization in the INTFAPAM Application Engine to pull in the PS_VOUCHER_LINE.SHIPTO_ID, as our AP Ship To Location ID’s are the same as the AM Asset Location ID’s.

I am pretty sure PeopleSoft removed this code prior to or immediately after Financials version 8.8 for some reason.

Hi Tyson,

I’m facing the same issue, i’ve checked the trace file of INTFAPAM and found that it is populating the location as blank in INTFC_PRE_AM table. Now when i checked the trace for AMPS1000, it is populating the location in INTFC_PHY_A based on the RECEIVER_ID found in INTFC_PRE_AM. And the location is picked from RECV_LN_ASSET table.

The main issue here is even if the RECEIVER_ID is there in the INTFC_PRE_AM table, it is not populating the LOCATION in INTFC_PHY_A table. I’m not sure why is this happening. Any comments on this?

Tyson, could you please explain me the customization that u have performed on INTFAPAM app engine?

Thanks,
P

P,

The customization that we’ve developed in the past was to take the PS_VOUCHER_LINE.SHIPTO_ID and populate the PS_INTFC_PRE_AM.LOCATION field with the same ID (or you can use a translate built off of a custom translate table).

For purchase orders, if your organization enters receipts (uses the Receiving functionality), then we could look into that code as well. Let me know if this is the case and we could explore that option to assign valid locations to asset additions through the interface.