, , , ,

Setup – Approval Hierarchies in Oracle Purchasing Position & Supervisor

Purchasing setup of approval hierarchies

There are two most commonly known methods to route documents for approval.
1. Approval Hierarchies (uses position hierarchies)
2. Employee/Supervisor Relationships (use employee/supervisor relationship)
* Third method of Advanced Approval Support for Requisitions (Release 12 use integration with Oracle Approvals Management) . However in this article, focus here is set on above two most commonly used methods.

1. Position Hierarchies

Position Hierarchies are hierarchies that have a position relationship. 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. The hierarchy for positions is defined on the Position Hierarchy form. When this is complete or is changed, the Fill Employee Hierarchy concurrent program must be run for the new hierarchy to come into effect. You must set up Positions if you plan to use either security or approval hierarchies. If you are using Shared HR navigate, Purchasing: Setup: Personnel: Position Hierarchy. Otherwise, if you are using a full install of HR then navigate, Human Resources: Work Structures: Position: Hierarchy.

2. Employee/Supervisor Relationships

This type of hierarchy does not use the Approval Hierarchy form, but is defined by the employee/supervisor relationship. The supervisor of an employee is defined on the Assignment region of the Employee form. If the purchase order entered by the employee exceeds the approval limits, the purchase order is forwarded onto the employees’ supervisor, as defined on the Employee form.

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 is able to be located and the job assigned to the employee does not have Approval Authority, then the Approving employee must enter a Forward-to person, or the Document will be returned to an Incomplete status and a notification will be sent to the Approving employee, stating – ‘No Approver Found – Please Select a Forward-To Employee’.

Selecting an approval routing method

There are two forms that determine the route that an approval will take:
1. Financial Options (Purchasing: Setup: Organizations: Financial Options)
2. Document Types (Purchasing: Setup: Document Types)

1. Financial Options
The Human Resources zone on the Financial Options form has an option called Use Approval Hierarchies. This option determines which type of hierarchy is used for the approval process. When checked, the Position Hierarchy is used and when unchecked the Employee/Supervisor relationship (i.e. Jobs) is used.

2. Document Types

There are three attributes on this form that determine the approval path of the document:
a) Forward Method
b) Default Hierarchy
c) Transaction Type (for Requisitions only)
* Each of these 3 options are described in some details below

a) Forward Method
This field has two options that apply regardless as to whether you use a Position Hierarchy or an Employee/Supervisor relationship.

– Direct: the document will pass to the next position or supervisor in the hierarchy who has enough authority to approve the document.
– Hierarchy: the document will pass to the next person in the hierarchy regardless to whether that position or supervisor has enough approval authority to approve.

b) Default Hierarchy
The Default Hierarchy option will only appear on the Document Type form if the option Use Approval Hierarchies is checked on the Human Resources zone on the Financial Options screen. The Default Hierarchy field has a LOV. This list is derived from the hierarchies created using the Position Hierarchy form.

The Default Hierarchy is the one that will be used by the approval process unless the person who submits the document for approval changes it in the Approval Modal form. But, the hierarchy can only be changed on the Approval Modal form if the attribute Can Change Approval Hierarchy is checked on the Document Type form – and this attribute is only enabled if the Use Approval Hierarchies is checked.
When choosing the action of ‘Approve’ for a document, if a Forward-To person is not defined and the person taking action does not have sufficient approval authority, the default hierarchy will first be searched for the employee attempting the approval. This default hierarchy is defined on the Document Types form:

Purchasing: Setup: Purchasing: Document Types

Thus, it is imperative that the low-end users (those with little approval authority) be present in this default hierarchy so the next Forward-To approver can be found. Alternatively, the checkbox Can Change Approval Hierarchies should be selected on the Document Types form. With this checkbox enabled, the user has the option to specify an alternate approval hierarchy; provided that the user belongs to one or more additional hierarchies (i.e. the Approval Hierarchy list of values in the Document Approval window will only contain the hierarchies that this user belongs to).
If the low-end user is not part of the default hierarchy specified in the Document Types form and chooses to approve the document, the end result will be a notification to the user stating ‘No Approver Found’.
A similar scenario of ‘No Approver Found’ will result if the ‘Owner Can Approve’ checkbox (on the Document Types form) is disabled and the person attempting to approve the document is not in the Default Hierarchy. When the Approve button is clicked, this setting is validated and enforced; it is at this time that the requisition and purchase order approval workflows will look to the default approval hierarchy, searching for the current approver’s position in the hierarchy in order for the next approver in line to be located.

