Tuesday, 31 March 2015

How to enable the MOAC parameter “Operating Unit” for a Concurrent Program

  • You can notice that the new field “Operating Unit” which is new field in R12 and by default is in disabled mode:-

  • With the introduction of multi-org access control in release 12, an applications responsibility can access multiple operating units. Some concurrent programs have been enhanced to process multiple operating units simultaneously, while for other requests the operating unit must be specified when you run the program.

  • To support this, concurrent programs are defined with an operating unit mode of 'S' for single operating unit or 'M'(concurrent program will be in this mode by default) for multiple operating units. If the 'Operating Unit Mode' is not set for the concurrent program it will fail.

  • The Operating Unit field/parameter is known as Reporting Context in MOAC(Multi Org Access Control) terminology.

  • For a concurrent program though there may be a need to only run for Single Operating Unit, though the Responsibility has access to Multiple Operating Units.

  1. Login into application with System Administration responsibility (NOT System Administrator)

  1. Navigate: Concurrent -> Programs

  1. Query for short name of the concurrent program

  1. Click on Update pencil icon of your program

  1. Under 'Update Concurrent Program' region, select Request tab

  1. Under 'Request Setting' region, select 'Single' from the drop down of 'Operating Unit Mode' field

  1. Save changes by clicking on 'Apply' button

Note:- Setting the Operating Unit Mode from the front-end can only be achieved using an Self-Service application i.e., System Administration but not System Administrator
  1. Change responsibility to the responsibility where the Concurrent Program can be run, in this example TESTOU is assigned to AR Super User responsibility
  2. Select the Concurrent Program from the SRS Window, now you can see that

Operating Unitfield is enabled and you can see the Operating Units in the LOV

This concludes the explanation about enabling the MOAC parameter Operating Unit for Concurrent Program.


Defaulting Requisition Sourcing details using Sourcing Rules

Sourcing Rules in Oracle R12:

  • You can define sourcing rules that specify how to replenish items in an organization, such as purchased items in plants. Sourcing rules can also specify how to replenish all organizations, as when the entire enterprise gets a subassembly from a particular organization.
    If there is a conflict between a sourcing rule and a bill of distribution, the sourcing rule takes precedence.

  • For instance, if you assign a bill of distribution to AUS that tells it to source a part from NYC, AUS can still define a sourcing rule to source the part from SAC. In this case, the local sourcing rule overrides the bill of distribution.
    Since purchasing only uses the default assignment set specified by the MRP: Default Sourcing Assignment Set profile option. 

  • Verify the value prior to creating a sourcing rule assignment in Purchasing.

1) MRP: Default Sourcing Assignment Set > Supplier Scheduling

2) PO: Automatic Document Sourcing

  • Navigate to Responsibility
    Purchasing, Vision Operations >Supply Base >Sourcing Rules

Replenishment sources can be.
1) Make At – The replenished organization that manufacture the item
2) Buy From – An external supplier
3) Transfer From – An inter-organization Transfer

  • Allocation % will determine the portion of the total order to each source.
    You can enter Shipping Method which will determines the Intransit time and shipping cost which planning will use in its calculations.
    You can Rank supplier Named and bills, giving one priority over another.

Assign Sourcing Rule :

Purchasing, Vision Operations >Supply Base >Assign Sourcing Rules

  • You can assign each sourcing rule to single item or category across all organization or specific organization. 
    Verify Sourcing Rules.
    Purchasing, Vision Operations > Requisitions > Requisitions 

  • Here Source has populated by default in purchase requisitions. Click approve button. You can view requisition summery.

  • This completes the sourcing rule assigning explanation.


UOM and Conversions

Define Units Of Measure:
  • Define units of measure, unit of measure classes, and base units of measure for tracking, moving, storing, and counting items. You can convert between the units of measure you define. This facilitates you to manufacture, order, or receive items in any unit of measure.
1.    Define unit of measure classes.
2.    Define units of measure.
3.    Define unit of measure conversions.
4.    Define lot-specific unit of measure conversions.

Defining Units of Measure Classes
  • Unit of measure classes represent groups of units of measure with similar characteristics. Creating unit of measure classes is the first step in unit of measure management.  Each unit of measure you define must belong to a unit of measure class.
  • You can define one base unit of measure to the units of measure in the class.
  • Navigate to the Inventory Super User responsibility.
    Setup>Unit Of Measure>Classes

Defining Units of Measure:
  • The base unit of measure to achieve conversions between units of measures in the class. The primary unit of measure is the stocking unit of measure for an item in a particular organization. The primary unit of measure is an item attribute that you specify when defining each item.
  • Navigate to the Inventory Super User responsibility.
    Setup>Unit Of Measure>Unit Of Measure

Defining Unit of Measure Conversions:
  • Unit of measure conversions are numerical factors that enable you to perform transactions in units other than the primary unit of the item being transacted. You can define:
    •    a conversion common to any item (Standard)
    •    a conversion for a specific item within a unit of measure class (Intra-class)
    •    a conversion for a specific item between unit of measure classes (Inter-class)
  • As below,
    Unit of measure conversions are not organization-specific.
    You must define a conversion between a non-base unit of measure and the base unit of measure before you can assign the non-base unit of measure to an item.
  • Navigate to the Inventory Super User responsibility.
    Setup>Unit Of Measure>Conversions

Lot-Specific Unit of Measure Conversions:
  • Lot specific conversions enable you to perform a specific inter-class conversion for a given lot. This enables you to establish more granular control over the transactional quantities of a lot. You can create lot-specific unit of measure conversions for on-hand lots or lots with a zero balance. If you create a lot-specific conversion for a lot with on-hand quantities, you can automatically update the quantities in the system to more accurately reflect the on-hand quantity.
    You can also view the history of changes made to the lot unit of measure conversion, and the corresponding quantity changes.

  • This concludes the explanation about unit of measure.


Contract Purchase Agreement Creation Process in R12.2

Definition: Contract Purchase Agreements in Oracle EBS

  • You create contract purchase agreements with your suppliers to agree on specific terms and conditions without indicating the goods and services that you will be purchasing. You can later issue standard purchase orders referencing your contracts, and you can encumber these purchase orders if you use encumbrance accounting.

  • Navigate to Purchasing Responsibility
Purchase Orders > Purchase Orders

  • Here you can include agreement dollar amount, Ship to and Bill to address with supplier details. Select the Global checkbox only if you are creating a Global agreement.

  • Standard purchase orders can only reference the contract during its effective dates. Part of the terms and conditions could include a percentage discount off list prices for all products the supplier sells or different discounts for different groups of products.
  • Click Approve button and then Ok.
  • Once contract purchase agreements is approved you can use it with standard purchase order per agreed amount or less than committed amount.

  • Click on Referenced Document tab.

  • Here you can refer previously created contract purchase agreements.
  • Click on Shipment button.

  • You can enter sub inventory here.
  • Click on Approve button. Once Standard Purchase order is approved you can check contract purchase agreement. Open purchase order in query mode and check released amount. The dollar value displayed in Released field is the total dollar value of all standard purchase order lines referencing the contract.

  • This completes the explanation of Contract Purchase Agreement in Oracle EBS R12.

Wednesday, 25 March 2015

Sale Quote Configuration with Creation and Approval process in R12

Oracle Sales Quote - Approval - Setup

Oracle Sale Quote is the system that offers excellent opportunity for the sales guys to create/follow up and play with the Sales Quotes as per the customer requirement and needs. Once Quote is approved it can be converted into Sales Order (in Order management) with Single click of mouse.          

One of advantage of Sales Quoting is that it enhance user experience , since it is part of OM , it retrieve all the relevant information from the Order management and once created and approved it creates Sales Order without much input from user.       

Oracle Quotes offers limited capability to create Quotes and Progress it through the Negotiation phase and finally creates Sales Order. In case your Organization has complex advance quoting needs we should Implement Oracle Sales Quoting.

Step 1) Line level Transaction type is created for the Quote.

Step 2) A Header level Transaction Type is created with Negotiation Flow As "Negotiation Flow - Generic With Approval"

Step 3) The Line transaction type is added to the Header transaction type by clicking Assign Line Flows.

Step 4) A approval List is created for the Transaction Type, The Approval will be sent to all the persons entered in the list.

Step 5) After we enter all the details we click Validate Workflow which will submit "Validate OM Workflow"

Step 6 ) A Document Sequence is created with type as Automatic and a Initial Value.

Step 7) Document Category is created with appropriate name and Table Name

Step 8) Document Assignment is done for the Category and in assignment Tab Sequence is attached

Sale Quote Creation and Approval Process
Step 1) A quote is created with the Quote Transaction type, and Transaction Phase as "Negotiation" and Status Will be in "Draft".

Step 2) Line Level details will be entered and the Status will be in “Draft” status. 

Step 3) The Quote is progressed to next level by right click option.

Step 4) Next Eligible action is “Submit Draft”. In this step the draft will be submitted for Approval

Step 5) After submiting the Draft the status will be changed to “Pending Internal Approval”.
The Quote Approval will be sent to list of Approvals.

Step 6) The List users defined in the Transaction type will be notified for Approval.

Step 7) The User Approves the Quote.

Another User is also gets the notification of Approval

The User Approves the Sale Quote.

Note -- The Status of the Quote now changes to Pending for Customer Acceptance, after all the approvers approve the Sales Quote.

Step 8) The Last Action in Negotiation Flow is Customer Acceptance.
Actions --> Customer Acceptance is selected

Step 9) Customer Accepted button is clicked

Note -- After customer accepts the Sale quote the transaction Phase changes to Fulfilment and Status changes to “Entered” and quote Document Becomes a sales order, and there after order can be booked and taken forward for shipment