System administration components: defining installation rules

You can set up rules that need to be defined when the Hub installs the application.

About this task

To set up installation rules:

Procedure

  1. From the tree in the application rules side panel, choose System Administration > Installation Rules.
  2. The Installation Rules window displays in the work area. Enter information in the applicable fields. Refer to Table 7–16 for field value descriptions.
  3. Choose the Save icon.
    Note: The encryption rules for credit cards and stored value cards are deprecated; encryption rules for debit cards are not supported.
    Table 1. Installation rules window.

    Installation rules
    Field Description
    Installation
    Bar Codes Generated on Server If checked, the system automatically generates bar codes for all items in the Hub environment.
    Encrypt Primary Payment Attributes for the following Payment Type Groups
    Note: IBM® recommends that payment information entering the system is already tokenized instead of being encrypted by the following rules. For this reason, the stored value card field and credit card-related fields in this box are deprecated, and encryption rules for debit card numbers are not supported.
    Credit Card If checked, Sterling Order Management System encrypts the credit card number in the database.
    Note: This field is deprecated. You can implement any payment validation system, that captures and tokenizes credit card numbers and store value card numbers.
    Additionally Encrypt Credit Card Name And Credit Card Expiration Date
    Note: The Credit Card field is deprecated. IBM recommends that credit card numbers are tokenized and stored securely in an external vault system.

    If checked, only the Sterling Order Management SystemUsers with the appropriate permissions can view decrypted credit card numbers.

    Note: Credit Card must be checked first.
    Stored Value Card
    Note: This field is deprecated. IBM recommends that stored value card numbers are tokenized and stored securely in an external vault system.

    If checked, Sterling Order Management System automatically encrypts the SVC number, and payment reference 1 in the database. Only users with the appropriate permissions can view the decrypted SVC number and payment reference 1.
    Customer Account If checked, Sterling Order Management System automatically encrypts the customer account number and payment reference 1 in the database. Only users with the appropriate permissions can view the decrypted customer account number and payment reference 1.
    Other If checked, Sterling Order Management System automatically encrypts the payment reference 1 in the database. Only users with the appropriate permissions can view the decrypted payment reference 1.
    Inventory Consolidation Level
    Hub Select the Hub option if you want product item IDs to remain unique across all organizations.

    Important: When an organization is created and this option is selected, the inventory organization is set to the default Hub organization. This can be changed in the Organization Details screen for the newly created organization.
    Enterprise Select the Enterprise option to allow product item IDs to repeat across enterprises but still be distinguished within the inventory model. Also select the Enterprise option if you want to add this Enterprise organization to a colony different from the DEFAULT colony.

    Important: When creating an Enterprise organization and this option is selected, the inventory organization is defaulted to the Enterprise organization you are creating. This can be changed in the Organization Details screen for the newly created organization.

    Note: If you choose Enterprise, an organization or Enterprise code must be specified when performing an inventory adjustment in the Consoles.
    Note: To create a business customer or an organization using Sterling Call Center or Sterling Store Engagement in a sharded environment, you must select the Enterprise option.
    Capacity Consolidation Level
    Hub Select the Hub option if you want service item IDs to remain unique across all organizations.

    Important: When an organization is created and this option is selected, the inventory organization is set to the default Hub organization. This can be changed in the Organization Details screen for the newly created organization.

    Enterprise Select the Enterprise option to allow service item IDs to repeat across enterprises but still be distinguished within the inventory model. Also select the Enterprise option if you want to add this Enterprise organization to a colony different from the DEFAULT colony.

    Important: When creating an Enterprise organization and this option is selected, the inventory organization is defaulted to the Enterprise organization you are creating. This can be changed in the Organization Details screen for the newly created organization.

    Note: To create a business customer or an organization using Sterling Call Center or Sterling Store Engagement in a sharded environment, you must select the Enterprise option.
    Catalog Model
    Maintained by Hub Select the Maintained by Hub option if you want the Hub to set up the a catalog for all of the participants.

    Important: When an organization is created and this option is selected, the catalog organization is set to the default Hub organization. This can be changed in the Organization Details screen for the newly created organization.
    Maintained by Enterprise Select the Maintained by Enterprise option if you want the individual Enterprises to set up the catalog for all of the participants involved with them.

    Important: When an organization is created and this option is selected, the catalog organization is defaulted to the organization's primary Enterprise.

    Note: To create a business customer or an organization using Sterling Call Center or Sterling Store Engagement in a sharded environment, you must select the Maintained by Enterprise option.
    Maintained by Participant Select the Maintained by Participant option if you want each individual participant to maintain their own catalog.

    Important: When an organization is created and this option is selected, the catalog organization is defaulted to the organization itself. This can be changed in the Organization Details screen for the newly created organization.
    Communication
    E-mail Server Name Enter the name of the Hub's e-mail server.
    E-mail Protocol Enter the Hub's e-mail protocol.
    E-mail Server IP Address Enter the Hub's e-mail server IP address.
    E-mail Server Listener Port Enter the Hub's e-mail server listener port.
    Item Based Allocation
    Item Based Allocation Agent Execution Interval (hr) This rule is used to indicate the interval during which the Item Based Allocation agent should not reprocess the triggers that were processed earlier in the YFS_IBA_TRIGGER table.
    Backward Compatibility
    Use Deprecated Order Hold Functionality Check this if you want to use the deprecated order hold functionality instead of the enhanced order hold functionality.

    In the deprecated mode, the order hold functionality works as follows.

    Putting an order on hold freezes the order at its current status in the sales order fulfillment pipeline. You can place an order on hold for any reason. For example, you may want to perform a security check on a particular Buyer, therefore you place the order on hold until you clear the necessary information.

    The following transactions are not processed when an order is put on hold:

    • Plan Order Complete
    • Allocate & Release
    • Chained Order Create
    • Derived Order Create
    • Schedule Order
    • Release Order
    • Send Release
    Note: Held orders are not picked up for scheduling.
    Note: If a shipment is created from an order and the order is then put on hold, the order is still confirmed during shipment confirmation.
    Enable Logical Kit Functionality Check this box if you want to enable logical kit functionality. By default this box is not checked as bundles is an enhanced feature of the logical kit.
    Is Procurement of Substitutes Allowed Check this box if you want to enable the procurement of substitutes.

    An order gets scheduled and not backordered, if inventory for the substitutes can be procured.
    Create Chained Orders Synchronously Check this box to create procurement and drop ship orders synchronously when scheduling.

    If this rule is enabled, chained orders are created only if the expected ship date on the child order is within the Advanced Notification Time of the child orders shipnode.
    Allow Automatic Service Item Group Change on Work Order Check this box to allow automatic changes in the Service Item Group when the Provided Service line is added or removed from the work order or when the Service Item Group of a work order is changed from one type of service to the other. For example, from a Provided Service to a Delivery Service.

    When this box is unchecked, changes cannot be made to the Service Item Group. For example, if the box is unchecked and the Provided Service is removed from a work order that contains the Provided Service, the Delivery Service, and the Product Item, the work order itself is cancelled. Also, when the Provided Service is added to a work order that contains the Delivery Service and the Product Item, a "VAS00002: Invalid Service Item Group Code" error is thrown.

    Note: Existing users who wish to upgrade from an older version of Yantra 7x or Sterling Supply Chain Applications to the current version of Sterling Order Management System, but wish to retain the previous functionality, should not check this box.
    Use Receiving Node's Calendar When Applying Receipt Processing Time This rule specifies whether the receipt processing time for future inventory and ATP Rule Processing time uses the node's receiving calendar. If no, then system days are added. If yes, then the node's receiving calendar days are added.
    Enable Extended Item Validation Check this box to extend item validations on orders to include the following:
    • Effective date
    • Minimum and maximum quantity
    • Item status
    • Customer entitlements
    • IsSoldSeparately flag
    Note: Item validation must be enabled before you extend validations.
    Use Deprecated Pricing Functionality Check this box to enable the deprecated pricing functionality used prior to Release 9.1 of Sterling Order Management System.

    By default, the deprecated pricing functionality is in effect after upgrade to Release 9.1. If you uncheck this box after upgrade to enable the pricing functionality for Release 9.1, be sure to define your pricing configuration rules in the Applications Manager and convert your price lists.

    Use Deprecated Data Access Policy Functionality Check this box to enable deprecated data access policies used prior to Release 9.1 across the entire application.

    To enable the deprecated data access policies for specific APIs, see the yfs.properties_ysc_ext.in property.

    Note: The application must be restarted to take into effect the unchecking of this configuration. Clearing of the database cache is required to take into effect the checking of this configuration. However, it is recommended to restart the application for better performance.
    Default User's Enterprise from Customer Organization Check this box if you want the enterprise code of the user to default to the organization code of the customer when you are creating a customer with a customer contact.
    Ship Advice Number Generation
    Use Numeric Ship Advice Number Select this option to use generated numeric values as ship advice numbers.
    Maximum Length Of Ship Advice Number Indicate the maximum length of generated numeric ship advice numbers. Upon reaching the maximum value, the generation sequence is reset. The default value is 9, the maximum length allowable.
    Note: Due to this constraint, ship advice numbers are not guaranteed to be unique.
    Inventory Tag
    Summarize and Maintain Total Supply and Demand Values For Tag Controlled Item Check this checkbox to summarize and maintain total supply and demand values for tag controlled items.

    This updates the tag descriptors and total supply and demand fields of inventory tags for tag-controlled items during inventory updates.

    Note: If this checkbox is selected and the volume of inventory updates increases, there will be an impact on performance as several threads will attempt to update the demand field in the YFS_INVENTORY_TAG. Also, the Hot SKU feature will not work for tagged items if this field is selected. The primary purpose of this checkbox is to maintain backward compatibility, and for new customers it is recommended to uncheck it.
    Display User ID
    Allow the Display User ID to be used across all enterprises Check this checkbox if you want each User ID to be usable globally across all the enterprises in your deployment. Do not check this box if you want each User ID to be unique within each enterprise.