c) Transaction Type
For requisitions only, selects the Approval Transaction Type. If you have implemented Oracle Approvals Management, this selection associates the transaction type with the requisition document type. Leave the field blank to use the standard Oracle Purchasing approval logic

/by
, , , ,

Purchasing Basic setup steps

Step 1 Set Up System Administrator (Required)
Step 2 Set Up Key Flexfields (Required)
Step 3 Set Up Calendars, Currencies, and Set of Books (Required)
Step 4 Set Up Organizations (Required)
Step 5 Set Up Units of Measure (Required)
Step 6 Set Up Items
           Define item attribute controls. (Required with defaults)
           Define container type QuickCodes. (Required with defaults)
           Define status. (Required with defaults)
           Define item type QuickCodes. (Required with defaults)
Step 7 Set Up Personnel (Required)
           Define employee QuickCodes. (Required with defaults)
           Define supplier and employee numbering. For this step,  Defining Financial
           Options. (Required)
           Define employees. (Required)
           Define jobs. (Required)
           Define positions. (Optional)
           Define position hierarchies. (Optional)
Step 8 Set Up Oracle Workflow (Required)
Step 9 Decide How to Use the Account Generator (Required)
Step 10 Define Manufacturing System and User Profiles (Required)
Step 11 Open Inventory and Purchasing Accounting Periods (Required)
Step 12 Define Subinventory Locations (Optional)
Step 13 Set Up Cross-Reference Types
            Tax Names, and Location Associations (Optional)
Step 14 Set Up Approval Information
            Define approval groups.(Required)
            Assign approval groups.(Required)
            Fill employee hierarchy.(Optional)
            Define document types.(Required with defaults)
Step 15 Set Up Lookups and Classes. (Required)
            Define Purchasing lookups.(Required with defaults)
Step 16 Define Standard Attachments (Optional)
Step 17 Set Up Purchasing Flexfields (Required)
Step 18 Define Purchasing Options (Required)
Step 19 Define Buyers (Required)
Step 20 Define Items (Optional)
Step 21 Set Up Document Controls (Required with defaults)
Step 22 Set Up Financial Options (Required)
Step 23 Set Up Receiving Options (Required)
Step 24 Set Up Transaction Managers and Resubmission Intervals. (Required)
             Start the following transaction managers.(Required)
             Receiving transaction manager
             Document approval manager
Step 25 Define Suppliers (Required)
Step 26 Start “Send Notifications for Purchasing Documents” Process (Required)
Step 27 Set Up Document Creation Options (Required with defaults)
Step 28 Set Up Approval Timeout Feature (Optional)
Step 29 Start Workflow Background Process (Optional)
Step 30 Modify Change Order Workflow Options (Optional)
/by
, , , , , , , , , ,

Important Profiles During Implementation

 Important Profiles
1. Receiving transaction Processor concurrent not visible
TP: INV Transaction processing mode                 —         On-line

RCV: Processing Mode                                   —         On-Line  set to User & Resp.

2. Auto creates tools copy document next document form not pop-up.

PO: Display the Autocreated Document               —         No to Yes

PO: Display the Autocreated Quotation                —         No to Yes

PO: Allow Buyer Override in Autocreate Find        —         Yes or No

PO: Allow Category Override in Autocreate Find   —         Yes or No

PO: Allow Referencing CPA Under Amendment    —         Yes or No

PO: Allow Requisition Approval Forward Action     —         Yes or No

HR: Supervisor Hierarchy Usage —Use Assignment-based  Supervisor Hierarchies
                                                     Use Person-based Supervisor Hierarchies

HR: Display Position Hierarchy                           —         Yes or No

PO: Allow Requisition Approval Forward Action     —         Yes or No       

3. Requisition Import required Internal & Purchase Requisition

PO: Legal Requisition Type                                             —         Both

PO: Restrict Requisition line modify to quantity split         —         No

RCV: Allow routing override                                             —         Yes

OM: Display New Order after Copy                                  —         Yes

OM: Item Change Honors Frozen Price                            —         Yes

OM: Return Item Mismatch Action                                   —         Allow

4. Sales Order Number not automatic sequencing

Sequential Numbering                                                    —         Always Used

AR:Maximum lines per AutoInvoice                                  —        20

AR: AutoInvoice Gather Statistics                                    —         No

AR: Use Invoice Accounting For Credit Memos                 —         Yes

eBTax: Allow Override of Customer Exemptions                —         Yes

WIP:Job Name Updatable                                               —         Yes to No

Drop ship

OM: Population Of Buyer Code For Dropship Lines           —         Order Creator     (not mandatory)

Requisition import & Create release both should run at a time

PO: Release During ReqImport                                        —         Yes

Localization Profiles

Responsibility    —          Purchasing

JG: Application                          —         Purchasing

JG: Product                               —         Asia/Pacific Localizations

JG: Territory                              —         India

JG: Company Operating Unit       —         Operating Unit Name

Responsibility    —          Inventory

JG: Application                          —         Inventory

JG: Product                               —         Asia/Pacific Localizations

JG: Territory                              —         India

JG: Company Operating Unit       —         Operating Unit Name

Responsibility    —          Order Management

JG: Application                          —         Order Management

JG: Product                               —         Asia/Pacific Localizations

JG: Territory                              —         India

JG: Company Operating Unit       —         Operating Unit Name

Any changes from SO Header level it won’t affect to line level need to set the profile – R12 Futures:-

OM: Sales Order Form:
Cascade Header Changes to Line               —    Automatic

QP: Item Validation Organization               —    IMO

OM: Item Validation Organization             —    IMO setting up both should Same
                                     (then only Item should be listing in price list and modifier)

FND: Record History Enabled

FND: Diagnostics                     —    Yes (Customer web page view record history

Personalize Self-Service Defn–>

                                            No to Yes (Customer web page view record history)

HZ: Enable Duplicate Prevention at Party Creation —   Disabled

                                                                               Organization only

                                                                               Organization and Person

                                                                                Person only

HZ: Enable DQM Party Search                          —    Yes

ASO : Price List Override                                   —    Yes

PO: Allow Buyer Override in Autocreate Find       —     Yes

Transaction type added Customer PO mandatory —    Check box enabled
                                                                              Organization Type
In a Human Resources responsibility, the navigation is Other Definitions > Application Utilities Lookup.

    Works
    Non-Works
    Dump
    Branch
    Warehouse
    Goodown

1. Define FOB: AR à Purchasing lookup à Query FOB      —         Add the Value
                                                                             
2. Define Freight carrier: Order Management à Setup à Shipping à Freight Carrier, Cost Type à Freight Carrier      —         Add the value

3. Define Freight Terms: Order Management à Setup à Quick Codes à Order Management à Query Freight Terms   —   Add the Value

AR: AutoInvoice Gather Statistics               —         No to Yes

( AutoInvoice Master Program concurrent error)

AR:Maximum lines per AutoInvoice worker    —         10000 (null to 10000)

Credit Memo Profile

AR: Use Invoice Accounting For Credit Memos         —        Null to Yes

AR: Transaction Batch Source                                 —         Null to
                                                                                    
INV: Advanced Pricing for Inter-Org Transfers        —         Null to Yes

INV: Advanced Pricing for Inter-Org Transfers        —         No

Price list security:-
Price list and Modifier need to set to Operating Unit level or Global
QP: Security Control                                                —         OFF / ON

QP: Security Default Maintain Privilege                    —  Global
                                                                                      None
                                                                                      Operating Unit
                                                                                      Responsibility
                                                                                      UserQP: Security Default ViewOnly Privilege                   —   Global
                                                                                      None
                                                                                      Operating Unit
                                                                                      Responsibility
                                                                                      User

CST: Transfer Pricing Option                                     —         No

 Internal Sales Order Price Defaulted from Inventory Item cost à Sales Order à Line items à pricing tab à Calculate Price flag set Freeze price to Calculate price.

OM: E-Mail Required on new Customers  — No to Yes (When create new customer or add Contact)

Parallel Pick Future R12
Set the profile site level to
1. WSH: Number of Pick Release Child Processes’  –  50

Consigned Inventory functionality set this Profiles
INV: Allow Expense to Asset Transfer = Yes.

Check following 2 condition for your environment.
1) OE: Autobackorder is only effective if the profile, OE: Reservation = Yes
2) only affects items in a kit, model, or ship set during Pick Release.

/by
, , , , ,

Oracle 11i/R12 Important Queries in Concurrent , Inventory, Purchaing , HR, Payrol , OPM

