Modifying customer information

  1. On the Business Center home page, select Users > Customers.
  2. To find a customer, specify your search criteria in the search form, and then click Search. Customers that match your search criteria are displayed.
  3. To modify customer details, click the customer number and specify this information in the Details area:
    1. DUNS Number
      Specify the DUNS (Data Universal Numbering System) number of the customer.
      DUNS numbers are used to assign a unique identifier to a customer or other business entity.
      DUNS numbers are important when interfacing e-Commerce with a back-end business system. If you are using DUNS numbers, then specify the appropriate number for the customer. If you are not using them, then you can leave this field blank.
    2. Default Shipping Address
      Select the default shipping address for this customer's orders.
      Note: Customers should not set this to null.
    3. Market Setting Override
      Select Yes to enable you to override the default market that is defined through BOD replication of customer information.
      Note: Selecting Yes in this field means that succeeding replications of customer records will no longer update the current market value.
    4. Market
      Select a market from the list to manually define the default market for this customer. You can only select a market if Market Setting Override is enabled.
    5. Virtual Enterprise Setting Override
      Select Yes to enable you to override the default virtual enterprise that is defined through BOD replication of customer information.
      Note: Selecting Yes in this field means that succeeding replications of customer records will no longer update the current value for the default virtual enterprise.
    6. Default Virtual Enterprise
      Select a virtual enterprise to manually define the default virtual enterprise for this customer. You can only select a virtual enterprise if Virtual Enterprise Setting Override is enabled.
    7. Block Order Placement
      Select Yes to block all users that belong to this customer from submitting orders.

      Only users with roles that contain the feature element Block Customer Order Placement can toggle this field. When this field is enabled, users of this customer receive a notification upon login that they cannot submit orders.

      Note: Blocking of order placements for a customer is controlled in the Business Center or directly from the ERP. If the application property Ordering.Customer Order Blocking through ERP is enabled, then the ERP settings are replicated into Infor e-Commerce and reflected in the Business Center. Consequently, this field becomes disabled.
    8. PunchOut Protocol
      Select OCI to view OCI Agreement and OCI Fields, or cXML to view PunchOut Order Message Fields.
      OCI
      Infor e-commerce includes OCI (Open Catalog Interface), a functionality that allows users to create and update the OCI Agreement and OCI Fields. OCI is an interface that incorporates external product catalogs into Site Recovery Manager (SRM) Server applications.
      Note: The application property Ordering.PunchOut Order must be enabled.
      OCI Agreement

      In the OCI Agreement area, specify the Valid From and Valid To dates.When OCI PunchOut is enabled, customers can transfer their shopping carts from the web shop to the SAP (System Applications Products) Supplier Relationship Management (SRM) application. Other OCI functions, such as product search from within SRM, are not supported.

      OCI Fields
      To enhance OCI punchout functionality, customization mapping is done for the OCI fields.
      • In the OCI Fields area, click Add. Specify the Field Name.
      • Click Modify Field Value. The OCI Field Value window is displayed.
        1. In the Type box, select from Order, Item, or Fixed Value.
          Note: Field Name refers to the OCI Field Name, while Field Value refers to the name of the fields in Rhythm.
        2. Click Modify Criteria. The Criteria window is displayed. In the Criteria area, specify a value for these fields:
          • Length: The maximum length for both character and number.
          • Decimal Length: The maximum number of decimals.
          • Multiply By: The multiplier.
          • Look Up: Used to update the "code" of unit of measure that is sent to the procurement system.
        3. Click Save.
      cXML
      cXML (Commerce eXtensible Markup Language) is a third-party protocol intended for communication of business documents between procurement applications, e-commerce hubs, and suppliers.
      Note: The application property Ordering.Punch Out Order must be set to true. Sender Credential Identity or From Credential Identity and Shared Secret must also be defined based on the settings on Application Details > Punchout Order > Credential Identity.

      For customizing the email template to be used in cXML-based ordering, see Infor Rhythm Services Notification Service User Guide.

      Customers can submit item numbers with alphanumeric characters such as a space or a slash. An email notification is sent to a Rhythm or non-rhythm user for successfully submitted orders through cXML Order Request.

      Note: Ensure that these elements and properties are enabled:
      • Set the application property Ordering.PunchOut Order Enabled to true
      • Select these elements in Users > Customer > Customer details​:
        • cXML in PunchOut Protocol
        • PunchOut Order
        • Submit cXML Order
        • Send Mail On Order
      PunchOut users can add an item to the cart using the Reorder button in the Order History page.
      cXML Header Fields
      In the cXML Header Fields area, specify the values for these fields:
      • From Credential Domain: The credential ID (example: NetwordId, BUNS, AribaNetworkUserId).
      • Sender Credential Domain: The sender credential ID (example: NetwordId, BUNS, AribaNetworkUserId).
      • From Credential Identity: The originator of the PunchOutSetUpRequest. The value is usually the Customer Number. This is also needed for the validation of cXML PunchOutSetupRequest and OrderRequest.
      • Sender Credential Identity: The user name of the buying organization. The value is usually the Customer Number. This is also needed for the validation of cXML PunchOutSetupRequest and OrderRequest.
      • Shared Secret: The password needed for the validation of the cXML PunchOutSetupRequest and OrderRequest.
      • Sender User Agent: This field identifies the originating application. It consists of the software company name, product name, and version.
      • Order Request User XPath: This field determines which email to be used to send order updates (example: /cXML/Request/OrderRequest/OrderRequestHeader/ShipTo/Address/Email).
        Fallback hierarchy Behavior
        Business Center > Customer Details: Order Request User XPath If there is no Xpath, has blank values, or invalid email, then proceed to next fallback.
        Business Center > Application Details: Default OrderRequest User XPath If there is no Xpath, has blank values, or invalid email, then proceed to next fallback. The default value is: /cXML/Request/OrderRequest/OrderRequestHeader/Contact[@role="buyer"]/Email
        Business Center > Customer Details: Service User If the user has no permission for punchout or has blank values, then an error is displayed.
      • PunchOut User Xpath: The admin can use this field to specify the user Xpath. The user Xpath is used to retrieve the user email address in the PunchOut. (example: /cXML/Request/PunchOutSetupRequest/Contact/Email).
        Fallback Hierarchy Behavior
        Business Center > Customer Details: PunchOut User Xpath If there is no Xpath, has blank values, or an invalid email, then proceed to next fallback.
        Business Center > Application Details: Default PunchOut User Xpath If there is no Xpath, has blank values, or an invalid email, then proceed to next fallback.
        /cXML/Request/PunchOutSetupRequest/Contact/Email If there is no Xpath, has blank values, or an invalid email, then proceed to next fallback.
        /cXML/Request/PunchOutSetupRequest/Extrinsic[@name='UserEmail'] If there is no Xpath, has blank values, or an invalid email, then proceed to next fallback.
        Business Center > Customer Details: Service User If the user has no permission for punchout or has blank values, then an error is displayed.
      • Service User: The email address of the service user for anonymous users.
      cXML Punchout Order Message Fields
      For cXML, fields are mapped to xpaths. The way that this works is similar to how OCI is implemented.
      • In the cXML PunchOut Order Message Fields area, click Add. Specify the Field Name.
      • Click Modify Field Value. The cXML Field Value window pops up.
      • Follow steps 1 to 3 in OCI Fields.
        Note: For step 1, Field name refers to the cXML PunchOut Order Message Fields name while field value refers to the cXML field value.
    9. Mail Receiver for Quote
      Optionally, specify one or more email addresses of the account managers to receive quote email notification. Account managers can be non-Rhythm users.
  4. In the Billing Address area, verify that the information is correct.
  5. In the Shipping addresses area, click the Address name. On the Shipping Address Details page, verify that the details are correct, then click Save. If not, click Reset then specify the correct address.
  6. Click Save.