Quickly Find Package Body and its Subprogram in SQL Developer

1. Enter the package name in SQL Developer Worksheet;

2. Click Shift+F4 to open package definition;

3. In the window for a package definition, you can press Ctrl+click on a procedure or function name to perform the Open Declaration command, which opens the procedure or function implementation (body specification) in a new window.

Object Version Number (object_version_number)

Object Version Number (OVN) is a column in a database table. It is used to track multiple changes to a record. When a new row is inserted, the OVN is set to 1. As updates are performed on the row through the Forms, the OVN is incremented. The OVN is transferred with a queried row. If an update is attempted when the change is saved to the table, the current OVN is compared with the value being passed back from the transaction. If the two are the same, the update can be committed to the table. If the two are different, the update is rejected and flagged with an error. The transaction must be re-queried, and the update made again to the more current version of the row.

APIs and Forms use OVNs similarly. Every published API has the p_object version_number control parameter.

For Create APIs, this parameter is defined as an OUT parameter: the API assigns the object version number to 1 for row inserts. For Update APIs, the parameter is defined as IN OUT, and is mandatory in the API call.

The current value must be passed in the API call and it is compared to the version on the row in the table. If the versions are different, the error HR_7155_OBJECT_LOCKED is raised. The information can be re-queried for a more current version.

Rejection Reason of Expense Report Import

To import expense report to AP invoice, we need to run Expense Report Import program from AP module. Some expense report may be not able to convert to AP invoice successfully, but fortunately, “Expense Report Import Report” will list all of the expense report transferred to AP invoice successfully and unsuccessfully. In the “Exceptions Report” part, you can also find out the rejection reason for the failed expense report from “Expense Report Import Report”.

Blow I listed all of the rejection reasons and the explanations from Oracle Document, the user can try to correct system against the reason.

  • Addr Line [1-3] Too Large. Invoice Import attempted to create a supplier from an employee and Address Line 1-3 for the employee home address exceeds 35 characters.
  • City/State/Country] Too Large. Invoice Import attempted to create a supplier from an employee and the City/State/Country for the employee home address exceeds 25 characters.
  • Create As Supplier. You are using manual supplier number entry and you did not enter the employee as a supplier before submitting Invoice Import.
  • Create Duplicate Supplier. You are trying to create an invoice from an expense report for an employee name that is not already a supplier and a supplier name already exists for the same employee name.
  • Duplicate Report. The invoice number already exists for an employee or supplier.
  • Future Date. The expense report date, the accounting date which determines the period in which your general ledger recognizes an invoice expense and liability, is in a closed period and is after the date you entered an expense report.
    If the expense report date is in a closed period but before the date you entered an expense report, Payables creates an invoice from this expense report so it does not appear on the Exceptions Report.
  • No Exchange Rate. The Payables option Require Exchange Rate Entry is Yes and the expense report is in a foreign currency and has no exchange rate information.
  • No Home Address. The expense report is being sent to the employee’s home address, but there is no home address defined for the employee.
  • No Location. You entered an employee as a supplier without entering a location.
  • No Office Address. The expense report is being sent to the employee’s office address, but there is no office address defined for the employee.
  • No Withholding on Site. Supplier site does not have the Allow Withholding Tax option enabled and you tried to import an invoice that a) has an invoice distribution with an automatic withholding tax group assigned to it, b) has an invoice distribution with a line type of Withholding Tax, or c) has a withholding tax group assigned to it.
  • Not A Supplier. The Payables option Automatically Create Employee as Supplier is not enabled, and the employee does not already exist in Payables as a supplier.
  • Zip Code Too Large. Invoice Import attempted to create a supplier from an employee on an expense report and the Postal Code for the employee home address exceeds 20 characters.