11.5.5 

Multi-Table Journal Import

The performance for importing data into Oracle General Ledger has been dramatically improved by enabling Journal Import to process data from multiple interface tables. You can now import data in multiple parallel streams with each stream making use of a separate import table.  

OFA Incremental Data Load

The Oracle General Ledger / Financial Analyzer link has been enhanced to enable the loading of incremental data changes from Oracle General Ledger to Oracle Financial Analyzer during any given close cycle.  With the Incremental Data Load feature, you no longer need to wait until the monthly period is closed to perform data loads.  After loading an initial full balance extract for a period, you can subsequently load only the incremental changes to account balances when changes occur, and update account balances in Oracle Financial Analyzer without having to run a full balance extract again for that period. Oracle General Ledger tracks the changes to account balances after the initial full balance extract so they can easily be loaded into OFA for reporting and analysis.  This enables you to assess your financial position in a more timely and efficient manner.  

Revaluation Gain/Loss Tracking by Cost Center

The Revaluation program has been enhanced to enable you to optionally track foreign currency unrealized gains or losses by cost center, in addition to the balancing segment.  This enhancement allows you to easily see the impact of exchange rate differences during revaluation on a company-by-company, and cost center-by-cost center basis.   For companies using Multiple Reporting Currencies (MRC) to achieve SFAS52 remeasurement compliance, Oracle General Ledger automatically remeasures the unrealized gain or loss journal entry lines in your primary set of books to your corporate functional currency reporting set of books and also offsets at the balancing segment and cost center level. This capability enables you to easily track detail unrealized gain or loss balances for in-depth reporting and analysis in both your local and corporate functional currencies..  

MRC Euro Historical Balances Conversion

For companies using MRC to transition to euro with the 1-2-3 EFC (Euro-as-Functional-Currency) process, you can now initialize a new euro reporting set of books that captures your historical balances prior to your first MRC period.  You can choose to convert the balances for any number of historical periods from your primary set of books to the new reporting set of books.  This flexibility is especially important when you decide to implement MRC in the middle of the fiscal year because it enables you to have a complete fiscal year of financial data in your reporting set of books for reporting and analysis.  This feature enables you to perform detail analysis on euro balances even for periods prior to your first MRC period.   

FSG Performance Improvement

The Financial Statement Generator (FSG) has been enhanced to increase the performance level of FSG reports that contain account assignments with a large number of parent segment values and child segment value ranges.    

11.5.7  

Account Hierarchy Manager

The Account Hierarchy Manager (AHM) is a new feature in Oracle General Ledger that allows you to create, maintain, and view account hierarchies over the internet.  The Account Hierarchy Manager is similar to the Account Hierarchy Editor in Applications Desktop Integrator, except you do not have to install additional software on your client PC to obtain a rich, graphical user-interface for manipulating chart of accounts structures and hierarchies. You can access the Account Hierarchy Manager directly from the general ledger menu.  The drag and drop user interface allows you to move segment values from one hierarchy to another to build and modify your chart of accounts segment hierarchies.  This enables rapid reorganization of business entities (cost centers, accounts, etc.) with the results immediately reflected in the organization structure, financial statements, and internal reports.  You can also create new child segment values, parent segment values, and rollup groups using icons or your right mouse button. The advanced query windows allow you to quickly find segment values by value or description using different search criteria.  You can also limit your search to find only specific values, only parent values, only child values, or child values not assigned to a parent value. You can instantly export your segment hierarchies to a delimited file to create “what if” scenarios in a spreadsheet and print changes before actually making changes in Account Hierarchy Manager. You can control the level of access for making changes to segment values and hierarchies through a profile option.  You can grant view access only or read and write access.  For example, you can grant read and write access to the selected individuals in your organization who have the responsibility to maintain segment value hierarchies, while other users have read-only access to just view the hierarchies. Because AHM is accessible from Oracle General Ledger, it supports all the languages supported by Oracle Applications. All AHM messages, field prompts, and segment value descriptions are displayed in the languages that you have installed with your Oracle Applications. 

Journal Import Adjusting Period Support

Journal Import has been enhanced to allow data from external systems to be imported into adjusting periods.  You are no longer restricted to using non-adjusting accounting periods when importing data from the interface table.  You can import actual, budget, and encumbrance data into adjusting periods.  You can also import reversing journals into adjusting periods. 

