Archive for January, 2010

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

Selecting the translate values from PSXLATITEM table by joining to another table

January 14th, 2010

Our current Version: PS8.9; People Tools: 8.47How can we select the translate values from PSXLATITEM table by joining to another table?I want the description(XLATLONGNAME) in the field value rather th
How can I get the translate values description selected in the query?
Record used :
PSXLATITEM.
HRS_JO_RQMT_I
fiels selected:
SCHEDULED_TYPE
SHIFT
Translate values of Schduled_type:
P
F
O
Long names:
par time
Full time
Optional
I want the descriptions (long names) of the tanslate values should be displayed in the output rather than
F, P, O
Any suggestions ?/ Thanks.

If you are doing this via the online Query tool, you can change the Field settings (on the Field tab) to display the Long description rather than the ID for the fields you are selecting.

If you are just writing SQL, I would suggest using XLATTABLE_VW instead of PSXLATITEM to obtain the long description of the field(s) you are selecting. In my queries, I typically join to that view with the following criteria:

SELECT D.XLATLONGNAME AS SCHEDULE_TYPE
FROM PS_HRS_JO_RQMT_I A, XLATTABLE_VW B
WHERE B.FIELDNAME = 'SCHEDULED_TYPE'
AND A.SCHEDULED_TYPE = B.FIELDVALUE AND B.EFFDT
(SELECT MAX(B_ED.EFFDT) FROM XLATTABLE_VW B_ED
WHERE B.FIELDNAME = B_ED.FIELDNAME
AND B.FIELDVALUE = B_ED.FIELDVALUE
AND B_ED.EFFDT <= SYSDATE);
Share and Enjoy:
  • PDF
  • Print
  • email
  • Twitter
  • Facebook
  • LinkedIn
  • RSS
  • Tumblr
  • Google Bookmarks
  • Netvibes