My Oracle Support Banner

Error Messages When Creating EPro Req From Work Order (Doc ID 2483389.1)

Last updated on NOVEMBER 23, 2019

Applies to:

PeopleSoft Enterprise FIN Maintenance Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

On : 9.2 version, Work Order

Error Messages When Creating ePro Req from Work Order

ERROR 1
-----------------------
Assignment of "" to PV_REQ_SR_WRK.VNDR_LOC failed. (2,119) FUNCLIB_PP.FUNCLIB.FieldFormula Name:SpecialRequestLayout PCPC:8584 Statement:133
Called from:PV_REQ_SR_GOOD.Activate Statement:6

The assignment to the specified field failed.

The failure can be caused by any one of several problems. The new value could be too long to fit into the field, the new value could have too many digits (possibly including a sign) to the left of the decimal point to fit into the numeric field, there could be problems converting the new value to internal format, the field might not be present in the page buffers (rare), or there could be a memory allocation error (very rare).

Review the program for errors. If necessary, run a PeopleCode trace to determine the program that failed. A trace including "Show Assignments to Variables" will trace the new value.

ERROR 2
-------------------------
Field does not exist -- PV_NEWSRCH_WRK.PV_TEXT_FIELD2. (2,104) PV_REQ_LINE_WRK.PV_INSERT_LINE.FieldChange PCPC:51177 Statement:708

A reference to a record.field name was made and the record.field name was not found to exist. Verify that the field exists on the page in which the PeopleCode program is being executed.

Review the program for errors. If necessary, run a PeopleCode trace to determine the program that failed.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Open a work order and click on schedules tab.
2. Click on add requisition button.
3. Click on continue
4. Click on Special Request tab and click Special Item link. Error message appears
5. Click on add item button and next error message appears.
6. This prevents the requisition from being created.



Changes

 < Internal Only

Documents:

Replication Steps

Unit Testing

Code Change

Internal Only >

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.