My Oracle Support Banner

EAP: VNDR_HDR_VW SQL Not Compatible for SQL Server Database Environments (Doc ID 2781260.1)

Last updated on SEPTEMBER 20, 2021

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

The VOUCHER record field order in App Designer is different than the order in a SQL Server environment. The VNDR_NAME_SEQ_NUM is the 5th position in App Designer and it's the last position on the SQL Server database table.

This is not a problem unless you code SQL in views or create a code that does not specifically call out the columns in the SQL statement and instead use something like "SELECT *". The PS_VNDR_HDR_VW, is coded with "SELECT a.* and this goes against all SQL coding standards and this will fail in a SQL server environment. The error below is seen when the PS_VNDR_HDR_VW was executed during Pending Approvals for Purchasing.

ERROR:
Error Position: 0 Return: 8601 - [Microsoft][ODBC Driver 13 for SQL Server]Numeric value out of range
[Microsoft][ODBC Driver 13 for SQL Server]String data, right truncation (SQLSTATE 01004) 0


STEPS:
1. VENDOR record field order in app designer: SETID, VENDOR_ID, VENDOR_NAME_SHORT, VNDR_NAME_SHRT_USR, VNDR_NAME_SEQ.....
2. VENDOR record field order in SQL Server environment: SETID, VENDOR_ID, VENDOR_NAME_SHORT, VNDR_NAME_SHRT_USR, NAME1.....TEMPLATE_ID, VNDR_NAME_SEQ_NUM.
    Field VNDR_NAME_SEQ_NUM is listed last.
3. Run Pending Approvals for Purchase Orders
4. The above error is received

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.