R12: Why is PROCESS_ORDER API not progressing line workflow used to "schedule" line?

(Doc ID 1988873.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Order Management - Version 12.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Trx Changes & Cancellations

ACTUAL BEHAVIOR
---------------
When using the Process_Order API to schedule order lines, lines are SCHEDULED as expected but the line workflow
is not progressed and remains at a "Schedule - Eligible" (Notified) status.

Example
----------
Passing the below standard attributes to trigger the API scheduling.

  l_line_tbl (1) := oe_order_pub.g_miss_line_rec;
  l_line_tbl (1).operation := oe_globals.g_opr_update;
  l_line_tbl (1).header_id := 423852;
  l_line_tbl (1).line_id := 10467692;
  l_line_tbl (1).schedule_ship_date := TO_DATE ('17-DEC-2014');


EXPECTED BEHAVIOR
-----------------------
Expect line to be scheduled - SSD (Schedule Ship Date) updated, Schedule Status Code populated etc...but also
expect line workflow to be progressed.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run Process_Order API wrapper script for single example order line.

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