Skip to main content

Expenditure Types still not by Operating Unit in R12.1.1

I was surprised to find out when installing R12.1.1 that Expenditure Types are still not Operating Unit (OU) dependent. Oracle have made a big push to add multi-org functionality to most areas of the E-Business Suite in R12, but they seem to have missed Expeniture Types. This is most frustrating in environments where there are two OUs within one business using Oracle Projects;

  • It is difficult to identify between each OU who owns / has set up which expenditure types
  • Related to the former, when entering transactions (e.g. in Purchasing and Payables), users are likely to choose expenditure types intended for other OUs
Expenditure Types are still not Operating Unit sensitive in R12.1.1
There are some workarounds of course. For example:
  1. Introducing a descriptive flexfield (DFF) segment on the expenditure type to flag which OU owns it
  2. Using Transaction Controls to restrict which expenditure types are chargeable
  3. Customise the Expenditure Type list of values in AP/PO and restrict the values available by referencing the DFF in point 1 above
  4. Prefix expenditure type names with a code relating to the OU
None of these workarounds are ideal for obvious reasons. However, I am hoping that this is something that will be brought into the core product. If this functionality is made available, there will need to be the ability for users to share Expenditure Types between OUs (akin to Rate Schedules). This will be needed for all of those organisations who are happy to share expenditure types between OUs!

https://www.rfsuny.org/media/RFSUNY/Procedures/ae_transaction-controls_pro.htm
Labels:

Comments

  1. moumitaApril 11, 2019 at 11:14 PM

    Thanks for sharing this blog. The content is beneficial and useful. Very informative post.
    finance write for us

    ReplyDelete

Post a Comment

Popular posts from this blog

Create Accounting for a Payment generates errors 95333 and 95359

Create Accounting for a Payment generates errors 95333 and 95359 Error: 95333: A conversion rate does not exist to convert USD to AUD for the conversion type Corporate and conversion date 20-MAR-09 for line -25. Please use the Daily Rates form in General Ledger to enter a conversion rate for these currencies, conversion date and conversion type. 95359: There is no accounted amount for the subledger journal entry line. Please inform your system administrator or support representative that: The source assigned to the accounting attribute Accounted Amount has no value for extract line number 88547. Please make sure the source assigned to the accounting attribute Accounted Amount has a valid value, or assign a different source to this accounting attribute. Solution: 1. Specify a conversion rate for the currencies and conversion date mentioned in the error message 95333 Navigation under the General Ledger responsibility: Setup > Currencies > Currency Rates Manager > Daily Rates ...
15 comments
Read more

Public API’s for FA Transactions

Public API’s for FA Transactions So far Oracle FA is have all the good things except the lack on reporting.Oracle FA is now offer lot of public API's that can be used to interfacing with third party or Oracle application other modules. Here are some of transaction's API's:   Additions API if you have requirement to add assets directly via PL/SQL then use  FA_ADDITION_PUB.DO_ADDITION. If you have selected the Allow CIP Assets check box on the Book Controls window of a tax book when adding CIP assets using the Additions API, the this API automatically adds those CIP assets to that tax book at the same time that they are added to the corporate book. Adjustments API you can make cost adjustments to your assetsdirectly via PL/SQL using  FA_ADJUSTMENT_PUB.DO_ADJUSTMENT  for any  process adjustment. Detail can be found in appendix H) You can use this API if you have a custom interface that makes it difficult to use with the existing Oracle Assets interfaces for adjusti...
Post a Comment
Read more

AP Table Relation Oracle Apps

AP Table Relation Oracle Apps ORACLE PAYABLE TABLE RELATION Source Table Dependent Table Condition AP_INVOICE_LINES_ALL AIL ZX_LINES_SUMMARY ZLS AIL.invoice_id = ZLS.trx_id and  ZLS.application_id  = 200 and  ZLS.entity_code  = 'AP_INVOICES' and  ZLS.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.summary_tax_line_id = ZLS.summary_tax_line_id AP_INVOICE_LINES_ALL AIL ZX_LINES ZL AIL.invoice_id = ZL.trx_id and  ZL.application_id  = 200 and  ZL.entity_code  = 'AP_INVOICES' and  ZL.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.line_number = ZL.trx_line_number AP_INVOICE_DISTRIBUTIONS_ALL AID ZX_REC_NREC_DIST ZD AID.invoice_id = ZD.trx_id and  ZD.application_id  = 200 and  ZD.entity_code  = 'AP_INVOICES' and  ZD.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and...
Post a Comment
Read more