Tenant (retailer information)

Purpose: Use the Tenant screen to define enterprise-wide settings for your enterprise’s use of Order Broker, including those related to:

  • the Order Broker module(s) you use
  • your logo

About tenant settings: Tenant settings are attributes of your enterprise in Order Broker at a level higher than the organization. Tenant-level settings apply to all your organizations in Order Broker.

How to display this screen: Select Tenant from the Systems Menu.

Note:

Only users with Tenant authority can display this screen. See the Role Wizard for more information. Also, the admin user does not have access to this screen.

Tenant - Admin screen: The Tenant-Admin screen displays additional settings related to cloud administration. This screen is available only to an admin user.

Fields at this screen

Update any of the fields described below and click Save, or click Cancel to exit the screen without making any changes.

Field Description
Settings
Tenant Logo

The URL for the logo to display in Store Connect. Not currently used.

Preview the logo: After entering the URL, click the preview icon (Illustrates the magnifying glass icon.) to preview the image at 254 x 33.

Note:

Oracle staff need to make sure that this URL is added to the allow list.
Time Zone

The time zone to use when setting schedules and displaying dates and times on screens, in reports, and in email notifications. This is the retailer’s time zone, which can be different from the system time zone and the user’s time zone. See Time Zones for a discussion.

Changing the time zone: If you change the time zone, you should reset the following:

  • Report schedules, through the Schedule Reports screen
  • Imports, through the Schedule Jobs screen
  • Incremental inventory import, probable quantity update and export, and fulfilled inventory export, at the System screen
Geocode Address

The URL to use when generating geocode requests to determine the latitude and longitude for:

  • a location, when the location is created or has its address updated, either through the New Location or Edit Location screens, or through the import process
  • a customer’s address, in order to calculate proximity for an order or inventory request, such as the SubmitOrder or the LocateItems request message

If you specify a URL, Order Broker uses the Oracle Maps Cloud Service to determine latitude or longitude. Otherwise, if this field is blank, Order Broker uses the proximity database.

This field is display-only at this screen, and can be set at the Tenant-Admin screen. Admin authority is required for access to the Tenant-Admin screen.

See Proximity Locator Searching for background.

Note:

Oracle staff need to make sure that this URL is added to the allow list.
Use Routing Engine

Select this option to be able to use the Routing Engine and see related screens.

Required settings:

  • If you select the Use Store Connect option but not this option, this option is selected automatically.
  • Order Broker requires that at least this option or the Use Vendor Portal option are selected. If you don’t select any of the module use options, the Use Routing Engine option is selected automatically.

See the Home Screen for information on screen access controlled by this setting.

Use Store Connect

Select this option to be able to use the Store Connect module. This option also requires the Routing Engine. If you select this option and don’t select Use Routing Engine, the Use Routing Engine option is selected automatically.

See the Home Screen for information on screen access controlled by this setting.

Use Vendor Portal

Select this option to use the Drop Ship (Supplier Direct Fulfillment) module.

See the Home Screen for information on screen access controlled by this setting.

About the Volume tables: The Volume tables display totals, broken out by month for the current year and the previous year, of SubmitOrder requests and of searches for fulfilling, sourcing, or pickup locations. Totals are for all organizations in the enterprise.

Activities that aren’t tracked: Order Broker does not include any of the following order-related activity in the Order or Merchandise Locator Volume tables:

  • status inquiries, either individually or by list
  • status updates, either through the status update request message or through the Order screen
  • fulfillment requests or intransit requests
  • order searches
  • order updates (updates to the Under Review setting or the Pickup By Date)
  • “reshopping” an order or line that is rejected

Supplier Direct Fulfillment? Activities related to the Supplier Direct Fulfillment module are not tracked in the Order or Merchandise Locator Volume tables.

Things to note:

  • All organizations: The totals listed include all organizations in the environment.
  • Counter reset: The counters reset at the start of a new month.
  • Actual date: The month incremented is based on the actual date, not the date specified in the request message. For example, a SubmitOrder request received on October 1 updates the total for October, even if the transaction date specified in the message is September 30.
  • Counter always incremented by 1: Each request increments the counter by 1, regardless of the number of items, requested quantity(s), or if multiple fulfillment types are specified for a ProductAvailabiity request.
  • Splitting order or line? The totals are incremented by just 1, regardless of whether the Allow Split Order or Allow Split Line preferences are selected and the order or line would need to be fulfilled out of multiple locations. For example, a SubmitOrder request for 2 units of item ABC123 results in 1 unit assigned to location 100 and 1 unit assigned to location 200; however, the Order Volume total is incremented by just 1.
  • Unfulfillable orders: The order counter is incremented for orders that cannot be fulfilled, and are automatically assigned to the Default Unfulfillable Location.
  • Order not created: The order count is not incremented when Order Broker returns an error to a SubmitOrder request if, for example, the specified product is not available in the specified location, or if the specified location does not support the order type.

Troubleshooting if last month in the tables is cut off: Depending on the browser you are using, the font size in your browser, the zoom level in your browser, and the Display settings for your computer, the last months in the volume tables may be cut off. Some things to try:

  • Make sure your computer’s Display setting is at 125% or less, and zoom out (-) if needed in the browser.
  • Decrease the font size in the browser.
  • If you prefer to leave the computer’s Display setting at the default, try another browser; for example, the last month may be cut off in Firefox, but displayed correctly in Chrome.
Order Volume

Displays order request totals broken out by month for the current year and the previous year. The monthly total is incremented by 1 each time the routing engine processes a SubmitOrder request.

Unfulfillable? The monthly total is incremented when an order or line on a new order is assigned to the unfulfillable location (Default Shipping Location), because there are no locations that could fulfill the order.

Unavailable? The monthly total is not incremented when the requested quantity of the item(s) is/are not available at the specified location (for example, Location does not have sufficient inventory of this item) or if the specified location does not support the order type (for example, Location (123) does not support pickup transactions).

Rejected: The monthly total is not incremented when an assigned location rejects the order or line, and Order Broker attempts to “reshop” it.

Error? The monthly total is not incremented when the routing engine returns an error, such as when the requested product is invalid, unless the error indicates that the requested quantity(s) of one or more items are not available for the order.

Merchandise Locator Volume

Displays merchandise locator requests broken out by month for the current year and the previous year. The monthly total is incremented by 1 each time the routing engine:

  • processes a LocateItems request, regardless of the number of items in the request.
  • processes a ProductAvailability request, regardless of the number of items in the request or the number of fulfillment types specified in a ProductAvailability request.

Unavailable? The monthly total is incremented regardless of whether the requested quantity(s) of the item(s) is/are available within the search criteria.

Error? The monthly total is not incremented when the Order Broker returns an error, except an error that indicates that the requested quantity(s) of the item(s) is/are not available within the search criteria.