In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   On Demand  |   Home  |   qad.com




MFG/PRO eB2.1 Service Pack 3
Service Pack 3 for MFG/PRO eB2.1 includes all ECOs closed between January 22, 2005, and August 18, 2005. A few significant changes introduced with ECOs that modify product features are highlighted in this section.
Support for Oracle Databases
Effective with this service pack, MFG/PRO eB2.1 is available for Oracle databases.
See MFG/PRO eB2.1 Installation Guide: Oracle Database.
Important: The stand-alone Service Pack 3 installation does not apply to Oracle. You must do a complete MFG/PRO installation to install the service pack features in an Oracle environment.
Note: MFG/PRO eB2.1 for Oracle requires Progress version OE10B02. The installation guide provides information on specific Progress components.
Domain PROPATH Setup
A new Propath Setting field has been added to Domain Maintenance (36.10.1) to support multiple-domain environments in which product licensing agreements or localizations are not the same across all domains. For example, one domain might use a Brazilian financials localization, a second European Accounting, and a third the standard MFG/PRO Financials functionality.
Note: This new field is typically needed only under very specific circumstances. Most MFG/PRO system administrators can leave it set to the default value, blank.
In MFG/PRO, the Progress PROPATH environment variable sets the directory paths the system uses to locate and run executable programs. Values set in the PROPATH can point to different directories for different sets of programs, or multiple versions of the same set of programs. The new Domain Maintenance field lets you associate each domain with a specific set of PROPATH entries—so that the system automatically runs the correct program code for the current domain.
When you log in to a domain that has a value entered in Propath Setting—or switch to one using Change Current Domain (36.10.13)—the system updates your current default PROPATH by adding the domain-specific directories to the front. This allows domain-specific programs to be found before those in your default PROPATH, which is assigned at log-in. Each time you switch domains, the system clears any PROPATH changes made for the previous domain and adds new values, if any are specified in the new domain’s Propath Setting field.
Use the following steps to update the new field.
Important: Because of a user interface limitation, you cannot update the Propath Setting field using Domain Maintenance in QAD Desktop; it is available only in the character or Windows UI. However, this does not limit QAD Desktop’s ability to run domain-specific programs based on Propath Setting values entered in a different UI.
1
Be sure you are not currently logged in to the domain you want to update. If you are, the Propath Setting field is disabled. If necessary, switch to a different domain using Change Current Domain.
2
Enter a comma-separated list of directories—in addition to those defined at log-in—the system should use for this domain.
3
Press Go. The system validates that your entry does not exceed 160 characters—the maximum size of the database field—and that all elements represent valid directories.
Security and Enhanced Controls
This service pack addresses a number of issues in the areas of general system security, as well as the Enhanced Control module.
Security Updates
Change Current Domain (36.10.13) has been modified to ensure that menu security works properly.
Logon Attempt Report (36.3.23.1) has been modified to sort by log-in date/time to assist in identifying intrusion patterns over time. Previously the program sorted by user ID.
User Group Report (36.3.23.4) now has different labels on the Active Domain and Active User columns. Previously both columns were labeled Active.
A security issue that could have allowed an unauthorized user to exit to the Progress Editor during MFG/PRO log-in has been corrected.
Enhanced Controls Updates
Several code changes have been made to ensure Enhanced Controls works with Progress OpenEdge 10.
Audit Trails functions have been updated as follows:
Overall performance has been improved by changing the way audit trail data is captured before being written to the audit database. This update requires schema changes to the audit trail transaction tables in the qaddb database.
See the Enhanced Controls chapter of Installation Guide: MFG/PRO eB2.1 for more information.
The new method does not work correctly if the table being audited has ever had fields deleted from it—for example, by a customization. The QAD installation utility MFG/UTIL now includes tools to identify this situation and correct it during installation. In addition, audit trail setup programs now check for deleted fields and display warning or error messages if they are found.
The subject line for e-mail notification for the Audit Trail Creation Process has been changed to Audit Trail Creation. Previously it read AT_CREATION.
Additional master comments have been added to clarify e-mail notifications.
Code modifications corrected a performance problem when the Audit Trail Creation Process is done with a full table scan.
Date, time, and time zone are now retrieved from the appropriate server in a multi-database environment.
Audit Profile Activation (36.12.13.8) has been modified so that the output report correctly displays the user-entered delete keys as type Other. Previously they were shown as Primary.
In the Audit Trail Report–Existing (36.12.1) and Audit Trail Report–Deleted (36.12.2), field labels now display correctly when users scroll through selected records.
The same two reports now correctly display modified field data when a database field is a substring of another.
Several changes have been made to Electronic Signatures:
Two features in E-Sig Workbench Profile Maintenance (36.12.14.5) now work in a QAD Desktop 2 environment. The lookup browse on the Filter field displays correctly, and you can now delete a filter criterion.
Additional master comment records have been added to clarify the e-mail for a profile activation event.
E-signature data has been corrected for category 0006, and PCC categories 0009 and 0010 have been added.
The Domain field can no longer be updated in E-Signature History Report (36.12.5). It displays the user’s current working domain. In the same program, the lookup browse on the Category Code field now works correctly.
Activated E-Sig Profile Report (36.12.14.9) now correctly displays results when E-Signatures On is set to No and E-Signatures Off is set to Yes.
Buffer-copy issues when running European Accounting with Enhanced Controls have been addressed. The affected programs are:
AR Payment Bank Reconciliation (27.6.5.7)
Draft Bank Reconciliation (27.6.6.17)
Recurring Voucher Release (28.8.4)
Cash Book Maintenance (31.13)
Note: In addition to these software updates, a new document is available to assist you in planning and implementing the Audit Trails portion of Enhanced Controls. QAD highly recommends that you consult this document prior to beginning an implementation. Deployment Guide: Audit Trails is located at the following URL:
Supplier Consignment Inventory
This service pack includes updates to AP pending vouchers to facilitate vouchering of supplier invoices for consigned inventory.
Voucher Maintenance (28.1) now supports processing multiple consignment pending vouchers. Previously, when multiple pending vouchers were associated with a single receiver, the first pending voucher listed was always being updated even when it had already been fully vouchered.
Each pending voucher is now processed independently of other vouchers for the same receiver and line.
This service pack updates the following Voucher Maintenance frames:
Receiver Matching Detail frame
Receiver Matching Maintenance frame
Auto-Select of Pending Vouchers
Open Receivers frame
The Receiver Matching Detail frames now display multiple pending vouchers in the scrolling window when using Auto Select. Previously, selected records did not display.
When manually selecting pending vouchers to process from the Open Receivers frame, the system creates a separate history record for each voucher. The Receiver Matching Maintenance frame now prompts you to select which pending voucher to update instead of returning an error message.
Additionally, when you enter a quantity greater than that shown on the selected pending voucher, the system displays a warning but allows you to continue vouchering. Previously, an error message prevented vouchering.
The effect of these changes extends to Unvouchered Receipts as of Date Report (5.13.10) and Purchase Receipt Report (5.13.5). Both reports now:
Report multiple pending vouchers for a single receiver.
Use the same calculation for Total Standard Cost when Use Total Std Cost field is No.
Show matching outputs when Non-Vouchered Only field is Yes.
Reserved Locations
A new Detail Allocate field has been added to the reserved locations frame in Location Maintenance (1.1.18). Use the field to specify whether the system automatically generates detail allocations on sales orders for the specified customer from the reserved location.
Yes (default): During Sales Order Maintenance (7.1.1), the system forces detailed allocation of the reserved inventory. This ensures that quantity-to-allocate calculations are correct for the same item in non-reserved locations.
No: The system does not automatically detail allocate.
It is recommended that you leave this field set to Yes. During general allocation, MFG/PRO does not update location detail records for locations with inventory status codes that have Available set to No, which is the typical setting for a reserved location. In these cases, entering subsequent orders for the same item in non-reserved locations can display an incorrect quantity to allocate. Setting Detail Allocate to Yes avoids this situation.
Enterprise Material Transfer
A new Allow Non-Ack Deletes field has been added to the Enterprise Material Transfer (EMT) frame of Sales Order Control (7.1.24). Use it to specify whether the primary business unit (PBU) can delete its primary sales order or individual order lines before importing an acknowledgment from the secondary business unit (SBU) when Require Acknowledgment is Yes in Purchasing Control (5.24).
No (the default): MFG/PRO displays an error message if you attempt to delete an unacknowledged order or line when Require Acknowledgment was set to Yes in Purchasing Control at the time the order was exported to the SBU.
Yes: You can delete unacknowledged orders or lines regardless of the Purchasing Control setting.
Inventory Control
A new field, Recalculate Deleted Locations, has been added to Inventory Valuation as of by Loc (3.6.16).
Set the field to Yes (the default) to have the system consider locations that have had detail records deleted between the effective date and the date the report is run. These can be records for temporary locations—automatically deleted when the balance falls to zero—or locations that were deleted manually.
When the field is set to No, the system does not re-create deleted locations and calculate inventory value for them.
Credit Card Processing
The Storefront module has been renamed Credit Cards to more accurately reflect the way it is used. Three menu items in the Sales Orders/Invoices module have been assigned new descriptions. The following table shows the changes.
 
Menu
Current Description
Previous Description
7.21
Credit Card Menu
Storefront Integration Menu
7.21.3
Credit Card Sales Order Browse
Storefront Sales Order Browse
7.21.24
Credit Card Control
Storefront Control
Available to Promise (ATP)
ATP Enforcement has been enhanced with the addition of a Family ATP Calculation field to Sales Order Control (7.1.24).
Enter one of the following values to control which family items and component items should be considered when determining family item ATP. Leave the field set to the default 1 to have the system behave as it did before the field was added.
0. Include all component item orders and exclude all family item orders.
1. Include all component item orders and include all family item orders.
2. Include all component item orders and only family item orders outside the item’s time fence.
3. Include only component item orders inside the item’s time fence and all family item orders.
4. Include only component item orders inside the item’s time fence and only family item orders outside the item’s time fence.
Before the new options were added, family ATP calculations were based on the total availability in aggregate rather than the mix of orders already received. This is especially appropriate for products that use a high degree of common components and a limited number of unique or difficult-to-manufacture or assemble items.
Based on the setting of the new field, ATP calculations can support scenarios that feature:
Lower commonality of components, as well as some unique or difficult-to-make items
A first-level component that is a unique option to a configured product with several unique components
The new settings give planners a way of determining option availability inside a time fence, while aggregating availability outside that same fence. They can enforce some schedule stability in the near term while allowing themselves to enter orders in the longer term—where they can more easily adjust the schedule.
Accounts Receivable
A new Unassigned Unapplied Amount field has been added to Payment Register (27.6.6). You can use it to control whether the report output is limited to the current open amount of an unapplied payment or reflects the entire historical amount.
Valid values are:
Current (the default): The open unapplied amount for an AR unapplied payment displays in the Unassigned Amount column. This is format of the Payment Register report before the new option was added.
Historical: The full historical unapplied payment amount displays in Unassigned Amount.
The Historical option supports a business model that requires a static document to serve as an historical record of cash application.
Global Tax Management
A new Display Reference Total Using Line Amount field has been added to Tax Detail by Transaction Report (2.13.15.3).
Set this field to Yes to assure that tax amounts display correctly when Display Taxable/Non-Taxable Total Amounts is Yes and multiple tax types apply to the same order line.
Previously, this situation could lead to incorrect calculations because of the way the system accumulates taxable and non-taxable amounts from tax detail records.
Sales and Use Tax Interface
A new Use Primary/PO Header Tax Entity field has been added to Tax Interface Control (36.5.3.24).
The new field lets you control the entity sent by purchasing functions to the Sales and Use Tax Interface for tax records for the current working domain. You can select either the default primary entity specified in Domain/Account Control (36.1) or the entity associated with the individual PO header site.
The new field supports environments in which the current working domain in MFG/PRO includes more than one entity and taxes are reported by entity. Setting this field to PO Header allows for better control and wider functionality of the Quantum Vertex TDM (Tax Decision Maker) database and associated tax override rates and exemptions.
To continue using the current functionality, leave the new field set to the default value, Primary.
Service Support Management
You can now control whether the system copies item usage records when you create calls using Call Quote Release to Recording (11.1.1.11).
Set the new Copy Item Usage field to the default No to exclude usage data from the call. Change the field to Yes to copy item usage records.
Previously, the system always copied usage data. In cases where a material order (MO) is used to obtain repair parts for a call, this could result in the same material usage being recorded twice: once when the quote was copied and again in Call Activity Recording (11.1.1.13).
EDI ECommerce
New Transmission Group Field
A new Reset Control Number field has been added to Transmission Group Maintenance (35.13.13).
The control number is used to name files that are exported to the transmission group. Previously, you could not reset the number. When the system-generated number became too large for the database field, a Progress error displayed.
The control number is now limited to 999999. After that, the system prompts you to reset it to 0 (zero) using Reset Control Number.
Note: When you reset the number, be sure to remove existing files with the specified destination prefix from the destination directory to avoid overwriting them.
Schedule Merge Enhancements
The schedule load merge functionality has been enhanced to let you define a range of requirement dates from the previous active schedule to be excluded from the merged schedule. You also can now specify the type of requirement records to be merged from the previous active schedule.
Use two new gateway variables, ed_start_exc_ date and ed_end_exc_date, to assign the range of dates to be excluded. Previously, the merge function provided only two date variables—ed_start_cpy_date and ed_end_cpy_date—to select the date range for merge.
Use a third new variable, schedule_merge_fp, to determine whether the system selects requirements records for merge depending on whether the requirements are firm or planned.
When the variable value is F or P, the system only merges requirements that both meet the date range criteria and have a matching value in the forecast qualifier (Q) field in the schedule detail record.
When the variable value is blank or B, the system merges requirements that meet the date range regardless of the forecast qualifier value. This was the system behavior before the variable was added.
Additional Transmission Group Cross-Reference
In Trading Partner Maintenance (35.13.7), you can now override the document-level transmission group specified in the Trading Partner Document Records frame for a specific trading partner/site reference.
A new T/O (transmission group override) field has been added to the TP Location Cross-Reference frame. When that field is Yes, the system displays an additional Trns Grp field. Enter a valid transmission group defined in Transmission Group Maintenance (35.13.13). During document processing, the system uses this transmission group record for this specific address-cross reference instead of the group defined for the top-level trading partner.
You can use this feature to specify different HTTP parameters for posting XML documents for specific trading partner locations; this is useful, for example, when you are using QXtend to communicate documents created by EDI ECommerce.