Professional Documents
Culture Documents
4.10.02 Release
Notes
This software was not developed for use in any nuclear, aviation, mass transit, medical
or other inherently dangerous applications. It is the customer’s responsibility to take all
appropriate measures to ensure the safe use of such applications if the programs are
used for such purposes.
The information in this document is subject to change without notice. If you find any
problems in the documentation, please report them to us in writing. Oracle Corporation does
not warrant that this document is error-free.
All other product or company names mentioned are used for identification purposes only and
may be trademarks of their respective owners.
Contents
Release Highlights 3
Overview ....................................................................................................................................3
Financials Modules Release Highlights......................................................................................3
Manufacturing Modules Release Highlights ..............................................................................4
Logistics Modules Release Highlights .......................................................................................4
Documentation Updates 21
Overview ................................................................................................................................. 21
Single-Level Cost Rollup ........................................................................................................ 21
Cost Rollup Process Status........................................................................................ 24
Overview
These resolutions to quality issues represent significant enhancements to
the overall quality of Oracle GEMMS. Highlights are listed by module.
Note that you can find a complete list of PCRs addressed in this release
under PCRs Addressed in 4.10.02 Release.
Overview
This section discusses the update scripts that have been included in the
4.10.02 Release. Scripts are discussed within module group (Financials,
Manufacturing, Logistics, System). Note that in addition to the
up41002.ora script (discussed next) the scripts glcstids.sql and
gldelacc.sql must be run separately; these scripts are described more
fully later in the discussion.
The system physically deletes all orphan account mappings for the SAL
account title. The above procedure needs to be repeated for ALL
companies.
Manufacturing Modules
Logistics Modules
System Module
Overview
These discussions relate to issues that will be addressed in upcoming
releases of Oracle GEMMS, but for which workarounds can be used in
the meantime. Oracle GEMMS configuration recommendations and
setup options (such as changes in System Constants settings) are also
discussed.
These discussions, along with any new implementation considerations,
will be included with each maintenance release. As the issues are
resolved, the discussions will be removed from the Implementation
Consideration topic, and the issue and resolution referenced in the PCRs
Addresses in This Release section.
GEMMS-Wide Considerations
Recommended Configuration
The following configuration for Oracle GEMMS for Windows (in
addition to the minimal system requirements) has been shown to
significantly improve system performance in a PC network environment.
We recommend you install Oracle GEMMS for Windows in this
configuration whenever performance in a network environment is a
concern:
♦ Client PC with an Intel Pentium 200 MHz processor (or greater)
♦ Client PC with 64 Mb of RAM (or greater)
♦ Install both the Oracle GEMMS for Windows Client
Workstation and File Server software on the client PC (this
configuration requires you to install any future File Server
software patches or upgrades on each client PC)
♦ Minimize the use of other PC applications while running
GEMMS
Financials Modules
Constants Value
GL$FINANCIAL_PACKAGE ORAFIN
GL$FINANCIAL_HOST_HOME APPL_TOP variable
GL$FINANCIAL_LOGIN_SCRIPT The name of the setup script e.g. APPLSYS.env
GL$FINANCIAL_HOST_MACHINE The name of the machine where the Oracle Financial code resides.
SY$GEMMS_HOST_MACHINE The name of the machine where the Oracle GEMMS code resides.
Constant Value/Description
OP$SEND_ZERO_TAX Send the zero tax amount to AR
GL$USE_GEMMS_REV_ACCT Use GEMMS revenue (SAL) accounts instead of AR autoaccounting
GL$TRANS_TYPE_MAP Use for building the transaction type during AR Update. This constant
can contain any combination of comma separated following values:
ORGN Shipping Organization
WHSE Order Line From Warehouse
CSTCLS SO Bill To Customer GL Class
SHPCLS SO Ship To Customer GL Class
ITMCLS Item GL Class
OP$ONE_TIME_SHIPTO Use One-time Ship-to functionality.
GL$USE_SHIP_UM Use shipment (order) UOM instead of Item's primary UOM for
invoicing.
GL$USE_SHIP_FOR_REV_MAP This is a new constant in Oracle GEMMS 4.1 and it is used to map
revenue account using Ship-to Cust/GL Class.
Document Sequences
If you are using document sequences and upgrading from Oracle
Financials 10.5 to 10.7, then you may receive an error message when
running Journal Import. You will receive error message EM17, if the
GEMMS journal categories are not manually assigned to a document
sequence.
To correct this occurrence, from the System Administrator Responsibility
(/Navigate Application Flexfield) disable the application_id and
category_code segments of the descriptive flexfield 'Document flexfield'
and then re-freezing the flexfield. Manually assign the document
sequences to the Oracle GEMMS Journal Categories. (PCR 510554)
Manufacturing Modules
Logistics Modules
System Module
Mei Files/Fastmenu
Fastmenus is a feature within ORACLE GEMMS that speeds up the login
process. It is implemented when setting up security of the user or user
group. Fastmenus is essentially a securely encoded, local menu file, so
that only the user’s security profile is loaded. If implemented, you must
recreate your fastmenus configuration whenever new menu features are
added.
To set up fast menus for a user, the Operator Code form needs to be
open(Object>System>System Security>Operator Code). From the
Operator Codes form enter the operator code or group operator code for
which you want to create the .mei file. From the Action menu, select
Create mei file. For more information, refer to the Oracle GEMMS
System Administration Guide.
Overview
The following discussions reflect anticipated updates to the Oracle
GEMMS User Guides, necessitated by the PCR resolutions included in
this release. These updates will be included in the next publication of the
Oracle GEMMS User Guides. In the meantime, you can make copies of
these pages and distribute them to appropriate users.
Higher Level
Product 2
Ingredient C Intermediate
Product 1
Level
Overview
The following issues have been resolved in the 4.10.02 Release of Oracle
GEMMS. Issues are listed by PCR number (ascending) within each
module.
510417
Issue:
End date of period finished at a time of 00:00:00 but should have finished
at a time of 23:59:59. Purchase Order receipts appear to have been
updated to an incorrect GL period. Purchase Order receipts received on
the last day of one period are updated to the GL Subledger in the
following period.
The period_end_date column in the gl_cldr_dtl table is updated
incorrectly. It is updated with the date of the last day at 00.00.00. If the
period started 01-JUN-97, the period_end_date of the previous period
may have been 31-MAY-97 23:59 instead it was 31-MAY-97 00:00:00.
As a result, May 31 was the first date of the June period.
Resolution:
The program has been corrected to solve this issue.
409548
Issue:
This problem occurred for a costing target warehouse that was marked for
purge. Subsequent display of that target warehouse record indicated that
the purge was not applied.
Resolution:
This PCR has been tested against 4.10.02, and it was determined that no
correction was required on this issue.
507869
Issue:
On the Allocation Definition form for a given allocation code, if there
was an item with no journal entry for an account, the allocation process
stopped.
Resolution:
The error that caused this problem has been corrected.
509612
Issue:
On the Cost Details form, after retrieving an existing cost detail, the
cursor disappeared.
Resolution:
Prior to this fix, the cursor was initially positioned in a non-display field
above the Item field. The program has been corrected to solve this issue.
509644
Issue:
When a cost calendar period was closed, start time stamps were changed
from 00:00:00 to 23:59:59.
Resolution:
The time stamp displayed incorrectly only after this specific sequence of
events occurred: 1) Period was closed; 2) Cursor was moved, and cursor
was on closed period when calendar was saved. When the cursor was
moved to the closed period, validation was turned off (this is where the
end date is set correctly). If the cursor was not moved after close of the
period, or was on a period that was not closed, the time stamp issue did
not occur. The code was changed to protect only from an entry and not
from a validation.
510287
Issue:
Cost Rollup should have an option to run a single item (calculate the
costs for only one level). The existing Cost Rollup runs for all items for a
given period and item (or item range). There should be an option for the
Cost Rollup to run on only one level for a Product Item without affecting
the costs for other products that may depend on the ingredients for the
Product Item.
Resolution:
An option is required to run the Cost Rollup for only one item
considering all the items in its formula and not rolling up the cost of the
ingredients even if they happen to be a product.
The queries and program have been modified to handle the single-level
rollup situation. For the product entered on the form, the effectivities and
material details are read, and the simple formula tree is generated and the
rest of the rollup continues as before. The single-level rollup now runs in
a fraction of the time required before.
510914
Issue:
An error caused the Cost Rollup to fail to complete on a specific machine
against a specific database.
Resolution:
A correction was made to the code to resolve the Cost Rollup issue.
510927
Issue:
When using one account key for the range on the Expense Alloc form, the
Actual Cost Process did not run.
Resolution:
When allocating expenses, the accounts are not recognized, when the
from_account and the to_account are the same. To fix this issue, the
max_length of several fields were increased so that there is no truncation
of value for the from_account, to_account or any related fields.
510928
Issue:
When the Amount field for a GL Account in the Allocation Detail Report
overflowed, the truncated data was added to the total. As a result, the
report was incorrect.
Resolution:
Formatted the column appropriately in the form, report, and the program
to report without any truncation.
510961
Issue:
Unable to add new source warehouse record (Object>Costing>Source
Warehouse). The following message was received "ERROR: Operator
expected, at line 930 in public JPL procedure: ‘1 <= num_occurs step1’.
Resolution:
The program has been corrected to solve this issue.
501332
Issue:
The Subledger Posting process did not prorate the journal voucher
quantity for component level booking. If the item cost consisted of
multiple components, each component booking to the Subledger stored
the total transaction quantity of the transactions. The GL Update for
these transactions summarized all the components. As a result, the
journal voucher quantity increased. The journal voucher quantity unit of
measure on the report was the multiple of the number of component
classes for that item and the quantity of that item shipped. For example,
if there was an inventory movement of 200 pounds for an item with three
cost component, then the journal entry was 600 pounds.
Resolution:
The program has been corrected to solve this issue.
501374
506497
506851
507657
Issue:
The Resource Usage and Substitution Variance used an actual step and
resource quantity for computation. As a result of this computation, there
was a possibility of batch close variance. The actual usage must have the
factor of step/resource quantity applied to it.
Resolution:
The program has been corrected to solve the following issues:
♦ Resource Usage and Substitution variances not calculated
properly (501374)
♦ Batch close sub-event must book the resource portion of Usage
and Yield variances separately (506497)
♦ Incorrect postings for Batch Close and Resource Substitution
variance (506851)
♦ Incorrect batch close variance when there is Yield or Usage
variance (507657)
510431
Issue:
When a Test Mapping Setup for sub-event STEP was performed, an error
message displayed indicating that the data for that subevent could not be
found. A subsequent run of the Test Subledger Update allowed the
correct accounts to be referenced for the subevent STEP.
Resolution:
A select statement was modified to select undeleted records only.
510873
Issue:
Error message not generated when the Subledger Posting program failed
due to non-existence of FM_YIELD_TYPE or standard unit of measures.
If FM_YIELD_TYPE was not defined or the standard UOM_TYPE
returned by sy_get_std_uoms was not valid, then the Subledger Posting
program did not generate an error message.
Resolution:
The Subledger Posting program was fixed to display an error message
when failure occurs. A script has been included in the up41002.ora
consolidated script to add this resolution.
411240
Issue:
On the Invoice History drilldown, total purchase order amount was
calculated incorrectly if there were acquisition costs on the purchase
order.
Resolution:
The acquisition costs were not multiplied by the PO Line Quantity before
being added in (they were added in as entered on the PO Acquisition
Costs form). The calculation was corrected to multiply the sum of all
acquisition costs by the PO Line quantity, then add the extended price for
each line ( Qty “times” Unit Price ).
502205
Issue:
The Organization selection criteria on the AP Update form did not
properly restrict the update to the specified organization (all
organizations with activity were updated).
Resolution:
Selecting Accept by using <Arrow> keys caused certain fields not to be
validated. A field exit function was added for the 4 fields on the selection
form to insure validation.
505886
Issue:
This problem occurred on a credit memo inventory adjustment query
(Inventory>Transaction Inquiry>Transaction Details). The document
number for the inventory adjustment should have been the credit memo
number (for auditing purposes). However, what displayed on the
Transaction Inquiry form was just an ID number (the debit memo ID
from Oracle Accounts Receivable was not displayed by Oracle
GEMMS).
Resolution:
If the adjustment was created by an Oracle AR memo, the memo ID now
displays as the document ID on the Transaction Inquiry.
510439
Issue:
While performing an Accounts Receivable synchronization, the update
was halted by a sales order with a line quantity of zero.
Resolution:
The error that caused this problem has been corrected.
510463
Issue:
While running the PO import, the user encountered an error message
indicating “Buffer overflow, limit of 1000000 bytes in the po_val_drv
module”.
Resolution:
A statement in the poval.sql file was modified to correct this problem.
510660
Issue:
If you entered a credit limit in one currency and the order was entered in
another, the credit function did not convert from one currency to another.
Resolution:
Exchange rates were not picked up by the credit checking. Modified the
PL/SQLs to take care of the exchange rates.
510784
Issue:
For the GL to OP Drill Down, Sales Order Id was displayed in the Sales
Ordr # column.
Resolution:
Modified the program to display the order no. value in the field for
shipments.
510821
Issue:
A database error message displayed when an AP update was run for a
company for which no fiscal policy was defined.
Resolution:
If no fiscal policy was defined for the company for which the AP update
is being run, the message "Fiscal policy not defined" now displays to
indicate that there is no data to update.
510836
Issue:
When the user selected Locate Customer, then selected All, the display
included all customers regardless of the current organization or company.
The user felt that the list should be limited to customers of the current
company for multi-organization, and blank company for non-multi org
setup.
Resolution:
This PCR has been tested against 4.10.02. It was determined that the
software functions as per design, and no correction was required on this
issue.
502142
Issue:
Component classes displayed more than once when the user used the
lookup on the Cmpnt Class field on the Resource form (Note: this was
also a System problem).
Resolution:
The code was corrected so that Component Classes display correctly on
that lookup.
508693
Issue:
On the Inventory Items form, the wild card lookup on the item
description did not permit lower-case characters. Item descriptions
should be allowed to be composed of upper- and lower- case letters.
Resolution:
The code was modified to permit the item description to support upper-
and lower- case characters.
508831
Issue:
On the Item Inquiry form, an error message displayed if a batch was open
that contained the item being queried ("No change variable has been
specified for the array 1 fields").
Resolution:
Program code that was changed in an earlier patch release caused the
error. This code was corrected.
411675
Issue:
The MPS Material Activity Report and MPS Bucketed Material Activity
Rpt both had limitations of 9999 items.
Resolution:
A select process was modified so that any number of items could be
included in the following reports: MPS Material Activity report, MPS
Bucketed Material Activity report, MPR Material Activity report.
508903
Issue:
A resolution to an earlier PCR caused a subsequent problem to occur with
MRP error messages. Certain messages appear on the hardcopy Error
Message report, but are not displayed on the Error Messages inquiry.
Resolution:
A “join” statement was corrected to resolve this problem.
508684
Issue:
This problem occurred on the Subledger Update when the Actual Usage
hours entered on the Batch Step Detail form (POC>Batch
Steps>Edit>Batch Step Dtl) were less than the planned hours. The
difference between the Actual and Planned hours was added to the
Planned Usage, which is the value the Subledger Update uses for
Actual Usage.
Resolution:
Logic was changed in the C code, and a delete mark check in inserted in
the JPL to resolve this issue.
504242
Issue:
On the Batches form lookup for the Batch field, GEMMS did not select
the desired batch record when the user highlighted the line and pressed
<Enter>. The cursor skipped to the next field on the lookup line instead
of returning to the Batch form; the <Continue> option was required to
retrieve the selected batch.
Resolution:
In order to mimic the behavior of standard lookup forms, the <New
Line> key was mapped to the transmit functionality. Users can now
select data from the lookup form by either pressing the <Do> key (as
before) or using the <Enter> key as with other lookup forms.
510032
Issue:
A general protection fault situation occurred in GEMMS while the user
was creating a firm-planned order (FPO) with byproducts
(Production>FPO>Ingredients>Edit>By Products).
Resolution:
This situation only occurred when the FPO had more than 2 byproducts.
It was determined that a jam/jpl array problem caused this issue, which
has been resolved. Code was also added so that the form mode would
display on the screen.
510936
Issue:
An error message displayed when the user unreleased
(Obj>Prod>Batch>Action>Unrelease) a “Pending” batch with partial
certification allocations. Subsequent display of the batch record
indicated that the previous allocations had been corrupted on the
Input/Output forms.
Resolution:
This problem was related to changes made for phantom functionality in
the 4.1 Release. The code was checking for unallocated items because
the batch was in “WIP” status. This was valid except in the case of
unreleasing a batch; the batch status was still “WIP” during unrelease, so
the check was made. The code has been changed so that the unallocated
check is not performed during unrelease of a batch.
510475
Issue:
A performance issue existed on the QC Product Results form. An
inordinate length of time was required to retrieve a record after the user
specified a sample number.
Resolution:
The number of calls to the master table for QC specifications was
excessive, causing time delays with data retrieval. The code was
modified to reduce the time required to retrieve specified records.
506304
Issue:
On the Line Detail form for an existing purchase order, changes made to
the line’s receiving location were not saved properly.
Resolution:
This PCR has been tested against 4.10.02, and the issue, as stated, cannot
be reproduced at Oracle. If an issue still exists, contact Level 1 support
with additional details.
507146
508861
Issue:
GEMMS did not handle user fields correctly when associated with the
Receipt Detail table. Mandatory entries were ignored, lookups showed
entries associated with the Receipt Header table (validation was also to
the Header table) and the values were not saved. All of these problems
occurred in Quick Receiving, and some of them appeared in PO
Receiving and Stock Receipts.
Resolution:
The SQL script P508861.sdt corrects these user field problems. After it
has been run, you must recreate the mei files for the correction to take
effect.
507738
Issue:
An existing generic item (one which did not have a vendor assigned to it)
did not appear on the lookup for the PO Lines and Generic Items forms.
The lookup included the item only when the Vendor field had an entry
on the Generic Items form.
Resolution:
A problem in the generic item lookup syntax caused this error, which has
been corrected.
508456
Issue:
This problem occurred on the Account Distribution form during entry of
acquisition costs for a purchase order line item. The user received the
message “ERROR: math error - Bad field # or subscript” on an attempt
to save.
Resolution:
In the code, a set of quotes (“) was missing at the end of a call. Quotes
have been entered for this call, eliminating the problem.
508733
Issue:
This was a request for the UOM field lookup to be available on the PO
Entry form (in the same manner as is available for the field on the PO
Lines form).
Resolution:
The field properties were changed for the UOM field on the PO Entry
form, making the UOM field lookup available.
508849
Issue:
This error occurred after the user entered a date (in “Add” mode) in the
Sched to Ship field on the PO Header form. GEMMS did not
successfully delete the date on a subsequent attempt by the user to delete
the date and do a Save in “Update” mode.
Resolution:
There were 2 dates involved here, one in user format and one in database
format. When the user cleared a previously-entered date, there was no
code to also clear the database format field. This code has been added to
correct the problem.
508968
Issue:
On the BPO Warehouse Allocation form the user was able to save a non-
existent warehouse by using the <Arrow> key to advance past the
Warehouse field without any validation.
Resolution:
A protection call existed which saved some entries from being validated
before the form validation was requested. This call was eliminated from
the list of protects, resolving the issue.
509058
Issue:
The Sublot field on the Quick Receipt form allowed only 10 characters,
resulting in truncation if the sublot number was more than 10 characters.
This prevented allocation to the existing sublot.
Resolution:
The Sublot field on the Quick Receipt form is now scrollable, such as the
Lot field.
509222
Issue:
This problem occurred on the Contract Information Inquiry form
(Purchasing>BPO Item Status>View>Contract Info). The form
incorrectly displayed the Start Date as the current GEMMS system date
for all lines except the first line (rather than the actual start date that the
user specified).
Resolution:
The problem originated in the POISBVW1.jam form before the user
accessed the Contract Information form (POBISVW5). The contract start
date and end date were transferred across from the VW1 form to the
VW5 form. However, the dates were not synchronized with the other
array elements, so only the first element was correct (the rest defaulted to
the system date). Since there was insufficient room on the form to add
these two fields, the size of the form has been increased from 80 to 82
characters to accommodate them both.
509910
Issue:
On the Purchase Order Line Items form, the Line Status field was not
refreshed properly when the Next Line and Previous Line options were
selected from the Edit menu.
Resolution:
The error that caused this problem has been resolved.
510558
Issue:
This problem occurred on the Quick Receipts form for receipt of an item
controlled by lots and status. When the user used the <F6> key to delete
the line during entry of the second receipt, that line disappeared.
Resolution:
The <F6> key mapping to for deletion of a line was not equivalent to the
Delete Lot Line function from the Edit menu.
510619
Issue:
GEMMS did not permit the save of a purchase order with 49 completed
line items when the cursor was positioned on the 50th (empty) line.
Resolution:
After the warning message indicates that you have entered the maximum
number of lines on the order, position move the cursor back up one line
(to line 49 in this case, the last completed line). The save function works
properly under this scenario.
500881
Issue:
When the user copied a sales order the tax amount for each line was
copied, but the tax details were not.
Resolution:
This function has been rewritten in the Oracle GEMMS 4.0 and 4.1 Order
Fulfillment module. The function now (Release 4.10.02) works properly
to copy sales order line taxes along with sales order lines.
507435
Issue:
This problem occurred during entry of shipment transactions
(Sales>Shipping>Edit>Shipping Lines>Edit>Transactions) to allocate
dual uom type 2 items ordered in the secondary unit of measure. On the
Transaction form there was no way to enter both the primary and
secondary unit of measure quantities (the Pick Lots and Transaction
Additional Edit forms were required). Use of the Transactions form only
seemed to work for this scenario if the order was in the primary unit of
measure.
Resolution:
This PCR has been tested against 4.10.02, and the issue, as stated, cannot
be reproduced at Oracle. If an issue still exists, contact Level 1 support
with additional details.
508687
Issue:
After an allocated shipment was canceled, GEMMS would not permit
cancellation of the original sales order (GEMMS indicated that the
canceled order had been shipped).
Resolution:
JPL and JAM file code was modified to check for cancellation data
correctly.
508901
Issue:
Inventory was not decremented properly for an indivisible dual uom3
item as a result of allocation in Pick Lots (Sales>Sales Order>>Edit>Pick
Lots). Only the inventory in the primary unit of measure was
decremented.
Resolution:
Code was added recently specific to items of type uom 3. This code did
not take into consideration items which are lot-indivisible. A clause was
added to some “if” statements that ignores this new code if the item is lot-
indivisible.
509098
Issue:
GEMMS did not correctly auto-allocate an item controlled by dual units
(type 2 or 3) when the Lot Indivisible flag for the item was set to “Yes”.
When the allocation was done manually and the user overrode the
defaults, GEMMS inserted erroneous quantities for the secondary units of
measure.
Resolution:
Code was added to stop unit of measure conversions using the default
conversion ratio, to properly mark lines allocated, and to properly update
the transactions in the Inventory Pending Transactions table.
509282
Issue:
On the Shipping Line Details form, a change made to the Warehouse
field was not updated and displayed on Transaction Inquiry form.
Resolution:
Transactions can be keyed on both bill of lading ID and order ID.
However, the code used the bill of lading ID only. There are now 2
attempts at deleting existing transactions based on the relevant bill of
lading and line IDs when a warehouse value has been changed.
509805
Issue:
If the user modified the order unit of measure after a shipment had been
created, then canceled, subsequent invoices were wrong.
Resolution:
Lot allocation failed to locate the correct document ID when invoked
from the sales order once backorder lines existed. The flag
“suppress_backorders” was added, which eliminates the problem.
510160
Issue:
In Order Entry, the user encountered an error message (sy_quiet_err no
msg_name) on an attempt to enter the 55th line of a sales order. This,
however, did not prevent the user from continuing with order entry.
Resolution:
The message indicates a problem with memory allocation, a problem that
has been resolved. However, if this message does display, users should
not continue to enter lines (your system has run out of resources). Delete
the current line, then close any other windows not being used and try to
proceed again. If the message displays again, delete the current line and
save the order; the limit has been exceeded.
510349
Issue:
When the Locate Customer option was used to select a customer, the
subsequent Billing view that appeared displayed a title bar with a status
of “Deleted” instead of “View”.
Resolution:
The heading of the Billing/Other form has been modified with the correct
opening status.
510351
Issue:
In Order Fulfillment, the Per Unit field on the Order Entry Charges View
appeared (incorrectly) in lowercase.
Resolution:
The field now displays correctly as Per Unit.
510391
Issue:
For the Locate Order option, display of the Minimum and Maximum Ship
% should show a default of “100” percent. However, the percentages
displayed as “1.00”.
Resolution:
The display is now consistent with the entry made in Customer Items
(100%, not 1%).
510551
Issue:
This problem occurred after a user opened a sales order. After the user
added line text, the cursor advanced to the Item Description, and the
message "Entry Required" displayed.
Resolution:
This situation occurred because the user could save an order that had no
terms code for the line. After opening the order and navigating to the
details, if Save is selected the line is validated (resulting in a "code not
found" message for the blank Terms Code field). For this type of error
GEMMS tries to position the cursor in the field in error, but Terms Code
was protected because the Terms Vary flag was disabled (causing the
cursor to be placed in the Description field).
The problem, caused by saving an order without a valid terms code, has
been corrected.
510668
Issue:
The Customer Number field on some forms (for example, Sales Order,
Profile, and Customer Maintenance) was not long enough, and the
underscore (_) character did not display in customer numbers. Problems
also occurred on some inquiries, lookups, and reports.
Resolution:
All forms which include the Customer Number or Item Number field
have been modified to eliminate these problems.
510743
Issue:
GEMMS permitted a credit hold reason on a sales order line to be
modified and saved, even though credit checking was established and the
order had already triggered a hold for credit checking.
Resolution:
In this situation, GEMMS now prevents the save of an order line if the
reason code has been changed from a credit hold reason to another
reason.
510769
Issue:
This was a request for the Last Edited tracking on the Order Entry forms
to be supported for “scratch” orders in the same manner as that used for
regular sales orders.
Resolution:
Additional tests were added to the code to distinguish new lines from
loaded lines on “scratch” orders.
510790
Issue:
During setup of order types (Order Fulfillment>Setup>Order Type) an
error message displayed intermittently when records were opened for
update.
Resolution:
This PCR has been tested against 4.10.02, and the issue, as stated, cannot
be reproduced at Oracle. The 4.10.02 Release includes a new executable
for this function which eliminates the problem. If an issue still exists,
contact Level 1 support with additional details.
510791
Issue:
In Order Entry, GEMMS inappropriately protected the Calculate
pushbutton during inquiry on a shipped order (the Calculate pushbutton
was “grayed out”). This was a request to make the Calculations available
for inquiry.
Resolution:
The Calculation pushbutton selection is now available for view of total
order amount, weight, and volume.
510798
Issue:
In Order Fulfillment, the Packaged Item form could not be minimized.
Resolution:
The Packaged Item form has been modified so that it can be minimized.
510806
Issue:
This problem occurred during an attempt to create a new profile. When
the user entered the first line's quantity and exited that field, an error
message displayed and the user was unable to continue. The user
subsequently had to exit the Order Fulfillment session and start a new
one in order to successfully enter a new profile.
Resolution:
This PCR has been tested against 4.10.02, and the issue, as stated, cannot
be reproduced at Oracle. The 4.10.02 Release includes a new executable
for this function which eliminates the problem. If an issue still exists,
contact Level 1 support with additional details.
510808
Issue:
When a new order was created by copying an existing one, the Order
Type from the original order was not retrieved properly for the new
order.
Resolution:
A language code was missing when information was retrieved from the
Order Type table. The language code has been added to the SQL
statement, eliminating the problem.
510814
Issue:
During order entry the user entered a manual price override.
Subsequently, each time the user returned to the Pricing view the
calculations for the Net Price and Extended Price fields displayed
increased values.
Resolution:
The Manual Pricing dialog box should have displayed the order unit of
measure rather than the pricing unit. The dialog box now correctly
displays the order unit of measure.
510875
Issue:
This problem occurred after the Locate Order function was used to
retrieve an order. When the user changed lines using the arrow in the
upper-right of the Order Entry form, the Min and Max Ship %
information did not display correctly.
Resolution:
The minimum and maximum ship percentage information were not
implemented correctly into the Order Detail table. Code was added to
correctly retrieve the customer item information.
510907
Issue:
The user entered a new sales order, specifying (on the Header) the ship
customer number. However, on the Line Items form, the customer
number was truncated after 11 characters. This caused GEMMS to
interpret the customer as invalid.
Resolution:
The length of the Customer Number widget was increased on the Sales
Order form, eliminating the problem.
510944
Issue:
This problem occurred on the Picklots form. After deletion of
established lines, the displayed lines indicated a mixture of field data
from the remaining lines and the deleted lines. Also, the line allocated
values did not reflect the deletions.
Resolution:
The problem was caused by extraneous field data that remained after the
delete line function was performed. This data is now cleared, eliminating
the problem.
507367
Issue:
On an attempt to run the Tax Period Report with no restricting criteria,
the message “Report Writer terminating abnormally”. GEMMS then
redisplayed the Tax Authority form with the message “Creating report...”
displayed at the bottom.
Resolution:
The Tax Period Report now generates without displaying the termination
message.
507633
Issue:
An error situation occurred on an attempt to generate the Shipping
Picklist report (Sales>Shipping>Reports>Shipping Picklist) which
prevented the user from performing further processing in the session.
Resolution:
RPT and BINARY files were missing from the release area. Both of
these files have been added, correcting the problem.
507666
Issue:
When reports were displayed online, the entire width of the report did not
appear on the screen. Users needed to use <Cursor> keys to scroll to the
right and display the rest of the report. This was a request for the entire
report to display, without the need to scroll across to display the
remaining columns.
Resolution:
The JAM window that was used to display reports was too small, and
offered no options for changing or resizing fonts. The code has been
changed to execute Notepad.exe on all Windows platforms when the
screen is specified as the print device. This allows the user to resize the
window within Notepad, and change the font of the text. (Note that the
Notepad report file is a temporary file, and modifications made in
Notepad will not be retained).
508294
Issue:
GEMMS did not handle user fields correctly when associated with the
Receipt Detail table. Mandatory entries were ignored, lookups showed
entries associated with the Receipt Header table (validation was also to
the Header table) and the values were not saved. All of these problems
occurred in Quick Receiving, and some of them appeared in PO
Receiving and Stock Receipts.
Resolution:
The SQL script P508861.sdt corrects these user field problems. After it
has been run, you must recreate the mei files for the correction to take
effect.
510816
Issue:
The user was unable to establish a text token. Also, when the user tried
to enter text directly into a shipment (in shipping) the "working"
displayed at the bottom of the form, but update of the entered message
never appeared to complete.
Resolution:
Long values were being passed as return values from the JPL functions.
In 16-bit Windows, all returns are short integers; once the value exceeded
32K, the value lost all meaning. This situation has been corrected.
510935
Issue:
This was a request for the addition of Polish (POL) and Russian (RUS)
language codes for Oracle GEMMS.
Resolution:
The script P510935.ora, which creates the Polish and Russian language
codes, has been consolidated into the script up41002.ora which must be
run with the 4.10.02 Release.