Efficient and User Friendly Concurrent Request Form


Make Concurrent Request Form more Efficient.


 

The Concurrent Request form is possibly the most used form in Oracle E Business Suite and probably the most unpleasant one. Throughout my implementations every business user (from a clerk to C Level managers) gives a black look when the report submission process is presented.

In order to enhance user experience and to reduce multiple steps we have developed and deployed following enhancements to the Concurrent Request Form.

 

CRF

 

 

 

Enhancement

Steps Reduced/eliminated

  1. Auto Refresh functionality tops the list of the enhancement.

When the check box is selected the form/data is Refreshed after specified timer (2 seconds is suggested). The user deselect the check box as and when required.

Reduces 8 to 9 Clicks or [Alt + r] on each request.

Approximately 400+ unnecessary clicks per day.

  1. Rerun Selected Request

uses the cursor placement and rerun the request with same parameters, new request id and refreshes the form

Reduces/Skips 8 Clicks and 5 Form Navigations on each run

Submit a new Request>>Single Request>>Copy>>Select Prior Request>>Submit>>Submit another Request(NO)>>Refresh Data

  1. Copy Request

although this functionality currently exists but if this is made available on the concurrent request form it eliminates few unnecessary steps. When used it takes user directly recent ran request LOV for selection

Reduces/Skips 4 Clicks and 3 Form Navigations on each run

Submit a new Request>>Single Request>>Copy>>Select Prior Request

  1. Submit a New Request and Submit a New Request Set Buttons

Most of the Users use Single Request Submission, they rarely use Request Sets. Therefore users suggested having separate buttons for both of them.

If user Clicks on “Submit a New Request” Button it will directly open the new request form.

Reduces/Skips 2 Clicks and 1 forms on each run

Submit a new Request>>Single Request

Advertisements

Mutli-Currency Receipts for landed cost invoices

We are implementing Landed Cost Management Module (LCM) at one of our client in Kingdom of Saudi Arabia. Now Landed Cost Management is recently released and still pre-mature although it is very useful and effective addition to Oracle EBS but it lacks one of the basic requirements.

I don’t know why Oracle Development didn’t catered this first hand. I am sure around the world whenever anything is Imported landed cost invoice is always different than PO currency.

PO is always raised in Foreign currency and Landed cost (Freight, Insurance, Duty, and local transport) in local currency.

In our case PO is raised in USD, EURO, JPY and landed cost invoices are always in SAR and while matching the landed cost invoices to the item receipt, it does not shows that receipt.

Now as per Oracle this is the intended functionality. PO currency and Invoice Currency Should be same.
This is a enhancement request and under development review.

Well we all know client doesn’t cares about Oracle Enhancement request and Developement review. This is a logical requirement and a basic one also.

Here on this project we are going with customization and recommend the same till oracle releases and standard functionality.

(Be advised this should be tested thoroughly before migrating it to your live environment)

  • Customize ‘Find Receipts for Matching’ Payables form ($AU_TOP/forms/US/ APXRMTCH.fmb) using following steps :
    • Comment out or remove following code fromOTHR_CHRG_MATCH_EVENT.CONSTRUCT_WHERE_CLAUSE program unit==
      — and this clause by default
      app_query.append (‘OTHR_CHRG_MATCH’,
      ‘CURRENCY_CODE = :INVOICE.INV_CURR_CODE’);
      ==
    • Replace ‘poh.currency_code = :invoice.inv_curr_code’ with ‘((:match_qf.match_type = ‘ITEM’ AND poh.currency_code = :invoice.inv_curr_code) OR (:match_qf.match_type <> ‘ITEM’))’ in PO_NUMBER record group
    • Replace ‘RTXN.currency_code = :invoice.inv_curr_code’ with ‘((:match_qf.match_type = ‘ITEM’ AND RTXN.currency_code = :invoice.inv_curr_code) OR (:match_qf.match_type <> ‘ITEM’))’ in RECEIPT_NUMBER record group (at 4 places)
  • Save the changes and Compile the form to generate APXRMTCH.fmx.
  • Go to $AP_TOP/forms/US and take a backup of APXRMTCH.fmx (i.e copy APXRMTCH.fmx to APXRMTCH.fmx.bak)
  • Copy APXRMTCH.fmx (from step b) to $AP_TOP/forms/US

Wollaaa!!

Do share your feedback.

Running Oracle Application on Google Chrome

Running Oracle Application on Chrome While Running Oracle Application on Google Chrome you will receive this error  FRM:92120: Registry file http://server:port/forms/oracle/forms/registry/Registry.dat is missing.

Because Google Chrome redirects you to a incorrect URL which is not available in your registry.

In Order to run Oracle application on Google Chrome I would Recommend a Spoofer Google Extension.

1. Go to http://spoofer-extension.appspot.com and install the User-Agent switcher

2. Restart your browser and now you should see a mask icon right next to your wrench icon.

3. Click on the wrench. Goto Options

4. Goto Extension Tab

5. Click on Options of User Agent Switcher for Chrome

6. Create Following Entry in Custom Domain List.

Enter http://f12.ABCGROUP.com:8020 in Domain segment

Select Mac Safari 4 from the drop Down Menu

Enter Apple, Inc. in Navigator.Vendor Segment.

Click Add.

7. Clear Your browsers History, Restart your computer and restest the Issue.

Solution for Bug 13412084: RESTRICT PAYMENT: IT SHOULD NOT ALLOW PAYMENT BEFORE INVOICE ACCRUAL

We had this issue @ our client where user accidentally  made payment on 21-Jan-11 instead of 21-Jan-12. These kind of mistakes are very frequent. The only Solution you have is to Void that payment and recreate a new one. But the problem doesnt ends there. To clear that you have to open that particular period. Transfer the accounting of payment and reversal and create a new payment.

This practise annoys the data entry user the payable key user and the General Ledger owner because they have to do that same practise all over again.

I Don’t know why we don’t have any profile option to control this. I have already raised an ER for this which might take a couple of more years. As we all know it will might come in future releases. (Please add your vote for this ER by raising an SR)

The only option we were left with was to create a custom.pll and use that. Below you have the step by step procedure to achieve this goal.

(courtesy of Mr Abid Hussain).

1)      Open terminal.

2)    Issue command Xhost + , this command will enable you to make your connection to the server from any host.

3)    Connect to the user by issuing command su – appltest (In case of Al-Abbas clone instance)

4)      cd /u02/test/apps/apps_st/appl/au/12.0.0/resource (Path where custom.pll reside check it at your instance).

5)      frmbld

6)      Select library Custom.pll (you will have to select manually)

7)      Include Library APPCORE2

8)      Now open the Package body of Custom.pll

9)      Now add the fallowing code in procedure “Event”

10)   Form_Name Varchar2(30)  := name_in(‘system.current_form’);

Block_Name Varchar2(30) := name_in(‘system.cursor_block’);

L_Gl_Date_scs Date;

L_invoice_id_scs Number;

11)  Now add the fallowing code in Begin.

If form_name = ‘APXPAWKB’ Then

If event_name = ‘WHEN-VALIDATE-RECORD’ Then

If block_name = ‘ADJ_INV_PAY’ Then

L_invoice_id_scs := name_in(‘ADJ_INV_PAY.INVOICE_ID’);

Select Gl_Date Into L_Gl_Date_scs From ap_invoices_all

Where Invoice_id = L_invoice_id_scs;

If name_in(‘PAY_SUM_FOLDER.CHECK_DATE’) <  L_Gl_Date_scs Then

fnd_message.set_string(‘Payment Date Should Not less Then Invoice GL Date’);

fnd_message.show( );

Raise Form_Trigger_Failure;

End If;

Else

Null;

End If;

Else

Null;

End If;

Else

Null;

End If;

Now you can call this custom.pll in personalization on Payment Workbench Form.

Cheers!!

Pre – Upgrade Functional Steps — First Darft

¦ Oracle General Ledger

  • Run Accounting Setup Manager Diagnosis for MRC
  • TUMS step key: GL_MRC_REVIEW_SETUP

