Archive for the ‘PeopleSoft’ category

Adjust Accumulated Depreciation

January 21st, 2010

We need to accelerate depreciation on the tax books for thousands of assets in prior years, and retain the cost, and future depreciation.

So for example, we need to take 50% of the asset depreciation in the year it was put in service, i.e. 2007. The asset would depreciation the remaining value through it’s life.

The partial retirement process gets me the results except it retires the asset, and adjusts the cost.

The adjust accumulated depreciation screen seems to get what we need, however, it is creating additional DPR and/or PDP entries (depending on trans_dt) used. these are small amounts but I can’t figure out where it is getting the number. If I knew how it was getting the nubmer I could adjust my plug to get the answers we need.

This is only for tax books. It is related to new repair regulations where a statistical method was applied by auditors, and we need to sync PeopleSoft to match the new values.

Thanks for any advice or detailed explanation on how the adjust accum depreciation screen works.

I may need a little more information before providing proper guidance.  Have the thousands of assets had any transactions (transfers, cost adjustments, recategorizations, etc.) performed on them since they were put in service?  Unfortunately PeopleSoft won’t allow you to make any adjustments to assets prior to the last possible change made to the asset (e.g. the new transaction date must be greater than or equal to the latest available transaction date associated to the asset).

Since the assets have very likely been touched since their in-service date, my recommendation would lean towards re-converting the tax books for the assets in question.  When you perform the re-conversion, you can add the 50% accumulated depreciation as of the asset’s in-service date (which would accomplish the FY2007 example you provided in your question).  Then the asset would depreciate as usual for the remainder of its useful life.

Alternatively, here is a quick explanation of the Adjust Accumulated Depreciation page that is delivered:

If the asset has already begun depreciating, use whatever transaction and accounting date needed and enter values for the Depr Accum Adjustment, and, if applicable, the Year to Date Depr Adjust.

This will create an ADD entry for the accumulated depreciation adjustment, which populates the PS_DEPRECIATION table.  Then, a RAD (Reserve Adjustment) entry gets created on the PS_OPEN_TRANS table.  After you run Depreciation Calculation it should adjust the future depreciation of the asset based on the cost basis, the total accumulated depreciation, and the transaction date used for the adjustment.

As for the DPR and PDP entries that get created, you may want to ensure that the Accounting Date is equal to the Transaction Date used when adjusting the accumulated depreciation (even though accounting entries aren’t being created, as you are only adjusting the tax books).  You’ll likely have to open up the periods in question, though, as PeopleSoft may still try to validate that the accounting period is open.

Share and Enjoy:
  • PDF
  • Print
  • email
  • Twitter
  • Facebook
  • LinkedIn
  • RSS
  • Tumblr
  • Google Bookmarks
  • Netvibes

EFT payments in PeopleSoft Expenses 9.0 without PeopleSoft HR

January 19th, 2010

Our company is in the process of implementing Expenses 9.0 (we do not have PSoft HR, but do have AP and GL). We have a requirement to allow users to be paid either via check or direct deposit (EFT). I have no problems getting the check portion to work. However, it seems no matter what configuration changes or user changes that I make payment is always being staged as System Check. Can anyone point me in the right direction as to what configuration area I should be looking at?

I am assuming you have your employees set up as vendors in the system. If this is the case, you should be able to modify their vendor record to point to Electronic Funds Transfer rather than Check.

Go to Vendors > Vendor Information > Add/Update > Vendor. Find the employee and click on the Location tab. Click the Payables hyperlink. Expand the Additional Payables Options section. In the Additional Payment Information section, select Specify and then Electronic Funds Transfer.

Share and Enjoy:
  • PDF
  • Print
  • email
  • Twitter
  • Facebook
  • LinkedIn
  • RSS
  • Tumblr
  • Google Bookmarks
  • Netvibes

SQL Developer Tweaks

January 16th, 2010

I came across Duncan Davies‘s PeopleSoft Tipster blog when searching for ways to customize and optimize SQL Developer to make my job easier. He has some great tips for tweaking Oracle’s free SQL Developer tool to look better and work better for the consultants of the world. Some tips that I’ve started using:

1) Change the Font. Developers like to indent and line up their code to make it more readable. Why deliver the product with a default font that isn’t fixed width, therefore making this harder? The first change I make is to swap the font (Tools > Preferences > Code Editor > Fonts) for Lucida Console, 11pts – although the font size may vary depending upon monitor resolution and the state of your eyesight.

3) Syntax Colours. Picking a better colour scheme eases readability as you’ll be able to pick out strings, operators and brackets/braces quicker but the delivered scheme highlights keywords in bold, which throws out the alignment if you’ve pick a fixed-width font. I normally make the following changes (Tools > Preferences > Code Editor > Syntax Colours):

  • Remove the bold highlight from ‘Default Element Name’ and ‘Default Keyword’.
  • Change Default Separator to purple
  • Change Default String to red
  • Uncheck ‘Enable highlight’ against Current SQL

I also use several of the Toolbar Shortcuts he mentions, such as F9 to execute SQL queries.

Thanks for the great article, Duncan!

Share and Enjoy:
  • PDF
  • Print
  • email
  • Twitter
  • Facebook
  • LinkedIn
  • RSS
  • Tumblr
  • Google Bookmarks
  • Netvibes