FAQ For Fusion Procurement Setup (Doc ID 1320802.1)
FAQ For Fusion Procurement Setup (Doc ID 1320802.1)
FAQ For Fusion Procurement Setup (Doc ID 1320802.1)
1
Support Identifier: 15584424 (Qemmah qemmah (Available) (0) Contact Us Help
PowerView is On
Consu...
Give Feedback...
Purpose Yes
No
Questions and Answers
What setups are needed for Purchasing?
Document Details
What setups are needed for Self Service Purchasing?
How are Procurement Business Units defined?
Type:
FAQ
How is SETID concept applied in Procurement? Status:
PUBLISHED
Where is the default Procurement Currency set? Last Major
17Mar2014
Update:
How does data flow from one Business Unit to Another? 17Mar2014
Last Update:
What Setups are migrated from EBS, Peoplesoft and JDE Applications?
Where are Purchasing and Requisitioning Approvals defined? Related Products
References Oracle Fusion Purchasing
Oracle Fusion Purchasing
Cloud Service
APPLIES TO:
Information Centers
Oracle Fusion Purchasing Version 11.1.1.5.1 and later
No Information Center
Oracle Fusion Purchasing Cloud Service Version N/A and later available for this document.
Information in this document applies to any platform.
***Checked for relevance on 17Mar2014***
Document References
This document provides answers to some basic questions about how the setup of Fusion Procurement is done.
Recently Viewed
Again, in addition to the common setups for all Fusion Applications, the following lists the main setups specifically for Fusion Self
Service Purchasing. These are configured in the Configure Requisitioning Business Unit page, shown below, and again is purely
done in the context of each Business Unit.
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=452805251941263&parent=WIDGET_RECENTLY_VIEWED&sourceId=1328173.1&id=13… 1/3
6/25/2015 Document 1320802.1
Key fields here include the Default DeliverTo org, the OneTime Location for noncatalog requests, the default Procurement
Business Unit to use, and some approval tolerance settings for changes.
Business Units are not defined explicitly for Procurement, it’s a generic structure to use across all products and features. What
makes a Business Unit suitable for use in Procurement is the assignment of the related Business Functions to it.
1. Business Units are defined in the HCM Application, done in the context of one Enterprise. Here the Manage Business Units
page allows the creation.
2. The second step is in the Assign Business Unit Functions page shows the 4 procurement functions (payables invoicing,
procurement, requisitioning, receiving). Also shows primary ledger and default legal entity (and Currency) that become
mandatory for certain functions. Note: If the Business Unit being setup is going to be used for receiving/holding inventory,
then it also requires the Materials Management Business Function.
3. Thirdly, the Manage Service Providers page sets who is the client Business Unit that will consume each activity assigned.
This is also a required step when the Business Unit is acting as a client of itself (e.g. One business unit acts as both a
Procurement Business Unit as well as Requisitioning Business Unit).
One can either create inventory organization units or reuse ones that are available within the Client BU of the Requisitioning BU.
The inventory organization is assigned to the BU in its own specific setup page.
Another way of assigning Requisitioning BU and SoldTo BU (beyond the Supplier Site assignments table that allows only 1 sold
to per Requisitioning BU) is via the Transaction Flow setup in SCM. This is in logistics and when setup the relationship between
two BU's it allows the soldto to show when creating a PO for one procurement BU.
Each Business Unit has applicable SetID’s available for their own use. Again, this is done in the HCM Application, in the context of
one Enterprise.
In the Manage Business Units page it allows the assignment of all the applicable SetID’s. These form the defaults, since set
enabled regions on a page allow the selection from other SetID’s should they be available. Procurement supports SetID for only
ShipTo, BillTo and Payment Terms.
Within the Business Unit creation (HCM Core), the Financial Reporting region shows the default Ledger and Legal Entity and here
the default currency is also assigned.
Where the SoldTo business unit differs from the Requisitioning Business Unit, it's possible to create a Transaction Flow to
facilitate additional features. Since the Supplier Site assignments table only allows one SoldTo Business Units per Requisitioning
BU, this provides another way of assigning more SoldTo BU’s. The actual setup is done via the Transaction Flow in SCM, as part
of the Logistics product. Once setup the new relationship between two BU's allows the additional SoldTo BU’s to show when
creating an Purchase Order.
In addition, within this relationship setup the From BU (soldTo) is important since this is used as the Inventory Organization that
is passed to the Transaction Account Builder (TAB) to derive the appropriate accounts.
What Setups are migrated from EBS, Peoplesoft and JDE Applications?
Only transaction data will be migrated from Applications Unlimited products, and setup will be required to be completed from
scratch using Functional Setup Manager to help ensure it is complete and accurate.
All procurement documents are processed using the respective BPEL process. The actual generation of the list of approvers, the
notifications sent, and final approval actions are all controlled by the Human Workflow component known as Approvals
Management (AMX). For more information see Note 1320368.1 and other specific documents related to Procurement Approvals
and AMX.
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=452805251941263&parent=WIDGET_RECENTLY_VIEWED&sourceId=1328173.1&id=13… 2/3
6/25/2015 Document 1320802.1
Didn't find what you are looking for? Ask in Community...
Attachments
reqSetup.jpg (59.43 KB)
Related
Products
Oracle Fusion Applications > Procurement > Procurement > Oracle Fusion Purchasing > Set Up ProcurementDefine Purchasing Configuration
Oracle Cloud > Oracle Software Cloud > Oracle Enterprise Resource Planning Cloud > Oracle Fusion Purchasing Cloud Service > Set Up Procurement > Define Purchasing
Configuration
Keywords
APPROVER; PROCUREMENT; PURCHASING OPTIONS; SET UP PROCUREMENT
Back to Top
Copyright (c) 2015, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=452805251941263&parent=WIDGET_RECENTLY_VIEWED&sourceId=1328173.1&id=13… 3/3