Friday, February 22, 2013

R12 - Project Statuses

Project Statuses

How Project Statuses Control the Transactions

(N) Projects Super User >  Setup > System > Statuses



We define project statuses in the above window.

As you can see in the above window, for each status we can select which actions are allowed and which actions are restricted. To allow charges on a project, you must assign the project a status with the status control Create New Transactions enabled. To allow users to adjust transaction on a project, you must assign the project a status with the status control Adjust Transactions


How to Define Project Statuses



To define a status:



1. Navigate to the Statuses window.
(N) Projects Super User >  Setup > System > Statuses

2. Select the Status Type that you want to define (such as Project).

3. Enter a Status name. Status name should be unique.

4. Every status must map to a predefined system status. Therefore you need to map a  System Status to the new status you are defining. 

5. Optionally enter a Description.

6. Optionally enter Effective Dates.

7. If you want this status to be eligible for use as the starting status for the kind of object it is associated with (such as a project, task, assignment, or candidate), check the Starting Status box.

8. Status Controls: The Status Controls region contains a list of actions that are allowed or restricted for each status.

When you create a new status, the system status you have selected for the status determines which actions are allowed for the object to which the status is assigned. If you want to change the status controls from the default settings, you can select or clear the Allow box.

The Default check box is display-only, and contains the original setting of the Allow check box.
For some system statuses, there are Allow check boxes that cannot be changed. For example, if a project status maps to the Closed System Status, the project status cannot allow Create New Transactions.

9. Next Allowable Statuses: Use this region to define the next allowable statuses for each status.

Four radio buttons control the next allowable statuses you can enter:
• All: The current status can be changed to any status. This is the default value.
• None: The current status cannot be changed.
• System Status: The Next Allowable Statuses are all system statuses.
• Status: The Next Allowable Statuses are all user-defined statuses.

If you choose System Status or Status, you can then enter as many next allowable statuses as you want.

10. Workflow: If you want to initiate workflow when an object is updated to this status, select the Workflow tab and select the Enable Workflow check box and enter a value in the following fields:

• Item Type. Enter the name of the Workflow Item Type to be used for this status.

• Process. Enter the name of the workflow process to submit for this status.

• Success Status. Enter the status to assign to the object upon successful completion of workflow.

• Failure Status. Enter the status to assign to the object if workflow fails. (This can be the same as the current status.)





11. Save your work.


Sample Business Case


When the project is created, it's initial status is Submitted. A workflow will be triggered and the delegation authority should approve the project before it can be used while creating the below transactions:-

  1. Purchase Orders
  2. Invoices
  3. Expenditures
But it takes some time for the delegation authority to approve the project. Before the project is approved, users receive few POs and Invoices related to the un-approved project.

If you want to enter the transactions against the un-approved project, then you need to enable the 'Create New Transactions' check box in the Project Statuses Window.

References:-

Oracle Documentation

Wednesday, February 20, 2013

How to setup Cost Manager to run every 5 Minutes

How to setup Cost Manager to run every 5 Minutes


Follow the below navigation to setup Cost Manager to run every 5 minutes:-

1/ (N) Inventory Super User > Setup > Transactions > Interface Managers




2/ Enter number 5 in the Minutes field. Ensure that hours and seconds fields have zero values

Note: To Launch the Cost Manager, click on Tools > Launch Manager as shown below:-


Tuesday, February 19, 2013

What is D-U-N-S Number in Suppliers Page?

D-U-N-S Number in R12 Suppliers Page

When you start creating a supplier in Oracle R12, you will notice a field with the name D-U-N-S Number as shown below:-


What is D-U-N-S Number?

Created in 1962, the Data Universal Numbering System or D-U-N-S® Number is D&B's copyrighted, proprietary means of identifying business entities on a location-specific basis.
Assigned and maintained solely by D&B, this unique nine-digit identification number has been assigned to over 100 million businesses worldwide.

A D-U-N-S® Number remains with the company location to which it has been assigned even if it closes or goes out-of-business.

For more details about D-U-N-S number please refer to the below link:-

http://dnb.com.au/Credit_Reporting/The_quality_of_DandBs_data/DUNS_Number/index.aspx


Monday, February 18, 2013

Pay on Receipt Functionality in R12 PO Module

Pay on Receipt:- Using this functionality we can automatically create an invoice for a PO when we enter a receipt for the respective PO.

Demo of Pay on Receipt Functionality in R12 Vision Instance 

Follow the below steps:-

Create a Standard PO with the below values:-

1/ Enter the PO Header details with the below values:-

Supplier = Advanced Network Devices
Site = SANTA CLARA-ERS
Ship To =V1- New York City
Bill to = V1- New York City

