Pre-Payment Receipt Creation Setups and Process Steps

This post is exclusively shared by Mr. Sidhartha Anireddy (Oracle Finance expert).

Setups Overview

The following setups are required for the purpose of being able to create a Prepayment Receipt for a customer from Order Management.

1          Update OM System Parameters

2         Define Customer Bank Account

3         Define New Payment Method (Optional)

4          Define Receivable Activity

5          Define Payment Terms

6          Assign Bank Account to Customer Site

7          Define/Assign Document Sequences

 

Process Steps Overview

Please follow the following steps to:-

-          Create a Prepayment Automatic Receipt from Order Management

o   Enter and Book Order

o   Create & View Prepayment Receipt

o   Ship Order

-          Apply the Receipt to An invoice created from the Order

o   Run Autoinvoice Program

o   Review the Receipt and Accounting Entries

1.     Update OM System Parameters

Navigation > Order Management Super User > Setup > System Parameters > Define

Define the system parameter if it is not defined. Query it, enable ‘Allow Multiple Payments’ and click on OK

Navigation > Order Management Super User > Setup > System Parameters > Values

Enter the name of the Operating Unit name and enable the “Show All” check box. Place your cursor in the field “Parameter” and query for “Allow Multiple Payments”. If the value for this parameter is not set to “Yes” update the value to “Yes”. The setup change once made cannot be updated later. Please refer the below screen shot.

2.     Define Customer Bank Account

Navigation >   Payables Super User > Setup > Payment > Banks

If the Bank is already created, query for the bank and click on the Bank Account button. Click on the new button from the menu options and enter the following fields

(a)    Bank Account Name

(b)   Account Use – Should be “Customer”

(c)    Bank Account Number

(d)   Currency – The default currency will be currency of the set of books assigned to the operating unit from which you are trying to create the bank account.

(e)   Save the record after entering the above information. Please refer the below screen shot.

3.     Define a New Payment Method

A new payment method is required if you wish to use the Credit Card Payment Type when creating the prepayment receipt from Order Management. If any other payment type is to be used from Order Management for creation of Prepayment Receipt a new Payment Method is not required to be created. However if you wish to create a new payment method for any other reason please follow the steps mentioned below.

Navigation >   Receivables Super User > Setup > Receipts > Receipt Classes

I have used an existing Receipt Class and only created a new Payment Method. Query for the payment method “XXX Manual Receipts” and place your cursor in the “Payment Method Name” field and click on new button from the menu options. To create a new payment methods enter the following detail:-

(a)    Payment Method Name

(b)   If you want a different name to be printed then enter a different name in the “Printed Name” field. Please refer the below screen shot.

(c)    Click on Bank Accounts and assign an internal bank account. The effective dates in the bank account default to the current system date. If you are entering back dated transactions when testing please ensure that this date is changed accordingly. Enter all the required information if it does not default from Bank Account Setup. Please refer the below screen shot.

(d)   Save the record, the new payment method is created.

4.     Define Receivable Activity

For creating automatic receipt from Order Management a new Receivable Activity of type prepayment has to be created. Accounting entries will also be generated using the account assigned to this Receivable Activity. You can define as many prepayment receivable activities as you want. Only one prepayment receivable activity can be active at any point in time. The accounting entries that get generated in the process are also provided elsewhere in this document.

Navigation >   Receivables Super User > Setup > Receipts > Receivable Activity

5.     Define Payment Terms

There should be at least one payment term which has the “Prepayment” check box enabled. If a payment term is already available then skip this step else create a new payment term or update an existing payment term. When testing we may have to manually enter the payment term in Order Header. However when we move the solution to Production we can agree on a process of defaulting the Prepaid Payment Term on Order Header

Navigation >   Receivables Super User > Setup > Transactions > Payment Terms

Please refer the screen shot below.                               

6.     Assign Bank Account to Customer Site

Navigation >   Receivables Super User > Customers > Standard

Assign the bank account created in #2 above to the customer site. Enable the Primary check box in the bank accounts window and ensure that the effective date is earlier than the date when you want to process transactions. Please refer to the screen shot below.

7.     Define/Assign Document Sequences

If a new payment method is created then document sequences have to be defined and assigned for the new payment method. In my process steps I have not defined a new sequence; hence I am referring directly to assigning of document sequences. Document sequence is an important step since the receipt number will be same as the document sequence number assigned to Prepayment Receipt.

Navigation > System Administrator > Application > Document > Assign

Enter the following information to complete the assignment of document sequences to the payment method:-

(a)    Application – Enter Receivables

(b)   Category – Enter the name of the new payment method created. If a new payment method is not created then ensure that the payment method that you are using has a document sequence assigned to it.

(c)    Set of Books – Enter the name of the new set of books associated with the operating unit where you would be entering transactions.

(d)   Method – Assign the document sequence to both manual and automatic methods.

(e)   Start Date – The start date entered here should be earlier than the date on which you wish to perform transactions.

(f)     Sequence – Enter the name of the sequence that would be generating numbers for your payment method. Please refer to the below screen shots.

Document Sequence Assignment – Document Tab

Document Sequence Assignment – Assignment Tab

Process Steps

1.     Enter and Book Order

Navigation > Order Management Super User > Orders, Returns > Sales Order

Enter the following information to create and book the order:-

(a)    Customer Name – Enter the name of the customer for whom the bank account was assigned in the setups.

(b)   Navigate to Other tab on Order Header and change the payment term to the new payment defined in #5 above.

(c)    Enter the order lines and book the order.

2.     Create & View Prepayment Receipt

After the order is booked click on Actions button on Order Header. From the list of values choose payment. The payment window will open. Follow the below steps to create a prepayment receipt

(a)    Enter the Payment Type as Cash.

(b)   Enter the Percent as 100 to create a receipt equal to the Order Header Amount.

(c)    Enable the Prepay Check box.

(d)   Scroll towards the right side using the scroll bar and choose the receipt method.

(e)   Click on Process Payments. This will call the Prepayment Receipt Creation API to create the receipt.

(f)     Click on View receipt to view the Prepayment Receipt.

3.     Ship Order

Navigation > Order Management Super User > Release Sales Order > Release Sales Order.

Enter the sales order number which has to be released. After releasing the sales order ship confirm and submit the workflow background process to interface Order to Receivables.

From Receivables responsibility submit the Autoinvoice program for the order. The “Prepayment Matching Program (Prepayments Matching Program)” will automatically get fired. This program applies the prepayment receipt to the invoice that gets created by Autoinvoice program.

Receipt Accounting Entries when the Receipt is created.

Cash A/c                                                               Dr.

Unapplied Receipts A/c                                 Cr.

Unapplied Receipts A/c                                 Dr.

Prepayment A/c                                                Cr.

Accounting Entries when the receipt is applied to an Invoice by the Prepayment Matching Program.

Prepayment A/c                                               Dr.

Unapplied Receipts A/c                                 Cr.

Unapplied Receipts A/c                                 Dr.

Receivables A/c                                                 Dr.

Manual / Online Discount at Order Line level

Based on few leading practices of industries user shall not be able to change list price on order directly. Some or the other justification has to be given. The changes has tobe based on some conditions e.g. Customer / Item / Location etc. Oracle does not allow to change price directly on order line.

 

In many case user want to change the price on Sales Order line directly without going to some other window and then put some entries. In this case we need to do some setup which enables this functionality, which is called as “Manual / Online Discount”

 

Below are the steps needs to be done to enable Manual / Online Discount at Order Line level:

