Oracle Demo Environment Instant Access

Oracle Demo Environment Instant Access

Oracle Business Intelligence

Open the URL below in your browser and log in with the credentials provided to access a fully functional OBIEE environment (aka Sample App V 309 which is based on release 11.1.1.7.1 and includes the new Mobile App Designer).

http://slc02okm.oracle.com:7780/analytics

User: Prodney

Password: Admin123

BI Mobile Application Designer (BIMAD)

Oracle provides instant access to demo applications created with BIMAD, so you can enjoy them directly on your mobile device.

Simply use a QR Reader to scan the QR code below on your mobile device to navigate to the login page or use the URL below.

http://aosdemeamt05.oracle.com:7777/mobile/appstore/#store-page

User: bimad_user

Password: welcome1

Alternative URL: http://slc02okx.oracle.com:7780/mobile/appstore

(Thanks to Christian for this update)

There is also a document available with detailed instructions.

BI Mobile HD

For iPad users, Oracle provides the BI Mobile HD app which can be connected to a demo environment as described in this document.

BI Mobile HD app on the iPad

Endeca

As announced on the BI & EPM blog, the latest release of Endeca - 3.1 - can be evaluated in a live demo environment as well, using the following URL and credentials.

http://slc02oku.oracle.com:7101/eid/webUser: publicuser@oracle.com

Password: Admin123

Endeca Information Discovery 3.1 Demo

FA Key Tables fa_additions_b , fa_adjustments

FA Key Tables fa_additions_b , fa_adjustments 

FA_ADDITIONS_B contains descriptive information to help you
identify your assets. Oracle Assets does not use this table to calculate
depreciation.
When you add an asset, Oracle Assets inserts a row into this table and
into FA_ASSET_HISTORY.
When you change the asset information stored in this table, Oracle
Assets updates it in this table. It also creates a new row in
FA_ASSET_HISTORY.
When you perform a unit retirement, Oracle Assets reduces the
CURRENT_UNITS by the units retired.
UNIT_ADJUSTMENT_FLAG is set to YES by the Additions form if you
change the number of units for an asset. The Transfers form resets it to
NO after you reassign the remaining units.
FA_ADJUSTMENTS stores information that Oracle Assets needs to
create journal entries for transactions. The posting program creates
journal entries for regular depreciation expense from information in
FA_DEPRN_DETAIL. Oracle Assets inserts a row in this table for the
debit and credit sides of a financial transaction. All the rows for the
same transaction have the same value in the TRANSACTION_HEADER_ID column.
The SOURCE_TYPE_CODE column tells you which program created
the adjustment:

• ADDITION Depreciation program
• ADJUSTMENT Expensed or Amortized Adjustment User Exit
• CIP ADDITION Depreciation program
• CIP ADJUSTMENT Expensed or Amortized Adjustment User Exit
• CIP RETIREMENT Gain/loss program
• DEPRECIATION Depreciation program (Retroactive transactions and
  expensed depreciation adjustments)
• RETIREMENT Gain/loss program
• RECLASS Reclassification user exit
• TRANSFER Transfers form
• TAX Reserve Adjustments form
• REVALUATION Mass revaluation program

The ADJUSTMENT_TYPE column tells you which type of account Oracle Assets adjusts.
DEBIT_CREDIT_FLAG is DR if the amount is a debit and CR if the amount is a credit.
ADJUSTMENT_AMOUNT is the amount debited or credited to the account.
ANNUALIZED_ADJUSTMENT is the adjustment amount for a period times the number of periods in a fiscal year. The depreciation program uses it to calculate the depreciation adjustment for an asset when you perform multiple retroactive transactions on the asset. Oracle Assets calculates ADJUSTMENT_PER_PERIOD by dividing the
ADJUSTMENT_AMOUNT for a retroactive transaction by the number
of periods between the period you entered the transaction and the
period that it was effective. For current period transactions, this column
is zero.
PERIOD_COUNTER_CREATED IS the period that you entered the adjustment into Oracle Assets.
PERIOD_COUNTER_ADJUSTED is the period to which the adjustment applies. It is the same as PERIOD_COUNTER_CREATED, unless you enter a reserve adjustment, in which case PERIOD_COUNTER_ADJUSTED is the last period of the fiscal year to which the adjustment applies.
CODE_COMBINATION_ID indicates the Accounting Flexfield combination Oracle Assets debits or credits for all transactions except reclassifications and intercompany transfers. This CODE_COMBINATION_ID is generated using the Account Generator, and the posting program does not perform any further processing.

