I have added section in the right column titled "PeopleSoft in the News". This section keeps you up to date on the market trends for PeopleSoft.
On a different subject, if you are looking for a change in jobs, please visit the PeopleSoft Developer Jobs site: http://jobs.psoftdev.com/ or simply click the JOBS link at the top of this page.
Tuesday, January 31, 2012
Career Reading - Success System That Never Fails
Here is a book I picked up a while back titled "The Success System That Never Fails". To summarize it, go after knowledge, absorb knowledge, then utilize knowledge.
Author: W Clement Stone
Title: The Success System That Never Fails
ISBN-10: 0671701819
ISBN-13: 978-0671701819
Overall it's a good book.
Thursday, December 29, 2011
AR_EXCL_EDIT: Runs to No Success with SQL error
Using as an example PeopleSoft Financials 9.0 and PeopleTools 8.49...
Error:
Stmt #: 1603
Error Position: 0
Return: 8601 - Numeric value out of range (SQLSTATE 22003) 0
Failed SQL stmt:SELECT COUNT(*) FROM PS_DEP_EXCEL_TAO
ABENDED at Step AR_EXCL_EDIT.MAIN.SETCNT1 (SQL) -- RC = 8601 (108,524)
Cause/Solution:
From what I see per the original error, the actual code in AR_EXCL_EDIT.MAIN.SETCNT1 is:
%SelectInit(COUNT_1)
SELECT COUNT(*)
FROM PS_DEP_EXCEL_TAO
The field COUNT_1 is only 3 digits...so I would assume only 999 records at a time can be processed.
Now the other issue you will have is deposits in limbo, the first line of peoplecode in AR_EXCL_EDIT.GETDEP2 reads:
&WHERE_CLAUSE = " WHERE ERROR_FLG = 'N' AND ERROR_FLG1 = 'N' AND PROCESS_INSTANCE = 0 ";
So update the process instance back to zero like so:
UPDATE PS_DEPOSIT_EXCEL
SET PROCESS_INSTANCE = 0
...then the records should pick back up. So my thoughts are to set the process instance back to zero then have the user process no more than 999 deposits at a time.
On a different subject, if you are looking for a change in jobs, please visit the PeopleSoft Developer Jobs site: http://jobs.psoftdev.com/ or simply click the JOBS link at the top of this page.
Error:
Stmt #: 1603
Error Position: 0
Return: 8601 - Numeric value out of range (SQLSTATE 22003) 0
Failed SQL stmt:SELECT COUNT(*) FROM PS_DEP_EXCEL_TAO
ABENDED at Step AR_EXCL_EDIT.MAIN.SETCNT1 (SQL) -- RC = 8601 (108,524)
Cause/Solution:
From what I see per the original error, the actual code in AR_EXCL_EDIT.MAIN.SETCNT1 is:
%SelectInit(COUNT_1)
SELECT COUNT(*)
FROM PS_DEP_EXCEL_TAO
The field COUNT_1 is only 3 digits...so I would assume only 999 records at a time can be processed.
Now the other issue you will have is deposits in limbo, the first line of peoplecode in AR_EXCL_EDIT.GETDEP2 reads:
&WHERE_CLAUSE = " WHERE ERROR_FLG = 'N' AND ERROR_FLG1 = 'N' AND PROCESS_INSTANCE = 0 ";
So update the process instance back to zero like so:
UPDATE PS_DEPOSIT_EXCEL
SET PROCESS_INSTANCE = 0
...then the records should pick back up. So my thoughts are to set the process instance back to zero then have the user process no more than 999 deposits at a time.
On a different subject, if you are looking for a change in jobs, please visit the PeopleSoft Developer Jobs site: http://jobs.psoftdev.com/ or simply click the JOBS link at the top of this page.
AR_EXCEL_PAY_UPLOAD: A fatal PeopleCode SQL error occurred
Using as an example PeopleSoft Financials 9.0 and PeopleTools 8.49...
Symptom: AR_DEPOSIT_EXCEL_ADD - AR_EXCEL_PAY_UPLOAD stuck in a working status.
Error:
Fatal SQL error occurred. (2,125)
FUNCLIB_AREIP.DEPOSIT_ID.FieldFormula
Name:deposit_excel_edit
PCPC:2139
Statement:37
Called from:AR_DEPOSIT.DepositExcel.OnExecute
Name:OnNotify
Statement:8
Cause/Solution:
A scenario I encountered that caused this issue was the date and dollar amount fields were not formatted. Simply put the date fields in the correct YYYY-MM-DD format and the dollars amounts number and decimal only...no commas or demon signs 99999999.99.
To get this queue unstuck, you will may have to inactivate the domain after brining down the Pub/Sub and delete the queue AR_EXCEL_PAY_UPLOAD. Else it will go back into a working status once everything is brought back up.
On a different subject, if you are looking for a change in jobs, please visit the PeopleSoft Developer Jobs site: http://jobs.psoftdev.com/ or simply click the JOBS link at the top of this page.
Symptom: AR_DEPOSIT_EXCEL_ADD - AR_EXCEL_PAY_UPLOAD stuck in a working status.
Error:
Fatal SQL error occurred. (2,125)
FUNCLIB_AREIP.DEPOSIT_ID.FieldFormula
Name:deposit_excel_edit
PCPC:2139
Statement:37
Called from:AR_DEPOSIT.DepositExcel.OnExecute
Name:OnNotify
Statement:8
Cause/Solution:
A scenario I encountered that caused this issue was the date and dollar amount fields were not formatted. Simply put the date fields in the correct YYYY-MM-DD format and the dollars amounts number and decimal only...no commas or demon signs 99999999.99.
To get this queue unstuck, you will may have to inactivate the domain after brining down the Pub/Sub and delete the queue AR_EXCEL_PAY_UPLOAD. Else it will go back into a working status once everything is brought back up.
On a different subject, if you are looking for a change in jobs, please visit the PeopleSoft Developer Jobs site: http://jobs.psoftdev.com/ or simply click the JOBS link at the top of this page.
Thursday, December 1, 2011
Old PeopleTools need Old ExcelToCI
I attempted to use an ExcelToCI template delivered with PeopleTools 8.49 against an old CRM 8.8 install using PeopleTools 8.43. The message I got returned was invalid userid password.
Looking at the OS authentication log, I see that the login credentials are not being passed with the PeopleTools 8.49 ExcelToCI hitting an older PeopleTools version 8.43. So, rather than dig through VBA, I pulled the delivered ExcelToCI template that came with PeopleTools 8.43. I entered the connection information and clicked "Build New Template". I successfully connected.
Subscribe to:
Posts (Atom)