1. Define one Manual Modifier List (uncheck Automatic at header level), although it not mandatory at header level.
2. Select Header type as "Discount List"
3. Define one Manual Modifier line (uncheck Automatic at line level) Required
4. Select checkbox for field ‘Override’ (in Modifier Summary Tab)Required
5. Select appropriate ‘Pricing Phase’ (in Modifier Summary Tab)
6. Select ‘Product Attribute’ and ‘Product Attribute Values’ is you want to restrict this to specific cases only.
7. Populate the field ‘Application Method’ with appropriate value.
8. Populate either of ‘Values’ or ‘Formula’ field.
9. If you have any other condition to restrict use of online discount, then use the other field as well as you can use Qualifier to enable extended conditions / filter.
10. Run ‘Build Attribute Mapping Rules’
11. Now User must be able to change to price column value directly on Sales Order form.
12. If multiple modifiers exist for manual application, then one pop-up opens showing all eligible modifier and user need to select the desired modifier. (No pop-up in case of single manual modifier)

 

What’s new in R12- Inventory Management

R12 Oracle Inventory Management, New Features

==========================================================
• Changed Features in R12 Inventory
----o OPM Inventory conversion.
----o Material traceability: Enhanced material control
----o Dual UOM functionality.
----o Material Status control.
----o Advanced Lot control.
----o Lot indivisibility functionality.
----o Material aging workflow.

• OPM Inventory Convergence
----o Structural changes in Inventory Organization
----o Benefits of OPM Inventory convergence

• Changed features for Inventory Process Convergence
----o Oracle Process Inventory Obsolescence
----o OPM Functionalities are supported by Oracle Inventory
----o New features pertaining to OPM
-------- Dual unit of Measure control
-------- Material status control
-------- Advanced Lot Control
-------- Support for Indivisible lot
-------- Material Aging workflow.

• Oracle Process Inventory Obsolescence: Before

• Oracle Process Inventory Obsolescence: After

• Advantages: Oracle Process Inventory Obsolesces
----o Single Item Master to be maintained.
-------- Process Attributes are added to Item definition
-------- Dual quantity tracking for item.

----o Combined view of Inventory
-------- On-Hand balance in one application
-------- Inventory transacted by one system

----o Integrated Supply Chain
-------- Seamless integration to other products like WMS & MSCA available to Process users.


• Advantages: Oracle Process Inventory Obsolesces
----o Dual Units of Measure control
----o Material Status control
----o Advanced Lot control
----o Lot Indivisibility
----o Material Aging Workflow


• Inventory tracking in Dual Units of Measure
----o Explanation
----o Set up and Process
----o Dependencies and Interactions.
----o Even without constant conversion, quantity can be tracked in two Units of Measures.
----o Transact, reserve, check on-hand and availability in multiple Units of Measure.
----o For Planning and Costing, Primary Units of Measure is used.


• Dual Units of Measure: Set up
----o Define Tracking for Single or Dual UOMs Specify defaulting logic for secondary UOM

• Dual Units of Measure control:
----o Transaction Enter Secondary Quantity at Receipt and all subsequent transactions

• Dual Units of Measure control: On-Hand material
----o View on hand and availability in both UOMs

• Dual Units of Measure control: Dependencies and Interactions
----o Oracle Receiving, Shipping Execution, Order Management, Inventory, WMS and the process manufacturing modules will honor dual UOM
----o If another module in e-Business suit or third party application posts a transaction to inventory via transaction open interface that does not indicate

the secondary quantity, the default conversion is used.


• Enhanced Material control by Material Statuses
----o Introduction
----o Set up and processes
----o Dependencies and Interactions
----o Material Status
-------- List of Allowed and Disallowed transactions
-------- Determination of whether or not the product is nettable, Reservable & ATP-able.

----o Applied to Lot, Serial, Sub inventory & Locator
-------- Assigned at receipt of new lot or serial
-------- Assigned in Sub inventory and Locator forms
-------- Disallowed transactions and planning actions are cumulative
-------- Location status applies to material in location and not Location

----o Update status in material workbench or mobile status update forms
----o Status change history report
----o View On-Hand balances by Material status.


• Set up required to enable Material Status:

• Material Status control setup: Enable Transaction
----o Specify which transaction types can be restricted by status

• Material Status control setup: Define Status code
----o Specify planning attributes for material status Specify allowed and disallowed transactions for this material status

• Material Status control setup: Enable Item
----o Enable status control selectively for Items

• Material Status Control Process- Perform Transaction
----o Status restrictions enforced during transactions
-------- Transactions prohibited by status at any level will not be allowed.
-------- Material will not be allocated for transaction not allowed to complete.


• Material Status Control: Dependencies and Interactions
----o Oracle Receiving, Shipping Execution, Advanced Planning and Scheduling, Inventory and Process manufacturing modules will honor material status.
----o If another module in e-Business suit or third party application posts transaction to inventory via transaction open interface that violated material status restriction, that transaction will be allowed.


• Improved Lot Traceability
----o Additional Lot attributes
-------- Grade, Origination, Retest Date, Expiration Action Code, Expiration Action Date, Maturity Date, Hold Release Date.

----o Sub-Lot tracking
----o Lot-level UOM conversions
----o Indivisibility of Lots


• Additional Lot Attributes:
----o Grade, Origination, Retest Date, Expiration Action Code, Expiration Action Date, Maturity Date, Hold Release Date.
----o Grade attributes allowed for allocating a particular grade of material for specific customer or order.
----o Expiration action code allows for particular action to be taken on material when lot has expired.


• Sub-Lot tracking:
----o Sub-Lot: A lot with parent
----o Sub-Lot numbers & Parent numbers can be generated at receipt.
----o Search for material by Lot or Sub-Lot.
----o Automatically name lots as a concatenation of parent lot and sub-lot name.


• Sub-Lot Track: Set up
----o Enable Sublot Control on Item Master

• Sub-Lot track: process
----o Parent Lot number entered during transaction for sublot controlled Items

• Lot level UOM Conversion:
----o Conversions can be created or modified for specific lots
----o Lot level conversions automatically stored as a part of initial receipt transactions for item.
----o Update conversion for the lot and automatically adjust on-hand balances accordingly.
----o View lot level conversions in lot maintenance form


• Lots Indivisibility:
----o Need for Lot Indivisibility
----o Item attribute to determine Indivisibility
----o System will over or under allocate accordingly so that only full lots are chosen
----o Indivisible lots may be manually split, but other transactions for partial quantities are prevented
-------- Exception for receipt into same locator and miscellaneous issue


• Lot Indivisibility: Set up
----o ‘ Lot Divisible’ flag indicates whether lots of this Item can be divided

• Management of Aging of Material
----o Material aging workflow: allows user to be notified about specific date attributes of lot or serial.
----o Concurrent Request: Designed to take action on any date attributes.
-------- The date attributes usually are Expiration date, retest date, maturity date or other types of dates.

----o Workflow is initiated when the given date attribute is within the given number of days of current date defined in concurrent request.
----o Default workflow sends notification, but can be customized to support any functionality.


• Lot Genealogy Enhancement:
----o The enhancement is incorporated in the lot genealogy form to allow user to:
-------- Highlight a particular item lot on a genealogy tree
-------- Toggle between the tabs like ‘where used’ & ‘source’ using highlighted item lot as a top node in the tree.
-------- Refresh the tree with different top level nodes without being forced to go back to query window
-------- View more level of details in the left side navigator where lot branches are expanded before they are forced to scroll horizontally.


• Summary
----o We have learnt about:
----o OPM inventory conversion
----o Dual UOM functionality
----o Material Status control
----o Advanced Lot control
----o Lot Indivisibility
----o Aging of material
----o Lot Genealogy Enhancement



*NOTE: This article is not completely prepared by me, content is edited and complied after referring various sites

Material Status Control in R12 Oracle Inventory

           Material Status control restricts the movement and usage of portions of on-hand inventory. Using material status control enables you to control whether you can pick or ship an internal order or sales order, or issue material for a work order. You can also specify whether material needs to be quarantined until you inspect it. In addition, you can determine whether products with a particular status can be reserved, included in available to promise calculations, or netted in production planning. You assign material statuses at four levels:

• Sub-inventory
• Locator
• Lot
• Serial Number

           Item status drives the item attributes by allowing you to keep an item from being built in Oracle Work In Process, ordered, procured etc. Material status is a granular control over each inventory transaction that applies to specific material within your warehouse or manufacturing facility

Material Status Control Levels:

           You assign subinventory and locator statuses in the subinventory and locator windows. The location status applies to the material in the location and not the location itself. To assign a material status to a lot or serial, you must first enable the item attributes Lot Status Enabled, and Serial Status enabled on the item in the Item Master. You can also optionally assign a default lot or serial status to an item on the Item Master. When you receive the item, the system automatically assigns the default lot or serial status to the item. The lot or serial status remains the same through all inventory transactions including organization transfers. If necessary, you can change the material status at receipt, use the material workbench, or mobile status update page to modify the material status.

  

            When a material status is assigned to a subinventory or locator, the material is not assigned the material status of the subinventory or locator; rather, it takes on the behavior indicated by the material status at the subinventory or locator level. i.e. Material Status is not directly assigned to Material, it is assigned to subinventory / locator / lot / serial and then Material is assigned to subinventory / locator / lot / serial. This way Material and Material Status are indirectly tagged to each other.

Cumulative Effective Status: 

            A cumulative effective status is the combination of all disallowed transactions. Disallowed transactions and planning actions are cumulative.

           When you transact an item, the system checks all of the material statuses. If the system finds a status that disallows the transaction, whether at the serial, lot, locator, or subinventory level, then the transaction fails.

           For example, if you have a locator whose status disallows WIP Issue and that locator is in a subinventory whose status disallows Sales Order Issue, neither of those transactions will be allowed for material that is in the locator

 
 
1. Enable Status Control for the Transaction Type :

We have to set Profile option INV: Material Status Support = Yes

• If you do not enable status control for a transaction type, then the transaction type is always allowed

2. Define Material Status Code :



3. Attach Material Status Code to Sub-inventory / Locator / Lot / Serial : 
Here we are attaching it to Locator.

As we defined Status code for Usage at Locator and Lot level, this can be used only for Locator or Lot



 
 
 

Item Reservation- (InSide View)

This article will help to understand table structure which supports Item reservations in Oracle E-business suite (R12).

Item Reservation Tables

• MTL_DEMAND : This table stores demand and reservation information used in Available to Promise, Planning, and other manufacturing functions. Four row types are stored in this table:

-                 Summary Demand rows

-                 Dependent Demand rows

-                 Open Demand rows

-                 Reservation rows

-                 The primary key is INVENTORY_ITEM_ID, DEMAND_SOURCE_TYPE, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE (o), DEMAND_SOURCE_DELIVERY (o), COMPONENT_SEQUENCE_ID (o).

• MTL_SALES_ORDERS : This table stores the Oracle Inventory local definition of sales orders and maps sales orders between Oracle Inventory and other Oracle Manufacturing applications. The primary key is SALES_ORDER_ID.

• OE_ORDER_HEADERS_ALL : This table stores header information for orders in Oracle Order Management. The primary key is HEADER_ID.

• OE-ORDER_LINES_ALL : This table stores information for all order lines in Oracle Order Management. The primary key is LINE_ID.

• GL_CODE_COMBINATIONS : This table stores valid Accounting Flexfield segment value combinations for each accounting flexfield structure within your General Ledger application. Available material can be reserved against a valid Accounting Flexfield combination. The primary key is CODE_COMBINATION_ID.

• MTL_GENERIC_DISPOSITIONS : This table stores the user-defined account alias. An account alias provides a method to use accounting numbers and makes it easier to transact account issues and receipts. Available inventory can be reserved against an account alias. The primary key is DISPOSITION_ID, ORGANIZATION_ID.