Other sites: http://oracleapps88.blogspot.com/2011/08/fixed-assets-tables.html

FA Depreciation Query

FA Depreciation Query

Data can come into Oracle Assets via the FA_MASS_ADDITIONS table from the following sources: external sources (i.e. legacy systems), Project Accounting (PA), Accounts Payable (AP) and indirectly from Purchasing (PO).

Once the data is posted in Oracle Assets, it is then considered to be a true asset. If an asset is setup as a capitalized asset, it can be depreciated. When Depreciation has ran successfully and the period has closed, you can then submit the Create Journal Entries program (FAPOST).

The Create Journal Entries program creates the journals for General Ledger (GL) and inserts that data directly into the GL tables, GL_JE_HEADERS, GL_JE_BATCHES, and GL_JE_LINES. Therefore, no journal import from within GL is necessary. If the Create Journals program was successful, the unposted journals can be viewed immediately in GL

SELECT

fp.period_name,

dhcc.segment2 business_unit,

dhcc.segment3 account,

dhcc.segment4 dept,

adt.asset_number,

adt.tag_number,

ltrim(rtrim(cat.segment1)) ||'-'|| ltrim(rtrim(cat.segment2)) ||'-'|| ltrim(rtrim(cat.segment3)) category,

bks.date_placed_in_service acquistion_date,

bks.original_cost,

adt.description,

dh.location_id,

adt.context subject_to_property_tax,

adt.attribute1 property_tax_code,

round(sum(decode(bks.period_counter_fully_retired, '',bks.cost, 0) * dh.units_assigned / ah.units), 2) COST, round(sum(nvl(dn.deprn_amount,0) * dh.units_assigned/ ah.units), 2) deprn,

round(sum(nvl(dn.deprn_reserve,0) * dh.units_assigned/ ah.units), 2) deprn_reserve,

round(sum(nvl(dn.ytd_deprn,0) * dh.units_assigned/ ah.units), 2) YTD_DEP,

round(sum(decode(bks.period_counter_fully_retired, '', (bks.cost - dn.deprn_reserve), 0) * dh.units_assigned/ ah.units), 2) c_nbv

FROM

fa_distribution_history dh,

fa_asset_history ah,

fa_additions adt,

fa_categories_b cat,

fa_books bks,

gl_code_combinations dhcc,

fa_deprn_summary dn,

fa_deprn_periods fp

WHERE

fp.book_type_code = 'XXX'

and dn.book_type_code = 'XXXX'

and dn.period_counter =

( select dp.period_counter from fa_deprn_periods dp where dp.book_type_code = 'XXXX'

and dp.period_counter =

( select max(dpz.period_counter) from fa_deprn_summary dsz, fa_deprn_periods dpz

where dpz.book_type_code = 'XXXX'

and dpz.period_counter <= fp.period_counter

and dsz.book_type_code = 'XXXX'

and dsz.period_counter = dpz.period_counter

and dsz.asset_id = dn.asset_id ))

and bks.book_type_code = 'XXXX'
and bks.asset_id = dn.asset_id

and nvl(bks.date_ineffective,sysdate) > to_date(to_char(nvl(fp.period_close_date, sysdate),'DD-MM-YYYY HH24:MI:SS'),'DD-MM-YYYY HH24:MI:SS')

and bks.date_effective < to_date(to_char(nvl(fp.period_close_date, sysdate),'DD-MM-YYYY HH24:MI:SS'),'DD-MM-YYYY HH24:MI:SS')

and nvl(bks.period_counter_fully_retired, fp.period_counter) in

( select dpy.period_counter

from fa_deprn_periods dpy

where dpy.book_type_code = 'XXXX'
and dpy.fiscal_year = fp.fiscal_year)
and adt.asset_id = dn.asset_id
and adt.ASSET_CATEGORY_ID = cat.category_id
and adt.asset_id = dh.asset_id
and dh.book_type_code = 'XXXX'
and nvl(dh.date_ineffective,sysdate) > to_date(to_char(nvl(fp.period_close_date, sysdate),'DD-MM-YYYY HH24:MI:SS'),'DD-MM-YYYY HH24:MI:SS')

