My Oracle Support Banner

Why PO using Dispatch Method EDX Fails with Error? (Doc ID 1420581.1)

Last updated on FEBRUARY 27, 2019

Applies to:

PeopleSoft Enterprise SCM eProcurement - Version 9 to 9 [Release 9]
Information in this document applies to any platform.

Goal


How to resolve below error which occurred after punchout and PO Dispatch via EDX:

 

SETID not setup for automatic numbering (18022,112)

Error saving Component Interface. {PV_PO_DISPATCH} (91,37)

SQL.Fetch: object isn't open on a select. (2,288) = PV_DISPATCH.MAIN.GBL.default.1900-01-01.CALLCI.OnExecute PCPC:1403 = Statement:29 

Process 179 ABENDED at Step PV_DISPATCH.MAIN.CALLCI (PeopleCode) -- RC = =3D 8 (108,524)



Solution

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
Goal
Solution


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