2/ Enter the PO Line details with the below values:-

Num=1
Item=f10000
Quantity=2



3/ Save the PO and note down your PO Number

4/ Click on (B) Terms and ensure that the value 'Receipt' is selected in the field 'Pay On'


5/ Close the Terms Window

6/ Review your shipments

7/ Review your distributions

8/ Close distributions and shipments window

9/ Approve the PO and ensure that the status is approved.

Create a Standard Receipt with the below values

10/ (N) Purchasing Vision Operations (USA) > Receiving > Receipts

11/ Query your PO and enter all the required receipt details and save the transaction.

12/ As soon as you save the receipt transaction, in the background the below programs will be submitted:-


  • Receiving Transaction Processor
  • ADS  (Pay On Receipt AutoInvoice)
  • Payables Open Interface Import
13/ View the output of the Payables Open Interface Import. You can notice the creation of an invoice in AP Module as shown below:-



14/ Query the invoice in the AP Module and view the invoice and its distribution details as shown below:-







Additional Notes


  1. Profile Options related to 'Pay On Receipt'
  • PO: ERS Invoice Number Prefix
  • PO: ERS Aging Period

References:-

Oracle Documentation

Details of Default Values and How They are Selected for PO fields?

The precedence of default values in PO fields is given below:-


  1. Financials Options
  2. Purchasing and Receiving Options
  3. Supplier
  4. Supplier Site
  5. Item
The highest number takes precedence over the lowest number i.e.,:-

2 takes over 1
3 takes over 2
4 takes over 3
5 takes over 4

R12 - Tables related to Purchasing Module

Tables related to the Purchasing Module



1. Purchase Requisition Tables


  • PO_REQUISITION_HEADERS_ALL: Contains data of Requisition Headers
  • PO_REQUISITION_LINES_ALL: Contains data of Requisition Lines
  • PO_REQ_DISTRIBUTIONS_ALL: Contains accounting data of Requisition Lines


2. Purchase Order (PO) Tables

Using the below tables we can find the high level details of a Purchase Order:-

  • PO_HEADERS_ALL:- contains the header information
  • PO_LINES_ALL:- contains the lines details
  • PO_LINE_LOCATIONS_ALL:- contains the shipment details
  • PO_DISTRIBUTIONS_ALL:- contains the distribution details
  • PO_RELEASES_ALL:- contains the information about blanket and planned purchase order releases

3. Receipt Tables


  • RCV_SHIPMENT_HEADERS:-stores common information about the source of your receipts or expected receipts.
  • RCV_SHIPMENT_LINES:-stores information about items that have been shipped and/or received from a specific receipt source
  • RCV_TRANSACTIONS:-stores historical information about receiving transactions




Note: For more details refer to Oracle e:-Business Suite Electronic Technical Reference Manual  that is available from Oracle MetaLink.

Thursday, November 3, 2011

Journal Approval Workflow on 11i

Follow the below steps to enable Journal Approval Workflow on Oracle 11i
1. Journal Approval Overview

The GL Journal Approval Process obtains the necessary management approvals for manual journal batches. The process validates the journal batch, determines if approval is required, submits the batch to approvers (if required), then notifies appropriate individuals of the approval results.

The process has a result type of GL Journal Approval Process Result that gives one of four results:
• Approval Not Required: The journal batch does not need approval.
• Approved: The journal batch was approved by all necessary approvers. In some cases, this may be the preparer.
• Rejected: The journal batch was rejected by an approver.
• Validation Failed: The journal batch failed the validation process and was never submitted to the approver.

2. Setups Required to Enable Journal Approval

2.1 Prerequisites:

1/ Setup Oracle Workflow including the configuration of the GL Journal Approval (Required)

2/ Set the following two profile options accordingly:
- Journals: Allow Preparer Approval (specifies if preparers can approve their own Journal batches)
- Journals: Find Approver Method (specifies the default approval method For the Journal Approval process) (Optional)

2.2 Setups Required:

Following setups are required to enable journal approval workflow.

1/ Enable Journal Approval for the Set of Books (mark the Enable Journal Approval check box on the Set of Books window)

2/ Specify journal sources that require journal approval by selecting the Require Journal
Approval check box for each journal source that should be subject to approval

3/. Create an approval hierarchy:
If using a shared install of Oracle Human Resources, use the Enter Person form of GL to enter all employees who are involved and preparing and approving journal entries and batches.

If using a full install of Oracle Human Resources, enter employees in the People window from the Human Resources Responsibility (required).

When entering employee, enter the employee's supervisor or manager name (this is the default next approver for journal entries and batches)

4/. Define authorization limits from the Journal Limits window

References:-

Oracle Documentation