New features added, version 7.5.2, 7.5.3, 8.1
New parameters added, version 7.5.1, 7.5.2, 7.5.3, 8.1, 7.5.3 Patches, 8.1 Patches
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 
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
Accounts Receivable Parameters
Customer and Prospect Parameters
Sales Order Shipping Parameters
Work Order & Production Schedule Parameters
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] 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].
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] 
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
* 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].
Unless otherwise noted, these parameters have the ACCOUNTING category
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.
Unless otherwise noted, these parameters have the ACCTS PAYABLE category.
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
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.
Unless otherwise noted, these parameters have the ACCTS RECEIVABLE category.
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.
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.
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.
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.
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.
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.
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.
Unless otherwise noted, these parameters have the category BACK ORDERS.
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
Unless otherwise noted, these parameters have the category CREDIT CARDS.
When the CC_PROCESSOR parameter is set to VERISIGN, the program will not display the VISANET parameters. When the CC_PROCESSOR parameter is set to VISANET, the program will not display the VERISIGN parameters.
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.
New features added, version 7.5.1, 7.5.3, 8.1
VeriSignTM variable 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 VeriSignTM 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. VeriSignTM 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 Mail and VeriSign 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 determines whether credit card processing will be done through VeriSignTM or VisaNetTM.
Valid values are VERISIGN or VISANET. Enter VERISIGN.
* VERISIGN_AVS: This parameter determines whether you are using VeriSignTM 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 VeriSignTM address verification, enter Y. Otherwise, enter N.
* VERISIGN_AVS_PP: This parameter determines whether you are using VeriSignTM 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 VeriSignTM address verification, enter Y. Otherwise, enter N.
* VERISIGN_AVS_CVV_HOLD: This parameter determines what hold code the sales order will be placed on if when you are using VeriSignTM 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.
Valid values are any hold code from program CMHM, Hold Code Maintenance.
* VERISIGN_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 VeriSignTM 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.
* VERISIGN_AVS_WARNING: This parameter determines whether when you are using VeriSignTM 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.
* VERISIGN_AVS_WARNING_PP: This parameter determines whether when you are using VeriSignTM address verification, the order should be put on hold when the verification fails 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. 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.
* VERISIGN_CVV_RESPONSE_TYPE: This parameter determines whether VeriSignTM 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, VeriSignTM should return only the normal response code. When set to 1, VeriSignTM will return both the normal response code and a CVV Result Code.
VeriSignTM 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
* VERISIGN_CVV_RESPONSE_TYPE_PP: This parameter determines whether VeriSignTM 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, VeriSignTM should return only the normal response code. When set to 1, VeriSignTM will return both the normal response code and a CVV Result Code.
VeriSignTM 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
* VERISIGN_CVV_WARNING: This parameter determines whether the warning message from the credit card processor will be displayed if the VERISIGN_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.
* VERISIGN_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 VERISIGN_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.
* VERISIGN_DLL_PATH: This parameter specifies the network location of the VeriSignTM .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 VeriSignTM .dll file. For example: c:\pfpro\signio\win32\lib\
* VERISIGN_DLL_PATH_PP: This parameter specifies the network location of the VeriSignTM .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 VeriSignTM .dll file. For example: c:\pfpro\signio\win32\lib\
* VERISIGN_HOST_ADDRESS: This parameter specifies the host address for processing credit cards with VeriSignTM. 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 processing credit cards with VeriSignTM. For example: test-payflow.verisign.com or connect.signio.com. Live users of VeriSignTM should use payflow.verisign.com.
* VERISIGN_HOST_ADDRESS_PP: This parameter specifies the host address for processing credit cards with VeriSignTM for this plant or sales location. The PP should be replaced with the desired plant code or sales location code.
Valid value is the appropriate URL for processing credit cards with VeriSignTM. For example: test-payflow.verisign.com or connect.signio.com. Live users of VeriSignTM should use payflow.verisign.com.
* VERISIGN_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.
* VERISIGN_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.
* VERISIGN_PARTNER: This parameter specifies the VeriSignTM partner that signed up the client for PayFlow Pro. If the clients signed themselves up, the entry here should be VeriSign. 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 VeriSignTM partner name.
* VERISIGN_PARTNER_PP: This parameter specifies the VeriSignTM 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 VeriSign. The PP should be replaced with the desired plant code or sales location code.
Valid value is the VeriSignTM partner name.
* VERISIGN_PASSWORD: This parameter specifies your VeriSignTM 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.
Valid value is your VeriSignTM account password.
* VERISIGN_PASSWORD_PP: This parameter specifies your VeriSignTM account password for the plant or sales location. The PP should be replaced with the desired plant code or sales location code.
Valid value is your VeriSignTM account password.
* VERISIGN_PORT: This parameter specifies the port used for VeriSignTM 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 port number. Normally this is 443.
* VERISIGN_PORT_PP: This parameter specifies the port used for VeriSignTM processing for this plant or sales location. The PP should be replaced with the desired plant code or sales location code.
Valid value is the appropriate port number. Normally this is 443.
* VERISIGN_PROXY_ADDRESS: This parameter specifies the local proxy IP address for VeriSignTM processing, if it exists. 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 proxy IP address.
* VERISIGN_PROXY_ADDRESS_PP: This parameter specifies the local proxy IP address for VeriSignTM processing, if it exists, for this plant or sales location. The PP should be replaced with the desired plant code or sales location code.
Valid value is the proxy IP address.
* VERISIGN_PROXY_LOGON: This parameter specifies the local proxy logon id for VeriSignTM processing, if required. 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 local proxy login ID.
* VERISIGN_PROXY_LOGON_PP: This parameter specifies the local proxy logon id for VeriSignTM processing, if required, for this plant or sales location. The PP should be replaced with the desired plant code or sales location code.
Valid value is the local proxy login ID.
* VERISIGN_PROXY_PASSWORD: This parameter specifies the local proxy password for VeriSignTM processing, if required. 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 local proxy password.
* VERISIGN_PROXY_PASSWORD_PP: This parameter specifies the local proxy password for VeriSignTM processing, if required, for this plant or sales location. The PP should be replaced with the desired plant code or sales location code.
Valid value is the local proxy password.
* VERISIGN_PROXY_PORT: This parameter specifies the local proxy port number for VeriSignTM processing, if it exists. 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 port number.
* VERISIGN_PROXY_PORT_PP: This parameter specifies the local proxy port number for VeriSignTM processing, if it exists, for this plant or sales location. The PP should be replaced with the desired plant code or sales location code.
Valid value is the appropriate port number.
* VERISIGN_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.
* VERISIGN_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.
* VERISIGN_SERVLET_URI: This parameter specifies the URI to the NDS Credit Card Servlet for VeriSignTM 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
* VERISIGN_SERVLET_URI_PP: This parameter specifies the URI to the NDS Credit Card Servlet for VeriSignTM 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
* VERISIGN_SERVLET_URL: This parameter specifies the URL to the web server hosting the NDS Credit Card Servlet for VeriSignTM 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.
* VERISIGN_SERVLET_URL_PP: This parameter specifies the URL to the web server hosting the NDS Credit Card Servlet for VeriSignTM processing for this plant or sales location. The PP should be replaced with the desired plant code or sales location code.
Valid value is the appropriate URL. For example: www.nds-i.com.
* VERISIGN_TIMEOUT: This parameter determines the number of minutes before VeriSignTM processing will time out. 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 numeric and defaults to 30.
* VERISIGN_TIMEOUT_PP: This parameter determines the number of minutes before VeriSignTM processing will time out for this plant or sales location. The PP should be replaced with the desired plant code or sales location code.
Valid value is numeric and normally is 30.
* VERISIGN_USER: This parameter specifies the VeriSignTM account name for VeriSignTM 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 your VeriSignTM account name.
* VERISIGN_USER_PP: This parameter specifies the VeriSignTM account name for VeriSignTM processing for this plant or sales location.
Valid value is your VeriSignTM account name. The PP should be replaced with the desired plant code or sales location code.
* VERISIGN_VENDOR: This parameter specifies your VeriSignTM vendor name for VeriSignTM 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 your VeriSignTM vendor name.
* VERISIGN_VENDOR_PP: This parameter specifies your VeriSignTM vendor name for VeriSignTM processing for this plant or sales location. The PP should be replaced with the desired plant code or sales location code.
Valid value is your VeriSignTM vendor name.
New variables added, version 7.5.2
VisaNetTM 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 VisaNetTM variables for each plant code in which sales orders are entered. In the example below, the PP should be replaced with the plant code. Values for these variables should be provided by your bank. VisaNetTM will look for a parameter with the plant code first, and if one does not exist, it will use the parameter without a plant code.
* CC_PROCESSOR: This parameter determines whether credit card processing will be done through VeriSignTM or VisaNetTM.
Valid values are VERISIGN or VISANET. Enter VISANET.
* VISANET_AGENT: This parameter specifies the AGENT for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the agent provided by your bank.
* VISANET_AGENT_PP: This parameter specifies the agent for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the AGENT provided by your bank.
* VISANET_AUTH_DAYS: This parameter determines the number of days that a VisaNetTM authorization is good for before the transaction needs to be reauthorized.
Valid value is numeric. The default is '10'.
* VISANET_AVS: This parameter determines whether you are using VisaNetTM address verification. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid values are Y or N. If you are using VisaNetTM address verification, enter Y. Otherwise, enter N.
* VISANET_AVS_PP: This parameter determines whether you are using VisaNetTM address verification for this plant. The PP should be replaced with the desired plant code.
Valid values are Y or N. If you are using VisaNetTM address verification, enter Y. Otherwise, enter N.
* VISANET_AVS_CVV_HOLD: This parameter determines what hold code the sales order will be placed on if when you are using VisaNetTM 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 if no parameter exists for a specific plant.
Valid values are any hold code from program CMHM, Hold Code Maintenance.
* VISANET_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 VisaNetTM 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.
Valid values are any hold code from program CMHM, Hold Code Maintenance.
* VISANET_AVS_WARNING: This parameter determines whether when you are using VisaNetTM 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 if no parameter exists for a specific plant.
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.
* VISANET_AVS_WARNING_PP: This parameter determines whether when you are using VisaNetTM address verification, the order should be put on hold when the verification fails for this plant. The PP should be replaced with the desired plant code.
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.
* VISANET_BATCH_SEQ: This parameter determines the name of the sequence to use to obtain new batch numbers, from program SPAN, Auto Number Control. The batch number range should be 1 through 999 and then recycled. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the appropriate Record Type value from program SPAN, Auto Number Control.
* VISANET_BATCH_SEQ_PP: This parameter determines the name of the sequence to use to obtain new batch numbers for this plant, from program SPAN, Auto Number Control. The batch number range should be 1 through 999 and then recycled. The PP should be replaced with the desired plant code.
Valid value is the appropriate Record Type value from program SPAN, Auto Number Control.
* VISANET_BIN: This parameter specifies the BIN for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the BIN provided by your bank.
* VISANET_BIN_PP: This parameter specifies the BIN for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the BIN provided by your bank.
* VISANET_CHAIN_NO: This parameter specifies the chain number for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the chain number provided by your bank.
* VISANET_CHAIN_NO_PP: This parameter specifies the chain number for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the chain number provided by your bank.
* VISANET_CITY_CODE: This parameter specifies the city code for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the city code provided by your bank.
* VISANET_CITY_CODE_PP: This parameter specifies the city code for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the city code provided by your bank.
* VISANET_COUNTRY: This parameter specifies the country code for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the country provided by your bank.
* VISANET_COUNTRY_PP: This parameter specifies the country code for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the country provided by your bank.
* VISANET_CURRENCY: This parameter specifies the currency for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the currency provided by your bank.
* VISANET_CURRENCY_PP: This parameter specifies the currency for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the currency provided by your bank.
* VISANET_CVV_RESPONSE_TYPE: This parameter specifies whether VisaNetTM 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 if no parameter exists for a specific plant.
Valid values are 0 or 1. When set to 0, VisaNetTM should return only the normal response code. When set to 1, VisaNetTM will return both the normal response code and a CVV Result Code.
VisaNetTM 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
* VISANET_CVV_RESPONSE_TYPE_PP: This parameter determines whether VisaNetTM will return only the normal response code or the normal response code and a CVV Result code for this plant. The PP should be replaced with the desired plant code.
Valid values are 0 or 1. When set to 0, VisaNetTM should return only the normal response code. When set to 1, VisaNetTM will return both the normal response code and a CVV Result Code.
VisaNetTM 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
* VISANET_CVV_WARNING: This parameter determines whether the warning message from the credit card processor will be displayed if the VISANET_CVV_RESPONSE_TYPE is set to 1. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
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.
* VISANET_CVV_WARNING_PP: This parameter determines whether the warning message from the credit card processor will be displayed for this plant if the VISANET_CVV_RESPONSE_TYPE is set to 1. The PP should be replaced with the desired plant 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.
* VISANET_HOST: This parameter specifies the name of the application server running the NDS VisaNetTM Gateway.
Valid value is the name of the application server running the NDS VisaNetTM Gateway. For example: http://www.ndsapps.com/
* VISANET_HOST_PORT: This parameter specifies the http port on the web server.
Valid value is the http port number. Defaults to 80 but may be different, especially for a secure server.
* VISANET_INDUSTRY: This parameter specifies the industry for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the industry provided by your bank.
* VISANET_INDUSTRY_PP: This parameter specifies the industry for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the industry provided by your bank.
* VISANET_MERC_LOC: This parameter specifies the merchant location for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the merchant location provided by your bank.
* VISANET_MERC_LOC_PP: This parameter specifies the merchant location for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the merchant location provided by your bank.
* VISANET_MERCH_ABA: This parameter specifies the merchant ABA number for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the merchant ABA number provided by your bank.
* VISANET_MERCH_ABA_PP: This parameter specifies the merchant ABA number for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the merchant ABA number provided by your bank.
* VISANET_MERCH_CAT: This parameter specifies the merchant category code for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the category code provided by your bank.
* VISANET_MERCH_CAT_PP: This parameter specifies the merchant category code for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the category code provided by your bank.
* VISANET_MERCH_CERT: This parameter specifies the merchant certification number for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the merchant certification number provided by your bank.
* VISANET_MERCH_CERT_PP: This parameter specifies the merchant certification number for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the merchant certification number provided by your bank.
* VISANET_MERCH_CITY: This parameter specifies the merchant city for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the merchant city provided by your bank.
* VISANET_MERCH_CITY_PP: This parameter specifies the merchant city for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the merchant city provided by your bank.
* VISANET_MERCH_NAME: This parameter specifies the merchant name for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the merchant name provided by your bank.
* VISANET_MERCH_NAME_PP: This parameter specifies the merchant name for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the merchant name provided by your bank.
* VISANET_MERCH_NO: This parameter specifies the merchant number for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the merchant number provided by your bank.
* VISANET_MERCH_NO_PP: This parameter specifies the merchant number for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the merchant number provided by your bank.
* VISANET_MERCH_PHONE: This parameter specifies the merchant phone number for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the merchant phone number provided by your bank.
* VISANET_MERCH_PHONE_PP: This parameter specifies the merchant phone number for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the merchant phone number provided by your bank.
* VISANET_MERCH_STATE: This parameter specifies the merchant state for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the merchant state provided by your bank.
* VISANET_MERCH_STATE_PP: This parameter specifies the merchant state for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the merchant state provided by your bank.
* VISANET_OESJ_HOLD: This parameter specifies 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.
Valid values are any hold code from program CMHM, Hold Code Maintenance.
* VISANET_RCV_INST_ID: This parameter specifies the instrument ID for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the instrument ID provided by your bank.
* VISANET_RCV_INST_ID_PP: This parameter specifies the instrument ID for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the instrument ID provided by your bank.
* VISANET_SERVLET_URI: This parameter specifies the URI to the NDS VisaNetTM Gateway.
This should always be set to /visanet/process
* VISANET_SHARE_GRP: This parameter specifies the share group for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the share group provided by your bank.
* VISANET_SHARE_GRP_PP: This parameter specifies the share group for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the share group provided by your bank.
* VISANET_STORE_NO: This parameter specifies the store number for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the store number provided by your bank.
* VISANET_STORE_NO_PP: This parameter specifies the store number for VisaNetTM processing for this plant. The PP should be replaced with the desired plant code.
Valid value is the store number provided by your bank.
* VISANET_TERM_NO: This parameter specifies the terminal number for VisaNetTM processing. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid value is the terminal number provided by your bank.
*