E1: 42: Real-Time Event Filter (P4230) Needs to Filter By Next Status not Last Status (Doc ID 2651333.1)

Last updated on OCTOBER 25, 2022

Applies to:

Symptoms

Client is unable to filter out non-EDI Sales Order Events using RTSOOUT, RTSOOUT2 or RTSOOUT3 using the Sales Order Real-Time Event Filter (P4230) if the order line was originally backordered which permanently sets the Last Status to 900.

This is because Sales Order Real-Time Event Filter (P4230) only filters on Last Status (F4211.NXTR) and does not allow filtering by Next Status (F4211.NXTR).

The issue can be reproduced at will with the following steps:

1. Go into Sales Order Real-Time Event Filter (P4230) and setup filters by various Last Statuses such as:
   1. 520 (Sales Order Entry)
   2. 540 (Pick Slip Print)
   3. 560 (Ship Confirm)
2. Create a two line Sales Order
   1. Line 1 has available inventory and status is set to Last Status 520 and Next Status 540
   2. Line 2 does not have available inventory and goes on backorder at Last Status 900 and Next Status 540
3. Real-Time Events does the following:
   
   1. Line 1 is filtered out and not sent to the customer
   2. Line 2 (Last Status 900) is NOT filtered out and is sent to the customer.
   3. The client does not want the change to Line 2 sent to the customer, because it is not an EDI event.
4. Inventory is received for Line 2 of the order.
5. Backorder Release (R42118) is run hard committing the inventory on Line 2
   
   1. On Line 2 the Last Status Remains at 900 and the Next Status is advanced to 560
6. Real-Time Events does the following:
   1. Line 2 is not filtered out and is sent to the customer as a Real-Time Event.
   2. The client does not want the change to Line 2 sent to the customer, because it is not an EDI event.
      
      

Cause

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