About Process Execution in Process

Manufacturing Family Pack L

Last revised: June 20, 2007 9:15 am

See Change Record

This document provides a complete, up-to-date description of product enhancements made to

Process Execution in Process Manufacturing Family Pack L. You should read and understand all
tasks described here before you begin your installation. The most current version of this
document can be found on MetaLink; see note 264929.1. Please ensure that you have the most
current version before you begin.

For family pack installation instructions, see How to Use this Document.

Attention:

Process Manufacturing Family Pack L can be applied only to an existing

Oracle Applications Release 11i environment. If you do not already have a
running Release 11i system, then you must first install the e-Business Suite.
Refer to the Release 11.5.8 Rapid Install, as documented in Installing Oracle
Applications, Release 11i (11.5.9) or Upgrading Oracle Applications, Release
11i (11.5.9), and Oracle Applications Release Notes, Release 11i (11.5.9).

How to Use this Document

This document describes the features that are new for Process Execution in Process
Manufacturing Family Pack L, and contains information about:

New and Changed Features

New and Changed Modules
Implementation and User Documentation
Known Issues for Process Execution in Process Manufacturing Family Pack L
New and Changed Setup Steps
Software Updates for Process Execution by Business Activity
Change Record
If your current Process Execution version is earlier than Process Manufacturing Family Pack K or
Maintenance Pack 11.5.9, then refer to the Process Execution 11i+ Features Matrix on MetaLink
to see a complete list of the new features you will get when you advance from your current
version to Process Manufacturing Family Pack L.

After you learn which features are new for your installation, you can find related documentation
for those features by referring to the most recent version of your Process Execution user guide or
online help, as described in the Implementation and User Documentation section.

If you are applying Process Manufacturing Family Pack L...

For family pack installation instructions, refer to the Release 11i About Oracle Process
Manufacturing Family Pack L document, located on the Oracle e-Business Suite Release 11i Info
Center on MetaLink. The installation instructions for applying Process Manufacturing Family Pack
L are appropriate for starting from any previous version of Process Execution Release 11i.

If you are applying the maintenance pack that includes this family pack as well as
other family packs...

DO NOT follow the family pack installation instructions in the Release 11i About Oracle Process
Manufacturing Family Pack L document. Instead, refer to the maintenance pack installation
instructions in the related Oracle Applications Release 11i Maintenance Pack readme, located on
the Oracle e-Business Suite Release 11i Info Center on MetaLink.

New and Changed Features

In Process Manufacturing Family Pack L, Process Execution has added or changed the following
features since its last release. If you are advancing from a release of Process Execution that is
earlier than Process Manufacturing Family Pack K or Maintenance Pack 11.5.9, then refer to the
Process Execution 11i+ Features Matrix, located on the Oracle e-Business Suite Release 11i Info
Center on MetaLink. Use the matrix to learn what additional new or changed features were
released in the versions that you are skipping.

New Features

Using the Shop Calendar to Schedule Batches and Firm Planned Orders

Oracle Process Manufacturing (OPM) Process Execution releases prior to 11.5.10L did not make
any distinction between downtime and uptime. There was no direct linkage between a shop
calendar and a plant. Shop calendars were associated to plants on planning schedules used by
OPM Material Requirements Planning (MRP) and Oracle Advanced Planning and Scheduling
(APS), but these associations were not necessarily unique across schedules. With this release, if
you attempt to create or reschedule a batch or batch step, and the plant is associated to a shop
calendar, then the create or rescheduling operation considers the shop calendar if you select Use
Shop Calendar on the batch header. The shop calendar is used to calculate batch duration, and it
warns you if you try to schedule a batch to start during nonworking time. This feature is also
available on the Production Scheduler.

You can convert a firm planned order to a batch using the shop calendar. By selecting Use Shop
Calendar, the firm planned order-to-batch conversion is done according to the shop calendar
associated to the plant. If there is no shop calendar associated to the plant, then the conversion is
scheduled contiguously.

Rescheduling the Batch and Batch Steps

The Use Shop Calendar option is used to reschedule batches and batch steps.

Date Changes for Batches and Firm Planned Orders (FPOs) with No Routing or Production Rules

If you enter dates for a batch or FPO that do not have a routing or a production rule, then it is
assumed that the dates entered are accurate and the duration of the batch reflects any downtime
that occurs during production. The application does not consider the shop calendar to adjust
batch duration under these circumstances. However, dates entered are validated against the
shop calendar to warn you of scheduling the start or completion during nonworking time.
However, once the dates are accepted, the batch is created in a single, contiguous block of time.

Understanding Warning Conditions

Warnings are issued for the reasons specified:

If you attempt to schedule a batch that starts during nonworking time

If you enter a planned completion date during nonworking time
If the Contiguous indicator is set to Yes, and the batch spans nonworking hours

Shop Calendar Impact on Enforcing Step Dependencies

If Enforce Step Dependency is selected, then you can change either the Planned Start Date or
the Planned Completion Date, but you cannot change both dates. When you change one of these
dates, then the other date field is disabled. This restriction is enforced because the application
must recalculate all dates based on a single date change. Business rules must maintain
synchrony with the underlying data already entered.

If Enforce Step Dependency is not selected, then you are asked:

Do you want the application to recalculate the other date based on current resource
usage?

If you click No, then date gaps can occur.

Date gaps occur when the span of the batch dates becomes larger than the calculated duration
for the batch. The batch start date and batch completion date are adjusted to meet the actual
dates you enter on the Reschedule dialog box.
If there is no routing, then you can enter one or both dates, and no truncation errors are reported.

Using the GME: Use Shop Calendar Default Profile Option

The GME: Use Shop Calendar profile option sets the default value for use of the shop calendar in
a plant. The profile default is No. Set the default to Yes so that the Use Shop Calendar indicator
is selected by default when you create or reschedule batches.

Using the Workbench to Reschedule Without a Defined Shop Day

If a shop calendar exists, but there is no shop day defined for the dates that a batch is scheduled,
then the workbench option issues a warning:

No shop day has been defined on the shop calendar for a day during this batch.
Reschedule batch anyway (Y/N)?

If you click Y (Yes), then the application continues the rescheduling process. If you click N (No),
then you return to the Reschedule window. This does not occur if you reschedule a firm planned
order.

Using the GME: Validate Planned Dates Profile Option

For each batch, the planned start date and planned completion date are validated against the
validity rule dates used for the batch. Neither date can be outside the date range defined on the
validity rule. This is enforced during batch creation and batch rescheduling. Certain business
scenarios require extension of the planned completion date beyond the date entered on the
validity rule without losing the planned start date validation.

This capability is also extended to validation of planned start date and planned completion date
for firm planned orders.

The GME: Validate Planned Dates profile option controls how batch dates and firm planned order
dates are validated against the validity rule used.

Set to Validate Both Planned Dates, the planned completion and planned start dates are
validated against the validity rule date range when creating or rescheduling a batch or
firm planned order.
Set to Validate Planned Start Date Only, only the planned start dates are validated
against the validity rule date range when creating or rescheduling a batch or firm planned
order.

Using GME: Allow Material Deletion Profile Option

The GME: Allow Material Deletion profile option is only used for a batch that does not have
automatic step calculations (ASQC). For batches with ASQC, you can only delete materials when
the batch has a status of Pending.

Set to Pending, you can only delete materials from a batch with a status of Pending.

Set to Pending and WIP you can delete materials from a batch with a status of Pending or WIP. If
your facility uses e-records or e-signatures, then it is recommended that you do not set this profile
to Pending and WIP, because material deletions are not captured on the e-record.
Adjusting the Timescale Unit Width on the Production Scheduler Workbench

Adjust the timescale unit width on the Production Scheduler Workbench by moving the Adjust
Unit Width slider to the left to decrease the interval step size of the timescale, or move the slider
to the right to increase the interval step size of the timescale.

The timescale consists of intervals in units ranging from 15 minutes to one month in selectable
scale intervals ranging from 15 minutes to months. Adjust the minor scale interval as follows:

1. Right-click the minor scale interval on the workbench.

2. Select one of the following to resize the minor time scale interval:
15 minutes
30 minutes
Hours
Days
Weeks
Months

The unit interval adjusts to the scale unit selected.

Using the GME: Display Nonworking Days in Scheduler Profile Option

You have the option to display nonworking days in a different color the Production Scheduler. The
GME: Display Nonworking Days in Scheduler profile option lets you choose whether or not to
display nonworking time in a different color. The default is No. There is a performance impact if
you choose to identify nonworking days by selecting Yes.

The application still considers the shop calendar (if one was selected) if you decide not to select
nonworking time. You continue to have access to the Shop Calendar window from either the
timeline or from the Batch Reschedule window.

Batch E-Records Include Unrelease, Revert to WIP, and Reopen Information

The Unrelease Batch e-record displays the same information content as is displayed in the
Release Batch e-record. Actual quantities and actual start date do not display. However, the
planned quantities display. If you deleted any existing allocations when you unreleased the batch,
then these deleted allocations are also displayed on the e-record.

The Revert to WIP Batch e-record displays the same information content as is displayed in the
Release Batch e-record.

The Reopen Batch e-record displays the same information content as is displayed in the
Complete Batch e-record.

Clarification of Batch Creation Calculations When Automatic Step Quantity

Calculation Is Not Selected

When a batch is created, the total output of the batch is divided by the routing quantity to
compute a scale factor. The individual routing steps are then multiplied by this scale factor to
calculate the batch step quantities. Based on these step quantities, the resource usages are
computed according to the scale type assigned to each resource (proportional, fixed, or by
charge). From these resource usages, the duration of the resources, activities, steps, and batch
are computed.

Clarification of Batch Step Date Calculations

When a pending transaction is created for an automatic-by-step, manual or incremental

consumption ingredient, and the ingredient is associated to a step, then the transaction date is
derived from the planned start date of the step. This also applies to a pending allocation that is
entered through autoallocation, using the Pick Lots window, or manually. Rescheduling a step
updates transaction dates of automatic-by-step, manual and incremental release type items
associated to that step. The transaction date of default lot transaction for these items reflects the
step dates.

When you click the Completed indicator to complete a transaction for a manual consumption
ingredient, the transaction date defaults to the system date. Similarly, when a transaction for an
incremental consumption ingredient is completed either through incremental backflushing, or by
selecting Completed, then the transaction date also defaults to the system date. You can enter a
date for incremental backflushing. These rules apply to manual and incrementally yielded
products. The pending transaction dates default to the planned completion date of their
associated step.

Terminating a Batch

If the results of quality results are not in-specification, and the batch cannot be adjusted to meet
the specification, then you can use the Terminate Batch option to end or terminate the batch. The
Terminate Batch option cancels all remaining batch steps. It is found on the Actions menu of the
Batches window. When you terminate a batch, the application:

Selects the Terminated indicator on batch header.

Completes all the WIP steps and sets indicators on these steps to Terminated.
Cancels steps that are Pending. A Step Status of canceled is assigned.
Deletes all pending inventory and resource transactions.
Retains actual quantities and actual usages as they were at termination. This action does
not change actual values.
Permits entry of the actual completion date (termination date) as when completing a
batch. The default is the system date.
Completes the batch. You can search for completed batches that were terminated.

When a batch is terminated, the sample creation workflow notifications that were open are
canceled. Manage any samples that were physically taken against the batch.

Terminating Batch Steps

The only way to terminate batch steps is to terminate the batch. Pending steps that are canceled
have no actual values. Phantom batches that are associated to pending steps are canceled. WIP
steps are completed, and are marked with the terminated indicator. Completed steps remain as
they were at batch termination. A batch with a Terminated status is closed in the same way as a
Completed batch. A batch history record is created on terminating the batch. When a batch step
is terminated, the sample creation workflow notifications that are open for this step are canceled.
Manage any samples that were physically taken against the batch step.

Displaying Samples Summaries for a Batch

You can choose Samples from the Actions menu. The Samples Summary window displays with
sample details associated with the material. Refer to the Oracle Process Manufacturing Quality
Management User's Guide for information about how to use this window.

Access the Product Development Simulator and Optimizer Tool

Refer to the Oracle Process Manufacturing Product Development User's Guide for a complete
discussion of the Simulator and Optimizer functionality.

The OPM Product Development Simulator and Optimizer windows:

Optimize the quantities for batch material lines

Update a batch with the result of optimized quantities
Rebalance a batch

Batches are loaded onto the OPM Product Development Simulator. You can work with lot
quantities and the parameters associated to a lot.

Changed Features

Impact of Using the Shop Calendar on Other Applications

Applications such as APS that query pending resource transactions in OPM Process Execution
can be affected by use of the shop calendar, because resource transactions can be created in
multiple segments instead of a single segment.

Displaying Plan Quantities for All Batch Statuses

In previous releases, the Material Details window displayed the Original Quantity and Plan
Quantity fields when a batch was Pending, and the WIP Plan Quantity and Actual Quantity fields
when a batch was released. To facilitate comparisons of the planned quantity with actual quantity,
the Plan Quantity field displays for all batch statuses.

Recipe Information Added to Process Execution Workbench Summary Windows

The Process Execution Workbench summary windows display recipe information with the
previously displayed formula and routing information. The recipe, its version, and its description
are added to the Summary by Plant, Summary by Status, and Summary by Product windows, and
to the Summary of Document windows. This information is also added to the Document
Properties window.

Line Allocation Transaction Date Reflects the Batch Step Completion

The logic on pending transactions was modified so that when a pending transaction is created for
an incremental or manual consumption item, the date assigned is the planned start date of the
step to which the item is associated, instead of the planned start date of the batch. Automatic-by-
step items functioned this way previously, but the other consumption types did not. This affects
batch creation, autoallocation, line allocations, and it changes the OPM Advanced Planning and
Scheduling application business rules for planned and rescheduled batches.

Changes to WIP Warehouse in FPO Reflected in FPO-to-Batch Conversion

When you change the WIP warehouse on a firm planned order and convert it to a batch, then the
batch is created with the newly assigned WIP warehouse. The conversion of a firm planned order
to a batch uses the WIP warehouse entered on the firm planned order.

Impact of Not Entering a Rounding Variance

Rounding Variance displays the percent variance allowable for rounding when the Scale Type is
Integer. If the Rounding Variance field is left blank, then rounding occurs without regard to
variance. You do not have to enter any value for ingredients that have a scale type of integer. If
the rounding variance is not entered, then the quantity is appropriately rounded up or down to the
integer value depending on the rounding direction without respect to the variance.

New and Changed Modules

This section lists the modules that were added, changed, or made obsolete for Process Execution
in Process Manufacturing Family Pack L. These modules may include the following: forms,
windows, reports, C programs, SQL*Loader programs, workflows, alerts, or APIs.

New Forms and Windows

