MURM - Initialization Parameter Maintenance

New features added, version 7.5.2, 7.5.3, 8.1, 7.5.4, 8.4, 7.5.4 Patches, 8.4 Patches, 7.5.4R4, 8.4R4, 8.5.1, 8.5.2, 8.6R1

Program MURM, Initialization Parameter Maintenance, is used to maintain the system and feature parameters throughout NDS. Do not delete the COMMON application user records from this program as these are the default settings for each application user.

The parameters are set up by Oracle user, by application user, or by COMMON user. Application users are set up in program MUSC, User Security Maintenance. Some parameters are only valid for the COMMON user.

Parameter determination is case sensitive. If you have an application ID that matches your Oracle User ID in both character and case, there may be problem. This is just one of the many reasons NDS recommends against the use of an application ID that matches the Oracle User ID.

When determining which parameter to use, the system uses the following order.

Application ID

Oracle User ID (if no setting for application ID found)

COMMON (if no setting for either application ID or Oracle User ID found)

Parameters can be categorized according to the module or program to which they apply.
Some parameters can be set up for specific enterprises, sales locations, or plant codes. If such a parameter is set up for one plant but not for the others, the plants for which the parameter has not been set up will use the setting for the default parameter settings.
System parameters include those used to open the NDS Help, the NDS Tutorials, Oracle Discoverer for web-powered NDS, and the report server for web-powered NDS. This program also governs the content and placement of the floating toolbar and the drilldown depth gage.
For each parameter, you can press the Comments $image\ebx_-515784695.gif$ button to view and maintain usage comments for the parameters. See the Viewing and Maintaining Parameter Usage Comments for more information.

Viewing and Maintaining Parameter Usage Comments

Usage comments are used to define the usage of specific parameters in program MURM, Initialization Parameter Maintenance, and can be accessed by clicking on the [Comments] $image\ebx_-515784695.gif$ button. Usage comment records are created automatically for each parameter record in program MURM, Initialization Parameter Maintenance. New records cannot be created here.

1. Query the parameter value for which you wish to view or maintain the usage comment.

2. In the Usage field, enter the desired text for the comment.

3. When all changes have been made, press [Commit].

Using this Program

1. Set the Show COMMON Only flag to on to view only the parameters entered for the COMMON user.

2. Set the Exclude TOOLBAR Murms flag to on to hide all toolbar, window settings, and drill down gage parameters when querying parameters on any of the tabs.

3. The Sort By pop-list determines the orders in which the parameters are displayed on the tabs. Choices are:

Murm/User
User/Murm
Category/Murm/User
Category/Program/Murm
Program/Murm

4. You can restrict the parameters displayed on the tabs using the Category pop-list. In the Category pop-list, select the category for which you wish to view the parameters.

5. You can press the [Remove User Murms] button to delete all application or oracle user level parameters settings for the selected Key.

6. This program contains four tabs for the entry and maintenance of parameters.

Standard MURMS Tab: Displays standard NDS parameters.
User MURMS Tab: Displays the parameters entered for a specific application user ID or Oracle user ID. The user queried is entered in the Query User field.
Custom MURMS Tab: Displays the custom parameters.
Missing Tab: Displays standard parameters for which no entry exists in this program. To create an entry for these parameters, set the Reinstate Murm flag to on.

7. When entering new parameters, in the App User field, enter the application ID, Oracle User ID, or enter COMMON as the user for which you are creating the parameter. The value will default to the current logged in application user ID.

8. In the Key field, enter the parameter for which you are defining a value setting. You can press the [Duplicate Record] $image\ebx_993918121.gif$ button in the NDS button bar to copy the settings of this field and the other fields from the previous parameter record.

9. In the Value field, enter the value for this parameter.

10. The Case pop-list determines the case or type of value that can be entered for the parameter. For new custom parameters, select the proper case for the values for this parameter. Otherwise, this pop-list should not be changed. Pop-list values include:

Upper
Mixed
Lower
Numeric
Integer
Date

11. Set the Y/N Only flag to on if this parameter value can only be Y or N. For new custom parameters, set this flag to the desired setting. Otherwise, the flag should not be changed.

12. In the Category field, enter the category for this parameter. Standard parameter categories include:

ACCOUNTING
ACCTS PAYABLE
ACCTS RECEIVABLE
BACK ORDERS
CREDIT CARDS
CUSTOMER
DISTRIBUTION
ECOMMERCE
EMAIL
GIFT CARDS
G/L
INVENTORY
INVOICING
MARKETING
ORDER ENTRY
PCR
PLANNING
PRICING
PROJECTS
PURCHASING
RECEIVING
RETURNS
SHIPPING
SYSTEM
TOOLBAR
VENDOR
WORK ORDERS
WORKFLOWS
XEPHR

13. In the Program field, if the parameter is for a specific program, enter that program here.

14. In the Type pop-list, the type indicates whether this parameter is system wide or if can be set up for specific sales locations, plants, or enterprises. Choices are:

Regular: The parameter is system wide for the application user.
Plant: The parameter can be set up by plant. If the plant code is appended to the end of the Key parameter _PP, the parameter is only applicable to that plant. Otherwise, if there is no plant code appended to the end of the Key parameter, the parameter is applicable to all plants for which a plant specific parameter has not been set up.
Location: The parameter can be set up by sales location. If the sales location code is appended to the end of the Key parameter _LLL, the parameter is only applicable to that sales location. Otherwise, if there is no sales location code appended to the end of the Key parameter, the parameter is applicable to all sales locations for which a sales location specific parameter has not been set up.
Enterprise: The parameter can be set up by financial enterprise. If the financial enterprise code is appended to the end of the Key parameter _FFF, the parameter is only applicable to that financial enterprise. Otherwise, if there is no financial enterprise appended to the end of the Key parameter, the parameter is applicable to all financial enterprises for which a financial enterprise specific parameter has not been set up.

15. When all fields have been entered, press [Commit].

Accounting Parameters

Unless otherwise noted, these parameters have the ACCOUNTING category

Hold Codes Unreleasable in program OEHR, Credit Hold Release

OEHR_EXCLUDE_HOLD: This parameter determines the list of hold codes that will not be displayed for release in program OEHR, Credit Hold Release, and corresponds with the Exclude Hold Codes field in program OEHR, Credit Hold Release. If an entry is made for this parameter, those entries will be displayed in the Exclude Hold Codes field in program OEHR, Credit Hold Release, and that field will not allow updates. If this parameter's value is left blank, then entries can be made in program OEHR, Credit Hold Release, in the Exclude Hold Codes field.

Valid values are any of the valid hold codes entered in program CMHM, Hold Code Maintenance, separated by commas.

OEHR_INCLUDE_HOLD: This parameter determines the list of hold codes that will be displayed for release in program OEHR Credit Hold Release, and corresponds with the Query List of Hold Codes field in program OEHR, Credit Hold Release. If an entry is made for this parameter, those entries will be displayed in the Query List of Hold Codes field in program OEHR, Credit Hold release, and that field will not allow updates. If this parameter's value is left blank, then entries can be made in program OEHR, Credit Hold Release, in the Query List of Hold Codes field.

Valid values are any of the valid hold codes entered in program CMHM, Hold Code Maintenance, separated by commas.

OEHR_EXCLUDE_STATUS: This parameter determines the list of order statuses to exclude from the query, separated by commas. This parameter is used in conjunction with the Exclude Hold Codes and Query List of Hold Codes list. This parameter corresponds with the Exclude Status field. If an entry is made for this parameter, those entries will be displayed in the Exclude Status field and that field will not allow updates. If this parameter's value is left blank, then entries can be made into the Exclude Status field.

If an entry is made for this parameter and either the OEHR_EXCLUDE_HOLD parameter or the OEHR_INCLUDE_HOLD parameter, then only orders with that status and hold codes will be affected.

For example, if you wanted to exclude hold code 'Z' but only for quotes, you would enter Z for the OEHR_EXCLUDE_HOLD parameter and Q for the OEHR_EXCLUDE_STATUS parameter. Status 'O' orders that were assigned the 'Z' hold code would still display.

If you wanted to exclude an order status for all but a few specific hold codes, then you would enter the list of hold codes for the OEHR_INCLUDE_HOLD parameter, and enter for the OEHR_EXCLUDE_STATUS parameter.

For example, to display only 'Z' hold codes for quotes, you would enter Q for the OEHR_EXCLUDE_STATUS parameter and Z for the OEHR_INCLUDE_HOLD parameter.

Valid values are any of the valid sales order statuses. For example: Q, I

Open order status values include:
Q - Quotation
I - Incomplete
O - Complete
J - Confirmed-Incomplete.

Return to See Also List

Accounts Payable Parameters

Unless otherwise noted, these parameters have the ACCTS PAYABLE category.

Accounts Payable Payment Selection Defaults

APPS_PG3_SORT: This parameter determines the default value for the sorting of invoice on the third page of program APPS, Payment Selection of Invoices by Range. If nothing is assigned to this parameter, the default is Vendor ID.

Valid values include:

DD - Discount Due Date
ID - Invoice Due Date
IN - Invoice Number
PA - Payment Amount
VN - Voucher Number
N - Vendor Name
VI - Vendor ID

Start Field for program APVM, Voucher Entry/Maintenance

APVM_START_IN_PO: This parameter determines whether the cursor will start in the PO field on new records when navigating to the voucher page in program APVM, Voucher Entry/Maintenance.

Valid values include: Y or N.

Return to See Also List

Accounts Receivable Parameters

Unless otherwise noted, these parameters have the ACCTS RECEIVABLE category.

Accounts Receivable Inter-Company Invoices

SHOW_INTER_COMPANY_INVOICES_AR: This parameter determines whether invoices from financial enterprises other than the logged in financial enterprise will be displayed for payments and adjustments in program ARPE, Cash Receipts Entry and program ARAD, Accounts Receivable Adjustments Entry.

Valid values include: Y or N. When set to Y, invoices for all financial enterprises can be displayed in program ARPE, Cash Receipts Entry, and program ARAD, Accounts Receivable Adjustments Entry, for payment and adjustment. When set to N, only invoices for the current logged in enterprise will be displayed in the programs for payment or adjustment.

Accounts Receivable System Generated Invoices

AR_INV_PREFIX: This parameter allows up to 2 characters to be appended to the beginning of an invoice number generated by the system (i.e. to the front of the invoice). Prefix number plus invoice number can not exceed 10 characters or an error will be raised.

Accounts Receivable Posting Date for Sales Order Processing with program OESJ, Sales Order End of Day and Journals

AR_POSTING_DT_SOURCE: This parameter determines whether the posting date for the invoices processed through program OESJ, Sales Order End of Day and Journals, will be the invoice date or the date on which program OESJ, Sales Order End of Day and Journals, was run.

Valid values include: INV or POST. When set to INV, the posting date for the invoices is the invoice date. When set to POST, the posting date for the invoices is the date entered in program OESJ, Sales Order End of Day and Journals.

Accounts Receivable Record Archive Setup

ARPG_ARCHIVE_RECORDS: This parameter determines whether accounts receivable records will be deleted or archived when program ARPG, AR Posted Journal Purge, is run.

Valid values include: Y or N. When set to Y, the purged accounts receivable records will be moved to the arpost_detail_hist table instead of being deleted. When set to N, or non-existent, the records are deleted when program ARPG, AR Posted Journal Purge, is run.

Comment Types for Invoice Printing

ARIP_PRINT_COMMENT_TYPE: This parameter determines the comment type that will print on the invoice when program ARIPL, Invoice Print (Laser), is run. This comment type is in addition to the OE comment type that prints on the report by default.

Valid values are any standard or user-defined comment type that you wish to print on the report.
For custom version of these reports, this functionality must be added. Contact NDS Professional Services for more information.

Customer Statement Batch Transmit Report

ARSS_BATCH_XMIT_RPT: This parameter determines the report that will be run when transmitting customer statements. The default is ARSS.

The valid value is the report name for the report to run for batch transmitting customer statements from program ARRS, Review Statements or a job stream. Drilldown keys with report parameters must be specified in program UTKM, Maintain Drill Down Keys, for the report entered here.

UTL_HTTP_TIMEOUT: This parameter is so you can set the http requests longer than Oracle default value of 60 seconds.

Exclude Credit Balances when Selecting Customers in program ARRS, Review Statements

ARRS_EXCLUDE_CREDIT_BAL: This parameter determines the default setting of the Exclude Credit Balances when Selecting All flag in program ARRS, Review Statements.

Valid values are Y or N. When the parameter is set to Y, the flag will default to on. When the parameter is set to N, the flag will default to off.

Invoice Batch Transmit Report

ARPF_BATCH_XMIT_RPT: This parameter determines the report that will be run when transmitting invoices for sales orders. The default is ARIPX.

The valid value is the report name for the report to run for batch transmitting sales order invoices from program ARPX, Cash Receipts Entry Reversal, or a job stream. Drilldown keys with report parameters must be specified in program UTKM, Maintain Drill Down Keys, for the report entered here.

Return to See Also List

Backorder Parameters

Unless otherwise noted, these parameters have the category BACK ORDERS.

Backorder Notification Method

New parameters added, 7.5.2

These parameters determine whether the backorder notification in program BONO, Back Order Notify, will be sent to the customer as a PDF attachment of report OEBOX, Backorder Notify Report, or as an inline text message through email or fax. Additional set up is also performed for this program for emailing and faxing purposes.

Additional parameters include those to define an expiration period for the outgoing notifications, to include the defined brand name in the notification message, to re-price stocked items at the time of notification, and the defaults for item notify percentages and days in program ICMM, Inventory Master Maintenance.

These parameters should be set up for the COMMON user.

BONO_BRAND_NAME: This parameter determines the brand name included in the notification sent.

Valid values are the desired brand name. When the notification is sent, the brand name will be included in the notification.

BONO_CRDR_CODE: This parameter determines the reason code used on sales orders when re-ordering items from customer responses to notifications sent out with program BONO, Back Order Notify.

Valid values are any sales reason code from program ARRM, Maintain Sales Reason Codes.

BONO_NOTIFY_EXPIRE: This parameter determines the number of calendar days in the expiration period. Replies received after the expiration date will not be processed. The expiration date is determined by adding the calendar days entered for this parameter to the notification date. This feature is only valid if you are using the API to accept responses from your customers and generate reorders using the notification ID.

Valid values are numeric.

BONO_NOTIFY_RPT_PATH: This parameter specifies the directory on database server for writing text files.

Valid value is the directory path with no trailing slash.

BONO_REPORT_METHOD: This parameter determines whether the message will be sent as an inline text message reporting which items are now available or as a PDF file generated from the report OEBOX, Backorder Notify Report, and attached to the email.

Valid values are MESSAGE_TEXT or PDF_ATTACHMENT.

MESSAGE_TEXT: The message will be sent as an inline text message reporting which items are now available. The message uses the mail/fax text information from program MURC, Report Class Definitions, for the OEBONO report class. Also included is a listing with the original order number, date, customer purchase order number, send-to name and address, and a list of items from the order which were not shipped but are now available. The subject line is prefixed with a sequence number that can be used as a reference number for the notification when the customer wishes to generate a new order. The text files generated are named in the format 'bono<seq>.txt'.

PDF_ATTACHMENT: The notification will be sent as a .PDF file generated from report OEBOX, Backorder Notify Report, and attached to the email.

BONO_REPRICE_OE: This parameter determines whether the item price is recalculated when the notification is sent.

Valid values are Y or N. When set to Y, when the notification is sent, the item price is recalculated. If the new price is not zero, and is different than the current price for the sales order line, the price is changed and the override flag is set to on for the sales order line. You cannot preserve override pricing on backorders when this feature is active.

BONO_RUN_MODE: This parameter determines the default operation mode for program BONO, Back Order Notify.

Valid values are B or N. When set to B, the default operation mode for program BONO, Back Order Notify, is Backorders. When set to N, the default operation mode is No Backorders.

BONO_SPOOF_FILTER_DISABLED: This parameter determines whether or not when the customer being processed does not match the customer on the other, the back order will be released and the items will be reordered.

Valid values are Y or N. When set to N, then if the customer being processed does not match the customer on the order then the backorder will not be released and items will not be reordered

DEF_BO_NOTIFY_PCT: This parameter determines the default percentage of the item's safety stock for which backorder notifications will be sent. This value is used as the default value in program ICMM, Inventory Master Maintenance, for new items and in program BONO, Back Order Notify, if an item does not have a percentage entered in program ICMM, Inventory Master Maintenance.

Valid value is numeric.

DEF_BO_NOTIFY_DAYS: This parameter determines the default number of days for which a sales order will be considered for backorder notification if one of the sales order lines is for this item. This value is used as the default value in program ICMM, Inventory Master Maintenance, for new items and in program BONO, Back Order Notify, if an item does not have a value entered in program ICMM, Inventory Master Maintenance.

Valid value is numeric.

Additional parameters used by program BONO, Back Order Notify, include the following with the category EMAIL:

MAIL_SMTP_CONNECT: Valid path to SMTP mail service
MAIL_DOMAIN: Domain name for mail service
MAIL_SENDER: E-mail address to used as from/reply to

Return to See Also List

Credit Card Parameters

Unless otherwise noted, these parameters have the category CREDIT CARDS.

Automatically Save Credit Card Information on Authorization

AUTOSAVE_CC_INFO: This parameter determines whether the credit card information on sales orders is updated automatically when the authorization is done.

*Valid values are Y or N. When set to Y, the credit card code is set to the pay type and the address is set to the payment values or the order header information. When set to N, the credit card information is saved when the payment is processed with program OESJ, Sales Order End of Day and Journals.

Define whether OESJ reauthorizes Credit Card on Back Orders

CC_BO_AUTO_AUTH: This parameter determines whether or not OESJ will re-authorize credit cards for back orders. Default setting is Y. If set to N, then credit cards won't get reauthorized on back orders during OESJ. Orders will also not go on hold if no reauthorization is done.

Payflow Pro Variable Setup

New features added, version 7.5.1, 7.5.3, 8.1, 7.5.4 Patches, 8.4 Patches

Payflow Pro variables should generally be set up for the COMMON user. If other users have different settings or you are restricting access to certain users, be sure to enter the settings separately for those users.

You can set up Payflow Pro variables for each plant code or sales location in which sales orders are entered. In the example below, the PP should be replaced with the plant code or sales location. Payflow Pro will look for a parameter with the plant code or sales location first, and if one does not exist, it will use the parameter without one. The CC_BY_SALES_LOCATION parameter indicates whether the PP indicates plant code or sales location.

All steps in the Setting up the Servlets on an Oracle Web Server section should have been completed before you complete these steps.

These parameters should be set up for the COMMON user.

CC_BY_SALES_LOCATION: This parameter determines whether or not the parameters in program MURM, Initialization Parameter Maintenance, are organized by plant code or sales location.

Valid values are Y or N. When set to Y, the PP in the below parameters indicates sales location. When set to N, the PP in the below parameters indicates plant code.
CC_PROCESSOR: This parameter indicates that credit card processing will be done through Payflow Pro.

Valid value is PAYFLOW
PAYFLOW_AUTH_DAYS: The number of days a Payflow Pro authorization is good for before the transaction needs to be reauthorized.

Valid values are numeric. Default value is 4.
PAYFLOW_AVS: This parameter determines whether you are using Payflow Pro address verification. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location.

Valid values are Y or N. If you are using Payflow Pro address verification, enter Y. Otherwise, enter N.
PAYFLOW_AVS_PP: This parameter determines whether you are using Payflow Pro address verification for this plant or sales location. The PP should be replaced with the desired plant code or sales location code.

Valid values are Y or N. If you are using Payflow Pro address verification, enter Y. Otherwise, enter N.
PAYFLOW_AVS_CVV_HOLD: This parameter determines what hold code the sales order will be placed on if when you are using Payflow Pro address verification or CVV code process, the verification fails for the CVV code or address check. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location.
PAYFLOW_AVS_HOLD and PAYFLOW_CVV_HOLD can be used separately allowing for hold codes to be different.

Valid values are any hold code from program CMHM, Hold Code Maintenance.
PAYFLOW_AVS_CVV_HOLD_PP: This parameter determines what hold code the sales order will be placed on in this sales location or plant if when you are using Payflow Pro address verification or CVV code process, the verification fails for the CVV code or address check. The PP should be replaced with the desired plant code or sales location code.

Valid values are any hold code from program CMHM, Hold Code Maintenance.

PAYFLOW_AVS_WARNING: This parameter determines whether when you are using Payflow Pro address verification, the order should be put on hold when the verification fails. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location.

Valid values are Y or N. When set to Y, the order will be put on hold. When set to N, a warning will be displayed to the user, but the order will not be placed on hold.
PAYFLOW_CVV_RESPONSE_TYPE: This parameter determines whether Payflow Pro will return only the normal response code or the normal response code and a CVV Result code. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location.

Valid values are 0 or 1. When set to 0, Payflow Pro should return only the normal response code. When set to 1, Payflow Pro will return both the normal response code and a CVV Result Code.

Payflow Pro CVV Result Codes
M: Match
N: No Match
P: Not Processed
S: Merchant indicated CVV code not present on card
U: Issuer is not certified and/or has not provided encryption keys
PAYFLOW_CVV_RESPONSE_TYPE_PP: This parameter determines whether Payflow Pro will return only the normal response code or the normal response code and a CVV Result code for this plant or sales location. The PP should be replaced with the desired plant code or sales location code.

Valid values are 0 or 1. When set to 0, Payflow Pro should return only the normal response code. When set to 1, Payflow Pro will return both the normal response code and a CVV Result Code.

Payflow Pro CVV Result Codes
M: Match
N: No Match
P: Not Processed
S: Merchant indicated CVV code not present on card
U: Issuer is not certified and/or has not provided encryption keys
PAYFLOW_CVV_WARNING: This parameter determines whether the warning message from the credit card processor will be displayed if the PAYFLOW_CVV_RESPONSE_TYPE is set to 1. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location.

Valid values are Y or N. When set to Y, the warning message from the credit card processor will be displayed. When set to N, the warning message will not be displayed.
PAYFLOW_CVV_WARNING_PP: This parameter determines whether the warning message from the credit card processor will be displayed for this plant or sales location if the PAYFLOW_CVV_RESPONSE_TYPE is set to 1 The PP should be replaced with the desired plant code or sales location code.

Valid values are Y or N. When set to Y, the warning message from the credit card processor will be displayed. When set to N, the warning message will not be displayed.
PAYFLOW_DLL_PATH: This parameter specifies the network location of the Payflow Pro .dll file. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location.

Valid value is the directory path to the Payflow Pro .dll file. For example: c:\pfpro\signio\win32\lib\
PAYFLOW_DLL_PATH_PP: This parameter specifies the network location of the Payflow Pro .dll file for this plant. The PP should be replaced with the desired plant code or sales location code.

Valid value is the directory path to the Payflow Pro .dll file. For example: c:\pfpro\signio\win32\lib\
PAYFLOW_OESJ_HOLD: This parameter determines the hold code that is used when sales orders are put on credit hold during processing with program OESJ, Sales Order End of Day and Journals, because they potentially need authorizing or reauthorizing. If program ARLM, Location Maintenance, has an entry in the Hold Code for Backorders field, that value will override the value here. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location.

Valid values are any hold code from program CMHM, Hold Code Maintenance.
PAYFLOW_OESJ_HOLD_PP: This parameter determines the hold code that is used when sales orders are put on credit hold for this plant or sales location during processing with program OESJ, Sales Order End of Day and Journals, because they potentially need authorizing or reauthorizing. If program ARLM, Location Maintenance, has an entry in the Hold Code for Backorders field, that value will override the value here. The PP should be replaced with the desired plant code or sales location code.

