Delivery# from SO#

Get Delivery Number from Sales order number


SELECT wda.delivery_id,wdd.*  FROM
ONT.OE_ORDER_HEADERS_ALL ooha,
ONT.OE_ORDER_LINES_ALL oola,
WSH.WSH_DELIVERY_ASSIGNMENTS wda,
WSH.WSH_DELIVERY_DETAILS wdd
WHERE
wdd.SOURCE_HEADER_ID= ooha.HEADER_ID
AND wdd.DELIVERY_DETAIL_ID =  wda.DELIVERY_DETAIL_ID
AND ooha.HEADER_ID=oola.HEADER_ID
AND wdd.SOURCE_LINE_ID=oola.LINE_ID
AND ooha.order_number= && /* Give the Sales Order Number */
AND ooha.org_id = &&; /*Give the Org Id */ 

User Responsibility

User Responsibility Query :


SELECT FU.USER_ID,
  FU.USER_NAME,
  FU.DESCRIPTION,
  FU.START_DATE "USER_START_DATE",
  FURG.START_DATE "RESP_ASSIGN_DATE",
  FRV.START_DATE "RESP_START_DATE",
  FRV.RESPONSIBILITY_ID,
  FRV.RESPONSIBILITY_NAME,
  FA.APPLICATION_ID,
  FA.APPLICATION_NAME FU.LAST_UPDATE_DATE,
  FU.LAST_UPDATED_BY,
  FU.LAST_LOGON_DATE,
FROM apps.FND_USER FU,
  apps.FND_USER_RESP_GROUPS_DIRECT FURG,
  apps.FND_RESPONSIBILITY_VL FRV,
  apps.FND_APPLICATION_VL FA
WHERE FU.USER_ID                       = FURG.USER_ID
AND FURG.RESPONSIBILITY_ID             = FRV.RESPONSIBILITY_ID
AND FURG.RESPONSIBILITY_APPLICATION_ID = FA.APPLICATION_ID
--AND FU.USER_NAME  = '&&'
AND FRV.RESPONSIBILITY_NAME LIKE '%&&%'
AND (FU.END_DATE   IS NULL
OR FU.END_DATE     >=SYSDATE)
AND (FURG.END_DATE IS NULL
OR FURG.END_DATE   >=SYSDATE)
AND (FRV.END_DATE  IS NULL
OR FRV.END_DATE    >=SYSDATE) ;

Query for Concurrent program run details

Query for Concurrent program run details


SELECT DISTINCT R.REQUEST_DATE,
  R.REQUEST_ID REQUEST,
  R.STATUS_CODE,
  R.PHASE_CODE,
  F.USER_NAME USERNAME,
  (R.ACTUAL_COMPLETION_DATE - R.ACTUAL_START_DATE) * 1440 ELAPSED,
  R.ARGUMENT_TEXT PROGRAM_PARAMETERS,
  C.USER_CONCURRENT_PROGRAM_NAME,
  RR.RESPONSIBILITY_NAME,
  R.CONTROLLING_MANAGER
FROM apps.FND_CONCURRENT_REQUESTS R,
  apps. FND_USER F,
  apps.FND_CONCURRENT_PROGRAMS_TL C,
  apps.FND_RESPONSIBILITY_TL RR
WHERE --R.REQUEST_ID = '&&' AND /* Enter request id */
  C.USER_CONCURRENT_PROGRAM_NAME = '&&' AND /* Enter Request Name */
  R.STATUS_CODE IN ('F', 'I') AND
  R.PHASE_CODE = 'P' AND
  C.CONCURRENT_PROGRAM_ID           = R.CONCURRENT_PROGRAM_ID
AND R.REQUESTED_BY                  = F.USER_ID
AND R.RESPONSIBILITY_ID             = RR.RESPONSIBILITY_ID
AND TRUNC(R.REQUEST_DATE)           = TRUNC(SYSDATE)
AND R.RESPONSIBILITY_APPLICATION_ID = RR.APPLICATION_ID
ORDER BY R.REQUEST_ID DESC;

