This chapter is an addendum to the general Defining and Designing Reports chapter. This addendum describes the sample reports that are provided with Oracle Enterprise Taxation Management.
This section provides an overview of each sample report supplied with Oracle Enterprise Taxation Management that may be found in the demonstration database. They may be used by your organization as they are or as a starting point for creating a new report.
Account Security. Please note that the sample reports provided with the product do NOT incorporate account security. If a user has been given security to view the report, then all the data in the report is available for viewing.
Contents
Billed Revenues by Rate - CI_BILREV
Case Statistics By Case Type - CI_CSESTS
Case Statistics for a Given Status - CI_CSESGS
Customer Contacts by Type - CI_CUSTCN
GL Accounting Summary - CI_GLACSM
Open Cases By Type - CI_CSEOPN
Tax Payables Analysis - CI_TXPYBL
Parameters
|
Parameter |
Parameter Code |
Description |
|
Accounting Period |
P_ACCT_PERIOD |
Defines the accounting period used for the report. A valid fiscal year and accounting period for a valid accounting calendar must be provided. |
|
Account type Characteristic |
P_CHAR_TYPE |
Defines a Characteristic Type for a characteristic linked to the Distribution Code to define an account type. |
|
Account type |
P_REV_ACCTY_CHAR |
Account type Char Value for Revenue related GL Accounts. The char type defined for this parameter should match the Char Type code defined as parameter #2. The parameter value indicated for this parameter should be one that represents revenue accounts. |
Report Description
This is an analysis report for the billed revenues for an accounting period according to the various rates, which were in effect in the system. The information in this report helps to adjust rates in order to achieve better financial results and comply with regulations and market trends.
This report selects all records in the financial transaction GL collection that satisfy the following criteria:
· The financial transaction is frozen.
· The Accounting Date on the financial transaction within input accounting period (parameter 1)
· The distribution code associated with the GL entry has a characteristic type and value that matches the input account type Characteristic and account type (parameters 2 & 3)
Performance Consideration. If your implementation chooses to use this report, you may consider adding an index to the CI_FT table on ACCOUNTING_DT to aid in performance. When making this decision, carefully weigh the benefit of improving report performance against the possible degradation to the performance of day-to-day processing as a result of defining a new index. Note that many companies opt to create a reporting database that is a shadow of production to ensure that indexes defined to benefit reports may be created without any affect on the production environment.
Parameters
|
Parameter |
Parameter Code |
Description |
|
Start Date |
P_FROM_DT |
See the report's description for how this field is used. If start date is not specified, it is defaulted to 7 days prior to the end date. |
|
End Date |
P_TO_DT |
See the report's description for how this field is used. If end date is not specified, it is defaulted to the current processing date. |
|
Case Condition (Open, Closed) |
P_COND_FLG |
If specified, only cases in this condition are included in the report. If left blank, the reports produces statistics for both open and closed cases. |
Report Description
This report provides two types of statistics:
1. Open cases whose creation date falls between the input Start Date and End Date (inclusive)
2. Closed cases whose closing date falls between the input Start Date and End Date (inclusive)
The third parameter is only used if you want to restrict the statistics to only open or closed cases. If you leave this parameter blank, both open and closed statistics will be produced.
The following information is provided in graphical format:
· Number of cases by case type
· Percentage of cases by case type
Parameters
|
Parameter |
Parameter Code |
Description |
|
Start Date |
P_FROM_DT |
See the report's description for how this field is used. If start date is not specified, it is defaulted to 7 days prior to the end date. |
|
End Date |
P_TO_DT |
See the report's description for how this field is used. If end date is not specified, it is defaulted to the current processing date. |
|
Case Type/Status |
P_CASE_STATUS_CD |
This is the desired Case Type and Status that will be reported on. |
|
Responsible User |
P_CASE_OWNER |
If specified, only cases with this responsible user are included in the report. |
|
First Bucket High Limit |
P_B1_LIMIT |
Cases that took <= this number of days to reach the given status will be grouped together for statistical reporting. |
|
Second Bucket High Limit |
P_B2_LIMIT |
Cases that took <= this number of days but more than the first bucket high limit to reach the given status will be grouped together for statistics reporting. |
|
Third Bucket High Limit |
P_B3_LIMIT |
Cases that took <= this number of days but more than the second bucket high limit to reach the given status will be grouped together for statistics reporting. Cases that took more than this number of days are included in another group. |
Report Description
This report shows cases of a given case type that transitioned to a given status during a given date range.
Graphs are printed to show the number and percentage of cases grouped by the time it took to reach the status. These statistics are grouped into age buckets whose size is controlled by the last 3 parameters.
Summary statistics are also printed showing the minimum, maximum, average and median times for these cases.
Parameters
|
Parameter |
Parameter Code |
Description |
|
Start Date |
P_FROM_DT |
Start date to use for reporting customer contacts. If not defined, the start date is set to the current date minus 7 days. |
|
End Date |
P_TO_DT |
End date to use for reporting customer contacts. If not defined, End Date is set to the current date. |
|
Customer Contact Class / Type |
P_CC_TYPE_CD |
Specify a Customer Contact Class / Type to restrict the report output to a specific class / type. |
Report Description
This report lists all customer contacts in the system created within the input date range. You may optionally restrict the report to customer contacts for a given Customer Contact Class / Type (parameter 3).
Graphs. The information on this report is shown in both textual and graphical formats.
Performance Consideration. If your implementation chooses to use this report, you may consider adding an index to the CI_CC table on CC_DTTM to aid in performance. When making this decision, carefully weigh the benefit of improving report performance against the possible degradation to the performance of day-to-day processing as a result of defining a new index. Note that many companies opt to create a reporting database that is a shadow of production to ensure that indexes defined to benefit reports may be created without any affect on the production environment.
Parameters
|
Parameter |
Parameter Code |
Description |
|
Accounting Period |
P_ACCT_PERIOD |
Defines the accounting period used for the report. A valid fiscal year and accounting period for a valid accounting calendar must be provided. |
|
Account Type Characteristic |
P_CHAR_TYPE |
Defines a Characteristic Type for a characteristic linked to the Distribution Code to define an account type. The account types for the GL accounts are used for grouping the output to the report. |
Report Description
This is a financial audit report used to check the financial details in Oracle Enterprise Taxation Management for an accounting period against the GL system. The report summarizes all financial transaction (FT) information for a given accounting period according to the different operating and GL divisions and according to various levels of the account GL information.
Performance Consideration. If your implementation chooses to use this report, you may consider adding an index to the CI_FT table on ACCOUNTING_DT to aid in performance. When making this decision, carefully weigh the benefit of improving report performance against the possible degradation to the performance of day-to-day processing as a result of defining a new index. Note that many companies opt to create a reporting database that is a shadow of production to ensure that indexes defined to benefit reports may be created without any affect on the production environment.
Parameters
|
Parameter |
Parameter Code |
Description |
|
Start Date |
P_FROM_DT |
See the report's description for how this field is used. If start date is not specified, it is defaulted to 7 days prior to the end date. |
|
End Date |
P_TO_DT |
See the report's description for how this field is used. If end date is not specified, it is defaulted to the current processing date. |
|
Case Type |
P_CASE_TYPE_CD |
If specified, only cases of this type are included in the report. |
|
Responsible User |
P_CASE_OWNER |
If specified, only cases with this responsible user are included in the report. |
|
First Bucket High Limit |
P_B1_LIMIT |
Cases that are open for less than or equal to this number of days will be grouped together for statistical reporting. |
|
Second Bucket High Limit |
P_B2_LIMIT |
Cases that are open less than or equal to this number of days but more than the first bucket high limit will be grouped together for statistics reporting. |
|
Third Bucket High Limit |
P_B3_LIMIT |
Cases that are open less than or equal to this number of days but more than the second bucket high limit will be grouped together for statistics reporting. Cases that took more than this number of days are included in another group. |
Report Description
This is a report on open cases that were created between a given date range.
The report can be limited to a specific type and/or responsible user.
For each case type, the report shows the following:
· Number of open cases by age bucket (the last 3 parameters control the size (in days) of each bucket)
· Percentage of open cases by age bucket
· Details of the open cases
Parameters
|
Parameter |
Parameter Code |
Description |
|
Start Date |
P_FROM_DT |
Report gets all the payments that have been received during a given date range (from and to date parameters). If start date is not defined by the user, it is set to 7 days prior to the current date. |
|
End Date |
P_TO_DT |
End date of the date range. If not defined by user it is set to the current date |
Report Description
This report provides an overall view of all payments created within the input date range. It is typically used for financial control and audit purposes. The report provides summary information about valid payments received and about canceled payment. Data is summarized by the tender source and the type of payment.
Parameters
|
Parameter |
Parameter Code |
Description |
|
Cutoff Date |
P_CUTOFF_DATE |
The date from which the arrears buckets are calculated. If no value is entered, the default is the current date minus 7 days. |
|
1st Bucket High Limit |
P_B1_LIMIT |
High limit of 1st bucket. |
|
2nd Bucket High Limit |
P_B2_LIMIT |
High limit of 2nd bucket. |
|
3rd Bucket High Limit |
P_B3_LIMIT |
High limit of 3rd bucket. |
Report Description
This report lists all accounts and their arrears information as of the input cutoff date using a balance forward accounting method.
Outstanding debt is placed into the buckets provided as input using the age of the debt as of the cutoff date. Credits are applied to the oldest debt first. For each account a separate bucket is used to display new charges. In addition, the total accounts receivable balance is displayed for each account.
Performance Consideration. If your implementation chooses to use this report, you may consider adding an index to the CI_FT table on ARS_DT to aid in performance. When making this decision, carefully weigh the benefit of improving report performance against the possible degradation to the performance of day-to-day processing as a result of defining a new index. Note that many companies opt to create a reporting database that is a shadow of production to ensure that indexes defined to benefit reports may be created without any affect on the production environment.
Parameters
|
Parameter |
Parameter Code |
Description |
|
Start Date |
P_FROM_DT |
Show summary of the tax amounts starting from this date. If not specified, the system will default this value to the current date minus 7 days. |
|
End Date |
P_TO_DT |
Show summary of the tax amounts up to this date. If not specified, the system will default this value to the current date. |
|
Account type Characteristic |
P_CHAR_TYPE |
Defines a Characteristic Type for a characteristic linked to the Distribution Code to define an account type. |
|
Account type |
P_TAX_ACCTY_CHAR |
Account type Char Value for tax related GL Accounts. The char type defined for this parameter should match the Char Type code defined as parameter #3. The parameter value indicated for this parameter should be one that represents tax liability accounts. |
Report Description
This report displays a summary of the tax amounts that were levied by the company to taxpayers within the input date range. It also includes the tax exemption information for that period.
This report select all records in the financial transaction GL collection that satisfy the following criteria:
· The financial transaction is frozen.
· The Accounting Date on the financial transaction within the input date range
· The distribution code associated with the GL entry has a characteristic type and value that matches the input account type Characteristic and account type (parameters 3 & 4)
The report also provides tax exemption information for bill segments whose financial transactions satisfy the above criteria. The tax exemption information is retrieved by looking at the bill calculation lines associated with the FT’s bill segment.
Performance Consideration. If your implementation chooses to use this report, you may consider adding an index to the CI_FT table on ACCOUNTING_DT to aid in performance. When making this decision, carefully weigh the benefit of improving report performance against the possible degradation to the performance of day-to-day processing as a result of defining a new index. Note that many companies opt to create a reporting database that is a shadow of production to ensure that indexes defined to benefit reports may be created without any affect on the production environment.
Parameters
|
Parameter |
Parameter Code |
Description |
|
ToDo Entry Status |
P_ENTRY_STATUS_FLG |
Defines if the ToDo entries on the report should be limited to those with a given status value. If this parameter is left blank, the report will show all open and being worked ToDo entries. |
|
ToDo Type |
P_TD_TYPE_CD |
Defines if the ToDo entries on the report should be limited to those of a given ToDo type. If this parameter is left blank, the report will show all ToDo type that have at least one open or being worked entry. |
Report Description
The report shows open and being worked To Do entries.
You can limit the report to entries in a given status by specifying the desired To Do Status (open or being worked). If you don't specify a status, all open and being worked To Do entries will appear on this report.
You can also limit the report to entries of a given To Do Type by specifying the desired To Do Type. If you don't specify a To Do Type, all To Do Types with at least one entry in the open / being worked state will appear on this report.
Graphs. The information on this report is shown in both textual and graphical formats.