Open Period Program Compatibility Across Sets of Books

You can now open periods for multiple sets of books simultaneously.  This significantly improves the performance of companies with multiple sets of books in a single database instance.  Instead of having to wait for the Open Period program to complete in each set of books before the next set of books can open its periods, multiple sets of books, including any combination of Average Daily Balance (ADB) and standard sets of books, can run the Open Period program simultaneously.  

Budget Programs Compatibility Across Sets of Books

You can now perform parallel budget processing across multiple sets of books when performing budget uploads, budget posting, and budget formulas.  This significantly improves budget performance.  Instead of having to wait for each set of books to complete one of the budget processes before the next set of books can begin, multiple sets of books can run the same process or any combination of budget uploads, budget postings, or budget formulas simultaneously.  

Segment Value Security for Journals Reports

The same security rules which secure access to key data for general ledger functions and protects financial information from being viewed by users without access has been expanded to include standard Journals reports.  Segment Value Security was first introduced in Release 11i for the following three types of general ledger standard reports: trial balance reports, account analysis reports, and general ledger reports. Now segment value security also applies to Journals reports. 

FSG Hierarchical Security Support

FSG reports now use the same segment value security rules based on parent hierarchies as those defined for online inquiries and most major general ledger standard reports.  This allows you to protect sensitive financial information from being viewed in FSG reports by any responsibility that has security rules assigned.  Hierarchical Security was first introduced in Release 11.5.6 to allow you to create segment value security rules with parent values and automatically apply the rules to all of the child values within the parent hierarchy.  This significantly simplifies the definition and maintenance of complex security rules.  When you add new segment values, you do not have to update the security rules if that value is assigned to a parent value with security rules already defined.  If you define a security rule to include or exclude a parent segment value, any FSG report that you run from the responsibility to which you assigned this rule will include or exclude data for the parent segment value and its child values accordingly.  Any additions or changes to your organization rollup structures will be reflected in both your reporting and security hierarchies simultaneously. 

FSG Report Set Enhancements

The FSG report set functionality has been enhanced to allow multiple users to more effectively share the usage of the same report set definition and also provide added viewing and publishing security on each individual user’s report set output. In ADI, each user can view a full history of all report set outputs that he has generated.  This allows the user to select and publish any report set previously generated without having to re-generate it again.  In addition, each user can only publish and view report set output that he has generated.  This ensures data output is secure because a user cannot publish report set output generated by another user, even if he were using the same report set definition. 

MassAllocation Performance Enhancement

MassAllocation is enhanced to improve the performance of MassAllocation formulas that use parent values with a large number of parent and child segment value ranges.  

Consolidation Enhancements for Alternative Accounting Representations

The consolidation functionality of Oracle General Ledger has been enhanced to complement the Global Accounting Engine Multiple Posting solution.  This enhancement is also available to users who do not use Global Accounting Engine but want to create alternative accounting representations of their accounting data using the standard consolidation data transfer functionality.  Global companies often need to perform financial accounting for multiple legislative authorities when they have business operations in foreign countries.  These business operations must maintain accounting records according to the local statutory rules, as well as for the statutory rules that the parent company operates under.  Therefore, they often need to maintain more than one accounting representation of their business transactions.  The Global Accounting Engine Multiple Posting solution enables you to transfer a single Payables or Receivables transaction to two sets of books using different accounting rules to achieve dual accounting representations.  As Global Accounting Engine Multiple Posting only addresses transactions from Payables and Receivables, all other transactions that require a second accounting representation are addressed by the General Ledger standard consolidation data transfer functionality.The General Ledger standard consolidation data transfer functionality has been enhanced to allow you to better synchronize transactions between the source and target sets of books when you need to maintain multiple accounting representations by preserving certain journal details during the transfer of data to the target set of books:

• Journal batching
• Batch names
• Journal names
• Batch and journal header descriptions
• Journal category names
• Journal line descriptions
• Journal line effective dates

You can now also exclude transactions that have already been transferred using Global Accounting Engine Multiple Posting or prevent transactions from being included in a particular accounting representation, by specifying a journal category, such as AX Payables or AX Receivables, to be filtered and excluded from the data transfer.  This allows you to exclude any transaction in your source set of books from being included in your target set of books. 

Journal Reference Date

