Introduction:
Oracle Fixed Assets is fully integrated with other modules so that data input in Purchasing, Payables and Projects will flow through Fixed Assets into the General Ledger. This also means that any asset can be queried and the source information obtained by drilling down to find details of invoices. You can perform most of your transactions in Oracle Assets using just three windows: the Assets Workbench, Mass Additions Workbench, and Tax Workbench.

Additions:
The majority of assets should come via the Purchasing, Payables / Project modules using the Mass Additions / Interface Supplier Costs process. There may be a few occasions when manual additions are required. Ordinary assets can be quickly entered using Quick Additions. Detailed Additions can be used to handle more complex assets as follows:

· Assets with a salvage value.
· Assets with more than one assignment.
· Assets with more than one source line.
· Assets that Category defaults do not apply.
· Subcomponents Assets.
· Leased assets and Leasehold Improvements.

Depreciation:
Default depreciation rates can be set up for each asset category and also can be overridden in special cases. Before running depreciation you can change any field but after running depreciation you can only change asset cost and depreciation rate. You then can choose whether to amortize the adjustment or expense it.

Retirement:
You can retire an entire asset or you can partially retire an asset. You can also use Mass Retirements to retire a group of assets at one time.

Tax Book Maintenance:
Oracle Assets allows you to copy your assets and transactions from your corporate book to your tax books automatically using Initial / Periodic Mass Copy. You can create as many tax books as you need, maintain your asset information in your corporate book, and then update your tax books with assets and transactions from your corporate book.

Prepaid Services:To record warranty and maintenance information into Oracle Assets, a purchase order must be created and the data input will flow into Payables with the proper prepaid account. Prepaid accounts are maintained in the general ledger and amortized over the period of coverage; however, the accounts charged are based on the designated account(s) for the prepaid services. The charges into the Fixed Assets account and asset category is based on the monthly charges from the monthly amortization of the prepaid services.


Capitalized Leases vs. Operating Leases:
Oracle Assets allows you to test leased assets in accordance with generally accepted accounting principles to determine whether to capitalize and depreciate your leased assets. Lease Capitalization Test: (1) the ownership of the asset transfers to the lessee at the end of the lease (2) a bargain purchase option exists (3) the term of the lease is more than 75% of the economic life of the leased asset (4) the present value of the minimum lease payment exceeds 90% of the fair market value of the asset at lease inception.

Regarding Operating leases, Fixed Assets tracks your payments under operating leases, or leases that do not meet any of the criteria, for informational purposes. You can use this information to create a schedule of future minimum payments under operating leases, information that may require disclosure in the footnotes of your financial statements.

Period-End Process:
The key components of the Period-End Process are:
· Ensure All Assets have been Properly Assigned.
· Copy New Assets Entries into Tax Books.
· Run Depreciation for the Corporate Book.
· Create Journal Entries.
· Post Journal Entries to the General Ledger.

In this article, we will cover accounting entries made by Oracle Fixed Asset module (FA). First we will cover some of the natural accounts that are setup and then we will cover what entries are made.
In the Assets module, following are some of the accounts we setup. Some accounts (like Clearing) are used by other modules as well.
Note: All of these accounts are natural accounts, and are created as flexfield values for the natural account (GL account) segment.

	Account	Segment Qualifier
1	Asset Cost	Asset Account
2	Asset Clearing	Asset Account
3	Depreciation Expense	Expense Account
4	Accumulated Depreciation	Contra-Asset Account
5	Deferred Depreciation Reserve	Liability Account
6	Deferred Depreciation Expense	Expense Account
7	Depreciation Adjustment	Expense Account
8	Proceeds of Sale Clearing	Asset Account
9	Cost of removal Clearing	Liability Account
10	Gain & Loss	Revenue Account

Here are the entries made by FA.

Transaction	Natural Account	Debit	Credit
Asset is added	Asset Cost	$100
	Asset Clearing		$100
Asset Depreciation	Depreciation Expense	$100
	Accumulated Depreciation		$100
Asset Retirement – W/o proceeds and W/o removal cost	Accumulated Depreciation	$60
	Gain/Loss	$40
	Asset Cost		$100
Asset Retirement – With Proceeds, W/o Cost of removal	Accumulated Depreciation	$60
	Gain/Loss	$40
	Gain/Loss		$10
	Proceeds from Sale	$10
	Asset Cost		$100
Asset Retirement -  With Cost of removal	Accumulated Depreciation	$60
	Gain/Loss	$40
	Gain/Loss	$5
	Cost of removal Clearing		$5
	Asset Cost		$100

 Want to Add a Responsibility | How about Oracle User Management

When you think of adding a new responsibility to an existing E-Business Suite user, does System Administrator come to mind? Visions of going to the Define User form, tabbing down and finding the new responsibility to add? Did you know that you can add responsibilities to a user through Oracle User Management? Let’s step through how this can happen together. Below I have setup a brand new user without any responsibilities.

DECLARE
l_trx_hdr_id NUMBER;
l_trx_lines_id NUMBER;
l_line_number NUMBER :=1;
l_cust_account_id NUMBER;
l_btch_source NUMBER;
l_count NUMBER;
l_cust_trx_type_id NUMBER;
l_memo_lines NUMBER;
l_return_status VARCHAR2(1);
l_msg_count NUMBER;
l_msg_data VARCHAR2(2000);
l_mesg VARCHAR2(2000);
l_batch_id NUMBER;
l_cnt NUMBER := 0;
l_batch_source_rec ar_invoice_api_pub.batch_source_rec_type;
l_trx_header_tbl ar_invoice_api_pub.trx_header_tbl_type;
l_trx_lines_tbl ar_invoice_api_pub.trx_line_tbl_type;
l_trx_dist_tbl ar_invoice_api_pub.trx_dist_tbl_type;
l_trx_salescredits_tbl ar_invoice_api_pub.trx_salescredits_tbl_type;
l_customer_trx_id NUMBER;
l_chr_mesg VARCHAR2(2000);
p_cm_line_tbl AR_CREDIT_MEMO_API_PUB.Cm_Line_Tbl_Type_Cover%TYPE;

--Reciepts
e_excp EXCEPTION;

BEGIN
fnd_global.apps_initialize (user_id => 0,
resp_id => 20678,
resp_appl_id => 222);

mo_global.init('AR');


AR_CREDIT_MEMO_API_PUB.create_request
( p_api_version => 1.0,
p_init_msg_list => FND_API.G_FALSE,
p_commit => FND_API.G_FALSE,
-- p_validation_level => FND_API.G_VALID_LEVEL_FULL,
x_return_status => l_return_status,
x_msg_count => l_msg_count,
x_msg_data => l_msg_data,
x_request_id => l_batch_id,
-- credit memo request parameters
p_customer_trx_id =>11101,
p_line_credit_flag =>'N',
p_line_amount =>-100,
p_tax_amount => 0,
p_cm_reason_code =>'RETURN',
--p_comments =>,
p_cm_line_tbl =>p_cm_line_tbl,
p_skip_workflow_flag =>'Y',
p_org_id => 81,
--p_trx_number => 107801,
p_batch_source_name => 'MANUAL-OTHER',
p_credit_method_installments => NULL,
p_credit_method_rules => NULL);

IF l_return_status<> FND_API.G_RET_STS_SUCCESS
THEN
dbms_output.put_line('... Msg Count: ' || l_msg_count);
l_chr_mesg := 'Error in Create Single Invoice';
IF l_msg_count = 1
THEN
dbms_output.put_line('... Msg Data: ' || l_msg_data);
l_chr_mesg := l_chr_mesg||l_msg_data;
ELSIF l_msg_count > 1
THEN
-- the messages on the stack are more than one so call them in a loop
-- and put the messages in a PL/SQL table.
l_count := 0;
LOOP
l_count := l_count +1 ;
l_mesg := fnd_msg_pub.get (fnd_msg_pub.g_next, fnd_api.g_false);
IF l_mesg IS NOT NULL
THEN
dbms_output.put_line('... Msg Data: ' || l_count || '. ' || l_mesg);
l_chr_mesg := l_chr_mesg||' '||l_mesg;
ELSE
RAISE e_excp;
END IF;
END LOOP;
END IF;
END IF;

dbms_output.put_line(l_return_status||l_msg_data);
END;

DECLARE
l_trx_hdr_id NUMBER;
l_trx_lines_id NUMBER;
l_line_number NUMBER :=1;
l_cust_account_id NUMBER;
l_btch_source NUMBER;
l_count NUMBER;
l_cust_trx_type_id NUMBER;
l_memo_lines NUMBER;
l_return_status VARCHAR2(1);
l_msg_count NUMBER;
l_msg_data VARCHAR2(2000);
l_mesg VARCHAR2(2000);
l_batch_id NUMBER;
l_cnt NUMBER := 0;
l_batch_source_rec ar_invoice_api_pub.batch_source_rec_type;
l_trx_header_tbl ar_invoice_api_pub.trx_header_tbl_type;
l_trx_lines_tbl ar_invoice_api_pub.trx_line_tbl_type;
l_trx_dist_tbl ar_invoice_api_pub.trx_dist_tbl_type;
l_trx_salescredits_tbl ar_invoice_api_pub.trx_salescredits_tbl_type;
l_customer_trx_id NUMBER;
l_chr_mesg VARCHAR2(2000);

--Reciepts
l_party_id NUMBER;
l_bank_acct_id NUMBER;
l_cr_id NUMBER;
l_receipt_method_id NUMBER;
l_pay_method_name ar_receipt_methods.name%TYPE;
l_recp_number ar_cash_receipts_all.receipt_number%TYPE;
e_excp EXCEPTION;
BEGIN
fnd_global.apps_initialize (user_id => 0,
resp_id => 20678,
resp_appl_id => 222);

mo_global.init('AR');


l_trx_header_tbl(1).trx_header_id := 11117; -- use gl group id
l_trx_header_tbl(1).trx_number := 'TestInvoiceAPI';
l_trx_header_tbl(1).bill_to_customer_id := 3043;
l_trx_header_tbl(1).cust_trx_type_id := 2;
l_batch_source_rec.batch_source_id := -1;

-- Populate line 1 information.
l_trx_lines_tbl(1).trx_header_id := 11117;
l_trx_lines_tbl(1).trx_line_id := 11117;
l_trx_lines_tbl(1).line_number := 1;
l_trx_lines_tbl(1).memo_line_id := 1052;
l_trx_lines_tbl(1).quantity_invoiced := 1;
l_trx_lines_tbl(1).unit_selling_price := 1;
l_trx_lines_tbl(1).line_type := 'LINE';

AR_INVOICE_API_PUB.create_single_invoice (p_api_version => 1.0,
p_batch_source_rec => l_batch_source_rec,
p_trx_header_tbl => l_trx_header_tbl,
p_trx_lines_tbl => l_trx_lines_tbl,
p_trx_dist_tbl => l_trx_dist_tbl,
p_trx_salescredits_tbl => l_trx_salescredits_tbl,
x_customer_trx_id => l_customer_trx_id,
x_return_status => l_return_status,
x_msg_count => l_msg_count,
x_msg_data => l_msg_data);

COMMIT;

dbms_output.put_line('Test'l_customer_trx_idl_return_statusl_msg_data);

IF l_return_status<> FND_API.G_RET_STS_SUCCESS
THEN
dbms_output.put_line('... Msg Count: ' l_msg_count);
l_chr_mesg := 'Error in Create Single Invoice';
IF l_msg_count = 1
THEN
dbms_output.put_line('... Msg Data: ' l_msg_data);
l_chr_mesg := l_chr_mesgl_msg_data;
RAISE e_excp;
ELSIF l_msg_count > 1
THEN
-- the messages on the stack are more than one so call them in a loop
-- and put the messages in a PL/SQL table.
l_count := 0;
LOOP
l_count := l_count +1 ;
l_mesg := fnd_msg_pub.get (fnd_msg_pub.g_next, fnd_api.g_false);
IF l_mesg IS NOT NULL
THEN
dbms_output.put_line('... Msg Data: ' l_count '. ' l_mesg);
l_chr_mesg := l_chr_mesg' 'l_mesg;
ELSE
RAISE e_excp;
END IF;
END LOOP;
END IF;
END IF;

l_msg_count := NULL;
l_msg_data := NULL;
l_cr_id := NULL;
l_return_status := NULL;

ar_receipt_api_pub.Create_and_apply
(p_api_version => 1.0,
p_init_msg_list => FND_API.G_TRUE,
-- p_commit => FND_API.G_FALSE,
p_validation_level => FND_API.G_VALID_LEVEL_FULL,
x_return_status => l_return_status,
x_msg_count => l_msg_count,
x_msg_data => l_msg_data,
p_currency_code => 'INR',
p_amount => 450,
p_receipt_number => 'TEST78889',
p_receipt_date => TRUNC(SYSDATE-30),
p_gl_date => TRUNC(SYSDATE-30),
p_customer_id => 3043,
--p_default_site_use => 'Y', --bug4448307-4509459
p_customer_bank_account_id => NULL,
p_customer_site_use_id => NULL,
p_remittance_bank_account_id => --Bank use id
--p_customer_site_use_id => r_main_rec.party_site_id,
p_receipt_method_id => 2001,
-- p_attribute_record => l_attribute_rec,
p_org_id => 81,
p_cr_id => l_cr_id,
p_customer_trx_id => 2187,
p_amount_applied => 450);

dbms_output.put_line('Test'l_cr_idl_return_statusl_msg_data);

COMMIT;

IF l_return_status<> FND_API.G_RET_STS_SUCCESS
THEN
dbms_output.put_line('... Msg Count: ' l_msg_count);
l_chr_mesg := 'Error in Create Single Invoice';
IF l_msg_count = 1
THEN
dbms_output.put_line('... Msg Data: ' l_msg_data);
l_chr_mesg := l_chr_mesgl_msg_data;
RAISE e_excp;
ELSIF l_msg_count > 1
THEN
-- the messages on the stack are more than one so call them in a loop
-- and put the messages in a PL/SQL table.
l_count := 0;
LOOP
l_count := l_count +1 ;
l_mesg := fnd_msg_pub.get (fnd_msg_pub.g_next, fnd_api.g_false);
IF l_mesg IS NOT NULL
THEN
dbms_output.put_line('... Msg Data: ' l_count '. ' l_mesg);
l_chr_mesg := l_chr_mesg' 'l_mesg;
ELSE
RAISE e_excp;
END IF;
END LOOP;
END IF;
END IF;

EXCEPTION
WHEN OTHERS THEN
l_chr_mesg := l_chr_mesg' ''Error in Create Single Invoice'SQLERRM;
RAISE e_excp;

Transactions Accounting:
Accounting setups:
1. Define Receivable and Revenue Account for Transaction Type like Invoice,Credit Memo,etc.
    Navigation
    Setup>Transactions>Transaction Types

2. Define AutoAccounting which determines defaulting rules for each segment of different Accounts like
    Receivable, Revenue, Tax, etc
    Setup>Transactions>AutoAccounting