The Accounting Setup Manager replaces many forms and user interfaces in this release. We recommend that you run the Accounting Setup Manager Pre-Update Diagnosis report to identify potential incompatibilities that would prevent you from using some new features. The report identifies Release 11i setup for Multiple Reporting Currencies, General Ledger, Global Accounting Engine, Assets, Payables, and Receivables. In order to run this report successfully, apply patch 5259121 to your Release 11i APPL_TOP. To access the report, run the Accounting Setup Manager Pre-Update Diagnosis report in the Standard Request Submission form from a General Ledger responsibility. Review the report and fix any setup it identifies as problematic. Note that modifying setup configurations is not easily done after the upgrade is complete.

  • Run the Accounting Healthcheck found in Note 416699.1 on My Oracle Support and Misclassified accounts (if available)
  • Resolve any issues that arise
  • Run the Segment Value Inheritance Program when changes are made tothe segment qualifiers for segment values of the chart of accounts.
  • Next, complete all your period close actions/processes. This is the time to validate and account for as much data as possible and make sure that everything is transferred to GL
  • Run the General Ledger Period Closing diagnostics test to verify that a ledger period is ready to close.
  • After successfully closing your period, run your standard reconciliation and account balance reports and resolve any issues that arise
  • run the Accounting Healthcheck again and resolve any remaining data issues
  • Check and Clear GL_interface Tables for duplicate, error and unprocessed events.

¦ Oracle Payables

  • Import all invoices from the Payables open interface.
  • TUMS step key: AP_IMPORT_INVOICES_CHECK

In this release, global descriptive flex fields (GDFs) are obsolete and are moved into tax and payment columns. Several validations are performed based on the country the invoice is imported from on these GDFs. They are not upgraded in the open interface tables. Import all invoices that have not yet been imported by running the Open Interface Import program on the 11i APPL_TOP. Resolve any rejections and resubmit the program until all invoices are imported.

  • Confirm or cancel all Unconfirmed Payment batches.
  • TUMS step key: AP__CNFM_PAY_BATCH_CHECK.

With the introduction of Oracle Payments, the new payment batch model is not compatible with 11i payment batches. To ensure that there are no in-process payment batches included in the upgrade processing, either confirm or cancel all payment batches before you begin.

Subledger Accounting (only if you they have subledger acounting).

  • TUMS step key: N/A

