When you create a journal in FCCS, you have to enter the below fields:

  • Journal Label and description
  • Point of View
  • Adjustment amount
  • Optional: Journal Group.

 

But rather than creating a journal, you can load Journals using data management by following the below steps:  

1. Import Format:

When you define the import format for loading journals, you need to add two rows in the import format detail mapping; Journal Label row and journal description row. The below are the steps on how you can add them.

  • From the Import Format Detail Mapping grid, select the source column and click the Add drop-down. Note: The file type is Delimited – Numeric Data.

  • Select the Journal Label Row, and enter the journal ID which will used as the journal label when loading to the application in the Expression field, also as per oracle documentation the below characters cannot include in the label name (., +, -, *, /, #, @, “, {})
  • Additionally, you can add an expression label; label and group; or no label or group
  • As the below LABEL=<Label>#GROUP=<Group>Example: LABEL=JE100GROUP=Azdan
    • Note: If the journal ID field is null, Data Management creates the journal label as JL<loaded> automatically.

     

    • Click add and insert the description row twice. But why? as per Oracle documentation: The journal description must be entered in “the Description 2” row, so you must add the description row 2 times, and then you can delete the Description 1 row if not needed
      • Finally, add other import format mappings for dimensions as needed
2. Locations:
  • After saving the import format, make sure that you associate it with a location, no special setup
3. Data Load Rule:
  • Usually, the user setups the data load rule after completing data load mapping. However, in this case, the user needs to start with data load rule because it will generate auto mapping which will help to complete the process.
  • Journals are loaded by defining a load type of “Journal” in the “Load Type” field in the “Target Options” tab.

  • Optionally, you can specify the status of the journals in the Journal Status field in the Target Option tab (Working – Submitted – Approved – Rejected)
  • After creating the data load rule for the journal load, Data Management automatically creates a data load mapping for the dimension “Data Source”.

4. Data Load Mapping:
  • Complete the mapping for any dimension as per your flat file and application design.
5. Flat File Format:
  • As an example, I will use the below a CSV comma delimited file to load journals :

  • So how data management differentiate between credit and debit? As per Oracle documentation; when loading journals to an Oracle Financial Consolidation and Close Cloud target, consider that Data Management does not determine the account types or select the credits/debits. All positive numbers are loaded as credits and all negative numbers are loaded as debits
  • Note: If you need to designate other credit or debit signs for your account type, use the change sign feature in Data Load Mappings
6. Execute Data Load Rule:
  • Run as usual steps no special processes

7. Check Created Journals: