41002

Oracle® GEMMS®
4.10.02 Release
Notes
Part No. A57502-01

Oracle® GEMMS® 4.10.02 Release Notes
Part No. A57502-01
Copyright © Oracle Corporation 1997
All rights reserved. Printed in the U.S.A.
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.
This software/documentation contains proprietary information of Oracle Corporation; it is

provided under a license agreement containing restrictions on use and disclosure and is also
protected by copyright law. Reverse engineering of the software is prohibited.
If this software/documentation is delivered to a U.S. Government Agency of the Department

of Defense, then it is delivered with Restricted Rights and the following legend is applicable:
Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to

restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, Rights in
Technical Data and Computer Software (October 1988).
Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065
If this software/documentation is delivered to a U.S. Government Agency not within the

Department of Defense, then it is delivered with “Restricted Rights,” as defined in
FAR 52.227-14, Rights in Data - General, including Alternate III (June 1987).
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.
ORACLE and GEMMS are registered trademarks of Oracle Corporation.
All other product or company names mentioned are used for identification purposes only and
may be trademarks of their respective owners.
Contents
GEMMS Maintenance Release 4.10.02 1

What is Release 4.10.02? ....................................................................................................... ....1
Cumulative Changes to 4.1 Release on Tape .............................................................................1
Format of 4.10.02 Release Notes ...............................................................................................2
Release Highlights 3
Overview ....................................................................................................................................3
Financials Modules Release Highlights......................................................................................3
Manufacturing Modules Release Highlights ..............................................................................4
Logistics Modules Release Highlights .......................................................................................4
Database Update Scripts 5

Overview ....................................................................................................................................5
Scripts Consolidated Into the 4.10.02 Release ...........................................................................5
Financial Modules Scripts ..........................................................................................................6
Credit Limits and Currencies (PCR 510660) ...............................................................6
Subledger PM POC Bookings Changes (PCR 501374) ...............................................6
Single Level Cost Rollup Changes (PCR 510287).......................................................7
Tax Authority Removed as a Selection Priority for the SAL Account Title (PCR
510341) ........................................................................................................................8
No Error Message When Subledger Post Fails (PCR 510873) ....................................9
Manufacturing Modules .............................................................................................................9
Cost Component Class Display (PCR 504142)............................................................9
Logistics Modules ......................................................................................................................9
Disabling of Vendor Associations (PCR 508768) .......................................................9
Warning Message for Maximum Quick Receipt Lots (PCR 508974)..........................9
Message for Exceeding Order Fulfillment Memory Limit (PCR 510160)...................9
Messages for Exceeding Length of Province and County Fields (PCR 510963) .....10
System Module.........................................................................................................................10
Polish, Russian Language Codes Added (PCR 510935)............................................10
Oracle GEMMS 4.10.02 Release Notes Contents • i

Implementation Considerations 11
Overview ................................................................................................................................. 11
GEMMS-Wide Considerations................................................................................................ 11
Recommended Configuration.................................................................................... 11
Address Enhancement for Order Fulfillment............................................................. 12
Financials Modules.................................................................................................................. 12
Single Login From Oracle GEMMS to Oracle Financials ........................................ 12
AP Update................................................................................................................. 13
AR Update ................................................................................................................ 14
Customer Synchronization ........................................................................................ 15
Document Sequences ................................................................................................ 15
Multiple-Organization Installation ............................................................................ 16
Manufacturing Accounting Controller Setup Requirements...................................... 16
Geography Code Synchronization Between Oracle GEMMS and Oracle Financials 17
Statements Resolve Customer Form Label Issue....................................................... 17
Manufacturing Modules .......................................................................................................... 17
New Formula Management Release Type Switch (PCR 410090)............................. 17
Partial Certification Release Types (PCR 511040) ................................................... 18
Inventory Quantities Document Ordering Setup ....................................................... 18
Logistics Modules ................................................................................................................... 18
Error Message When GL Accounts Are Not Defined ............................................... 18
Proforma Invoice Print.............................................................................................. 18
Ship Tolerance and Automatic Close ........................................................................ 19
System Module........................................................................................................................ 19
Mei Files/Fastmenu ................................................................................................... 19
Security by Operator Groups..................................................................................... 19
Applying Security to System Constants .................................................................... 20
Purge & Archive Documentation Warning ............................................................... 20
Invalid Document Type Error Message .................................................................... 20
Inventory Journal Transactions - Document Ordering .............................................. 20
Documentation Updates 21
Overview ................................................................................................................................. 21
Single-Level Cost Rollup ........................................................................................................ 21
Cost Rollup Process Status........................................................................................ 24
ii • Contents Oracle GEMMS 4.10.02 Release Notes

PCRs Addressed in 4.10.02 Release 25
Overview ..................................................................................................................................25
Accounting Setup PCR Resolutions .........................................................................................25
Cost Management PCR Resolutions.........................................................................................26
Manufacturing Accounting Controller PCR Resolutions .........................................................29
Oracle GEMMS and Oracle Financials Integration PCR Resolutions......................................31
Capacity Requirements Planning PCR Resolutions..................................................................35
Inventory Management PCR Resolutions.................................................................................35
Material Requirements Planning PCR Resolutions ..................................................................36
Process Operations Control PCR Resolutions..........................................................................36
Production Management PCR Resolutions ..............................................................................37
Quality Management PCR Resolutions ....................................................................................38
Purchasing PCR Resolutions....................................................................................................38
Sales Management/Order Fulfillment PCR Resolutions...........................................................43
Tax Module PCR Resolutions..................................................................................................53
System Module PCR Resolutions.............................................................................................54
Oracle GEMMS 4.10.02 Release Notes Contents • iii

iv • Contents Oracle GEMMS 4.10.02 Release Notes
GEMMS Maintenance Release
4.10.02
What is Release 4.10.02?

Oracle GEMMS Release 4.10.02 represents the first port of the 4.1
Release on IBM AIX, Sun Solaris, Windows 95, and Windows NT 3.51
platforms. It also includes an enhancement to Cost Rollup functionality,
as well as resolutions to quality issues from Oracle GEMMS users.
Cumulative Changes to 4.1 Release on Tape

The 4.10.02 version of GEMMS is included on the enclosed maintenance
tape. Note that this tape includes the cumulative changes to GEMMS
since the 4.1 Release; review the "Readme" file on the tape for further
details.
A copy of this report is included with each maintenance tape. It lists the
PCRs resolved within each individual release; PCRs are listed
sequentially, by module. With each maintenance release, a new list of
resolved PCRs will be added to the report to produce a running record of
all PCRs resolved since the 4.1 Release.
Oracle GEMMS 4.10.02 Release Notes GEMMS Maintenance Release 4.10.02 • 1

Format of 4.10.02 Release Notes
The Release Notes include the following topics:
♦ Release Highlights - A list of selected PCR issues closed in this
release, with resolutions that we feel significantly enhance the
quality of Oracle GEMMS
− You will find a complete list of closed PCRs, issues and
resolutions, in the PCRs Addressed in 4.10.02 Release
section
♦ Database Update Scripts - A list of the database scripts included
in the release, with an explanation of how each script resolves
the particular issue
♦ Implementation Considerations - Discussions that reference
current workarounds, as well as upcoming fixes
2 • GEMMS Maintenance Release 4.10.02 Oracle GEMMS 4.10.02 Release Notes

Release Highlights
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.
Financials Modules Release Highlights

♦ Issues With Resource Use/Substitution Variance Have Been
Corrected (PCRs 501374, 506497, 506851, 507657)
♦ Subledger Posting Now Prorates Journal Quantities for
Component-Level Booking (PCR 501332)
♦ Single-Level Cost Rollup Feature Added (PCR 510287)
♦ GEMMS now calculates current period costs (using PMAC
averaging) taking previous period costs into account (PCR
509846)
♦ The Cost Rollup process was optimized to greatly reduce the
time required to queue and process the rollup (PCR 510155)
♦ A field overflow situation that caused inaccuracies in the
Allocation Detail report has been resolved (PCR 510928)
♦ You can now specify a single account key on the Expense
Allocation form when allocating expenses (PCR 510927)
♦ A situation that produced an error message during generation of
the GL Expense Allocation Definition report has been resolved
(PCR 510926)
♦ On the Allocation Definition form for an allocation code, the
allocation process no longer stops for an item with no journal
entry for an account (PCR 507869)
♦ Credit checking now converts a credit limit entered in one
currency to the currency of the order (PCR 510660)
♦ GL Update performance was improved by the addition of
indices to some of the update queries (PCR 510437)
♦ Code was modified to correct unit price rounding errors on
invoiced orders resulting from the AR synchronization (PCR
508572)
Oracle GEMMS 4.10.02 Release Notes Release Highlights • 3

Manufacturing Modules Release Highlights
♦ An issue was resolved on the Subledger Update, when the
Actual Usage hours entered on the Batch Step Detail form were
less than the planned hours (PCR 508684)
Logistics Modules Release Highlights

♦ The GEMMS vendor association is now removed when a vendor
site is made inactive in Oracle Financials (PCR508768)
♦ Last edited functionality is now supported for scratch orders
(PCR 510769)
♦ The functionality for copying sales orders was enhanced (PCRs
510808, 500881)
4 • Release Highlights Oracle GEMMS 4.10.02 Release Notes

Database Update Scripts
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.
Scripts Consolidated Into the 4.10.02 Release

The following scripts have been consolidated into the script
up41002.ora, and must be run with the 4.10.02 Release. A description
of each script is included in this section. Please refer to the 4.10.02
Installation Instructions for run procedures.
P501374.sdt
P502142.sdt
P508768.sdt
P508861.sdt
P508974.sdt
P510160.sdt
P510287.sdt
P510873.sdt
P510963.sdt
P501374i.ora
P510287s.ora
P510341a.ora
P510935.ora
P510988.ora
Oracle GEMMS 4.10.02 Release Notes Database Update Scripts • 5

Financial Modules Scripts
Credit Limits and Currencies (PCR 510660)

glcstids.sql
The glcstids.sql script updates customer records in the op_cust_mst table
in Oracle GEMMS with various tables from Oracle Financials. See the
4.10.02 Installation Instructions for the procedures to run a .sql script.
This script is required when upgrading from version 3.21.xx to 4.10.02
or from 3.21.xx to 4.10.00 or 4.10.01. If you are upgrading from 3.21.xx
to 4.10.02 directly, ensure that fiscal policies are set up and that the
Oracle GEMMS data migration scripts 3.21 to 4.10 (glcstupg.sql,
glvndupg.sql, glslsupg.sql) have been executed.
If you have a fresh installation of 4.10.00 or a later patch (i.e., you
have never migrated any data from 3.21 databases), do not run this
script.
Following is the mapping of columns:
Column in Oracle GEMMS Column in Oracle Financials

Table_Name.Column_Name
of_cust_id ra_customers.customer_id
of_ship_to_address_id ra_addresses_all.address_id
of_ship_to_site_use_id ra_site_uses_all.site_use_id
of_bill_to_address_id ra_addresses_all.address_id
of_bill_to_site_use_id ra_site_uses_all.site_use_id
Subledger PM POC Bookings Changes (PCR

501374)
sdt file: P501374.sdt
This script includes a message in the sy_mesg_tbl (message_code
GLUPD_POC_BATCHES_LOAD_FAILED). The message "Unable to
load batch numbers for POC batches. Contact system admin" is
displayed. A new query was introduced in the Subledger Update process
to determine the POC batches while booking the Batch Close Sub-Event
(CLOS). If the query fails, then this message is written to the Subledger
Errors file which can be viewed in the Subledger Update Error Messages
form.
6 • Database Update Scripts Oracle GEMMS 4.10.02 Release Notes

ora file: P501374i.ora
This script inserts a row into the gl_sevt_ttl table. This includes the
account title Resource Control Account (RCA) into the sub-event -
account title setups for the Batch Close Sub-event (CLOS). The default
options for this account title is to include quantities on a Journal Voucher
and to use Whse Organization for mapping.
Single Level Cost Rollup Changes (PCR 510287)

sdt file: P510287.sdt
This script introduces label and messages for the Single Level Cost
Rollup option. Following are the details:
Label SNG_LVL_RLP$L with Text (English - "Single Level:") included
in the sy_labl_tbl table. The text for this label appears in the Cost Rollup
Startup dialog box and Process Status form.
♦ Error messages are inserted in the sy_mesg_tbl table. These
error message codes are used to generate detailed error messages
when the Cost Rollup fails to complete. The error messages can
be viewed in the Rollup Error messages form
♦ Message code CM_RL_FMEFF_FAIL (ENGLISH "Unable to
load Formula Effectivities. Contact System Admin.") indicates
that the Single Level Rollup failed because it could not load the
formula effectivities due to database or other errors
♦ Message code CM_RL_MATL_DTL_FAIL (ENGLISH
"Unable to load Formula Material Details. Contact System
Admin.") is generated when formula material details cannot be
loaded due to database or other errors
♦ Message code CM_RL_NO_MATL_DTL (ENGLISH - "Cannot
find material details for the formula. Process aborted.") is
generated when the Cost Rollup process cannot find the relevant
material (ingredient) details. The Single Level Cost Rollup will
terminate if it cannot find the ingredients for the formula used in
producing the item for which the Cost Rollup is being run
♦ Message code CM_RL_NO_PROD_ITEM (ENGLISH -
"Rollup Item is not defined as a product in Formula Material
details.") is generated if the Single Level Cost Rollup item is not
defined as a product in the Formula Material details
♦ Message code CM_RL_CIRC_REF (ENGLISH - "Rollup Item
cannot be a product as well as ingredient in the Formula.") is
generated when the Cost Rollup detects a Circular Reference in
the formula (the same item is defined as a product as well as an
ingredient). Single level cost rollup cannot resolve the
relationship under such conditions. The Cost Rollup process
will terminate

ora file: P510287s.ora
This script adds two new columns to the cost rollup control table
(cm_rlup_ctl):
♦ single_level indicates whether the rollup being run is a Single
Level Rollup
♦ item_id holds the item_id of the item if a single level rollup is
run, 0 (zero) otherwise
Tax Authority Removed as a Selection Priority for

the SAL Account Title (PCR 510341)
Two scripts are provided for PCR 510341. Following are the details:
P510341a.ora
Does not allow you to enter tax authority as a selection priority for the
SAL account title. This script needs to be in upgrade script.
gldelacc.sql
See the 4.10.02 Installation Instructions for the procedures to run a .sql
script.
Deletes duplicate account mappings from the database for the SAL
account title. Run this script only if duplicate account mappings for the
SAL account title are to be deleted. Running this script is one method for
deleting duplicate account mappings for the SAL account title.
Following is an additional method:
From the Acct Sel Prior form, retrieve record for SAL account title.
Choose Save from the Edit menu.
If the company has a duplicate account mappings, then the following
prompts are displayed:
(013161) Acct mappings will be invalid due to new sel priority.
Delete them (Y/N)? Enter Y
(013181) Physically delete all 2 invalid account mappings (Y/N)?
Enter Y
(013184) Are you sure you want to delete ALL invalid account
mappings (Y/N) ? Enter Y
The system physically deletes all orphan account mappings for the SAL
account title. The above procedure needs to be repeated for ALL
companies.

No Error Message When Subledger Post Fails (PCR
510873)
P510873.sdt
The Subledger Posting program was modified to display an error message
when failure occurs. The P510873.sdt script has been included in the
up41002.ora script to add this resolution.
Manufacturing Modules
Cost Component Class Display (PCR 504142)

P502142.sdt
Alters the lookup for cost component classes so they will not display
more than once.
Logistics Modules
Disabling of Vendor Associations (PCR 508768)

P508768.sdt
Removes GEMMS vendor association when a vendor site is made
inactive in Oracle Financials.
User Field Validation in Receipt Programs (PCR

508861)
P508861.sdt
Adds object for user-defined fields entry for Quick Receiving
Warning Message for Maximum Quick Receipt Lots

(PCR 508974)
P508974.sdt
Adds a message to alert users when they have reached the maximum
numbers of lots (PO$MAX_LOTS) that can be entered in Quick
Receipts.
Message for Exceeding Order Fulfillment Memory

Limit (PCR 510160)
P510160.sdt
Adds message for exceeding memory limit in Order Fulfillment
during entry of a new Sales Order Line.

Messages for Exceeding Length of Province and
County Fields (PCR 510963)
P510963.sdt
Adds messages for exceeding the length of new fields Province and
County on the Order Fulfillment Address Entry/Edit form.
Pay Vendor Lookup Fix (PCR 510988)

P510988.ora
This script provides an insert statement for the sy_lkup_typ table, and has
been consolidated into the script up41002.ora. This resolves an issue
with the Pay Vendor Lookup, which did not function after an sdt. script
was run to resolve an earlier PCR issue.
System Module
Polish, Russian Language Codes Added (PCR

510935)
P510935.ora
The script P510935.ora creates Polish and Russian language codes, and
has been consolidated into the script up41002.ora.

Implementation Considerations
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
Note: Each installation is different, and many variables affect

performance, including (but not limited to): network traffic, WAN
environments, network topology/bandwidth, and PC configuration and
performance.
Oracle GEMMS 4.10.02 Release Notes Implementation Considerations • 11

Address Enhancement for Order Fulfillment
GEMMS Release 3.21.12 included an enhancement to allow entry of the
City, Province, and County on the Address Entry/Edit form throughout
GEMMS. This was to achieve consistency with address handling in
Oracle Financials.
However, the enhancement did not consider that Order Fulfillment uses a
different Address Entry/Edit form than the other GEMMS modules. The
address enhancement was not applied to the Order Fulfillment version of
the Address/Edit form.
For the 4.10.02 Release, the address enhancement has been applied to the
Order Fulfillment Address Entry/Edit form. However, address displays
on forms and reports (throughout GEMMS) will still be missing this
additional address information; this display/report issue will be addressed
in a future GEMMS release.
Financials Modules
Single Login From Oracle GEMMS to Oracle

Financials
To ensure that the single login from Oracle GEMMS to Oracle Financials
is working properly, the following prerequisites are required:
1. Copy the latest version of Oracle GEMMS gllogon.sh file to the
APPL_TOP directory
2. The username and password must be the same for both Oracle
Financials and Oracle GEMMS
3. Copy the appropriate FNDSCSGN.frm from the integration
directory to the FND_TOP/forms directory
4. The following constants must have the appropriate values:
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.
12 • Implementation Considerations Oracle GEMMS 4.10.02 Release Notes

AP Update
If you upgrade from Oracle Financials 10.5 to 10.7, then ensure that you
apply the patch for bug 492585. If you upgrade without applying this
patch, then the upgrade will not be successful and you may encounter
referential integrity problems. The following problem might be
encountered (also its fix is provided):
Problem: Running PO Interface gives error ‘ Cannot find rows in
FND_DESCRIPTIVE_FLEXES’
Fix: Log on to System Administrator responsibility and rename the
reports and its concurrent program as follows:
1. /Navigate Concurrent Program Executable
Rename executables po_val_drv, po_load_drv and
PO_Exception report.
2. /Navigate Concurrent Program Define
Rename program po_val_drv, po_load_drv and PO Exception
report. Note that the SHORT NAME on this form cannot be
renamed. Do not make any changes.
3. /Navigate Reports Set
Retrieve the PO Interface report set and delete the three reports
assigned to it.
4. Redefine the Concurrent programs and the report set as per the
README instructions in $GEMMS/ofint directory. The only
exception is that the SHORT NAME for the program definitions
need to be changed to something new.
If you upgrade from Oracle Financials 10.5 to 10.7, you may encounter
the following error "ora-1422: exact fetch returns more than requested
number of rows" in the PO Exception report. This situation occurs
because PO Interface uses the sequences defined below from PO User
instead of the sequences from the caidtlx user. The next value of these
sequences are not in sync with the various PO tables.
PO Interface Sequence
♦ po_headers_s
♦ po_lines_s
♦ po_line_locations_s
♦ po_distributions_s
Run the poseq.sql file from the $GEMMS/ofint directory for the apps
user to resequence appropriately and correct this issue.

AR Update
To ensure the AR Update program completes successfully, the following
set up is required:
♦ In Oracle GEMMS 4.1, define additional segments for the Line
Transaction Flexfield. If the Oracle GEMMS 3.21 Flexfields
are used (five segments instead of seven), then Autoinvoicing
may terminate with an error ('more than one rows retrieved for
the sub-query')
♦ Set up at least one dummy segment for the Territory flexfield.
If one segment does not exist, then autoinvoicing does not
complete successfully
♦ Set up the Tax Profile option. This allows for the override of
Customer Exemptions
♦ While defining the Transaction Types for Autoinvoicing, the
descriptive flexfield 'Memo returns inventory' is set to No (if
enabled). Set to Yes for credit memos
The following constants are used for AR Update:
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.

Customer Synchronization
Is terms code a required field for 4.1 integration? In Oracle GEMMS
4.1, the terms code must be assigned to a customer if the terms vary flag
in Oracle is set to no. The terms vary is defined for the profile.
Following is the order in which the profile is read:
♦ Customer site profile
♦ Customer Profile
♦ Profile Class
Following is order in which terms code is read:
♦ Bill-to site terms code
♦ Ship-to site terms code (if the ship-to site as the same name as
bill-to site)
♦ Customer site profile terms code
♦ Customer profile terms code
♦ Profile class terms code
Following are the various descriptive flexfields that are used for customer
synchronization. These attributes are reserved for the integration and
must not be used for any other purpose. If you are currently using them
for a different purpose, please move them to an unused attribute.
Field name Form Attribute Order

Freight Bill Method Customer Address Attribute1 Ship-to, Bill-to
From Warehouse Customer Address Attribute2 Ship-to, Bill-to
GL Class Customer/ Site Attribute1 Bill-to, Ship-to, Customer
Tax Location Code Customer/ Site Attribute2 Ship-to, Bill-to, Customer
Tax Calculation Code Customer/ Site Attribute3 Ship-to, Bill-to, Customer
Customer Price Class Customer/ Site Attribute3 Bill-to, Ship-to, Customer
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)

Multiple-Organization Installation
If you have upgraded from Oracle Financials 10.5 to 10.7 and plan on
using the multiple-organization feature, then the multiple-organization
conversion might fail. This may occur because of the way the prior
integrations were creating sequences. In order to avoid this occurrence,
run the following script before you convert your 10.7 installation to
multiple-organizations:
From the ofint directory under the GEMMS root directory, run sqlplus -S
/NOLOG @chgseq.sql <apps_user> <apps_passwd> <ar_user>
<ar_passwd> <caidtlx_user> <caidtlx_passwd>
Note: Ensure that you have write privileges to the ofint directory. Also,
substitute the proper user names and passwords.
Manufacturing Accounting Controller Setup

Requirements
Prior to setting up and saving an Oracle GEMMS purchase order,
complete the following setup requirements in the Oracle GEMMS
Manufacturing Accounting Controller module. If the following
requirements are not fulfilled, then a database error (ORA-00936:missing
expression) may occur:
♦ The Event Fiscal Policy must be setup for your company where
Source = PO and Event = RCPT
♦ Ensure that at least the default Account Mapping (by specifying
the Company and Account Title and leaving the remaining
fields blank) exists for the following Account Titles in your
company
• INV
• AAP
• PPV
• EXP
• AAC
• ACV
♦ Ensure that at least the default Accounting Unit Mapping (by
leaving the Organization and Warehouse fields blank) exists
for your company
♦ Ensure that at least the default Ledger Mapping (by leaving the
Organization field blank) exists for your company

Geography Code Synchronization Between Oracle
GEMMS and Oracle Financials
Oracle Financials only supports a two-character geography code, while
Oracle GEMMS supports a 3-character geography code. Customers
implementing GEMMS in an Oracle Financials Integrated environment
need to be aware of this and ensure proper use.
Statements Resolve Customer Form Label Issue

A form label issue exists if you are upgrading from an existing 4.1
database. If you do not run the following statements, on your attempt to
access the Customer form (Sales>Customer) a message will display
indicating that the form cannot be found.
At the end of the Oracle GEMMS install, but prior to the Oracle
Financials installation, follow these procedures:
1. Sign on to sqlplus using sqlplus gemms/dlx
2. Enter the following:
delete from sy_objt_tbl where object_code=’OPCUSED’;

delete from sy_labl_tbl where label=’OPCUSED’;
commit;
Note that the message “0 rows deleted” may display if rows have already
been deleted.
Manufacturing Modules
New Formula Management Release Type Switch

(PCR 410090)
The software switch FM$DEFAULT_RELEASE_TYPE was added to
the 4.10 Release. This switch controls the release type to which formula
lines default when you create new formulas or add new lines to existing
formulas or batches. The default for the switch is “1” (Manual Release).
Prior to 4.10, release type defaulted to Automatic Release. To continue
formula line default to Automatic Release, you must change the value of
this new switch (otherwise your formula lines will default to Manual
Release). Go to the Constants form (Object>System>Constants for CHUI
or Object>System>System Maintena>Constants for GUI) and enter “FM”
in the Module field. This displays the Constants list.
Go to FM$DEFAULT_RELEASE_TYPE and <Tab> to the Constants
Value field. To insure that your new formula lines continue to default to
Automatic Release, enter “0” in the Constant Value field, and save.

If you want new formula lines to default to Manual Release, leave the
Constant Value set to 1. If you want new formula lines to default to
Incremental Release, change the Constant Value to “2”. Note that you
have to log out of GEMMS and back in for the change to take effect.
Partial Certification Release Types (PCR 511040)

When using partial certification from a batch line
(Object>Production>Batches>Partial Cert), you must set the release type
of the item (ingredient) to Manual. If you entered an Auto-release item
on the Partial Certification screen, the quantity for that item is not
updated in the batch. This occurs because partial certification is
intended to be driven by a Manual release item, and then to backflush
Incremental release items; Auto-release items are not intended to be
updated.
You set release types on the Additional Edit dialog box on the Batches
form (Object>Production>Batches> Edit>Additional Edit). You can also
set release types on the Additional Information form on the Additional
Information dialog box from the Formulas form (Formulas>
Edit>Additional Info) or the Ingredients form
(Object>Formula>Edit>Ingredients> Edit>Additonal Info).
Inventory Quantities Document Ordering Setup

When you first set up Document Order sequencing for the Inventory
Quantities form, you only need to set the sequencing one time for the
Inventory Journal Transactions document (JRNL). When you set up the
other Inventory Quantities document types (such as ADJI, CREI, etc.)
you do NOT need to do this again.
Go to the Document Order form (Object>System>System
Setup>Document Order). Specify JRNL in the Document Type field
and the organization code in the Organization field, then assign a type
(Manual or Automatic).
Logistics Modules
Error Message When GL Accounts Are Not Defined

If general ledger accounts are not setup correctly, when a purchase order
or a stock receipt is saved the user will see an SQL error instead of a
message indicating that accounts are not set up. An appropriate message
will be added in an upcoming release.
Proforma Invoice Print

The Proforma Invoice will not print unless there is a sold-to customer and
a FOB code on the order header, and a freight bill method on the order
line.

Ship Tolerance and Automatic Close
If maximum ship tolerance is not set, the order line will not be closed
automatically.
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.
Security by Operator Groups

Establishing Oracle GEMMS security requires you to do so on an
operator code basis. This can be very time consuming. Operator codes
can be defined not only for individual users but also groups, so that
several users can be assigned to one user group who have the same
security profile. When implemented, security updates need only be
performed for the group operator code, rather than on a user-by-user
basis.
Group security can be established for modules, objects, and subobjects.
From either the Module Security form (Object>System>System
Security>Module Security) or the Object Security form
(Object>System>System Security>Object Security), select a group
operator code, and apply the appropriate levels of security. For more
information, refer to the Oracle GEMMS System Administration Guide.

Applying Security to System Constants
In order to ensure the integrity of your system constants,
LOAD_FROM_DB was implemented in Oracle GEMMS 3.21. This flag
determines whether a system constant will be read from the database
(SY_CONT_TBL) or from the tran.ini file. In order to assure the highest
level of security, load as many of the system constants as possible from
the database. The following system constants must be read from tran.ini:
SY$GUI
SY$ERRORLOG_FILE
SY$CONFIG_PATH
SY$DEFAULT_LANG
SY$DBMS
Purge & Archive Documentation Warning

The enhanced Oracle GEMMS 4.1 Purge & Archive Functionality must
be implemented by an experienced DBA or System Administrator. Once
data is purged, it cannot be retrieved, except from a system backup.
Detailed procedures for using the Oracle GEMMS Purge and Archive
utility are provided in the Oracle GEMMS System Administration Guide.
Invalid Document Type Error Message

When defining document sequencing for a new document
type/organization, an error message will display informing you that
document sequencing is not set up. This is only a warning and can be
ignored.
Inventory Journal Transactions - Document

Ordering
When setting up document ordering to create Inventory Journal
transactions, the only document type that is necessary is JRNL. All other
document types should be disregarded for this specific transaction.

Documentation Updates
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.
Single-Level Cost Rollup

Object>Costing>Cost Rollup>Action> Path
Start Cost Rollup
The Single-Level Cost Rollup option lets you run a cost rollup for one
item utilizing only one level for a product item. When it is executed it
utilizes only the previous level of costs. When the Single-Level Cost
Rollup is executed for the lowest-level product, these costs become a
combined cost.
The combined cost of the lowest-level is now used for determining the
cost of other higher-level products. The lowest-level costs are no longer
used on an individual basis when executing a Single-Level Cost Rollup.
This does not affect the costs for other products that may depend on the
ingredients for the product item.
On the Start Cost Rollup dialog box there is now a Single-Level Cost
Rollup option.
Cost Rollup Form
Oracle GEMMS 4.10.02 Release Notes Documentation Updates • 21

The procedures to perform a cost rollup have not changed, but a new
feature has been added to Oracle GEMMS. The Single-Level Cost
Rollup uses the same forms as the standard Cost Rollup. Now on the
Cost Rollup forms there is a Single-Level Cost Rollup option.
The Single-Level Cost Rollup is setup and started in the same manner as
the Cost Rollup, with the following considerations:
♦ Place “X” in the Single Level field to indicate a single-level cost
rollup (blank is the default, indicating a standard cost rollup)
♦ In the Character-User Interface version of Oracle GEMMS, if a
single-level cost rollup is indicated, only the “Now” Start Date
is a valid option; the single-level cost rollup is performed
immediately as a foreground process (processing time depends
on data volume)
♦ In the Graphical-User Interface version of Oracle GEMMS, if a
single-level cost rollup is indicated, both the “Now” and
Specific Date Start Dates are valid options
♦ When a single-level cost rollup is indicated, only one item may
be entered (“All” and “range of items” are not valid). Item
Cost Class is not a valid option, and is disabled
22 • Documentation Updates Oracle GEMMS 4.10.02 Release Notes

Example:
A product contains three levels of ingredients and their associated costs -
lowest level, intermediate level, and highest level. When a Single-Level
Cost Rollup is executed for the lowest-level product (Ingredient A and
B), these costs become the combined cost for the intermediate product
(Product 1).
The combined cost of the lowest level is now used for determining the
cost of other higher-level products. The lower-level costs are no longer
used on an individual basis when executing a single-level cost rollup.
In this example, the costs for Ingredients A and B are used to determine
the cost of Product 1. When a single-level cost rollup is performed for
the higher-level product (Product 2), only the intermediate level costs
(Product 1 and Ingredient C) are used to calculate the cost. In this case,
the individual costs for Ingredient A and B do not influence the cost of
the higher-level product (Product 2).
Higher Level
Product 2
Ingredient C Intermediate
Product 1
Level
Ingredient A Ingredient B Lowermost Level
Oracle GEMMS 4.10.02 Release Notes Documentation Updates • 23

Cost Rollup Process Status
Object>Costing>Cost Rollup>Action> Path
Process Status
After a single-level cost rollup is started you can view its status by
choosing Process Status from the Action menu on Cost Rollup
Process form. The Cost Rollup Process Status form now has a Single
Level field. If a single-level cost rollup was indicated on the Start Cost
Rollup form, the item displays in the Single Level field. This field is
blank if a single-level cost rollup was not indicated.
Cost Rollup Process Form With Status Data
24 • Documentation Updates Oracle GEMMS 4.10.02 Release Notes

PCRs Addressed in 4.10.02 Release
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.
Accounting Setup PCR Resolutions
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.
Oracle GEMMS 4.10.02 Release Notes PCRs Addressed in 4.10.02 Release • 25

Cost Management PCR Resolutions
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.
26 • PCRs Addressed in 4.10.02 Release Oracle GEMMS 4.10.02 Release Notes

510013
Issue:
If the trans_cnt field was greater than nine, then you were unable to save
new target warehouse. When the trans_cnt field in cm_whse_eff was
greater than nine, if you tried to change/overwrite the default target
warehouse, the following message was received "Someone else has saved
this record."
Since the trans_cnt had a length of one, when trans_cnt was updated to
10, it found only the first digit of the value (for example, one) and tried
updating the record. As a result, the update failed and provided the
indicated message.
Resolution:
The trans_cnt field length was increased to accommodate numbers
greater than nine.
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.

510926
Issue:
Database error "ORA-01401-inserted value too large for column"
occurred, when the GL Expense Allocation Definition Report was run.
The following procedures were followed:
1. Entered a company
2. Chose All Allocation Codes.
3. Entered SCREEN as the printer.
4. Chose Accept.
Resolution:
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:

Manufacturing Accounting Controller PCR Resolutions
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:
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)

510341
Issue:
When the selection priorities for the account title SAL was defined, you
were allowed to use tax authority to map to an account. When the Oracle
GEMMS and Oracle Financials integration was run, the SAL account title
was used in the GL process. This process did not use the tax authority as
a criteria for mapping to an account. Therefore, the accounts were
mapping to default accounts. You must not be allowed to enter tax
authority as a selection priority for the SAL account title.
Resolution:
Tax authority is disabled from the Selection Priority form for the SAL
account title.
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.

Oracle GEMMS and Oracle Financials Integration PCR
Resolutions
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.

510218
Issue:
The Oracle-to-GEMMS synchronization for Sales Order Entry only
brought across the foreign-to-functional currency exchange rate (the
functional-to-foreign exchange did not get updated to Oracle GEMMS).
Resolution:
JPL code was added to get the exchange rate from functional to foreign
currency.
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.

510757
Issue:
After closing the detail and header GL Drill Down windows, the
following message displayed:
"Do you want save the changes you have made?"
This message also displayed when the Detail button on the Drill Down
window was chosen. This message should not appear.
Resolution:
The program has been modified to resolve this issue.
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.

510973
Issue:
In Oracle GEMMS, customer currency (which is a mandatory field) was
not populated by customer synch.
Resolution:
If no currency was defined for the customer in Oracle Financials, then the
cust_currecy field was set to ' '. This created problems in the credit
checking program. The program has been corrected to resolve this issue.
Please review the following for additional information on customer
currency:
The currency of the primary bank account is set as the cust_currency in
Oracle GEMMS. This bank account can be defined at the customer or
site level. Site level definition takes precedence over customer level. If
only one primary bank account is defined at the site level, then the
currency of this bank account is used as the customer currency. If more
than one primary bank account is defined at the site level, then base
currency for the set of books will be used as customer currency.
If no primary bank account is defined at site level and only one primary
bank account is defined at customer level, then the currency of this
customer level bank account will be used as the customer currency. If
more than one or no primary bank accounts are defined at the customer
level, then the base currency for the set of books will be used as customer
currency.

Capacity Requirements Planning PCR Resolutions
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.
Inventory Management PCR Resolutions
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 lowercase letters.
Resolution:
The code was modified to permit the item description to support upper-
and lowercase 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.

Material Requirements Planning PCR Resolutions
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.
Process Operations Control PCR Resolutions
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.

Production Management PCR Resolutions
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.

Quality Management PCR Resolutions
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.
Purchasing PCR Resolutions
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.

507250
Issue:
When the user copied a purchase order the status on the new purchase
order retained a status of “closed” if the source purchase order was
closed. Also, the Header fields on the new PO could not be modified.
The PO Line Detail form subsequently displayed in “query” mode, but
changes could be made and saved.
Resolution:
A jpl file was modified to correct the problem; the status of the new PO is
now “open” and the details are in “add” mode.
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.

508768
Issue:
Disabling of vendor sites in Oracle Payables did not remove vendor
associations in Oracle GEMMS Purchasing .
Resolution:
When a pay site in Oracle Payables was disabled, the vendor in the
Oracle GEMMS Vendor Master had the Inactive flag set to “1”.
However the view for Vendor Associations only referenced the column
DELETE_MARK (rather than the Inactive flag). During purchase order
entry the default pay site is the first in an alphanumeric sort of the
vendors associated to the purchase-from site. The problem was that the
default pay site vendor could be disabled, since inactive sites were
included in the view. The code for the vendor association view has been
modified to correct this problem.
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.

508974
Issue:
The user encountered a problem in Quick Receipts when receiving more
than 20 lots/line items.
Resolution:
A message has been added to inform users that the maximum number of
lots has been received in Quick Receiving.
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.

509830
Issue:
On the BPO Confirmation report, a maximum of twelve lines of attached
text printed out on the report. This presented a problem when more
extensive text was attached.
Resolution:
The text restriction has been removed from the report, eliminating the
problem.
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.

510988
Issue
The Pay Vendor Lookup did not function after an sdt. script was run to
resolve an earlier PCR issue.
Resolution:
An insert statement was added for the sy_lkup_typ table, which resolved
the issue.
Sales Management/Order Fulfillment PCR Resolutions
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:
be reproduced at Oracle. If an issue still exists, contact Level 1 support
with additional details.

508341
Issue:
An error message displayed on an attempt to run the Shipping Picklist
report (Sales>Shipping>Reports>Shipping Picklist).
Resolution:
It was determined that the problem occurred only on the DEC/ALPHA
machine. This problem has been corrected.
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.

509118
Issue:
On the Pick Lots/Locations form, the error message “Alloc Qty May not
be greater the available qty” displayed erroneously on an attempted
change to an allocation from one lot to another.
Resolution:
The error that caused this problem has been corrected. Note that this
correction also resolved PCR 506315.
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.

510198
Issue:
Allocating inventory to a shipment with more than 22 lines caused a jpl
error message (Sales>Shipping>Edit>Pick Lots>Edit>Tran Addl Dtl).
Resolution:
The SY$MISC_UPDATE_VALUES array became synchronized with the
shipment line array (which had only 20 occurrences) producing the error
when line 21 was updated. This problem has been resolved.
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%).

510407
Issue:
This was a request for Oracle GEMMS to prevent the user from assigning
a hold to an order if that hold is incompatible with the order line status.
For example, if the order line already has been picked, the user should
not be able to put a hold on the line that would prevent the line from
being picked.
Resolution:
GEMMS now validates that a hold reason code is compatible with the
line status, and flags the user immediately if an incompatibility exists.
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.

510735
Issue:
This problem occurred during order entry when the user used the Item
Lookup to select an item. The Item Description on the first order line
was not retrieved, and the user was unable to continue.
Resolution:
A problem with cursor positioning when returning from the Item Lookup
was corrected, eliminating the problem.
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.

510776
Issue:
During manual allocation entry, if a specific series of entries was made,
GEMMS did not recognize status of a lot as being non-nettable for order
entry. When the user specified the lot and sublot prior to entering the
location, GEMMS prompted for the location. The user could go to the
Quantity field and allocate, then accept the manual allocation to a lot
not nettable for order entry. GEMMS did not, in fact, accept these
allocation entries; when the user exited the form the allocations went
unsaved.
Resolution:
An incorrect validation of the lot and sublot allowed the user to save the
allocations when there were no onhand quantities. This validation has
been corrected.
510790
Issue:
During setup of order types (Order Fulfillment>Setup>Order Type) an
error message displayed intermittently when records were opened for
update.
Resolution:
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.

510792
Issue:
While the Order Entry form was displayed, the user selected Clear from
the File menu. Since there is no function associated with Clear from the
Order Entry form, that function should not have been accessible.
Resolution:
Clear on the File menu is now protected in this situation.
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:
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.

510811
Issue:
This problem occurred while using the Pick Lots form to look up lots.
When the user selected a lot for an item controlled by dual units, the
second unit quantity did not display. However, if the user did not use
picklots, but instead allocated the line manually by typing in the data, the
second unit of measure quantity displayed.
Resolution:
The second unit of measure is now calculated and displayed properly
when the Pick Lots form is used.
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.

510906
Issue:
The user entered a new sales order and (on the Header) specified the
same customer for ultimate destination and consignee. However, on the
Line Details form, an error message displayed when the user attempted to
specify this same consignee.
Resolution:
The Customer Type for consignee was assigned to “4”, which was not
implemented in the customer number functionality. The customer type
was changed to “1” (Ship-to Type) eliminating the problem.
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.

510963
Issue:
An earlier GEMMS release enhancement provided for entry of the City,
Province, and Country on the Address Entry/Edit form throughout
GEMMS. This enhancement, however, did not take into account that
Order Fulfillment used a different Address Entry/Edit form than the rest
of GEMMS, so the enhancement was not applied to the Order Fulfillment
version of the form.
Resolution:
The address enhancement has been applied to the Order Fulfillment
Address Entry/Edit form. Please note the Order Fulfillment
Implementation Considerations for more information on this resolution.
Tax Module PCR Resolutions
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.

System Module PCR Resolutions
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.

510162
Issue:
The user was unable (intermittently) to create a shipment because of a
database situation, which produced an error message.
Resolution:
The error that caused this problem has been corrected, and shipment
creation now processes smoothly.
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.


41002

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

41002

Uploaded by

Copyright:

Available Formats

Oracle® GEMMS®

Part No. A57502-01

Part No. A57502-01

Copyright © Oracle Corporation 1997

All rights reserved. Printed in the U.S.A.

This software/documentation contains proprietary information of Oracle Corporation; it is

If this software/documentation is delivered to a U.S. Government Agency of the Department

Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to

Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065

If this software/documentation is delivered to a U.S. Government Agency not within the

ORACLE and GEMMS are registered trademarks of Oracle Corporation.

GEMMS Maintenance Release 4.10.02 1

Database Update Scripts 5

Oracle GEMMS 4.10.02 Release Notes Contents • i

ii • Contents Oracle GEMMS 4.10.02 Release Notes

Oracle GEMMS 4.10.02 Release Notes Contents • iii

What is Release 4.10.02?

Cumulative Changes to 4.1 Release on Tape

Oracle GEMMS 4.10.02 Release Notes GEMMS Maintenance Release 4.10.02 • 1

2 • GEMMS Maintenance Release 4.10.02 Oracle GEMMS 4.10.02 Release Notes

Financials Modules Release Highlights

Oracle GEMMS 4.10.02 Release Notes Release Highlights • 3

Logistics Modules Release Highlights

4 • Release Highlights Oracle GEMMS 4.10.02 Release Notes

Scripts Consolidated Into the 4.10.02 Release

Oracle GEMMS 4.10.02 Release Notes Database Update Scripts • 5

Credit Limits and Currencies (PCR 510660)

Column in Oracle GEMMS Column in Oracle Financials

Subledger PM POC Bookings Changes (PCR

6 • Database Update Scripts Oracle GEMMS 4.10.02 Release Notes

Single Level Cost Rollup Changes (PCR 510287)

Oracle GEMMS 4.10.02 Release Notes Database Update Scripts • 7

Tax Authority Removed as a Selection Priority for

8 • Database Update Scripts Oracle GEMMS 4.10.02 Release Notes

Cost Component Class Display (PCR 504142)

Disabling of Vendor Associations (PCR 508768)

User Field Validation in Receipt Programs (PCR

Warning Message for Maximum Quick Receipt Lots

Message for Exceeding Order Fulfillment Memory

Oracle GEMMS 4.10.02 Release Notes Database Update Scripts • 9

Pay Vendor Lookup Fix (PCR 510988)

Polish, Russian Language Codes Added (PCR

10 • Database Update Scripts Oracle GEMMS 4.10.02 Release Notes

Note: Each installation is different, and many variables affect

Oracle GEMMS 4.10.02 Release Notes Implementation Considerations • 11

Single Login From Oracle GEMMS to Oracle

12 • Implementation Considerations Oracle GEMMS 4.10.02 Release Notes

Oracle GEMMS 4.10.02 Release Notes Implementation Considerations • 13

14 • Implementation Considerations Oracle GEMMS 4.10.02 Release Notes

Field name Form Attribute Order

Oracle GEMMS 4.10.02 Release Notes Implementation Considerations • 15

Manufacturing Accounting Controller Setup

16 • Implementation Considerations Oracle GEMMS 4.10.02 Release Notes

Statements Resolve Customer Form Label Issue

delete from sy_objt_tbl where object_code=’OPCUSED’;

New Formula Management Release Type Switch

Oracle GEMMS 4.10.02 Release Notes Implementation Considerations • 17

Partial Certification Release Types (PCR 511040)

Inventory Quantities Document Ordering Setup

Error Message When GL Accounts Are Not Defined

Proforma Invoice Print

18 • Implementation Considerations Oracle GEMMS 4.10.02 Release Notes

Security by Operator Groups