Valid values are any hold code from program CMHM, Hold Code Maintenance.
PAYFLOW_PARTNER: This parameter specifies the Payflow Pro partner that signed up the client for PayFlow Pro. If the clients signed themselves up, the entry here should be Payflow. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location. This value is required.

Valid value is the Payflow Pro partner name.
PAYFLOW_PARTNER_PP: This parameter specifies the Payflow Pro partner that signed up the client for PayFlow Pro for this plant or sales location. If the clients signed themselves up, the entry here should be Payflow. The PP should be replaced with the desired plant code or sales location code. This value is required.

Valid value is the Payflow Pro partner name.
PAYFLOW_PASSWORD: This parameter specifies your Payflow Pro account password. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location. This value is required.

Valid value is your Payflow Pro account password.
PAYFLOW_PASSWORD_PP: This parameter specifies your Payflow Pro account password for the plant or sales location. The PP should be replaced with the desired plant code or sales location code. This value is required.

Valid value is your Payflow Pro account password.
PAYFLOW_SERVLET_PORT: This parameter specifies the http port on the web server. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location.

Valid value is the http port number. Defaults to 80 but may be different, especially for a secure server.
PAYFLOW_SERVLET_PORT_PP: This parameter specifies the http port on the web server for this plant or sales location. The PP should be replaced with the desired plant code or sales location code.

Valid value is the http port number. Defaults to 80 but may be different, especially for a secure server.
PAYFLOW_SERVLET_URI: This parameter specifies the URI to the NDS Credit Card Servlet for Payflow Pro processing. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location.

This should always be /verisign/process
PAYFLOW_SERVLET_URI_PP: This parameter specifies the URI to the NDS Credit Card Servlet for Payflow Pro processing for this plant or sales location. The PP should be replaced with the desired plant code or sales location code.

This should always be /verisign/process
PAYFLOW_SERVLET_URL: This parameter specifies the URL to the web server hosting the NDS Credit Card Servlet for Payflow Pro processing. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location.

Valid value is the appropriate URL. For example: www.nds-i.com.
PAYFLOW_SERVLET_URL_PP: This parameter specifies the URL to the web server hosting the NDS Credit Card Servlet for Payflow Pro processing for this plant or sales location. The PP should be replaced with the desired plant code or sales location code. This value is required.

Valid value is the appropriate URL. For example: www.nds-i.com.
PAYFLOW_USER: This parameter specifies the Payflow Pro account name for Payflow Pro processing. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location. This value is required.

Valid value is your Payflow Pro account name.
PAYFLOW_USER_PP: This parameter specifies the Payflow Pro account name for Payflow Pro processing for this plant or sales location.

Valid value is your Payflow Pro account name. The PP should be replaced with the desired plant code or sales location code.
PAYFLOW_VENDOR: This parameter specifies your Payflow Pro vendor name for Payflow Pro processing. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location. This value is required.

Valid value is your Payflow Pro vendor name.
PAYFLOW_VENDOR_PP: This parameter specifies your Payflow Pro vendor name for Payflow Pro processing for this plant or sales location. The PP should be replaced with the desired plant code or sales location code. This value is required.

Valid value is your Payflow Pro vendor name.

Return to See Also List

Customer and Prospect Parameters

Unless otherwise noted, these parameters have the category CUSTOMER.

Comment Sort in Customer Programs

CUST_COMMENT_SORT: This parameter determines how the customer comments will be sorted in program CMCM, Customer Credit Maintenance.

Valid values are: T, S, or D. When set to T, the comments are sorted in comment type and then comment sequence order. When set to S, the comments are sorted by descending comment sequence. When set to D, the comments are sorted by descending date sequence and then descending comment sequence.

Customer Parent Removal on Deletion

AUTO_REMOVE_CUST_PARENT_LINK: This parameter determines whether the parent customer will be removed from its child customers if the parent customer is deleted.

Valid values are: Y or N. When set to Y, the Parent Cust No field will be set to null if the parent customer number is deleted. If the parameter is set to N, customers that are assigned child customers cannot be deleted.

Hide/Show cost and profit columns in CMHI

ICHI_MODE: This parameter determines who can see the cost and profit columns in form CMHI.

Default is 'A'dmin which can see everything. Value 'O'perational will hide cost and profit columns.

Default Revenue Level for Customer Revenue Pricing

CMMM_DEF_REVENUE_LEVEL: This parameter determines the default value for the Revenue Level field in program CMMM, Customer Master Maintenance, when the customer's Price Method is set to Revenue. Revenue priced customers will receive the best price from program CMPC, Price Matrix Maintenance, regardless of quantity for the items on their sales orders when the sales order gross unit price or list price reaches the revenue level set for the customer in program CMMM, Customer Master Maintenance.

For more information on Revenue Pricing, see the Pricing section.

Valid values are numeric and should be the default dollar value for customers with the Revenue Price Method in program CMMM, Customer Master Maintenance. The dollar value can be changed for each customer, but this is the initial value assigned.

CMMM_REV_LEVEL_TYPE: This parameter determines whether the revenue is based on the gross unit price or the gross list price set in the Pricing Tab in program CMMM, Customer Master Maintenance. Revenue priced customers will receive the best price from program CMPC, Price Matrix Maintenance, regardless of quantity for the items on their sales orders when the sales order gross unit price or list price reaches the revenue level set for the customer in program CMMM, Customer Master Maintenance.

For more information on Revenue Pricing, see the Pricing section.

Valid values are 'L' for gross list price or 'U' for gross unit price.

Prospect Deletion in program PRMM, Prospect Master Maintenance

PRMM_ALLOW_DELETE: This parameter determines whether a user is allowed to delete prospect records in program PRMM, Prospect Master Maintenance.

Valid values are Y or N. When set to Y, the user can delete prospect records in program PRMM, Prospect Master Maintenance. When set to N, the user cannot delete prospect records.

Mail Address ID requirement in program PRMM, Prospect Master Maintenance

PRMM_REQUIRE_MAIL_ADDR_ID : This parameter determines whether a mail_address_id is required when creating a prospect in program PRMM, Prospect Master Maintenance.

Valid values are Y or N. When set to Y, the user a mail_address_id is required and the system will automatically create one and link it. PRMM, Prospect Master Maintenance. When set to N, a mail address id is not required.

Auto Launch Customer Master in program PRMM, Prospect Master Maintenance

PRMM_AUTO_LAUNCH_CMMM: This parameter determines whether the CMMM, Customer Master Maintenance screen will auto launch when the [Convert to Customer] button is pressed in program PRMM, Prospect Master Maintenance.

Valid values are Y or N. When set to Y, the CMMM screen will automatically launch after pressing the [Convert to Customer] button in program PRMM, Prospect Master Maintenance. When set to N, the CMMM screen will not auto launch.

Tax Exemption Expiration Date Default

TAX_EXEMPT_EXPIRE_DAYS: This parameter determines the default number of days after the system date on which the tax exemption number expires. This parameter is used to calculate the tax exempt expiration date in program CMMM, Customer Master Maintenance, when no date is entered.

Valid values are numeric and indicate the number of days that will be added to the system date to calculate the default expiration date for tax exemption numbers.

Return to See Also List

Distribution Parameters

Unless otherwise noted, these parameters have the category DISTRIBUTION.

Inventory Replenishment Moves Handling

ICRC_AUTO_SELECT: This parameter determines whether all move tickets are processed when the [Complete Open Moves] button is pressed or if a pop-up screen is displayed to allow you to select the moves to be completed.

Valid values are Y or N. When set to Y, when the [Complete Open Moves] button is pressed, all move tickets are processed. When set to N, when the [Complete Open Moves] button is pressed, a pop-up screen is displayed to allow you to select the moves to be completed.

Return to See Also List

Ecommerce Parameters

Unless otherwise noted, these parameters have the category ECOMMERCE.

Web Sales Order Determination

WEB_CRDR_CODE: this parameter determines which sales orders are considered web sales orders.

Valid values are any of the sales reason codes from program ARRM, Maintain Sales Reason Codes. The entered sales reason code indicates that the sales order is a web sales order.

Return to See Also List

Email Parameters

Unless otherwise indicated, these parameters have the category EMAIL.

Email and Fax Variable Setup

Email and fax variables should generally be set up for the COMMON user. For information on faxing and emailing reports to customers and vendors, see the Faxing and Emailing Reports section.

MAIL_DOMAIN: Domain name for mail service
MAIL_FROM: This is the mail signer for mail from the server. For example, service@ndsapps.com. When emailing reports, if the report class email and employee emails are both null, this is the address used.
MAIL_FROM_TEXT_DFLT: This is the default from text to be used if no text is provided.
MAIL_GATEWAY: This is the address of the NDS mail servlet. The NDS mail servlet lives on the middle tier, i.e. the same computer as the Forms and Reports servers. For example, http://host.domain.tld/ndsmail/send where host.domain.tld is the internet address of the server running the ndsmail application.
MAIL_HOST: This is the mail system server name. For example, mail.ndsapps.com.
MAIL_SENDER: The e-mail address to used as from/reply to
MAIL_SMTP_CONNECT: Valid path to SMTP mail service. For example, mail.ndsapps.com.
MAIL_TO_DFLT: The default to email address if one is not provided.
MAIL_TO_TEXT_DFLT: The default to text to be used if no text is provided.
MAIL_WEB_STYLE: Leave this set to blank to run the report generation in the background. Enter FORMS to run the report generation in the foreground.
USE_WEB_MAIL: Y or N. When set to Y, the transmissions will be sent through the database server's SMTP rather than using the client based mail tools. When set to any other value, the client based mail tools will be used.

Additional parameters should be set up for emailing reports to vendors and customers:

SYSTEM category parameters

REPORT_SERVER: rep60_ndsi0, for example.
REP_TEMP: the reports temporary directory output for fax and email reports.

SALES ORDER category parameters

OE_SEND_TO_MAX_SEQ: The first report class sequence number for which the send to records will not be entered on sales orders. All report classes with sequence numbers less than this value will be entered.

This parameter is used to determine the report classes for which send to records will be placed on each sales order automatically. Send to records associated with a report class with sequence numbers that are less than this value are entered on the sales orders. Sequence numbers are entered in program MURC, Report Class Definitions, for the report class.
OEDI_SENDTO_CHECKBOX: Y or N. When set to Y, the user can set the Add to Customer Master flag to on in program OEDI, Sales Order Detail Inquiry, for a sales order and update the send to information for the customer. In addition, when entering new send to records in program OEDI, the setting of this flag determines the default value for the new send to records.

Return to See Also List

General Ledger Parameters

Unless otherwise indicated, these parameters have the category G/L.

General Ledger Account Ranges for Reports

KEEP_GLRPT_ACCT_RANGES: This parameter determines whether ranges previously entered in program GLRPT, GL Reports Segment Selector, will be retained the next time the program is opened for a general ledger report.

Valid values are Y or N. When set to Y, the ranges entered in this program will be retained for the next time a report with this parameter form is run. When set to N, the ranges entered in this program will not be retained.

Reports that use this parameter form include:

GLALS, GL Account Number Listing by Segment
GLBL, Budget Listing
GLJLA, GL Journal Transactions by Account Report
GLPLA, GL Journal Transactions Posted by Account Report
GLRRA, GL Recurring Journals by Account Report
GLTB, GL Trial Balance Summary Report
GLTC, GL Trial Balance Summary Listing (Parent Currency)
GLTD, GL Trial Balance Detail Report

General Ledger Balance Record Creation

GLBAL_CREATE_DEFERRED: This parameter determines whether general ledger balance records will be created when program GLJP, General Ledger Journal Transaction Posting, is run. If you are using automatic account segments for your general ledger accounts, it is highly recommended that this parameter be set to N.

Valid values are Y or N. When set to Y, general ledger account balance records are not created when program GLJP, General Ledger Journal Transaction Posting, is run. Instead, the creation is handled before insert into the general ledger account table. When set to N, general ledger account balance records are created as normal when program GLJP, General Ledger Journal Transaction Posting, is run. . If you are using automatic account segments for your general ledger accounts, it is highly recommended that this parameter be set to NO.

Return to See Also List

Gift Card Parameters

Unless otherwise noted, these parameters have the category CREDIT CARDS.

Gift card murms are all set up and accessed under user COMMON, do not set up any user specific values as they will be ignored.

GIFTCARD_PAY_TYPE: The paytype in SPPT designated as a gift card.

GIFTCARD_PIN_FORMAT: This is the security password used when gift cards are applied as payments. The pin can be all numeric, all alpha or a combination. The format mask determines what the pin will look like and must be at least 6 char. Use '9' to indicate a numeric placeholder and 'A' to indicate an alpha placeholder in the format string. For example, a format of AA9999A9 may return a pin of GZ3430T8. A default format of AA99999A will be used if none is provided or the format is < 6 char. A pin is required for payment validation on orders.

GIFTCARD_SERIAL_FORMAT: This is the control# assigned to the gift card item to differentiate it from other gift cards. Enter a format mask in manner similar to the pin format, however, the serial number should be longer (up to 20 char is allowed). If a format is not provided then the lot control generation rules in ICEM will be used.

GIFTCARD_PG: The product group designated in IPGM to be associated with gift cards. It is used to determine whether an item or payment entered in order entry is a gift card or not.

GIFTCARD_EXPIRE_DAYS: Used if expiration date required checked in ICMM. The number of days the control# is good for before it expires. Zero or null will indicate no expiration date.

GIFTCARD_WFLOW_EMPNO: This is the employee number to send adhoc workflows generated by the system concerning gift cards.

Inventory Parameters

Unless otherwise indicated, these parameters have the category INVENTORY.

Alternate Material Overhead Calculation

MATL_OVHD_MULTIPLY: This parameter determines how material overhead for Percent and Inverse % overhead codes will be calculated when program PCIC, Incremental Cost Calculation, is run. For more information on how material overhead is calculated, see the Calculating Material Overhead for Items section.

Valid values are Y or N.

When the overhead type is Fixed or when the overhead type is Variable and the MATL_OVHD_MULTIPLY parameter is set to N or No, the percentage entered will be multiplied by the material cost of the item and the result will then be added to the material cost of the item.

When the overhead type is Variable and the MATL_OVHD_MULTIPLY parameter is set to Y or Yes, the resulting rate is a sum of all of the percent calculation variable rates that will be applied. Once the percentage is calculated, it is applied to the material cost of the item.

In these cases, the rates are multiplied together such that:
Rates a,b would be calculated as (a+b+ab). Example: 70% and 50% would be (.7+.5+.35) = 1.55 or 155%
Rates a,b,c would be calculated as (a+b+c+ab+abc+bc). Example: 70%, 50%, and 25% would be (.7 + .5 +.25 + .35 + .0875 + .125) = 2.0125 or 201.25%
Rates a,b,c,d would be calculated as (a+b+c+d+ab+abc+abcd+bc+bcd+cd). Example: 70%, 50%, 25%, and 10% would be (.7 + .5 +.25 + .1 + .35 + .0875 + .00875 + .125 + .0125 + .025) = 2.24875 or 224.875%

Inverse % indicates that the sum of the inverse rates will be applied to the material cost. The MATL_OVHD_MULTIPLY parameter determines whether or not the material cost will be increased by a factor before applying the sum of the inverse rates. The increase factor is the number of inverse rates being applied.

When the parameter is set to Y or Yes, the formula used to calculate the inverse rate is ( 1 / 1 - overhead rate / 100)). This formula is used for each rate and then the rates are added together and multiplied by the material cost.

When the parameter is set to N or No, the formula used to calculate the inverse rate is ( 1 / 1 - overhead rate / 100) - 1 ). This formula is used for each rate and then the rates are added together and multiplied by the material cost.

For example, for a single inverse rate of 30% and a material cost, the calculations for each of these situations would be:

Y: (1/(1-30/100)) = 1.42857 * .85 = 1.21428
N: (1/(1-30/100)-1) = 0.42857 * .85 = .36428
If an additional rate of 70% were applied to the item, the calculations would be:

Y: (1/(1-30/100)) + (1/(1-70/100)) = 4.7619 * .85 = 4.0476
N: (1/(1-30/100)-1) + (1/(1-70/100)-1) = 2.7619 *.85 = 2.3476

Common Customer for Item Configuration String Cross Reference

ICCR_COMMON_CUST_NO: This parameter specifies the common customer number used when setting up and querying cross references for configuration items in program ICCR, Customer / Item Cross Reference Maintenance. The customer number should not exist in program CMMM, Customer Master Maintenance. If you have items that are now configurable model items, you can set a cross reference in program ICCR, Customer / Item Cross Reference Maintenance, to connect the item number to the new configuration string. When the item is entered in the sales order entries program, the item number will be replaced with the new model item and its new configuration string.

The valid value for this parameter is a customer number that does NOT exist in program CMMM, Customer Master Maintenance.

ICCR User Ref Labels

ICCR_USER_REF1_LABEL and ICCR_USER_REF2_LABEL: Determines the boiler text for fields in ICCR.

Controlling Item Price Group Modifications

ICSM_DISALLOW_IPG_UPDATE: This parameter determines whether the item price group for an item can be updated or maintained in program ICSM, Inventory Sales Data Maintenance and whether the Item Price Groups tab can be maintained. The value set up for this parameter is the default if no plant-specific parameter exists for a plant.

Valid values are Y or N. When set to Y, the item's default item price group cannot be edited and the item price groups tab cannot be maintained.

ICSM_DISALLOW_IPG_UPDATE_PP: This parameter determines whether the item price group for an item can be updated or maintained in program ICSM, Inventory Sales Data Maintenance and whether the Item Price Groups tab can be maintained in this plant. The PP should be replaced with the plant code.

Valid values are Y or N. When set to Y, the item's default item price group cannot be edited and the item price groups tab cannot be maintained.

ICMI Item Comments

ICMI_RUN_MODE: This parameter determines whether item comments in ICMI can be edited or viewed only. It also determines whether drill downs are in edit or view only mode.

Cost/Price Update for Shipped Sales Order Lines

ICKM_RECOST_ORDER_LINE: This parameter determines whether the sales order cost and prices for margin priced customers are recalculated during shipping.

Valid values are Y or N. When set to Y, the pricing and cost will be recalculated when all other conditions are met as well. When set to N, the pricing and cost will not be recalculated.

In addition to the setting of this parameter, the following conditions must be met:

The S type cost is set up to be Actual or Average cost.
Sales order status is S - Confirmed Complete.
There is a pullcard assigned to the sales order line in program ICKM, Inventory Pull Card Moves.
The actual transfer is done in program ICKM, Inventory Pull Card Moves, after shipping.

Cycle Count Parameters

PH_POST_ALL_COUNTS: This parameter determines whether during cycle counting, if the system inventory and the counted inventory amounts match, an item transaction log entry should be written for the zero quantity to preserve the correct population of counts in the item transaction log for statistical purposes.

Valid values are Y or N. When set to Y, an item transaction log record will be written for all counted items, including those for which the system quantity and the inventory quantity are equal. When set to N, item transaction log records will only be written for items for which an adjustment is required.

ESVM Item Variables Maintenance

ESVM2_MODE determines who can maintain the item variable values, default value is Q for query only. Other option is 'A' Admin to allow maintenance. Filtering can be done using relational operators and values against the existing item variable value.

Default Item Location Warning through Item Location Bulk Move

ICLM_DEFAULT_WARN: This parameter determines whether a warning will be displayed when the 'from location' is not the item's current default location and the 'to location' is marked as being the item's new default location. This setting affects bulk moves by location with program ICLM, Inventory Bulk Move by Location.

Valid values are Y or N. When set to Y, a warning will be displayed. When set to N, a warning will not be displayed.

Default Item Location when Disassembling Items

ICDM_CUSTOM_LOC: This parameter determines whether the Loc Rule pop-list will be displayed in program ICDM, Inventory Disassembly Management. The Loc Rule pop-list determines whether the item's default location will be used as the default when disassembling items, or if a user-defined set of rules from the user's procuser file will determine the default location.

Valid values are Y or N. Y indicates that the pop-list will be displayed in program ICDM, Inventory Disassembly Management. Any other entry indicates that the pop-list will not be displayed, and the item's default location from program ICEM, Item Plant Maintenance, will be used as the default.

Default Settings for Item Plant Control

ICEM_SHIPPABLE_DEF: This parameter determines the default value of the Shippable flag in program ICEM, Item Plant Maintenance, for new items when the plant parameter does not exist.

Valid values are Y or N.

ICEM_SHIPPABLE_DEF_PP: This parameter determines the default value of the Shippable flag in program ICEM, Item Plant Maintenance, for new items in this plant. PP should be replaced by the plant code for which you are defining the default.

Valid values are Y or N.

ICEM_STOCKED_DEF: This parameter determines the default value of the Stocked flag in program ICEM, Item Plant Maintenance, for new items when the plant parameter does not exist.

Valid values are Y or N.

ICEM_STOCKED_DEF_PP: Y or N. This parameter determines the default value of the Stocked flag in program ICEM, Item Plant Maintenance, for new items entered in this plant. PP should be replaced by the plant code for which you are defining the default.

Valid values are Y or N.

Harmonized Code Validation

VALIDATE_WCO_HS_CODE: This parameter determines whether harmonized codes entered in program ICMM, Inventory Master Maintenance, will be validated against the harmonized code values in program SPHM, WCO Harmonized Code Maintenance.

Valid values are Y or N. When set to Y, harmonized codes will be validated. When set to N, harmonized codes will not be validated.

ICMI - Inventory Item Inquiry Mode Setting

ICMI_MODE: This parameter determines whether maintenance screens accessed through the buttons program ICMI, Inventory Master Inquiry, will be in query-only or maintenance mode.

Valid values are Q or M. When set to Q, the maintenance screens will be in query-only mode. When set to M, the maintenance screens will be in maintenance mode. Inquiry screens will always be in query only mode.

ICMI_RUN_MODE: This parameter determines whether users can edit item comments or only view them.

Valid values are Q or M. When set to Q, the item comments pop-up will be in query-only mode. When set to M, the item comments pop-up will be in maintenance mode. This parameter also controls whether drilldowns are in query only mode or maintenance mode, Default is Q.

Hide Profit and Cost Columns in Program ICHI

ICHI_MODE: This parameter determines who can see the profit and cost columns in ICHI.

Default is 'A'dmin which can see everything. Value 'O'perational will hide cost and profit columns.

Include Internal Shipments in Usage

ICAR1_INCL_INTERNAL_SHIP: This parameter determines whether intercompany shipments are included in usage figures.

Default is 'N'. 'Y' will include internal shipments.

Inventory Replenishment Trigger Quantity on Hand Determination

IPSM_QOH_SOURCE: This parameter determines whether the replenishment trigger in program IPSM, Inventory Pull Card Definition, should consider the quantity on hand in the plant or in the item location when creating inventory replenishment move tickets. The value set up for this parameter is the default if no plant-specific parameter exists for a plant.

Valid values are PLANT or LOCATION.

When set to PLANT, the quantity on hand at the plant level will be considered when determining whether a move ticket should be created to replenish inventory. The sum of the trigger values in program IPSM, Inventory Pull Card Definition, for the plant will be compared against the quantity on hand. If a move ticket is created, it will be generated based on the first replenishment trigger found for the item in the plant. Using this parameter works best when there is only one trigger per item.

When set to LOCATION (or anything besides PLANT), the quantity on hand in the defined item location will be used to determine if a move ticket should be created.

IPQ_DEFER_UPDATE: Determines whether inventory transactions are posted in real time to item_plant_quantities or whether they are deferred into an interface table for batch updating. This is for use by high transaction companies to better control accurate on_hand quantities. If set to Y, inventory transactions will be posted into a new table ITEM_PLANT_QUANTITY_DEFER. A new batch job IPQ_DEFER (which must be scheduled to run every xx minutes) will then post the actual transactions to the ITEM_PLANT_QUANTITIES. This new feature will not affect fulfillment schemas. Default is N.

IPSM_QOH_SOURCE_PP: This parameter determines whether the replenishment trigger in program IPSM, Inventory Pull Card Definition, should consider the quantity on hand in the plant or in the item location when creating inventory replenishment move tickets. This parameter is plant-specific. When setting up the parameter, replace the PP with the appropriate plant code.

Valid values are PLANT or LOCATION.

When set to PLANT, the quantity on hand at the plant level will be considered when determining whether a move ticket should be created to replenish inventory. The sum of the trigger values in program IPSM, Inventory Pull Card Definition, for the plant will be compared against the quantity on hand. If a move ticket is created, it will be generated based on the first replenishment trigger found for the item in the plant. Using this parameter works best when there is only one trigger per item.

When set to LOCATION (or anything besides PLANT), the quantity on hand in the defined item location will be used to determine if a move ticket should be created.

Physical Inventory/General Ledger Post Date

Added to NDS Applications, version 7.5.3, 8.1

PIUP_POSTING_DATE: This parameter determines whether the physical inventory transactions will be posted to the general ledger using the snapshot date from program PIWW, Physical Inventory Control, or the transaction date.

Valid values are S or blank. When set to S, the snapshot date from program PIWW, Physical Inventory Control, is used for the physical inventory general ledger postings. When set to blank or anything besides S, the transaction date is used.

Protected Sales Order Line Allocations in Background Batch Shipping

PROTECTED_ALLOC_WARN_DAYS: This parameter determines how many days before the protected allocation expiration date the expiration workflow will be sent. The expiration date is based off of the estimated ship date for the sales order. The parameter is only valid for background batch shipping.

Valid value is the number of days before the estimated ship date of the sales order that the expiration workflow will be sent for the protected allocations.

Protecting Plant Level Differences

PLANT_PROTECT: This parameter determines whether the buttons in certain programs are disabled so that plant-specific values are not pushed to other plants accidentally.

Valid values are Y or N. When set to N, the buttons are enabled. When set to Y, the buttons are disabled.

Programs affected by this parameter include:

ICMM, Inventory Master Maintenance - [Push $] button
ICSM, Inventory Sales Data Maintenance - [Push to Other Plants] button
ICCM, Inventory Cost Data Maintenance - [Push to Other Plants] button
BMMM, Bill of Material Maintenance - [Make ECL Current] button
RTMM, Routing Master Maintenance - [Make Current Rev] button

Quarantine Location Warning in program ICBM, Inventory Bulk Moves

ICBM_QUARANTINE_WARN: This parameter determines whether a warning will be displayed when the to or from location entered in program ICBM, Inventory Bulk Moves, is set up as a quarantine location in program ILMM, Location Master Maintenance.

Valid values are Y or N. When set to Y, the warning will be displayed. When set to N, the warning will not be displayed.

Sales Order Allocations include Drop Ship Items

SALES_ALLOC_INCL_DROP_SHIP: This parameter determines whether sales allocations for an item include sales order line items that are marked as drop ship.

Valid values are Y or N. When set to Y, sales order lines for drop ship items will be included in sales allocation calculations. When set to N, sales order lines for drop ship items will not be included in sales allocation calculations.

Settings for program ICSS, Stock Status Inquiry

ICSS_MODE: This parameter determines the setting for program ICSS, Stock Status Inquiry, to limit the information available for a user.

Valid values are P, O, or A.

P - Plant: the user can only see default plant quantities, no costs, no values, and no drill down to program ICPI, Perpetual Inventory Inquiry.

O - Operator: the user can see all plant quantities, but no costs, no values, and no drill down to program ICPI, Perpetual Inventory Inquiry.

A - Administrator: Can view all information.

Return to See Also List

Invoicing Parameters

Unless otherwise indicated, these parameters have the category INVOICING.

Model Item Work Order Cost Determination

COGSMODELWOCOST: This parameter determines determine how work order cost is calculated for non-maintain on hand model items when the sales order for the model item is processed through program OESJ, Sales Order End of Day and Journals.

Valid values are Y or N. When set to Y, sales orders for model items are updated during program OESJ, Sales Order End of Day and Journals, with the model costs recalculated from the work order. If the Second Manufacturing Cost flag in program PCTM, Cost Type Maintenance, is set to on for the S type cost type, the actual cost is used. If the Second Manufacturing Cost flag in program PCTM, Cost Type Maintenance, is set to off, the setting of the COGSMODELWOCOST_OVERRIDE parameter determines the update.

COGSMODELWOCOST_OVERRIDE: This parameter overrides the setting for the update of the model cost in program OESJ, Sales Order End of Day and Journals, when the Second Manufacturing Cost flag in program PCTM, Cost Type Maintenance, is not set to on for cost type S.

Valid values are N (None), S (Standard), or A (Actual).
N - None: When set to N, the model cost will not be updated when program OESJ, Sales Order End of Day and Journals, is run.
S - Standard: When set to S, the model cost is updated with the standard cost for the item when program OESJ, Sales Order End of Day and Journals, is run.
A - Actual: When set to A, the model cost is updated with the actual cost for the item when program OESJ, Sales Order End of Day and Journals, is run.

Sales Order Batch Invoicing Parameters

OESJ_BATCH_DATE_OFFSET: This parameter determines the default settings for batch invoicing that can be set up using a batch file in your scheduled tasks on your operating system. For more information, see the Batch Invoicing documentation. If no plant parameter is found, this parameter is used as the default value.

Valid value is the number of days to subtract from the system date to get the cutoff ship date for the batch run. Default is 1 if no value is entered or the parameter does not exist.

OESJ_BATCH_DATE_OFFSET_PP: This parameter determines the default settings for this plant for batch invoicing that can be set up using a batch file in your scheduled tasks on your operating system. For more information, see the Batch Invoicing documentation. The PP should be replaced with the plant code as these parameters are defined by plant. If no parameter exists for the plant, the OESJ_BATCH_DATE_OFFSET parameter value is used.

Valid value is the number of days to subtract from the system date to get the cutoff ship date for the batch run for this plant.

Return to See Also List

Marketing Parameters

Unless otherwise indicated, these parameters have the category MARKETING.

Default Settings and Set Up for program CMSU, Mail Label Selector

This parameter determines various settings and behaviors in program CMSU, Mail Label Selector. The following programs are included when referring to master programs in this section.

CMMM, Customer Master Maintenance
MTMM, Mail To/Prospect Input for Catalogs
SPWM, System Contacts Maintenance
PRMM, Prospect Master Maintenance

CMMM_CMSU_CASCADE_NY: This parameter determines whether when the Catalog Ok flag is changed from off to on in program CMMM, Customer Master Maintenance, the Catalog Ok flag will be set to on in program MTMM, Mail To/Prospect Input for Catalogs and program SPWM, System Contacts Maintenance, for all mail to addresses and contacts for the customer.

Valid values are Y or N. When set to Y, the update described above will be made.

CMMM_CMSU_CASCADE_YN: This parameter determines whether when the Catalog Ok flag is changed from on to off in program CMMM, Customer Master Maintenance, the Catalog Ok flag is set to off in program MTMM, Mail To/Prospect Input for Catalogs and program SPWM, System Contacts Maintenance, for all mail to addresses and contacts for the customer.

Valid values are Y or N. When set to Y, the update described above will be made.

CMSU_ACTIVE: This parameter determines whether changes to the Catalog Ok, Selected, and Send Mass Mail flags in the master programs will also update the in the synchronization table in program CMSU, Mail Label Selector, depending on the setting of the CMSU_DAILY_EXPORT_LL parameter for the sales location.

Valid values are Y or N. When set to Y, changes to the Catalog Ok, Selected, and Send Mass Mail flags in the master programs will also update the in the synchronization table in program CMSU, Mail Label Selector, depending on the setting of the CMSU_DAILY_EXPORT_LL parameter for the sales location.

CMSU_AUTO_SYNC_MAIL: This parameter determines whether the settings for the Mass Mail flag will be updated in the search table when program CMSU, Mail Label Selector, is opened to match the setting of the Send Mass Mail flag in the synchronization table.

Valid values are Y or N. When set to Y, the Mass Mail flag will be updated in the search table when program CMSU, Mail Label Selector, is opened to match the setting of the Send Mass Mail flag in the synchronization table.

CMSU_AUTO_SYNC_SEL: This parameter determines whether the settings for the Selected flag will be updated in the search table when program CMSU, Mail Label Selector, is opened to match the setting of the Selected flag in the synchronization table. Synchronization of the Selected flag includes pulling in the Catalog ID and mail class from the synchronization table.

Valid values are Y or N. When set to Y, whether the settings for the Selected flag will be updated in the search table when program CMSU, Mail Label Selector, is opened to match the setting of the Selected flag in the synchronization table.

CMSU_EXPORT_DIR: This parameter determines the path to the default export directory for export files created from program CMSU, Mail Label Selector.

Valid value is the network path to the default export directory for export files created from program CMSU, Mail Label Selector. For example, c:\temp\

CMSU_CSV_HEADER: This parameter determines whether the column headers will be written to the remarks line in the csv file. The column headers will overwrite any remarks entered on the export screen. You cannot have both remarks and column headers in the same csv file.

Valid values are Y or N. When set to Y, the column headers will be written to the remarks line in the csv file.

CMSU_DAILY_EXPORT: This parameter determines whether a sales location is exported daily and that when a change is made to one of the master programs for a customer/prospect/contact/mail address in the defined location, the change will be copied to the synchronization table so that automatic synchronization of the selected and mass mail flags will be performed the next time program CMSU, Mail Label Selector, is run. This parameter is the default value for each location specific parameter and if a parameter does not exist for a location, the value from this parameter will be used for that location.

Valid values are Y or N. When set to Y, the above described functionality will occur. When set to N, changes to the master programs will not be copied to the synchronization table, and thus will not be synchronized with the records in program CMSU, Mail Label Selector.

CMSU_DAILY_EXPORT_LLL: This parameter determines whether the sales location is exported daily and the when a change is made to one of the master programs for a customer/prospect/contact/mail address in the defined location, the change will be copied to the synchronization table so that automatic synchronization of the selected and mass mail flags will be performed the next time program CMSU, Mail Label Selector, is run. Replace the LLL in the parameter with the sales location code.

Valid values are Y or N. When set to Y, the above described functionality will occur for the defined sales location. When set to N, changes to the master programs will not be copied to the synchronization table, and thus will not be synchronized with the records in program CMSU, Mail Label Selector.

CMSU_USE_STD_CSV_HDR: This parameter determines whether the export will use the standard column list for the columns being exported.

Valid values are Y or N. When set to Y, the export uses the standard column list for the columns being exported. When set to N, the export uses the custom column header list created in the procuser.sql file.

MTMM_CMSU_CASCADE_NY: This parameter determines whether when the Catalog Ok flag is changed from off to on in program MTMM, Mail To/Prospect Input for Catalogs, the Catalog Ok flag will be set to on in program SPWM, System Contacts Maintenance, for all contacts for the mail to address.

Valid values are Y or N. When set to Y, the update described above will be made.

MTMM_CMSU_CASCADE_YN: This parameter determines whether when the Catalog Ok flag is changed from on to off in program MTMM, Mail To/Prospect Input for Catalogs, the Catalog Ok flag will be set to off in program SPWM, System Contacts Maintenance, for all contacts for the mail to address.

Valid values are Y or N. When set to Y, the update described above will be made.

PRMM_CMSU_CASCADE_NY: This parameter determines whether when the Catalog Ok flag is changed from off to on in program PRMM, Prospect Master Maintenance, the Catalog Ok flag is set to on in program MTMM, Mail To/Prospect Input for Catalogs and program SPWM, System Contacts Maintenance, for all mail to addresses and contacts for the prospect.

Valid values are Y or N. When set to Y, the update described above will be made.

PRMM_CMSU_CASCADE_YN: This parameter determines whether when the Catalog Ok flag is changed from on to off in program PRMM, Prospect Master Maintenance, the Catalog Ok flag is set to off in program MTMM, Mail To/Prospect Input for Catalogs and program SPWM, System Contacts Maintenance, for all mail to addresses and contacts for the prospect.

Valid values are Y or N. When set to Y, the update described above will be made.

Mail To Default Settings

These parameters determine the defaults for the default template customer and list of values display in program MTMM, Mail To/Prospect Input for Catalogs.

MTMM_LABEL_FORM: This parameter determines the label print form to be drilled down to when printing labels in program MTMM, Mail To/Prospect Input for Catalogs. The default is MTLL, Contact Mailing Label.

Valid value is any label print form that will print contact mailing labels.

MTMM_DEF_CUST_FFFPP: This parameter determines the default customer number used in program MTMM, Mail To/Prospect Input for Catalogs, for this financial enterprise and plant. This parameter is enterprise and plant specific. The FFF should be replaced by financial enterprise code and the PP should be replaced by plant code. For example, when the user is logged into enterprise 100 and plant 10, the default template customer is taken from the MTMM_DEF_CUST_10010 parameter.

Valid value is any template customer number from program CMMM, Customer Master Maintenance, that is valid for the financial enterprise.

MTMM_USER1_LOV: This parameter determines whether a list of values is available on the first user field in program MTMM, Mail To/Prospect Input for Catalogs.

Valid values are Y or N. When set to Y, the list of values is available on the first user field in program MTMM, Mail To/Prospect Input for Catalogs. When set to N, the list of values is not available for the first user field.

MTMM_USER2_LOV: This parameter determines whether a list of values is available on the second user field in program MTMM, Mail To/Prospect Input for Catalogs.

Valid values are Y or N. When set to Y, the list of values is available on the second user field in program MTMM, Mail To/Prospect Input for Catalogs. When set to N, the list of values is not available for the second user field.

MTMM_USER3_LOV: This parameter determines whether a list of values is available on the third user field in program MTMM, Mail To/Prospect Input for Catalogs.

Valid values are Y or N. When set to Y, the list of values is available on the third user field in program MTMM, Mail To/Prospect Input for Catalogs. When set to N, the list of values is not available for the third user field.

MTMM_USER4_LOV: This parameter determines whether a list of values is available on the fourth user field in program MTMM, Mail To/Prospect Input for Catalogs.

Valid values are Y or N. When set to Y, the list of values is available on the fourth user field in program MTMM, Mail To/Prospect Input for Catalogs. When set to N, the list of values is not available for the fourth user field.

Prospect Upload Parameter Setup

Some setup is required in this program for program PUTM - Prospect Upload & Template Maintenance.

PUTM_START_IN_DIR: This parameter is the default server directory for reading prospect upload files in program PUTM - Prospect Upload & Template Maintenance. If null, then the value from the UTL_FILE_DIR parameter in this program will be used..

Valid value is the network path to the directory. For example, c:\temp\

Planning Parameters

Unless otherwise indicated, these parameters have the category PLANNING.

Forecast Filtering Activation

FCCX_AUTO_FC_ACTIVATE: This parameter determines whether the Statistical Forecast flag for items will be changed automatically when the sample population of the item exceeds the minimum population for the forecast group. The Statistical Forecast flag must be set to Track, and when the population exceeds the minimum population for the forecast group, the flag setting will be changed to Yes if the Filter Enabled flag is set to on for the item's forecast group. This allows the forecasting for new items to be set to Track initially, and have the forecasting be automatically activated when enough data exists.

Valid values are Y or N. When set to Y, the Statistical Forecast flag should be changed from Track to Yes automatically.

ICPM Access Parameters

ICPM_MODE: This parameter determines if the users can modify both the manufacturing enterprise and plant planning parameters in program ICPM, Inventory Planning Data Maintenance.

Valid values are A or P. When set to A, the user is an administrative user and can modify both the manufacturing enterprise and plant planning parameters in program ICPM, Inventory Planning Data Maintenance. When set to P, the user is a plant user and can view the manufacturing enterprise planning parameters, but can only modify the plant planning parameters.

Master Production Scheduling (MPS) Forecast Calculation Record Suppression

MPS_SUPPRESS_FD: This parameter determines whether the creation of type FD forecast calculation records will be suppressed during master production schedule (MPS) runs. This parameter is provided mainly for situations where large numbers of FD records slow the performance of MPS run and forecast calculations are not being used.

Valid values are Y or N. When set to Y, the creation of type FD forecast calculation records will be suppressed. This parameter is provided mainly for situations where large numbers of FD records slow the performance of MPS run and forecast calculations are not being used. When this parameter is set to Y, the projected on hand calculation will not be accurate, and users will need to interpret projected on hand values as projected available to promise values instead.

Master Schedule Authorization Settings

MSSX_SR_NO_UPDATE: This parameter determines whether existing authorized schedules will be added to or if new schedules will be planned when transferring Master Schedules to the live system with program MSSX, Master Schedule Authorization.

Valid values are Y or N. When set to Y, instead of adding to existing authorized schedules, a new schedule will be planned on the next available date that has no schedule for the item. When set to N or if no value is assigned, quantities will be added to existing authorized schedules for the item.
Note: Resulting schedules may not match Master Scheduling plan displays. This option is NOT compatible with lot or serial control.

Master Schedule Time Fence

MPS_REPLAN_FENCE: This parameter determines which time fence from program MSBM, MPS Period Maintenance, is used to limit the consideration of existing firm planned orders in Master Production Scheduling (MPS). Normally, Master Production Scheduling (MPS) is limited to only planning orders beyond the Firm Plan Fence in program MURM, Initialization Parameter Maintenance. However, Firm Planned orders are the primary product of running MPS, and some users prefer that it be allowed to re-plan everything, or almost everything. This parameter allows the user to do this.

Valid values are D or F. When set to D, the demand fence period is used. When set to F, the Firm fence period is used. If the Demand Time Fence in program MSBM, MPS Period Maintenance, is not set, and this parameter is set to D, when MPS is run, all existing firm planned orders will be replaced with new planned orders.

Material Requirements Planning (MRP) Authorization Settings

MPPX_SR_NO_UPDATE: This parameter determines whether existing authorized schedules will be added to or if new schedules will be planned when transferring MRP Planned Orders to the live system with program MPPX, MRP Planned Order Transfer.

Valid values are Y or N. When set to Y, instead of adding to existing authorized schedules, a new schedule will be planned on the next available date that has no schedule for the item. When set to N or if no value is assigned, quantities will be added to existing authorized schedules for the item.
Note: Resulting schedules may not match MRP plan displays. This option is NOT compatible with lot or serial control.

Materialized Views in MRP and MPS Settings

MRP_USE_FAST_OE: This parameter determines whether or not you wish to use materialized views to increase the performance of the MRP or MPS run, if you have a large number of sales order entry lines records to be considered when MRP or MPS is run.

Valid values are Y or N. When set to Y, the MRP process and MPS process will use a materialized view for performance reasons. This requires that the materialized view has been refreshed and analyzed immediately prior to running MRP or MPS so the data is fresh.

If you are using this parameter, then the materialized view needs to be refreshed immediately before MRP or MPS is run by adding a job parameter in program MUJM, Menu and Job Parameter Maintenance. Once this step has been added, the MRP or MPS run must be done as the database schema owner. (MRP in program MPPP, Material Requirements Planning, MPS in program MSSP, Master Production Scheduling)

For more information on setting up MRP to use the materialized view, see the Using Materialized Views in MRP for Performance section.

For more information on setting up MPS to use the materialized view, see the Using Materialized Views in MPS for Performance section.

Proxy Schedule Maintenance Defaults

PXSM_BUCKET_DAYS: This parameter determines the default value of the Bucket Days field in program PXSM, Proxy Schedule Maintenance, when the program opens.

Valid value is the default number of days for each bucket into which the planning horizon will be split in the Proxy Netting section.

PXSM_HORIZON: This parameter determines the default value of the Plan Horizon field in program PXSM, Proxy Schedule Maintenance, when the program opens.

Valid value is the default number of days in the future from the system date used when calculating the proxy netting for items.

Return to See Also List

Purchasing Parameters

Unless otherwise indicated, these parameters have the category PURCHASING.

Comment Types for Purchase Report Printing

POPR_PRINT_COMMENT_TYPE: This parameter determines the comment types that will print on the purchase order when program POPRL, P.O. Print Standard and Blanket (Laser), or program POP3L, PO Print - Blanket Order Releases (Laser), is run. This comment type is in addition to the PO comment type that prints on the report by default.

Valid Values are any user-defined or standard comment type.
For custom version of these reports, this functionality must be added. Contact NDS Professional Services for more information.

Default Settings for program POIK, PO / Item Kiosk

These parameters determine the default values for the Service Z Factor and Horizon fields in program POIK, PO / Item Kiosk.

POIK_SERVICE_Z: the default value for the Service Z factor in program POIK, PO / Item Kiosk. Generally, values between 1 and 3 are used.
POIK_STAT_HORIZON: the default number of days before the current system date for which the shipments will be analyzed.

Due Date Matches Promise Date in PDQM, PO Detail Quick Maintenance

PDQM_DUE_DATE: This parameter determines whether the purchase order due date will be forced to match the current promise date when the current promise date is changed in program PDQM, PO Detail Quick Maintenance.

Valid values are Y or N. When set to Y, the due dates will be forced to match the current promise date. When set to N, the due date will not change when the current promise date is updated.

Item Description display flag in PDQM, PO Detail Quick Maintenance

PDQM_SHOW_USER_REF1: This parameter determines whether the item description field displays the USER_REF1 value or the default item description.

Valid values are Y or N. When set to Y, the item description field displays the USER_REF1 value for the item. When set to N, the item description shows the item description field value of the item.

Due Date Recalculation in program PORK, Requisition to PO Conversion

PORK_RECALC_DUE_DATE: This parameter determines whether the due date will be recalculated for the purchase order line generated in program PORK, Requisition to PO Conversion, regardless of the due date on the requisition line. The recalculation includes the lead times, vendor changes, and lapses in time between when the requisition was created and when it was converted. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.

Valid values are Y or N. When set to Y, the due dates will always be recalculated. When set to N, the due date will be recalculated as described in the documentation for program PORK, Requisition to PO Conversion.

PORK_RECALC_DUE_DATE_PP: This parameter determines whether the due date will be recalculated for the purchase order line generated in program PORK, Requisition to PO Conversion, for this plant regardless of the due date on the requisition line. The recalculation includes the lead times, vendor changes, and lapses in time between when the requisition was created and when it was converted. Replace the PP with the plant to which the parameter value applies.

Valid values are Y or N. When set to Y, the due dates will always be recalculated. When set to N, the due date will be recalculated as described in the documentation for program PORK, Requisition to PO Conversion.

Internal Supplier Settings

These parameters determine the functionality of the Internal Suppliers features.

INT_SUPPLY_PRICE_OVRD: This parameter determines the pricing on the sales order line for internally supply purchase orders.

*Valid values include: N, C, or anything else.
N - the unit price on the sales order will be 0.
C - the unit price on the sales order will match the unit price on the purchase orders.
Any other setting indicates that standard pricing will be used on the sales order.

INTERNAL_SUPPLY_NOHIST: Sales analysis and item history are recorded for internal supply transactions, but they can be suppressed. This parameter determines whether or not the sales analysis and item history is recorded for the internal supply sales orders and purchase orders. This parameter has the category INVENTORY.

*Valid values are Y or N. When set to Y, the information IS NOT recorded. When set to N, the information IS recorded.