You can now reserve batch production to a sales order. When a product is yielded, it is
automatically allocated to the sales order. Refer to Using Oracle Order Management with Process
Inventory for additional information.

The following windows are introduced for the Oracle Order Management integration with Oracle
Process Manufacturing Process Execution:

Production Reservation Rules (GMLCONRL.fmb)

Refer to "Setting Up Production Reservation Rules" in the Using Oracle Order Management with
Process Inventory for details on setting up production reservation rules.

Find Reservations (GMLOMRES.fmb)

Refer to the "Finding Reservations" topic in the Using Oracle Order Management with Process
Inventory for details on querying reservations.
Batch Sales Order Reservation Information (GMLORES.fmb)

Refer to the "Viewing or Updating Production Information" topic in the Using Oracle Order
Management with Process Inventory for details on viewing or updating production information.

Allocation Details (GMLOMRES.fmb)

Refer to the "View Allocation Details" topic in the Using Oracle Order Management with Process
Inventory for details on allocations.

Changed Forms and Windows

Workbench (GMEWKBCH.fmb, GMEPOCSM.fmb, GMEPMSM.fmb)

Workbench windows that display the Terminated indicator are:

Batch Summary By Plant or Product

Summary of Document
Summary of Batch Steps
Summary of Step

"Terminated" text displays in the navigator nodes next to batch status when a batch is terminated.

Query Find functionality from the Workbench has the Terminated indicator.

Batches (GMEBCHED.fmb)

The Terminated indicator and Use Shop Calendar appear on this window.

Batch Material Details (GMEMATED.fmb)

Terminated Ind is hidden in the folder on the batch header portion of this window, and can be
enabled.

Batch Steps (GMESTPED.fmb)

Terminated Ind appears on both the header portion and batch steps portion of the window.
Terminated Ind is hidden in a folder on the batch header portion of the window, and can be
enabled.

Convert Firm Planned Order to Batch (GMEBCHED.fmb)

Use Shop Calendar appears on this window.

Incremental Backflush (GMEPCTED.fmb)

The Terminated indicator appears on this window.

The following windows add the Terminated indicator field on the query find window:

Find Batches (GMEBCHED.fmb)

Find Batch Material Details (GMEMATED.fmb)
Find Batch Steps (GMESTPED.fmb)
Workbench (GMEWKBCH.fmb)

Scheduler Workbench (GMEPWBSC.fmb)

You can reschedule a batch or firm planned order, and reschedule batch steps using the shop
calendar option.

Obsolete Forms and Windows

There are no forms or windows that were made obsolete for Process Execution with Process
Manufacturing Family Pack L.

New Reports
There are no new reports for the OPM Process Execution application.

Changed Reports
There are no changed reports for the OPM Process Execution application.

Obsolete Reports
There are no obsolete reports for the OPM Process Execution application.
New Workflows
There are no new workflows for the OPM Process Execution application.

New APIs
There are no new APIs for the OPM Process Execution application.

Implementation and User Documentation

The corresponding consolidated documentation HTML patch for Process Manufacturing Family
Pack L is patch 2657249. We strongly recommend the installation of this patch. This patch
contains important implementation information for new features, end user documentation for new
features, and updates to documentation for previously released features.

An Adobe Acrobat version of the documentation is available on MetaLink: Process Execution

User Guide, March 2003, note 209936.1.

This documentation HTML patch and pdf are cumulative; they include updated documentation
for all Process Execution 11i+ changes.

Known Issues for Process Execution in Process

Manufacturing Family Pack L
Process Execution in Process Manufacturing Family Pack L contains the following known
implementation issues:

Shop Calendar Implementation

Following issues relate to implementation of the shop calendar:

Rescheduling the Batch and Batch Steps

Prior to this enhancement, when a batch or batch step was rescheduled, the application
rescheduled dates by applying the date change uniformly to all dates on the batch and batch
steps. This practice ensured that any manual changes made to batch dates and step dates were
maintained because only the change interval was applied. Dates were not recalculated based on
available working time.

With the shop calendar enhancement, planned start and completion dates for the batch and its
step are recalculated. Nonworking time is taken into account if you use the shop calendar,
however date calculations are based on the duration of the batch and batch steps.

Actions that Do Not Make Use of the Shop Calendar

The following actions do not make use of the shop calendar functionality:

Rerouting a batch
Creating a batch step
Inserting a step in a batch
Scaling a batch
Editing a step and step details
Changing step dependencies
Deleting a step or step details

Limitations for Staggered Activities

Following is an example of staggered activities that are affected by shop calendar scheduling of
nonworking time:

Act1 is the startup activity

Act2 is the actual process
Act3 is the cleanup

In order to model this to be a startup, process, and cleanup, stagger these activities with offsets
so that they follow each other.

Act1 has an offset of zero and usage of one hour

Act2 has an offset of one hour and usage of two hours
Act3 has offset of three hours and usage of one hour

Assume that:

Act1 starts at noon and lasts until 1 p.m.

Act2 starts at 1 p.m. and lasts until 3 p.m.
Act3 starts at 3 p.m. and lasts until 4 p.m.

If a shop calendar is applied that has working hours for a shop day defined from noon until 2 p.m.
and from 3 p.m. until 5 p.m., then the times are:

Act1 starts at noon and lasts until 1 p.m.

Act2 starts at 1 p.m. and lasts until 4 p.m., and consists of two transactions:
Transaction1: 1 p.m. to 2 p.m.
Transaction 2: 3 p.m. 4 p.m.
 Act3 starts at 3 p.m. and lasts until 4 p.m. Note that this is not properly sequenced,
because you do not begin cleanup until Act2 is complete.

The activities are modeled to be offset from the beginning of the step and not from each other.
There is currently no way to accommodate dependencies between these activities.

Refer to the R11i e-Business Applications Patch Strategy to see if you should apply any
additional Process Execution patches on top of Process Manufacturing Family Pack L.
The most current version of this document can be found on MetaLink; see note 123456.1.

New and Changed Setup Steps

This section lists the setup steps that were added or changed for Process Execution since the
base release of 11i (11.5.1). Complete these steps in the order listed below only for features that
are new to your installation. Refer to the Process Execution 11i+ Features Matrix to see which
features are new for your installation.

If you already completed the setup for a feature after installing a previous version of Process
Execution, then you do not need to repeat those steps. Additionally, if you do not plan to use an
optional new feature, then you can ignore that setup.

Software Updates in this Mini-pack by Business

Activity
11i.GME.L includes 84 patches. To assist you with your patch application testing, these patches
are listed below by business activity. Note that some patches may be listed under more than one
business activity.

Note:

You may need to re-enter your OracleMetaLink user name and password to
access patch number information.

API
The API business activity includes the patches listed in the following table:

