Dashboards, Reporting & Business Intelligence

CST_ITEM_COSTS stores item cost control information by cost type.
For standard costing organizations, the item cost control information for
the Frozen cost type is created when you enter a new item. For average
cost organizations, item cost control information is created when you
transact the item for the first time.

CST_ITEM_COST_DETAILS stores detailed cost information for an item
for a cost type. It is the child table of CST_ITEM_COSTS.
There are three types of detailed item cost: User–defined, Defaulted,
and Rolled up. User–defined costs can be entered in the Item Costs
window. Defaulted and Rolled up costs are generated by Cost Rollup.
If the item does not have cost control information for the cost type you
are rolling up, Cost Rollup copies this level detailed cost information
from the default cost type and marks the rows as Defaulted. Previous
level costs are rolled up costs.

WIP_LINES stores production line information. Each row includes a
line name, maximum and minimum rate information, throughput for
rate based lines (lead time), and the start and stop time information that
determines the amount of time per day that the line is available. Oracle
Work in Process uses this information when you associate a line with a
repetitive assembly and when you define a repetitive schedule on the
line. Production line information is optional for discrete jobs.

WIP_OPERATIONS stores information about job and repetitive
schedule operations. Each row represents a specific operation and
includes an operation sequence number, which orders the operations for
the job or repetitive schedule. Each row also includes the assembly
quantity completed at an operation, the quantity at each intraoperation
step, the department associated with an operation, the scheduled start
and completion dates for an operation, the operation’s count point and
backflush types and other operation attributes. In general, Oracle Work
in Process uses this information to control and monitor assembly
production on the shop floor.

WIP_ENTITIES stores information about jobs, repetitive assemblies, and
flow schedules. Each row includes a unique entity name, the entity type,
and the assembly being built. Oracle Work in Process uses this information to control production activities and to ensure that entities with duplicate names are not created.

WIP_DISCRETE_JOBS stores discrete job information. Each row
represents a discrete job, and contains information about the assembly
being built, the revision of the assembly, the job quantity, the status of
the job, the material control method, accounting information, and job
schedule dates. Oracle Work in Process uses this information to control
discrete production.

WIP_TRANSACTIONS stores information about WIP resource
transactions. Each row represents a single resource transaction and
includes a unique transaction Identifier, a transaction date, the job or
repetitive schedule charged, the WIP operation and resource charges,
and the number of units of measure applied. Oracle Work in Process
uses this information to track resource charges and to calculate the
values stored in WIP_TRANSACTION_ACCOUNTS. 

 

FA_DEPRN_PERIODS contains information about your depreciation
periods. Oracle Assets uses this table to determine when each period in FA_CALENDARS was open for a depreciation book.
PERIOD_OPEN_DATE and PERIOD_CLOSE_DATE are the dates when
you opened and closed each book’s depreciation period.
Each time you run the depreciation program, it closes the current period
by setting PERIOD_CLOSE_DATE to the system date. It also opens the
next period by inserting a new row into this table in which PERIOD_CLOSE_DATE is NULL and PERIOD_OPEN_DATE equals the PERIOD_CLOSE_DATE of the old row.
CALENDAR_PERIOD_OPEN_DATE and CALENDAR_PERIOD_CLOSE_DATE correspond to your calendar as defined by the START_DATE and END_DATE columns in
FA_CALENDAR_PERIODS.

FA_DEPRN_SUMMARY contains depreciation information for your assets.
Each time you run the depreciation program, it inserts one row into this
table for each asset.
PERIOD_COUNTER is the period for which you ran the depreciation program.
DEPRN_AMOUNT is the depreciation expense for an asset in a depreciation period. It is the sum of DEPRN_AMOUNT in all the rows of FA_DEPRN_DETAIL for the asset and period.
YTD_DEPRN is the accumulated depreciation of an asset for the current fiscal year as of the end of this period.
DEPRN_RESERVE is the total accumulated depreciation for this asset.
DEPRN_SOURCE_CODE tells you what program created the row
BOOKS Created by the Depreciation Books form, QuickAdditions
form, or the post mass additions program when you enter a new asset.
DEPRN Created by the depreciation program when you run depreciation.
ADJUSTED_COST is the depreciable basis the depreciation program uses to calculate depreciation for an asset in a depreciation period. This value is the same as the asset’s recoverable cost, except for assets that use a diminishing value depreciation method, assets to which you have made an amortized adjustment, and assets you have revalued.

