Table of Contents

APPLIES TO:.....................................................................................................................................................1
PURPOSE..........................................................................................................................................................1
SCOPE................................................................................................................................................................1
DETAILS.............................................................................................................................................................1
Introduction:............................................................................................................................................................1
Best Practices & Common Mistakes for FBDI Filling and Upload..............................................................................2
Frequently Asked Questions.....................................................................................................................................4
Enhancements..........................................................................................................................................................4
White papers............................................................................................................................................................4

APPLIES TO:

Oracle Demand Management Cloud Service - Version 11.13.20.01.0 and later

Oracle Supply Planning Cloud Service - Version 11.13.20.01.0 and later

Oracle Planning Central Cloud Service - Version 11.13.20.01.0 and later

PURPOSE

This Document provides information about best practices to be followed while filling and uploading FBDI. It also
discusses common mistakes that user make and should be avoided.

SCOPE

The functionality described on this document is applicable to all FBDI used during Collections. This can be used
as a general best practice document for other FBDI other than Collections FBDI too.

DETAILS

Introduction:
This Document provides information about best practices to be followed while filling and uploading FBDI. Many
times error occurs while filling and uploading an FBDI and the best practices document if followed will help in
minimizing errors.

Best Practices & Common Mistakes for FBDI Filling and Upload
1. Always Download FBDI for Correct Release

Always download the correct version of FBDI for your release version. For example if your current Application
version is 20B (11.13.20.04), then always ensure that you have downloaded the FBDI from the 20B Oracle
documentation only. If you continue to use a previous version like 20A or 19D, there are chances that an
additional column might have been added/removed and the FBDI will fail during import because the sequence
of columns have been changed.

FBDI can be downloaded from the below Oracle Documentation Site after selecting the correct version.

https://docs.oracle.com/en/cloud/saas/supply-chain-management /20b/oefsc/supply-chain-
planning.html#supplychainplanningitems-3198

Please also note that the URL will have reference to the version. For example the above URL has ‘20b’ in the URL
hence it is for 20B release.

2. POD Sizing

Significant changes to your usage patterns such as adding many new users or the execution of high volume data
imports may change your pod sizing assessment. Ensure that your Fusion environment has been properly sized
to handle the import data volumes your organization generates along with other operations that are performed
by your users. Before starting a high volume import process or one time data load, you may want to have Oracle
review your sizing. Contact Oracle Support to start this review process.

3. Volume of Records per FBDI File

Do not import more than 100,000 records in a single import or perform more than 5 concurrent import
activities. Ensure the size of the FBDI Zip File does not exceed 250 MB.

4. Filling Date Type Columns in an FBDI

Always ensure when you fill any Date format column, it is populated as YYYY/MM/DD format only. Any other
format will lead to errors for the date column.
 5. Pay attention to ‘Required’ and ‘Optional’ columns

In any FBDI, not all the columns are always required. Please ensure to fill all the ‘Required’ columns. Use the
optional columns to fill only data which you need. A good practice is to perform the 1 st trial FBDI load with lesser
optional columns filled so as to minimize data validation errors. Each column in an FBDI(except text or
comments columns) is validated with business logic during Import.

6. Do not change the name of the CSV file

After filling an FBDI xlsm, users click on ‘Generate CSV File’ macro to generate the CSV/Zip file. Always ensure
not to change the name of CSV and leave it as generated. Changing csv name leads to error during FBDI upload.

7. Always Upload the Zip File (Not CSV) to the UCM Folder
In some FBDI xlsm, after user clicks the ‘Generate CSV File’ macro, only a CSV is generated and in some FBDI a
ZIP file is generated too which contains the CSV. Irrespective of either of the 2, ONLY the zip file generated must
be uploaded to the suitable UCM Folder and not the CSV file.

8. Review the column if ‘Code’ or ‘Name’ is needed

Please pay attention to required columns which say Code or Name. For example M1 maybe the Organization
Code whereas ‘Seattle Manufacturing’ may be the Organization Name.

9. Potential Issues when opening CSV with Excel

Potential issues that might occur include:

 Saving ID fields:
Issue: If you save your CSV file and then reopen it in Excel, IDs and other large numbers are typically
displayed in scientific notation: the product of a decimal number and a power of 10. For example, the
value 123456789012 is displayed as 1.23457E+11.
Cause: By default, Excel displays numbers with greater than 11 characters in scientific notation.
Workaround:
1. Highlight the column containing the value.
2. Right-click and select Format Cells.
3. On the Format Cells dialog box, select the Category Number and set the decimal places to 0.
Click OK.
 Saving date-related fields:
Issue: If you save your CSV file and then reopen it in Excel, date-related fields such as PeriodName are
typically displayed in yy-mmm format. For example, the value 12-16 is displayed as 16-Dec.
Cause: By default, Excel displays date-related numbers in yy-mmm format.
Workaround:
1. Highlight the column containing the value.
2. Right-click and select Format Cells.
3. On the Format Cells dialog box, select the Category Custom and enter the type mm-yy or any
other date format of your choice. Click OK.
 Saving numeric values with greater than 15 digits:
Issue: If your CSV file has a value with more than 15 digits, such as 1234567890123456, then Excel
displays it as 1234567890123450 when the file is opened. Excel replaces the digits beyond 15 with
zeroes.
Cause: Excel supports only 15 digits of precision.
Workaround:
Method 1
1. Highlight the column containing the value.
2. Right-click and select Format Cells.
3. On the Format Cells dialog box, select the Category Text and click OK.
4. Enter the value again in the cell.
Method 2
5. Highlight the cell containing the value.
6. On the Formula Bar, precede the value with an apostrophe. For example, type the value
'1234567890123456 and press enter.
 10. Perform regular purging of Staging Tables for optimal FBDI loading performance

Over a period of time, the volume of data in the Planning Staging tables builds up and may impact any future
new FBDI load. It is a good practice to purge Staging Table Data periodically using the ESS Job ‘Purge Staging
Tables’ so that the FBDI load performance is optimal.

11. Validate records from FBDI columns in the Staging Table columns

In the Oracle documentation, below each FBDI xlsm, there is a control file. Please review the control file for
definition of which table and column in the Staging table is mapped to each of the column visible in the FBDI
xlsm.

12. Ensure FBDI column value does not have extra space or special characters

Often users copy and paste values from another application to the FBDI xlsm. Sometimes while pasting an
additional space or special character may be introduced leading to import error. Please ensure there are no
space or special characters.

Frequently Asked Questions

Enhancements
Not Applicable

White papers
Not Applicable