POAB_VENDOR_REQUIRED: This parameter determines whether a vendor is required when a range of POare allocated in POAB. If set to , vendor must be entered before allocating a block of POs and buyer code and initials are required to default onto block of allocated POs. If MURM is set to N, then vendor is optional. Default is .

POEM_INTERCO_WARN: This parameter determines whether a warning will be displayed in program POEM, PO Entry/Maintenance, when a user queries an internal purchase order, only one sales order is associated with the purchase order, the sales order is not open, and there are no open back orders for the sales order.

Valid values are Y or N. When set to Y, the warning will be displayed.

REOM_INT_SO_REQD: This parameter determines whether receipt of internal supply purchase orders requires receipt of entire sales order shipment. This parameter has the category RECEIVING.

Valid values are Y or N. When set to Y, receipt of internal supply purchase orders requires receipt of entire sales order shipment.

Item Description Synchronization for Vendor Quotes

VEQM_ITEM_DESC_SYNC: This parameter determines whether the item description will be updated in program VEQM, Vendor Quote Maintenance, when item descriptions are changed in program ICMM, Inventory Master Maintenance.

Valid values are Y or N. When set to Y, when the item description is changed in program ICMM, Inventory Master Maintenance, any vendor quotes with that item will also be updated with the new description. When set to N, item descriptions in program VEQM, Vendor Quote Maintenance, are not affected by changes in program ICMM, Inventory Master Maintenance.

Lock Purchase Unit Cost on Receipt

POEM_LOCK_COST_ON_RECEIPT: This parameter determines whether the purchase order unit price is locked for a purchase order once a receipt for that order has been entered.

Valid values are Y or N. When set to Y, the PO Unit Price is locked once a receipt has been entered.

Purchase Order Cost Variance Options

PO_COST_VARIANCE_ALLOWED: This parameter determines whether the price on the purchase order will be compared against the purchase order unit cost for maintain on hand items to see if it is within tolerance levels. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.

Valid value is the variance by which the price can differ from the cost on the purchase order for maintain on hand items for the plant. If no value is entered, the purchase price and cost will not be compared.

PO_COST_VARIANCE_ALLOWED_PP: This parameter determines whether the price on the purchase order will be compared against the purchase order unit cost for maintain on hand items to see if it is within tolerance levels for this plant.

Valid value is the variance by which the price can differ from the cost on the purchase order for maintain on hand items for the plant. If no value is entered, the purchase price and cost will not be compared. The PP should be replaced with the plant code for which the variance applies.

Purchase Order Price Updates Sales Order Cost Options

PO_COST_UPDATE_ALLOWED: This parameter determines whether an update to the price of a purchase order line that is assigned to a sales order will also update the sales order line cost.

Valid values are STANDARD, ALWAYS, or NEVER.

STANDARD: the sales order cost will be updated according to the standard cost update rules in the Cost Overrides and Updates section.

ALWAYS: the sales order cost will always be updated with the purchase order price.

NEVER: the sales order cost will never be updated with the purchase order price.

Stale Purchase Order Expediting Setup

EXPEDITE_PO: This parameter determines whether when existing purchase orders meet or exceed the vendor minimums when requisitions are added with program PORK, Requisition to PO Conversion, the purchase order date will be changed to the current system date to assist in expediting the purchase orders.

For more information, see the Stale Purchase Orders section.

Valid values are Y or N. When the parameter is set to YES, the purchase order date will be changed.

Receiving Parameters

Unless otherwise indicated, these parameters have the category RECEIVING.

APACHE Virtual Directory Setup

The following set up instructions are used for printing MSDS sheets for the Shipping Director Set Up.

1. Go to the ORACLE_HOME/Apache/Apache/conf directory.

2. Edit the file: httpd.conf

3. Search for the line reading: <IfModule mod_alias.c>

4. Immediately AFTER this line, on its own line, add the following:

Alias /pdf "E:\nds\msds\" or as appropriate (exactly the same as MSDS_FILES_ROOT below)

5. Change the "E:\nds\msds\" to point to the correct directory where the PDF files will be stored, taking care to place a trailing forward slash or backslash at the end.

6. Note that the above directory should follow the file/directory naming conventions for the operating system. i.e. Windows uses backslashes (\), while UNIX/Linux/AIX uses forward slashes, but the /pdf is a forward slash (/) followed by pdf.

Control Number Warning

RELX_SHIP_CTRL_WARN: This parameter determines whether the user will be warned that a control number is required for shipment when a controlled item without a control number is selected in program RELX, Shipping New Receipts Batch Control.

Valid values are Y or N. When set to Y, a warning will be displayed in program RELX, Shipping New Receipts Batch Control, when a receiver line for a controlled item is selected to be shipped and no control number is associated with it. When set to N, no warning will be displayed.

Default Item Location Update through Purchase Receipts

RCVG_UPDATES_DEFBIN: This parameter determines whether, when an item is received to a location for the first time, the default location for the item is set to that new location. This setting affects program REOM, One Step Receiver Entry/Maintenance, program REMD, Move to Destination, and program REFS, Miscellaneous Receipts

Valid values are Y, N, ASK, ZERO, or ZEROASK.
N: Receiving an item to a location for the first time has no effect on the item's default location. The New Default flag is set to off automatically in program REFS, Miscellaneous Receipts.
Y: Receiving an item to a location for the first time will always set that location to be the item's default location. No warning is displayed. The New Default flag is set to on automatically in program REFS, Miscellaneous Receipts. The Def flag is set to on automatically in program REOM, One Step Receiver Entry/Maintenance.
ASK: When an item is received to a location for the first time, the program will ask the operator if the location should be made the item's default location. No affect on the New Default flag in program REFS, Miscellaneous Receipts or the Def flag in program REOM, One Step Receiver Entry/Maintenance. This only affects program REMD, Move to Destination.
ZERO: When the item's on hand quantity is zero, receiving an item to a location for the first time will set that location to be the item's default location. No warning is displayed. The New Default flag and the Def flag default to off unless the item does not have a quantity on hand in the plant, in which case the flags default to on.
ZEROASK: When the item's on hand quantity is zero and an item is received to a location for the first time, the program will ask the operator if the location should be made the item's default location. No affect on the New Default flag in program REFS, Miscellaneous Receipts or the Def flag in program REOM, One Step Receiver Entry/Maintenance. This only affects program REMD, Move to Destination.

Receiver Header Comment

RECV_HDR_AUTO_COMMENT: This parameter determines if the header comment box pops up upon COMMIT of receiver entry/maintenance in programs REEM, Receiver Entry/Maintenance and REOM, One Stop Receiver Entry/Maintenance. If this parameter is NULL the pop up box will not open. If this parameter has a value, the comment pop up box will appear with this murm value in the type field.

Header Comment

Label Printing for Receipts

Program OESX, Shipping Director, program RELX, Shipping New Receipts Batch Control, and program REOM, One Step Receiver Entry/Maintenance, require that some keys be set up in this program for the COMMON user in order to allow printing for license plates, AIAG labels, MSDS Sheets, and put-away labels. The default label printer is also defined here.

License plate set up is also used by program RTVM, Return to Vendor Maintenance.

To make MSDS sheets work, an APACHE virtual directory needs to be set up. Also, for printing MSDS Sheets, the system will choose the printing program as follows:

(1) Is PDF_PRINT_BATCH parameter setting present? If so, set it to HOST and print the pdf.
(2) Is the mode WEB? If so, show document in web browser.
(3) If none of the above, use the PDF_PRINT_COMMAND parameter setting to HOST and print the pdf.

LPS_DTD: This parameter determines the network path to the file name for the .dtd on the server, default is c:\Program Files\Loftware\Labeling\Batch\label.dtd

Valid value is the network path to the file name for .dtd file on the server.

LPS_ENGINE: This parameter determines the LPS Engine.

Valid values are TCP or file

LPS_FILE_ROOT: This parameter specifies the directory name where output files are to be placed by the client machine. Must end with \.

Valid value is the network path to the directory where output files are to be placed by the client machine. Must end with \.

LPS_HOLD: This parameter specifies the path to the file name for the hold labels on the server.

Valid value is the network path to the file name for hold labels on the server.

LPS_IP: This parameter specifies the IP address of the LPS server.

Valid value is the IP address of the LPS server.

LPS_LABEL_ROOT: This parameter specifies the directory name where AIAG file definitions are located on the server. Must end with \.

Valid value is the network path to the directory where AIAG file definitions are located on the server. Must end with \.

LPS_LICENSE: This parameter specifies the path to the file name for the license plate label definition on the server.

Valid value is the network path to the file name for the license plate label definition on the server.

LPS_PORT: This parameter specifies the port number for the LPS server, default 2723.

Valid value is the port number for the LPS server.

LPS_PUTAWAY: This parameter specifies the path to the filename for the put-away labels on the server.

Valid value is the network path to the file name for put away labels on the server.

LPS_SHIPPED: This parameter specifies the path to the filename for shipped labels on the server.

Valid value is the network path to the file name for shipped labels on the server.

LPS_USER_COMPUTER: This parameter specifies the computer name for the LPS CLIENT.

Valid value is the computer name for the LPS CLIENT.

LPS_USER_NAME: This parameter specifies the user name for the LPS CLIENT.

Valid value is the user name for the LPS CLIENT.

RELP_LABEL: This parameter determines the default label printer that is used by program RELX, Shipping New Receipts Batch Control, before the DEF_BARCODE_PRINTER is used.

Valid values are any printer from program MUPM, Printer Definition Maintenance.

RELP_LASER: This parameter determines the default laser printer that is used by program RELX, Shipping New Receipts Batch Control, before the printer from the menu is used.

Valid values are any printer from program MUPM, Printer Definition Maintenance.

INVENTORY Parameters for Label Printing

MSDS_FILES_ROOT: This parameter determines the location on the server where the MSDS .pdf files can be found. Should always have a trailing \. For example: E:\NDS\MSDS\
This parameter has the category INVENTORY.

Valid value is the appropriate network directory path for the MSDS pdf files.

SYSTEM Parameters for Label Printing

DEF_BARCODE_PRINTER: This parameter determines the printed to be used for label printing with program RELX, Shipping New Receipts Batch Control, and program OESX, Shipping Director. This parameter has the category SYSTEM.

Valid value is any printer from program MUPM, Printer Definition Maintenance.

PDF_PRINT_BATCH: This parameter determines the command for printing pdf files. For example, to use the Ghost PDF print program: "C:\Program Files\Ghostgum\gsview\gsprint" This parameter is considered before the PDF_PRINT_COMMAND parameter.

Valid value is the command for printing pdf files.

PDF_PRINT_COMMAND: This parameter determines the command for printing .pdf files in client/server mode.

Valid value is the command for printing pdf files in client/server mode. For example: "C:\Program Files\Adobe\Acrobat 5.0\Reader\AcroRd32.exe" /p /h

PDF_PRINT_WEB: This parameter determines the URL to reach the MSDS files on the server.

Valid value is the appropriate URL. For example http://www.nds-i.com/pdf/

Return Parameters

Unless otherwise indicated, these parameters have the category RETURNS.

Return To Vendor Parameters

These parameters determine the functionality of program RTVM, Return to Vendor Maintenance. Some of these parameters are plant code specific.

ALLOW_RTV_INSERT: This parameter determines whether discontinued items can be inserted into return to vendor transactions without moving them to a quarantine location.

Valid values are Y or N. When set to Y, discontinued items can be inserted into return to vendor transactions without moving them to a quarantine location. When set to N, discontinued items must be moved into a quarantine location before they can be inserted into a return to vendor transaction.

RTVM_DEFAULT_REASON_CODE: This parameter determines the reason code that is used when inserting discontinued items into return to vendor transactions without moving them to a quarantine location. This parameter is only used when the ALLOW_RTV_INSERT parameter is set to Y.

Valid values are any reason code from program RERM, Reject/Scrap Reason Code Maintenance.

RTVM_INSPECT_REASON: This parameter determines the reason code from program RERM, Reject/Scrap Reason Code Maintenance, that indicates that the item needs to be inspected. When entering return to vendor lines in program RTVM, Return to Vendor Maintenance, if the line is assigned the reason code defined here, the Inspect flag will be set to on during the pick cycle.

Valid values are any reason code from program RERM, Reject/Scrap Reason Code Maintenance.

RTV_AUTO_CLOSE: This parameter determines whether the return to vendor status changes to Closed after the [Voucher] button is pressed or if it must be changed manually. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.

Valid values are Y or N. When set to Y, the return to vendor status changes to Closed after the [Voucher] button is pressed. When set to N, the return to vendor status must be changed to Closed manually.

RTV_AUTO_CLOSE_PP: This parameter determines whether the return to vendor status changes to Closed after the [Voucher] button is pressed or if it must be changed manually for this plant. Replace the PP with the appropriate plant code.

Valid values are Y or N. When set to Y, the return to vendor status changes to Closed after the [Voucher] button is pressed. When set to N, the return to vendor status must be changed to Closed manually.

RTV_AUTO_PACK_PRINT: This parameter determines whether the return to vendor packing list will be printed automatically from the drill down. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.

Valid values are Y or N. When set to Y, the return to vendor packing list will be printed automatically from the drill down. When set to N, the return to vendor packing list must be printed manually.

RTV_AUTO_PACK_PRINT_PP: This parameter determines whether the return to vendor packing list will be printed automatically from the drill down for this plant. Replace the PP with the appropriate plant code.

Valid values are Y or N. When set to Y, the return to vendor packing list will be printed automatically from the drill down. When set to N, the return to vendor packing list must be printed manually.

RTV_HOLD_INSPECT: This parameter determines when the general ledger journal is created for return to vendor transactions that require inspection. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.

Valid values are Y or N. When set to Y, the general ledger journal is not created when the return to vendor transaction status changes to Picked. If credit is to be received after the vendor inspects the material, the credit journal entries get written when the Inspect Only flag is set to off. When set to N, the general ledger journal is created when the return to vendor transaction status is changed to Picked.

RTV_HOLD_INSPECT_PP: This parameter determines when the general ledger journal is created for return to vendor transactions that require inspection for this plant. Replace the PP with the appropriate plant code.

Valid values are Y or N. When set to Y, the general ledger journal is not created when the return to vendor transaction status changes to Picked. If credit is to be received after the vendor inspects the material, the credit journal entries get written when the Inspect Only flag is set to off. When set to N, the general ledger journal is created when the return to vendor transaction status is changed to Picked.

Service Warranty Parameters

These parameters determine the functionality in program SVMM, Service Master Maintenance.

COMMENT_LOV_SVMM: parameter determines whether double-clicking in a comment text field opens a list of values or an editor in program SVMM, Service Master Maintenance.

Valid values are EDIT or LOV. When set to EDIT, an editor will be displayed. When set to LOV, the boilerplate text lists of values will be displayed.

SVMM_ALLOW_REOPEN: This parameter determines whether when an invoice has not been created on the Failed/Return tab for the service warranty transaction, and the transaction status is Closed, the [Re-open Service] button will be displayed in the header to allow the invoice to be re-opened.

Valid values are Y or N. When set to Y, if an invoice has not been created on the Failed/Return tab for the service warranty transaction, and the transaction status is Closed, the [Re-open Service] button will be displayed in the header that will reopen the transaction. When set to N, service warranty transactions that have been closed cannot be reopened.

SVMM_AUTO_CONFIRM: This parameter determine whether invoices created in program ARIE, One-Step Invoice Entry, from service warranty transactions will be created as confirmed and ready to process. This parameter is used as the default for new sales locations or if the parameter doesn't exist for a specific sales location.

Valid values are Y or N. When set to Y, invoices created in program ARIE, One-Step Invoice Entry, from service warranty transactions will be created as confirmed and ready to be processed. When set to N, the invoice must be confirmed in program ARIE, One-Step Invoice Entry, before being processed through OESJ, Sales Order End of Day and Journals.

SVMM_AUTO_CONFIRM_LLL: This parameter determine whether invoices created in program ARIE, One-Step Invoice Entry, from service warranty transactions in this sales location will be created as confirmed and ready to process. Replace the LLL with the sales location to which the parameter value applies.

Valid values are Y or N. When set to Y, invoices created in program ARIE, One-Step Invoice Entry, from service warranty transactions entered in this location will be created as confirmed and ready to be processed. When set to N, the invoice must be confirmed in program ARIE, One-Step Invoice Entry, before being processed through OESJ, Sales Order End of Day and Journals.

SVMM_DEFAULT_RETURN_TO_TECH: This parameter determines whether the Return to Tech flag on the Failed/Return tab in program SVMM, Service Master Maintenance, is set to on automatically.

Valid values are Y or N. When set to Y, the Return to Tech flag on the Failed/Return tab in program SVMM, Service Master Maintenance, is set to on automatically. When set to N, the Return to Tech flag on the Failed/Return tab in program SVMM, Service Master Maintenance, is set to off automatically.

SVMM_LOCS_SYNCH: When the SVMM_START_IN parameter is set to CUSTOMER, this parameter determines whether the sales location in the header can be changed, or must be kept in synch with the customer's sales location from program CMMM, Customer Master Maintenance.

Valid values are Y or N. When set to Y, the sales location cannot be changed. When set to N, the sales location can be changed.

SVMM_RTN_MORETHAN_ORIGQTY_SOLD: This parameter determines whether or no the quantity failed, expected, and returned can be greater than the original quantity sold for the sales order for that item.

Valid values are Y or N. When set to N, the quantity failed, expected, and returned cannot be greater than the original quantity sold for the sales order for that item. When set to Y, the quantity failed, expected, and returned can be greater than the original quantity sold for the sales order for that item.

SVMM_RTV: This parameter determines whether program SVMM, Service Master Maintenance, will create return to vendor transactions when items are returned to a quarantine location from program SVMM, Service Master Maintenance.

Valid values are Y or N. When set to Y, program SVMM, Service Master Maintenance, will create return to vendor transactions when items are returned to a quarantine location from program SVMM, Service Master Maintenance. When set to N, the items returned to the quarantine location will be added to the appropriate tab in program RTVM, Return to Vendor Maintenance, but a return to vendor transaction will not be automatically created.

SVMM_START_IN: This parameter determines whether the cursor will start in the Invoice No field or the Customer No field when program SVMM, Service Master Maintenance, is run.

Valid values are INVOICE or CUSTOMER. When set to INVOICE, the cursor will start in the Invoice No field when program SVMM, Service Master Maintenance, is run. The sales location and sales reason code cannot be changed when this parameter is set to INVOICE. When set to CUSTOMER, the cursor will start in the Customer No field when program SVMM, Service Master Maintenance, is run.

SVMM_SYNC_COMMENTS: This parameter determines whether when a service warranty transaction is created from a sales order, any comment changes or additional comments added to the service warranty transaction can be updated to the original sales order.

Valid values are Y or N. When set to Y, if the service warranty transaction is created from a sales order, comment changes or additional comments added to the transaction can be updated to the original sales order when the change is saved in program SVMM, Service Master Maintenance. When set to N, the comment will only be written when a sales order or invoice is created from the service warranty transaction.

SVMM_LIMIT_INV_LOV_BY_DAYS: This parameter determines the limit on the order number list of values to be shown. The initial entry is 1000 days, zero days would show all available orders. This parameter is by location.

Sales Order Entry Parameters

Unless otherwise indicated, these parameters have the category ORDER ENTRY.

Automatic Catalog Assignation for Contacts Entered for Mail To Addresses

AUTO_CREATE_CONTACT_CAT: This parameter determines whether a catalog ID will be assigned to the contact record regardless of the setting of the Catalog Ok flag in program MTMM, Mail To/Prospect Input for Catalogs, for the contact record. This parameter is used as the default for new sales locations or if the parameter doesn't exist for a specific sales location.

Valid values are Y or N. When set to Y, the catalog will be assigned to the contact created in program MTMM, Mail To/Prospect Input for Catalogs, regardless of the setting of the Catalog Ok flag for the contact. When set to N, the catalog will be assigned to the contact according to the setting of the Catalog Ok flag for the contact.

AUTO_CREATE_CONTACT_CAT_LLL: This parameter determines whether a catalog ID will be assigned to the contact record regardless of the setting of the Catalog Ok flag in program MTMM, Mail To/Prospect Input for Catalogs, for the contact record in this sales location. Replace the LLL with the sales location code to which the setting applies.

Valid values are Y or N. When set to Y, the catalog will be assigned to the contact created in program MTMM, Mail To/Prospect Input for Catalogs, regardless of the setting of the Catalog Ok flag for the contact. When set to N, the catalog will be assigned to the contact according to the setting of the Catalog Ok flag for the contact.

Automatic Freight Credit Charges Determination

AFC_FROM_PRICING_LOC: This parameter determines whether the automatic freight credit charges for a sales order will be taken from the shipping sales location or the customer sales location when the Price From pop-list for the sales location is set to Price Based on Customer Location.

Valid values are Y or N. When set to Y and the Price From pop-list for the sales order sales location is set to Price Based on Customer Location, the automatic freight credit (AFC) charges settings in the customer's sales location will be used to determine the AFC charges for the sales order. Otherwise, the settings from the shipping sales location are used.

Automatic Mail To Address Creation for Contacts

These parameters determine whether a mail to address should be created when a new address and contact are entered for a customer during sales order entry. These parameters are set up by sales order location and are used in conjunction with the Auto Contact pop-lists in program ARLM, Location Maintenance, for the location.

AUTO_CONTACT_MAIL_ID: This parameter determines whether the mail address pop-up window is displayed in program OEXP, Fast Order Entry, and can be used to override the standard logic and assign new contacts to a different mail to address.

Valid values are Y or N. When set to N, the mail address pop-up window is displayed in program OEXP, Fast Order Entry, and can be used to override the standard logic and assign new contacts to a different mail to address. The [Mail Addresses] $image\ebx_-1808887797.gif$ button in program OEXP, Fast Order Entry, is only displayed when this parameter is set to N. For more information, see program OEXP, Fast Order Entry. When set to Y, standard logic is used as described in the Automatic Contact and Mail To Address Creation section.

AUTO_CREATE_SOLD_ADDR: This parameter determines whether a mail address will be created when a new sold to address is entered for a customer during sales order entry. This parameter is used as the default for new sales locations or if the parameter doesn't exist for a specific sales location.

Valid values are Y or N. When set to Y, and the Sold To Auto Contact pop-list is set to Always or Exclude Drop Ships and a new sold to address or contact is entered for a sales order, the contact and mail to address will be created automatically for the sold to address. When set to N, and the pop-list is set to Always or Exclude Drop Ships and a new sold to address is entered, a mail to address will not be created. However, if a new contact is entered, the contact record will still be created for the customer.

AUTO_CREATE_SOLD_ADDR_LLL: This parameter determines whether a mail address will be created when a new sold to address is entered for a customer during sales order entry in this sales location. Replace the LLL with the sales location code to which the setting applies.

Valid values are Y or N. When set to Y, and the Sold To Auto Contact pop-list is set to Always or Exclude Drop Ships and a new sold to address or contact is entered for a sales order, the contact and mail to address will be created automatically for the sold to address. When set to N, and the pop-list is set to Always or Exclude Drop Ships and a new sold to address is entered, a mail to address will not be created. However, if a new contact is entered, the contact record will still be created for the customer.

AUTO_CREATE_SHIP_ADDR: This parameter determines whether a mail address will be created when a new ship to address is entered for a customer during sales order entry. This parameter is used as the default for new sales locations or if the parameter doesn't exist for a specific sales location.

Valid values are Y or N. When set to Y, and the Ship To Auto Contact pop-list is set to Always or Exclude Drop Ships and a new ship to address or contact is entered for a sales order, the contact and mail to address will be created automatically for the ship to address. When set to N, and the pop-list is set to Always or Exclude Drop Ships and a new ship to address is entered, a mail to address will not be created. However, if a new contact is entered, the contact record will still be created for the customer.