For assets that use a diminishing value method, the ADJUSTED_COST is the
beginning of year net book value, which the depreciation program updates at the start of each fiscal year. When you perform an amortized adjustment on an asset or revalue it, the ADJUSTED_COST becomes the asset’s net book value at the time of the adjustment or revaluation.
BONUS_RATE is the bonus rate that Oracle Assets adds to the adjusted
rate to give you the flat rate for the fiscal year. The depreciation
program uses this rate to calculate depreciation for an asset. This only
applies to assets that use both a flat–rate depreciation method and bonus
depreciation.

Continued from previous list 

 

 

This is a useful list covering most of the Oracle e-Business Suite products.

I bet there must be quite a number of products still in research and development and some will never get to see the light
out of the development labs.

Oracle Product Codes

 

 

 

http://www.sq.ro/spamplants.php

“By analyzing text using computational linguistics methods, you can detect anger and sadness. Turning those into gestures in three dimensions, that would be interesting,” said Dragulescu, who is now head of the Experimental Game Lab, a research lab at the Center For Research and Computing and the Arts (CRCA) within the University of California at San Diego.

Dragulescu’s work stands out at a time when scientists and technologists are struggling to harness the massive quantities of data online and make sense of it for fields like earth science, drug discovery, genetic research and U.S. security. Information visualization is a traditional scientific method that’s getting a lot of attention now because it involves projecting a visual image of the data so that onlookers can make connections that might otherwise be lost.

More at

GL_SETS_OF_BOOKS stores information about the sets of books you define in your Oracle General Ledger application. Each row includes the set of books name, description, functional currency, and other information. This table corresponds to the Set of Books form.

GL_IMPORT_REFERENCES stores individual transactions from subledgers that have been summarized into Oracle General Ledger journal entry lines through the Journal Import process. You can specify the journal entry sources for which you want to maintain your transaction’s origin by entering ’Yes’ in the Import Journal References field of the Journal Sources form.

For each source that has Import Journal References set to ’Yes’, Oracle General Ledger will populate GL_IMPORT_REFERENCES with one record for each transaction in your feeder system.

GL_DAILY_RATES stores the daily conversion rates for foreign currency transactions. It replaces the GL_DAILY_CONVERSION_RATES table.
It stores the rate to use when converting between two currencies for a given conversion date and conversion type. Each row in this table has a corresponding inverse row in which the from and to currencies are switched.

For example, if this table contains a row with a from_currency of YEN, a to_currency of CND, a conversion_type of Spot, and a conversion_date of January 1, 1997, it will also contain a row with a from_currency of CND, a to_currency of YEN, a conversion_type of Spot, and a conversion_date of January 1, 1997.

In general, this row will contain a rate that is the inverse of the matching row. One should never insert directly into this table. They should instead insert into the DAILY_RATES_INTERFACE table. Data inserted into the GL_DAILY_RATES_INTERFACE table will be automatically copied into this table.

GL_JE_LINES stores the journal entry lines that you enter in the Enter Journals form. There is a one–to–many relationship between journal entries and journal entry lines. Each row in this table stores the associated journal entry header ID, the line number, the associated code combination ID, and the debits or credits associated with the journal
line. STATUS is ’U’ for unposted or ’P’ for posted.

GL_PERIODS stores information about the accounting periods you define using the Accounting Calendar form. Each row includes the start date and end date of the period, the period type, the fiscal year, the period number, and other information. There is a one–to–many relationship between a row in the GL_PERIOD_SETS table and rows in
this table.