During the upgrade, existing accounting data from the subledgers is upgraded into the new Oracle Subledger Accounting data model. By default, the upgrade updates the data for the current fiscal year, as well as the necessary periods of the previous fiscal, to ensure that there are at least six periods included in the upgrade (occurs when the upgrade is performed in the first half of the fiscal year).You may need to run the SLA Pre-Upgrade program if you are using Oracle General Ledger and at least one of the following subledgers: Assets, Cost Management, E-Business Tax, Payables, Receivables, or Projects Accounting. This optional program allows you to change the default number of periods of historic data to be upgraded. You can define a larger range of periods to be upgraded, and you can decide to perform the upgrade for all or most of the data during the downtime phase. This is an important decision because some of the Oracle Subledger Accounting functionality, such as accounting reversals and business flows, rely on the existence of previous accounting
If you do not perform a complete upgrade of the accounting data, Oracle Subledger Accounting allows you to perform an additional upgrade of the data by running the SLA post-upgrade process whenever the missing data is required (see Subledger Accounting, page G-9 in Appendix G, page G-1). This program is executed at the same time as daily operations. As a result, it may have an impact on overall system performance.
If you need to change the default number of periods of historic data to be upgraded, you must apply patch 5233248 to your Release 11i APPL_TOP and submit the SLA Pre-Upgrade program. When submitting this program, you can enter the following parameters
• Migrate all sets of books: Possible values are Yes (SLA Pre-Upgrade program updates the periods in all sets of books) or No (SLA Pre-Upgrade program updates the periods that belong to the selected set of books).
• Set of books: Set of books to be upgraded where you have selected to upgrade one set of books.
• Start Date: Date to be used to determine the first period to be upgraded. Does not have to be the starting date of a period – the initial period is determined as the first period in which this date falls.

  • Run the Payables Accounting Health Check script (My Oracle Support Doc ID 416699.1 to ensure that there are no inconsistencies in your 11i data.
  • Reslove any issues that araise.
  • Next, complete all your period close actions/processes. This is the time to validate and account for as much data as possible and make sure that everything is transferred to GL
  • run the Accounting Healthcheck again and resolve any remaining data issue.
  • please run the needed reports to balance within PayablesTrial Balance, Posted Invoice Register, and Posted Payment Register reports. You’ll also need to run the Account Analysis in General Ledger and reconcile that to Payables.

¦ Oracle Receivables

  • Run Accounting Healthcheck
  • Import/Clear All AR interfaces.
  • Ensure that the Create Accounting program in Receivables has successfully completed.
  • Resolve any issues that arise
  • Review the Un-posted Items reports to confirm that all items are posted to the General Ledger
  • Review the Posting Execution Report to check that journal entries transferred from Receivables are successfully posted to the General Ledger. Receivables automatically prints the Posting Execution Report that displays a summary line for each currency within every category of transaction that you transfer.
  • Next, complete all your period close actions/processes. This is the time to validate and account for as much data as possible and make sure that everything is transferred to GL
  • run the Accounting Healthcheck again and resolve any remaining data issue.
  • The following steps are recommended for reconciliation of Receivables with General Ledger:
  • Run the Receivables Reconciliation Report as the first step in the reconciliation process. It displays summary information consistent with detailed registers and journal reports. It also displays transactional data in an Activity column, and accounting data in a Journal column. If any discrepancies exist, run the following reports for more details:

Transaction Register versus Sales Journal Adjustment Register versus Adjustment Journal Applied Receipts Register versus Journal Unapplied and Unresolved Receipts Register versus Journal Invoice Exception Report Run the Ageing – 7 Buckets – By Account OR the Ageing – 4 Buckets report to view beginning and ending customer balances, and to compare with AR Reconciliation Report balances. Run the Journal Entries Report after completing Create Accounting (Final Accounting) to show the accounting data transferred to Subledger Accounting. This should be matched with the AR Reconciliation Report to ensure that Receivables versus Subledger Accounting reconciliation is done.
Run the AR to GL Reconciliation Report to ensure that there are no differences. Run this report after transactions in Receivables are posted to General Ledger and there are no unposted transactions per the “Unposted Items” report. This report compares the account balances in Receivables to those in General Ledger and highlights the journal sources where discrepancies might exist.

¦ Oracle Cash Management.

reader’s Input required

¦ Oracle Fixed Assets.

  • By default, transactions in the current fiscal year in Assets books will have their accounting lines migrated to the Subledger Accounting model. Accounting for current period depreciation will be upgraded only if depreciation has already run for the period, and the period remains open. After the upgrade, you can run the SLA post-upgrade process to update accounting for past transaction data as needed.
  • Important reports such as the transaction diagnostics report and reconciliation reports should be run before closing the period to ensure that the accounting entries are reviewed and verified.

¦ Oracle Purchasing.

reader’s Input required

¦ Oracle Order Management.

reader’s Input required

¦ Oracle Project Costing and Project Billing.

  • Complete distribution, transfer, and tieback of expense reports (conditional)
  • TUMS step key: PA_COMPLETE_DIST_TIEBACK_EXP
  • If you create expense reports using Pre-Approved Expenditure Entry or import unaccounted expense reports from external systems, then run the following concurrent programs for each operating unit that uses Oracle Projects as a source entry point for expense report creation, adjustment, or both:

• PRC: Distribute Expense Report Costs2-18 Oracle E-Business Suite Upgrade Guide

• PRC: Interface Expense Reports to Payables • Expense Report Import (must be run from the Payables responsibility)

• PRC: Tieback Expense Reports from Payables Your Projects application specialist should ensure that all transactions are successfully interfaced and that no exceptions remain.

  • Complete transfer and tieback of cost, cross charge, and revenue (conditional)
  • TUMS step key: PA_JRNL_IMPORT_TIEBACK_REV.
  • Run the following concurrent programs for each operating unit implemented in Oracle Projects and Oracle Grants Accounting. Ensure there are no exceptions.

• Journal Import: Complete Journal Import in General Ledger for all project journal sources

• PRC: Tieback Labor Costs from General Ledger.

• PRC: Tieback Usage Costs from General Ledger.

• PRC: Tieback Total Burdened Cost from GL.

• PRC: Tieback Cross Charge Distributions From General Ledger (does not apply to Grants Accounting).

• PRC: Tieback Revenue from General Ledger.

¦ Oracle Property Manager.

reader’s Input required