A new Reference Date field has been added to the Journal Entry definition to complement the Italian Libro Giornale reporting requirements supported by the Global Accounting Engine module.  Libro Giornale is a report of journal entries, and it lists and numbers journal entries by reporting date.  The Reference Date differs from the system date or GL date that the application currently supports.  Please refer to the Italian Daily Journal Book (Libro Giornale) feature in the Global Accounting Engine (AX) module for further details.  The Reference Date field can also be used in a more general manner to capture any other date information as required. The Reference Date can be manually entered or imported for actual journal entries.  The Reference Date on journal entries will be preserved in the transfer from the source set of books to the target set of books when using the consolidation transfer functionality, and from the primary set of books to the reporting set of books when using the Multiple Reporting Currency functionality.  

Journal Import Currency End Date Bypass

 On January 1, 2002, the euro currency replaced the national currencies (NCU) of twelve European countries.   Accordingly, customers may have chosen to assign an end date to the NCU currencies to prevent users from entering new business transactions in these currencies and to enforce using the new euro currency.  However, if there are any business transactions in the NCU currencies that had been created in the subledgers and had not been transferred to General Ledger, customers would be prevented from completing this accounting flow during Journal Import if the NCU currencies were assigned an end date. Journal Import has been enhanced to allow you to optionally bypass the currency end date validation.  This allows you to import journals even though the transaction currency has been inactivated with an end date.  A new profile option allows you to control the users or responsibilities that can import journal batches with inactive currencies.  This feature applies not only to the NCU currencies, but also to any currency that is assigned an end date. 

11.5.8 

Global Consolidation System Cross Instance Data Transfer

The Global Consolidation System now facilitates users to consolidate data from remote subsidiary ledger database instances to a central consolidation database instance. Using database links, this enhancement allows Global Consolidation System users to automatically transfer consolidation data from one instance to another, as well as optionally import and post the data automatically in the consolidation database instance. Users no longer have to manually transfer consolidation data files from the remote subsidiary instances to the consolidation database instance and manually import and post the data into the parent set of books. This enhancement automates the entire process and also includes workflow notifications to notify users of the cross instance consolidation status. Global companies with operations on multiple database instances can use this feature to consolidate their subsidiaries in a more efficient and automated manner. 

Parallel Consolidation Performance Enhancement

The performance of the Global Consolidation System’s consolidation transfer process has been dramatically improved for users who run multiple concurrent consolidation transfer processes in parallel for different subsidiaries and who consolidate a high volume of detail. This feature takes advantage of using separate GL_INTERFACE tables to speed up the transfer and import of consolidation data into the target sets of books using multiple parallel processes. This allows global companies, who often need to transfer data for a large number of subsidiaries, to increase processing efficiency and save time during the critical close process. Users must select the Run Journal Import option in the Transfer Consolidation Data or Transfer Consolidation Data Set form to obtain this performance benefit. 

Translation/Consolidation Compatibility

You can now translate balances and consolidate data simultaneously within the same set of books or across multiple sets of books on the same database instance. This significantly improves the performance of companies that routinely run the translation and consolidation processes during the close cycle for multiple subsidiaries. Instead of having to wait for the Translation program to complete before the Consolidation Transfer program can proceed in each set of books, you can now run these programs simultaneously. 

Open Period/Posting/Translation Compatibility Across Sets of Books

You can now open periods and initialize beginning period balances, post journals, and translate balances simultaneously across multiple sets of books. This significantly improves the performance of companies with multiple sets of books in a single database instance. Instead of having to wait for the Open Period, Posting, or Translation program to complete before the next one of these programs can proceed, you can now run these programs simultaneously. 

Translation Performance Enhancement

The Translation program can now intelligently determine when to retranslate balances in a prior period based on the specific period for which period rates were changed or new transactions were entered. This greatly improves the performance of the Translation process. 

Journal Import Warning Status for Data Errors

Journal Import now completes with a status message of Warning when data errors are encountered during the journal import process. For example, data errors such as importing into an invalid period, invalid segment values, or importing an unbalanced journal would result in Journal Import completing with a Warning status. This allows you to quickly and easily identify journal import requests that did not complete successfully, without having to view the details in the Journal Import Execution report. System errors, such as problems with the concurrent manager or database environment, will still result in Journal Import completing with an Error status.

11.5.9 

Streamlined Revaluation Process

