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 4
    Service Pack 4 for MFG/PRO eB2.1 includes all ECOs closed between August 19, 2005, and January 27, 2006. A few significant changes introduced with ECOs that modify product features are highlighted in this section.
    In addition to these ECO changes, a change to the Progress requirements has been made. Beginning with MFG/PRO eB2.1 SP4, Progress OpenEdge 10B Service Pack 3 is now a requirement for installation.
    Lean Manufacturing Updates to Kanban Module
    This service pack includes additional Lean Manufacturing enhancements to the Kanban module. These updates provide the same functionality previously added in service packs to MFG/PRO eB2.
    Using new Kanban features, you can now:
    Use a new menu program, Kanban Card Management (17.22.16.16), to manage multiple loops by analyzing and optionally implementing system-generated recommendations to create, activate, close, or inactivate cards to bring the loops back into conformance with optimum loop sizing. This multifunction program also lets you add or remove a fixed number of cards from multiple loops, as well as delete inactive cards. You can print new and activated cards before leaving the program.
    Use Kanban Workbench (17.22.23.1) or Supermarket Workbench (17.22.23.2) to reconcile the actual number of active replenishment cards in a loop with the system-recommended number of cards. When reconciling cards, the system creates, activates, or inactivates cards as needed to rebalance the loop.
    For two-card loops, control how replenishment card reconciliation affects the number of move cards.
    When card reconciliation creates or activates cards, print them directly from the workbench.
    Use Kanban Control (17.22.24) settings to select the logic the system uses when phasing in new cards or phasing out unneeded ones.
    Instead of having the reconciliation function inactivate unneeded cards, prompt the user to inactivate them next time they are recorded in Kanban Consume/Post (17.22.19.1).
    Use regeneration enforcement to display a warning or error message when a card is recorded if the system determines that key information on the card—kanban quantity, BOM, routing, and so on—no longer matches the loop master record.
    Control your kanban process flow by enforcing the sequence in which cards must be recorded. For example, you can specify that users cannot record a card in Kanban Acknowledge unless it is first recorded in Kanban Consume/Post. You can specify different enforcement settings for individual loops or have loops use the system-level settings defined in Kanban Control.
    From Kanban Dispatch List Processing (17.22.18.1), export dispatch lists to loop suppliers as electronic data interchange (EDI) kanban shipping schedules using EDI ECommerce.
    Note: The new export gateway that supports this feature uses the same standards-neutral format (SNF) and the same exchange definition as standard 830 and 862 schedules. Although a new implementation definition is required, you can use the current Schedule exchange definition for exporting dispatch lists.
    Automatically change the status of cards to Shipped when Document Import (35.1) loads EDI advance ship notices (ASNs) from loop suppliers. The system identifies eligible loops and calculates the number of cards to be updated based on ASN information.
    Use several additional programs on the new Kanban Dispatch Menu (17.22.18) to more efficiently manage cards placed on dispatch lists.
    Kanban Dispatch Maintenance (17.22.18.2) lets you select an individual card based on the dispatch ID and kanban ID. You can then view dispatch-related data, as well as update some associated information as needed.
    Three additional view and reporting programs let you see information about dispatched cards.
    Note: Kanban Dispatch List Processing has been moved to 17.22.18.1 on the new menu. It was previously at menu location 17.22.19.13.
    Automatically update card dispatch status when you record ship or fill/receive transactions, receive a PO shipper, or import an ASN for a card that has been placed on a dispatch list.
    Consume a batch of cards using two new menu programs:
    Use Kanban Consumption Import (17.22.19.20) to import comma-delimited records that identify a supplier, item, and quantity to consume. The system identifies eligible loops, calculates the number of cards required, and automatically updates cards to be consumed.
    Use Supplier Kanban Consumption (17.22.19.21) to identify eligible loops based on selection criteria. Then specify the number of cards to be consumed in each loop.
    Automatically change the status of cards to Full when confirming the supplier’s shipping document using PO Shipper Receipt (5.13.20). The system identifies eligible loops and calculates the number of cards needed based on information in the shipper.
    Identify suppliers that can have automatic card updates made during ASN import or PO shipper receipt based on a new Kanban Supplier field in Supplier Maintenance (2.3.1).
    For programs that automatically select cards for status updates, use two new fields in Kanban Master Maintenance (17.22.4)—Qty Mismatch Method and Rounding Threshold—to define the rules the system uses when the quantity specified is not a multiple of the kanban quantity.
    Create new loops based on comma-delimited records imported using Kanban Workbench Import (17.22.23.14).
    Perform card reconciliation functions on new or updated loops while importing records using Kanban Workbench Import. Optionally, print new or activated cards from the same program.
    In the view programs on the Kanban Transactions Menu (17.22.19), drill down to the operation-history level when related records are associated with a kanban transaction.
    Set up optional, reference-only label definitions using Kanban Label Definition Maint (17.22.16.18) to specify the appearance and content of labels placed on kanban containers. Associate a label with a kanban loop in the new Kanban Label field in Kanban Master Maintenance.
    For information on setting up and using the added features, see User Guide: Kanban (item 78-0593F), which includes an updated version of the Kanban chapter from MFG/PRO eB2 User Guide Volume 3: Manufacturing. This new product information is available in Portable Document Format (PDF) on the latest Supplemental Documents on CD, as well as on the QAD ServiceLinQ Web site, where it is included with the user guide set for MFG/PRO eB2.
    General Ledger
    A new Offset Account for GL Import field has been added to General Ledger Control (25.24).
    Important: You must enter a valid account number in the new field before you can run Transaction Import (25.19.15).
    The new field supports a software update that lets Transaction Import correctly process a file containing more than 9999 lines by creating multiple GL references. Previously, all lines were imported into a single GL reference, even though the maximum field size for reference lines is 9999. This created potential problems in functions such as Standard Transaction Maintenance (25.13.1), since that program cannot retrieve line numbers greater than 9999.
    Now, when you import a large file, the system processes the first 9998 lines for a GL reference, then uses line 9999 to record the accumulated value of those lines. It creates a transaction detail record for that amount against the specified offset account. The system next creates a new GL reference, continuing with more lines—and more references, if required—until it reaches the end of the import file. (The last line in the last reference—even if it is not line 9999—includes an offset transaction for the total amount represented by that GL reference.) The system uses the offset transactions to keep the GL reference in balance so that it posts correctly.
    New Accounts Receivable Utility
    A new utility, Update AR Records for P4Z2 (27.25.3, utarrnd.p), updates AR master table (ar_mstr) records to address incorrect discrepancies between the ar_base_amt and ar_base_applied fields. Previously, an exchange rate rounding issue created incorrect values in these fields.
    Accounts Payable Reports
    A new Display Open Vouchers with Amount = 0 field has been added to AP Aging by Voucher Date Report (28.17.4) and AP Aging by Due Date Report (28.17.5). The field controls whether the report output displays open zero-amount vouchers.
    Previously, open zero-amount vouchers were always displayed.
    Service/Support Management
    A new Next Date field in Call Queue Manager (11.1.6) lets you specify the first next activity date the system should use for finding calls to display.
    This field is important when calls are being displayed by next activity date and end user, based on setting Queue Manager to 0 in Call Management Control (11.1.24).
    The default is the current system date. If you have calls that are overdue, you should change the default to a date before the oldest next activity date to see all the calls. You can clear the date field to see all calls; however, this may impact performance since the system must sort through all calls in the database.
    1099-MISC Reporting
    The system now validates additional IRS miscellaneous income tax form boxes in the following programs:
    1099-MISC Report (28.20.1)
    1099-MISC Form Print (28.20.2)
    1099-MISC Magnetic Media Report (28.20.3)
    Boxes 15a and 15b correctly display in these reports.
    Advanced Repetitive
    A new Order Multiple field has been added to Repetitive Picklist Calculation (18.22.3.1) to let users choose how the system calculates the quantity to transfer on the picklist.
    Yes (default): The system determines the number of items to be transferred (quantity required) and then rounds that number up based on the order multiple defined in Item-Site Planning Maintenance (1.4.17), Item Planning Maintenance (1.4.7), or Item Master Maintenance (1.4.1).
    No: The exact quantity required prints on the picklist and no rounding is applied by the system. Set this field to No when you are using lean manufacturing techniques and do not want any extra items on the shop floor.
    EDI ECommerce
    This service pack includes additional functionality to support exchange of EDI documents related to warehouse distribution.
    Two new export gateways have been added:
    Use DO Packing List Export (35.4.16) to export an EDI document containing shipping instructions in the form of a packing list generated based on a distribution order. This is designed to request a warehouse to transfer products to another warehouse. It supports such EDI standards as ANSI X12 940, Warehouse Shipping Order.
    An existing gateway, Packing List Export (35.4.15), performs a similar function for transferring products from a warehouse based on the customer’s sales order. It exports a request to ship goods from a warehouse to the customer.
    To use this gateway, three additional parameters must be defined in Trading Partner Parameter Maint (35.13.10):
    Logical parameter: Send DO Packing List, set to Yes
    Character parameter: DO Packing List Doc Name, set to the name of the associated MFG/PRO document definition
    Integer parameter: DO Packing List Doc Vers, set to the version number of the associated MFG/PRO document definition
    Use Warehouse Shipment Advice (35.4.18) to inform the receiving warehouse that products have been shipped from another warehouse. This document type supports such EDI standards as ANSI X12 943, Warehouse Stock Transfer/Shipment Advice.
    To use this gateway, three additional parameters must be defined in Trading Partner Parameter Maint (35.13.10):
    Logical parameter: Send Warehouse Shipment, set to Yes
    Character parameter: Warehouse Shipment Doc Name, set to the name of the associated MFG/PRO document definition
    Integer parameter: Warehouse Shipment Doc Vers, set to the version number of the associated MFG/PRO document definition
    Two new fields have been added to Packing List Export to let you refine the selection of documents to be exported.
    Export Only if Lines Picked: Set this to Yes to limit the selection to lists for order lines with a quantity picked greater than zero.
    Export Only if Shipper Exists: Set this to Yes to limit the selection to lists for order lines with a quantity shipped greater than zero.
    Leave the fields set to No (the default) to have the program work the same way it did before the new fields were added; lines matching the selection criteria are selected regardless of picking or shipper status.
    Supplier Consignment Inventory
    A number of modifications have been made to the Supplier Consignment Inventory module to address issues related to financial transactions generated during inventory receipts, usages, and vouchering:
    You can now specify if you want to track PO costs at the time of receipt or usage.
    The system now tracks cost information at a more detailed level, ensuring that you can generate accurate reports and reconcile costs in the general ledger.
    Tax calculation for consigned inventory has been simplified.
    A new utility has been provided to create pending voucher detail records and update cost point data.
    PO Cost Point
    A new PO Cost Point field in Supplier Consignment Control (5.18.24) lets you choose whether to recalculate purchase order cost at time of usage or retain the cost from the time of physical receipt. This same field can be set for a specific supplier or supplier/item combination in Supplier/Item Controls Maintenance (5.18.1).
    Tracking Cost Details
    The system now maintains additional PO cost details required for accurate reporting. These details are created during PO receipt. When the PO Cost Point field is set to usage, the system records changes in item/PO unit price and changes in exchange rates as inventory is used.
    When usage details with different costs or exchange rates exist during vouchering, a message displays letting you choose to update these records manually. When you respond No to this prompt, MFG/PRO automatically processes the details on a first-in first-out basis. When you respond Yes, a new frame displays all the detailed records and you can select the ones you want to voucher. Multiple pending vouchers associated with a single receiver are correctly processed.
    Note: When you use background processes such as ERS Processor (28.10.13) or load supplier invoices using ECommerce Document Import (35.1), the system always uses the first-in first-out method to update the detailed records.
    When the vouchering cycle is complete, additional cost data is included during archive/delete in the following programs:
    Uninvoiced Receipt Delete/Archive (28.22)
    Closed PO Receipt Delete/Archive (5.22)
    Reporting and Reconciling Cost Details
    Unvouchered Receipts as of Date (5.13.10) and Purchase Receipt Report (5.13.5) now correctly calculate and display the purchase price variance (PPV) when the exchange rate, GL cost, or PO price have changed between the time of physical receipt and the time of usage of consigned inventory (PO Cost Point is set to Usage). It also now displays cost details and accurately calculates and displays quantities and report totals.
    Other reports, browses, and inquiries that help users reconcile PPV on receipts and supplier-consigned transactions with amounts booked to the general ledger have been updated to use the new cost details and calculate correct totals. These include:
    Receipt Transactions Report (5.9.14)
    Voucher/Standard Cost Variance Report (28.17.1)
    Voucher/PO Cost Variance Report (28.17.2)
    Purchase Receipt Inquiry (5.13.3) and PO Receipt Cost Browse (5.13.3)
    In addition, the calculation that is performed by various purchasing reports that include the option Use Total Standard Cost has been normalized so that they all display the same results.
    Tax Calculation
    For supplier-consigned orders (discrete and scheduled), tax is no longer accrued at physical receipt of consigned inventory. The system ignores the Accrue Tax at Receipt setting in Tax Rate Maintenance (2.13.13.1). Tax on supplier-consigned orders is now calculated only at time of usage.
    New Utility Program
    To support the enhancements to Supplier Consignment, you must run the new utility Create Pending Voucher Detail (5.25.6, uxcrpvod.p) before processing any supplier consignment transactions. This is required to properly voucher and report consigned material.
    This utility:
    Creates a single pending voucher detail record for each existing pending voucher master record in the database.
    Moves exchange rate data out of the pending voucher master record into the pending voucher detail record.
    Updates the PO consignment cost point on all PO headers marked as consigned or having attached consigned PO lines.
    Customer Consignment Inventory
    Customer Consignment usage functions now perform price-list lookups at the time of usage for scheduled orders in the following programs:
    Cycle Count Results Entry (3.14)
    Aging Inventory Update (7.18.10)
    Aging Inventory Batch Update (7.18.11)
    Inventory Usage Create (7.18.13)
    Authorization Usage Create (7.18.14)
    Sequenced Usage Create (7.18.15)
    Shipper Usage Create (7.18.19)
    Usage Create Undo (7.18.22)
    This function is only invoked when the underlying sales order is from a customer consigned scheduled order with a price list.
    Adding this capability makes Customer Consignment more consistent with Supplier Consignment. However, an SO Price Point field (comparable to the PO Cost Point field) is not being introduced.
    Previously, customer consignment usage functions ignored the price list information for scheduled orders; invoices were created with the price at shipment rather than the price at usage.
    Product Structure, Service Structure, Formula/Process
    When you copy a product structure, a service structure, or a formula to create a new one, the system copies components from the source structure and adds them to the destination structure. When the destination already has existing components, the system displays a warning and prompts you to continue.
    If you choose to continue, a new field, Combine Common Components, determines how the system manages updates when the same item exists in both the source and destination structures:
    No: The system overwrites destination component quantities with component quantities defined in the source.
    Yes: The system combines component quantities being copied from the source structure with the component quantities of the destination structure.
    Previously, the system always overwrote the target components.
    The option has been added to the following programs:
    Product Structure Copy (13.9)
    Service Structure Copy (11.19.9)
    Formula Copy (15.8)
    Intersite Requests
    You can no longer leave the due date blank in the following two programs, since this created records that were not recognized by MRP:
    Intersite Request Maintenance (12.15.1)
    Intersite Demand Confirmation (12.17.1)
    To ensure that the correct relationship is maintained between the shipping dates and due dates, a new field has been added to Intersite Demand Confirmation. The new header Due Date field lets you enter the date the items are due at the receiving site. The system calculates the default ship date based on:
    The header due date from the request header
    The load, transit, and unload lead times defined in Transportation Network Maintenance for the transportation mode specified on the detail portion of the request.
    With this change, Intersite Demand Confirmation now manages the relationships among dates in the same way as Intersite Request Maintenance.
    In addition, two new messages have been added that display when due dates or shipping dates are changed on existing records and the new dates are not the same as the dates the system calculates based on the setup associated with transportation ID. Normally, the lead times defined in Transportation Network Maintenance provide the correct defaults.
    New Inventory Report
    A new Device History Record Report (3.6.20) has been added to the Inventory Reports menu. This report displays the production history of a finished device—if it is a serialized end item—or an end lot of finished devices. Multiple levels of component history can be included.
    The output of this report can be used by medical device manufacturers to help satisfy the reporting requirements outlined in Food and Drug Administration 21 CFR Part 820.