Inventory Management

This release contains the following features and changes for Inventory Management:

Par and Net Sales for Suggested Ordering

This release adds the Par + Net Sales quantity method for calculating a suggested order for an item group.

The following table describes an example soda machine that has two Bag-in-Box (BIB) on hand, but requires a minimum of four to function and is forecasted to sell three for the day.
  • The Par quantity method suggests an order of two BIBS, but this only allows the machine to function and does not account for the forecasted sales.

  • The Net Sales quantity method suggests an order of one BIB, but this does not allow the machine to reach the minimum requirement and does not ensure the machine stays functional over the day.

  • The Par + Net Sales quantity method suggests an order of five BIBs, to allow the machine to reach the minimum requirement for functioning and to account for stock consumption based on the forecasted sales.

Table 1-1 Suggested Order Quantity Example

Machine BIB Stock-On-Hand (SOH) Minimum BIB Requirement (Par) BIB Requirement for Forecasted Sales (Net Sales) Suggested Par Quantity Suggested Net Sales Quantity Suggested Par + Net Sales Quantity

Soda Machine

2

4

3

2 (4-2)

1 (3-2)

5 (4+3-2)

Legacy Back Office Export

This release deprecates the legacy thick client Back Office interfaces used with Inventory Management. Customers that used thick client for financial export with Inventory Management can use the Legacy Back Office Export interface to:
  • Create and edit booking entries.

  • View, re-open, and re-book exported booking records.

  • Define export parameters for each interface type.

WARNING:

  • Do not use Legacy Back Office Export if you did not use the thick client Back Office export. New interfaces and interfaces for customers converting from Oracle MICROS Materials Control must be re-created and integrated into Close Financial Period.

  • The Legacy Back Office Export interface does not port jobs created when using the thick client Back Office Export function. You must recreate the job as a Legacy BO Export job in the Inventory Management Scheduler. For more information, refer to the Oracle MICROS Inventory Management Legacy Back Office Export User Guide (Doc ID 2243756.1) on https://support.oracle.com/.

Poland Fiscal Inventory Export

You can now configure and run the Fiscal Export – Poland job to create fiscal inventory data outputs for legal compliance. The Oracle MICROS Inventory Management Poland Fiscal Inventory Export User Guide contains configuration instructions and references for the exported data.

Performance Enhancements

This release includes the following performance enhancement options:

  • You can enable multi-threading for Inventory Count Cycle jobs to improve inventory creation performance if your environment either contains a large number of inventory items or uses more than 50 cost centers.

    In Inventory Management, click Settings, click the Inventory tab, and then enter the number of cost centers in the Start Count Cycle Multithreading field upon which Inventory Management begins to use multi-threading.

  • You can configure a maximum date range for generating Transfer on Sales records.

    In Inventory Management, click Configurations, click Names, and then set the SYSTRSFONSALESDAYS parameter to the maximum number of days that the Transfer on Sales job checks.

Configuration Parameters

This release adds the following configuration parameters:

  • To configure external-facing connection security for the Inventory Management web application, navigate to root\Inetpub\wwwroot\myinventory\, open web.config in a text editor, and then add or set the following keys:

    • <add key=”myMicrosURL” value=”public exposed URL for Oracle Hospitality Reporting and Analytics, such as https://www.example.net/login.jsp” />

    • <add key=”MyMicrosProtocol” value=”network communication protocol for Reporting and Analytics, such as https” />

    • <add key=”SecureCookies” value=”set as true if HTTPS is used for the exposed URL, otherwise set as false” />

    • <add key="myMicrosAllowedDomains" value="comma-separated list of acceptable domains" />: The application rejects URLs in HTTP POST requests that do not belong to the listed domains. For example, if you enter domain1.org,domain2.com, the application does not start for an HTTP POST passing a URL from domain3.net.

  • To configure custom error pages, navigate to root\Inetpub\wwwroot\myinventory\, open system.web in a text editor, and then create or find the following element:

    <customErrors mode="On" defaultRedirect="~/Common/Forms/Err.html">

    You can then add error redirects by adding the following line:

    <error statusCode="error number" redirect="error page URL">

    For example, a redirect for the 500 error could be: <error statusCode="500" redirect="~/Common/Forms/500_Err.html">