Oracle General Ledger has enhanced Revaluation to provide more flexibility when defining and submitting revaluations. You can now reuse revaluation definitions and rerun them on a daily or more frequent basis to ensure that your foreign currency balances are always current. This is particularly useful for companies with extensive foreign currency exposure, such as companies in the Financial Services industry, but other companies with detailed revaluation requirements may also benefit from this feature. The revaluation process has been streamlined through the following enhancements:

• You can save and reuse revaluation definitions for future revaluations. This removes the need to redefine revaluation criteria every time revaluation is run.

• You can submit revaluations from Standard Report Submission (SRS) to take advantage of the SRS features, such as grouping revaluations into request sets and scheduling them to run automatically. This allows multiple revaluations to be run as a single process, even if those revaluations use different runtime parameters such as rate types.

• You can apply daily rates, in addition to period rates and one-time rates for revaluation. This provides greater flexibility in choosing the rates to use when revaluing balances and enables you to revalue daily using the appropriate rates.

• You can choose different conversion types for different account ranges. For example, you can revalue balance sheet accounts using current rates and income statement accounts using average rates.

• You can control the effective dates of revaluation journals to ensure that daily balances are updated as of the correct date.

• You can use parent values when specifying revaluation account ranges for the natural account segment and balancing segment. This provides easier account assignments because the parent accounts will automatically be expanded to include assigned child values at run-time.

• You can automatically revalue and post your Revaluation batches in one step.

• You can choose to specify different unrealized gain and loss accounts to track the unrealized gains and losses separately, rather than netting them together. 

Translation of Income Statement Accounts Using Period-End Rates

You now have the option to translate income statement accounts using the year-to-date (YTD) translation rule, which uses period-end rates. For example, instead of using the period-to-date (PTD) rule, by which the net activity balances for the period are used, you can use the year-to-date (YTD) balances to translate income statement accounts. This is critical for global companies who operate in multiple countries and need to adhere to different countries' generally accepted accounting rules. Some countries require using the period-to-date (PTD) rule with period-average rates, whereas other countries require using the year-to-date (YTD) rule with period-end rates. You can control the translation method to use by setting the GL Translation: Revenue/Expense Translation Rule profile option to either PTD or YTD. In addition, currency rounding has been enhanced to eliminate very minor differences (equivalent to the minimum currency unit), such as a penny, during Translation. 

Enhanced Global Consolidation System Cross-Instance Data Transfer Security

Global Consolidation System's Cross-Instance Data Transfer was first introduced in Financials Family Pack C to allow you to transfer account balances from one or more remote database instances to a central database instance for consolidation. The Cross- Instance Data Transfer feature now provides database security for the central consolidation database instance during data transfer. Instead of providing remote databases with one database user that has full read/write access to the central consolidation instance, you can define additional users with limited access to the database objects in the central consolidation database. This allows global companies with operations on multiple database instances to better secure database objects in their central consolidation database. For example, you can limit the functions that your subsidiaries can perform on the parent consolidation database by providing them a database user that can only transfer, import, and post consolidation data in the parent consolidation instance. These subsidiaries would not be able to modify the tables and other objects in the parent's instance. In addition, transferring data across database instances has been streamlined by eliminating the need to re-enter your username and password every time you transfer consolidation data. The username and password is now validated once, at the time you sign on to Oracle Applications. 

Enhanced Account Hierarchy Manager Security

The web-based Account Hierarchy Manager now provides chart of accounts security. Instead of being able to view all of the charts of accounts defined in the system, you can limit users' access to only those charts of accounts associated with their responsibilities. This allows global companies with multiple charts of accounts to prevent unauthorized users from modifying charts of accounts outside of their responsibilities. 

Global Intercompany System Rejection of Intercompany Transactions Option

Global Intercompany System (GIS) has improved intercompany transaction processing by allowing you to control the ability to reject GIS transactions. You can apply Function Security to the Reject function to remove the option to reject intercompany transactions. This allows companies with multiple operations to control which responsibilities or subsidiaries can reject intercompany transactions. For example, you can prevent a child subsidiary from rejecting GIS transactions sent by the parent subsidiary. 

MRC Journal Originator Tracking