• MTL_MATERIAL_TRANSACTIONS : This table stores a record of every material transaction or cost update performed in Inventory. An issue transaction to an account number or account alias can relieve a reservation against the account number or alias. The primary key is TRANSACTION_ID.

• MTL_DEMAND_INTERFACE : This table is the interface point between non-Inventory applications and the Oracle Inventory demand module. Records inserted into this table are processed by the Demand Manager concurrent program.

• MTL_SYSTEM_ITEMS_B : This table is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key for an item is the INVENTORY_ITEM_ID and the ORGANIZATION_ID.

Inventory Transaction data flow

Inventory Transaction Tables
This article will help to understand table structure which supports material  transactions in Oracle E-business suite (R12). 

•       MTL_TRANSACTIONS_INTERFACE: This is the interface point between non-Inventory applications and the Inventory transaction module. The Transaction Manager concurrent program polls this table at a user-specified process interval and submits the transaction workers to process them. Processing consists of data derivation, validation, and transfer of records from MTL_TRANSACTIONS_INTERFACE, MTL_TRANSACTION_LOTS_INTERFACE, and MTL_SERIAL_NUMBERS_INTERFACE into their respective TEMP tables, from where they are processed by the transaction processor.

•       MTL_MATERIAL_TRANSACTIONS_TEMP: This table is the gateway for all material transactions. Records are processed from this table into Inventory through the transaction processor. All Inventory transaction forms write directly to this table. Outside applications must write transaction records to MTL_TRANSACTSIONS_INTERFACE TXN Processor makes use of TXN worker to process the transactions from MTL_TRANSACTIONS_INTERFACE to MTL_MATERIAL_TRANSACTIONS_TEMP and from MTL_MATERIAL_TRANSACTIONS_TEMP to MTL_MATERIAL_TRANSACTIONS..

•       MTL_MATERIAL_TRANSACTIONS: This table stores a record of every material transaction or cost update performed in Inventory. Records are inserted into this table either through the transaction processor or by the standard cost program. The primary key is TRANSACTION_ID.

•       MTL_TRANSACTION_ACCOUNTS: This table holds the accounting information for each material transaction in MTL_MATERIAL_TRANSACTIONS. Oracle Inventory uses this information to track the financial impact of your quantity moves.

Multi-Org Access Control - Understanding

Now in Release 12, Multi-Org Access Control (MOAC) enables companies that have implemented a Shared Services operating model to efficiently process business transactions by allowing users to access, process, and report on data for an unlimited number of operating units within a single application’s responsibility.

This increases the productivity of Shared Service Centers as users no longer have to switch application responsibilities when processing transactions for multiple operating units.  Data security and access privileges are still maintained using security profiles that will now support multiple operating units.

---

The question is how it is possible in R12 and not in 11i...

ANSWER is the Virtual Private Database (VPD) enables data access control by user or by customer with the assurance of physical data separation. This feature came in Oracle 10g  databse.

Base data tables exist in the product schema with a naming convention of %_ALL.  The data in this table is striped by ORG_ID (Operating Unit).
To view this info in APPS schema user use to use some VIEWs based on evirnmental variable.

In R12 these kind of VIEWs are phased out and  SYNONYMs came in...

e.g.
In 11i therer was a view OE_ORDER_HEADERS in APPS schema which use to retrive / show information base on below SQL statement.
SUBSTRB(USERENV ('CLIENT_INFO'), 1, 10)

....................................................................................................................................................
Now in R12 synonym in the APPS schema provides the Multi-Org filtering based the Virtual Private Database feature of the Oracle 10G DB Server.

For more technical knowledge please refer www.norcaloaug.com/seminar_archive/2009.../4_01_peters.ppt

---

 

In Release 12, you can create a Security Profile and assign as many operating units as you want to that security profile.

Multi-Org Access Control Setup:

-

Using Oracle HRMS, you can define your security profile using two forms:

