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  |   Cloud ERP  |   Home  |   qad.com



  •     QAD Glossary

  • MFG/PRO eB2.1 Service Pack 2
    Service Pack 2 for MFG/PRO eB2.1 includes all ECOs closed between May 25, 2004, and January 21, 2005. A few significant changes introduced with ECOs that modify product features are highlighted in this section.
    Enhanced Controls
    See User Guide: MFG/PRO eB2.1 New Features for detailed information.
    Two new features have been added to MFG/PRO eB2.1 to support customers who have regulatory or legal requirements in the area of user accountability, such as Food and Drug Administration 21 CFR Part 11 and the Sarbanes-Oxley Act. The programs that support these features are located on the Enhanced Controls menu (36.12).
    You can configure your system to maintain audit trails. Audit trail records are created and stored in an MFG/PRO audit database. They contain facts about changes made in the MFG/PRO primary database. A typical audit record includes information that helps you identify who made a change, when the change was made, and what the change was. You can set up these functions for all MFG/PRO primary database tables or you can limit the audit trail recording activity to specific database tables.
    You can configure your system to require electronic signatures on some programs. Users of signature-enabled programs must enter a valid user ID and password before they can create or update records. Additionally, they must provide a reason code that defines the meaning of the signature; for example, Approved or Tested. Reporting tools provide access to historical signature records to let you track updates to critical data.
    Enhanced Controls is an optional module that is separately licensed and installed. You must have the appropriate license codes to activate it.
    System Security
    This service pack includes additional enhancements to security features.
    Operating System Access to MFG/PRO
    The Enforce OS User ID field has been added to Security Control (36.3.24) to let system administrators control user access to MFG/PRO character and Windows environments directly from the operating-system level. Leave the field set to No (the default) to continue using existing log-in procedures.
    Important: Regardless of this setting, QAD Desktop users must continue to enter a valid user ID and password to access the system.
    When the new field is Yes, the default user ID displayed in the log-in screen is the same ID used by the operating system, and the user cannot change it.
    Note: This must still be a valid MFG/PRO user ID defined in User Maintenance (36.3.1).
    Subsequent processing depends on whether a password is specified in User Maintenance or User Password Maintenance (36.3.3):
    If no password is specified in the MFG/PRO user record, log-in proceeds automatically, subject to proper licensing.
    If the user record includes a password, the system displays a password prompt.
    This new feature essentially allows customers to bypass MFG/PRO log-in security completely and rely on operating-system security.
    Important: If you enable this feature and reset MFG/PRO user passwords to blank, you should use caution if Enforce OS User ID is ever changed to No. If you do so without reentering passwords in user records, anyone can gain access to MFG/PRO by entering just a user ID. When you change the field from Yes to No, the system displays a message to warn you of a potential security compromise. In addition, in Windows environments it is not recommended that you reset MFG/PRO user passwords to blank. It is relatively easy to create a new user on an existing Windows machine with an ID that matches one in MFG/PRO.
    Updating Security Control
    Whenever a change is made in Security Control (36.3.24), the system now automatically generates an e-mail message to members of the administrator group specified in that program. The message lists the old and new values of each changed field as stored in the control record, as well as the user ID of the person who made the change.
    Additionally, you can no longer change any data in the user control table (usrc_ctrl) from outside of MFG/PRO. For example, you cannot use the Progress Editor to update the record directly in the database.
    Domain Field Restriction
    To support ongoing development, the system now restricts the value of the Domain field in Domain Maintenance (36.10.1). The value can still be up to eight characters in length. However, it is now limited to the characters A–Z, a–z, and 0–9.
    Shipper Gateway
    Shipper Gateway (7.9.22) has been modified to optionally add multiple containers to the shipper during import when the quantity specified for a container line is not equal to 1.
    Set the new Load Multiple Containers field to Yes to enable this feature. When the field is No, the system adds a single container regardless of the quantity.
    Previously, the program added only one container in all cases.
    Supplier Scheduled Orders
    Scheduled Order Maintenance (5.5.1.13) now lets you specify the revision level associated with an order line. The new Revision field defaults from Item Master Maintenance (1.4.1).
    Revision is also included in the output produced by Schedule Print (5.5.3.8) and Schedule Print in Fax Format (5.5.3.9).
    Previously, you could associate a revision level with discrete purchase orders in Purchase Order Maintenance (5.7), but not with scheduled orders.
    Salesperson Reports
    A new Based on Header/Detail field has been added to the following programs to improve salesperson reporting related to customer scheduled orders:
    Salesperson Commission Report (2.5.13)
    Salesperson Payments Report (2.5.16)
    Valid values for the new field are:
    Header (the default): The report includes only on the salesperson identified on the scheduled order header—even if individual lines list a different salesperson. This is the same as the current functionality.
    Detail: The program calculates line-by-line information to report on individual salesperson data.
    Belgian VAT Registration Code
    MFG/PRO has been updated to allow 10-digit VAT registration codes for Belgium (country code BE). Prior to January 1, 2005, those codes were specified as 9 digits. Now they can be either 9 or 10.
    Intrastat
    You can now enter the net weight and unit of measure for an Intrastat memo item in the Intrastat data frame in the following programs:
    Order Intrastat Data Maintenance (2.22.11)
    Build PO from Requisitions (5.2.18)
    Purchase Order Maintenance (5.7)
    Sales Order Maintenance (7.1.1)
    Pending Invoice Maintenance (7.13.1)
    Note: You cannot update these fields for inventory items.
    The system uses this information in weight calculations for Intrastat history records.
    Financials
    AP Vouchers
    The following enhancements have been made to Voucher Maintenance (28.1):
    The system now prompts you to keep open a zero-amount voucher with no distribution lines when it references a daybook that has Allow Discarding set to No in Daybook Maintenance (25.8.1). When you respond Yes, the voucher is available for future use.
    Previously, you could not reaccess a voucher created under those circumstances.
    When Enter Vouchers Confirmed is Yes in Accounts Payable Control (28.24), the system now updates the tax environment when you change the ship-to address on a voucher without an attached purchase order.
    Previously, unless you updated the tax environment manually, the system did not recalculate taxes based on the new ship-to.
    Additionally, to support compliance with regulatory controls, a new Allow Modification to Supplier field has been added to Accounts Payable Control (28.24).
    When this field is No, you cannot update the supplier using Voucher Maintenance on either of the following:
    A confirmed voucher with or without a purchase order attached
    An unconfirmed voucher with a purchase order attached
    Previously, the system displayed a warning message if you changed the supplier, but did not prevent you from updating the voucher. To continue using this functionality, leave Allow Modification to Supplier set to Yes (the default).
    AR Balances
    A new utility, Adjust AR Invoices (27.25.2, utarinvc.p), updates AR master table (ar_mstr) transaction and base total amounts to equal the sum of the amounts in the AR detail table (ard_det). Previously, some invoice-related programs were incorrectly calculating these amounts.
    Important: You should run Adjust Customer Balances (36.25.5, utcsbal.p) after running the new utility to update the customer balance (cm_balance) in the customer master with the correct amounts.
    You can run the utility multiple times. It updates only records that are out of balance.
    AR Self-Billing
    When you use AR Self-Billing, the system now prevents invoices from posting in Invoice Post (7.13.4) unless Integrate with AR is set to Yes in Sales Order Control (7.1.24). Additionally, Pre-Shipper/Shipper Auto Confirm (7.9.7) and Shipper Unconfirm (7.9.21) no longer confirm self-bill invoices when the Sales Order Control field is No. Instead, the programs display an MFG/PRO error message.
    Previously, the system displayed a Progress error but still posted the invoices.
    Product Change Control (PCC)
    You can now include five additional routing-related fields in a product change request (PCR) or product change order (PCO):
    WIP Item
    Purchase Order
    Line
    Move to Next Operation
    Auto Labor Report
    These fields correspond to those in the second frame of Routing Maintenance (14.13.1) and Routing Maintenance–Rate Based (14.13.2). You can update them when you choose the Routing Data Maintenance function in PCR Maintenance (1.9.2.1) or PCO Maintenance (1.9.2.13).
    Service/Support Management (SSM)
    Deferred Revenue Contracts
    This service pack includes two additions to the deferred revenue contracts functionality in SSM.
    New Utility
    A new utility program, Set Contract Revenue to Deferred (11.25.27, utsarev.p), lets customers who have upgraded from an earlier release to MFG/PRO eB2.1 take advantage of the deferred revenue enhancements added in MFG/PRO eB2.
    This utility checks for existing cash contracts that have the following settings in Contract Maintenance (11.5.13.1):
    Revenue Type is C.
    Bill Arrears is No.
    End Date is later than the current date.
    When you set Update to Yes, the utility makes the following changes to the selected contracts:
    Sets Revenue Type to D.
    Sets the contract deferred revenue account.
    Resets the contract line sales and discount accounts.
    Important: This utility does not create the required deferred records for the current billing cycle. You must recognize revenue manually for this cycle. After you run this utility, revenue is automatically recognized for future billing cycles when you run Revenue Recognition (11.5.18.21).
    Enhanced Access Control
    A site range has been added to the selection criteria in Revenue Recognition. This lets you use site security to control which users are allowed to recognize revenue for contracts associated with a given site.
    Previously, you could not use site security with this program.
    RTS Pricing
    The SSM return to supplier (RTS) functionality supports only manual pricing, even though RTS Maintenance (11.7.3.1) previously included Price Table and Discount Table fields.
    To avoid confusion, those two fields have been removed from RTS Maintenance. Additionally, the label for PO/RTS/Sched/RMA Rcpt Price Menu (1.10.2) has been changed to PO/Sched/RMA Rcpt Price Menu.
    Project Realization Management
    This service pack includes two enhancements to PRM.
    Loading Project Structure
    When adding line items to a project in Project Maintenance (10.1.1), you can now specify whether you want to explode the complete product structure or only add the components of the parent item when the parent includes subassemblies.
    Previously, the system automatically loaded the entire bill of material (BOM) into the project structure when you responded Yes to the following prompt:
    Load BOM into project structure?
    Now, when the parent item includes subassemblies, a second prompt displays:
    Load all structures?
    If you respond Yes to the second prompt, the system explodes the entire BOM and adds it to the project structure, just as before. However, if you respond No, only the components of the parent item are added.
    For example, this new feature supports a scenario where component items are sometimes built at a different site and shipped to the project site as part of inventory, and other times the component items are assembled as part of the project.
    Specifying Effective Date
    The system now prompts you for a GL effective date when you record project information in Project Activity Recording (10.5.13) or Project Labor Recording (10.5.14).
    Previously, the system used the current date.
    The new Effective Date field defaults to the current date. When Verify GL Accounts is Yes in Domain/Account Control (36.1), the specified date must be in an open GL calendar period.
    EDI ECommerce
    This service pack includes several enhancements to EDI ECommerce.
    Product Transfer Import Gateway
    A new inbound gateway has been added to support a scenario in which your customer is a distributor who has a product transfer/resale relationship with their own end customer. This new functionality is particularly useful for MFG/PRO users—especially in the food and beverage industries—who sell products to military distributors that in turn send them to military posts and require the supplier to bill each post directly for the quantity it receives.
    Using the inbound product transfer gateway, you can receive an EDI message (typically in ANSI 867 format, Product Transfer and Resale Report) at the end of a standard sales order cycle with your own customer—the distributor. Importing the product transfer document triggers an additional sales order cycle that lets you create a shipment, as well as optionally confirming it and producing an invoice for the end customer based on the quantity they received. Optionally, this process can also start another sales order cycle for a negative quantity so you can issue a credit memo to the distributor.
    In effect, this process lets you transfer the financial liability from your direct customer—the distributor—to the end customer. Sales orders created by importing the product transfer/resale documents are not tied to the original sales order used to provide goods to the distributor. This allows flexibility during the distribution process; the distributor can procure a large quantity of an item on one sales order, break the shipment into smaller quantities for multiple end customers, and then send a product transfer document for each. On what began as a single sales order, you can ultimately bill multiple end customers.
    Note: In addition to the new inbound gateway, you use existing EDI ECommerce processing to manually export the invoices and credit memos that complete the business cycle. Additionally, if you fill orders to your ordering distributor using your own warehouse or distribution center, you can use existing functionality for such activities as exchanging shipping orders and shipping advice documents with the warehouse. These existing capabilities are outside the business cycle introduced by the new gateway.
    Gateway Variables
    The new functionality is based on an inbound gateway that runs when you import the product transfer document (867) using Document Import (35.1). The new gateway is very similar to the standard sales order gateway. The table below summarizes the gateway variables that control processing for the new functionality.
    Note: The shipper and invoice-related variables control processing for both the end-user sales order and the distributor sales order, if one is created.
     
    Gateway Variable
    Effect When Yes
    ed_create_shpr
    Automatically generates a shipper for the sales order created when you import the Product Transfer and Resale Report
    ed_confirm_shpr
    Automatically confirms the shipper
    ed_shpnbr_as_invnbr
    Sets the invoice number to equal the shipper number
    ed_post_invoice
    Automatically posts the invoice; for distributor’s negative-quantity sales order, this is a credit memo
    ed_cr_neg_so
    Indicates whether the sales order is for a negative quantity
    Business Cycle
    The following is a typical business cycle using this type of document:
    1
    Your customer—the distributor—sends you a purchase order (such as ANSI 850, UCS 875, or EDIFACT ORDERS), which you import to generate the primary sales order.
    2
    You complete the sales order cycle, shipping the product and invoicing the distributor.
    3
    The distributor delivers the product to their end customer.
    4
    The distributor sends you the Product Transfer and Resale Report document in EDI format.
    5
    When you import the document, the transformation map creates MFG/PRO repository sequences for both positive and negative (if required) quantities. These in turn become sales orders in MFG/PRO. The system uses the values of gateway variables to determine whether to create a shipper, confirm it, and post the invoice. For a negative sales order, the invoice becomes a credit memo.
    Note: Creating the negative sales order first, where applicable, avoids potential issues with inventory availability.
    6
    Regardless of whether this negative order was created, the system uses the existing EDI ECommerce sales order load gateway to create a sales order for the distributor’s end customer. Depending on gateway variables, it also creates and confirms a shipper for the specified quantity, as well as creating and optionally posting an invoice based on this end-customer sales order.
    Note: The import file may include a sales order number (variable ed_so_no). The gateway uses that number if it is provided. Otherwise, a new number is generated based on Sales Order Control settings. Optionally, you can consider creating a transformation function that lets you distinguish transfer-related sales orders from other orders; for example, by assigning a different prefix.
    7
    After the automatic or manual shipper/invoice process is completed, you use Invoice Export (35.4.3) to export the invoice to the end customer and the credit memo to your own customer.
    Gateway Processing Sequence
    A new Gateway Process Priority field has been added to MFG/PRO Definition Maintenance (35.15.10).
    ECommerce EMT Manager (35.22.13) uses the specified value to determine the relative order in which multiple EMT documents are processed at the primary business unit (PBU), secondary business unit (SBU), or tertiary business unit (TBU). Leave the field set to the default 0 (zero) to continue with the current functionality.
    Note: You can also use this feature to control the processing sequence of multiple document types in a non-EMT context.
    Previously, ECommerce functions always processed documents in alphabetical sequence based on the Progress program names of the gateways. In some EMT scenarios, this could lead to errors; for example, the PBU’s system might attempt to import an advance ship notice (ASN) before it imported the associated purchase order acknowledgement.
    Note: When the system loads standards-neutral format (SNF) files for processing based on the new sequence logic, it loads all files at the same time and then performs transformation and gateway processing. Previously, the system always loaded one SNF, transformed it, and did gateway processing before loading the next SNF.
    Price Catalog Export
    An EDI document containing item and price information can now be exported using Price Catalog Export (35.4.17). For example, this exported document can be used to transmit price data to a catalog system or to a customer who needs the latest list of prices.
    Report Output Enhancement
    A Display Passed/Failed/Both field has been added to most EDI ECommerce document import and export processing programs to control whether the output report is limited to either passed documents or failed documents, or includes both.
    For example, setting the field to Failed lets users immediately identify documents that experienced processing problems.
    Supplier Shipping Schedule Export
    A new Include Only EDI Schedules field has been added to Supplier Shipping Schedules (35.4.8). It provides more control over the way supplier schedules are selected for export based on the setting of EDI Schedules in Scheduled Order Maintenance (5.5.1.13).
    No (the default): Supplier Shipping Schedules disregards the value of EDI Schedules when selecting schedules for export. If the system cannot find valid associated settings in Trading Partner Parameter Maint (35.13.10), errors result. This is the functionality available before the new field was added.
    Yes: The system limits the selection to schedules that have EDI Schedules set to Yes in Scheduled Order Maintenance.
    By setting the field to Yes, you can now use the EDI Schedules field to control which schedules you want to export. This prevents you from having to review error messages associated with schedules that should not be exported.