Purchasing Setups - Oracle R12

Download as ods, pdf, or txt
Download as ods, pdf, or txt
You are on page 1of 16

PUR - SETUPS

Oracle R12
Steps Task

Step 1 Set Up System Administrator

Step 2 Define Accounting Key Flexfields

Step 3 Set Up Calendars, Currencies, and Ledgers

Step 4 Define Human Resources Key Flexfields

Step 5 Define Locations

Step 6 Define Organizations and Organization Relationships

Step 7 Convert to a Multi-Org Architecture

Step 8 Define Inventory Key Flexfields

Step 9 Define Units of Measure

Step 10 Define Freight Carriers


Step 11 Define Item Attributes, Codes, and Templates
Step 12 Define Categories

Step 13 Define Catalog Groups

Page 1
PUR - SETUPS

Step 14 Set Up Personnel

Step 15 Set Up Oracle Workflow

Step 16 Decide How to Use the Account Generator

Step 17 Open Inventory and Purchasing Accounting Periods

Step 18 Define Subinventory Locations

Step 19 Define Cross-Reference Types

Step 20 Define Taxes

Step 21 Define Payment Terms

Step 22 Set Up Approval Information

Step 23 Define Lookups and Classes

Step 24 Define Standard Attachments

Step 25 Define Purchasing Options

Step 26 Define Buyers

Step 27 Define Items

Page 2
PUR - SETUPS

Step 28 Define Line Types

Step 29 Start the Purchasing Database Administrator

Step 30 Define Financial Options

Step 31 Define Transaction Reasons

Step 32 Define Receiving Options

Step 33 Set Up Transaction Managers and Resubmission Intervals

Step 34 Define Suppliers

Step 35 Set Up Workflow Options

Step 36 Submit Workflow-related Processes

Step 37 Define Descriptive Flexfields

Step 38 Set Up Automatic Sourcing

Page 3
PUR - SETUPS

Step 39 Perform Additional System Administrator Setup

Step 40 Define Manufacturing System and User Profiles

Page 4
PUR - SETUPS

Oracle R12 – Purchasing Required Setups


Navigation

System Administrator → Security → User → Define

Oracle Purchasing → Setup → Flexfields → Key → Segments

Oracle Purchasing → Setup → Financials → Accounting Calendar


Oracle Purchasing → Setup → Financials → Currency → Currencies
Oracle General Ledger → Setup → Financials → Accounting Setup Manager → Accounting Setups

Oracle Purchasing → Setup → Flexfields → Key → Segments

Oracle Purchasing → Setup → Organizations → Locations

Oracle Purchasing → Setup → Organizations → Organizations

System Administrator → Profile → Systems

Oracle Purchasing → Setup → Flexfields → Key → Segments

Oracle Purchasing → Setup → Units of Measures → Units of Measures

Oracle Inventory → Setup → Freight Carriers


Oracle Inventory → Setup → Items → Templates/Attribute Control/Status Code/ Container Types
Oracle Purchasing → Setup → Items → Categories → Category Sets

Oracle Purchasing → Setup → Items → Catalog Groups

Page 5
PUR - SETUPS

Oracle Human Resource Management

This field will be updated on documenting screen shot explanation

System Administrator responsibility → Application → Flexfield → Key → Accounts


Oracle Purchasing responsibility → Setup → Flexfields → Key → Accounts

Oracle Purchasing → Setup → Financials → Accounting → Open and Close periods

Oracle Inventory → Setup → Organizations → Subinventories

Oracle Purchasing →Items → Cross Reference

India Localization → Setup → Tax Setup → Taxes

Oracle Purchasing → Setup → Financials → Payment Terms

India Localization → Setup → Approvals

Oracle Purchasing → Setup → Purchasings → Lookup Codes

Oracle Purchasing → Setup → Attachments

Oracle Purchasing → Setup → Organizations → Purchasing Options

