| • | The bridge import of the general ledger extract file occurs in the Bridge Import screen under Import in the Data Transfer area. |
| • | Using the bridge can help build an audit trail because it represents the book general ledger data on an account-by-account basis, as well as the tax treatment of that account. |
| • | Information that is bridged into the application can be assigned a Tag letter or Classes and Subclasses to identify the source of the data as being bridged from the general ledger information. This allows you to segregate bridged data from amounts that were manually entered or populated by the Import Spreadsheet template in the data review screens and run reports based on the received data for a specific class or class group. |
| • | The bridge relies on either the SQL Server utility program “BCP” or the Oracle utility “SqlLdr” to load the general ledger extract file into a staging area database table. This area is available for review of all imported information before updates are made to calculations. The most common problem encountered when using the Bridge is that the BCP or SqlLdr utilities are not installed on the user’s computer. Verify the proper utility is installed before proceeding with the Bridge process. |
| • | The database operating server (Oracle or SQL) needs to be known and identified when bridging. |
| • | The extracted file from General Ledger can have four or six columns of data and be either a comma or tab delimited file type. |
Note: PTBI, Permanent Differences, Temporary Differences, and Trial Balances will only populate Data entry pages and reports by Bridge Import if they are mapped correctly in Administration. For more information, refer to the Unit Mapping section.
|
