My Oracle Support Banner

OM: How to make the Modifier Start date same as Blanket Sales Agreement Start Date? (Doc ID 1184997.1)

Last updated on OCTOBER 01, 2019

Applies to:

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


Client will be migrating the Blanket Sales Agreements from their Legacy System (Non Oracle Application) to Oracle Apps - 12.0.4. The Activation Date of the BSA will be a past date. It is observed that the Modifiers automatically created from the BSA will be having its Start Date as System
Date and not the activation date of the BSA from which it got created. Their requirement is that the start date of the Modifier should be same as Activation Date of the BSA and not sysdate as observed. This is needed by them as otherwise the modifier will not get applied to releases created with
activation date as pricing date. If they update the Modifier Start Date manually to the BSA Activation Date, then their issue is resolved, but this is not feasible due to the huge number of BSA that will be created. Client states that they need the modifier start date to be the BSA Activation Date due to this business reason

Is this as per design and if yes what is the work around available?


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

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