To Find Duplicate Item Category Code


SELECT category_set_name, category_concat_segments, COUNT (*)
FROM mtl_category_set_valid_cats_v
WHERE (category_set_id = 1)
GROUP BY category_set_name, category_concat_segments
HAVING COUNT (*) > 1
ORDER BY category_concat_segments

Get Number Of canceled requisition


SELECT a.AUTHORIZATION_STATUS,(a.ORG_ID),(SELECT distinct hr.per_all_people_f.first_name|| ‘ ‘|| hr.per_all_people_f.middle_names|| ‘ ‘|| hr.per_all_people_f.last_name “Employee Name”
FROM hr.per_all_people_f
where hr.per_all_people_f.PERSON_ID in
(select employee_id from fnd_user fu where fu.user_id = a.CREATED_BY)) CREATED_BY,count(SEGMENT1 )
FROM
po_requisition_headers_all a
WHERE
a.creation_date BETWEEN TO_DATE(’01/01/2007′, ‘DD/MM/YYYY’)
and TO_DATE(’30/05/2007′, ‘DD/MM/YYYY’)
and a.AUTHORIZATION_STATUS = ‘CANCELLED’
group by a.AUTHORIZATION_STATUS,a.ORG_ID,a.CREATED_BY

Number of line processed in Order Management


SELECT COUNT (line_id) “Order Line Processed”
FROM oe_order_lines_all
WHERE creation_date BETWEEN TO_DATE (:Fdate, ‘DD/MM/YYYY’)
AND TO_DATE (:tdate, ‘DD/MM/YYYY’)
AND flow_status_code = ‘CLOSED’;

To Check Item Catogry For Inventory master (No Of Segments May Varry)


SELECT ood.organization_name,
segment1|| ‘-‘|| segment2|| ‘-‘|| segment3 catgory
FROM org_organization_definitions ood,
mtl_categories_vl mcv,
mtl_category_sets mcs
WHERE mcs.structure_id = mcv.structure_id
ORDER BY ood.organization_name

Check Locators for inventory Inventory Org Wise(Number of segment may varry)


SELECT mil.segment1 loc_seg1, mil.segment11 loc_seg11, mil.segment2 loc_seg2,
mil.segment3 loc_seg3, mil.segment4 loc_seg4, mil.segment5 loc_seg5,
mil.segment6 loc_seg6,ood.ORGANIZATION_NAME,mil.SUBINVENTORY_CODE
FROM mtl_item_locations mil,org_organization_definitions ood
where mil.ORGANIZATION_ID = ood.ORGANIZATION_ID

Display All Subinventories Setup

select msi.secondary_inventory_name, MSI.SECONDARY_INVENTORY_NAME “Subinventory”, MSI.DESCRIPTION “Description”,
MSI.DISABLE_DATE “Disable Date”, msi.PICKING_ORDER “Picking Order”,
gcc1.concatenated_segments “Material Account”,
gcc2.concatenated_segments “Material Overhead Account”,
gcc3.concatenated_segments “Resource Account”,
gcc4.concatenated_segments “Overhead Account”,
gcc5.concatenated_segments “Outside Processing Account”,
gcc6.concatenated_segments “Expense Account”,
gcc7.concatenated_segments “Encumbrance Account”,
msi.material_overhead_account,
msi.resource_account,
msi.overhead_account,
msi.outside_processing_account,
msi.expense_account,
msi.encumbrance_account
from mtl_secondary_inventories msi,
gl_code_combinations_kfv gcc1,
gl_code_combinations_kfv gcc2,
gl_code_combinations_kfv gcc3,
gl_code_combinations_kfv gcc4,
gl_code_combinations_kfv gcc5,
gl_code_combinations_kfv gcc6,
gl_code_combinations_kfv gcc7
where msi.material_account = gcc1.CODE_COMBINATION_ID(+)
and msi.material_overhead_account = gcc2.CODE_COMBINATION_ID(+)
and msi.resource_account = gcc3.CODE_COMBINATION_ID(+)
and msi.overhead_account = gcc4.CODE_COMBINATION_ID(+)
and msi.outside_processing_account = gcc5.CODE_COMBINATION_ID(+)
and msi.expense_account = gcc6.CODE_COMBINATION_ID(+)
and msi.encumbrance_account = gcc7.CODE_COMBINATION_ID(+)
order by msi.secondary_inventory_name

