Copying Report Objects From Another Database (FSG Transfer Program)
Run the FSG Transfer program to copy report objects from one General Ledger database to another. You can copy row sets, column sets, reports, report sets, content sets, row orders, display sets, and display groups.
For example, when you implement General Ledger, you might also define all of your FSG objects in a test database. Once your production database is fully functional, you can easily copy the FSG objects from your test database by using the FSG Transfer program.
You or your System Administrator must define database links.
The chart of accounts in your source database must be identical to the chart of accounts in your target database.
Any currencies and sets of books referred to by the row sets and column sets being copied must exist in the target database.
Report details, such as budgets and encumbrance types, referred to by copied reports must exist in the target database.
You must be logged in to General Ledger and connected to the target database.
To run the FSG Transfer program:
1. Navigate to the Submit Request window.
2. Select the concurrent program named Program - FSG Transfer.
3. Enter the program parameters.
5. When the concurrent request finishes, review the report for any warnings and error messages. If there are errors, correct them, then rerun the FSG Transfer program.
The report produced by the FSG Transfer concurrent request identifies any warnings and error messages which occurred when the program ran. Some of the reasons for warnings include:
- Name collisions: If a report object you are trying to copy already exists in your target database, you will get a warning message and the report object will not be copied.
- Row and column set references: If any of the copied row or column sets refer to a currency or set of books which doesn't exist in the target database, you will get a warning message and the reference will be excluded from the copied row or column set.
If the FSG Transfer program is interrupted, you can resubmit the program with the same parameters. Note that the program will produce warning messages for any report objects that were successfully transferred during the interrupted run. You can ignore these warnings.
- Report details: If any copied FSG reports refer to report details, such as budgets and encumbrance types, which don't exist in the target database, you will get a warning message and the reference will be excluded from the copied report.
FSG Transfer Program Parameters
Defining Database Links
Copying Report Objects
Submitting a Request