My Oracle Support Banner

How To Setup The Generation Of An OXD (Order Output-For Sales Orders Auto-Created By WMS) File For New Crossdock Orders (Doc ID 2636779.1)

Last updated on FEBRUARY 07, 2020

Applies to:

Oracle Warehouse Management Enterprise Edition Cloud Service - Version 19.3 and later
Information in this document applies to any platform.

Symptoms

Attempting to set up a Scheduled Job to create the Order Output File (OXD) (For Sales Orders auto-created by WMS), fails unless the Order is specifically noted in the Job parameter.

There are three scenarios that were attempted:

1) Scheduled job parameter values (Order Nbrs = ORD001, Origin Code = S, Interface Format = 4).
Outcome: Generates an OXD file for only the specific order = ORD001.

2) Scheduled job parameter values (Order Nbrs = ORD*, Origin Code = S, Interface Format = 4).
Outcome: The job ends with 'Completed' status, but no OXD file gets generated. The following error shows up in the log file:

"Exception processing order ORD*: OrderHdr matching query does not exist."

3) Scheduled job parameter values (Order Nbrs = *, Origin Code = S, Interface Format = 4).
Outcome: The job ends with 'Failed' status. No OXD file gets generated. The following error shows up in the log file:
"Error: Call to generate_order_files.run failed. Error: Exception in generate_order_files.run: invalid literal for int() with base 10:''

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


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