My Portfolio

Introduction  :  Organisations always Aim for the follwing objects.  1.Reduce the cost to improve the Margin  2.Quick decesion Making.  Therefore To reduce the Reconciliation process time  so that decesion making would be faster and avoid manual errors Oracle has introduced AP/AR Netting  for the Parties who acts as Supplier and Customer for the Organisation.  What is AP/AR Netting:   In the business if a party is a supplier and also customer then the amount need to pay and elgible to receive from that Party would need to be knocked off and only the left amount received or paid need to  be settled in cash.  Oracle AP/AR Netting is  the process  where in the AP , Party who is a supplier  and also in AR where Party is a customer has some balance in their Account.  To do the settlement both AP and AR Balnce need to be knocked off and rest amount need to be paid.  How to do AP/AR Netting:   Define...

Accounting Entries – Fixed Assets 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. Tra...

Accounting entries for the Asset Life Cycle Finally am able to put the detailed accounting entries for the Asset Cycle. As highlighted in one of the post  Oracle Assets creates journal entries  for the following general ledger accounts: Asset Cost Asset Clearing Depreciation Expense Accumulated Depreciation Revaluation Reserve Revaluation Amortization CIP Cost CIP Clearing Proceeds of Sale Gain, Loss, and Clearing Cost of Removal Gain, Loss, and Clearing Net Book Value Retired Gain and Loss Intercompany Payables Intercompany Receivables Deferred Accumulated Depreciation Deferred Depreciation Expense Depreciation Adjustment The setup of these accounts is done while you defining the asset books as per below. The number for above accounts can usually map it with Oracle seeded screen of setup;. Fig 1: Accounts and accounting in Fixed Assets Fig 2: Accounts and accounting in Fixed Assets Next we will see the different accounting at various transactional events.  Depreciation A...

AP Invoice Technical Details with Functional Inputs When Invoice Booked and Saved ============================= One row created in ap_invoices_all and its distribution lines created in ap_invoice_distributions_all When Invoice Validated : ====================== ap_invoice_distributions_all.MATCH_STATUS_FLAG='A' ap_invoice_distributions_all.ACCOUNTING_EVENT_ID=NOT NULL(Here 1370092) one row created in ap_accounting_events_all with accounting_event_id=ap_invoice_distributions_all.ACCOUNTING_EVENT_ID ap_accounting_events_all.EVENT_STATUS_CODE='CREATED' ap_accounting_events_all.SOURCE_TABLE='AP_INVOICES' ap_accounting_events_all.SOURCE_ID=ap_invoice_distributions_all.INVOICE_ID= AP_INVOICE_ALL.INVOICE_ID When Invoice Accounted : ===================== ap_invoice_distributions_all.ACCRUAL_POSTED_FLAG='Y' ap_invoice_distributions_all.POSTED_FLAG='Y' ap_accounting_events_all.EVENT_STATUS_CODE='ACCOUNTED' ONE ROW CREATED IN AP_AE_HEADERS_ALL where...

AP Invoice Validation Status (See Metalink doc ID 301806.1) There is no column in the AP_INVOICES_ALL table that stores the validation status. Invoice distributions are validated individually and the status is stored at the invoice distribution level. This status is stored in  AP_INVOICE_DISTRIBUTIONS_ALL.MATCH_STATUS_FLAG. Valid values for the column are: A – Validated (it used to be called Approved) N or null – Never validated T – Tested but not validated The invoice header form derives the invoice validation status based on the following: ‘Validated’ - If all of the invoice distributions have a MATCH_STATUS_FLAG = ‘A’ ‘Never Validated’ - If all of the invoice distributions have a MATCH_STATUS_FLAG = null or ‘N’ ‘Needs Revalidation’ - If there are any rows in AP_HOLDS that do not have a release code. - If any of the invoice distributions have a MATCH_STATUS_FLAG = ‘T’. - If the invoice distributions have MATCH_STATUS_FLAG values = ‘N’, null and ‘A’ (mixed).   Query: ========...

AP_SUPPLIERS: This table replaces the old PO_VENDORS table. It stores information about your supplier level attributes. Each row includes the purchasing, receiving, invoice, tax, classification, and general information. Oracle Purchasing uses this information to determine active suppliers. The supplier name, legal identifiers of the supplier will be stored in TCA and a reference to the party created in TCA will be stored in AP_SUPPLIERS.PARTY_ID, to link the party record in TCA. AP_SUPPLIER_SITES_ALL: This table replaces the old PO_VENDOR_SITES_ALL table. It stores information about your supplier site level attributes. There is a row for unique combination of supplier address, operating unit and the business relationship that you have with the supplier. The supplier address information is not maintained in this table and is maintained in TCA. The reference to the internal identifier of address in TCA will be stored in AP_SUPPLIER_SITES_ALL.LOCATION_ID, to link the address record in TCA...

Query to get Oracle Apps URL SQL: select home_url from icx_parameters; select * from registry$history; SELECT a.application_name, DECODE (b.status, 'I', 'Installed', 'S', 'Shared', 'N/A') status, patch_level FROM apps.fnd_application_vl a, apps.fnd_product_installations b WHERE a.application_id = b.application_id and a.application_id ='200'; SELECT patch_name, patch_type, maint_pack_level, creation_date FROM applsys.ad_applied_patches ORDER BY creation_date DESC