Period End Close - Inventory

Once closed, Inventory period can't be re-opened from Apps. Execute below to re-open a closed inventory period:

SELECT acct_period_id period, open_flag, period_name name,  
      period_start_date, schedule_close_date, period_close_date  
      FROM  org_acct_periods  
      WHERE organization_id = &org_id  
      order by 1,2;
UPDATE org_acct_periods 
SET open_flag = 'Y', 
period_close_date = NULL, 
summarized_flag = 'N' 
WHERE organization_id = &&org_id 
AND acct_period_id >= &&acct_period_id; 
DELETE mtl_period_summary 
WHERE organization_id = &org_id 
AND acct_period_id >= &acct_period_id; 
DELETE mtl_period_cg_summary 
WHERE organization_id = &org_id 
AND acct_period_id >= &acct_period_id; 
DELETE mtl_per_close_dtls 
WHERE organization_id = &org_id 
AND acct_period_id >= &acct_period_id; 
DELETE cst_period_close_summary 
WHERE organization_id = &org_id 
AND acct_period_id >= &acct_period_id;  
commit

Oracle Alerts

SELECT a.* FROM ALR_ALERTS a WHERE ALert_Name LIKE 'XXX%Eco%';
SELECT * FROM ALR_ACTIONS WHERE UPPER(to_recipients) LIKE '%CHUA%';

Oracle E-Business Suite (EBS) Upgrades

Custom code can be expensive to develop but even more expensive to maintain.

Minimize EBS custom code

Try to eliminate as much custom code as possible. Research the more recent releases to see if new functionality replaces the homegrown code.

Set up queries or monitor the concurrent requests to see if reports and even interfaces are being used.

Global companies may see that the improved localization functionality in R12 can allow them to eliminate some custom code as well.

If you have taken copies of standard Oracle reports and modified them, the best practice is to take a new copy of that object from the new release and reintroduce the modifications. Don't spend inordinate amounts of time trying to get an old 11i report to work in an R12 environment.

The same recommendation holds true for workflow items.

While many standard open interfaces and APIs are typically not heavily changed during the migration to EBS R12, you may rename interfaces, and add new or additional parameters. 

Event alerts are typically disabled during the upgrade, so you may need to re-enable them prior to testing.

Customizations to Oracle Forms can be tricky, as they are probably one of the most invasive customizations besides database triggers. If your business processes require modifications to the forms, replace them with personalizations as much as possible. If you do have customized forms, look to see if those forms will exist in the new, plain-vanilla version. Some EBS modules have quite a few brand-new forms.

You should be able to replace some old forms with new OA Framework-based forms. 

Finally, consider the third-party products that you may have previously licensed. You may be spending extra money for functionality that has now been introduced into the applications. Examples include third-party form and label software, check printing software, invoice printing and delivery solutions, and more.

Oracle Payables (AP) - Elementary

• Payables Accounting Process - to create accounting entries in Payables.

1. The Payables Accounting Process APACCENG writes to the following tables:
   
   ap_accounting_events_all
   ap_ae_headers_all
   ap_ae_lines_all
   
   For invoices it updates the accounting_event_id in ap_invoice_distributions_all
   For payments it updates the accounting_event_id in ap_invoice_payments_all
   For Clearing events it updates the accounting_event_id in ap_payment_history_all

2. Parameter Submit Transfer to GL. If you want to initiate the Payables Transfer to General Ledger program immediately after the accounting entries are created, then enter Yes.
3. The Payables Accounting Process is obsoleted in R12 and replaced by the Create Accounting Program.

• P