Data load in PBCS with FDMEE


I have been trying from long to work on Integration of FDMEE and PBCS to load data as part of automation process. So here you go with complete steps.

Using FDMEE, you must register the source system from which you want to import data. For Oracle Planning and Budgeting Cloud, it is a file-based source system. FDMEE creates a file-based source system automatically when you install and configure the product. You must also register the target application (for example, Planning) to which you want to load the data from one or more source systems.

In this tutorial, we take source data from a data file that we downloaded from an Enterprise Resource Planning (ERP) source ledger and load the data to a Oracle Planning and Budgeting Cloud application.

In Oracle Planning and Budgeting Cloud Service Workspace, select Navigate > Administer > Data Management to launch FDMEE.

Launching FDMEE

On the Setup tab, under Register, select Source System.

The Source System Summary grid displays the File source system.

In the “File : Details” grid you can define the URL for drill through.

File: Details grid

  • Note: You can drill to any system that has an externally available URL.

    Under Register, select Target Application. Confirm that the Oracle Planning and Budgeting Cloud application that you want to load data to is included as a valid target application. If it hasn’t been included, you’ll need to add it. Here we see that the FinApp application is set up as a target application.

    TargetApplication

    In the Application Details grid for the target application, you specify the dimension details and application options. The Dimension Details tab shows the dimensions in the Oracle Planning and Budgeting Cloud application. Among other dimensions, this application includes the Account, Entity, Period, and Years dimensions.

    Application Details grid

    The Application Options tab shows the available options for the Oracle Planning and Budgeting Cloud application. If you set the Drill Region flag to Yes, you’ll be able to drill through to the source file or system.

    Application Options tab

    In FDMEE, you create an import format based on the source type that you want to load to the target application. The import format defines the layout of source data.

    In this tutorial, you define the layout of a source data file that includes fields delimited by a comma. The following columns are included in the file:

    1. Account
    2. Entity
    3. Amount
    4. CCID
    5. Period

    The following screenshot displays a portion of the data file, TrialBalAug2013.csv:

    TrialBalAug2013.csv

    In the import format, you define the location of these columns and map them to dimensions in the target application. In this tutorial, you also define the CCID dimension as an attribute dimension in the import format.

    To create the import format, perform the following steps:

    1. Under Integration Setup, select Import Format.
    2. On the Import Format page, click Add to add an import format. Under Details, enter the import format name (OperationsIF), source system (File), file type (Delimited), file delimiter (Comma), and target application (FinApp). You also specify the URL for drill through.

    alt description here

    In the Mappings grid of the import format, you map the columns in the source data-load file to the dimensions in the target application. You add the CCID source column as an attribute dimension in the import format. By including the CCID in the data-load file and import format, you can drill back to the source environment.
    The currency is not included in the data-load file, but you define the default currency, USD, in the import format

    Application Options tab

    After defining the import format, you create a location and specify the import format for the location. The location combines related mapping and data load rules into a logical grouping.  You also review the period and category for the data load.

    Perform the following steps to add a location and review the period and category definitions:

    1. Under Integration Setup, select Location, and click Add to add a location

    Location grid

    In the Details grid, define the location name (Operations) and the associated import format (OperationsIF). The system automatically populates the Target Application (FinApp) and Source System (File) for you

    Details grid

    Under Integration Setup, select Period Mapping to review the period definitions on the Global Mapping page.

    You define period mappings in FDMEE to map your source system data to Period dimension members in the EPM target application. You can define period mappings at the Global, Application, and Source System levels. In this tutorial, we will load data to the Aug-13 time period.

    Period Mapping

  • Note: If the periods to which you want to load data do not exist, you must create them.

    Under Integration Setup, select Category Mapping to review the category definitions. You define category mappings to map source system data to target Scenario dimension members.
    In this tutorial, you load data into the Current category.

  • Period Mapping

    Note: If the categories to which you want to load data do not exist, you must create them.

    You create data load mappings in FDMEE to map source dimension members to their corresponding target application dimension members. You define the set of mappings for each combination of location, period, and category to which you want to load data.  Perform the following steps to define the data load mappings:

    In FDMEE, click the Workflow tab. Under Data Load, select Data Load Mapping.

    Data Load Mapping

  • The Data Load Mapping page is displayed.

    You must select the Point of View (POV) to define the data load mappings for a specific location, period, and category. At the bottom of the page, click the current location name and define the POV in the Select Point of View dialog box. In this tutorial, you select the Operations location, Aug-13 period, and Current category.

  •           Select Point of View

    On the Data Load Mapping page, define the mappings for the Entity, Version, and Account dimensions.
    In this tutorial, you define an Explicit mapping for the Entity dimension to map the source value, 1, to the target entity, Operations.

    Data Load Mapping page for the Entity dimension

    You define a Like mapping for the Version dimension to map any source value to the target version, BU Version_1.

    Data Load Mapping page for the Version dimension

    You also define Like mappings for the Account dimension to map source values to target accounts. For example, all source account values that begin with 14 are mapped to the target account, Inventory. The source data file includes accounts 1410 and 1499 that are both mapped to the account member Inventory in the target application.  When you run the data load, the source data for these two members will be summed up in the Inventory account in Oracle Planning and Budgeting Cloud.

    Your next step in FDMEE is to create a data load rule for a specific location and category to define what you want to import from the source system. For example, the data load rule defines the file(s) that you want to import in addition to other details. After creating the data load rule, you execute it to import the data for one or more periods. You then verify that the data was imported and transformed correctly, and then export the data to the target application.

    Perform the following steps to define and execute the data load rule, and then verify that the data was imported and transformed:

    On the Workflow tab, under Data Load, select Data Load Rule.

    Workflow tab

    The Data Load Rule page is displayed with the current POV. In this example, the POV is set to the Operations location, Aug-13 period, and Current category.

    Click Add to add a data load rule. In the Details grid, specify the data load rule name, OperationsDLR, and select the data load file name. In this example, you load the file TrialBalAug2013.csv.

    • Note: If the file information is left blank, the user will be prompted to select a file at run time.

     

    Data Load Rule

    With the rule selected, click Execute.  In the Execute Rule dialog box, you define the options for running the rule. In this example, you specify Import from Source, select Aug-13 as the starting and ending period, select the Replace import mode, and click Run.

    You only check the box labeled “import from source” so you can look at the data and the mapped results in the workbench prior to loading the data to Oracle Planning and Budgeting Cloud.  After everything is confirmed, additional data imports can load to the workbench and export to Oracle Planning and Budgeting Cloud in the same step.

    Execute Rule

    Note: When you import source data, FDMEE imports and also transforms (validates) the data by using the data load mappings that you defined.

    An Information dialog box displays your process ID.

    Information

     

    • Note: To verify the status of your process, you can navigate to Process Details. A green check mark indicates success for your process ID.

      Under Data Load, select Data Load Workbench to see the results of the data load and the mapping process in Data Load Workbench.

    Data Load Workbench

     

    • The Load Data tab displays the imported data. At the top of the page, the Import and Validate tasks display a gold fish, which indicate a successful import and validation.

      Note: During validation, FDMEE applies your data load mappings to map source members to target members. When validation errors occur during the Validate task, a Validation tab displays the unmapped source members. You must review the unmapped source members and then, in the Data Load Mapping task, adjust the mappings to correct all errors. After correcting the errors, execute the data load rule again and check the results in Data Load Workbench. You must iterate between adjusting the data load mappings, importing the data, and viewing the results until you are satisfied that they include the rows that you want to load to the target application.

    • After a successful load, click Export to load the data to the target application. Select the desired load options, and then click OK.

    Execute Rule

    When complete, the icon will change to indicate a successful load.

    Information

    Let’s now look at the data that you loaded to the target application. In Oracle Planning and Budgeting Cloud, we open a form to verify that the data was loaded, and then we confirm that we can drill through from the Oracle Planning and Budgeting Cloud form to the source system.
    In Oracle Planning and Budgeting Cloud, perform the following steps to verify the data load and the drill through:

    Open a form in the Oracle Planning and Budgeting Cloud application that contains the accounts for which you loaded data. The data form displays data for the Operations entity, Aug period, FY13 year, Current scenario, BU Version_1 scenario, and USD currency. The form displays the loaded data.

    FinApp - TrialBal tab

     

    • You also notice an icon in the upper-right corner of the data cells indicating that you can drill on the cells to navigate back to the source.

      Right-click on the Inventory data cell, and select Drill Through.

    Drill Through

    Then click Drill Through to source to start the drill-through process.

    Drill Through to source

    The first step in the drill-through process displays the source rows that comprise the Inventory amount in Oracle Planning and Budgeting Cloud.  Note that two rows (1410 and 1499) from the source data-load file were loaded to the same account in Oracle Planning and Budgeting Cloud.

    Drill Through Summary

     

    • From here you can click on an amount to display the source data-load file or drill-through to the source system.

      In the Drill Through Details grid, click the amount for the 1499 row, and select Drill Through to Source to drill through to the source system; in this case, Oracle E-Business Suite. Because you included the CCID in the data-load file, you can drill-through to the original data in Oracle E-Business Suite.

    Drill Through Details

    The first time you access this source system, you are prompted to enter a user name and password.

    This will be prompted to ERP data source with respective code combinations.

     

    That’s it . Queries and comments awaited.

    Thanks.

     

     

     

     

    Advertisements

    Leave a Reply

    Fill in your details below or click an icon to log in:

    WordPress.com Logo

    You are commenting using your WordPress.com account. Log Out / Change )

    Twitter picture

    You are commenting using your Twitter account. Log Out / Change )

    Facebook photo

    You are commenting using your Facebook account. Log Out / Change )

    Google+ photo

    You are commenting using your Google+ account. Log Out / Change )

    Connecting to %s