and dh.date_effective < to_date(to_char(nvl(fp.period_close_date, sysdate),'DD-MM-YYYY

HH24:MI:SS'),'DD-MM-YYYY HH24:MI:SS')
and dhcc.code_combination_id(+) = dh.code_combination_id
and ah.asset_id = adt.asset_id
and nvl(ah.date_ineffective,sysdate) > to_date(to_char(nvl(fp.period_close_date, sysdate),'DD-MM-YYYY
HH24:MI:SS'),'DD-MM-YYYY HH24:MI:SS')

and ah.date_effective < to_date(to_char(nvl(fp.period_close_date, sysdate),'DD-MM-YYYY

HH24:MI:SS'),'DD-MM-YYYY HH24:MI:SS')

GROUP BY

fp.period_name,

dhcc.segment2,
dhcc.segment4,
dhcc.segment3,
adt.asset_number,
adt.tag_number,

ltrim(rtrim(cat.segment1))||'-'||ltrim(rtrim(cat.segment2))||'-'||ltrim(rtrim(cat.segment3)),

adt.description,

bks.date_placed_in_service,

bks.original_cost,

dh.location_id,

adt.context,

adt.attribute1

R12 SLA Tables connection to AP, AR, INV,Payments, Receiving

R12 SLA (Sub ledger Accounting)

1) All accounting performed before transfer to the GL. Accounting data generated and stored in “Accounting Events” tables prior to transfer to GL

2) Run “Create Accounting” to populate accounting events (SLA) tables. User can “View Accounting” only after “Create Accounting” is run. Create Accounting process

– Applies accounting rules

– Loads SLA tables, GL tables

– Creates detailed data per accounting rules, stores in SLA “distribution links” table

3) Below are the key tables for SLA in R12

XLA_AE_HEADERS xah

XLA_AE_LINES xal

XLA_TRANSACTION_ENTITIES xte

XLA_DISTRIBUTION_LINKS xdl

GL_IMPORT_REFERENCES gir

Below are the possible joins between these XLA Tables

xah.ae_header_id = xal.ae_header_id

xah.application_id = xal.application_id

xal.application_id = xte.application_id

xte.application_id = xdl.application_id

xah.entity_id = xte.entity_id

xah.ae_header_id = xdl.ae_header_id

xah.event_id = xdl.event_id

xal.gl_sl_link_id = gir.gl_sl_link_id

xal.gl_sl_link_table = gir.gl_sl_link_table

xah.application_id = (Different value based on Module)

xte.entity_code =

'TRANSACTIONS' or

'RECEIPTS' or

'ADJUSTMENTS' or

'PURCHASE_ORDER' or

'AP_INVOICES' or

'AP_PAYMENTS' or

'MTL_ACCOUNTING_EVENTS' or

'WIP_ACCOUNTING_EVENTS'

xte.source_id_int_1 =

'INVOICE_ID' or

'CHECK_ID' or

'TRX_NUMBER'

XLA_DISTRIBUTION_LINKS table join based on Source Distribution Types

xdl.source_distribution_type = 'AP_PMT_DIST'

and xdl.source_distribution_id_num_1 = AP_PAYMENT_HIST_DISTS.payment_hist_dist_id

---------------

xdl.source_distribution_type = 'AP_INV_DIST'

and xdl.source_distribution_id_num_1 = AP_INVOICE_DISTRIBUTIONS_ALL.invoice_distribution_id

---------------

xdl.source_distribution_type = 'AR_DISTRIBUTIONS_ALL'

and xdl.source_distribution_id_num_1 = AR_DISTRIBUTIONS_ALL.line_id

and AR_DISTRIBUTIONS_ALL.source_id = AR_RECEIVABLE_APPLICATIONS_ALL.receivable_application_id

---------------

xdl.source_distribution_type = 'RA_CUST_TRX_LINE_GL_DIST_ALL'

and xdl.source_distribution_id_num_1 = RA_CUST_TRX_LINE_GL_DIST_ALL.cust_trx_line_gl_dist_id

---------------

xdl.source_distribution_type = 'MTL_TRANSACTION_ACCOUNTS'

and xdl.source_distribution_id_num_1 = MTL_TRANSACTION_ACCOUNTS.inv_sub_ledger_id

---------------

xdl.source_distribution_type = 'WIP_TRANSACTION_ACCOUNTS'

and xdl.source_distribution_id_num_1 = WIP_TRANSACTION_ACCOUNTS.wip_sub_ledger_id

---------------

xdl.source_distribution_type = 'RCV_RECEIVING_SUB_LEDGER'

and xdl.source_distribution_id_num_1 = RCV_RECEIVING_SUB_LEDGER.rcv_sub_ledger_id

Queries:

In this post, we will check the Data related to the   Payable INVOICE ( Invoice_id = 235452 ) in Sub-Ledger Accounting (XLA). All the queries given in this post and their related posts were tested in R12.1.3 Instance.

XLA_EVENTS

SELECT DISTINCT xe.*

FROM   ap_invoices_all ai,

       xla_events xe,

       xla.xla_transaction_entities xte

WHERE  xte.application_id = 200

AND    xte.application_id   = xe.application_id

AND    ai.invoice_id        = '166014'

AND    xte.entity_code      = 'AP_INVOICES'

AND    xte.source_id_int_1  = ai.invoice_id

AND    xte.entity_id        = xe.entity_id

ORDER BY

       xe.entity_id,

       xe.event_number;

XLA_AE_HEADERS 

 

SELECT DISTINCT xeh.*

FROM   xla_ae_headers xeh,

       ap_invoices_all ai,

       xla.xla_transaction_entities xte

WHERE  xte.application_id = 200

AND    xte.application_id   = xeh.application_id

AND    ai.invoice_id        = '166014'

AND    xte.entity_code      = 'AP_INVOICES'

AND    xte.source_id_int_1  = ai.invoice_id

AND    xte.entity_id        = xeh.entity_id

ORDER BY

       xeh.event_id,

       xeh.ae_header_id ASC; 

XLA_AE_LINES

SELECT DISTINCT xel.*,

       fnd_flex_ext.get_segs('SQLGL','GL#', '50577' , xel.code_combination_id) "Account"

FROM   xla_ae_lines xel,

       xla_ae_headers xeh,

       ap_invoices_all ai,

       xla.xla_transaction_entities xte

WHERE  xte.application_id = 200

AND    xel.application_id   = xeh.application_id

AND    xte.application_id   = xeh.application_id

AND    ai.invoice_id        = '166014'

AND    xel.ae_header_id     = xeh.ae_header_id

AND    xte.entity_code      = 'AP_INVOICES'

AND    xte.source_id_int_1  = ai.invoice_id

AND    xte.entity_id        = xeh.entity_id

ORDER BY

       xel.ae_header_id,

       xel.ae_line_num ASC;

XLA_DISTRIBUTION_LINKS

SELECT DISTINCT xdl.*

FROM   xla_distribution_links xdl,

       xla_ae_headers xeh,

       ap_invoices_all ai,

       xla.xla_transaction_entities xte

WHERE  xte.application_id = 200

AND    xdl.application_id   = xeh.application_id

AND    xte.application_id   = xeh.application_id

AND    ai.invoice_id        = '166014'

AND    xdl.ae_header_id     = xeh.ae_header_id

AND    xte.entity_code      = 'AP_INVOICES'

AND    xte.source_id_int_1  = ai.invoice_id

AND    xte.entity_id        = xeh.entity_id

ORDER BY

       xdl.event_id,

       xdl.a_header_id,

       xdl.ae_line_num ASC;

XLA_TRANSACTION_ENTITIES 

SELECT DISTINCT xte.*

FROM   ap_invoices_all ai,

       xla.xla_transaction_entities xte

WHERE  xte.application_id = 200

AND    ai.invoice_id        = '166014'

AND    xte.entity_code      = 'AP_INVOICES'

AND    xte.source_id_int_1  = ai.invoice_id;

XLA_ACCOUNTING_ERRORS

SELECT DISTINCT xae.*

FROM   ap_invoices_all ai,

       xla_events xe,

       xla.xla_transaction_entities xte,

       xla_accounting_errors xae

WHERE  xte.application_id = 200

AND    xae.application_id   = xte.application_id

AND    xte.application_id   = xe.application_id

AND    ai.invoice_id        = '166014'

AND    xe.event_id          = xae.event_id

AND    xte.entity_code      = 'AP_INVOICES'

AND    xte.source_id_int_1  = ai.invoice_id

AND    xte.entity_id        = xe.entity_id;