PO_DISPATCH.EDX.Step01 Abend Error While Dispatching a Purchase Order (PO) via EDX for Direct Connect Items (Doc ID 1602085.1)

Last updated on JANUARY 11, 2017

Applies to:

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

Symptoms

User is getting an error message while Dispatching a Direct Connect Item using Dispatch Method via Online or Batch Dispatch Process

Error

 

SQLExec: 16 select list items in parameter list, but SQL has 17 select columns. (2,124) PO_DISPATCH. Utilities.LinkedSupplierData.OnExecute  Name:setBillAddress  PCPC:4199  Statement:75

Called from:SCM_PV_PO_DISPATCH.PurchaseOrder.OnExecute  Name:setHeaderMsgData  Statement:75

Called from:SCM_PV_PO_DISPATCH.CxmlPurchaseOrder.OnExecute  Name:XMLPDispatch  Statement:375

Called from:PO_DISPATCH.PO_Dispatch_EDX_Dynamic.OnExecute  Name:dispatch  Statement:34

Called from:PO_DISPATCH.PO_Dispatch_EDX_ALL.OnExecu

 

Process 17815 ABENDED at Step PO_DISPATCH.EDX.Step01 (PeopleCode) -- RC = 8

17815 PO_DISPATCH EDX Step01 PeopleCode 8


Steps to reproduce the issue:


1. Set up a direct connect vendor that requires punchout

2. Ensure Routing Parameters are been set up for direct connect punchout and dispatch

3. Ensure linked supplier set up is done properly

4. Create a new Requisition and punchout to Direct Connect vendor

5. Add a minimum of 2  items to the shopping cart and Check out

6. Go to review and submit link

7. Select Requisition Line 1 and then click the delete button. Line 1 of Requisition is Deleted

8. Save and submit the requisition

9. Expedite the Requisition

10. Check the PO created. Save and Approve the PO. Ensure dispatch type is set to EDX

11. Navigate to eprocurement > Administer Procurement > Dispatch Purchase orders > Batch Dispatcher

12. Select the PO created above and click dispatch PO

13. Ensure output type is selected as Web and PDF for POXMLP

14. Check the PO status on the ePro Manage Purchase Order page show the PO is still in Approved status

15. Check the Log files from Message Log for error message



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms