New & Changed Feature in OPM

About Process Execution in Process Manufacturing Family Pack LLast 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 11 i About Oracle Process Manufacturing Family Pack L document, located on the Oracle e-Business Suite Release 11 i 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 11 i 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 11 i 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:

Component

Subcomponent

Patch Number Description Resolution

API Issues

3620264

(Duplicate of bug 3612970) The update batch step resource API generated syntax errors.

Code was modified in update_batchstep_rsrc API to manage character data properly to resolve the syntax issue.

API Issues

Process Execution APIs

3552262

(Port bug 3543428 to 11.5.10L) A record processed by the Insert Material API (GME_API_PUB.insert_material_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

Code was modified to correct the typographic error in assignment of error status to correct the issue.

Component

Subcomponent


to the variable x_return_staus instead of x_insert_return_status. Therefore, the correct status was never returned to the calling procedure.

API Issues

Production Management APIs

3777331

POOR PERFORMANCE IN GME_API_PUB.INSERT_LINE_ALLOCATION API AFTER INSTAL 3689809

API Issues

Production Operation Control APIs

3479669

If you used the start_cmplt_actual_rsrc_txn API to record the batch start time in GME_RESOURCE_TXNS, and ran a subledger update, then the posted_ind was set to 1 (indicating the subledger was posted). If you proceeded to run the end_cmplt_actual_rsrc_txn, the API mistakenly allowed the upadate of a posted record by entering an end date on the record in GME_RESOURCE_TXNS and an actual resource_usage.

Code was modified in the gme_resource_engine_pvt.consolidate_batch_resources procedure so that the initial check l_resource_row.completed_ind = 0 is removed irrespective of the current value of the completed_ind. The row is fetched from the database and checked for completed_ind. Transactions created are now initialized with a posted_ind of 0. If the completed resource transaction is deleted, then the new transaction is created with posted_ind of 0.

BATCHES

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

Component

Subcomponent


Batch Issues

3464841

(Port Bug 3347280 to 11.5.10L) Actual resource

The GME: Calculate Interim Resource Usage profile option is introduced. Set to No, the actual resource

Component

Subcomponent


usage was not properly represented for WIP. Lengthy steps did not reflect actual usage when actual step quantities were updated.

usage is not updated whenever the actual step quantity is updated. Set to Yes, the actual resource usage is updated based on the progress made through a lengthy step. This allows the planning and scheduling applications to identify that there is less remaining resource time required than that posted at the start of the step.

Batch Issues

3500386

(Port Bug 3345062 to 11.5.10L) The batch header descriptive flexfield did not open in the Greek language.

The batch header descriptive flexfield opens in the Greek language and all other supported languages.

Batch Issues

3507304

(Port Bug 3482271 to 11.5.10L) You could not allocate a batch line with a Manual Consumption 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."

Code was modified by addition of an "OR" condition for completed batches so that you can allocate quantities through the Pick Lots/Locations window without displaying an error message for any release type.

Batch Issues

3530087

(Port bug 3488739 to 11.5.10L) Even with GMI: Bypass Sublot

Code was modified so that when GMI: Bypass Sublot Warning is set to 1, no error message displays when you tab out of the Sublot field

Component

Subcomponent


Warning set to 1, the error message "APP-GMA-80432: Entry is required" displayed when you tabbed out of the Sublot field without entering a value.

without entering a value.

Batch Issues

3545726

(Port Bug 3516077 to 11.5.10L) In many instances, the calculation of resource usage was not accurate when based solely on ingredient consumption. Performing an incremental backflush on a product that was associated to a step did not record the resource usage correctly.

To record actual resource usage for a step associated to a product, use the incremental backflushing functionality without ASQC selected, and the GME: Backflush Resource Usage profile option set to Yes. Performing an incremental backflush on a product that is associated to a step records the resource usage proportionally when this profile option is set to Yes.

Batch Issues

3554030

(Port bug 3511883 to 11.5.10L) FRM-41077: "Error deleting Group Rows" displayed under these conditions: set default folder to Production Operator, set Consumption Type for Ingredient as a hidden field, navigate to the Material Details

Code was modified to add an "if" condition in remove_folder_field function of GME_BATCH_HEADER_API package. The application now checks for the existance of a row before calling DELETE_GROUP_ROW.

Component

Subcomponent


window, query a batch, and place cursor focus on the Products tab.

Batch Issues

3581403

Use of the Pick Lots window did not properly default the secondary quantity after batch creation. This resulted in an unnecessarily running of the UOM conversion when the full primary quantity was consumed.

Code was modified to consume the secondary quantity derived by the stock cursor instead of running the UOM conversion when the full primary quantity was consumed.

Batch Issues

3614820

When you completed a batch, you were unable to determine the validity of the warning that pending transactions exist for manual and incremental items. If a quantity greater than zero existed in the default transaction, and 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

A new system profile, GME: Warn If Plan Qty Is Greater Than Allocated Qty, was created to rectify this issue. Set to Yes, the application considers the default lot when determining whether incomplete or pending transactions exist for manual and incremental items, and a warning displays. Set to No, the application does not consider the default lot when determining whether incomplete or pending transactions exist for manual and incremental items, and no warning displays.

Component

Subcomponent


ignored for manual and incremental items.

Batch Issues

3648627

You were not able to query all batches and FPOs in the Production Schedule Inquiry. The error "APP-GMA-80300 Document Number Assignment record not set up" displayed.

Code was modified so that you can view or query all batches and FPOs in the Production Schedule Inquiry whether or not you select any document number. Relevant data is displayed regardless of deleting the document ordering.

Batch Issues

3818266

FP:11.5.10+ - 11.5.10L :PERFORMANCE PROBLEMS WHEN THERE ARE MANY BATCH RESOURCE

Batch Issues

3834514

FP:11.5.7I - 11.5.10L :SCALING DOWN A BATCH DOES NOT REVERSE THE TRANSACTIONS.

In GMEUNISM form, when the adjustment of the allocated quantities happens,By calling the function,update_completed_trans for the existing completed transactions in ic_tran_pend with completed indicator as 1, the problem is corrected.

Batch Issues

Batch Creation

3469968

During the batch scaling process, the quantities of the primary products were verified using the minimum and maximum quantities of the selected validity rule. This checking procedure did

The Scale_batch API quantities are converted to the validity rule UOM before comparisons are made to determine whether the scaled quantities are outside the validity rule limits.

Component

Subcomponent


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 Issues

Batch Creation

3500392

(Port Bug 3452221 to 11.5.10L) When the Document Ordering Assignment Type was Automatic, and the Last Assigned field value was NULL, creation of a production batch gave a blank error message.

To resolve the issue, an appropriate error message displays to inform you that the organization uses automatic document ordering, and that you must enter a valid value in the Last Assigned field for the document before creating a batch.

Batch Issues

Batch Creation

3533505

If you queried a batch on the Batches window, modified the batch status, and then tried to navigate to the next or previous record, then all other batches were not accessible except the one you modified.

Code for the cntrl_reschedule procedure was modified so that reassignment of fields is performed instead of a requery. This resolves the accessibility issue.

Batch Issues

Batch Creation

3591066

If you navigated from the Batches window to the

Batches or Batch Material Details windows that are open as the result of a call from another window are

Component

Subcomponent


Batch Material Details window, kept the Batch 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.

refreshed properly, and display the newly retrieved data after queries.

Batch Issues

Batch Creation

3700014

If you entered the plan start date and plan completion date for a batch with production rules, but no routing, then the application ignored the these dates if you responded "No" to the question "Calculate dates?"

Code was added to the date check for batches with production rules, but no routing. The plan start date and plan completion date entered are used. If no dates are entered, then you are not asked whether you want to calculate dates.

Batch Issues

Batch Material Transactions

3476239

Unreleasing a batch led to negative inventory for a product that moved to another warehouse or location.

The issue is fixed by use of the GMI: Allow Negative Inventory profile option to warn you when editing or reversing product or byproduct yield. Set to 0, if the change to the product or byproduct yield quantity drives 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,

Component

Subcomponent


then a warning displays and you are asked if you want to proceed. You can save your work or cancel the transaction.

Batch Issues


3630485

It was possible to partially allocate an indivisible lot using the secondary quantity field.

Code was modified so that you can no longer partially allocate an indivisible lot by entering a value less than its total quantity in the secondary quantity field.

Batch Issues


3633271

There was a defective recall of the primary UOM and detail line UOM in the Pick Lots query. Both parameters were entered in the same UOM without a conversion. The message that you drove inventory negative occurred when the allocated quantity was greater than the available quantity, irrespective of the setting for the GMI: Allow Negative Inventory profile option.

Code was modified to the correct the defective recall of the primary UOM and detail line UOM in the Pick Lots query. When a transaction is completed, the onhand inventory is properly reduced in both the primary and secondary UOM. In those cases where inventory is legitimately driven negative, an appropriate error message displays on both Pick Lots window and on the Line Allocation window. Display of the message is in accord with the setting for GMI: Allow Negative Inventory.

Batch Issues


3643292

When you queried a lot number from the Line Allocations window of a batch item, you had to search for it in the list. If you

Code was modified by the addition of app_query.query_foreign_key code in pre_query for lot_no and sublot_no so that the appropriate release type is available for the query.

Component

Subcomponent


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 Issues


3720215

Locations with field lengths greater than 10 characters do not display in the Pick Lots window because the location tab was defined as varchar2(10).

Code was modified in GMEVALLS.pls to accommodate greater than 10 characters. Locations with field lengths greater than 10 characters display properly in the Pick Lots window.

Batch Issues

Material Details

3519756

When you selected a material line on the Batch Material Details window, 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 allocation to proceed

Code was modified so that after inserting a material in a batch, you can create line allocations without the requirement to save your work each time.

Component

Subcomponent


without errors.

Batch Issues

Material Details

3575387

If the plan quantity was zero, or was not entered, then the scrap factor and required quantity fields were disabled.

Code was added to disable the Required Qty and Scrap Factor fields initially if the plan quantity in a pending batch, or the WIP plan quanity in work-in-process batch is not entered or is zero. These fields are enabled once 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 Issues

Material Details

3590875

If you deleted a completed allocation in a WIP batch, clicked OK, did not save your work, deleted a material line in Material Details 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.

Correct action codes are sent to a temporary table. Transaction consolidation does not create incorrect reversals. When a completed transaction is updated and deleted, the application now fetches the current transaction in ic_tran_pnd and uses it to reverse the transaction.

Batch Issues

Material Details

3648996

It was not possible to add extra validations on the transaction date of an allocation line using the

Code was modified to add CUSTOM.pll functionality to the Line Allocations window to enable extra validations. WHEN-VALIDATE-RECORD fires properly.

Component

Subcomponent


CUSTOM.pll code on the Line Allocations window. WHEN-VALIDATE-RECORD did not fire properly.

Batch Issues

Material Details

3788987

REMAINING 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:

Component

Subcomponent

Patch Number

Description Resolution

Firm Planned Orders

3460631

When converting a firm planned order (FPO) to a batch, the required completion date did not default to the planned completion date.

Code was modified so that in converting a FPO to a batch, the required completion date defaults to the planned completion date.

Component

Subcomponent

Patch Number

Description Resolution

Firm Planned Orders

3503020

The batch or firm planned order (FPO) creation process now uses the planned start date and planned completion date you entered. If you enter only one date, then the application calculates the other date based on the routing or production rules.

The Convert Firm Planned Order to Batch window was updated so that the leadtime defaults are based on the production rules, but can be changed. An indicator was added to the window so you can select whether to use the leadtime, or have the batch creation process use the calculated duration from the production rules or the routing (if one exists). The gme_api_create_batch.create_batch procedure was modified to consider a user-entered planned start date and planned completion date when creating a batch or firm planned order. Code was modified so that after creating a batch and before creating any transactions, the application checks for and uses the Plan Start Date and Plan Completion Date if these fields are entered.

Firm Planned Orders

3669300

When you converted a firm planned order to a batch, the error message: "FRM-47023: No such parameter named g_query_find" displayed.

Code was modified so that the character formats for the start_date and end_date parameters are compatible.

GME-PE

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

Component

Subcomponent


Batch Issues

Batch Steps

3258214

Query by Example functionality does not work on the Batch Steps window.

Code was modified to remove unneeded when-list-changed triggers that disable various fields from being queried.

GME Process Execution 11.5.1I+

2379723

You were not allowed to enter the actual quantity a plain controlled item without drilling down to the Line Allocations window from the Batch Material Details window.

You can enter or update the actual quantity of a plain controlled item on the Batch Material Details window or using the Update Material Detail API for the material satisfying all of the following conditions: 1. Material is plain controlled 2. Consumption type is auto release or auto by step 3. Batch status is WIP or Complete 4. Only one completed transaction exists for the material


2383672

You cannot save a folder as the default on the Material Details window. The Planned Qty field does not display by default in a WIP, Completed, or Closed batch, therefore you cannot compare planned versus actual quantities.

You can save a folder as the default on the Material Details window. The Planned Qty field displays by default in a WIP, Completed, or Closed batch, so that you can compare planned versus actual quantities.


2673289

Field labels were not properly aligned on the Batch Step Dependencies window.

Fields were properly aligned on the Batch Step Dependencies window.


2951035

Batch resources displayed on the workbench were not shown in an appropriate order. The scale type in Summary of Step Activity Resource window

Resources are not displayed in their appropriate order, and the scale type on the Step Activity Resource window displays the correct value.

Component

Subcomponent


displayed the wrong value.


2990442

If you changed a location controlled warehouse to a nonlocation controlled warehouse on the Pick Lots/Locations 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 rather than NULL (blank) for the nonlocation controlled warehouse.

When you place the cursor on a nonlocation controlled item, navigate to Pick Lots/Locations window, change the warehouse to a nonlocation controlled warehouse, and tab out of the field, no value is displayed in location field, and entry of a value is not required.


3005804

When you rerouted a batch with a status of Pending, you were not able to save it if all its products were not convertible to the routing UOM.

An error displays when a pending batch is rerouted and all the products are not convertible to the routing UOM.

GME Process Execution

3027004

If the planned or actual activity factor was updated using the Update

Updating an activity using Update Activity API did not populate, the GME_INVENTORY_TXNS_GTMP and GME_RESOURCE_TXNS_GTMP

Component

Subcomponent


11.5.1I+

Activity API, then the resource usage was updated, but the resource transactions were not updated.

tables. Therefore, the save_batch did not find header information, and it could not perform a consolidation transaction. Code was added to the ME_BATCHSTEP_ACT_PVT.update_batchstep_activity procedure to load material and resource transactions when a resource is modified as a result of updating the activity factor.


3041718

You were not able to set up the descriptive flexfield on the Resource Process Parameter window.

The flexfield name in the call present in GMESTPED_FORM.when_new_form_instance procedure exceeded the maximum 32-character length (GME_BATCH_RESOURCE_PROC_PARAM_FLEX). The flexfield name was changed to ME_BATCH_PROC_PARAM_FLEX. The descriptive flexfield on the Resource Process Parameter window is displays successfully.


3041731

Refer bugs 2919829 and 2989923.

Refer bugs 2919829 and 2989923.


3045577

(For Release 11.5.1J) The autoallocation option was not functioning properly for a lot-controlled, indivisible item with multiple lots onhand, and a batch that required more than one lot.

No code existed to manage autoallocation for this scenario. Code was added in the procedure gme_api_allocate_line_pvt.allocate_line to allocate quantities from multiple lots to manage this situation.


3045672

(Port of bug 2820817 to 11.5.10K) The Transaction Date on Line Allocations window of the

Code was modified so that line allocation transaction date displays the actual batch step completion date.

Component

Subcomponent


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.


3046358

After upgrade from 11.5.1F to 11.5.1J, performance problems occurred when you clicked Proceed on the Complete Batch - Incomplete Manual Allocations window.

Code was modified with the addition of an index on the table gme_material_details for column phantom_id. The query executes with an index scan rather than a full table scan. This improved performance.


3054001

The error APP-GMA-80310 displayed when changing the actual start date on a completed batch step to a date that was later date than the batch header start date.

Code was modified so that you can enter the actual start date on a WIP completed step.

GME Process Executi

3060700

In the SQLBIND-compliant project, some of the

Quotes and concatenations that are required for building the dynamic query in the trigger 'when-button-pressed' for object batchfpo_find

Component

Subcomponent


on 11.5.1I+

concatenation quotes were removed, including those required to build a dynamic query. This resulted in disabling the advanced search capability in the Process Execution Workbench.

were restored.


3066471

When you released or completed a batch or a step that required mandatory flexfield segment entries, no error displayed.

Code was modified to check for mandatory flexfield segment entries. If they are required, and none are entered, then an appropriate error message displays.


3069210

If you created a formula with a single UOM for product and ingredients, 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.

The secondary quantity in IC_TRAN_PND is not updated if the item has a single UOM.


3069546

You were able to perform multiple allocations for the same lot of an indivisible item.

Code was modified so that you cannot create multiple allocations for the same lot of an indivisible item. If you attempt to do this, the following error message displays: "This indivisible lot has already been allocated elsewhere." You cannot proceed until the record is

Component

Subcomponent


deleted or cleared.


3208453

(Port Bug 2880076 to 11.5.10L) When you create a folder on the Line Allocations window, and set it as default, the folder columns are not properly aligned.

Code prompts were modified to correct the problem. Folders are now properly aligned on the Line Allocations window.


3216349

(Port Bug 3035457 TO 11.5.10L) Prior to Release 11.5.1I, you were allowed to 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.

You can create a batch with an automatic phantom ingredient quantity set to 0.


3253344

During the process of picking lots, changing lot status affected the available quantity of an item.

Code was modified so that when lot status is changed, the application does not update any of the pending transactions allocated using that lot.


3258483

(Port Bug 3241391 to 11.5.10L) If you changed the WIP warehouse on an FPO, and converted the FPO to a batch, then the batch was not created

Changes to the WIP warehouse on an FPO are carried forward when the FPO is converted to a batch.

Component

Subcomponent


with the newly assigned WIP warehouse.


3309480

(Port Bug 3255993 TO 11.5.10L) Decimal rounding issues arose when you tried to complete a batch after an incremental backflush. The completion failed, and an error message was displayed informing you that pending allocations exist for manual release items.

Rounding during incremental backflushing was modified so that the difference between the new actual quantity and the material detail quantity is rounded to the 32nd decimal place. This eliminates any differences calculated for the comparison of the allocated quantity in the update allocation procedure.


3330326

(Port Bug 3313541 to 11.5.10L) The message token 'inv_resrc_qty_usage_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."

The message was uploaded to the message token.

GME Process

3333822

(Port Bug 3242987 to 11.5.10L) If more

Code was modified for proper locking and query-only viewability for individual users who try to

Component

Subcomponent


Execution 11.5.1I+

than one user tried to access the Material Details 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.

access the Material Details or Line Allocations windows for the same batch simultaneously.


3349444

(Port Bug 3240262 to 11.5.10L) The following error occurred when trying to change the batch date from Production Scheduler window: "Your user area applet has caused a runtime exception, the applet will be terminated to ensure continued functioning of your form." (This was followed by JAVA error codes.)

The local variable length was increased to 4000, and rpadding was increased so that when this variable is used in a message display in SET_CUSTOM_ITEM_PROPERTY with substr it has sufficient length available.


3372774

The Break indicator was not passed properly to a new batch. The memory-

The Activities window has the Break indicator and the Maximum Break fields with folder access. The memory-based planner does not display errors when running OPM

Component

Subcomponent


11.5.1I+

based planner displayed errors when running OPM plans.

plans.


3375112

(Port Bug 3343877 TO 11.5.10) If you used Query Find functionality on the Batch Material Details window to find a batch containing lot-controlled, autoallocated 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."

Code was added to the when_new_record_instance of the batch header to load the transactions into the _gtmp table. This is done only if the table did not already have the transactions for the batch. A cursor cur_get_row_count was created to check the transactions in the table. If the records are not found, then GMEMATED.load_transactions is called to load the transactions.


3377595

When no corresponding row of nls_language and nls_territory was found in fnd_language, no error message was displayed to indicate a problem. This

Code was modified in the applet handler to check the return from the cursor to determine if any corresponding row is found in the fnd_language. If no row is found, then a message is displayed to inform the user.

Component

Subcomponent


resulted in improper translation of the day and date on the Production Scheduler GANTT chart.


3406630

Only the formula_id was used to determine validity rules during a batch reroute. The product quantity was not considered.

Code was modified to pass the parameters item_id, qty, and uom to the validity rules window so that the criteria for validity rules are set appropriately. APIs were modified by the addition of where conditions in the cursor to check quantities.


3424838

(Port Bug 3402951 to 11.5.10L) There was a performance problem in inventory shortage checking during the initial batch creation.

Code was modified so that lot_id and location are only passed with default values during batch creation. Lot and location values are not needed. Their removal improved performance.


Batch/FPO Details

3035457

Prior to Release 11.5.1I, you were allowed to 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.

You can create a batch with an automatic phantom ingredient quantity set to 0.


Batch/FPO Details

3040053

(Reference to Release 11.5.10J) You were not able to allocate

If the nettable status for a particular lot is set to NO, and production is set to YES, then the lot is available for production. Prior to the fix you were not able to use such lots for

Component

Subcomponent


11.5.1I+

quantities that were already allocated for sales order lines (OMSO document type lines).

production.


Batch/FPO Details

3046479

An error displayed if you allocated a WIP batch ingredient from a nonlocation warehouse on the Pick Lots/Location window.

You can enter a WIP batch ingredient from nonlocation warehouse lots on the Pick Lots/Location window.


Batch/FPO Details

3047814

When a lot-controlled ingredient was allocated using the Pick Lots/Location 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.

A new error message was created: "No inventory for lot &LOT_NO in warehouse &WHSE. Item's default lot status &LOT_STATUS is not usable for production."


Batch/FPO Details

3377768

You were able to insert, update, or delete material on the Firm Planned Order Material Details window.

Code was modified by the addition of a condition for batch type to disable insert, update, or delete functions on the FPO Material Details window.

GME Batch/ 3013 When the value Code was modified so that the

Component

Subcomponent


Process Execution 11.5.1I+

FPO Header

664 of the profile option GME: Check Inventory Shortage Upon Save was set to No, it interfered with the finish-to-start offset type in the FPO conversion process.

check for the profile option "GME: Check Inventory Shortage Upon Save" occurs before displaying inventory shortages. A check was added for the same profile option in GMEBCHED.when_form_navigate, before checking for inventory shortages.


Batch/FPO Header

3088739

Both the planned start date and planned completion date of a batch are validated against the dates on the validity rule for the batch. Neither the planned start date nor the planned completion date can be outside the date range defined on the validity rule. This is 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.

The GME: Validate Planned Dates profile option was added to control how batch dates and firm planned order dates are validated against the validity rule used. When set to 0, 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. When set to 1, 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.

GME Process Execution 11.5.1I

Batch/FPO Header

3294507

If you entered text for a production batch using the Edit Text option on the Batches,

The Edit Text icon displays appropriately on all these windows.

Component

Subcomponent


+ Batch Steps, or Batch Material Details windows, then the Edit Text icon did not display properly.


Batch/FPO Header

3406639

Batch release displayed an error when context-sensitive flexfields were used on the Batch window if these flexfields had different sets of attribute context values for plant codes.

Code was modifed so that the validation of current attribute values is done simultaneously with validation of global data elements. Six new procedures were created in the gme_api_grp package to validate the descriptive flexfields using server-side flexfield validation.


Inquiries 3440649

After batch reallocation, manual completion of transactions did not display the grade information. Phantom batch overallocations were not displayed properly on the Items Requiring Allocation window.

Code was modified so that after batch reallocation and manual completion all transactions, the grade is recorded appropriately for all completed transactions. Adjustments to the phantom batch material, such as scaling of a phantom ingredient, and appropriate product allocations are adjusted appropriately.


Reports 3161928

You were not able to set up a process loss of zero at the routing class level for various quantity ranges.

Code was modified to evaluate a process loss of zero by adding the NVL condition in get_process_loss.


Workbench

3022100

A batch scaled to a quantity of 10,000 displayed as 9999.999999999 on the Workbench.

Code was added to round off the planned quantity and the original quantity to 32 decimal places after scaling is performed in the procedure gme_api_create_batch.create_batch.

Component

Subcomponent



Workbench

3224143

In the SQLBIND-compliant project, some of the concatenation quotes were removed which resulted in the inability to expand Personal Shortcuts on the Process Execution Workbench.

Concatenation quotes that are required were restored so that you can expand Personal Shortcuts.

Other Issues

3425554

The Procedure - Close Batch (close_batch) API did not properly interpret resource reversals.

Code was modified to fetch the resource transactions properly in the close_batch API to correct the interpretation of resource reversals.

GMF-MAC

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

Component SubcomponentPatch Number Description Resolution


Batch/FPO Details

3303901 The Subledger Update process doe not pick up batch allocation from different companies.

Bug number: 3303901 All warehouses used in a batch must be owned by the 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 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 invoked from the Transaction Date field.

INQUIRY

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


Inquiries 3488630 The Batch Step Variance and Resource Variance related windows only display details for the last activity of an operation.

Code was modified so that the Batch Step Variance and Resource Variance related windows display details for all activities of an operation.

OTHER

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

Component

Subcomponent


Batch Issues

Batch Creation

3498508

(Port Bug 2729171 to 11.5.10L) Lot dates were not calculated properly. You were able to consume lots with a NULL expiration date. Dynamically created lots were assigned a date when they still had a status of Pending.

Code was modified so that the dates for the lot remain NULL until a completed transaction is 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 Issues

3638139

When you ran the gme_api_pub.insert_material_line API, you received the error: Cannot insert NULL into GME.GME_MATERIAL_DETAILS.ALLOC_IND. The alloc_ind was passed in as NULL.

Code was modified for the validate_field procedure of the gme_api_material_details package to check the

Component

Subcomponent


value of 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_details without any error.

REPORTS

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


Report Issues

3685721 When calculating accounting-related functions in the Batch Yield Variance Report and Material Usage and Substitution Variance Report, the item's secondary unit of measure was used when the primary unit of measure was not entered.

Batch Yield Variance Report: In the calculation of accounting-related functions, including actual cost, code was modified to convert quantities expressed the in the item's secondary unit of measure to its primary UOM 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 calculated in the primary UOM.

SCHEDULER

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


Scheduler Workbench

3503368 The Enable/Disable Schedule option on the Production Scheduler Workbench was not functioning properly due to a National Language Support (NLS) issue.

The NLS issue was resolved so that you can enable or disable the schedule on the Production Scheduler Workbench.

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.

New & Changed Feature in OPM

Documents

Transcript of New & Changed Feature in OPM