Multiple Reporting Currencies (MRC) now allows you to optionally retain the journal creation information from the primary book's journal. The new GL/MRC Journals: Inherit the Journal Creator from the Primary Book's Journal profile option allows you to copy the journal creator from the primary journal to each of the reporting journals. This allows you to easily identify who created the original journal entry in the primary set of books while you are viewing the same journal entry in a reporting set of books. By supplying the journal creator information online and in standard reports, you now have a better audit trail to trace journal information back to the person who created the journal. 

Budget Programs, Translation and Posting Compatibility Across Sets of Books

You can now run the key General Ledger Budgeting programs concurrently with the General Ledger Translation and Posting processes across sets of books. This significantly improves performance for companies using multiple sets of books in a single database instance. Instead of having to wait for the Budgeting, Posting, or Translation program to complete before the next program can proceed, you can now run these programs simultaneously. 

Fiscal Year-End Amount Type in FSG Reports

Financial Statement Generator (FSG) has added a new amount type to allow you to report on year-to-date actual balances as of the end of a fiscal year. Instead of having to manually supply the correct period offset to derive the fiscal year-end balance, you can simply select the YTD-Actual (FY End) amount type for more efficient and reusable report definitions. This allows you to produce comparison reports to compare the actual fiscal year-end balances of the current year with those of previous years. In addition, the YTD-Actual (FY End) amount type can be combined with the YTD-Budget (FY End) and YTD-Encumbrance (FY End) amount types to produce fiscal year-end budget versus actual and encumbrance reports. 

11.5.10 

Interface Data Transformer

The Interface Data Transformer is a user-friendly tool that facilitates the import of data from external feeder systems into Oracle General Ledger. It takes data from external feeder systems that have been loaded into the GL_INTERFACE table and transforms it into the proper format for import into Oracle General Ledger based on rules that you define. The Interface Data Transformer offers a variety of ways to transform data in the GL_INTERFACE table. You can use string functions to parse and concatenate substrings, reference lookup tables to convert one value into another, or call PL/SQL functions to perform sophisticated transformations. You can even define conditions to control when transformation rules are applied and validate the results of the transformation through value sets and lookup tables. This flexibility makes it easier for you to integrate non-Oracle systems into Oracle General Ledger. 

Open Integration with External Processing

Oracle General Ledger now includes a number of business events to allow you to customize Oracle General Ledger processes without modifying the standard code. You can configure each event to trigger a notification, message, or other process to perform additional data validation or enrichment, for example.  The Oracle Workflow Business Event System is an application service that leverages the Oracle Advanced Queuing (AQ) infrastructure to communicate business events among systems within an enterprise as well as between enterprises. The Business Event System consists of the Event Manager, which lets you register subscriptions to events that are significant to your systems, and event activities, which let you model business events within workflow process. For more information, please refer to documentation on the Oracle Workflow product. Oracle General Ledger now includes the following business events:

• Account Disabled: This event occurs when an account is disabled in the GL Accounts form or by the Inherit Segment Value Attributes program.

• Period Opened: This event occurs when a period is opened for the first time.

• Period Closed: This event occurs when a period is closed.

• Period Re-opened: This event occurs when a period is opened after it was previously closed.

• Journal Import Started: This event occurs when a journal import process is initiated.

• Journal Import Completed: This event occurs when a journal import process is completed.

• Posting Completed: This event occurs when a posting process is completed. 

XBRL Financial Reporting

Oracle General Ledger now supports eXtensible Business Reporting Language (XBRL). You can create financial reports in XBRL format using the Financial Statement Generator (FSG). XBRL is an open specification for software that uses eXtensible Markup Language (XML) data tags to standardize financial reporting across industries, regulatory bodies, and geographies. You can link FSG reports to XBRL taxonomies, enabling the automatic creation of XBRL instance documents. The ability to create reports in XBRL allows you to prepare, publish and exchange financial information across all software formats and technologies in a consistent standards-based manner for easy distribution, analysis, and comparison.  

Currency Rates Manager