Patc
h
Compo Subcomp Num
nent onent ber Description Resolution
API 3620 (Duplicate of bug 3612970) Code was modified in
Issues 264 The update batch step update_batchstep_rsrc API to
resource API generated manage character data properly to
syntax errors. resolve the syntax issue.
API Process 3552 (Port bug 3543428 to Code was modified to correct the
Issues Execution 262 11.5.10L) A record processed typographic error in assignment of
APIs by the Insert Material API error status to correct the issue.
(GME_API_PUB.insert_materi
al_line) returned a status error
of S even though the insert
was not successful due to the
record being locked by
another user. The exception
raised as update_row_error
assigned the error status to
the variable x_return_staus
instead of
x_insert_return_status.
Therefore, the correct status
was never returned to the
calling procedure.
API Productio 3777 POOR PERFORMANCE IN
Issues n 331 GME_API_PUB.INSERT_LIN
Managem E_ALLOCATION API AFTER
ent APIs INSTAL 3689809
API Productio 3479 If you used the Code was modified in the
Issues n 669 start_cmplt_actual_rsrc_txn gme_resource_engine_pvt.consolida
Operation API to record the batch start te_batch_resources procedure so
Control time in that the initial check
APIs GME_RESOURCE_TXNS, l_resource_row.completed_ind = 0 is
and ran a subledger update, removed irrespective of the current
then the posted_ind was set value of the completed_ind. The row
to 1 (indicating the subledger is fetched from the database and
was posted). If you proceeded checked for completed_ind.
to run the Transactions created are now
end_cmplt_actual_rsrc_txn, initialized with a posted_ind of 0. If
the API mistakenly allowed the completed resource transaction
the upadate of a posted is deleted, then the new transaction
record by entering an end is created with posted_ind of 0.
date on the record in
GME_RESOURCE_TXNS
and an actual
resource_usage.

BATCHES
The BATCHES business activity includes the patches listed in the following table:

Patch
Component Subcomponent Number Description Resolution
Batch 3464841 (Port Bug The GME: Calculate Interim
Issues 3347280 to Resource Usage profile option is
11.5.10L) Actual introduced. Set to No, the actual
resource usage resource usage is not updated
was not properly whenever the actual step
represented for quantity is updated. Set to Yes,
WIP. Lengthy the actual resource usage is
steps did not updated based on the progress
reflect actual made through a lengthy step.
usage when This allows the planning and
actual step scheduling applications to
quantities were identify that there is less
updated. remaining resource time required
than that posted at the start of
the step.
Batch 3500386 (Port Bug The batch header descriptive
Issues 3345062 to flexfield opens in the Greek
11.5.10L) The language and all other supported
batch header languages.
descriptive
flexfield did not
open in the Greek
language.
Batch 3507304 (Port Bug Code was modified by addition of
Issues 3482271 to an "OR" condition for completed
11.5.10L) You batches so that you can allocate
could not allocate quantities through the Pick
a batch line with a Lots/Locations window without
Manual displaying an error message for
Consumption type any release type.
in a completed
batch using the
Pick
Lots/Locations
window. The
application
displayed the
error, "APP-GME-
82629 - Pending
Allocation not
allowed in the
current batch
status."
Batch 3530087 (Port bug Code was modified so that when
Issues 3488739 to GMI: Bypass Sublot Warning is
11.5.10L) Even set to 1, no error message
with GMI: Bypass displays when you tab out of the
Sublot Warning Sublot field without entering a
set to 1, the error value.
 Patch
Component Subcomponent Number Description Resolution
message "APP-
GMA-80432:
Entry is required"
displayed when
you tabbed out of
the Sublot field
without entering a
value.
Batch 3545726 (Port Bug To record actual resource usage
Issues 3516077 to for a step associated to a
11.5.10L) In many product, use the incremental
instances, the backflushing functionality without
calculation of ASQC selected, and the GME:
resource usage Backflush Resource Usage
was not accurate profile option set to Yes.
when based Performing an incremental
solely on backflush on a product that is
ingredient associated to a step records the
consumption. resource usage proportionally
Performing an when this profile option is set to
incremental Yes.
backflush on a
product that was
associated to a
step did not
record the
resource usage
correctly.
Batch 3554030 (Port bug Code was modified to add an "if"
Issues 3511883 to condition in remove_folder_field
11.5.10L) FRM- function of
41077: "Error GME_BATCH_HEADER_API
deleting Group package. The application now
Rows" displayed checks for the existance of a row
under these before calling
conditions: set DELETE_GROUP_ROW.
default folder to
Production
Operator, set
Consumption
Type for
Ingredient as a
hidden field,
navigate to the
Material Details
window, query a
batch, and place
cursor focus on
the Products tab.
Batch 3581403 Use of the Pick Code was modified to consume
Issues Lots window did the secondary quantity derived
 Patch
Component Subcomponent Number Description Resolution
not properly by the stock cursor instead of
default the running the UOM conversion
secondary when the full primary quantity
quantity after was consumed.
batch creation.
This resulted in
an unnecessarily
running of the
UOM conversion
when the full
primary quantity
was consumed.
Batch 3614820 When you A new system profile, GME:
Issues completed a Warn If Plan Qty Is Greater Than
batch, you were Allocated Qty, was created to
unable to rectify this issue. Set to Yes, the
determine the application considers the default
validity of the lot when determining whether
warning that incomplete or pending
pending transactions exist for manual and
transactions exist incremental items, and a warning
for manual and displays. Set to No, the
incremental items. application does not consider the
If a quantity default lot when determining
greater than zero whether incomplete or pending
existed in the transactions exist for manual and
default incremental items, and no
transaction, and warning displays.
the detail line was
incremental or
manual, then
completing the
batch advised you
to rectify the
situation. If you
clicked OK, then
the situation was
ignored for
manual and
incremental items.
Batch 3648627 You were not able Code was modified so that you
Issues to query all can view or query all batches
batches and and FPOs in the Production
FPOs in the Schedule Inquiry whether or not
Production you select any document
Schedule Inquiry. number. Relevant data is
The error "APP- displayed regardless of deleting
GMA-80300 the document ordering.
Document
Number
Assignment
record not set up"
 Patch
Component Subcomponent Number Description Resolution
displayed.
Batch 3818266 FP:11.5.10+ -
Issues 11.5.10L
:PERFORMANCE
PROBLEMS
WHEN THERE
ARE MANY
BATCH
RESOURCE
Batch 3834514 FP:11.5.7I - In GMEUNISM form, when the
Issues 11.5.10L adjustment of the allocated
:SCALING DOWN quantities happens,By calling the
A BATCH DOES function,update_completed_trans
NOT REVERSE for the existing completed
THE transactions in ic_tran_pend with
TRANSACTIONS. completed indicator as 1, the
problem is corrected.
Batch Batch Creation 3469968 During the batch The Scale_batch API quantities
Issues scaling process, are converted to the validity rule
the quantities of UOM before comparisons are
the primary made to determine whether the
products were scaled quantities are outside the
verified using the validity rule limits.
minimum and
maximum
quantities of the
selected validity
rule. This
checking
procedure did not
convert these
quantities to the
validity rule UOM
which resulted in
the error 'Scaled
quantity <x> is
outside the
validity rule limits
of minimum <y>
and maximum
<z>.
Batch Batch Creation 3500392 (Port Bug To resolve the issue, an
Issues 3452221 to appropriate error message
11.5.10L) When displays to inform you that the
the Document organization uses automatic
Ordering document ordering, and that you
Assignment Type must enter a valid value in the
was Automatic, Last Assigned field for the
and the Last document before creating a
Assigned field batch.
value was NULL,
 Patch
