PO ID Disappearing On VCF Payment File Test Upload
(Doc ID 2437498.1)
Last updated on FEBRUARY 03, 2019
Applies to:PeopleSoft Enterprise SCM Purchasing - Version 9.1 to 9.1 [Release 9]
Information in this document applies to any platform.
PO ID disappearing on VCF Payment File test upload
When ran the upload, Load ProCard Stage, the app-engine PO_CCPCRDSTG places the data into the PS_CC_TRANS_EC table.
PO_ID value winds up in a field on that table called DESCR60, while the PO_ID field remains blank.
Oracle/Peoplesoft has a T5 layout and derived work record called CC_VISA_FLO05.
The PO_ID field on the T5 layout is field #32. It is "VS_PURCH_ID", and its dimension is X(50)
It is followed by field #33, "VS_CUSTOMER_CODE," which is X(76)
From VISA, the VCF-4 layout also contains two fields
#32 and #33, and they also have dimensions of X(50) and X(76) respectively.
The VISA layout calls #32, the X(50) field, "CUST CODE/CRI".
And it calls #33, X(76), "PURCHASE ID".
It appears to have the exact reverse idea of what these 2 fields are for.
As per VISA specs #32 should be "PURCHASE ID" and #33 "CUST CODE/CRI".
The issue can be reproduced at will with the following steps:
1. Place Visa-3 file in App. server folder
2. Run Load ProCard Stage
The issue has the following business impact:
Due to this issue, users cannot use Procard process to upload transactions.
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