1. Define Employee - Employee setup for document approval
(N) US Payroll Manager>People>Enter and Maintain
Screen - People
2. Define Jobs
(N) US Payroll Manager>Work Structures>Jobs>Descriptions
Screen - Position
3. Define Position
(N) US Payroll Manager>Work Structures>Position>Descriptions
Screen - Position
4. Choose Set of Books
(N) Purchasing>Setup >Organizations > Set of Books > Choose
This step would be required for a new Operating unit set up and if the same
function is not already done in the Accounts Payable module.
5. Create Position Hierarchies
(N) Purchasing>Setup >Personnel>Position Hierarchy
Screen - Position Hierarchy
Steps:
1. Query for the Position Hierarchy Name
2. Click in the Position Block against the Name Field and query for the top
most position in the Hierarchy. All those positions existing in the
Hierarchy will have the Exists in Hierarchy check box checked.
3. Click in the Subordinates field and keep drilling down to see the listed
subordinates below the appearing subordinate.
6. Assign Employees
(N) US Payroll Manager>People>Enter and Maintain > Assignment
Screen - Assignment
7. Assign Employee to the User
(N) System Administrator>Security>User > Define
Screen - Users
Link the User name with the Person (Employee).
8. Run Fill Employee Hierarchy Report
(N) Reports>Run>Fill Employee Report
Run this report to compile the Position Approval Hierarchy. Any change to the
Hierarchy is ineffective until and unless this report is not run.
9. Tax Codes (N) Payables>Setup>Tax>Codes
Description: In the Tax Codes window, you define the tax names, or tax codes, you use on invoices to record invoice taxes you pay to suppliers and tax authorities. Each tax code has a tax type, a tax rate, and an account to which you charge tax amounts.
These Tax code can be defined at various levels i.e. Financial options, Suppliers, Item etc. and can have a predefined hierarchy choosen for defaults on the transactions.
10. Financial Positions (N) Setup > Organizations > Financial Options
Screen - Financial Options
This step is performed for a new Operating Unit. This is a common set up for
Accounts Payable module & Purchasing Module.
11. Purchasing Options (N) Setup > Organizations > Purchasing Options
Screen - Purchasing Options
12. Receiving Options
(N) Setup > Organizations > Receiving Options
Screen - Receiving Options
13. Approval Groups (N) Purchasing>Setup >Approvals>Approval Group
Screen - Approval Group
14. Approval Assignment (N) Purchasing>Setup >Approvals>Approval Assignment
Screen - Assign/Approval Group
For each position in your organization, you assign specific Approval/Control
groups to individual document types. Employees who are assigned to positions
acquire the authorization limits assigned to the respective positions.
16. Define Buyers
(N) Setup > Personnel > Buyers
Screen - Buyers
Only defined Buyers can enter Purchasing Documents
17. Quality Inspection Codes
(N) Setup > Purchasing > Quality Inspection Codes
Screen - Quality Inspection Codes
Quality Codes are used at the time of Quote Comparison, analysis and approval.
New Quality codes can be defined as and when required.
18. Define Payment Terms (N) Setup > Financials > Payment Terms
Description: Define payment terms that you can assign to an invoice to automatically create scheduled payments when you submit the invoice for Approval.
You can define payment terms to create multiple scheduled payment lines and multiple levels of discounts. You can create unlimited number of payment terms.
19. Define Line Types (N) Setup > Purchasing > Line Types
Screen - Line Types
20. Define Document Types
(N) Setup > Purchasing > Document Types
Screen - Document Types
21. Look Up Codes (N) Setup > Purchasing > Look Up Codes
Screen - Purchasing Options
Oracle Purchasing application uses lookup codes to define the list of Quick Pick
values for Quick Picks throughout the system. You can customize your Oracle
Purchasing application for certain fields by adding your own codes to those
initially provided. These lookup codes are used for reference purpose only. Few
default Reports does have these Lookup Codes as one of the Report Parameters.
Assign the Inactive Date as & when any of the Lookup code is not to be used.
Ensure that the Displayed Value and the Description of the Lookup Code is self-
explanatory.
22. Profile Options
(N) System Administration Responsibility > Profiles > System Profiles
23. Open Periods
(N) Setup > Financials > Accounting > Control Purchasing Periods
Description: Open accounting periods to record purchasing activity. Your Oracle Purchasing application lets you create journal entries only for transactions you enter in an open purchasing period. You also need to open your purchasing periods to create correct ‘receipt accrual’ journal entries in your General Ledger, only if the Accrual Option is Perpetual. Use Control Purchasing Periods form to open or close in your Oracle Purchasing application.
Setup > Accounting Close Cycle >Inventory Accounting Periods
We need to open an accounting period to enter transactions in Oracle Inventory. Accounting Periods are defined in Oracle General Ledger and then opened in Oracle Inventory using the Open Accounting Periods form. Oracle Inventory allows to have multiple periods open at any given time.
24. Define Categories
(N) Setup > Item > Categories > Category Codes
Screen - Find Categories
A category is a logical classification of your items.
25. Define Category Set
(N) Setup > Items > Categories > Category Sets
Screen - Category Sets
A category set is a set or group of categories.
Each functional area viz. Purchasing, Inventory, Costing, Order entry can have a
separate default Category set.
26. Define Items
(N) Items > Item Master
Screen - Items
Monday, May 11, 2009
Purchasing - Setup - Overview
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment