Download as pdf or txt
Download as pdf or txt
You are on page 1of 1

Copyright (c) 2024, Oracle. All rights reserved. Oracle Confidential.

30143221:Planning Trimming The Forecast Name To Six Characters (Doc ID 2615018.1)

In this Document

Goal
Solution
References

APPLIES TO:

Oracle Supply Planning Cloud Service - Version 11.13.19.04.0 and later


Information in this document applies to any platform.

GOAL

Planning Trimming the forecast name to six characters

When data is extracted from EBS instance, the extraction process is trimming the forecast name to first six characters and
appending it by the org code.

For example:
Forecast name AAA-BBB-CC is getting updated to AAA-BB:ORG and AAA-BBB-DD also trimmed to AAA-BB:ORG in the csv
file.
So different Forecast Names in EBS however they will look the same in Cloud Planning.

This creates confusion for the planners to identify the correct forecast name.
The whole forecast name should come in and not just the first six characters.

SOLUTION

The extract process from EBS is designed to append ORG code because the same designator can be part of two orgs. So to
differentiate, ORG Code is appended.

The unique key on eBS side is ORGANIZATION_ID, FORECAST_DESIGNATOR.


So the same forecast name can be present in different organizations. Each can have different demand class,
customer/customer sites, etc.
If the forecasts are extracted as is, the collection might end up rejecting 1 set from a different organization.

So EBS Extraction was designed to sub-string FORECAST_NAME to 6 chars and then append ORG to accommodate 10
chars.

The following Enhancement Request is in place to change this behavior to allow the entire Forecast Name
(FORECAST_DESIGNATOR) to be extracted and then collected into Cloud SCP:
Enh 30143221 - ISSUE WHEN COLLECTING EXTERNAL FORECAST FROM EBS INTEGRATION

REFERENCES

Didn't find what you are looking for?

You might also like