Pages

Showing posts with label Oracle Purchasing. Show all posts
Showing posts with label Oracle Purchasing. Show all posts

04 November 2012

Oracle Purchasing Enables The Automatic Creation of Sourcing Rules Setup

Oracle Purchasing enables the automatic creation of Sourcing Rules, Sourcing Rule
Assignments and Approved Supplier List entries during Blanket Agreement approval
submission. The system automatically creates the relevant entries, once the Blanket
Agreement is approved

1) A new Profile Option "PO: Allow Auto-generate Sourcing Rules and ASL" has been
introduced. The default value is 'None'. In order to activate this feature, the profile option
value needs to be set to either "Create Only" or "Create and Update".
If the value is set to "Create only" then the "Enable Automatic Sourcing" checkbox and
the "Release Generation Method" field are visible and can be updated on the Approval
window.
If the value is set to "Create and Update", then the "Enable Automatic Sourcing"
Checkbox, the "Update Sourcing Rule and ASL Entries" checkbox and the "Release
Generation Method" field are visible and can be updated on the Approval window.
Note: If the Archival mode being used for Blanket Agreements is "Archive on Print", this
feature cannot be used and the new fields and checkboxes would not be visible in the
Approval window. User must select "Archive on Approve" to use this feature

2. Sourcing Rule Name Prefix can be customized. The prefix value is read from the
activity attribute "PO Sourcing Rule Name Prefix" in PO Approval Workflow. The
default value is "PURCH".
Note: The new Sourcing Rules will be assigned

26 July 2011

Purchasing Encumbrance Accounting Concepts and Process


Encumbrance accounting is a form of budgetary control within Oracle Applications which allows a company to allocate funding for specific accounts.  There is a funds checking feature integral to encumbrance accounting which checks for funds availability on those accounts and can either prevent (absolute), warn (advisory) or ignore (none) funding availability (dependent on how each account is defined in GL) for the specific transaction (requisition or purchase order)
that is currently being performed
Basic Process
---------------------
The basic process flow for encumbrance accounting activity related to Oracle Purchasing typically is as follows:
1. Create a requisition.
2. Approve and reserve funds for the requisition.
3. AutoCreate requisition onto a purchase order.
4. Approve and reserve PO (which automatically reverses the requisition funds
   reservation)
5. Receive against the purchase order (either period-end or online accruals)
   and the funds are reversed for the amount received and entered against the
   charge account

Purchasing Setup: Encumbrance Accounting

Setting up encumbrance accounting actually has very few actions that need to be performed in Oracle Purchasing module. The primary level of effort required for encumbrance accounting setup is in the General Ledger module. There is one action that can be taken by PO and it deals with the AP form Financial Options
Here are some quick setup steps for encumbrance accounting. The setup details may differ depending on the business needs. the steps included here are for Release 11

1) Define the Encumbrance Account
    1.1. Navigation in GL: Setup -> Financials -> Flexfields -> Key -> Values
         Navigation in PO: Setup -> Financials -> Flexfields _> Key -> Values
    1.2. Perform a find by entering the following criteria:
         Application: Oracle General Ledger
         Title: Accounting Flexfield
         Structure: <name of a structure to be used>
         Segment: Account
    1.3. Click the Find button.
    1.4. Add a new segment value.
         Value: (enter your own)
         Description: Reserve For Encumbrance

07 July 2011

Purchase Order Types In Oracle Purchasing

Purchase Order Types
Oracle Purchasing provides the following purchase order types: Standard Purchase Order, Planned Purchase Order, Blanket Purchase Agreement and Contract Purchase Agreement. 



You can use the Document Name field in the Document Types window to change the names of these documents. For example, if you enter Regular Purchase Order in the Document Name field for the Standard Purchase Order type, your choices in the Type field in the Purchase Orders window will be Regular Purchase Order, Planned Purchase Order, Blanket Purchase Agreement and Contract Purchase Agreement

Standard Purchase Orders
You generally create standard purchase orders for one–time purchase of various items. You create standard purchase orders when you know the details of the goods or services you require, estimated costs, quantities, delivery schedules, and accounting distributions. If you use encumbrance accounting, the purchase order may be encumbered since the required information is known

