EBS: SNO: Demand Report Not Showing Org Code Properly
Last updated on JUNE 23, 2017
Applies to:Oracle Strategic Network Optimization - Version 12.2 and later
Information in this document applies to any platform.
On : 12.2 version, Planning Engine
In the demand report client identified there are two organizations that are not visible (GDM and FDM). Instead, it enters the ITEM CODE as ORGANIZATION CODE which causes issues to the business because
they cannot easily identify to which organization the demand corresponds to.
When the client needs to analyze and report the montly results they need to check the demand value in the grapchic model (which it takes too long to open) and match the demand value to the organization (GDM or FDM) and this is very time consuming and not optimal according to the natural SNO behavior.
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