Propagating Majority Of Milestone Notifications For Bulk Orders Are Intended To Be Stopped (Doc ID 3008185.1)

Last updated on MARCH 12, 2024

Applies to:

Goal

The customers implementation of OSM 7.3.0.1.9 generates a lot of milestone notifications. For bulk orders, these milestones overwhelm the customers AIA server.

"Currently at the O2A COM layer, there are two options control how the UpdatesSalesOrder notifications sent from COM to CRM."

1. The O2A_ENRICH_DATA_FLAG flag at the Solution Cartridge Model Variables value determines whether to enrich order level data while sending UpdateSalesOrder notifications to CRM. By setting the value of “disable”, COM stop enriching the data in UpdateSalesOrder notifications.
2. The “orderlifecyclemodule:updateUpstreamRequired” method in the OracleComms_OSM_O2A_CommonUtility/resources/OrderLifecycleModule.xquery determines whether to send UpdateSalesOrder notifications or not. This determines based n ComponentMilestoneMap.xml configuration.

In the customer case, first some indication has to come in the order indicating that whether the order is a bulk order or not. And using that information, the above method needs to be customized as per the customer requirement.

The customer cannot disable O2A_ENRICH_DATA_FLAG as this will affect normal orders that are not part of bulk orders.

Solution

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