• The Security Profile form, which allows you to select operating units from only one Business Group
• The Global Security Profile form, which allows you to select operating units from multiple Business Groups

Also it can be done by creating organization hierarchies to show reporting lines and other hierarchical relationships. If you want to include organizations from a single Business Group, use the Organization Hierarchy window, alternatively, use the Global Organization Hierarchy window to include organizations from any Business Group. Always define hierarchies from the top organization down.

After doing these setups or modification in security profile, run a concurrent request called “Security List Maintenance” from HR which makes those security profiles available and allows you to assign them to a responsibility via a profile option called “MO: Security Profile”

1. The MO Security Profile controls the list of operating units that a responsibility or user can access. If you set the security profile at the responsibility level, then all users using that responsibility will have access to only the operating units available in the security profile.

If you set the security profile at the user level, then the user will have access to only those operating units, irrespective of application responsibility that they log into. User level security profile over rides, security profile assigned at other levels.

2. The MO: Default Operating Unit is optional and allows you to specify a default operating unit that defaults when you open different subledger application pages. Because you can access multiple operating units, you may want to set up a default one instead of forcing users to constantly have to choose one. User Preferences allows you to specify a default operating unit at the user level. Use the MO: Default Operating Unit profile option to set the operating unit context or default operating unit when accessing an applications.

3. The last profile option is for backwards compatibility and to support products that do not use Multiple Organizations. The release 11i setting was for this is preserved during upgrade. The Release 11i MO: Operating Unit profile option is supported in Release 12 as not all customers of Oracle products require multiple organizations.

Multi-Org Access Control Process:

---

CASE:

Within a Business Group “Vision Corporation”  we need to give access to Multiple Operating Unit through one responsibility, base on conditions. MOAC going to help in this.

For one particular responsibility called “DG- Purchasing SuperUser” there is a requirement of having access to multiple Operating Units listed below:

• Vision Construction
• Vision Corporation
• Vision Operations
• Vision Services

Due to many other requirements one hierarchy “DEVendra- Org Hierarchy” exists with the structure as show below.

• Vision Corporation
• Vision Operations
• Vision Services
• Vision Utilities

In this case we can define one security profile “DEVendra- Security Profile”, use existing hierarchy and include one more OU “Vision Construction” also exclude “Vision Utilities”.

As this is the requirement with in Business Group, Organization Hierarchy and Security profile will serve the purpose. Had it been a requirement across Business group, we would have gone for Global Organization Hierarchy and Global Security profile.

NOTE: The case we are going to consider is hypothetical and the numbers of Operating Units are only 3-4, in practical it could be much more. So just imagine if a hierarchy has 50 OUs list and only 2 OUs needs to excluded / included for one of requirement… this consideration will give better understanding of this demo…

Check / Create a Hierarchy:

HRMS Manger (R) > Work Structures > Organizations > Hierarchy

Create a Profile:

HRMS Manger (R) > Security > Profile

Enter a name, and select the Security Type called “Secure organizations by organization hierarchy and/or organization list”. This allows you to assign multiple OUs.

NOTE: Optionally use the next two steps to enter a list of Operating Units instead of a Hierarchy or to add additional Operating Units to the list included in the Hierarchy.

Enter Classification: Operating Unit and Organization Name.

This will give access to “Vision Construction” as well as all OUs in the attached hierarchy excluding “Vision Utilities”. Hence the purpose mentioned in this case will get solved.

Run the Security Maintenance List program

Name : Security Maintenance List

Parameters: Generate list for... All Security Profiles

Create a customized responsibility

System Administrator (R) > Security > Responsibility > Define
.

Assign the security profile

System Administrator (R) > Profile > System

Assign the responsibility to your user

System Administrator (R) > Security > User > Define

Test the MOAC Setup whatever we did here...

Login > DG- Purchasing SuperUser (R) > Purchase Order > Purchase Order

Check LOV in the Operating Unit field to see the list of Operating Units that can be accessed.

Note: If the pictures have bad visibility please CLICK HERE