The Currency Rates Manager presents a new interface for you to easily manage your daily and historical rates. You can quickly upload and download currency rates via spreadsheets, or you can enter and maintain rates using the new web-based user interface. For daily conversion rates, you can automatically upload daily rates from a spreadsheet or manage rates using the web-based interface. Currency Rates Manager can even automatically calculate the cross rates between two or more currencies to ensure consistency in daily conversion rates across currencies. For example, if you define rates from U.S. dollars to euros, and from U.S. dollars to Japanese Yen, the Currency Rates Manager can calculate the cross rate between euros and yen, and the inverse rate from yen to euros. This ensures that intercompany transactions across multiple currencies are accounted for with consistent rates, minimizing the effect of exchange rate differences during the intercompany elimination process. Automatic generation of cross rates also reduces the number of currency combinations and rates that you must enter manually, thus enabling you to work more efficiently. For historical rates, you can automatically upload rates from a spreadsheet, or you can automatically download rates into a spreadsheet. The ability to download historical rates into a spreadsheet enables you to modify the rates if necessary, and copy them from one set of books to another for ease of maintenance. Added security is provided to ensure that you can only upload historical rates to periods that are open. 

Secondary Tracking Segment

You can now specify a segment in your chart of accounts as a secondary tracking segment, in addition to the balancing segment, to perform more detailed analysis within Oracle General Ledger. The secondary tracking segment is used in the revaluation, translation, and fiscal year-end close processes. The system will automatically maintain unrealized gain/loss, retained earnings, and cumulative translation adjustments by unique pairs of balancing segment and secondary tracking segment values.11i10 Release Content Document, Rev. 7 Oracle General Ledger 23 

MRC Revaluation Against Primary Currency

You now have more flexibility when revaluing balances in Multiple Reporting Currencies (MRC) Reporting sets of books. Instead of revaluing the MRC reporting book’s balances against the primary book’s entered currency amounts, you can revalue against the primary set of books’ functional currency balances. Applying this revaluation methodology in your reporting sets of books enables you to adhere to the Translation standards of #SFAS52 (which can also be satisfied by Oracle General Ledger translation functionality), while maintaining transaction level detail in your reporting currency at the same time. 

Multilingual Support For FSG Amount Types

Multilingual support has been added to the Financial Statement Generator (FSG) amount types. Amount types, such as PTD and YTD, can now be displayed in the installed language. This is particularly useful for global companies using multiple language installations on a single instance to view amount types in the language of their choice when creating reports. 

FSG Reports Name Display in Concurrent Manager

The Financial Statement Generator (FSG) report name is now displayed when you review your concurrent requests. This allows you to quickly and easily identify your FSG reports in the Concurrent Manager without having to view each report’s output.
 

Continue Step-Down Allocation Option

Step-Down Allocation Sets was first introduced in Release 11i to allow you to automatically generate journal batches in a specific order so that the posted results of one step are used in the subsequent step. Previously, Step-Down Allocations stopped processing if a step did not generate a journal entry. This required users to manually generate the subsequent batches. Now, you can control whether a Step-Down Allocation process should continue processing even if one of the steps did not generate a journal entry. By setting a new profile option, you can  instruct Step-Down Allocation Sets to continue processing to the end of the Allocation Set. 

Open Period/Posting/Translation/Summary Accounts Program Compatibility Among Sets of Books

You can now open periods, run translation, post journals, and maintain your summary accounts simultaneously when these programs are initiated in different sets of books. This significantly improves performance for companies using multiple sets of books in a single database instance. Instead of having to wait for each program to complete before the next one can begin, you can run the following programs in parallel among different sets of books: Open Period, Posting, Translation, Add/Delete Summary Accounts, Incremental Add/Delete Summary Templates, and Maintain Summary Templates. 

Journal Import Group By Effective Dates

Journal Import now provides an option to automatically group journal lines into journal entries based on effective dates. This functionality was previously only available to customers using average balance processing. Now this option is available to all customers and is particularly useful for those who use Daily Business Intelligence. 

Presentation Quality FSG Reports Using XML Publisher

Financial Statement Generator (FSG) is now integrated with XML Publisher so that you can use the convenient formatting features of a word processing application to design the layout of your FSG reports. Some of the report formatting options include changing font characteristics, adding graphical images, inserting headers and footers, creating borders, reordering columns, and supporting an unlimited number of columns in your reports. This enables you to create boardroom-quality financial reports directly from the general ledger, which ensures the integrity and auditability of your financial information. For more information on formatting features, please refer to the XML Publisher release content document. 

Journal Import SRS Program

You can now submit the journal import program from Standard Request Submission (SRS) to take advantage of the SRS features, such as grouping journal import runs into request sets and scheduling journal import to run automatically. Using request sets and scheduling allow multiple journal import requests to run simultaneously, and also allow you to control the sequence in which journal import should run during the period close.