AUTO_CREATE_SHIP_ADDR_LLL: This parameter determines whether a mail address will be created when a new ship to address is entered for a customer during sales order entry in this sales location. Replace the LLL with the sales location code to which the setting applies.

Valid values are Y or N. When set to Y, and the Ship To Auto Contact pop-list is set to Always or Exclude Drop Ships and a new ship to address or contact is entered for a sales order, the contact and mail to address will be created automatically for the ship to address. When set to N, and the pop-list is set to Always or Exclude Drop Ships and a new ship to address is entered, a mail to address will not be created. However, if a new contact is entered, the contact record will still be created for the customer.

AUTO_CREATE_INV_ADDR: This parameter determines whether a mail address will be created when a new invoice to address is entered for a customer during sales order entry. This parameter is used as the default for new sales locations or if the parameter doesn't exist for a specific sales location.

Valid values are Y or N. When set to Y, and the Invoice To Auto Contact pop-list is set to Always or Exclude Drop Ships and a new invoice to address or contact is entered for a sales order, the contact and mail to address will be created automatically for the invoice to address. When set to N, and the pop-list is set to Always or Exclude Drop Ships and a new invoice to address is entered, a mail to address will not be created. However, if a new contact is entered, the contact record will still be created for the customer.

AUTO_CREATE_INV_ADDR_LLL: This parameter determines whether a mail address will be created when a new invoice to address is entered for a customer during sales order entry in this sales location. Replace the LLL with the sales location code to which the setting applies.

Valid values are Y or N. When set to Y, and the Invoice To Auto Contact pop-list is set to Always or Exclude Drop Ships and a new invoice to address or contact is entered for a sales order, the contact and mail to address will be created automatically for the invoice to address. When set to N, and the pop-list is set to Always or Exclude Drop Ships and a new invoice to address is entered, a mail to address will not be created. However, if a new contact is entered, the contact record will still be created for the customer.

AUTO_CREATE_BILL_ADDR: This parameter determines whether a mail address will be created when a new bill to address is entered for a customer during sales order entry. This parameter is used as the default for new sales locations or if the parameter doesn't exist for a specific sales location.

Valid values are Y or N. When set to Y, and the Bill To Auto Contact pop-list is set to Always or Exclude Drop Ships and a new bill to address or contact is entered for a sales order, the contact and mail to address will be created automatically for the bill to address. When set to N, and the pop-list is set to Always or Exclude Drop Ships and a new bill to address is entered, a mail to address will not be created. However, if a new contact is entered, the contact record will still be created for the customer.

AUTO_CREATE_BILL_ADDR_LLL: This parameter determines whether a mail address will be created when a new bill to address is entered for a customer during sales order entry in this sales location. Replace the LLL with the sales location code to which the setting applies.

Valid values are Y or N. When set to Y, and the Bill To Auto Contact pop-list is set to Always or Exclude Drop Ships and a new bill to address or contact is entered for a sales order, the contact and mail to address will be created automatically for the bill to address. When set to N, and the pop-list is set to Always or Exclude Drop Ships and a new bill to address is entered, a mail to address will not be created. However, if a new contact is entered, the contact record will still be created for the customer.

Automatic Mail To Address Creation for Customers

AUTO_CREATE_CUST_ADDR: This parameter determines whether when a customer is created in program CMMM, Customer Master Maintenance, a mail to address will be created automatically. Mail to addresses may still be created when new contacts are created during sales order entry. For more information, see the Automatic Mail To Address Creation for Contacts section.

Valid values are Y or N. When set to Y, when a new customer is created, a mail to address record will be created in program MTMM, Mail To/Prospect Input for Catalogs, for the sold to address. When set to N, when a new customer is created, a mail to address will not be created automatically.

Automatic Re-pricing for Sales Orders when Opened

OE_REPRICE_ON_OPEN: This parameter determines whether sales orders will have the pricing on all line items recalculated when the sales order is opened. For more information, see the Re-pricing Sales Orders when Opened section in the documentation for program OEOE, Sales Order Entry/Maintenance.

Valid values are Y or N. When set to Y, the pricing for the sales order lines will be recalculated when the [Open Order] button is pressed. When set to N, the pricing will not be recalculated.

Upon Insert - Set Invoice Print Flag

OE_INV_PR_FLAG_DEF: This parameter determines whether the print flag on invoices is set to on or off when inserting data through oehead.

default the invoice print flag, value determined by location. It will set the inv_pr_flg value on insert only. It will override any manual setting done prior to insert.

Automatic Release of Sales Orders

AUTO_RELEASE_MODULAR_WO: This parameter will auto release orders created through the cascade process when set to Y.

Automatic Sales Order Acknowledgment and Quote Print

Sales order acknowledgments can be printed from program OEOE, Sales Order Entry/Maintenance, program OQEM, Sales Order Quotation Entry/Maintenance, and program OEXP, Fast Order Entry, automatically when the sales order status changes to O - Complete. Set up is required in this program.

Sales order quotes can be printed from program OEXP, Fast Order Entry, automatically when the sales order status changes to Q - Quotation. Set up is required in this program.

See Printing Order Acknowledgments Automatically and Printing Quotations Automatically for more information on this feature.

AUTO_ACK: This parameter determines whether sales order acknowledgments will be printed automatically when the sales order status changes to O - Complete.

Valid values are Y or N. In order for acknowledgments to be printed, this value must be Y.

AUTO_ACK_PROG: This parameter determines the drill down program that will be used to print the sales order acknowledgment.

Valid values are OEAPT or OEAPX.

AUTO_ACK_OQEM: This parameter determines whether when there is an automatic drill down set up in program OQEM, Sales Order Quotation Entry/Maintenance, to print sales order acknowledgements, the sales order acknowledgement will be printed when the sales quotation is converted to a sales order.

Valid values are Y or N. When set to Y, then the sales order acknowledgement will be printed when the sales order is converted to a sales order. When set to N, the print acknowledgment flag is set to off for the sales quotation before it is converted or saved as won, and the sales order acknowledgment will not be printed.

AUTO_QUOTE_PRINT: This parameter determines whether sales order quotations will be printed automatically when the sales order status changes to Q - Quotation in program OEXP, Fast Order Entry.

Valid values are Y or N. In order for quotations to be printed, this value must be Y.

AUTO_QUOTE_PRINT_PROG: This parameter determines the drill down program that will be used to print the sales order quotation.

Valid value is OQQPX.

Automatic Work Order Creation for Model Items

AUTO_CREATE_MODULAR_WO: This parameter determines whether when a sales order line is entered in program OEXP, Fast Order Entry, program OQEM, Sales Order Quotation Entry/Maintenance, or program OEOE, Sales Order Entry/Maintenance, for a model item, the Create WO flag will be set to on automatically for the item.

Valid values are Y or N. In order for the flag to be set to on, this value must be Y.
See Automatic Work Order Creation for Model Items in the Sales Order Entry Features section for more information on this feature.
See the Work Order Receiving Location section for related information.

Available to Promise Inventory Calculation

ATP_HORIZON_DAYS: This parameter determines number of future days used by the available to promise calculation in program OESP, Soft Pegging, and all sales order entry programs. This is a plant-specific parameter code. If no parameter exists for a plant, this parameter will be used as the default value for that plant.

Valid value is the default number of future days used by the available to promise calculation for plants. The default horizon date setting is 42 days (six weeks). If the parameter value is blank, the system will calculate the available to promise using all types of orders up to 42 days in the future.

ATP_HORIZON_DAYS_PP: This parameter determines number of future days used by the available to promise calculation in program OESP, Soft Pegging, and all sales order entry programs. This is a plant-specific parameter code. Replace the PP in the parameter with the desired plant code.

Valid value is the number of future days used by the available to promise calculation for this plant.

Backorder Reservations Retention

OE_RESV_NO_BO: This parameter determines whether reservations for backordered items will be retained after the original sales order is processed through program OESJ, Sales Order End of Day and Journals.

Valid values are Y or N. When set to Y, the reservations are preserved and attached to the backorder. When set to N, reservations are cleared.

Booked Values include Cancelled Sales Orders

EXCL_CANCELLED_FROM_BOOKED: This parameter determines whether the customer/item booked values will include cancelled sales orders or not. Set up is required in this program at installation time. It is NOT recommended that you change this option at a later date as the booked values will not be updated for periods before the change was made.

Valid values are Y or N. When set to N, cancelled orders will be included in the booked values for customer/item history. When set to Y, cancelled orders will not be included in the booked values for customer/item history.

Comment Lists of Values in Sales Order Entry

COMMENT_LOV_ARIE: This parameter determines whether double-clicking in a comment text field opens a list of values or an editor in program ARIE, One-Step Invoice Entry.

Valid values are EDIT or LOV. When set to EDIT, an editor will be displayed. When set to LOV, the boilerplate text lists of values will be displayed.

COMMENT_LOV_OEDI: parameter determines whether double-clicking in a comment text field opens a list of values or an editor in program OEDI, Sales Order Detail Inquiry.

Valid values are EDIT or LOV. When set to EDIT, an editor will be displayed. When set to LOV, the boilerplate text lists of values will be displayed.

COMMENT_LOV_OEOE: parameter determines whether double-clicking in a comment text field opens a list of values or an editor in program OEOE, Sales Order Entry/Maintenance.

Valid values are EDIT or LOV. When set to EDIT, an editor will be displayed. When set to LOV, the boilerplate text lists of values will be displayed.

COMMENT_LOV_OEXP: parameter determines whether double-clicking in a comment text field opens a list of values or an editor in program OEXP, Fast Order Entry.

Valid values are EDIT or LOV. When set to EDIT, an editor will be displayed. When set to LOV, the boilerplate text lists of values will be displayed.

COMMENT_LOV_OQEM: parameter determines whether double-clicking in a comment text field opens a list of values or an editor in program OQEM, Sales Order Quotation Entry/Maintenance.

Valid values are EDIT or LOV. When set to EDIT, an editor will be displayed. When set to LOV, the boilerplate text lists of values will be displayed.

Comment Sort in Sales Order Programs

OE_COMMENT_SORT: This parameter determines how the sales order comments will be sorted in the sales order programs.

Valid values are: T, S, or D. When set to T, the comments are sorted in comment type and then comment sequence order. When set to S, the comments are sorted by descending comment sequence. When set to D, the comments are sorted by descending date sequence and then descending comment sequence.

Counter Sales Shipping Setup

Program OEPX, Counter Sales Shipping, requires some set up in this program before it can be run from program OEXP, Fast Order Entry.

COUNTER_PRINTER: This parameter determines the printer to which reports will be printed from program OEPX, Counter Sales Shipping.

Valid values include any printer set up in program MUPM, Printer Definition Maintenance.

COUNTER_SALES: This parameter determines whether program OEPX, Counter Sales Shipping, will be run automatically from program OEXP, Fast Order Entry.

Valid values are Y or N. In order for program OEPX, Counter Sales Shipping, to be run automatically from program OEXP, Fast Order Entry, this value must be Y.

OE_DEF_CASH_PAYTYPE: This parameter determines the default payment type for payments entered in program OEPX, Counter Sales Shipping. When the [Process Order] button is pressed, and amount has been entered in the Amount Tendered field, this is the payment type that will be used for the payment record created.

Valid values include any pay type from program SPPT, Payment Type Maintenance.

OE_DEF_HDR_PICK_FLAG: This parameter determines whether the Pick Print Flag is defaulted on or off. If set to , the Pick Print Flag will be checked upon creation of an order in OEOE. If set to , the Pick Print Flag will not be checked. Default is .

OEPX_PICK: This parameter determines the setting and display of the Pick List flag in program OEPX, Counter Sales Shipping. This parameter has the category POINT OF SALE.

Valid values are ON, OFF, or HIDE. When set to ON, the Pick List flag will be set to on automatically. When set to OFF, the Pick List flag will be set to off automatically. When set to HIDE, the Pick List flag will not be displayed in the program.

OEPX_PACK: This parameter determines the setting and display of the Priced Packing List flag in program OEPX, Counter Sales Shipping. This parameter has the category POINT OF SALE.

Valid values are ON, OFF, or HIDE. When set to ON, the Priced Packing List flag will be set to on automatically. When set to OFF, the Priced Packing List flag will be set to off automatically. When set to HIDE, the Priced Packing List flag will not be displayed in the program.

OEPX_INVOICE: This parameter determines the setting and display of the Invoice flag in program OEPX, Counter Sales Shipping. This parameter has the category POINT OF SALE.

Valid values are ON, OFF, or HIDE. When set to YES, the Invoice flag will be set to on automatically. When set to OFF, the Invoice flag will be set to off automatically. When set to HIDE, the Invoice flag will not be displayed in the program.

OEPX_MSDS: This parameter determines the setting and display of the MSDS Sheets flag in program OEPX, Counter Sales Shipping. This parameter has the category POINT OF SALE.

Valid values are ON, OFF, or HIDE. When set to YES, the MSDS Sheets flag will be set to on automatically. When set to OFF, the MSDS Sheets flag will be set to off automatically. When set to HIDE, the MSDS Sheets flag will not be displayed in the program. See MSDS sheets for more information.

Credit Card Payment Reauthorization for Point of Sale orders

POS_CRDR_CODE: This parameter specifies the default sales reason code for sales orders entered through point of sale.

Valid values are any sales reason code from program ARRM, Maintain Sales Reason Codes.

OESJ_RECALC_POS_CC: This parameter determines whether those orders will have their credit card payments reauthorized.

Valid values are Y or N. When set to Y, sales orders with the POS sales reason code will have their credit card payments reauthorized when processed through program OESJ, Sales Order End of Day and Journals. Otherwise, sales orders assigned the POS sales reason code will not have their credit card payments reauthorized when processed through program OESJ, Sales Order End of Day and Journals.

Custom Pricing for Sales Order Lines

PROCPRIC_CPG_REFRESH: When changing a line item quantity, this parameter re-determines the customer price group for a sales order line before re-pricing the line for the new quantity. This parameter is only used in certain cases of custom pricing.

.Valid values are Y or N. Set to N for standard pricing rules. Set to Y f using custom pricing that requires the customer price group to be re-determined when quantities are changed for sales order lines.

Customer / Item Cross Reference Creation in Sales Order Entry

CREATE_CUST_ITEMS_ON_FLY: This parameter determines whether the customer/item cross reference will be created automatically in program ICCR, Customer / Item Cross Reference Maintenance, when a customer item number is entered in the customer item field during sales order entry.

Valid values are Y or N. Set to N to prevent customer / item cross reference records from being created. Set to Y to allow automatic creation of customer/item cross reference records when a customer item number is entered in the customer item field during sales order entry.

Customer Phone Lookup Performance Options

In some cases in sales order entry, when the phone number is being used to look up the customer (such as in program OEXP, Fast Order Entry), if there are a large number of contact phone records, the search may be slow. In order to increase the speed of customer lookups, the standard view can be replaced by a materialized view. The following set up must be completed.

In SQL*Plus, run the following scripts:

As the SYSTEM user, run the nds_mvw_grants script. This script grants the CREATE MATERIALIZED VIEW privilege to the application owner, which is an optional privilege not granted by program MUNU, Maintain Oracle Users.
As the table owner, run the makemvw script to create the materialized views. This script is currently setting the refresh option to COMPLETE. To change to a fast refresh, logs would need to be built on the underlying tables. At the moment, the system is using a periodic refresh using the mvw_refresh script.
As the table owner, run the make_refresh script to refresh all materialized views owned by the user. This script needs to be run periodically to rebuild the materialized views.

In this program, enter the following parameter.

PHONE_LOOKUP_MVW_ACTIVE: This parameter determines whether materialized or standard views will be used for the phone lookups.

Valid values are Y or N. When set to Y, the materialized views will be used for phone lookups. When set to N, standard views will be used for phone lookups.

Customer Quick Search Setup

CUST_QUICK_SEARCH_BUTTON: This parameter determines whether an additional quick search button will be displayed when performing customer searches on the customer search screen in sales order entry. When this button is pressed, the search results will contain only customers that have placed an order in the last three years. .

Valid values include Y or N. When set to Y, the button is displayed. When set to N, the button is hidden.

Customer Sales Order Hold

CUST_ORDER_AUTO_HOLD: This parameter determines whether all sales orders will be placed on hold using the R - Management Review hold code for a customer if that customer has a hold order balance in program CMCM, Customer Credit Maintenance. Only sales orders with the Do No Hold Order flag set to on in the sales order header will not be placed on hold.

Valid values include Y or N. When set to Y, all sales orders will be placed on hold for customers with a hold order balance in program CMCM, Customer Credit Maintenance. When set to N, sales orders will not be placed on hold for customers with a hold order balance in program CMCM, Customer Credit Maintenance

Customer Search / LOV Setup for Sales Order Entry

CUST_LOV: This parameter determines whether the list of values on the customer number in the sales order entry screens is disabled and replaced with the customer search screen. When the user double-clicks in the field or presses F9, the setting of this parameter will determine which opens, the list of values or the search screen.

If you enter blank, l, lov, L, Lov, or LOV, the list of values will be used in the customer field. If you enter SEARCH or anything other than the LOV settings the search screen will be used in the customer field.

Customer Search Default Flag Settings

SEARCH_CB_MAIL_BILL_SHIP_ALL: This parameter determines the default settings of the Bill To, Mail To, Ship To, and All flags for the customer search screen in the sales order entry programs.

Valid value is a series of four Y and N characters. The order in which the characters are entered determines the default settings for the flags. The first character is the default for the Mail To flag. The second character is the default for the Bill To flag. The third character is the default for the Ship To flag. The last character is the default for the All flag. So, a setting of NNNY would default the Mail To, Bill To, and Ship To flags to off and the All flag to on.

Customer Send To Information Update in program OEDI, Sales Order Detail Inquiry

OEDI_SENDTO_CHECKBOX: This parameter determines whether users can update the send to information for customers from sales orders queried in program OEDI, Sales Order Detail Inquiry. This parameter also determines the default value for the Add to Customer Master flag for new send to records entered in program OEDI, Sales Order Detail Inquiry.

Valid values are Y or N. When set to Y, the user can set the Add to Customer Master flag to on in program OEDI, Sales Order Detail Inquiry, for a sales order and update the send to information for the customer. In addition, when entering new send to records in program OEDI, the setting of this flag determines the default value for the new send to records.

Default View in program MOCF, Modular Bill Configuration

MOCF_DEF_VIEW: This parameter determines which values will be displayed in the lower right corner of program MOCF, Modular Bill Configuration, when it is opened to configure a model item from a sales order entry program.

Valid values are A,B,R,I or P. When set to A, the Attributes will be displayed. When set to B, the bill of material will be displayed. When set to R, the routing will be displayed. When set to I, the inventory availability will be displayed. When set to P, the pricing will be displayed.

Editable Fields in Sales Order Entry Header

OE_VAL_SRC_DOC: This parameter determines whether the Src Doc Type and Src Doc ID fields are editable on the Order Codes screen in the sales order entry programs.

Valid values are Y or N. When set to N, the Src Doc Type and Src Doc ID fields are editable. When set to Y, the fields are not editable.

Estimated Freight Removal in Sales Order Entry

OE_REMOVE_FREIGHT: This parameter is used to determine whether the freight costs and charges will be cleared when a change is made in the sales order entry programs that would potentially affect freight calculation. This parameter is generally used by customers doing their own estimated freight. The changes that could potentially affect freight include changing the order terms or ship via code, adding or deleting line items, and changing item quantities.

Valid values are Y or N. When set to N, freight charges and costs are not cleared when the changes are made. When set to Y, freight charges and costs are cleared when the changes are made.

Excluding Send to Records from Sales Orders

OE_SEND_TO_MAX_SEQ: This parameter is used to determine the report classes for which send to records will be placed on each sales order automatically. Send to records associated with a report class with sequence numbers that are less than this value are entered on the sales orders. Sequence numbers are entered in program MURC, Report Class Definitions, for the report class.

Valid value is the first report class sequence number for which the send to records will not be entered on sales orders. All report classes with sequence numbers less than this value will be entered.

Fax Cover Comments for Sales Order Acknowledgments

XMIT_COMMENT_TYPE: This parameter determines the comment type for the comments that will be added to the body text or fax cover for sales order acknowledgements that are emailed or faxed to the customer.

Valid values are any standard or user defined comment type.

Updating Sales Rep Header and Lines

OE_AUTO_UPD_LINE_REPS: This parameter is used for removing the update lines on sales rep message when a sales rep is changed in the header for an order. If set to 'Y', then don't prompt user if they want to update the line item sales reps to match the header sales rep. When header sales rep is changed, automatically update the lines. When set to 'N', the user will be prompted to update the lines.

Item Exists on Open Quote Warning

WARN_ITEM_ON_QUOTE: This parameter determines whether a warning will be displayed when an item entered in program OEOE, Sales Order Entry/Maintenance, program OQEM, Sales Order Quotation Entry/Maintenance, or program CMPV, Price Verification, already exists on another quote or order for the same customer.

*Valid values are Y or N. When set to Y, and an item is entered on a sales order line or in program CMPV, Price Verification, that already exists on another open or incomplete sales order or quotation, a warning will be displayed including the quotation or sales order number on which it has been entered. When set to N, no warning is displayed.

*Item in Discontinued Status

ALLOW_PO_WO_ON_DISCONTINUED: This parameter determines whether or not a purchase order or work order can be created for an item that has been discontinued. Default is Y. If set to N, then user cannot create a WO or a PO for the line item if the item is set as discontinued.

Large Quantity Pricing

OE_STICKY_QTY_PRICE: This parameter determines whether when a sales order line quantity exceeds the highest quantity for the item/item price group and customer/customer price group, the quantity price for the sales order line will be set to the price for the highest quantity bracket entered in the price matrix for the item/item price group and customer/customer price group, taking into consideration all catalog IDs. This provides pricing coverage for large quantities when price matrix is not filled out to upper quantity limit possible.

See the Large Quantity Pricing Feature section for more information.

Valid values include Y or N. When set to Y, the price for the highest quantity bracket will be used instead of the book price, if the quantity ordered is greater than the highest quantity bracket in the price matrix. When set to N, the book price is used.

List Price Warning in Sales Order Entry

OE_LIST_PRICE_WARN: This parameter determines whether a warning will be displayed when the list price is lower than the unit price when sales order lines are entered during sales order entry.

Valid values are Y or N. When set to Y, if a sales order line's list price is lower than the unit price when the sales order line is entered, a warning will be displayed. Otherwise, a warning will not be displayed.

NDS Cash Drawer Opener Parameters

CASH_DRAWER_URL: If the NDS Cash Drawer Opener is installed, this parameter determines the address to engage the serial port and open the cash drawer. The NDS Cash Drawer will be opened if a payment record is entered on a sales order for a payment type for which the Cash Drawer flag is set to on in program SPPT, Payment Type Maintenance. For more information, see program OEPX, Counter Sales Shipping.

Valid value is the web address to engage the serial port and open the cash drawer.

Order Level Discount Parameters

These parameters determine how order level discounts are applied to sales orders. These parameters also have fields in program CMDM, Discount Level Maintenance, that control the values assigned to them. If the parameter is changed here, the change will be reflected in program CMDM, Discount Level Maintenance, and vice versa.

CMDM_AUTO_APPLY: This parameter determines whether discounts will be automatically applied or a pop-up message will be displayed to the user for confirmation before applying the discounts. Corresponds to the Auto apply discounts instead of popup alert flag in program CMDM, Discount Level Maintenance.

Valid values are Y or N. When set to Y, automatically apply the discounts to the sales order lines when the sales order is eligible. Corresponds to the flag being set to on. When set to N, have a pop-up message displayed when the sales order is eligible asking whether you want the order level discounts applied to the sales order. Corresponds to the flag being set to off.

CMDM_CONTRACTS_GET_DISCOUNT: This parameter determines whether order level discounts are used on sales contracts.

Valid values are Y or N. When set to Y, order level discounts are applied to sales contracts. When set to N, order level discounts are not applied to sales contracts.

CMDM_DISC_OVERRIDES_LINE_DISC: This parameter determines whether the initial application of the order level discount to the sales order lines will overwrite existing discounts or whether the [Calc Discount] button must be pressed for that to happen.

Valid values are Y or N. When set to Y, when the order level discount is applied to the sales order, all sales order lines will have the order level discount applied, regardless of whether there is an existing discount on that sales order line. The order level discount will either overwrite or be added to the existing discount depending on the order level discount's settings in program CMDM, Discount Level Maintenance. When set to N, when the order level discount is applied to the sales order, only sales order lines that do not have a discount applied will have the order level discount applied. In order to apply the order level discount to sales order lines with existing discounts, the [Calc Discount] button must be pressed in the sales order entry program.

CMDM_NONSTKS: This parameter determines whether order level discounts will be applied to non-stock sales order lines when the price override flag is set to on. Its value corresponds to the Apply discounts to Nonstocks if price override is on flag in program CMDM, Discount Level Maintenance.

Valid values are Y or N. When set to Y, apply the discounts to non-stocked sales order lines regardless of the setting of the price override flag. Corresponds to the flag being set to on. When set to N, only apply the discounts to non-stocked sales order lines when the price override flag is set to off. Corresponds to the flag being set to off.

CMDM_QUOTES_GET_DISCOUNT: This parameter determines whether order level discounts are used on sales quotations.

Valid values are Y or N. When set to Y, order level discounts are applied to both sales orders and sales quotations. When set to N, order level discounts are applied to sales orders only.

CMDM_USE_GROSS_ORD_VALUE: This parameter determines how the sales order amount will be calculated when determining eligibility for order level discounts. Its value corresponds to the Order Value Based On radio buttons in program CMDM, Discount Level Maintenance.

Valid values are Y or N. When set to Y, uses the sales order line unit price to calculate the order value when determining whether to apply the order level discount. This value corresponds to the Unit Price radio button. When set to N, uses the sales order line list price to calculate the order value when determining whether to apply the order level discount. This value corresponds to the List Price radio button.

CMDM_CUST_OVRD: This parameter determines whether customer specific discounts should override customer price group discounts..

Set this flag to on if the customer has at least one customer specific discount and you want to exclude all customer price group discounts.

Set this flag to off and whichever discount is greater will apply.

Required Margin Warning

OE_REQ_MARGIN: This parameter determines whether a message will be displayed when the margin for a sales order line falls below a specified margin percentage. This parameter is used as the default for new sales locations or if the parameter doesn't exist for a specific sales location.

Valid value is the required margin percentage. This value defaults to 0. When a sales order line item's calculated margin falls below this percentage, a warning will be displayed in the sales order entry program.

OE_REQ_MARGIN_LLL: This parameter determines whether a message will be displayed when the margin for a sales order line falls below a specified margin percentage in the sales location. Replace the LLL with the sales location to which the parameter value applies.

Valid value is the required margin percentage. This value defaults to 0. When a sales order line item's calculated margin falls below this percentage, a warning will be displayed in the sales order entry program.

Sales Commission Settings

OE_EXCLUDE_ZERO_COMM: This parameter determines whether sales representatives with a zero percent commission will be included in the sales order header.

Valid values are Y or N. When set to Y, then sales representatives will not be included in the sales order header if the sales commission percentage is zero. When set to N, they will be included in the sales order header.

Sales Location Updates during Sales Order Entry

OE_LOCATION_UPD_ALLOWED: This parameter determines whether the sales location can be manually changed during sales order entry when the Default Location Rule in program SPON, Order and Invoice Number Control, is set to Login.

Valid values are Y or N. When this parameter is set to N, users cannot manually change the location during sales order entry, although the location may change during processing, such as if the ship to location changes and the default shipping location is derived from the ship to location.

When this parameter is set to Y, then users can manually change the sales location during sales order entry.

Sales Order Acknowledgment Print Parameters

Valid values are Y or N. When set to Y, then the sales order acknowledgement will be printed when the sales order is converted to a sales order. When set to N, the print acknowledgment flag is set to off for the sales quotation before it is converted or saved as won, and the sales order acknowledgment will not be printed.

OEAF_UPDATE: This parameter determines whether program OEAF, Maintain Acknowledgment Print Flags, will force the Print Acknowledgment flag to on for sales orders when printing is complete. This value is dependent on the version of OEAP.rdf that you are running.

Valid values are Y or N. This value is dependent on the version of OEAP.rdf that you are running. If you are running a standard version of OEAP.rdf or a custom version that does NOT set the print flag to off, then set this value to Y. However, if the custom OEAP.rdf that you are running is also setting the print flag to off, set this value to N or leave it blank. Otherwise, you will receive 'record updated by another user' errors when printing sales acknowledgments.

OEAP_PRINT_COMMENT_TYPE: This parameter determines the comment type that will print on the order acknowledgement when program OEAPL, Print Order Acknowledgements (Laser), is run. This comment type is in addition to the OE comment type that prints on the report by default.

Valid values are any user-defined or standard comment type that you wish to print on the report.
For custom versions, this functionality must be added. Contact NDS Professional Services for more information.

Sales Order Comment Print Flag Defaults

OEHEAD_COMMENTS_PRINT_FLAG: This parameter determines the default setting of the print flag for new sales order header comments in the sales order entry programs.

Valid values are Y or N. When set to Y, the print flag will be set to on. When set to N, the print flag will be set to off.

OE_LINE_COMMENTS_PRINT_FLAG: This parameter determines the default setting of the print flag for new sales order line comments in the sales order entry programs.

Valid values are Y or N. When set to Y, the print flag will be set to on. When set to N, the print flag will be set to off.

Sales Order Copy - Automatic Debit Memo/Credit Memo Confirmation

OECO_AUTO_CONFIRM: This parameter determines whether debit memos and credit memos created from program OECO, Sales Order Copy, will be automatically confirmed upon creation. Debit and credit notes are always confirmed on creation from program OECO, Sales Order Copy. This parameter is used as the default for new sales locations or if the parameter doesn't exist for a specific sales location.

Valid values are Y or N. When this parameter is set to Y, then credit and debit memos are automatically confirmed on creation. If set to N, null, or non-existent, credit and debit memos are not confirmed and must be manually confirmed in program ARIE, One-Step Invoice Entry, before they can be processed through program OESJ, Sales Order End of Day and Journals.

OECO_AUTO_CONFIRM_LLL: This parameter determines whether debit memos and credit memos created from program OECO, Sales Order Copy, will be automatically confirmed upon creation in this sales location. Debit and credit notes are always confirmed on creation from program OECO, Sales Order Copy. Replace the LLL with the sales location code to which this parameter value applies.

Valid values are Y or N. When this parameter is set to Y, then credit and debit memos are automatically confirmed on creation. If set to N, null, or non-existent, credit and debit memos are not confirmed and must be manually confirmed in program ARIE, One-Step Invoice Entry, before they can be processed through program OESJ, Sales Order End of Day and Journals.

Sales Order Copy - Default Status for Copied Sales Orders

OECO_DEFAULT_STATUS: When accessing program OECO, Sales Order Copy, from the menu, this parameter determines the default order status in the New Status pop-list for the non-quote, ORD type orders being created in program OECO, Sales Order Copy, by copying an existing order. This parameter overrides the Initial Order Status from program ARLM, Location Maintenance, if a value is assigned to it. For example, you can have the default initial order status in program ARLM, Location Maintenance, set to I - In-Process for orders created through regular sales order entry and have the sales orders created from program OECO, Sales Order Copy, default to O - Open.

Valid values are O, Q, I, or T. O - Open, Q - Quote, I - In-Process, T - Template.

Sales Order Cost Change

OE_ANY_COST_CHANGE: This parameter determines whether unit cost change is allowed on sales orders entered in program OEOE, Sales Order Entry/Maintenance, regardless of the standard rules.

Valid values are Y or N. When this parameter is set to Y, unit cost change is allowed on sales orders entered in program OEOE, Sales Order Entry/Maintenance, regardless of the standard cost rules. When this parameter is set to N, standard cost rules are followed.

Sales Order Default Sort

OE_DEFAULT_SORT: This parameter determines the default order in which sales orders will be listed when queried in sales order entry programs.

Valid values are O, L, or D.

O - Sales orders will be listed in order by descending order number when queried in the sales order entry programs.

L - Sales orders will be listed in order by ascending sales location code, and then by descending order number when queried in the sales order entry programs.

D - Sales orders will be listed in order by order date and then by descending order number when queried in the sales order entry programs.

Sales Order Line Item Lookup

OE_ITEM_LOOKUP_CUST_FIRST: This parameter determines whether when entering items in sales order entry, the customer cross reference will be searched before the item master.

Valid values are Y or N. When this parameter is set to Y, the customer cross reference will be searched before the item master when items are entered in sales order entry.

Sales Order Merge Settings

OECH_CUST_PO_TEXT: This parameter determines whether the customer purchase order and purchase order line on the primary sales order will be copied to the primary sales order lines, replaced by the text entered for this parameter. When a value is entered for this parameter and a primary sales order with values in the Cust PO and Cust PO Line fields is merged, the values will be transferred to the line items for the primary sales order, and the value for the parameter will be entered in the Cust PO field for the primary sales order.

Valid value is up to 30 characters of text.

Sales Order Price Group Display

OEOE_SHOW_PRICE_GROUP: This parameter determines whether the customer price group and description are displayed in program OEOE, Sales Order Entry/Maintenance, to the right of the sales location.

Valid values are Y or N. When set to Y, then the customer price group and price group description are to the right of the Loc field during sales order entry in program OEOE, Sales Order Entry/Maintenance. When set to N, the price group information is not displayed.

Sales Order Revenue Pricing Options

OE_QUICK_PRICE: This parameter determines whether pricing will be delayed for sales orders for customers with the Revenue Pricing Method until the status of the sales order or quotation changes or until the summary screen is opened during sales order with program OQEM, Sales Order Quotation Entry/Maintenance, and program OEOE, Sales Order Entry/Maintenance.

Valid values are Y or N. When set to N, the pricing will occur as the sales order lines are entered for customers with Revenue Pricing. When set to Y, sales order lines for customers with Revenue Pricing will not be priced until the following parameters are met:

In program OQEM, Sales Order Quotation Entry/Maintenance, the sales order status changes from Q - Quotation to O - Open Order.

In program OEOE, Sales Order Entry/Maintenance, the sales order status changes from I - Incomplete to O - Open Order.

In both programs, the summary screen is opened.

In addition, this parameter determines when order level discounts are calculated when entering sales orders in program OEXP, Fast Order Entry

When set to N, the order level discounts are calculated when you navigate between tabs in program OEXP, Fast Order Entry. When set to Y, the order level discounts are calculated when the order is generated or when the commit is forced with the [Commit] $image\ebx_980670422.gif$ button on the item tab.

Sales Order Splitter Setup

Program OESS, Order Splitter by Plant (Interactive), and program OESSB, Order Splitter by Plant (Batch Mode), use parameters set up in this program to determine the settings for pricing preservation and comment type when sales orders are split by plant using these programs.

OESS_COMMENT_TYPE: This parameter determines the comment type that will be entered for the comment created when sales orders are split by plant.

Valid values are any user-defined or standard comment type.

OESS_PRESERVE_PRICING: This parameter determines the default setting of the Preserve Pricing flag in program OESS, Order Splitter by Plant (Interactive) and whether or not pricing will be preserved when program OESSB, Order Splitter by Plant (Batch Mode), is run.

Valid values are Y or N.

When set to Y, the Preserve Pricing flag in program OESS, Order Splitter by Plant (Interactive), will be set to on by default. When set to N, the Preserve Pricing flag in program OESS, Order Splitter by Plant (Interactive), will be set to off by default.

When set to Y, pricing will be preserved when program OESSB, Order Splitter by Plant (Batch Mode), is run. When set to N, pricing will be recalculated for the new plant when program OESSB, Order Splitter by Plant (Batch Mode), is run.

Sales Order to Purchase Order Comments Setup

OEPO_COMMENT_COPY: This parameter determines the comments that are copied when purchase orders are created from sales order lines, and the sales order line comments are written to the purchase order line. All comments containing the type entered in the parameter will be copied. For example, if the type entered is PO, comments with PO, POR, POQ, QAPO, etc will be copied.

Valid values are any the comment type entered on the sales order line comments that will be copied to the purchase order. For example, if the type entered is PO, comments with PO, POR, POQ, QAPO, etc will be copied.

Sales Order to Work Order Comment Copy

OEWO_COMMENT_COPY: This parameter determines the comment types that will be copied from the sales order to the work order when a work order is created from a sales order line.

Valid values are any user-defined or standard comment type.

Sales Quotation Comment Types

OQQP_PRINT_COMMENT_TYPE: This parameter determines the comment type that will print on the sales order quotation when program OQQP, Quotation Print, is run. This comment type is in addition to the OE comment type that prints on the report by default.

Valid values are any user defined or standard comment types.

Sales Quotation Drop Ship Purchase Orders

OQEM_DROP_SHIP_PO: This parameter determines whether the Create PO flag will be set to on automatically for drop ship items.

Valid values are Y or N. When set to Y, the Create PO flag will be set to on for drop ship items entered on sales order quotations. When set to N, the Create PO flag will be set to off for drop ship items entered on sales order quotations.

Sales Quote to Order Conversion Options

New features added, version 7.5.4 Patches, 8.4 Patches

OQEM_USES_ARLM_STATUS: This parameter determines whether the sales order created when a sales quotation is converted will use the Initial Order Status value from program ARLM, Location Maintenance.

Valid values are Y or N. When set to Y, then the sales order will be assigned the Initial Order Status from program ARLM, Location Maintenance. When set to N, the sales order will be assigned the status of O - Complete upon conversion.

QUOTE_CONVERT_RECALC_DATES: This parameter determines whether the estimated ship date, request date, and initials will be recalculated when a sales quotation is converted to a sales order.

Valid values are Y or N. When set to Y, the request date and estimated ship date will be recalculated according to the sales order date, and the initials will be changed to that of the user who converted the quote to the sales order. When set to N, all values will remain as they were entered on the original quote.

Settings for program OEXP, Fast Order Entry

These parameters determine the settings for various features in program OEXP, Fast Order Entry.

COMMENT_LOV_OEXP: parameter determines whether double-clicking in a comment text field opens a list of values or an editor in program OEXP, Fast Order Entry.

Valid values are EDIT or LOV. When set to EDIT, an editor will be displayed. When set to LOV, the boilerplate text lists of values will be displayed.

OEXP_AUTOSAVE_LOST_QUOTES: This parameter determines whether sales orders cancelled in program OEXP, Fast Order Entry, will be saved as lost quotes. This parameter is used as the default for new sales locations or if the parameter doesn't exist for a specific sales location.

Valid values are Y or N. When set to Y, all cancelled sales orders will be saved as lost quotes. When canceling the sales order in program OEXP, Fast Order Entry, there are only two buttons - [Return] and [Clear and Save as Lost Quote]. When set to N, users can elect to save the cancelled orders as a lost quote or simply clear the order. When canceling the sales order in program OEXP, Fast Order Entry, there are three buttons - [Return], [Clear], and [Save as Lost Quote].

OEXP_AUTOSAVE_LOST_QUOTES _LLL: This parameter determines whether sales orders cancelled in program OEXP, Fast Order Entry, will be saved as lost quotes for this sales location. Replace the LLL with the desired sales location code.

Valid values are Y or N. When set to Y, all cancelled sales orders will be saved as lost quotes. When canceling the sales order in program OEXP, Fast Order Entry, there are only two buttons - [Return] and [Clear and Save as Lost Quote]. When set to N, users can elect to save the cancelled orders as a lost quote or simply clear the order. When canceling the sales order in program OEXP, Fast Order Entry, there are three buttons - [Return], [Clear], and [Save as Lost Quote].

OEXP_COMPL_NONMAINT: This parameter determines whether the Ship Complete Only flag for the sales order will be set to on automatically if the sales order contains any non-maintain on hand items for sales orders entered in program OEXP, Fast Order Entry.

Valid values are Y or N. When set to Y, the Ship Complete Only flag for the sales order will be set to on automatically if the sales order contains any non-maintain on hand items.

OEXP_COMPL_NONSTOCK: This parameter determines whether the Ship Complete Only flag for the sales order will be set to on automatically if the sales order contains any non-stock items for sales orders entered in program OEXP, Fast Order Entry.

Valid values are Y or N. When set to Y, the Ship Complete Only flag for the sales order will be set to on automatically if the sales order contains any non-stock items.

OEXP_LOC: This parameter determines whether an entry is required in the Letter of Credit field for sales orders entered in program OEXP, Fast Order Entry.

Valid values are OPTIONAL or REQUIRED. When set to OPTIONAL, the Letter of Credit field is displayed, but is not required to be entered. When set to REQUIRED, the Letter of Credit field is displayed and is required to be entered.

OEXP_LOST_QUOTE_REASON: This parameter determines whether a reason code must be entered when a quote is saved as a lost quote from program OEXP, Fast Order Entry. Reason codes for lost quotes are set up in program CMRC, Complaint Reason Codes Maintenance and are stored in the quote header.

Valid values are Y or N. When set to Y and a quote is saved as a lost quote from program OEXP, Fast Order Entry, the user is alerted to enter a reason.

OEXP_PF: This parameter determines whether e Price From pop-list, Price Plant field, and [Reprice] $image\ebx_-1954182126.gif$ button will be displayed in program OEXP, Fast Order Entry.

Valid values are Y or N. When set to Y, the Price From pop-list, Price Plant field, and [Reprice] $image\ebx_-1954182126.gif$ button will be displayed. Otherwise, they will be hidden.

OEXP_PHONE_LOOKUP: This parameter determines whether when the user presses the 'F9' key on the keyboard when in the Contact Phone field, the system will open the customer lookup based on phone number or will open a list of values of contacts.

Valid values are Y or N. When set to Y, when the F9 is pressed in the contact phone field, the system will open the lookup screen that looks the customer up based on phone number entered. When set to N, the list of values will open.

OEXP_RA: This parameter determines whether an entry is required in the Release Authorization field in program OEXP, Fast Order Entry.

Valid values are OPTIONAL or REQUIRED. When set to OPTIONAL, Release Authorization the field is displayed, but is not required to be entered. When set to REQUIRED, the Release Authorization field is displayed and is required to be entered.

OEXP_ROLLOUT_MODE: This parameter determines whether sales orders in program OEXP, Fast Order Entry, will initialize from the template order rather than the dummy order, preserving any line items from template. Sales orders and quotes will be created using the template customer instead of creating a new customer. This allows sales orders and quotes to be shipped to people without setting them up as separate customers.

Valid Values are Y or N. When set to Y, sales orders in program OEXP, Fast Order Entry, will initialize from the template order rather than the dummy order, preserving any line items from template and allowing sales orders and quotes to be shipped to people without setting them up as separate customers

OEXP_SAVE_THP_ACCT: This parameter determines whether the third party account will be added to the customer master record in program CMMM, Customer Master Maintenance, when a sales order or quotation is created, and the third party account does not already exist. The following rules are applied:

If the ship to code is SAME or DROP, the third party account is entered with a null ship to code.

If no carrier vendor is entered on the Summary tab, then the account will not be added to program CMMM, Customer Master Maintenance.

If the vendor entered does not match the vendor assigned to the ship via code in program SPSF, Ship Via Code Maintenance, then the user will be notified and the account will not be saved.

Valid values are Y or N. When set to Y, the third party account will be added to the customer master record in program CMMM, Customer Master Maintenance, when a sales order or quotation is created, and the third party account does not already exist.

OEXP_SHIPTO_SAVE: This parameter determines whether when a ship to address is changed in program OEXP, Fast Order Entry, for a customer order, the ship to record in program CMMM, Customer Master Maintenance, and the mail to address record in program MTMM, Mail To/Prospect Input for Catalogs, will be updated with the change.

Valid values are Y, N, or ASK. When this parameter is set to Y, when a ship to address is changed in program OEXP, Fast Order Entry, for a customer order, the ship to record in program CMMM, Customer Master Maintenance, and the mail to address record in program MTMM, Mail To/Prospect Input for Catalogs, will be updated with the change.

When this parameter is set to ASK, and a ship to address is changed in program OEXP, Fast Order Entry, the user will be asked if the ship to address in program CMMM, Customer Master Maintenance, should also be updated. If the user selects Yes, both the ship to record in program CMMM, Customer Master Maintenance, and the mail to address record in program MTMM, Mail To/Prospect Input for Catalogs, will be updated with the change.

When this parameter is set to N, and a ship to address is changed in program OEXP, Fast Order Entry, the ship to address will not be updated in program CMMM, Customer Master Maintenance.

OEXP_USE_STD_MAN_LOGIC: This parameter determines whether the standard processing for the manual entry of customers in this program will be used. This processing allows users who are authorized for multiple financial enterprises to enter a customer with the sales location for a financial enterprise different than the financial enterprise presently associated with the order. Program OEXP, Fast Order Entry, then automatically changes the sales location and the associated financial enterprise, manufacturing enterprise, and plant of the sales order to match the customer default.

Valid values are Y or N... When this parameter is set to Y, the standard processing for the manual entry of customers in this program will be used. When this parameter is set to N, it indicates that the program should access the custom code to return the appropriate location or error message. This custom code is located in the user's procuser.sql: procuser.oexp_manual_entry.

OEXP_USER_VW_FIELD1_TITLE: The entry for this parameter determines the label for Field 1 on popup screen accessed with the custom popup $image\ebx_-1182321424.gif$ button.

Valid values are any string of characters to use as the label.

OEXP_USER_VW_FIELD2_TITLE: The entry for this parameter determines the label for Field 2 on popup screen accessed with the custom popup $image\ebx_-1182321424.gif$ button.

Valid values are any string of characters to use as the label.

OEXP_USER_VW_TITLE: The entry for this parameter determines the title on the popup screen accessed with the custom popup $image\ebx_-1182321424.gif$ button.

Valid values are any string of characters to use as the title.

OEXP_VALIDATE_CONTACT: This parameter determines whether contacts are validated against a list of contacts for the customer when sales orders are entered in program OEXP, Fast Order Entry.

Valid values are Y or N. When set to Y, the user is forced to choose from the list of values when entering a contact. If the contact does not exist, the user must create one through a drill down to program SPWM, System Contacts Maintenance, before entering the sales order. When set to N, the contact is not validated when the order is entered.

OEXP_VALIDATE_SRCDOCID: The parameter determines whether the value entered in the Src Doc ID field on the Customer Tab in program OEXP, Fast Order Entry, will be validated against the user defined list of values for that field.

Valid values are Y or N. When set to Y, the value entered in the Src Doc ID field on the Customer Tab in program OEXP, Fast Order Entry, will be validated against the user defined list of values for that field. The list of values for the field is defined in program UTLV, LOV Configuration, as the OEXPSRCDOC list of values ID. When set to N, the value will not be validated against the list.

Ship To Address Creation for Sales Orders

OE_ALLOW_SHIPTO_CREATE: This parameter determines whether users can create new ship to addresses or update existing addresses for customers in program ARIE, One-Step Invoice Entry, program OQEM, Sales Order Quotation Entry/Maintenance, and program OEOE, Sales Order Entry/Maintenance.