Component Subcomponent Number Description Resolution
creation of a
production batch
gave a blank error
message.
Batch Batch Creation 3533505 If you queried a Code for the cntrl_reschedule
Issues batch on the procedure was modified so that
Batches window, reassignment of fields is
modified the performed instead of a requery.
batch status, and This resolves the accessibility
then tried to issue.
navigate to the
next or previous
record, then all
other batches
were not
accessible except
the one you
modified.
Batch Batch Creation 3591066 If you navigated Batches or Batch Material Details
Issues from the Batches windows that are open as the
window to the result of a call from another
Batch Material window are refreshed properly,
Details window, and display the newly retrieved
kept the Batch data after queries.
Material Details
window open,
placed cursor
focus on the
Batches window,
and attempted to
query another
batch, then
windows were not
refreshed
properly, and did
not display the
newly retrieved
data.
Batch Batch Creation 3700014 If you entered the Code was added to the date
Issues plan start date check for batches with
and plan production rules, but no routing.
completion date The plan start date and plan
for a batch with completion date entered are
production rules, used. If no dates are entered,
but no routing, then you are not asked whether
then the you want to calculate dates.
application
ignored the these
dates if you
responded "No" to
the question
 Patch
Component Subcomponent Number Description Resolution
"Calculate
dates?"
Batch Batch Material 3476239 Unreleasing a The issue is fixed by use of the
Issues Transactions batch led to GMI: Allow Negative Inventory
negative profile option to warn you when
inventory for a editing or reversing product or
product that byproduct yield. Set to 0, if the
moved to another change to the product or
warehouse or byproduct yield quantity drives
location. inventory negative, then an error
message displays and you
cannot save your work. Set to 1,
you can save without warning or
error. Set to 2, if the change to
the product or byproduct yield
quantity drives inventory
negative, then a warning displays
and you are asked if you want to
proceed. You can save your
work or cancel the transaction.
Batch Batch Material 3630485 It was possible to Code was modified so that you
Issues Transactions partially allocate can no longer partially allocate
an indivisible lot an indivisible lot by entering a
using the value less than its total quantity
secondary in the secondary quantity field.
quantity field.
Batch Batch Material 3633271 There was a Code was modified to the correct
Issues Transactions defective recall of the defective recall of the primary
the primary UOM UOM and detail line UOM in the
and detail line Pick Lots query. When a
UOM in the Pick transaction is completed, the
Lots query. Both onhand inventory is properly
parameters were reduced in both the primary and
entered in the secondary UOM. In those cases
same UOM where inventory is legitimately
without a driven negative, an appropriate
conversion. The error message displays on both
message that you Pick Lots window and on the
drove inventory Line Allocation window. Display
negative occurred of the message is in accord with
when the the setting for GMI: Allow
allocated quantity Negative Inventory.
was greater than
the available
quantity,
irrespective of the
setting for the
GMI: Allow
Negative
Inventory profile
option.
 Patch
Component Subcomponent Number Description Resolution
Batch Batch Material 3643292 When you Code was modified by the
Issues Transactions queried a lot addition of
number from the app_query.query_foreign_key
Line Allocations code in pre_query for lot_no and
window of a batch sublot_no so that the appropriate
item, you had to release type is available for the
search for it in the query.
list. If you
attempted to find
a particular lot
number using the
Lot No parameter
and Query by
Example, then all
the line
allocations were
returned, and not
just the specific
lot number
entered.
Batch Batch Material 3720215 Locations with Code was modified in
Issues Transactions field lengths GMEVALLS.pls to accommodate
greater than 10 greater than 10 characters.
characters do not Locations with field lengths
display in the Pick greater than 10 characters
Lots window display properly in the Pick Lots
because the window.
location tab was
defined as
varchar2(10).
Batch Material Details 3519756 When you Code was modified so that after
Issues selected a inserting a material in a batch,
material line on you can create line allocations
the Batch Material without the requirement to save
Details window, your work each time.
attempted to
insert a new item,
and drilled down
to line allocations
for the next
ingredient, the
application
displayed the
error "FRM-
40654: Record
has been
updated. Requery
block to see
change." You
needed to save
your work for
each line
 Patch
Component Subcomponent Number Description Resolution
allocation to
proceed without
errors.
Batch Material Details 3575387 If the plan Code was added to disable the
Issues quantity was zero, Required Qty and Scrap Factor
or was not fields initially if the plan quantity
entered, then the in a pending batch, or the WIP
scrap factor and plan quanity in work-in-process
required quantity batch is not entered or is zero.
fields were These fields are enabled once
disabled. quantities are entered. Code was
also added to calculate the scrap
factor from the required quantity
only if plan or WIP quantities
have a value other than zero.
Batch Material Details 3590875 If you deleted a Correct action codes are sent to
Issues completed a temporary table. Transaction
allocation in a consolidation does not create
WIP batch, incorrect reversals. When a
clicked OK, did completed transaction is updated
not save your and deleted, the application now
work, deleted a fetches the current transaction in
material line in ic_tran_pnd and uses it to
Material Details reverse the transaction.
window, and
saved the batch,
then the
allocations were
not properly
reversed. Instead
of adding back an
ingredient to
reverse the
transaction
properly, an
additional
negative
transaction was
created.
Batch Material Details 3648996 It was not Code was modified to add
Issues possible to add CUSTOM.pll functionality to the
extra validations Line Allocations window to
on the transaction enable extra validations. WHEN-
date of an VALIDATE-RECORD fires
allocation line properly.
using the
CUSTOM.pll code
on the Line
Allocations
window. WHEN-
VALIDATE-
 Patch
Component Subcomponent Number Description Resolution
RECORD did not
fire properly.
Batch Material Details 3788987 REMAINING
Issues ISSUES AFTER
APPLYING
2379723 -
CHANGING
ACTUAL QTY IN
MATERIAL
REMAINING
ISSUES AFTER
APPLYING
2379723 -
CHANGING
ACTUAL QTY IN
MATERIAL
DETAILS
DETAILS

FP_ORDERS
The FP_ORDERS business activity includes the patches listed in the following table:

Patch
Component Subcomponent Number Description Resolution
Firm 3460631 When Code was modified so that in
Planned converting a converting a FPO to a batch, the
Orders firm planned required completion date defaults to
order (FPO) the planned completion date.
to a batch,
the required
completion
date did not
default to the
planned
completion
date.
Firm 3503020 The batch or The Convert Firm Planned Order to
Planned firm planned Batch window was updated so that
Orders order (FPO) the leadtime defaults are based on
creation the production rules, but can be
process now changed. An indicator was added to
uses the the window so you can select
planned start whether to use the leadtime, or have
date and the batch creation process use the
planned calculated duration from the
completion production rules or the routing (if
date you one exists). The
 Patch
Component Subcomponent Number Description Resolution
entered. If gme_api_create_batch.create_batch
you enter procedure was modified to consider
only one a user-entered planned start date
date, then the and planned completion date when
application creating a batch or firm planned
calculates the order. Code was modified so that
other date after creating a batch and before
based on the creating any transactions, the
routing or application checks for and uses the
production Plan Start Date and Plan
rules. Completion Date if these fields are
entered.
Firm 3669300 When you Code was modified so that the
Planned converted a character formats for the start_date
Orders firm planned and end_date parameters are
order to a compatible.
batch, the
error
message:
"FRM-47023:
No such
parameter
named
g_query_find"
displayed.

GME-PE
The GME-PE business activity includes the patches listed in the following table:

Patch
Compon Subcompo Numb
ent nent er Description Resolution
Batch Batch Steps 32582 Query by Example Code was modified to remove unneeded
Issues 14 functionality does when-list-changed triggers that disable
not work on the various fields from being queried.
Batch Steps
window.
GME 23797 You were not You can enter or update the actual
Process 23 allowed to enter the quantity of a plain controlled item on the
Executio actual quantity a Batch Material Details window or using the
n plain controlled item Update Material Detail API for the material
11.5.1I+ without drilling down satisfying all of the following conditions: 1.
to the Line Material is plain controlled 2. Consumption
Allocations window type is auto release or auto by step 3.
from the Batch Batch status is WIP or Complete 4. Only
Material Details one completed transaction exists for the
window. material
 Patch
Compon Subcompo Numb
ent nent er Description Resolution
GME 23836 You cannot save a You can save a folder as the default on
Process 72 folder as the default the Material Details window. The Planned
Executio on the Material Qty field displays by default in a WIP,
n Details window. The Completed, or Closed batch, so that you
11.5.1I+ Planned Qty field can compare planned versus actual
does not display by quantities.
default in a WIP,
Completed, or
Closed batch,
therefore you cannot
compare planned
versus actual
quantities.
GME 26732 Field labels were not Fields were properly aligned on the Batch
Process 89 properly aligned on Step Dependencies window.
Executio the Batch Step
n Dependencies
11.5.1I+ window.
GME 29510 Batch resources Resources are not displayed in their
Process 35 displayed on the appropriate order, and the scale type on
Executio workbench were not the Step Activity Resource window
n shown in an displays the correct value.
11.5.1I+ appropriate order.
The scale type in
Summary of Step
Activity Resource
window displayed
the wrong value.
GME 29904 If you changed a When you place the cursor on a
Process 42 location controlled nonlocation controlled item, navigate to
Executio warehouse to a Pick Lots/Locations window, change the
n nonlocation warehouse to a nonlocation controlled
11.5.1I+ controlled warehouse, and tab out of the field, no
warehouse on the value is displayed in location field, and
Pick Lots/Locations entry of a value is not required.
window, allocated
the required
quantity, navigated
to Line Allocations
window, and tried to
move to the next
line, then the cursor
was placed in the
Location field. The
message: Entry is
required displayed.
This prevented the
allocation. The
default location was
displayed as NONE
 Patch
Compon Subcompo Numb
ent nent er Description Resolution
rather than NULL
(blank) for the
nonlocation
controlled
warehouse.
GME 30058 When you rerouted An error displays when a pending batch is
Process 04 a batch with a status rerouted and all the products are not
Executio of Pending, you convertible to the routing UOM.
n were not able to
11.5.1I+ save it if all its
products were not
convertible to the
routing UOM.
GME 30270 If the planned or Updating an activity using Update Activity
Process 04 actual activity factor API did not populate, the
Executio was updated using GME_INVENTORY_TXNS_GTMP and
n the Update Activity GME_RESOURCE_TXNS_GTMP tables.
11.5.1I+ API, then the Therefore, the save_batch did not find
resource usage was header information, and it could not
updated, but the perform a consolidation transaction. Code
resource was added to the
transactions were ME_BATCHSTEP_ACT_PVT.update_batc
not updated. hstep_activity procedure to load material
and resource transactions when a
resource is modified as a result of
updating the activity factor.
GME 30417 You were not able to The flexfield name in the call present in
Process 18 set up the GMESTPED_FORM.when_new_form_inst
Executio descriptive flexfield ance procedure exceeded the maximum
n on the Resource 32-character length
11.5.1I+ Process Parameter (GME_BATCH_RESOURCE_PROC_PAR
window. AM_FLEX). The flexfield name was
changed to
ME_BATCH_PROC_PARAM_FLEX. The
descriptive flexfield on the Resource
Process Parameter window is displays
successfully.
GME 30417 Refer bugs 2919829 Refer bugs 2919829 and 2989923.
Process 31 and 2989923.
Executio
n
11.5.1I+
GME 30455 (For Release No code existed to manage autoallocation
Process 77 11.5.1J) The for this scenario. Code was added in the
Executio autoallocation option procedure
n was not functioning gme_api_allocate_line_pvt.allocate_line to
11.5.1I+ properly for a lot- allocate quantities from multiple lots to
controlled, manage this situation.
indivisible item with
 Patch
Compon Subcompo Numb
ent nent er Description Resolution
multiple lots onhand,
and a batch that
required more than
one lot.
GME 30456 (Port of bug Code was modified so that line allocation
Process 72 2820817 to transaction date displays the actual batch
Executio 11.5.10K) The step completion date.
n Transaction Date on
11.5.1I+ Line Allocations
window of the batch
does not reflect the
actual completion
date of the step to
which the material is
associated. The
date in the pending
inventory
transactions is the
transaction date
rather than the
planned step
completion date.
The transaction date
is the date that the
batch is due to be
completed as a
whole.
GME 30463 After upgrade from Code was modified with the addition of an
Process 58 11.5.1F to 11.5.1J, index on the table gme_material_details
Executio performance for column phantom_id. The query
n problems occurred executes with an index scan rather than a
11.5.1I+ when you clicked full table scan. This improved
Proceed on the performance.
Complete Batch -
Incomplete Manual
Allocations window.
GME 30540 The error APP- Code was modified so that you can enter
Process 01 GMA-80310 the actual start date on a WIP completed
Executio displayed when step.
n changing the actual
11.5.1I+ start date on a
completed batch
step to a date that
was later date than
the batch header
start date.
GME 30607 In the SQLBIND- Quotes and concatenations that are
Process 00 compliant project, required for building the dynamic query in
Executio some of the the trigger 'when-button-pressed' for
n concatenation object batchfpo_find were restored.
 Patch
Compon Subcompo Numb
ent nent er Description Resolution
11.5.1I+ quotes were
removed, including
those required to
build a dynamic
query. This resulted
in disabling the
advanced search
capability in the
Process Execution
Workbench.
GME 30664 When you released Code was modified to check for
Process 71 or completed a mandatory flexfield segment entries. If
Executio batch or a step that they are required, and none are entered,
n required mandatory then an appropriate error message
11.5.1I+ flexfield segment displays.
entries, no error
displayed.
GME 30692 If you created a The secondary quantity in IC_TRAN_PND
Process 10 formula with a single is not updated if the item has a single
Executio UOM for product UOM.
n and ingredients,
11.5.1I+ created a batch with
a product that has a
single UOM, then
released and
partially certified the
batch, the IC-
TRAN_PND
transactions
erroneously created
transactions for
quantities in the
secondary UOM.
GME 30695 You were able to Code was modified so that you cannot
Process 46 perform multiple create multiple allocations for the same lot
Executio allocations for the of an indivisible item. If you attempt to do
n same lot of an this, the following error message displays:
11.5.1I+ indivisible item. "This indivisible lot has already been
allocated elsewhere." You cannot proceed
until the record is deleted or cleared.
GME 32084 (Port Bug 2880076 Code prompts were modified to correct the
Process 53 to 11.5.10L) When problem. Folders are now properly aligned
Executio you create a folder on the Line Allocations window.
n on the Line
11.5.1I+ Allocations window,
and set it as default,
the folder columns
are not properly
aligned.
 Patch
Compon Subcompo Numb
ent nent er Description Resolution
GME 32163 (Port Bug 3035457 You can create a batch with an automatic
Process 49 TO 11.5.10L) Prior phantom ingredient quantity set to 0.
Executio to Release 11.5.1I,
n you were allowed to
11.5.1I+ create a batch, or a
phantom batch, with
a zero product
quantity. After
Release 11.5.1J,
this was prevented.
When you
attempted this, you
got the error:
'Primary Product qty
must be greater
than 0' displayed.
GME 32533 During the process Code was modified so that when lot status
Process 44 of picking lots, is changed, the application does not
Executio changing lot status update any of the pending transactions
n affected the allocated using that lot.
11.5.1I+ available quantity of
an item.
GME 32584 (Port Bug 3241391 Changes to the WIP warehouse on an
Process 83 to 11.5.10L) If you FPO are carried forward when the FPO is
Executio changed the WIP converted to a batch.
n warehouse on an
11.5.1I+ FPO, and converted
the FPO to a batch,
then the batch was
not created with the
newly assigned WIP
warehouse.
GME 33094 (Port Bug 3255993 Rounding during incremental backflushing
Process 80 TO 11.5.10L) was modified so that the difference
Executio Decimal rounding between the new actual quantity and the
n issues arose when material detail quantity is rounded to the
11.5.1I+ you tried to 32nd decimal place. This eliminates any
complete a batch differences calculated for the comparison
after an incremental of the allocated quantity in the update
backflush. The allocation procedure.
completion failed,
and an error
message was
displayed informing
you that pending
allocations exist for
manual release
items.
GME 33303 (Port Bug 3313541 The message was uploaded to the
Process 26 to 11.5.10L) The message token.
 Patch
Compon Subcompo Numb
ent nent er Description Resolution
Executio message token
n 'inv_resrc_qty_usag
11.5.1I+ e_opm' was
displayed instead of
the message:
"Process quantity
cannot be zero with
a nonzero usage for
the scaleable
resource
<resource_name> in
the activity
<activity> in the
operation <stepno,
operation_no>.
Please correct the
resource definition
in the operation."
GME 33338 (Port Bug 3242987 Code was modified for proper locking and
Process 22 to 11.5.10L) If more query-only viewability for individual users
Executio than one user tried who try to access the Material Details or
n to access the Line Allocations windows for the same
11.5.1I+ Material Details batch simultaneously.
window or Line
Allocations window
simultaneously for
the same batch,
then these
messages
displayed: "Could
not reserve record.
Keep Trying?" If
either user clicked
No, then "FRM-
40501: ORACLE
error: unable to
reserve record for
update or delete"
displayed.
GME 33494 (Port Bug 3240262 The local variable length was increased to
Process 44 to 11.5.10L) The 4000, and rpadding was increased so that
Executio following error when this variable is used in a message
n occurred when display in
11.5.1I+ trying to change the SET_CUSTOM_ITEM_PROPERTY with
batch date from substr it has sufficient length available.
Production
Scheduler window:
"Your user area
applet has caused a
runtime exception,
the applet will be
 Patch
Compon Subcompo Numb
ent nent er Description Resolution
terminated to ensure
continued
functioning of your
form." (This was
followed by JAVA
error codes.)
GME 33727 The Break indicator The Activities window has the Break
Process 74 was not passed indicator and the Maximum Break fields
Executio properly to a new with folder access. The memory-based
n batch. The memory- planner does not display errors when
11.5.1I+ based planner running OPM plans.
displayed errors
when running OPM
plans.
GME 33751 (Port Bug 3343877 Code was added to the
Process 12 TO 11.5.10) If you when_new_record_instance of the batch
Executio used Query Find header to load the transactions into the
n functionality on the _gtmp table. This is done only if the table
11.5.1I+ Batch Material did not already have the transactions for
Details window to the batch. A cursor cur_get_row_count
find a batch was created to check the transactions in
containing lot- the table. If the records are not found, then
controlled, GMEMATED.load_transactions is called to
autoallocated load the transactions.
ingredients, and
added at least one
ingredient, when the
batch was allocated,
the window updated
correctly. If you did
this for several
batches, and
attempted to
navigate to a batch
displayed on the
window using the
arrow keys, when
you drilled down to a
lot controlled item,
the application
displayed this error:
"Default Lot cannot
be found."
GME 33775 When no Code was modified in the applet handler
Process 95 corresponding row to check the return from the cursor to
Executio of nls_language and determine if any corresponding row is
n nls_territory was found in the fnd_language. If no row is
11.5.1I+ found in found, then a message is displayed to
fnd_language, no inform the user.
error message was
 Patch
Compon Subcompo Numb
ent nent er Description Resolution
displayed to indicate
a problem. This
resulted in improper
translation of the
day and date on the
Production
Scheduler GANTT
chart.
GME 34066 Only the formula_id Code was modified to pass the
Process 30 was used to parameters item_id, qty, and uom to the
Executio determine validity validity rules window so that the criteria for
n rules during a batch validity rules are set appropriately. APIs
11.5.1I+ reroute. The product were modified by the addition of where
quantity was not conditions in the cursor to check
considered. quantities.
GME 34248 (Port Bug 3402951 Code was modified so that lot_id and
Process 38 to 11.5.10L) There location are only passed with default
Executio was a performance values during batch creation. Lot and
n problem in inventory location values are not needed. Their
11.5.1I+ shortage checking removal improved performance.
during the initial
batch creation.
GME Batch/FPO 30354 Prior to Release You can create a batch with an automatic
Process Details 57 11.5.1I, you were phantom ingredient quantity set to 0.
Executio allowed to create a
n batch, or a phantom
11.5.1I+ batch, with a zero
product quantity.
After Release
11.5.1J, this was
prevented. When
you attempted this,
you got the error:
'Primary Product qty
must be greater
than 0' displayed.
GME Batch/FPO 30400 (Reference to If the nettable status for a particular lot is
Process Details 53 Release 11.5.10J) set to NO, and production is set to YES,
Executio You were not able to then the lot is available for production.
n allocate quantities Prior to the fix you were not able to use
11.5.1I+ that were already such lots for production.
allocated for sales
order lines (OMSO
document type
lines).
GME Batch/FPO 30464 An error displayed if You can enter a WIP batch ingredient from
Process Details 79 you allocated a WIP nonlocation warehouse lots on the Pick
Executio batch ingredient Lots/Location window.
n from a nonlocation
 Patch
Compon Subcompo Numb
ent nent er Description Resolution
11.5.1I+ warehouse on the
Pick Lots/Location
window.
GME Batch/FPO 30478 When a lot- A new error message was created: "No
Process Details 14 controlled ingredient inventory for lot &LOT_NO in warehouse
Executio was allocated using &WHSE. Item's default lot status
n the Pick &LOT_STATUS is not usable for
11.5.1I+ Lots/Location production."
window, and the
warehouse was
subsequently
changed on the
Allocations window
so that the new
warehouse had no
onhand inventory for
that lot, then an
incorrect error
message displayed
indicating that the lot
was unusable for
production.
GME Batch/FPO 33777 You were able to Code was modified by the addition of a
Process Details 68 insert, update, or condition for batch type to disable insert,
Executio delete material on update, or delete functions on the FPO
n the Firm Planned Material Details window.
11.5.1I+ Order Material
Details window.
GME Batch/FPO 30136 When the value of Code was modified so that the check for
Process Header 64 the profile option the profile option "GME: Check Inventory
Executio GME: Check Shortage Upon Save" occurs before
n Inventory Shortage displaying inventory shortages. A check
11.5.1I+ Upon Save was set was added for the same profile option in
to No, it interfered GMEBCHED.when_form_navigate, before
with the finish-to- checking for inventory shortages.
start offset type in
the FPO conversion
process.
GME Batch/FPO 30887 Both the planned The GME: Validate Planned Dates profile
Process Header 39 start date and option was added to control how batch
Executio planned completion dates and firm planned order dates are
n date of a batch are validated against the validity rule used.
11.5.1I+ validated against the When set to 0, Validate Both Planned
dates on the validity Dates, the planned completion and
rule for the batch. planned start dates are validated against
Neither the planned the validity rule date range when creating
start date nor the or rescheduling a batch or firm planned
planned completion order. When set to 1, Validate Planned
date can be outside Start Date Only, only the planned start
the date range dates are validated against the validity rule
 Patch
Compon Subcompo Numb
ent nent er Description Resolution
defined on the date range when creating or rescheduling
validity rule. This is a batch or firm planned order.
enforced during
batch creation and
batch rescheduling.
You need the ability
to schedule batches
that have a planned
completion date that
extends beyond the
end date of the
validity rule.
GME Batch/FPO 32945 If you entered text The Edit Text icon displays appropriately
Process Header 07 for a production on all these windows.
Executio batch using the Edit
n Text option on the
11.5.1I+ Batches, Batch
Steps, or Batch
Material Details
windows, then the
Edit Text icon did
not display properly.
GME Batch/FPO 34066 Batch release Code was modifed so that the validation of
Process Header 39 displayed an error current attribute values is done
Executio when context- simultaneously with validation of global
n sensitive flexfields data elements. Six new procedures were
11.5.1I+ were used on the created in the gme_api_grp package to
Batch window if validate the descriptive flexfields using
these flexfields had server-side flexfield validation.
different sets of
attribute context
values for plant
codes.
GME Inquiries 34406 After batch Code was modified so that after batch
Process 49 reallocation, manual reallocation and manual completion all
Executio completion of transactions, the grade is recorded
n transactions did not appropriately for all completed
11.5.1I+ display the grade transactions. Adjustments to the phantom
information. batch material, such as scaling of a
Phantom batch phantom ingredient, and appropriate
overallocations were product allocations are adjusted
not displayed appropriately.
properly on the
Items Requiring
Allocation window.
GME Reports 31619 You were not able to Code was modified to evaluate a process
Process 28 set up a process loss of zero by adding the NVL condition
Executio loss of zero at the in get_process_loss.
n routing class level
11.5.1I+ for various quantity
 Patch
Compon Subcompo Numb
ent nent er Description Resolution
ranges.
GME Workbench 30221 A batch scaled to a Code was added to round off the planned
Process 00 quantity of 10,000 quantity and the original quantity to 32
Executio displayed as decimal places after scaling is performed
n 9999.999999999 on in the procedure
11.5.1I+ the Workbench. gme_api_create_batch.create_batch.
GME Workbench 32241 In the SQLBIND- Concatenation quotes that are required
Process 43 compliant project, were restored so that you can expand
Executio some of the Personal Shortcuts.
n concatenation
11.5.1I+ quotes were
removed which
resulted in the
inability to expand
Personal Shortcuts
on the Process
Execution
Workbench.
Other 34255 The Procedure - Code was modified to fetch the resource
Issues 54 Close Batch transactions properly in the close_batch
(close_batch) API API to correct the interpretation of
did not properly resource reversals.
interpret resource
reversals.

GMF-MAC
The GMF-MAC business activity includes the patches listed in the following table:

Patch
Component Subcomponent Number Description Resolution
GME Batch/FPO 3303901 The Subledger Bug number:
Process Details Update process 3303901 All
Execution doe not pick up warehouses used in
11.5.1I+ batch allocation a batch must be
from different owned by the
companies. company that owns
the WIP warehouse.
The following
changes are
introduced in
various Process
Execution windows
to implement this:
When creating a
batch or a Firm
Planned Order,the
 Patch
Component Subcomponent Number Description Resolution
WIP warehouse is
limited to the
warehouses owned
by the parent
company of the
batch. In the
Material Details
window,warehouses
owned by the
company that owns
the WIP warehouse
of the batch,can be
used in the batch.
Similarly, for the
items requiring
allocation screen.
The WIP
warehouse on the
Pick Lots window
shows only
warehouses owned
by the parent
company of the
batch. Similarly
through the API,
you cannot create a
batch or FPO with a
warehouse that
does not belong to
the plant of the
batch. You also
cannot insert or
update the
warehouse for a
transaction to a
warehouse outside
of the parent
company through
the API. Bug
number: 3544683
While creating a
batch, the Pick Lots
option from the
Actions menu
should be disabled
for the items failing
allocation. Bug
number: 3535751 In
the line allocations
window of the
material details, the
calendar LOV
displays when
 Patch
Component Subcomponent Number Description Resolution
invoked from the
Transaction Date
field.

INQUIRY
The INQUIRY business activity includes the patches listed in the following table:

Patch
Component Subcomponent Number Description Resolution
Inquiries 3488630 The Batch Step Code was modified
Variance and so that the Batch
Resource Variance Step Variance and
related windows Resource Variance
only display details related windows
for the last activity display details for
of an operation. all activities of an
operation.

OTHER
The OTHER business activity includes the patches listed in the following table:

Patch
Compon Subcompon Numb
ent ent er Description Resolution
Batch Batch 34985 (Port Bug 2729171 to 11.5.10L) Lot Code was modified
Issues Creation 08 dates were not calculated properly. so that the dates for
You were able to consume lots with a the lot remain NULL
NULL expiration date. Dynamically until a completed
created lots were assigned a date transaction is
when they still had a status of Pending. performed against
the lot. This includes
a transaction on an
e-signature. Lot
dates are now
properly computed
based on the
completed
transaction date and
any item additional
information setup.
Other 36381 When you ran the Code was modified
Issues 39 gme_api_pub.insert_material_line API, for the validate_field
you received the error: Cannot insert procedure of the
NULL into gme_api_material_d
 Patch
Compon Subcompon Numb
ent ent er Description Resolution
GME.GME_MATERIAL_DETAILS.ALL etails package to
OC_IND. The alloc_ind was passed in check the value of
as NULL. the alloc_ind for the
INSERT action code.
If the alloc_ind is
passed as null, then
it is set to 0. With
this modification, the
material line inserts
into the table
gme_material_detail
s without any error.

REPORTS
The REPORTS business activity includes the patches listed in the following table:

Patch
Component Subcomponent Number Description Resolution
Report 3685721 When calculating Batch Yield
Issues accounting-related Variance Report: In
functions in the the calculation of
Batch Yield accounting-related
Variance Report functions, including
and Material Usage actual cost, code
and Substitution was modified to
Variance Report, convert quantities
the item's expressed the in
secondary unit of the item's
measure was used secondary unit of
when the primary measure to its
unit of measure primary UOM
was not entered. before multiplying
by the cost.
Material Usage and
Substitution
Variance Report:
Code was modified
to convert a
variance quantity
expressed the in
the item's
secondary unit of
measure to its
primary UOM
before multiplying
the variance by the
actual cost. Item
costs are always
 Patch
Component Subcomponent Number Description Resolution
calculated in the
primary UOM.

SCHEDULER
The SCHEDULER business activity includes the patches listed in the following table:

Patch
Component Subcomponent Number Description Resolution
Scheduler 3503368 The Enable/Disable The NLS issue was
Workbench Schedule option on resolved so that
the Production you can enable or
Scheduler disable the
Workbench was schedule on the
not functioning Production
properly due to a Scheduler
National Language Workbench.
Support (NLS)
issue.

Change Record
Date Version Description of Change
2/14/03 1.0 Created document.

Oracle Corporation
Copyright Information
Copyright 1994-2003, Oracle Corporation. All rights reserved.

Trademark Information
Oracle is a registered trademark of Oracle Corporation.