Order To Cash Cycle

Sourcing Process

Sourcing process include the below activities:-
1.Analyze
2.Develop
3.Qualify
4.Negotiate
5.Evaluate
6.Award
7.Monitor Performance 


The steps for Sourcing requirements Flow following Quotations and auctioning process :

1. Buyer creates an RFQ with RFQ Template .
2. Item Attributes ,relative scores ,weights for Bid Analysis , Supply Requirements (Delivery requirements, Packaging), Service Requirements (Part-level sequencing, Serialization), Related Costs (Freight, Tooling, etc.) , Pricing Structure (location based, time phased, etc.) , Technical and Commercial requirements are identified.
3. Suppliers are identified or all suppliers listed are added for the RFQ 
4. Set the starting and ending times and Specify Bidding rules
5. Review the RFQ and submit for approval , once approved it is published.
6. Published RFQ are available for suppliers to be viewed.
7. Supplier send acknowledgement to the buyers for the participation.
8. Suppliers creates quotes sand submits for buyer evaluation
9. Once all quotes are ready for evaluation the RFQ is closed
10. First buyers unlocks the technical requirements , then unseal it and completed the evaluation
11. Commercial requirements are unlocked and unsealed and then completed for evaluation.
12. After evaluation and analyzing By quote and suppliers , buyer awards by quote and line .
13. If target price is met the buyer completes the award , publishes the results and submits for creations of Standard or Blanket purchase order .
14. If Buyer's requirement is not met RFQ is cancelled and starts reverse auctioning which means suppliers would bid for the order.
15. Buyer creates an Auction same as RFQ identifies all requirements commercial, technical , pricing , cost factors etc.
16. Buyer then reviews and submits for approval and once approved pulishes the auction
17. Suppliers will get notified for the auction , once acknowledged , create Bids and submits the Bid.
18. Suppliers have the proxy bid feature where in online bidding monitor  would suggest for decrement of bidding rates according to the decrement criterias
19. Buyer Monitors the Auction and closes the Auction  once target price is met.
20. Collect and evaluate responses to award the contract or agreement, Analyze based on price, non-price and subjective factors and Make award decisions on basis of commodity / supplier strategy
21. Completes award and share decisions and  submits for creations of Standard or Blanket purchase order .

Document Types in Purchasing

Document Types in Purchasing


Blanket Purchase Agreements : Used for purchases that will be delivered according to an unknown schedule, or with negotiated prices. Releases are performed when a shipment is scheduled. Can be limited by Price, Quantity, and Effective Dates.Blank Releases are Issued against Blanket Purchases for an actual scheduled order,and is constrained by Price, Quantity, and Effective Dates.
Contract Purchase Orders : Created when terms and conditions pertaining to goods or services are agreed upon in a contract. Standard purchase orders are issued against the contracts and are constrained to these terms and conditions.In this PO material required 
are not specified.
Planned Purchase Orders : Used when a long-term agreement to buy goods or services from a source is made, and tentative delivery schedules are known. Scheduled Releases Used with Planned Purchase Orders to create the actual orders.
Standard Purchase Orders : Used for one-time purchases when the goods or services along with the estimated costs are known.
Internal Requisitions : Used to create requisitions for internally sourced items from locations and organizations set up in EBS.
Purchase Requisitions : Used to create requisitions for externally sourced items. Requisitions need to be turned into Purchase Orders or Releases prior to purchase.


Requisition Status Changes

Status                        Meaning
Approved                   Requisition has been approved.
In Process                  Requisition has been submitted for approval and is still pending.
Incomplete                 Requisition has not yet been submitted for approval.
Pre-Approved             Approver who has proper authority has forwarded requisition to another person for additional approvals.
Rejected                    Approver rejected the requisition.
Requires Reapproval   Changes were made to an approved requisition, requiring it to be          reapproved.
Reserved                    Budgetary Funds are reserved for the requisition.
Returned                    Approved requisition is returned to requestor by the buyer. Note
                                  that requisitions in this status are still considered in MRP, as they
                                  are approved. Canceling the requisition will remove it from MRP.




Purchasing Status Changes


Action                         Description
Cancel                 PO Cancels the entire PO, allowing no further actions on the order or any associated receipts.
Close         Closes the purchase order so that it will no longer appear on reports.
Close for Invoicing Closes the order of invoicing only.
Close for Receiving Closes the order for receiving only.
Finally Close                 Once an order is Finally Closed, no additional transactions can    happen to the order or any of its associated transactions. This can not be undone via any standard functionality in the applications, and it will lock up any pending or future transactions that are attempted against the order (such as matching it to an invoice or   adjusting an invoice that is matched to it).
Freeze                        Prevents any future modifications to the order but allows receipts and  invoices against it. This is removed by unfreezing the order.
Place on Hold               Placing an order on hold will not only unapprove it, but will also prevent printing, receiving, invoicing, and reapproval until the hold is removed by selecting RELEASE HOLD. At this time, the order will require reapproval.
Open for Invoicing This is only available when the order or line is closed for invoicing; it allows it to be reopened.
Open for Receiving This is only available when the order or line is closed for receiving; it allows it to be reopened. As mentioned earlier, closed lines can still be received, so this is more about reporting than the actual receipt.

Purchasing Procure to Pay Set ups

Basic Procure to Pay Set ups 

1. Define Accounting Key Flexfields and load account numbers(Req) -  General Ledger account numbers are required on several of the setup forms for purchasing as well as on the distributions added when creating a purchase order.
2. Setup Accounting Calendar (Req)-  This associates dates with a specific accounting period. 
3. Set Up of Currencies (Req) -  Any currency used on a purchase order must be enabled, and  conversion types created and  conversion rates entered. 
4. Ledgers (Req)- All transactions are assigned to a specific Ledger for accounting.
5. Locations for Delivery(Req) - Locations are used for several purposes in EBS, including business locations that are associated with Legal Entities, physical locations that are associated with employees, and purchasing locations that represent where a product will be delivered.
6. Organization Classification (Req) - For Purchasing, the Organization setup required is called Operating Unit. The main purpose of an Operating Unit Organization is to associate a purchasing organization to the Ledger; this is a many-to-one relationship, where each Ledger can have multiple organizations associated to it, but each organization can be related to only one Ledger.EBS also requires an inventory organization to be set up when using purchasing
7. Inventory Parameters (Req) :  Enter Oraganization and calender
8. Define Items (Req)
9. Define Unit of Measure, UOM Clases and conversions (Req)
10. Creating Categories for Purchasing (Req) : Two ways to create requisitions and purchase orders in EBS are  with items, or by using a category with a description. They can be assigned to items to group them for reporting or sourcing rules, or used to assign an account number and to derive the accounting information. Categories can also be assigned to approval groups, limiting the documents a person can approve. Buyers can be associated with a specific category, allowing them to AutoCreate purchase orders only for the category they are associated with. Categories are Key Flexfields, or fields required by EBS that allow flexibility in their formatting and qualifiers to be added for additional functionality. The default item category used by Purchasing Functional Area, called the PO Item Category, allows for multiple segments to be created (Purchasing Superuser > Setup > Flexfields > Key > Segments, select the Flexfield title of Item Categories).
11. Set up Suppliers and supplier sites
12. Set up Employee (Req)
13. Setting Up Approvers for Requisitions and Purchase Orders (Req) : The approval rules used -  the purchasing hierarchies or Oracle Approval Management AME), which is only available for requisition approvals.
14. Set up Buyers (Req) : In EBS employees setup as Buyers are allowed to create purchase orders, while any employee with the proper access can create requisitions and approve both documents.
15. Set up Purchasing Options  (Req)  : Document Controls, Document Defaults, Receipt Accounting , document Numbering
16. Set up Receiving Options  (Req) : Receiving Options , Accounting, Cost factors
17. Set up Finanacial Options (Req) : 
18. Set up Line Types : Line types are used on both requisitions and purchase orders, and they determine how the  amount is calculated on the line.

         Basis for Line Types
         Value Basis    Purchase Basis           Calculation
         Amount Services                  Quantity entered becomes line amount. Price  can not be updated and defaults to 1.
          Fixed Price Services Temp Labor  Only Amount can be entered. Quantity and Price are null.
          Quantity Goods                    Quantity entered times Price entered equals line amount.
          Rate Temp Labor             Only Price can be entered; it becomes the line amount.

     19. Set up Requisition Templates (Opt) : Requisition Templates can be defined and used with the Supplier Item Catalog

     20. Set Up Document Types (Req) : Document Types, selected when entering a purchasing document, are used to set up approval options and controls for the document

Order Management Setup Steps

Order Management Setup Steps
The implementation steps for Oracle Order -
1. Define multiple organizations in Oracle Inventory
2. Setup Multi-Org (Multiple Organization) Access Control Oracle Applications Multiple Organizations
3. Define key and descriptive flexfields
4. Define inventory organizations (warehouses), parameters, subinventories, and picking rules in Oracle Inventory
5. Define Profiles
6. Setting OM System Parameters
7. Define invoicing information
8. Define your sales representatives 
9. Define Tax Features
10. Define Quickcodes11. Define header and line processing flows
12. Define Document Sequences for Order Numbering
13. Define Order Import Sources
14. Define the units of measure
15. Define item information 
16. Define the items that you sell
17. Define the configurations that you sell
18. Define price lists Oracle Advanced Pricing
19. Define customer profile classes
20. Define information on your customers
21. Define item cross references current
22. Define your sourcing rules 
23. Define Order Management Transaction Types
24. Set up Cost of Goods Sold Accounting flexfield combination
25. Define Processing Constraints
26. Define Defaulting Rules
27. Define Credit Checking Rules
28. Define Automatic Holds
29. Define Attachments 
30. Define Freight and Special Charge Types
31. Define shipping parameters


Profile Options for Order Management.In the below list not all are mandatory for set up .As per business requirement , one has to set up for the Profile Options values.

Physical Inventory Process

Overview of Physical Inventory

• Fully automated physical inventory 
• Reconcile system–maintained item on–hand balances 
• Actual counts of inventory. 
• Manage supply and demand 
• Maintain high service levels and planning production.

Maintaining Physical Inventory
Steps Involved:

• Define a physical inventory for your whole warehouse or  subdivisions within your warehouse.
• Take a snapshot of system on–hand quantities.
• Generate alphanumeric tags.
• Void unused or lost tags.
• Approve or reject physical inventory adjustments based on approval tolerances.
• Automatically post adjustments to inventory balances and general ledger accounts.
• Purge physical inventory information.

Defining a Physical Inventory

• You can define and maintain an unlimited number of physical inventories which are identified by a unique name you assign 

Taking Snap shot of Inventory Quantities

• Before you can generate tags for a physical inventory, you must take a snapshot of all system on–hand quantities for your items.
• The snapshot saves all current item on–hand quantities and costs.

Generating Physical Inventory Tags

• You can generate default or blank tags for your physical inventory
• Tag numbers may be alphanumeric
• you can increment only the numeric portion.

Physical Inventory Counts

• Use the tags that you generated to record your physical counts.

Void Tags

• Track the status of each physical inventory tag for auditing. 
• Void unused tags in the Physical Inventory Tag Counts window.

Entering and Voiding Physical Inventory Tag Counts

• After recording your physical counts you must enter the quantity for each tag. You can query tags for easy data entry.

Approving Physical Inventory Adjustments

• You can view, reject, or approve physical inventory adjustments pending approval.

Purging Physical Inventory Information

• Oracle Inventory deletes all information associated with the physical definition. 
• However, the purge does not affect any adjustments or adjustment transactions made using the physical definition.Those adjustments are not changed. 
• You can also purge just tags if you made a mistake and want to start over.

O2C Accounting

OPM Batch processing Accounting

PO Accounting

Process Manufacturing Flow

OPM Batch Processing Flow

 

Process Manufacturing Basic set ups

Process manufacturing is a branch of manufacturing associated with production of end materials in association with the recipes and formulas and batch creation modes of operations.

Basic set up of Process manufacturing includes :

1. Organization Set up with process manufacturing enabled checked- Laboratory and plant
2. Set up the security parameters in the product development responsibility
3. Process Execution Parameter set up in Production Scheduler
4. Quality systems parameters set up in process engineers
5. Set up of approval management in ERES Administrator
6. Set up Item with primary and secondary UOM based on the nature of material as raw material or finished good.
7. Set the process Manufacturing parameters enabled : Process Quality , Process Costing, Recipe enabled.
8. Set the formula for the end product with ingredients and output by product and product
9. Set up of Generic and Plant Resources
10. Resources Cost set up for resource.
11. Material Cost set up for FG and raw materials
12. Set up Sampling plan , tests in quality Manager
13. Set up Specifications
14. Set up activities
15. Set up Operations
16. Set up Process Routings for FG with / without resources
17. Create Recipes for intermediate and FG with validity rules

The basic contradictory factors of process and discrete manufacturing are as follows:

Drop Shipment Set ups and Flow

Drop Shipment Set ups and Flow:
A Drop Shipment is a process where items /deliverables are directly sourced and shipped to customers by Suppliers.


Drop Shipment - Setup
1. Item Attribute set ups:  
Purchased : Enabled
Purchasable : Enabled
Transactable : Enabled
Stockable : Optional
Reservable : Optional
Inventory Item : Optional
Customer Ordered : Enabled
Customer Order Enabled : Enabled
Internal Ordered : Disabled
OE Transactable : Enabled
Shippable : Optional
SO Source type  : External.


2.  Set up of Order Management Transaction Types to order and line workflows that support drop shipments.
3. Oracle Workflow Background Engine is running.
4. Define Drop ship locations used to perform drop shipments have the Ship To Site and Receiving Site.
5. Define the Internal Ship To Locations for your drop shipment customers (Oracle Receivables Standard Customer window, Business Purpose Details Tab).
6. Items have an associated List Price defined within your PO Inventory organization (Oracle Payables Financial Options window, Supplier-Purchasing Tab).
7. Items to be sourced in order management should have a price list assigned.


Drop Shipment - Process Steps

1. Create a Quote with the customer and order type as quote , item and in shipping tab source type as External.
2. Submit the Quote > Submit Draft > Quote status changes to ‘Pending Customer Acceptance’
3. Go to Order Returns > Order Organizer find the quote and Click (T) Order Information > (ST) Main > Actions button > Customer Acceptance
4. Enter the acceptance customer details and  Click (B) Customer Accepted.
5. The status of the Quote Changes to ‘Entered’. The Quote has been converted to a Sale Order which is same as Quote number
6. Book and Schedule the Sales Order - Status changes from Booked
7. Click on ‘Progress Order’. Select ‘Purchase Release Eligible’, 
8. Run Requisition Import Process - Purchase Release process - Orders, Returns > Purchase Release
9. Run Requisition Import Process - Orders, Returns > Requisition Import
10. Now the line status will be in Awaiting Receipt
11. Login to the Receiving Organization (Purchasing) who has been setup as an Approver
12. Create a Purchase Order from the Requisition through Auto Create
13. Approve the PO
14. Receive the full quantity
15. Run Auto Invoice
16. Verify Invoice in Sales Order

Item Status Attributes

Item attributes are information about an item, such as order cost, lead time, and revision control.

Item Defining Attributes - An item defining attribute identifies the nature of an item. What designates an item as an “engineering item” is the attribute Engineering Item, but what controls the functionality of the item are the collection of attributes that describe it. You can buy an engineering item if you want to; simply set Engineering Item, Purchased, and Purchasable to Yes. 

The following table presents item defining attributes and Item Status Attributes:

When you set an item defining attribute to Yes, the item is automatically assigned to the default category set of the corresponding functional area. 

For example, if you set Inventory Item to Yes, the item is automatically assigned to the default category set for the inventory functional area.

Item Status attributes

Item Status attributes are item attributes that enable key functionality for each item.

Status attributes enable and disable the functionality of an item over time. 

Each status attribute allows you to enable the item for a particular use. For example, if you set the status attribute Purchasable to Yes, you can put the item on a purchase order. 

The status attributes are related to the item defining attributes. You cannot enable a status attribute if you do not set the corresponding item defining attribute to Yes. 

Interdependencies for Status Attributes

Each status attribute is dependent on the value of at least one other attribute.

For example, you cannot set Stockable to Yes if you set Inventory Item to No. The interdependences for the status attributes are:

Flexfields

Flexfields

• A flexfield is a flexible data field that your organization can customize to your business needs without programming.
• A flexfield is a field made up of sub-fields, or segments.
• There are two types of flexfields: key flexfields and descriptive flexfields.

Key Flexfield

• A key flexfield appears on the form as a normal text field with an appropriate prompt and can customize to enter multi–segment values such as part numbers, account numbers, and so on. 
• The Oracle Applications store these "codes" in key flexfields. 
• Key flexfields are flexible enough to let any organization use the code scheme they want, without programming.
• For example, consider the codes your organization uses to identify general ledger accounts. Oracle Applications represent these codes using a particular key flexfield called the Accounting Flexfield. One organization might choose to customize the
• Accounting Flexfield to include five segments: company, division, department, account, and project. Another organization, however, might structure their general ledger account segments differently, perhaps using twelve segments instead of five. 
• The Accounting Flexfield lets your Oracle General Ledger application accommodate the needs of different organizations by allowing them to customize that key flexfield to their particular business usage.

Descriptive flexfield

• A descriptive flexfield appears on the form as a two-character-wide text field with square brackets [ ] as its prompt to enter additional information for which Oracle product has not provide any field.
• Descriptive flexfields provide customizable "expansion space" on your forms
• Descriptive flexfields have two different types of segments, global and context-sensitive, decided to use in a descriptive flexfield structure.
• A global segment is a segment that always appears in the descriptive flexfield pop-up window, regardless of context (any other information in your form). 
• A context-sensitive segment is a segment that may or may not appear depending upon what other information is present in your form.

Flexfields features : 

• Customize applications to conform to your current business practice for accounting codes, product codes, and other codes.
• Customize applications to capture data that would not otherwise be tracked by your application.
• Have "intelligent fields" that are fields comprised of one or more segments, where each segment has both a value and a meaning.
• Rely upon your application to validate the values and the combination of values that you enter in intelligent fields.
• Have the structure of an intelligent field change depending on data in your form or application data.
• Customize data fields to your meet your business needs without programming.
• Query intelligent fields for very specific information.

Basic Flexfield Concepts:

Segment

• A segment is a single sub-field within a flexfield. You define the appearance and meaning of individual segments when customizing a flexfield. A segment is represented in your database as a single table column.
• For a key flexfield, a segment usually describes a particular characteristic of the entity identified by the flexfield. For example, you can have a key flexfield that stores part numbers. The key flexfield can contain the part number PAD-YEL-NR-8 1/2x14, which represents a yellow, narrow ruled, 8 1/2" x 14" note pad. Each section in the part number, separated by a hyphen, describes a characteristic of the part. The first segment describes the object, a note pad, the second segment describes the color of the object, yellow, and so on.
• Note that we also refer to the fields in a descriptive flexfield pop-up window as segments even though they do not necessarily make up meaningful codes like the segments in key flexfields. However, they do often describe a particular characteristic of the entity identified elsewhere on the form you are using.

Values, Validation and Value Sets

• Your end user enters a segment value into a segment while using an application. Generally, the flexfield validates each segment against a set of valid values (a "value set") that are usually predefined. To "validate a segment" means that the flexfield compares the value a user enters in the segment against the values in the value set for that segment.
• You can set up your flexfield so that it automatically validates segment values your end user enters against a table of valid values. If your end user enters an invalid segment value, a list of valid values appears automatically so that the user can choose a valid value.
• You can think of a value set as a "container" for your values. You choose what types of values can fit into your value set: their length, format, and so on.
• A segment is usually validated, and usually each segment in a given flexfield uses a different value set. You can assign a single value set to more than one segment, and you can even share value sets among different flexfields. For most value sets, when you enter values into a flexfield segment, you can enter only values that already exist in the value set assigned to the segment.

Structure

• A flexfield structure is a specific configuration of segments. If you add or remove segments, or rearrange the order of segments in a flexfield, you get a different structure.
• You can define multiple segment structures for the same flexfield (if that flexfield has been built to support more than one structure). Your flexfield can display different prompts and fields for different end users based on a data condition in your form or application data. Both key and descriptive flexfields may allow more than one structure.
• In some applications, different users may need a different arrangement of the segments in a flexfield (key or descriptive). Or, you might want different segments in a flexfield depending on, for example, the value of another form or database field.
• Your Oracle General Ledger application, for example, provides different Accounting Flexfield (Chart of Accounts) structures for users of different sets of books. The Oracle General Ledger application determines which flexfield structure to use based on the value of the GL Set of Books Name user profile option.

Intelligent Key

• An intelligent key is a code made up of sections, where one or more parts may have meaning. 
• An intelligent key "code" uniquely identifies an object such as an account, an asset, a part, or a job. Intelligent keys are useful in applications because they are usually easier for a user to remember and use than a unique number. 
• For example, a part number of PAD-YEL-11x14 is much easier to remember than a unique part number of 57494. However, unique ID numbers are easier to maintain in a relational database application because only one column is required for the ID number.

Combination

• A combination is a particular complete code, or combination of segment values that  makes up the code, that uniquely identifies an object. 
• For example, each part number would be a single combination, such as PAD-YEL-11x14 or 01-COM-876-7BG-LTN
• (where the dash "-" is the segment separator). If you had ten parts you would define ten  combinations. 
• A valid combination is simply an existing or new combination that can currently be used (that is, it is not out of date, is not disabled, and does not violate  cross-validation or security rules).

Qualifiers

Flexfield Qualifier

• A flexfield qualifier identifies a particular segment of a key flexfield.
• A segment qualifier identifies a particular type of value in a single segment of a key  flexfield. In the Oracle Applications, only the Accounting Flexfield uses segment
• qualifiers. You can think of a segment qualifier as an "identification tag" for a value. In the Accounting Flexfield, segment qualifiers can identify the account type for a natural
• account segment value, and determine whether detail posting or budgeting are allowed for a particular value.

The basic steps in defining a key Flexfields are as given below.

• Identifying Key flexfields that are required for you in apps installation
• Designing a Key flexfield structure
• Selecting the appropriate Key flexfield to define
• Defining structure information for the Key flexfield
• Defining segment attributes
• Defining flexfield qualifiers
• Defining segment qualifiers
• Implementing optional features as needed

STEPS

The steps for you to implement flexfield security are noted below. 

1. You enable security on the Value Set form (FNDFFMVS) by navigating

   through the following steps:

   a. You sign-on to the Oracle Applications and choose the System Administrator responsibility.

   b. You navigate to the Value Set form as follows:

      Application --> Validation --> Set

   c. You query the desired value set and click the "Find" button.

   d. You check the "Security Available" box.  In the 11.5 version, an  LOV of Security Type will appear.  Choose Hierarchical Security or  Non-Hierarchical Security. NOTE:  If you use a different responsibility, like General Ledger Superuser it will have a different navigation path.

2. You enable security on the Flexfield Segments forms (FNDFFMIS or 

   FNDFFMDC) by navigating through the following steps:

     a. You sign-on to the Oracle Applications and choose the System

      Administrator responsibility.

    b. You navigate to the Value Set form as follows:

      DESCRIPTIVE FLEXFIELD

      ---------------------

      Application --> Flexfield --> Key

      KEY FLEXFIELD

      -------------

      Application --> Flexfield --> Descriptive

   c. You query the desired value set and click the "Find" button.

   d. You must unfreeze the Flexfield description if it is frozen  before proceeding.

   e. You click the "Segments" button.

   f.  Click Open

   g. You check the "Security Enabled" box.

   h. You compile the flexfield.

   i. You freeze the Flexfield description.

3. You enable Concurrent Program Parameters Security from the Concurrent

   Program Definition form (FNDCPMCP) by navigating through the following

   steps:

   a. You sign-on to the Oracle Applications and choose the SystemAdministrator responsibility.

   b. You navigate to the Program Parameter Value Set form as follows:

      Concurrent --> Program --> Define

   c. You query the desired Program and click the "Find" button.

   d. You click the Parameters button and check the "Enable Security" box.

   

4. How security rules interact?

   It is important for you to understand how the rules interact before   defining them.  For example, more than one security rule can be defined   for a segment and each security rule may consists of one or more "RULE   ELEMENTS" (e.g., sometimes referred to as CLAUSES).  A "RULE ELEMENT",   or clause, specifies a RANGE of values within the same value set to   include or exclude based on security access.  

   a. Single Rule, or One Rule with OVERLAPPING RANGES behaves: 

       All values included in either range are included by the rule because it performs as a union.  

         EXAMPLE:  100 - 500, 400 - 800 (two clauses)

         RESULT :  100 union 800  

   b. Single Rule with NO OVERLAPPING RANGES behaves:

       All values that satisfy ANY of the include clause are returned.

        EXAMPLE:  100 - 500,  600 - 800 (two clauses)

        RESULT :  100 - 500 union 600 - 800  

   c. Multiple Separate Rules with OVERLAPPING RANGES behaves:

       It is an INTERSECTION.  

        

       ONLY the values included in the overlap between both rules

       are available. 

         EXAMPLE:  100 - 500 (rule 1)  

                   400 - 800 (rule 2) 

         RESULT :  400 intersection 500

   d. Multiple Separate Rules with NO OVERLAPPING RANGES behaves:

        No values are included to satisfy all the rules. 

          EXAMPLE:  100 - 500 (rule 1)  

                   600 - 800 (rule 2) 

          RESULT :  empty set 

               

5. You define the security rules from the Define Value Set form (FNDFFSRN)

   by navigating through the following steps:

  a. You sign-on to the Oracle Applications and choose the System Administrator responsibility.

  b. You navigate to the Value Set form as follows:

      Security --> Responsibility --> Value Set --> Definition

   c. You query the desired value set by the value set name or any       flexfield segment or concurrent program parameter that uses the value set.  If security is not enabled as qualified in Step #1  above, then nothing will appear.

   d. You should specify include and exclude rule elements for values     in the Security Rule Elements block within the form (FNFFSRN).  All values you enter must pass all security rules for it to appear in  any List of Values (LOVs).  

6. You assign your security rule to a responsibility in the Assignment

   form (FNDFFSRA) by navigating through the following steps:

 a. You sign-on to the Oracle Applications and choose the System Administrator responsibility.

  b. You navigate to the Value Set form as follows:

      Security --> Responsibility --> Value Set --> Assign

  c. You query the desired value set and click the "Find" button.

  d. You assign value security for value sets, flexfield segments, or concurrent programs in this form.  You can apply security      rules to more than one responsibility, and a single responsibility can have more than one security rule.   (Ref Note Id : ID 73743.1)