Oracle Purchasing → Setup → Personnel → Buyers

Oracle Purchasing → Items → Master Items

Page 6
PUR - SETUPS

Oracle Purchasing → Setup → Purchasings → Line Types

To run the Purchasing Database Administration process:

1. Navigate to the Submit Requests window.


2. Select Requests in the first field.
3. Select Purchasing Database Administration in the Name field.
4. Choose Submit Request.
Oracle Purchasing → Setup → Organizations → Financial Options

Oracle Purchasing → Setup → Transaction Reasons

Oracle Purchasing → Setup → Organizations → Receiving Options

System Administrator responsibility → Concurrent → Manager

Oracle Purchasing → Supply Base → Suppliers

Oracle Purchasing → Workflow Users

Oracle Purchasing → Workflow Users

Oracle Purchasing → Setup → Flexfields → Descriptive

Oracle Purchasing → Supply Base → Sourcing Rules

Page 7
PUR - SETUPS

System Administrator responsibility → Application → Menu


System Administrator responsibility → Security → Responsibility → Define
System Administrator responsibility → Security → User → Define
System Administrator responsibility → Install → Printer

System Administrator responsibility → Profile → System

Page 8
PUR - SETUPS

ups
Description
Create a super user to use as a logon name during setup and assign the super user
the required setup responsibilities. Typically, the required responsibilities are as
follows (Required):
* Purchasing
*System Administrator

Define Accounting key flexfields and cross validation rules. You may not need to
perform this step if you have already installed and set up Oracle General Ledger or
performed a common-applications setup.

If you have defined your calendars, currencies, and ledgers while setting up a
different Oracle Applications product, proceed to the next step.

You may not need to set up Human Resources key flexfields if you have already
installed and set up Oracle Human Resource Management Systems or performed a
common-applications setup. Refer to the Oracle HRMS Implementation Guide for
details.

If you're also setting up other Oracle applications, you may already have defined
locations when you set up those applications. You are required to set up at least
one location for now. You can set up the remaining locations after you define
inventory organizations and tax codes.
You may not need to perform this step if you have already installed and set up
Oracle Inventory or performed a common-applications setup.

Although optional, this setup step is recommended even if your business is


composed of just one operating unit. Performing this step now gives you the
flexibility to add operating units later.
This step includes the following tasks:
* Set the profile options MO: Operating Unit and HR: User Type.
* Run the utility to convert to a Multi-Org architecture. It is recommended to
involve your system administrator with this task.

You may not need to set up Inventory key flexfields if you have already installed and
set up Oracle Inventory or performed a common-applications setup.

You may not need to perform this step if you have already installed and set up
Oracle Inventory or performed a common-applications setup.
Define freight carriers if you want to specify on a purchase order the freight carrier
that a supplier should use.
See: Inventory Setups Documents for the detailed contents
If you're also setting up Oracle Inventory, you may already have performed this step
when you set up Inventory.

A catalog group consists of descriptive elements for items to which you assign sets
of values such as type, size, or color. If you're also setting up Oracle Inventory, you
may already have performed this step when you set up Inventory.

Page 9
PUR - SETUPS

You may not need to perform this step if you have already installed and set up
Oracle Human Resource Management Systems or performed a common-
applications setup.

Since Purchasing uses Oracle Workflow technology to perform document


approvals, automatic document creation, and account generation via the Account
Generator, you need to set up Oracle Workflow, if you haven't done so already.

The Account Generator in Oracle Purchasing utilizes Oracle Workflow. You can view
and customize Account Generator processes through the Oracle Workflow Builder.
You can also monitor account generation through the Oracle Workflow Monitor.

An accounting period must be open for you to complete a transaction; that is, the
transaction date you enter must fall within the beginning and ending dates you
define for the period.
You can define your own subinventory locations such as Inspection, Cold Storage,
or Reject-Disposition. You may not need to perform this step if you have already
installed and set up Oracle Inventory.
An example of a cross-reference type is one used to cross-reference an item
number to the part number that the supplier uses. See: Defining Cross-Reference
Types.
Define taxes and assign them recovery rates or rules. You may not need to perform
this step if you have already installed and set up Oracle Payables or performed a
common-applications setup.
If you're also setting up Oracle Payables, you may already have performed this step
when you set up Payables. You can set up payment terms such as 1/10 Net 30,
which
All approvers must be employees and must have a logon user name as described in
Step 14. Note: Even offline approvers must have a user name.

Purchasing uses lookup codes to define lists of values throughout the system. You
can add your own codes to those initially provided for some of the lookup codes.

If you do not want to define standard attachments now, you can do so at any time
later.
Use the Purchasing Options window to define default values and controls for
functions throughout Purchasing. You can often override purchasing options when
you are creating documents.
Employees who will use Purchasing as buyers or managers must all be defined as
buyers.
Although you can define items at any point from this step onward, it is
recommended that you set up at least one item to ensure that your flexfields are
working properly.

Page 10
PUR - SETUPS

Oracle Purchasing provides the line type feature so that you can clearly
differentiate orders for goods from those for services or outside processing. In
addition, the services related line types support a broad range of service categories
including general business services, consulting services, and contingent labor.

Use the Purchasing Database Administration process to initiate concurrent


processes that purge obsolete records in Purchasing interface tables and other
temporary tables. The purging of obsolete data helps reduce memory load and
improve system performance. You need to run this process only once because the
AutoSubmit process resubmits itself daily after you submit it the first time.

This step needs to be performed for each operating unit.

Transaction reason codes allow you to provide predefined explanations for each
receiving transaction. Examples of transaction reason codes you can define include
No Packlist, Shortage, Recall, or Supplier Error. If you're also setting up Oracle
Inventory, you may already have performed this step when you set up Inventory.

You may not need to perform this step if you've already defined receiving options in
Step 6 Define Organizations and Organization Relationships.

This step involves the following tasks:


* Start the following transaction managers. See: Administer Concurrent Managers
Window.
* Receiving transaction manager
* Document approval manager
* Define resubmission intervals for concurrent processes.

You may not need to perform this step if you have already installed and set up
Oracle Payables or performed a common-applications setup.

Purchasing uses Oracle Workflow technology to handle requisition and purchase


order approvals, automatic creation of purchase orders and releases, purchase
order changes (specifically, any additional approvals those changes require), and
receipt confirmation. Workflow runs in the background. It automates these
procurement activities whenever you submit a document for approval, create a
requisition, or change a purchase order.

Start the following Workflow-related processes, if you haven't already done so in


the previous step.
If you do not want to define descriptive flexfields now, you can define them at any
time.
You can set up Purchasing to automatically default source document information
from a purchase agreement or catalog quotation onto a requisition or purchase
order line for a particular item and supplier. Or you can default just a supplier and
optionally a supplier site.

Page 11
PUR - SETUPS

This step involves the following tasks:

* Define custom menus. (Optional)


* Define new responsibilities based on your business and security needs.
* Define user names. Purchasing users must have user names, and the user names
must be linked to an employee name.
* Define printers if you haven't already. (Optional)

Setting User Profile Options.

Page 12
PUR - SETUPS

Optional/Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Optional
Mandatory with Defaults
Mandatory

Optional

Page 13
PUR - SETUPS

Mandatory

Mandatory

Mandatory

Mandatory

Optional

Optional

Optional

Optional

Mandatory

Mandatory with Defaults

Optional

Mandatory

Mandatory

Optional

Page 14
PUR - SETUPS

Mandatory with Defaults

Mandatory

Mandatory

Optional

Mandatory

Mandatory

Mandatory

Mandatory with Defaults

Mandatory

Optional

Optional

Page 15
PUR - SETUPS

Mandatory

Mandatory

Page 16

You might also like