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.
Prerequisites
- 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.
- 4. Submit the request.
- 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.
Other Considerations
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.
- 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.
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.
|
In this Document
APPLIES TO:Oracle General Ledger - Version 10.7 to 12.1.3 [Release 10.7 to 12.1]Information in this document applies to any platform. Executable:RGRXFR - Program - FSG Transfer Form:RGXGDDBL.FMB - Define Database Links PURPOSETroubleshooting Guide for the FSG Transfer program (RGRXFR). TROUBLESHOOTING STEPSCHECK SETUP1. Check the log file for error messages. OTHER ISSUES1. You see the errors ORA-20000, ORU-10027 and ORA-06512 in the log file:ERROR at line 1: 2. You see the errors APP-01126 and ORA-20000 in the log file:APP-01126: Concurrent manager got error running sql*plus 3. You see the errors ORA-00604 and ORA-01000 in the request log file:ORA-00604 Error occurred at recursive SQL Level 1 4. You get error APP-09518 (APP-RG-09518) on the Define Database Links form (RGXGDDBL)You are trying to create the database link for the FSG Transfer on the Define Database Links form (RGXGDDBL) in General Ledger. |
Defining Database Links
You can define links to other General Ledger databases by using the Define Database Links window. You give each linked database a name, which you can then use for copying FSG report objects from the linked database into your current database.
For example, when you implement General Ledger, you might define all of your FSG report objects in a test database. Once your production database is fully functional, you will probably want to transfer your report objects to it. To do this, you first create a link from the production (target) database to the test (source) database. Once the link is established, you can copy the report objects by using the FSG Transfer program.
Prerequisites
- For both the source and target databases, you or your database administrator must set the DISTRIBUTED_TRANSACTION parameter to a number greater than zero. The parameter is located in the init.ora file on the database server.
- You or your database administrator must grant permission for database link creation in the target database by executing the following SQL statement:
grant create database link to <APPS account>
- where
<APPS account>
- is your APPS account name.
To create a link to a General Ledger database:
- 1. Navigate to the Define Database Links window.
- 2. Enter the Database Name and optional Description for the linked database. You must also supply the Database Name to the FSG Transfer program.
- You can find the database name by executing the following query in the source database:
SELECT value FROM v$parameterWHERE UPPER(name) = 'DB_NAME';
- 3. Enter the following additional information for the database. If you do not know what to enter, ask your System Administrator.
Connect String:
- The network connect string to point to the General Ledger database.
Domain Name:
- The domain of the remote General Ledger database to which this link connects.
- You can find the domain name by executing the following query in the source database:
SELECT value FROM v$parameterWHERE UPPER(name) = 'DB_DOMAIN';APPS Username:
- The name of the Oracle Applications account that has read access to the General Ledger database tables. Note that this is not the username you enter to login to Oracle Applications.
APPS Password:
- The password for the above username. Note that, for security reasons, when you enter the password General Ledger will display asterisks instead of the actual characters in the password.
- See: Creating Database Links
(Oracle 7 Server SQL Reference, Release 7.3)
- 4. Save your work.
To delete a database link:
- 1. Navigate to the Define Database Links window.
- 2. Query the database name you want to delete.
- 3. Choose Delete Record from the Edit menu.
- 4. Choose Yes to delete the database link.
db_domain操作方法记录
col type for a10
col value for a20
show parameter db_domain
NAME TYPE VALUE
------------------------------------ ---------- ------------------------------
db_domain string
show parameter name
NAME TYPE VALUE
------------------------------------ ---------- ------------------------------
db_file_name_convert string
db_name string doudou
db_unique_name string doudou
global_names boolean FALSE
instance_name string doudou
lock_name_space string
log_file_name_convert string
service_names string doudou
alter system set db_domain='com' scope=spfile;
SQL> show parameter db_domain
NAME TYPE VALUE
------------------------------------ ---------- ------------------------------
db_domain string
SQL> show parameter name
NAME TYPE VALUE
------------------------------------ ---------- ------------------------------
db_file_name_convert string
db_name string doudou
db_unique_name string doudou
global_names boolean FALSE
instance_name string doudou
lock_name_space string
log_file_name_convert string
service_names string doudou
虽然我们修改成功了，但是没有立刻生效，我们重启数据库
shutdown immediate
startup
SQL> show parameter db_domain
NAME TYPE VALUE
------------------------------------ ---------- ------------------------------
db_domain string com
SQL> show parameter name
NAME TYPE VALUE
------------------------------------ ---------- ------------------------------
db_file_name_convert string
db_name string doudou
db_unique_name string doudou
global_names boolean FALSE
instance_name string doudou
lock_name_space string
log_file_name_convert string
service_names string doudou.com
修改db_domain重启数据库后生效！还有一点需注意service_names自动变为doudou.com也就是说当你设置db_domain时，在不设置service_names的情况下，service_names =db_unique.db_domain(为什么会有这个公式，下面会讲)