Blanket Purchase Agreements (BPA)
You create blanket purchase agreements when you know the detail of the goods or services you plan to buy from a specific supplier in a period,

PO Approval Hierarchy Methods

Oracle Purchasing offers three methods to route documents for approval..

1. Position Approval hierarchy
2. Employee/Supervisor approval hierarchy
3. Advanced Approval Support for Requisitions

1. Position Approval hierarchy
Position Hierarchies are hierarchies that have a position relationship. By position, we mean position that are attached to employees. Purchasing utilizes positions as a roadmap to determine how and where documents will be routed once the approval process has been initiated. It is first necessary to have created all positions that are going to be used in the system. Once all positions have been created, it is necessary to build the position hierarchy. Each position has approval limits, so when a purchase order exceeds the limits of the position, the purchase order is forwarded onto the next position in the Hierarchy.

2. Employee/Supervisor approval hierarchy
Employee/Supervisor approval hierarchy uses the employee-supervisor relationships.
To implement this form of approval routing, you need only to define jobs. The job will then serve as the tie to the Approval group, and based on the approval limits from the Approval Group, the Document will either be Approved or Forwarded to the Employees’ Supervisor. If no Supervisor

PO Approval Hierarchy Forward Method

If Position Hierarchy is used and two employees are attached to a particular position, then the application will select the forward-to person based on alphabetical name order.

Below is an example for better understanding.

Abdulla (Clerk) and couple of more clearks report to position Manager (Materials). James and Smith have the position Manager (Materials) attached.

In the above scenario, when Abdulla (Clerk) chooses the Approve button without entering a forward-to person, and the next position above the clerk is the Manager (Materials), the document would be routed to James
James  is selected by the system because the system will choose the employee assigned to the position in alphabetical order, and since James comes before Smith, James is selected. Therefore, unless the clerk selects a specific person to forward the document to, the document will always be routed to the first person alphabetically assigned to the position

Encumbrance / Budgetory Control In Oracle Purchasing

You can define encumbrance accounting or budgetary control in Financial options window:
Navigation: AP or PO ----> Setup--> Organizations --> Financial Options.

In order to use encumbrance accounting or budgetary control, you must install Payables, Purchasing, and General Ledger modules. You may go to encunbrance region to enable encumbrance accounting and to specify the default encumbrance types which Payables module assigns to your invoices, and Purchasing module assigns to your requisitions and purchase orders.

If you enable encumbrance accounting or budgetary control, Purchasing creates
encumbrances when you reserve funds for a requisition or purchase order. If you use the perpetual accrual method in Purchasing, it reverses the purchase order encumbrances when you inspect, accept, and deliver the units. If you are using the periodic accrual method in Purchasing, Payables reverses the purchase order encumbrances when you create accounting

28 June 2011

Concept Of "Price Variance Accounting" Entry On Matching Invoice to PO in AP


We can understand the Price variance concept by the following examples,
Create and approve PO qty=100 price=$5 for total of $500
Invoice is matched to PO qty =100 price = $1 total of  $100

Conditions To Change The Charge Account In Auto Created PO

The charge account cannot be modified under the following conditions:
- If the DESTINATION is INVENTORY or SHOP FLOOR; OR
- The distribution has been encumbered; OR
- PO is autocreated from an encumbered Requisition; OR
- If expense_accrual_code=RECEIPT and destination_type_code=EXPENSE and either

27 June 2011

Oracle PO: Create Release against Blanket PO

We have 3 basic choices for the requisitions created by this process:
1. Release against a blanket PO
2. Autocreate into POs
3. Release as standard PO (but you must have a quotation to use instead of a blanket -- pricing has to come from one or the other).                                                                                                                               


Oracle PO: Enable Default Expense Accounts Based Upon Category

To enable default expense accounts based upon category rules:

Assign a Default Expense Account to the Employee: 

Note:  This step is no longer required but can be used to default in part of the account string, while using the category rules to change only specific segments.

Oracle PO: Steps to debug the Approval Workflow for Purchase Order or Purchase Requisition


Step 1
Review the action history of the document having a problem. This is done in the Purchasing Summary screens – either Requisitions Requisitions Summary or Purchase Orders Purchase Order Summary. If you attempt to view the action history and you receive the following error: