Sunday, July 25, 2010

Interview Questions : Pick Release Concepts


Here we have collected some of the most important Questions with their answers.  We framed the answers based on different  Oracle guides , Blogs and  our personel learnings too.  Hope it will be helpful!! 

What is Release Rules in Oracle apps?

Release Rules define the criteria to be used during Pick Release. Only orders which meet the criteria and are eligible will be Released. An Order line is eligible if it has completed the prerequisite workflow activities, such as Schedule - Line or Create Supply.

What is meant by Release Sequence Rules in Oracle apps?

Release Sequence Rules determines the order in which inventory is allocated to sales orders. Users can choose to allocate by order, outstanding Invoice value, Scheduled Date, Departure Date & Shipment Priority.
The order in which sales orders are filled could be very important. If a company has a problem of running out of material before all of their orders have been filled it is very important that they have filled their most important orders first.

What is meant by Picking Rules?

Picking Rules, which are created and maintained in Inventory, suggests which material to use, based on inventory controls such as Revision control, Lot control, FIFO (first in first out) or subinventory/locator picking numbers.

Picking Rule is an Item Attribute. Create a variety of picking rules and associate them with the appropriate items. If there isn’t a Picking Rule associated with the item, the system will use the Organization’s default Picking Rule which is found on the Shipping Organization’s Parameters.

Note: Picking Rules are covered in Inventory. To learn more see Inventory’s users guide.

What is meant by Pick Slip Grouping Rules?

Pick Slip Grouping Rules organize how released order lines are grouped on Pick Slips for ease of picking. For Example: By using the Pick Slip Grouping Rule "Sub-Inventory" the user can reduce the number of trips to a particular subinventory by grouping all lines for that sub-inventory on to one Pick Slip.

What Happens during Pick Release ?

  • A pre-approved Move Order is automatically created in Inventory.
  • A Move order is a request for a subinventory transfer from the source (stocking) subinventory to the destination (staging) subinventory.
  • A Move order is created for every Sales Order Line that has the status of “Awaiting Shipping” and passes the picking criteria (Use your Release Rules to guide this process).
  • The Destination subinventory is the Staging subinventory entered on the Release Sales Orders form or defaulted from the Shipping Parameters. Only one staging subinventory is allowed per Picking Batch.
  • Note: A Picking Batch is the total number of Order Lines that were released at one time.
  • Inventory uses the move order to manage material requisitions within an Organization.


Other options During Pick Release

 Allocate Inventory to the move order
  • Allocating can be done automatically after the move order is created by setting “Auto Allocate” to yes on the Release Sales Order form or postponed until later, then manually allocated from the Transaction Move Orders form.
  • The Release Sequence Rule, that was entered on the Release Sales Orders form, or defaulted from the Shipping Parameters, will be used to determine in what sequence to fill the move orders.
  • Move orders use inventory’s picking rules to suggest the material that should be allocated. The sourcing values for subinventory, locators, revisions, and lots are defaulted on to the move order.
  • Serial Numbers can be allocated if the profile option: INV: Detail Serials = “Yes”. If it is set to “No” serial numbers can be entered before Pick Confirm from the Move Orders form or after Pick Confirm from the Shipping Transaction form.
  • The source defaults can be manually updated from the Transaction Move Orders form.
  • A high level reservation is placed for the Move Order’s material requirements.
  • Allocating inventory is a prerequisite for printing Pick Slips. The Pick Slip Grouping Rule entered on the Release Sales Orders form or defaulted from the Shipping Parameters is used while printing pick slips.


  Pick Confirm the move order                                

  • Pick Confirm can be done automatically during the picking process by setting “Pick Confirm” to yes on the Release Sales Orders form or by unchecking the Pick Confirm Required checkbox in the Organization Parameters form. If it is not done automatically during pick release it can be done manually from the Transaction Move Orders form by selecting the Transact button.
  • The Pick Confirm transaction executes the subinventory transfer, moving the material from it’s source location to it’s destination staging location. Only 1 staging subinventory is supported per picking batch.
  • The high level reservations are replaced with detail reservations.
  • Note: A high level reservation puts a reservation on a given quantity. For example if the sales order line needs ten 12” Monitors and you have 15 on hand, the reservation will guarantee that 10 of them will be available for this order but it doesn’t specify which 10. Detail reservations puts a reservation on specific subinventory, locator, revision, and lot number.
  • If you transact less than the requested quantity, the Move Order will stay open until the total quantity is transacted, or the order is closed or cancelled.
  • The status of the Sales Order Line, which is linked to the Move Order, is changed to “Picked” making it eligible for Ship Confirm.
  • If not all of the Move order quantity was transacted the status of the Sales Order Line, is changed to “Picked Partial”. During Ship Confirm the order line will split into 2 shipment schedules (e.g. 1.1 and 1.2). The status of the unfilled line will be changed to “Awaiting Shipping”.
  • If there is a shortage of material a shortage messages alerts the appropriate individual.
  • If an organization’s actual picks rarely deviate from the suggested material, it is suggested that you run your picking process with Auto Allocate and Pick Confirmed set to Yes to cut down on the overhead which is required to transact manually. 

  Auto Create Deliveries - Optional 
  • A delivery is required in order to Ship Confirm. You can select to have the Picking process automatically group your delivery lines into deliveries to expedite this process.



Enjoy Learning!    Happy Sharing!!   All the Best for your Interview!!

Sunday, July 25, 2010 by Team search · 4

Sunday, July 18, 2010

Oracle Process Manufacturing API's

Below is the collection of most widely used API's in Oracle Process Manufacturing. We will post the wrapper programs for these api's soon.


OPM Area
API Name
DESCRIPTION
Formula
GMD_FORMULA_PUB
Public Formula Header package that the user defined function calls. The business API can be used for creating, modifying, or deleting a formula header. While creating a Formula header the API also creates Detail and Effectivity associated with this header.
Formula
GMD_FORMULA_DETAIL_PUB
Public Formula Detail package that the wrapper or user defined function calls.
The business API can be used for creating, modifying, or deleting a formula detail.
Formula
GMD_FORMULA_EFFECTIVITY_PUB
Public Formula Effectivity package that the wrapper or user defined function calls. The business API can be used for Creating, Modifying, or deleting a formula effectivity.
Recipe
GMD_RECIPE_HEADER
Public Recipe API that the user
defined function calls.
Recipe
GMD_RECIPE_DETAIL
Public Recipe API that the user
defined function calls.
Recipe
GMD_RECIPE_FETCH_PUB
Public Recipe API that Recipe
Header and Recipe Detail APIs
call.
Recipe
GMD_FETCH_VALIDITY_
RULES
Public Recipe API that Recipe
Header and Recipe Detail APIs
call.
Routings
GMD_ROUTINGS_PUB
Public Routing package that the
user defined function calls. The
business API is used for creating, modifying, or deleting a routing header.
Routing Steps
GMD_ROUTING_STEPS_PUB
Public Routing package that the
user defined function calls. The
business API is used for creating
or modifying routing steps
associated to the routing header
Routing Dependency
GMD_STEP_DEPENDENCY_
PUB
Public Routing package that the
user defined function calls. The
business API is used for creating
or modifying routing step
dependency information
associated to the routing steps.
Operations
GMD_OPERATIONS_PUB
Public Operation package that
the user defined function calls.
The business API is used for
creating, modifying, or deleting
a operation header. When
creating an operation header,
the API also creates activities
and resources associated with
this header.
Operation Activities
GMD_OPERATION_
ACTIVITIES_PUB
Public Operation Activities
package that the wrapper or
user defined function calls. The
business API is used for creating, modifying, or deleting operation activities. When creating an operation activity, the API also creates operation resources associated with this operation activity.
Operation Resources
GMD_OPERATION_
RESOURCES_PUB
Public Operation Resources
package that the wrapper or
user defined function calls. The
business API is used for
creating, modifying, or deleting
operation resources.
Activities
GMD_ACTIVITY_PUB
Public Activity package that the
user defined function calls. The
business API is used for creating, modifying, or deleting activity information.
Status
GMD_STATUS_PUB
Public API that modifies the
status for routings, recipes,operations, and validity ruleS
Resources
GMP_RESOURCES_PUB
Public level package used for creating, updating, and deleting generic resources in OPM.
Resources
GMP_RESOURCE_DTL_PUB
Public level package used for creating,updating, and deleting plant resources in OPM.
Resources
GMP_RSRC_AVL_PKG
Public level package used for resource
availability calculations.
General
GMP_CALENDAR_API
Public level package used for fetching data from the OPM Shop Calendar. These APIs are used by OPM Process Execution

Sunday, July 18, 2010 by Team search · 0

Disclaimer

The ideas, thoughts and concepts expressed here are my own. They, in no way reflect those of my employer or any other organization/client that I am associated. The articles presented doesn't imply to any particular organization or client and are meant only for knowledge Sharing purpose. The articles can't be reproduced or copied without the Owner's knowledge or permission.