Fatal SQL Error on Clicking Document Status for Receipts and Return to Vendor
(Doc ID 2057537.1)
Last updated on AUGUST 20, 2020
Applies to:
PeopleSoft Enterprise SCM Purchasing - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
Scenario 1
1)- Navigate to Main Menu > Purchasing > Receipts > Review Receipt Information > Document Status
2)-Search for the Receipt Number.
3)-Click on the Receipt Number Link.
Fatal PeopleCode SQL Error Occurs.
4)-Click OK.
SQL error in DescribeCol. (2,279) SRM_DOCSTATUS.DocumentStatus.OnExecute
Name:getSqlCount PCPC:24663 Statement:346
Called from:SRM_DOCSTATUS.DocStatusRcv.OnExecute Name:initCounts
Statement:41
Called from:SRM_DOCSTATUS.DocStatusRcv.OnExecute Name:DocStatusRcv
Statement:3
Called from:SRM_DOCSTATUS.DocStatusViewController.OnExecute
Name:getDocInquiry Statement:26
Called from:SRM_DOCSTATUS.DocStatusViewController.OnExecute
Name:initDocStatus Statement:57
Called from:PRCR_DS_INQ_WRK.FUNCLIB.FieldFormula Name:InitDocStatus Stat
During the execution of SQL, an error occurred in the DescribeCol subroutine.
The preceding message should have described the details of the SQL being
executed.
Scenario 2
1)-Navigate to Main Menu > Purchasing > Return To Vendor / Supplier > Document Status.
2)-Search for the RTV Document.
3)-Click on RTV Link.
System throws a --A fatal PeopleCode SQL error occurred. Please consult your system log for details.
4)-Click OK.
SQL error in DescribeCol. (2,279) SRM_DOCSTATUS.DocumentStatus.OnExecute
Name:getSqlCount PCPC:24663 Statement:346
Called from:SRM_DOCSTATUS.DocStatusRtv.OnExecute Name:initCounts
Statement:35
Called from:SRM_DOCSTATUS.DocStatusRtv.OnExecute Name:DocStatusRtv
Statement:3
Called from:SRM_DOCSTATUS.DocStatusViewController.OnExecute
Name:getDocInquiry Statement:29
Called from:SRM_DOCSTATUS.DocStatusViewController.OnExecute
Name:initDocStatus Statement:57
Called from:PRCR_DS_INQ_WRK.FUNCLIB.FieldFormula Name:InitDocStatus Stat
During the execution of SQL, an error occurred in the DescribeCol subroutine.
The preceding message should have described the details of the SQL being
executed.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |