FDMEE

Configure: Integration:
• System settings • Import format
• application • Location
settings • Period
• security mapping Data load setup:
Register:
settings • Category • Logic group
• source system
• User settings mapping • Check rule
• Target
group
Application
• Check entity
group

Reports: Batch:
Reports definition Batch definition
Profile type:
Specifies the type of data source or connection profile that FDMEE will use to extract data from your source system (in this case, EBS) and load it into your
target EPM application (Hyperion Planning). It determines the underlying technology or method FDMEE employs to establish connectivity and process data from the source.

• In FDMEE, the Profile Type helps configure the integration environment by aligning it with the nature of your source system.
• For integrating ERP systems like EBS with EPM applications, the Profile Type dictates how metadata and data are accessed and handled.

• Options:
When you look at the Profile Type dropdown under System Settings, you’ll typically see options like:

1. File - flat files (e.g., CSV, text files). This is a common choice for manual file-based integrations.

2. ODI - Oracle Data Integrator, underlying engine for FDMEE. Leverages ODI’s capabilities for connecting to and extracting data from various systems, including ERPs like EBS.

3. POV- Point of View, organises data into target application as user-specific dimensions mapped. IT extracts subset of data.

4. Other specific ERP-related options - Depending on your FDMEE version and configuration, additional options tailored to specific ERP systems (e.g., Oracle ERP Cloud, SAP, etc.)

Profile Type shifts the focus of the system to a metadata-driven or user-defined perspective (POV) for managing data loads, rather than a purely source-system-driven approach (like ODI) or file-based input.

• For this specific scenario—integrating EBS (an ERP) with Hyperion Planning (an EPM application)—the ODI Profile Type is most relevant.
Because:
• ODI has prebuilt connectors which says how to extract metadata and transactional data from the source system,
• It manages seamless data transfer between source and target behind the scenes
• Supports drill-back and write-back.

• By setting the Profile Type to ODI, you’re preparing FDMEE to handle the technical complexity of pulling data from EBS (e.g., General Ledger data) and mapping it to Hyperion Planning’s
dimensions (e.g., Account, Entity, Period). It’s a foundational step before you dive into defining import formats, locations, and data load rules. The ODI Profile Type might feel abstract, but
think of it as the "engine selector" for your integration. For EBS and Hyperion Planning, ODI is the right engine to drive the process.
1. The Application Root Folder can only be specified in System Settings when the Profile Type is set to File.
• The Application Root Folder defines the default directory where FDMEE looks for these files or stores them during the data load process (e.g., inbox, outbox, or archive folders). You must specify this
folder path in System Settings to tell FDMEE where to read/write files.
RDBMS of FDMEE
----------------------------------------------------------------------------------------------------------------------------------------------------------------------- Flat file
(staging, Target (Hyperion
(in Application Root Planning).
validation,
Folder)
2. In that case ‘create location folder’ will be set to YES. transformation)

• A Location is a grouping that determines how data is extracted from a source, transformed using an import format, and loaded into a target application.
• Each Location in FDMEE has an associated Location Folder, where the system temporarily stores files related to data loads for that Location.
E.g.: Loading GL data from an Oracle ERP system into Hyperion Planning and import format is Fixed File Format (mapping ERP data to Planning). Then Location Folder is a subfolder within the ARF, but it is tied to a specific
location in FDMEE. It is created under ARF\Inbox\Location_Name when you run a data load. It is used for storing source files and other processing files specific to that location. Since it is location-specific, it allows
automation, meaning different locations can have different automation rules without affecting others.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

3. Archive Mode Controls how files are handled after processing.

• Enabled: Moves processed files to an archive folder (useful for tracking), Disabled: Leaves the files in the location folder (not recommended).
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
4. Excluded File Upload Wildcards defines file patterns that should be ignored when uploading files.
• Example: *.tmp, ~*.*, *.bak If a file matches this pattern, FDMEE won't process it.
• Useful for preventing unwanted or temporary files from interfering with data loads.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
5. Batch Size determines the number of records processed at a time during a data load.
• Larger batch size = Faster processing, but may consume more memory.
• Smaller batch size = Slower, but prevents performance issues.
• Typical values: 1000, 5000, 10000 (depends on system capacity).
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6. File Character Set defines the encoding used for reading data files.
• Common values: UTF-8 (default, supports all characters), ISO-8859-1 (for older Western files), Shift-JIS (for Japanese characters).
• Ensures special characters (like ₹, €, ñ) are read correctly.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

7. Encrypted Password Folder

• A secure location where encrypted credentials for external systems are stored.
• Used when connecting to secure FTP, databases, or cloud sources.
• Instead of storing plain-text passwords, FDMEE encrypts them for security.
For Manual File Loads (Using INBOX) [FDMEE does not support automatic processing from the INBOX folder because INBOX is meant for manual uploads.]
• User places the file in INBOX (<FDMEE_ROOT>/inbox/).
• User must select the Import Format, Location, and Data Load Rule in FDMEE before running the process.
• Import Format → Defines file structure (columns, mappings).
• Location → Defines source and target system.
• Data Load Rule → Links the file to the specific import format & target application.
• User runs the data load → FDMEE extracts, transforms, and loads the data.
• File is archived after processing.
• ✅User action is required to select Import Format, Location, and Data Load Rule in FDMEE before processing.

For Automated File Loads (Using ODI, Scripts, etc.)

• An external system (ODI, FTP, EBS process, etc.) places the file in the LOCATION folder
(<FDMEE_ROOT>/locations/<Location_Name>/).
• A batch/script/ODI process triggers the Data Load Rule automatically.
• Import Format and Location are pre-configured in the Data Load Rule.
• Since the rule is predefined, the system knows which Import Format and Location to use.
• FDMEE automatically processes the file and loads the data.
• File is moved to the Archive folder after processing.
Profile Type: POV*
When the Profile Type is set to POV in FDMEE, it means that the data load settings will be controlled by the Point of View (POV) rather than
fixed values.
-------------------------------------------------------------------------------------------------------------------------------------------------------
1. Default POV Location: default Location when processing data in POV mode.
• Every Location in FDMEE is linked to a Source, Import Format, and Target, so setting this means FDMEE knows where to pull data from by default.
• Example: If you set SAP_GL as the Default POV Location, then whenever FDMEE runs a POV-based load, it will assume data is coming from SAP_GL unless
changed.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2. POV Period defines the time period for which data is being processed.
• It ensures that the data loaded is relevant to the correct period.
• Example: If the POV Period is set to Jan-2025 by user, then FDMEE will look for and load data related to January 2025 only.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
3. POV Category represents the scenario/version of the data being processed.
• In Hyperion Planning or HFM, the Category is used to distinguish Actuals, Budget, Forecast, etc.
• Example: If POV Category is Forecast, then FDMEE knows that the data should be loaded into the Forecast version of the target system.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
4. Global POV Mode
• Controls whether the POV settings are locked globally or customizable per user session.
• Enabled → The same POV values (Period, Category, Location) apply for all users.
• Disabled → Users can modify their POV for specific data loads.
• Example:
• Global POV Mode ON → All users will see Jan-2025, Forecast, SAP_GL as default values.
• Global POV Mode OFF → Users can change the POV to Feb-2025, Actual, ORACLE_AR, etc.
• Import Format is mainly used to define how the file is read—it specifies which column in the file contains the Period and Category.
• POV settings tell FDMEE which specific Period and Category to use at runtime, overriding or complementing the Import Format.

Example Scenario

🔹 Case 1: Using Import Format Only

•You have a file with data for Jan-2025, Forecast in Column 2 & 3.
•Your Import Format maps Column 2 → Period, Column 3 → Category.
•When FDMEE loads the file, it picks up the Period & Category only from the file itself.
•🚨 Problem? If the wrong file is uploaded, FDMEE loads incorrect data!

🔹 Case 2: Using POV Settings

•You set POV Period = Jan-2025 and POV Category = Forecast.
•FDMEE now ignores whatever is in the file and uses the POV values.
•✅ Advantage? Even if a user uploads the wrong file, FDMEE only loads Jan-2025, Forecast data.

Key Takeaways
1.Import Format is for file structure, while POV is for execution control.
2.Import Format extracts Period/Category from the file, but POV can override it.
3.Using POV ensures strict control over which Period/Category is loaded, preventing mistakes.
Example of an Import Format

🔹 Raw File (CSV) 🔹 Import Format Definition

Column 1 Column Column Column Column 1 Account
2 3 4

Column 2 Period
Account Jan-2024 1000 Actual
4100 Jan-2024 500 Actual Column 3 Amount
4200 Jan-2024 300 Actual
Column 4 Category

So, FDMEE now knows:

✅ Column 1 = Account → 4100, 4200
✅ Column 2 = Period → Jan-2024
✅ Column 3 = Amount → 500, 300
✅ Column 4 = Category → Actual
 Final Takeaway
✔Import Format only defines how to read the file and extract values.
✔ It does not decide where the data goes (Location) or which period/category should be loaded (POV).
✔ POV and Data Load Rules are what actually control the execution.

Source Column Mapped To

Col 1 Col 2 Col 3 Col 4
Column 1 Account
Account Jan-2024 1000 Actual
Column 2 Period
4100 Jan-2024 500 Actual
Column 3 Amount
4200 Jan-2024 300 Actual
Column 4 Category