Accounting entries:
Below are Transaction Accounts that are hit for Transaction like Invoices and Credit Memos
Invoices
When you enter a regular invoice through the Transactions window,
Receivables creates the following journal entry:
DR Receivables
CR Revenue
CR Tax (if you charge tax)
CR Freight (if you charge freight

Credit Memos
When you credit an invoice, debit memo, or charge back through the
Credit Transactions window, Receivables creates the following journal
entry:
DR Revenue
DR Tax (if you credit tax)
DR Freight (if you credit freight)
CR Receivables (Credit Memo)
DR Receivables (Credit Memo)
CR Receivables (Invoice)

Receipts Accounting:
Depending upon the status of the Receipt whether its Applied, Unapplied, Applied On-Account the
Transaction entries will hit different accounts. The Accounts are defaulted based on Payment method
(Receipt Class) and Remittance Bank selected when you enter the receipt.

Accounting setups:
Navigation:
Setup>Receipts>Receipt Classes
1.Define your Receipt Class along with  Remittance Bank. Receivables uses the default Cash, Unapplied,
   Unidentified, On account, Unearned, and Earned accounts that you specified in the Remittance Banks
    window for this receipt class.

2. Remittance Method: determines status of receipt, remittance required or not Standard, No Remittance

3. Clearance Method: Determines whether clearance is required or not.
        By Automatic Clearing
        By Matching
       Directly
4. At Receipt Class the values of Remittance method and Clearance method determines whether accounting
     entries hit Remittance and Cash Clearing accounts. If these are No Remittance and Clearing is Directly
     the accounting entries don't hit Remittance and Cash Clearing accounts.

Accounting entries:
These examples assume that the receipt has a Remittance Method of No Remittance and a Clearance Method of Directly.
When you enter a receipt and its Unapplied, Receivables creates the following journal entries:
DR Cash
CR Unapplied Cash

When you fully apply a receipt to an invoice, Receivables creates the following journal entry:
DR Cash
DR Unapplied Cash
CR Unapplied Cash
CR Receivables

When you enter an unidentified receipt, Receivables creates the following journal entry:
DR Cash
CR Unidentified

When you enter an on– account receipt, Receivables creates the following journal entry:
DR Cash
CR Unapplied
DR Unapplied
CR On–Account

When your receipt includes a discount, Receivables creates the following journal entry:
DR Receivables
CR Revenue
DR Cash
CR Receivables
DR Earned/Unearned Discount
CR Receivables

At Receipt Class the Remittance and Clearance method is set as Standard and By Matching
Enter the Receipt the entry hits Receipt Confirmation with status of receipt as Confirmed
DR Receipt Confirmation
CR Receivables

Once the receipt is remitted and status becomes "Remitted"
DR Remittance
CR Receipt Confirmation

Once receipt is Cleared
Dr Cash
CR Remittance

To complete the close process in Payables:
1. Validate all invoices.
    Run Invoice Validation Concurrent program.

2. Confirm or cancel all incomplete payment batches.

3. If you use future dated payments, submit the Update Matured Future Dated Payment Status Program.
   This will update the status of matured future dated payments to Negotiable so you can account for them.

4. Resolve all unaccounted transactions. Submit the Payables Accounting Process to account for all
    unaccounted transactions. Review the Unaccounted Transactions Report. Review any unaccounted
    transactions and correct data as necessary. Then resubmit the Payables Accounting Process to account
    for transactions you corrected. Or move any unresolved accounting transaction exceptions to another
    period (optional).

• Payables Accounting Process.
• Submit the Unaccounted Transactions Sweep Program.

5. Transfer invoices and payments to the General Ledger and resolve any problems you see on the output report: Payables Transfer to General Ledger Program.

6. In the Control Payables Periods window, close the period in Payables.Controlling the Status of Payables Periods.

7. Reconcile Payables activity for the period. You will need the following reports

• Accounts Payable Trial Balance Report (this period and last period).
• Posted Invoice Register.
• Posted Payment Register.

You cannot close a period in Payables if any of the following conditions exist:
o Outstanding payment batches. Confirm or cancel all incomplete payment batches.
o Future dated payments for which the Maturity Date is within the period but that still have a status of Issued.
o Unaccounted transactions. Submit the Payables Accounting Process to account for transactions, or submit the Unaccounted Transaction Sweep to move any remaining unaccounted transactions from one period to another.
o Accounted transactions that have not been transferred to general ledger. Submit the Payables Transfer to General Ledger process to transfer accounting entries.

Conversion approach
Setups for Property Manager Conversion
APIs used for Conversion: