Operational hold codes

You can use operational hold codes instead of standard legacy hold codes. Operational hold codes are created from existing system-defined and user-defined legacy hold codes. They are applied to sales orders using the same criteria as legacy hold codes, but provide greater visibility and a comprehensive removal process.

Although several hold codes might apply to a sales order, you can only view one legacy hold code per order. After you remove the hold, the sales order is available for further processing. Operational hold code processing implements these additional requirements, resulting in improved sales order management:

  • Each operational hold code that applies to a sales order is displayed in the applicable sales entry and inquiry functions.
  • Each operational hold code on a sales order must be removed before further sales order processing can occur.
  • Each operational hold code can only be removed by a user that has permission in SA Operator Setup-Other Options to remove that hold code.

Operational hold codes are automatically created in SA Table Code Value Setup when you activate the feature. They are based on legacy hold codes such as credit card, amount, margin, customer return, electronic, and zero-shipped order holds. You can set up additional hold codes that are specific to your business requirements.

Because multiple operational hold codes can be associated with an order, the order approval type is limited to these values:

  • y: No holds are placed on the order.
  • n: One or more holds are placed on the order.

Each active and inactive operational hold code on an order is displayed in Sales Order Inquiry and on the Operational Hold Code Approval page in these functions:

  • Sales Order Entry
  • Sales Shipping Feedback Entry
  • Sales Credit Release Inquiry

You can remove or create individual holds on Operational Hold Code Approval page, based on your hold code security. When the last hold on the order is removed, the approval type changes to y. You cannot re-activate a hold code that was removed, but you can create a new hold using the same code.

Holds can be removed in other functions. For example, you can remove credit card authorization holds by running the Customer Credit Card Manager Report. If an order is on an electronic hold, or e-hold, you can remove operational hold codes in Electronic Transaction Control Center Entry.

Activation and required setups

To activate the feature, select the Use Operational Hold Codes option in SA Administrator Options-Documents-Sales Order-Entry Settings. Operational hold codes are then automatically created in SA Table Code Value Setup, based on these legacy hold codes:

  • Amount hold
  • Credit card authorization
  • Credit card failure
  • Credit hold
  • Customer return
  • Electronic hold, also called e-hold or API/EDI hold
  • Margin hold
  • Service Warranty
  • Zero shipped order

Hold codes for credit holds (h), e-holds (e), and Service Warranty (w) are defined by the system. The other legacy hold codes are user-defined and set up on these pages in SA Administrator Options:

  • Credit card, amount, and margin holds in Documents-Sales Orders-Approval Process.
  • Customer return and zero ship order holds in Logistics-WL Options

After the operational hold codes are set up, you must update SA Operator Setup records to allow users to manage operational hold codes. Each operational hold code that an operator is allowed to approve must be selected as Allowed in the Allowed Operational Hold Codes section on the Other Options tab. Each time you add a hold code, you must update the appropriate operator records.

After activation, you must manually apply operational hold codes to open sales orders that were on hold before you activated the feature. You can export a list of orders with legacy hold codes from Sales Order Inquiry. Then, apply operational hold codes in Sales Order Entry or Sales Shipping Feedback Entry. You are not required to manually change the approval code on orders. It automatically changes to n when you apply an operational hold code.

SA Event Manager

These events that generate email or ION alerts about order holds are specific to operational hold codes:

  • oe-apierrhold
  • oe-ccauthhold
  • oe-ccfailhold
  • oe-amounthold
  • oe-marginhold
  • oe-returnshold
  • oe-wlebshold
  • oe-zerohold

The oe-credhold event can be used for both legacy and operational hold codes. The criteria that is used to trigger the event is different for each type of hold code.

See Event and trigger list.

If you receive notifications about margin holds or amount holds, you can receive two notifications when you process an order that meets these conditions:

  • The order is fully-tendered with at least one product that requires back order.
  • A margin hold or amount hold is applied to the order after the order is saved. No other holds are applied to the order.

If you follow this work flow, it will result in the two notifications. Because the event is triggered before the back order processing is complete, you can ignore the second notification.

  1. After you save the order, you receive notification that the order is on hold.
  2. You release the hold, and the order is approved.
  3. You print the pick ticket or ship the order.
  4. The back order is created.
  5. You receive notification that the back order is on hold.

    This is a temporary hold that is removed.

  6. Payment is applied to the back order.
  7. The hold is automatically removed from the back order.
  8. You can verify that the back order is approved in Sales Order Inquiry.

Miscellaneous

For an Infor Service Management integration, you must allow the default operator to process API/EDI holds to prevent sales order holds. The default operator is the specified in the Inbound Message Service Operator field in SA Administrator Options-Integrations-ION Interface Options. If the Inbound Message Service Operator is blank, then the default operator is the 'sys' user.

If you copy an order with holds in Sales Order Entry, the holds are not copied to the new order.

These functions support operation hold codes:

  • SA Data Extraction for Data Lake and Birst: The OEEHCH database table, which contains the operation hold codes from SA Table Code Value Setup, can be extracted for the Infor Data Lake.
  • Sales Order Master List Report
  • SA Data Archive Orders Report
Related topics