To Select Unit Of measure exist in ebusiness suite

select uom_code,unit_of_measure
from mtl_units_of_measure

Query to find out Customer Master Information. Customer Name, Account Number, Adress etc.

select p.PARTY_NAME,ca.ACCOUNT_NUMBER,loc.address1,loc.address2,loc.address3,loc.city,loc.postal_code,
loc.country,ca.CUST_ACCOUNT_ID
from apps.ra_customer_trx_all I,
apps.hz_cust_accounts CA,
apps.hz_parties P,
apps.hz_locations Loc,
apps.hz_cust_site_uses_all CSU,
apps.hz_cust_acct_sites_all CAS,
apps.hz_party_sites PS
where I.COMPLETE_FLAG =’Y’
and I.bill_TO_CUSTOMER_ID= CA.CUST_ACCOUNT_ID
and ca.PARTY_ID=p.PARTY_ID
and I.bill_to_site_use_id=csu.site_use_id
and csu.CUST_ACCT_SITE_ID=cas.CUST_ACCT_SITE_ID
and cas.PARTY_SITE_ID=ps.party_site_id
and ps.location_id=loc.LOCATION_ID

Query to Find Responsibilities assigned to particular user.


SELECT b.responsibility_name NAME
FROM apps.fnd_user_resp_groups a,
apps.fnd_responsibility_vl b,
apps.fnd_user u
WHERE a.user_id = u.user_id
AND u.user_id = (select user_id from FND_USER where user_name=:User_name)
AND a.responsibility_id = b.responsibility_id
AND a.responsibility_application_id = b.application_id
AND SYSDATE BETWEEN a.start_date AND NVL (a.end_date, SYSDATE + 1)
AND b.end_date IS NULL
AND u.end_date IS NULL

Query To find the Request Run By Concurrentselect b.user_concurrent_queue_name, c.request_id
from fnd_concurrent_processes a, fnd_concurrent_queues_vl b, fnd_concurrent_requests c
where a.concurrent_queue_id = b.concurrent_queue_id
and a.concurrent_process_id = c.controlling_manager;

Query to find on Hand Quantity

select sum(transaction_quantity) from MTL_ONHAND_QUANTITIES
where inventory_item_id=9
and organization_id=188

Qunatity on order, Expected Deliverselect sum(ordered_quantity),a.SCHEDULE_SHIP_DATE
from oe_order_lines_all a
where inventory_item_id=10
and ship_from_org_id=188
group by a.SCHEDULE_SHIP_DATE

Query to find Item Code, Item Description Oracle Item Master Query(select item, description from mtl_system_items_b
where inventory_item_id=&your_item
and organization_id=&organization_id) item,

Query to Find out On Hand Quantity of specific Item Oracle inventory
(select sum(transaction_quantity) from mtl_onhand_quantity_details
where inventory_item_id=&your_item
and organization_id=&organization_id) onhand,
— Qty Issued by X No clue what you want here
–Qty On Order,Expected deivery date(select sum(ordered_quantity),scheduled_ship_date from oe_order_lines_all
where inventory_item_id=&your_item
and ship_from_org_id=&organization_id
group by scheduled_ship_date) order_info,
–Toatl Received Qty
(select sum(transaction_quantity) from mtl_material_transactions
inventory_item_id=&your_item
and organization_id=&organization_id
and transaction_quantity>0) tot_rec_qty,
–Total received Qty in 9 months
(select sum(transaction_quantity) from mtl_material_transactions
inventory_item_id=&your_item
and organization_id=&organization_id
and transaction_quantity>0
and transaction_date between trunc(sysdate) and trunc(sysdate-270)) tot_rec_qty_9mths,
–Total issued quantity in 9 months(select sum(transaction_quantity) from mtl_material_transactions
inventory_item_id=&your_item
and organization_id=&organization_id
and transaction_quantity<0 and transaction_date between trunc(sysdate) and trunc(sysdate-270)) tot_iss_qty_9mths, –Average monthly consumption
(select sum(transaction_quantity)/30 from mtl_material_transactions
inventory_item_id=&your_item
and organization_id=&organization_id
and transaction_quantity<0) avg_month_consumption; Find detail of specific Applications Running in System System Administrator

SELECT application_id,APPLICATION_NAME
FROM fnd_application_tl
WHERE application_name = ‘Purchasing’
AND rownum = 1;