Valid values are Y or N. When set to Y, users can create new ship to addresses and update existing ship to addresses when entering sales orders for existing customers. When set to N, users cannot create new ship to addresses or update existing ship to addresses when entering sales orders for existing customers.

Ship To Attn Defaults

SHIP_ATTN_DEFAULT: This parameter determines whether during sales order entry, the ship to attention field value will always default from the ship to record's attn field, regardless of the value.

Valid values are Y or N. When set to Y, the ship to attn value will always default to the one in assigned to the ship to code, regardless of the value. If the ship to code's attn field is null, it will retrieve the null from the ship to code. When set to N, if the ship to attn is entered in the form, the ship to attn will not be retrieved from the ship to code.

Supersede Item Comments

OE_ADD_SUPERSEDE_COMMENTS: This parameter determines whether a comment will be written to the line item comments when an item is superseded on a sales order line.

Valid values are Y or N. When this parameter is set to N, supersede comments will not be entered on the sales order line when the item is superseded.

Vendor and Buyer Requirements in Sales Orders and Model Configurations

OE_REQ_VENDOR_BUYER: This parameter determines whether the vendor and buyer are required for purchased sales order line and component items. For model configurations, this parameter is used in conjunction with the flag settings in program POSE, Create Purchase Orders from Sales. For more information, see the Vendor/Buyer Requirements for Modular Components section.

Valid values are Y or N. When this parameter is set to Y, the vendor and buyer are required to be entered for purchased model components in program MOCF, Modular Bill Configuration, dependent on the settings of the flags in program POSE, Create Purchase Orders from Sales. The vendor and buyer are also required to be entered for purchased line items during sales order entry.

When this parameter is set to N, the vendor and buyer are not required to be entered for purchased model components in program MOCF, Modular Bill Configuration or purchased line items.

Will Call Hold Setup

WILL_CALL_HOLD: This parameter determines whether the will call hold feature is activated from sales orders shipping.

Valid values are Y or N. When set to Y, sales orders with the sales reason code of W - Will Call Hold will be placed on will call hold in program OESC, Shipping Confirmation. When set to N or missing, sales orders with the sales reason code W - Will Call Hold will not be placed on hold during shipping.

Work Order Creation Status for Model Items on Sales Orders

AUTO_RELEASE_MODULAR_WO: This parameter determines the status of a work order created from a sales order line in program OEXP, Fast Order Entry, program OQEM, Sales Order Quotation Entry/Maintenance, or program OEOE, Sales Order Entry/Maintenance.

Valid values are Y or N. When set to Y, all modular and regular items will be released and the status will become Open. When set to N, the status will remain Pending.

Zip Code Validation

OE_ZIP_WARN_ONLY: This parameter determines whether a warning or an error is displayed when an invalid zip code is entered during sales order entry for a country with the Validate Zip Code checkbox set to on in program SPNM, Country Code Maintenance.

Valid values are Y or N. When set to Y, a warning will be displayed when an invalid zip code is entered on a sales order. When set to N, an error will be displayed when an invalid zip code is entered on a sales order, and the zip code must be corrected before the sales order can be saved.

Return to See Also List

Sales Order Shipping Parameters

Unless otherwise indicated, these parameters have the category SHIPPING.

Shipping Container Segregation by Plant

COMINGLE_PALLETS: This parameter determines the default setting of the Comingle Pallets flag in the sales order header. When the flag is set to on, shipping can be done in any container for an order, regardless of the sales order line plant. When the flag is set to off, a plant cannot ship in containers that are already in use on a sales order line by another plant. Valid ues are Y or N. When set to Y, the Comingle Pallets flag in the sales order header will be set to on automatically. When set to N, the Comingle Pallets flag in the sales order header will be set to off automatically.

OEKF Default Pick Flag

OEKF_RESET_DTL_PICK_FLAG determines whether the Force Pick Line to Y on All Lines checkbox is defaulted to checked or not in OEKF. Default is N. If murm is set to Y, the checkbox will default as checked on. The checkbox can be changed in OEKF.

Setting Drop List for Default Plant

OEKF_PLANT: This parameter determines the default for the plant drop list to all plants instead of the default plant. Default is null for standard, 'A' or 'ALL' for all plants or enter the plant you want it to default to.

Automatic Backorders for Shipping Allocations

OESHIP_AUTO_BACKORDER: This parameter determines the default setting of the Auto Backorder flag in the sales order header. When the flag is set to on and shipping is initialized, the ordered amounts will be defaulted into the Backorder field for the sales order line. This retains sales allocations for the sales order line until shipping is completed. If the customer does not allow backorders, the Remove Backorders flag will be set to on automatically as well, so that the backorders are removed automatically when shipping is complete. When the flag is set to off, and shipping is initialized, the ordered quantities will not be defaulted into the backordered field.

Valid values are Y or N. When set to Y, the Auto Backorder flag in the sales order header will be set to on automatically. When set to N, the Auto Backorder flag in the sales order header will be set to off automatically.

Case Splitting during Sales Order Staging

CASE_SPLIT_STAGE: This parameter determines whether cases will be split when the [Auto Stage] button is pressed in program OSEM, Stage Sales Order for Shipping.

Valid values are Y or N. When set to Y, the cases will be split according to the Split Staging Rule pop-list in program ARLM, Location Maintenance. When set to N, the cases will not be split regardless of the setting of the pop-list.

Comment Lists of Values in Sales Order Shipping

COMMENT_LOV_OESC: parameter determines whether double-clicking in a comment text field opens a list of values or an editor in program OESC, Shipping Confirmation.

Valid values are EDIT or LOV. When set to EDIT, an editor will be displayed. When set to LOV, the boilerplate text lists of values will be displayed.

COMMENT_LOV_OESX: parameter determines whether double-clicking in a comment text field opens a list of values or an editor in program OESX, Shipping Director.

Valid values are EDIT or LOV. When set to EDIT, an editor will be displayed. When set to LOV, the boilerplate text lists of values will be displayed.

Containerizing Staged Sales Orders

AUTO_CONTAINERIZE: This parameter determines how staged sales order lines will be containerized when the [Containerize] button is pressed in program OSEM, Stage Sales Order for Shipping.

Valid values are O, S, or P:

When set to 'O', all of the staged lines are put into one container.

When set to 'S', one container is created per staging line, regardless of the case quantity or case per pallet quantity in program ICPM, Inventory Planning Data Maintenance.

When set to 'P', when containerizing the order, the program will go through all of the staged lines on the order.
For items with a case per pallet value of 0 or 1 in program ICPM, Inventory Planning Data Maintenance, the program will create one container record for each staging line.
If the case per pallet for an item is greater than 1, the program will ask whether you want to create the containers as one per staging line or one per pallet. If one per staging line is chosen, one container per staging line will be created. If one per pallet is chosen, one container per pallet will be created.

Pricing Changes in program OESC, Shipping Confirmation

OESC_ALLOW_PRICE_CHANGES: This parameter determines whether or not unit prices can be modified for sales order line items during shipping with program OESC, Shipping Confirmation.

Valid values are Y or N. When set to Y, the user can set to Override flag to the desired setting and change the unit price, or modify the extended price to force a flat discount. When set to N, no price changes are allowed.

Print Pack List Flag Setting in OESC, Shipping Confirmation

OE_SHIP_PACK_ALWAYS: This parameter determines whether the Print Pack List flag will be set to on when the [Ship Order] and [Manually Ship Order] buttons are pressed in program OESC, Shipping Confirmation.

Valid values are Y or N. When set to N, the flag will not be affected when one of the buttons is pressed. When set to Y or blank, the flag will be set to on when one of the buttons is pressed.

Print Foreign Packing List Copies in OESC, Shipping Confirmation

FOREIGN_PACKLIST_COPIES: parameter to set the number of foreign packing slips to print. Default is 4 if NULL.

Print Invoice Flag in OESC, Shipping Confirmation

SHIPPING_INV_DOC: parameter to control the invoice print checkbox on printdocs window. Default is N for not checked. If set to N, then the system does not check oehead and does not print an invoice. If set to Y, then system checks OESX murms for which invoice drill down to run.

Sales Order Batch Shipping Future Order Protection

OESB_FUTURE_ALLOC: This parameter determines whether sales orders with future due dates within the item lead time from the current end date will have their quantity subtracted from the nettable on hand when evaluating whether a sales order line is shippable and the quantity to ship. This prevents later sales orders from using the inventory for a sales order with a future due date. In order to preserve the priority when a future sales order becomes shippable, the Ship Priority Method pop-list in program ILPM, Plant Code Maintenance, should be set to Order Date.

Valid values are Y or N. When set to Y, the feature acts as described above.

Sales Order Batch Shipping Parameters

New parameters added, version 7.5.3, 8.1

These parameters determine the default settings of parameters in program OESB, Sales Order Batch Shipping and for the background batch shipping process that can be set up in program JOBQ, NDS Job Queue Management.

BATCH_SHIP_EVAL_INTERVAL: This parameter determines the number of minutes that a given order will be suspended for shipping evaluation following a failed evaluation and is the default for the Order Eval Interval field in program OESB, Sales Order Batch Shipping. With this feature active, if an inventory transaction occurs which adds inventory, any open sales orders for that item will have their evaluation timers reset so they become available for shipment. When set to a negative number, the feature is disabled. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.

Valid value is a numeric value. When set to a positive number, this is the number of minutes that a given order will be suspended for shipping evaluation following a failed evaluation.

BATCH_SHIP_EVAL_INTERVAL_PP: This parameter determines the number of minutes that a given order will be suspended for shipping evaluation following a failed evaluation and is the default for the Order Eval Interval field in program OESB, Sales Order Batch Shipping for this plant. With this feature active, if an inventory transaction occurs which adds inventory, any open sales orders for that item will have their evaluation timers reset so they become available for shipment. When set to a negative number, the feature is disabled.

Valid value is a numeric value. The PP in the parameter above should be replaced with the plant code when setting up this variable. When set to a positive number, this is the number of minutes that a given order will be suspended for shipping evaluation following a failed evaluation.

OESB_BG_MAIL_TO: This parameter determines the email address to which failures will be sent for background batch shipping job in program JOBQ, NDS Job Queue Management.

Valid values are any email address.

OESB_BG_COPY_TO: This parameter determines the email address to which failures will be copied for the background batch shipping job in program JOBQ, NDS Job Queue Management.

Valid values are any email address.

OESB_BG_ORDER_LIMIT: This parameter determines the number of orders to process before exiting. Once this number of orders has been processed, the background cycle will exist regardless of the amount of time that has passed. This parameter can be used in conjunction with the OESB_BG_TIME_LIMIT parameter. If left blank, then the limit will not be tested. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.

Valid value is numeric.

OESB_BG_ORDER_LIMIT_PP: This parameter determines the number of orders to process before exiting when running background batch shipping for this plant. Once this number of orders has been processed, the background cycle will exist regardless of the amount of time that has passed. This parameter can be used in conjunction with the OESB_BG_TIME_LIMIT parameter. If left blank, then the limit will not be tested. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.

Valid value is numeric. The PP in the parameter above should be replaced with the plant code when setting up this variable.

OESB_BG_TIME_LIMIT: This parameter determines the maximum time to spend in a cycle. Once this amount of time has passed, the background cycle will exit regardless of number of orders processed. This parameter can be used in conjunction with the OESB_BG_ORDER_LIMIT parameter. If left blank, then the limit will not be tested. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.

Valid value is numeric.

OESB_BG_TIME_LIMIT_PP: This parameter determines the maximum time to spend in a cycle when running background batch shipping in this plant. Once this amount of time has passed, the background cycle will exit regardless of number of orders processed. This parameter can be used in conjunction with the OESB_BG_ORDER_LIMIT parameter. If left blank, then the limit will not be tested. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.

Valid value is numeric. The PP in the parameter above should be replaced with the plant code when setting up this variable.

OESB_FORCE_UPROC25: This parameter determines whether the procuser.uproc25 should run even if there are not any pick tickets to print. If set to Y and the oesb pick ticket print routine does not think there are any pick tickets to print, then run the system will run the procuser.uproc25 routine anyway, since other functions within uproc25 need to run. Default is N.

Sales Order Pack List Printing Parameters

OEPL_PRINT_COMMENT_TYPE: This parameter determines the comment type that will print on the packing list when program OEPLL, Sales Order Packing List (Laser), is run. This comment type is in addition to the OE comment type that prints on the report by default.

Valid values include any user-defined or standard comment type.
For custom version of these reports, this functionality must be added. Contact NDS Professional Services for more information.

Sales Order Pick List Printing Parameters

OEPR_PRINT_COMMENT_TYPE: This parameter determines the comment type that will print on the pick list when program OEPRL, Sales Order Pick List (Laser), is run. This comment type is in addition to the OE comment type that prints on the report by default.

Can be set up by plant.
Valid values include any user-defined or standard comment type.
For custom version of these reports, this functionality must be added. Contact NDS Professional Services for more information.

Shipping Confirmation Parameters

These parameters determine parameters for the functionality of program OESC, Shipping Confirmation.

OESC_BO_RED: This parameter determines whether non-zero backorder quantities are displayed in red on the order lines.

Valid values are Y or N. When set to Y, they are displayed in red. When set to N, they are not.

OESC_DISPLAY_MODE: This parameter determines the default setting for the Display Mode field in program OESC, Shipping Confirmation.

Valid values are N or O. When set to N, the pop-list will default to Normal. When set to O, the pop-list will default to Operational.

OESC_LINE_SORT: This parameter determines the default setting for the Line Sort field in program OESC, Shipping Confirmation.

Valid values are:
L - Line
I - Item Number
D - Description
B - Back Orders
S - Ship Quantity
K - Kit is incomplete.

OESC_OPER_DISPLAY_ONLY: This parameter determines whether the user can only run program OESC, Shipping Confirmation, in the Operational Display Mode.

Valid values are Y or N. When set to Y, the user can only run program OESC, Shipping Confirmation, in the Operational Display Mode.

Shipping Director Setup

These parameters determine the functionality in program OESX, Shipping Director. You should also see the Label Printing for Receipts section for additional label printing set up parameters.

OESX_F8_MODE: This parameter determines how the F8 key will work in program OESX, Shipping Director.

Valid values are ON or OFF: When set to OFF, F8 will only execute query if the program is in 'enter-query' mode so that if F8 is pressed and the order is in normal mode nothing will happen. When set to on, F8 will execute query when in either normal mode or enter query mode.

OESX_GOODS_DESCR: This parameter defines the 'goods_descr' field in the clipper table. Generally, the goods_descr field is used for customs and/or because delivery companies like to know what in the shipment. The default value is null.

Valid values are any string of characters that you wish to default to the field.

OESX_DEST_CONTROL_STMT: This parameter defines the 'dest_control_stmt' field in the clipper table. Generally, the dest_control_stmt field might contain a user-defined control statement for customs. The default value is null.

Valid values are any string of characters that you wish to default to the field.

FOREIGN_PACKLIST_COPIES: parameter to set the number of foreign packing slips to print. Default is 4 if NULL.

OESX_DISABLE_NAFTA: This parameter defines whether the NAFTA Documents checkbox is forced on or off when querying orders where shipping or billing to Mexico or Canada,

*Valid values are Y or N. When set to Y, the checkbox will not be forced on..

SHIPPING_INV_DOC: parameter to control the invoice print checkbox in OESX and OESC. Default is N for not checked. If set to N, then the system does not check oehead and does not print an invoice. If set to Y, then system checks OESX murms for which invoice drill down to run.

OESX_DTL_INVOICE: parameter setting for drill down to use in OESX amd OESC for printing a detailed invoice. If oehead is set to use a detail invoice then the system will look at this murm for which drill down to use for printing. Default is ARIPS.

OESX_INVOICE: parameter setting for drill down to use in OESX and OESC for printing an invoice. If oehead is set to print an invoice but no detail invoice is selected, the system will look at this murm for which drill down to use for printing. Default is ARIPS.

Single Bill of Lading Shipping

SINGLE_BOL_SHIPPING: When shipping staged and containerized items with program OESC, Shipping Confirmation, this parameter determines whether the containers selected must be associated with a single bill of lading in program OSLM, Bill of Lading Maintenance.

Valid values are TRUE or FALSE. When the parameter is set to TRUE, the containers must be associated with a single bill of lading.

Unship Defaults

UNSHIP_PICK_PRINT: This parameter determines whether the pick print flag for the sales order will be reset to on when the sales order is unshipped in program OESC, Shipping Confirmation, or program OESX, Shipping Director.

Valid values are Y or N. When set to Y or null, the pick print flag for the sales order will be reset to on when the sales order is unshipped. Otherwise, the pick print flag for the sales order will not be reset when the sales order is unshipped.

UNSHIP_ORDER_STATUS: This parameter determines the sales order status for sales orders that are unshipped in program OESC, Shipping Confirmation or program OESX, Shipping Director.

Valid values are O or I. When set to O, the sales order status will be changed to O - Complete when the sales order is unshipped. When set to I, the sales order status will be changed to I - Incomplete when the sales order is unshipped. If the value is not I or O, the status in the Initial Order Status pop-list in program ARLM, Location Maintenance, for the sales location will be used.

System Parameters

Autocommit Message Level

AUTOCOMMIT_MESSAGE_LEVEL: This parameter determines the commit level for the nds_autocommit functionality.

Valid value is numeric. The default 20. This is the commit level for the nds_autocommit functionality.

Automatic Report Shutdown

AUTO_REPORT_SHUTDOWN: This parameter determines whether report engine will shut down after a report has been printed, instead of remaining open as is the default behavior.

Valid values are Y or N. When the parameter is set to N, the report engine will be shut down after completing each report.

Automatic Window Resize

AUTO_RESIZE_MDI_WINDOW: This parameter determines whether when entering a new form, the system will resize the outer window large enough to accommodate the new form if it is not large enough already.

Valid values are Y or N. When set to Y, when entering a new form, the system will resize the outer window large enough to accommodate the new form if it is not large enough already. When set to N, the window will not be resized automatically.

Capacity Planning Suppression

Added to NDS Systems, version 7.5.2

SKIP_LOAD_WC: This parameter determines whether the WIP data load will be bypassed when calculating capacity planning for work orders and production schedules.

Valid values are Y or N. When set to Y, regardless of the capacity settings in program SPMM, System Parameters/Default Maintenance, bypass the WIP data load when calculating capacity planning. When set to N, the settings in program SPMM, System Parameters/Default Maintenance, will be used.

CLOSE_BROWSER_ON_EXIT: This parameter if for use only when using database 10g or higher. It allows for the 2nd web window to automatically close upon exit from NDS menu. The new murm must be set to Y and the provided file called closebrowser.htm must be placed into the following directory ORACLE_HOME\forms\webutil directory on the application server. The directory can be added if it does not exist. The murm default is N.

Valid value is any printer from program MUPM, Printer Definition Maintenance.

UTL_HTTP_TIMEOUT: This parameter is used when the http requests need to be longer than the standard Oracle default value of 60 seconds.

Discoverer Reports for Client/Server

If you are running Discoverer Reports from the NDS Menu in Client/Server mode, entries need to be made in this program so that NDS can find Discoverer and the Discoverer Reports.

DISC_ROOT: This parameter contains the path to the discoverer reports that will be run.

Valid value is the network path to the discoverer reports. For example: n:\EIS Reports

DISC_PROG: This parameter contains the path to the discoverer program executable.

*Valid value is the network path to the executable. For most clients, this will be c:\orawin95\discvr31\dis31usr.exe

DISC_WEB: This is the parameter for running oracle discoverer for web-powered NDS.

DO NOT CHANGE THIS - should be http://www.ndsasp.com/discoservlet/

Email Determination for Sales Order Acknowledgement Automatic Transmission

BACKGROUND_TRANSMIT: This parameter determines which email address will be used as the From email address when automatically transmitting sales order acknowledgements from sales order entry. This parameter should be set up as application user ID specific.

Valid values are Y or N. When set to Y, the employee number from the sales order entry program is used to determine the From email. When set to anything else or if the parameter does not exist, the logged in employee is used to determine the From email.

Limiting Query Results

LIMIT_QUERY_ROWS: When you are executing a query in some programs in NDS Applications, the program will warn you if the query results will exceed a specific number and allow you to select whether or not to continue with the query. This parameter determines whether that warning will be displayed and sets the number of rows that the query must reach or exceed before displaying the warning.

Valid value is the number of rows that the query must reach or exceed before displaying the warning. You can enter 0 or leave the value blank to skip the query count altogether.

Locking the NDS Log In Locations for Users

NDS_LOCK_LOGIN: This parameter determines whether or not the financial enterprise, manufacturing enterprise, and plant code can be changed on the menu for a specific Oracle User ID or Application ID. This is useful for users for batch jobs or other processes that require the location to remain static.

Valid values are Y or N. When set to Y, the user can change the logged in location on the menu, provided the [Lock] $image\ebx_-2124183198.gif$ button is green. When set to N, the user can never change the logged in location on the menu, regardless of the color of the button.

NDS Application MIDI Window Parameters

These parameters determine the size and location of the NDS Application MIDI windows on your screen. These parameters are set up and maintained by application user ID and are updated when you exit NDS Applications. The MIDI window is the outermost window frame in the NDS application.

MW_XPOSN: This parameter determines the placement of MIDI window in relation to the X-axis (horizontal) on the screen.

Valid values are numeric. Default is 0.

MW_XSIZE: This parameter determines the width of the MIDI window.

Valid values are numeric. The default is 800.

MW_YPOSN: This parameter determines the placement of MIDI window on the screen.

Valid values are numeric. Default is 0.

MW_YSIZE: This parameter determines the height of the MIDI window.

Valid values are numeric. The default is 525.

NDS Custom Help Parameters

WEBCUSTURL: This parameter determines the custom location for the help files for programs flagged as using custom help in program MUJM, Menu and Job Parameter Maintenance.

Valid value is the website or shared directory containing the custom help files in html format, with a training slash or backslash, as appropriate. For example: http://www.ndsapps.com/customhelp/

NDS Help Parameters

WEBBROWSER: This is the path on the user's machine to the preferred web browser on which the NDS Help will be run when operating NDS in client/server mode.

Generally, this C:\Program Files\Netscape\Communicator\Program\netscape.exe or C:\Program Files\Internet Explorer\IEXPLORE.EXE

WEBHELP: This parameter controls whether NDS Help will be run from the web or from the NDS Home Directory when operating NDS in client/server mode.

Valid values are TRUE or FALSE. When set to TRUE, the help will from the web site on the browser that is defined in the WEBURL key. When set to FALSE, the help will run from the NDS Home Directory in Windows help format.

WEBURL: This is the web address for the NDS Help.

WEBURL: DO NOT CHANGE THIS. It should be http://www.ndsapps.com/webhelp/

NF File Directory

NF_FILE_DIR: This parameter determines the Oracle named directory where the nf files exist on the application server when program MUIW, Windows Menu File Uploads, and program MUEW, Windows Menu File Exports, are run.

Valid value is the network location where the nf* files live on the application server, typically this would be C:\nds\nf_files.
Oracle named directories provide an alias for the path on the server to the directory so that users don't have to know the actual path to the files. You can have as many Oracle directories as you need. They simply need to be created by the database administrator and have access granted to the users.

PDF Print Parameters

Valid value is the command for printing pdf files.

PDF_PRINT_COMMAND: This parameter determines the command for printing .pdf files in client/server mode.

Valid value is the command for printing pdf files in client/server mode. For example: "C:\Program Files\Adobe\Acrobat 5.0\Reader\AcroRd32.exe" /p /h

PDF_PRINT_WEB: This parameter determines the URL to reach the MSDS files on the server.

Valid value is the appropriate URL. For example http://www.nds-i.com/pdf/

Report Server Parameters

REP_WEB: This is the parameter for running the report server for web-powered NDS.

DO NOT CHANGE THIS - The REP_WEB key should be set up as the URL to your report server, such as: http://nds-i.com/dev60cgi/rwcgi60?server=rep60_ndsi0

REP_TEMP: This is the reports temporary directory output for fax and email reports.

Valid value is the network path to desired directory on the server.

REPORT_SERVER: This is the name of the report server for creating faxes from web-powered NDS.

Valid value could be rep60_ndsi0, for example.

REPORT_ENVID: Allows a value to be added to the report URL as an environment variable defining the report path to use. Contact NDS Professional Services for assistance.

Sarbanes-Oxley (SOX) Password Compliance Setup

SOX_PASSWORD_COMPLIANCE: This parameter determines whether passwords set up for users in program MUSC, User Security Maintenance, must comply with the Sarbanes-Oxley (SOX) requirements.

Valid values are Y or N. Set to Y to use the SOX compliance features. When set to anything other than Yes, SOX compliance will not be enforced.

SOX_PASSWORD_COUNTDOWN: This parameter determines number of days before the password expiration date for which the user receives a warning that the password will expire.

Valid value is the desired number of days. This number should be less than the 'Password is valid for X days' value in program MUSC, User Security Maintenance.

User Menu Administrator

UTUB_ADMINISTRATOR: This parameter determines whether the application user is set up to be an application user menu administrator that can modify, create, and delete menus for all application users in program UTUB, User Menu Maintenance. This parameter should be set up by application user ID or Oracle User ID. If a value is set up for the COMMON user, that value will be used as the default for new users or users for which there is no parameter set up.

Valid values are Y or N. Users with this parameter set to Y can modify, create, and delete menus for all application users in program UTUB, User Menu Maintenance.

NDSM_USER_MENU_ONLY: This parameter determines whether a user can have STD and RCL menus. Set to 'Y' and the STD and RCL will be excluded from the menu choices. Set to 'N' and all menus can be seen by user.

Utl File Directory

UTL_FILE_DIR: This is the Oracle named directory that the Oracle utl file calls can read and write to for the system. It is used by applications reading and writing files using procedure calls as opposed to reading and writing from within a form.

Oracle named directories provide an alias for the path on the server to the directory so that users don't have to know the actual path to the files. You can have as many Oracle directories as you need. They simply need to be created by the database administrator and have access granted to the users.

Oracle named directories replace the use of the utl_file_dir parameter in the init.ora file.

At minimum, installations should have an Oracle directory named UTL_FILE_DIR as some applications expect to find this. The load_utl_file_dir.sql script sets the directory name to 'UTL_FILE_DIR' for any mappings in this program that have the File Located On pop-list set to Database Server. This script must be run by the database administrator as SYSTEM to create the 'UTL_FILE_DIR' directory. If any additional directories are required, the database administrator can create them using the create_oracle_dir.sql script.

Valid value is the network path to the directory that the oracle utl file calls can read and write to for the system.

Virtual Private Database Setup

FF_VPD: This parameter determines whether a user is using a virtual private database.

Valid values are Y or N. When set to Y, the user is using a virtual private database.

Web Mail Server Interface Usage

USE_WEB_MAIL: This parameter forces report transmission via email through the database server's SMTP when running in client-server mode, allowing the email to overcome message length limitations or other restrictions posed by the client based mail tools and interface.

Valid values are Y or N. When set to Y, the transmissions will be sent through the database server's SMTP rather than using the client based mail tools. When set to any other value, the client based mail tools will be used.

Return to See Also List

Toolbar Parameters

Toolbar parameters include toolbar settings, window positioning and size settings, and drill down gage positioning and size settings. The following should be noted, however:

It is easier and recommended that you maintain toolbar settings in program UTCB, Toolbar Configuration.
Changes to the menu window settings are recorded from the position and size of the window when you exit the menu.
Changes to the drill down gage are recorded from the positions and size when you exit the program to which you drilled down.

Toolbar parameters can be queried for the COMMON user on the Standard Murms Tab and for specific application user IDs and Oracle user IDs on the User Murms Tab. The Exclude TOOLBAR Murms flag must be set to off for these parameters to be queried.

Vendor Parameters

Unless otherwise indicated, these parameters have the category VENDOR.

Vendor Hidden Fields

New features added, version 7.5.4, 8.4

VEMM_HIDDEN_FIELDS: This parameter determines whether the fields containing sensitive information are displayed in program VEMM, Vendor Master Maintenance, for the user. These fields include:

Bank Routing No
Vendor (Bank)
Acct No
Vendor Acct Ref

Valid values are Y or N. When set to Y, the user will be able to see the values in the fields. When set to N, the data will be concealed as asterisks ****.

VEMM_ INTERNAL_CONTROL_MODE determines what fields are updateable in program VEMM, Vendor Master Maintenance.. If MURM is set to Y, then the only updates allowed are to the return address, contacts and mail/fax screens. Default is N, which allows updates and inserts to all fields.

Vendor Upload Parameter Setup

New features added, version 7.5.2

Some setup is required in this program for program VUTM, Vendor Upload.

VUTM_START_IN_DIR: This parameter determines the directory in which the browse for vendor upload files will start when the [] button is pressed in program VUTM, Vendor Upload, when the File field is blank and the File Location pop-list is set to Client Server. This parameter is used when the program is being run in client/server mode.

Valid value is the network path to the directory. For example, c:\temp\

VUTM_ONE_MFG_PER_ITEM: This parameter determines whether when items are maintained with program VUTM, Vendor Upload, a relationship of one manufacturer per item is maintained for the manufacturer part record in program ICMX, Manufacturer Item / NDS Item Cross Reference.

Valid values are Y or N. When set to Y, then when items are maintained with program VUTM, Vendor Upload, a relationship of one manufacturer per item is maintained for the manufacturer part record in program ICMX, Manufacturer Item / NDS Item Cross Reference. If a new manufacturer ID is on the item record, it will replace any existing manufacturer part record for any other vendor for that item in program ICMX, Manufacturer Item / NDS Item Cross Reference. When set to N, new manufacturer/item records are inserted for the new manufacturer.

VUTM_MAX_ITEM_LENGTH: This parameter determines whether the incoming item number is too long. If the item number length exceeds the length here, the upload process calls the custom procuser.cfunc8 procedure to determine how to handle the item. If it is still too long after the procuser call, then the item will not be processed.

Valid value is a numeric value indicating the maximum number of characters allowed for item numbers being imported.

VUTM_UTL_DIR: When uploading files over a web connection, since there is no browse button, this parameter determines the directory on the server from which the file will be uploaded. The File Location pop-list must be set to Database. .

Valid value is the network path to the directory. For example, c:\temp\

Work Order & Production Schedule Parameters

Closing Work Orders

MRFE_CLOSE: This parameter determines whether the user will be asked to close work orders in program MRFE, Finished Goods Receipts Entry, regardless of whether or not the quantity received equals the quantity ordered.

Valid values are Y or N. When set to Y, the user will be asked to close the work order whenever a receipt is made against the work order in program MRFE, Finished Goods Receipts Entry, regardless of the quantity received. When set to N, the user will only be asked to close the work order when the total quantity received for the work order is equal to or greater than the quantity ordered.

Comment Types for Work Order Report Printing

OEWO_COMMENT_COPY: This parameter determines the comment types that will be copied from the sales order to the work order when a work order is created from a sales order line. This parameter has the category ORDER ENTRY.

Valid values are any user-defined or standard comment type.

Determining Comment Type

WOBC_PRINT_COMMENT_TYPE: This parameter determines the comment types that will print on work order bitmap reports.

Valid values are any user defined or standard comment type that you wish to on the shop paper when program WOBC, Print Shop Paper, is run. This comment type is in addition to the WO comment type that prints on the report by default.
For custom version of these reports, this functionality must be added. Contact NDS Professional Services for more information.

Hide Calculation Window in BMMM

BMMM_HIDE_QTY_CALC: This parameter determines whether to hide the popup window converting feet / inches decimal to qty per. Default is set to 'Y'.

Calculation of Header Total Field - BMMM

BMMM_QTY_PER: This parameter determines how the header total field is calculated.

Set to 'Y' to calculate the header total field that is a sum of 'qty per' where the qty_ind is not "fixed".

Downstream Operation Visibility

WO_OPER_VISIBILITY: This parameter determines the default setting of the Downstream Operation Visibility pop-list in program WOEM, Work Order Entry/Maintenance. The setting of this pop-list is used in custom dispatching to determine whether the operations for this work order are visible to the work center for the next operation. The setting of this pop-list is also used in program ULEM, Universal Labor Entry, to determine whether the work order operation can be reported against on the Work Orders Tab.

Valid values are O, U, or A.

When set to O, the pop-list will default to Operation Completed. When the pop-list is set to Operation Completed, the operation must be complete to be visible to the next work center. For labor reporting with program ULEM, Universal Labor Entry, the previous operation must be marked complete for the operation to have labor reported.

When set to U, the pop-list will default to Units Good. When the pop-list is set to Units Good, operations with units good reported are visible to the work center for the next operation. For labor reporting with program ULEM, Universal Labor Entry, the previous operation must have units good reported against it and the current operation's units good + units scrapped cannot exceed the previous operation's units good for the operation to have labor reported.

When set to A, the pop-list will default to All Operations. When this pop-list is set to All Operations, then any operation can have labor reported in program ULEM, Universal Labor Entry.

Pre-Issue Work Order Manual Issue Components

WO_REL_FFLUSH_ALL: This parameter determines whether the operations with manual issue non-controlled components will be pre-issued to work orders when the work order is released. This parameter overrides the standard options for manual component material issues.

Valid values are Y or N. When set to Y, all operations with manual issue components and null operations on the bill of material will be pre-issued to work order.

Quick Labor Entry Settings

LRQE_DEFAULT_EMPNO: This parameter determines whether the employee number in program LRQE, Quick Labor Entry, will default to the logged in employee. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.

Valid values are Y or N. When set to Y, the employee number from program MUSC, User Security Maintenance, for the logged in user will be entered in the Employee No field.

LRQE_DEFAULT_EMPNO_PP: This parameter determines whether the employee number in program LRQE, Quick Labor Entry, will default to the logged in employee for this plant. Replace the PP with the appropriate plant code.

Valid values are Y or N. When set to Y, the employee number from program MUSC, User Security Maintenance, for the logged in user will be entered in the Employee No field.

LRQE_HIDE_FIELDS: This parameter determines whether the Actual Hours, Good, and Scrap fields are displayed in program LRQE, Quick Labor Entry. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.

Valid values are any combination of ACT_HOUR, UNITS_GOOD, and UNITS_SCRAPPED, separated by commas. When ACT_HOUR is entered, the Actual Hours field will not be displayed in program LRQE, Quick Labor Entry. When UNITS_GOOD is entered, the Good field will not be displayed. When UNITS_SCRAPPED is entered, the Scrap field will not be displayed.

For example, if you entered ACT_HOUR, UNITS_GOOD in the value field, then the Scrap field will be displayed in program LRQE, Quick Labor Entry, but the Actual Hours and Good fields will not.

LRQE_HIDE_FIELDS_PP: This parameter determines whether the Actual Hours, Good, and Scrap fields are displayed in program LRQE, Quick Labor Entry, in this plant. Replace the PP with the appropriate plant code.

Valid values are any combination of ACT_HOUR, UNITS_GOOD, and UNITS_SCRAPPED, separated by commas. When ACT_HOUR is entered, the Actual Hours field will not be displayed in program LRQE, Quick Labor Entry. When UNITS_GOOD is entered, the Good field will not be displayed. When UNITS_SCRAPPED is entered, the Scrap field will not be displayed.

For example, if you entered ACT_HOUR, UNITS_GOOD in the value field, then the Scrap field will be displayed in program LRQE, Quick Labor Entry, but the Actual Hours and Good fields will not.

RTG_AUTO_BEHAVIOR: This parameter determines whether only one labor entry will be allowed in program LRQE, Quick Labor Entry, for automatic routing operations or whether multiple entries can be made updating the automatic operations with each transaction.

Valid values are F or A. When set to F, only one labor reporting transaction is allowed for automatic routing operations on work orders. When set to A, automatic operations will be updated with each labor reporting transaction, provided that no later pay point or finished goods receipt transaction (with program MRFE, Finished Goods Receipts Entry) reports a greater good + scrap quantity for the work order.

Routing Operations and Engineering Specifications

RT_TEMPLATE_VALS_FROM_MASTER: This parameter determines whether engineering specifications assigned to the operations and tools assigned to routings are routing-specific or global. The parameter only affect engineering specification templates assigned to routings in program RTMM, Routing Master Maintenance.

Valid values are Y or N. When set to Y, engineering specification templates assigned to routings are global. When a change is made to an engineering specification template on a routing, the change is actually made to the master template definition in program ESTM, Engineering Template Maintenance, thus all routings that are assigned that template are also changed to match. This includes templates assigned to the operations and tools assigned to the routing.

When set to N, engineering specification templates assigned to routings are routing specific. When a template is assigned to the routing, the variables and values are copied from the master template to the routing itself. Changes that are made to the routing's template do not affect the master template from which the variables and values were copied. Later changes to the master template are not copied to the routings that were previously assigned that template. This includes templates assigned to the operations and tools assigned to the routing.

Tool Availability Warning

WOEM_TOOL_WARN: This parameter determines whether a warning will be displayed when a work order is opened in program WOEM, Work Order Entry/Maintenance, and any tool on the work order's routing does not have the status 'In Plant' in program TLMM, Tool Master Maintenance.

Valid values are Y or N. When set to Y, the warning will be displayed in program WOEM, Work Order Entry/Maintenance. When set to N, the warning will not be displayed.

ULEM, Universal Labor Entry, Parameters

ULEM_SHOW_ENTRIES: This parameter determines the default values of the Show Current Day Entries flag in program ULEM, Universal Labor Entry. When this flag is set to on, the displayed time entries with errors are limited to those for the current day. Otherwise all time entries with errors will be displayed.

Valid values are Y or N. When set to Y, the flag is set to on automatically. When set to N, the flag is set to off automatically.
ULEM_WO_CLOSE: This parameter determines whether the work order will be closed automatically when the last operation is entered in program ULEM, Universal Labor Entry. The work order will be closed if the following conditions are met:

The ULEM_WO_MRFE parameter is set to Y in this program.
This parameter is set to S or C.
The quantity complete + the quantity scrapped >+ quantity ordered.
The labor is being reported against the final operation.

Valid values are: S, C, A, or N.

S (Silent) - Close the work order silently when the labor is stopped.

C (Conditional) - Close the work order silently when the labor is stopped, if possible. If the work order cannot be closed silently, ask the user if they want to close the work order short.

A (Ask) - Do not auto-close the work order. Always ask the user if they want to close the work order.

N (No)- Do not auto-close the work order, and do not ask the user.

ULEM_WO_MRFE: This parameter determines whether when the operation is the final operation and the item is non-controlled, the finished receipt transaction is done automatically when the last operation is entered in program ULEM, Universal Labor Entry.
Valid values are Y or N. When set to Y, the finished receipt transaction is done automatically. When set to N, the finished receipt must be completed with program MRFE, Finished Goods Receipts Entry.
ULEM_ITEM_COMMENTS This parameter determines whether the user is allowed to enter item comments in ULEM. If this parameter is set to , comments can be entered or modified here. If set to , comments can only be read.
ULEM_ITEM_COMMENT_TYPE determines the default comment type if the user is entering comments while recording labor. If left NULL, a valid comment type must be entered when entering comments.
ULEM_ITEM_TARGET_TYPE determines whether the comment target type will default to the operation sequence being reported against If set to OPER_SEQ, the operation sequence will default in. If left NULL, the target type can be left blank or manually entered.
ULEM_ITEM_COMMENTS_AUTO_QUERY determines whether the comments will automatically display. If set Y and comments exist that match on item number, comment type and operation sequence, the comments will automatically display.

Work Order Scrap Reason Default

WOIF_SCRAP_REASON can be set to default the scrap reason code in program WOIF.

Work Order Due Date Rescheduling

WOVS_SYNC_DUE_DT: This parameter determines whether work order due dates will be rescheduled automatically when the work order operations are rescheduled in program WOVS, Operation Rescheduling.

Valid values are Y or N. When set to Y, the Update Order Due Date to Maximum WC Leave Date flag in the program will be set to on automatically. When this flag is set to on and a work order operation is rescheduled, the work order due date will be updated to the last scheduled finish date for the work order operations and the start date will be updated to the scheduled start date for the first operation.

When set to N, Update Order Due Date to Maximum WC Leave Date flag in the program will be set to off automatically.

Work Order Quantity Scrapping

WO_QTY_ADJUST_xx (where xx is the plant number) is supposed to adjust the quantity ordered on the work order DOWNWARD by the quantity scrapped in all operations except the first.. Default 'N'. If set to 'Y' then automatically adjust the qty ordered in sched_receipts downward by any units scrapped in a downstream operation. Any units scrapped in the first operation will not affect the order qty. This has been modified so that the work order quantity ordered is only adjusted if the quantity ordered exceeds the units good being reported for that operation and then it will be adjusted to the greater of the quantity ordered less the quantity scrapped OR the units good for that labor operation

Work Order Inventory Picking Parameters

In program MRPE, Work Order Pick List Entry, work orders can have the parent quantity ordered adjusted to equal the total amount that can be created according to the component reservations for the work order.

The quantity available for non-controlled component items can be checked to prevent the item's locations from containing negative quantities when performing automatic picking in program MRPE, Work Order Pick List Entry.

The Auto Pick flag in program MRPE, Work Order Pick List Entry, can be defaulted to on when the [Start Pick] button is pressed, and a warning can be displayed if not all items have been picked when the [Process Pick] button is pressed.

For more information on these features, see program MRPE, Work Order Pick List Entry

See Work Order Optional Control Item Issue or Receipt without Control Numbers for additional parameters that affect program MRPE, Work Order Pick List Entry.

MRPE_ALLOW_NEG_INV: This parameter determines whether the Allow Neg flag will be set to on or off by default when program MRPE, Work Order Pick List Entry, is run. Users can modify the setting of the flag in the program.

Valid values are Y or N. When set to Y, the Allow Neg flag will be set to on by default when program MRPE, Work Order Pick List Entry, is run. When set to YN the Allow Neg flag will be set to off by default when program MRPE, Work Order Pick List Entry, is run.

MRPE_ADJUST_WO: This parameter determines whether the Adj WO flag is available in program MRPE, Work Order Pick List Entry.

Valid values are Y or N. When set to Y, the Adj WO flag is available and can be used for the Work Order Quantity Adjustment for Reservations feature. When set to N, the Adj WO flag is not available.

MRPE_AUTO_PICK_WARN: This parameter determines whether when the Process Pick button is pressed, the user will be warned if any required components have not been picked, and allowed to cancel the process to correct it.

Valid values are Y or N. When set to Y, the warning is displayed.

MRPE_DEF_AUTO_PICK: This parameter determines whether when the [Start Pick] button is pressed in program MRPE, Work Order Pick List Entry, the Auto Pick flag will be set to on for all components.

Valid values are Y or N. When set to Y, the flag is set to on.

Work Order Labor Parameters

WO_QTY_ADJUST: This parameter determines whether when labor is being reported for operation sequences other than the first operation sequence, the work order quantity ordered will be decremented when the labor detail record is created and quantity was scrapped. Units scrapped in the first operation will not affect order quantity.

Valid values are Y or N. When set to Y, the work order quantity ordered will be decremented by the quantity scrapped reported for operation sequences other than the first. When set to N, the work order quantity ordered will be not be affected.

Work Order Optional Control Item Issue or Receipt without Control Numbers

WO_CONTROL_OPTIONAL: This parameter determines whether control number entry is required when receiving to or adjusting a controlled item in a non-controlled location with program MRFE, Finished Goods Receipts Entry, and if control number entry is required when issuing an optional controlled item from a non-controlled location in program MRPE, Work Order Pick List Entry.

Valid values are Y or N. When set to N, a control number must be entered for the item when it is received or issued.

When set to Y, you can receive work orders for optionally controlled items without entering a control number when the following conditions are true for the item:

Item is flagged as optional controlled in ICEM.
The receiving location is not controlled.
No control number has been entered into program MRFE, Finished Goods Receipts Entry.
No control numbers have been assigned to the item in program WOAC, Work Order Assign Control Number.

When set to Y, you can issue optionally controlled items without entering a control number in program MRPE, Work Order Pick List Entry, if the item is being picked from a non-controlled location.

WOAC_AUTO_RESERVE_OE_ITEM: This parameter determines that when a controlled item on a sales order is linked to a work order, when reserving the controlled item assigned to the work order, it should also reserve it on the sales order.

Valid values are Y or N. Default is Y. When set to N, the control number reservation on the sales order will not be made.

Work Order Receiving Locations

These parameters determine the default receiving locations for purchase orders received to work orders, and the default receiving location for work orders automatically received and closed from the purchase order receiving programs. If not entered or if the location entered does not exist, for purchase orders the default receiving locations from program ILPM, Plant Code Maintenance, is used. For work orders, the default item location from program ICEM, Item Plant Maintenance, is used.

WO_RECV_AREA: This parameter contains the default receiving stock area.

Valid value is any existing stock area from program ILMM, Location Master Maintenance.

WO_RECV_BIN: This parameter contains the default receiving bin location.

Valid value is any existing bin location from program ILMM, Location Master Maintenance, that is linked to the area entered for the WO_RECV_AREA parameter.

Workflow Parameters

Workflow Bypass by Sales Location or Plant

Workflows can be bypassed by sales location or plant code. Workflow bypass should generally be set up for the COMMON user. For more information, see the Bypassing Workflow Creation section.

The parameter is the template ID followed by the sales location or plant for which you do not wish the workflow to be created. The format should be template_location or template_plant.

Valid values are Y or N.

Example: If sales location ABC did not want a workflow sent when sales orders are cancelled (NDSORDCAN), but all other sales locations do want the workflow to be generated, you would enter the following:

App User Key Value

COMMON NDSORDCAN_ABC N

Example: If plant 10 did not want a workflow sent when an adjustment was made to inventory (NDSPERPLOG), but all other plants do want the workflow to be generated, you would enter the following:

App User Key Value

COMMON NDSPERPLOG_10 N

Workflow Variable Setup

MAIL_GATEWAY: This parameter contains the address of the NDS mail servlet. The NDS mail servlet lives on the middle tier, i.e. the same computer as the Forms and Reports servers.

Valid value is the internet address of the NDS mail servlet. For example, http://host.domain.tld/ndsmail/send where host.domain.tld is the internet address of the server running the ndsmail application.

WFLOW_MAIL_DOMAIN: This parameter contains this is the SMTP mail system domain used by the workflow mailer.

Valid value is the appropriate SMTP mail system domain.

WFLOW_MAIL_SERVER: This parameter contains the SMTP mail system server used by the workflow mailer.

Valid value is the appropriate SMTP mail system server.

WFLOW_EMAIL_RECIPIENT: This parameter determines whether the default setting of the Email Recipient flag is on or off for manually created workflows.

Valid values are Y or N. When set to Y, the default setting of the Email Recipient flag is on for manually created workflows. When set to N, the default setting of the Email Recipient flag is off for manually created workflows.

WFLOW_FROM_EMAIL: This parameter allows a company to create a standard from email address for all employee workflows instead of using the individual employee email. Default is NULL and employee email will be used.