Find the Request Groups and Concurrent ProgamsSELECT g.request_group_name, c.user_concurrent_program_name,
a.application_name, g.application_id, g.request_group_id,
u.unit_application_id, u.request_unit_id
FROM fnd_request_groups g,
fnd_request_group_units u,
fnd_application_tl a,
fnd_concurrent_programs_tl c
WHERE g.request_group_id = u.request_group_id
AND u.unit_application_id = a.application_id
AND u.request_unit_id = c.concurrent_program_id
–and c.USER_CONCURRENT_PROGRAM_NAME like ‘%Purchase Order%’
ORDER BY C.user_concurrent_program_name, A.application_name, g.request_group_id;

Display all categories that the Item Belongs
SELECTunique micv.CATEGORY_SET_NAME “Category Set”,
micv.CATEGORY_SET_ID “Category Set ID”,
decode( micv.CONTROL_LEVEL,
1, ‘Master’,
2, ‘Org’,
‘Other’) “Control Level”,
micv.CATEGORY_ID “Category ID”,
micv.CATEGORY_CONCAT_SEGS “Category”
FROM
MTL_ITEM_CATEGORIES_V micv

Another Query to Get Onhand Qty With Oranization ID, Item Code,  Quantity
SELECT organization_id,
(SELECT ( msib.segment1|| ‘-‘|| msib.segment2|| ‘-‘|| msib.segment3|| ‘-‘|| msib.segment4)
FROM mtl_system_items_b msib
WHERE msib.inventory_item_id = moq.inventory_item_id
AND msib.organization_id = moq.organization_id) “Item Code”,
(SELECT description
FROM mtl_system_items_b msib
WHERE msib.inventory_item_id =
moq.inventory_item_id
AND msib.organization_id = moq.organization_id)
“item Description”,
SUM (moq.transaction_quantity) onhandqty
FROM mtl_onhand_quantities moq
GROUP BY moq.organization_id, (moq.inventory_item_id)

/by
, , , , , , , , , ,

Inter Company

More and more companies are doing business globally, and taking advantage of the operations and tax benefits that can be achieved by running operations throughout the world. These companies have multiple operating units and organizations around the world. When goods are shipped or received, the financial ownership through these organizations does not necessarily follow the physical movement of goods. Oracle Applications support three main logistics needs of global organizations – Central Distribution, Central Procurement and Drop Ship.
  • Central Procurement (P2P)
  • Central Distribution (IR ISO)
  • Drop Ship
    1.  External (O2C)
     2. Internal (O2C)
A corporation manages its global operations in various countries through a network of subsidiaries, separate legal entities, licensees and several associated label franchisee. This complex network of operations is necessitated to take care of local legal and fiscal environment, which prevail in each of those countries.
Consider the below example:
Vision Operations (V1) is based in USA. It has a 100 % owned subsidiary company called Vision Asia (VA). VA in turn has two subsidiaries – Vision Japan (VJ) and Vision China (VC). VJ has manufacturing facilities in Osaka (O1) and distribution center at Tokyo (T1). Due to tax advantages, V1 sources all the goods from china through VJ. Though the financial transactions between V1 and VC are routed through VJ, logistic movement of goods takes place directly between V1 and VC.
Continuing the above example, Vision Operations (V1) has another subsidiary company called Vision Singapore (VS), 100 % that it owns. Individual plants procure components from their own suppliers. VS centralizes all the commodity (like steel, Aluminum etc.,) procurement needs of Vision Operations across Overview of Intercompany Invoicing 1 world and procures the material on behalf of all VJ and its subsidiary plants and places purchase orders on its suppliers. However, material is directly shipped from the suppliers to all the manufacturing plants.

Fig1
A key requirement for the global implementation of Oracle applications in such a complex business environment is the ability to process “intercompany transactions,” where one business unit (across OUs)invoices another for transfer of goods and services. Often these intercompany transactions involve transactions related to general expenses, funds transfer, salary transfers, asset transfers, royalty payments and product transfers.
For example, the organization structure depicted in figure 1 can be modeled in Oracle applications as depicted in Figure 2.

Following are the key implementation points you need to look into:
  • Understand the corporation business entities and the relationship between them. Identify selling-shipping relationships and procuring-receiving relationships.
  • Understand Oracle multi org structure and the building blocks in data structure.
  • Breakup the business relationships into manageable process flow and map it to various entities in Oracle applications.
/by