Topic overview

The Recompilation of availability records application reconstructs the availability records for various order categories (sales order, sales quotation, purchase order, production order, distribution order, delivery order, picking order, inventory requisition, receipt of goods) and non-order categories (inventory posting, incorrect inventory posting, voucherless demand, batch inventories).

Definitions of terms

Availability
The availability is the predicted supply of an item on a current or a future date. Availability is calculated by means of an availability rule and consists of:

• the current inventory,
• planned receipts,
• the planned issues.

Possible back orders can also be taken into account with the calculation of availability. If the reservation function is used, availability consists of:

• the unreserved current inventory,
• the unreserved planned receipts, and
• the unreserved planned issues.

Partial quantities are also taken into consideration in the process.

Application description

The Recompilation of availability records application is used to reconstruct the availability records for the following origins.

• Order categories:
  • Sales quotation
  • Sales order
  • Delivery order
  • Picking order
  • Distribution order
  • Production order
  • Purchase order
  • Inventory requisition
  • Receipt of goods
• Non-order categories:
  • Inventory posting
  • Incorrect inventory posting
  • Voucherless demand
  • Inventory

You can select the order categories and non-order categories individually, combined or all. The new structure can also be restricted to a single item.

The Inventory category is used to create new availability records that are managed for batch inventories (see Introduction: Availability).

Control parameters are used to influence the speed and output of the application.

Procedures

The recompilation of the availability records can only function correctly if no other process is changing the availability data at the same time; conversely, the simultaneous recompilation could also disrupt these processes. For this reason, the first thing that is checked after starting the batch job for the recompilation is that no user has opened a dialog application (cross-database). Otherwise, an error message is issued for each active application and the recompilation is terminated immediately; inventory management servers are an exception; they can also run during the recompilation.

As a user starting this application, please log out first. Then restart the session to ensure that this application is the only open application.

As soon as it is determined that no other dialog application is active, the recompilation is started; for each order or non-order category, all availability records for this category are first deleted from the database (if necessary, only for the specified item) and then recompiled from orders, vouchers or other source data.

Once all order and non-order categories have been processed, the data created is compared with the demand and reservation data:

• reserved quantities are copied to the availability records
• information on existing demand data is entered in the availability records
• new 0-availability records are created as required for existing completed demand data if they were not or could not be created during the recompilation (for reasons of data integrity)
• availability quantities are increased if excess demand quantities are noted in demand data

Demand and reservation data itself is not changed.

Special case: receipts of goods

Receipts of goods should not have their own availability or reservation data. Recompiling availability records for receipts of goods means that all availability data for receipts of goods is deleted and not recompiled.

This situation makes it necessary to delete any existing demand and reservation data as they would otherwise be generated automatically during the final comparison (see the Process section above). This is done by directly calling up the Reorganize reservation data application for receipts of goods.

Error handling

The batch job is not started if no initiator has been selected or a non-existent item has been entered.

The batch job is canceled if at least one dialog application from the APP area is open.

If execution is interrupted due to a serious error, the reason for the error should be found immediately, the error rectified and the recompilation executed again, as otherwise all availability records for the affected order category may be missing.

During the final comparison of the demand and reservation data, different incorrect constellations can also be detected; in this case, these errors are reported and the recompilation is continued with the next data element.

Work pane

Above the work pane you will find a brief description of the application. The following fields are also available:

Origin – in this field, select the origin(s) for which you want to recompile the availability records. The following order categories or non-order categories can be used as origins:

• Order categories:
  • Sales quotation
  • Sales order
  • Production order
  • Inventory requisition
  • Picking order
  • Delivery order
  • Purchasing RFQ
  • Purchase order
  • Receipt of goods
  • Distribution order
• Non-order categories:
  • Inventory posting
  • Incorrect inventory posting
  • Voucherless demand
  • Inventory

Item – if required, enter an item for which you want to recompile the availability records. If you do not enter an item, the availability records will be recompile for all items.

Control parameters grouping

Fast delete – if this function is not active, all availability records to be deleted are deleted in blocks of an adjustable size via the persistence service.
If this function is active, all availability records to be deleted are deleted in one step with a DELETE-OQL statement in a large database transaction. Although this works faster, it can lead to an abort if the amount of data is too large because database systems have limited buffers for transactions, depending on the configuration.

Block size when deleting – database transaction size for the deletion of availability records when deleting via the persistence service (maximum number of deleted availability records after which a transaction change takes place).

Process outputs – if this function is active, a progress message is written to the message log after each processed data block.

Block size when inserted – database transaction size for saving generated availability records (maximum number of availability records inserted after which a transaction change takes place).

Application-related action: Start data correction

The action performs the recompilationing of the availability records for the selected origins.

Customizing

No settings need to be defined in the Customizing application for the Recompilation of availability records application.

Business entities

No business entity is relevant for this application.

Authorizations

Authorizations can be assigned both with the help of authorization roles and by assigning an organization. The authorization concept can be found in the technical article Authorizations.

Special capabilities

There are no special capabilities for the Recompilation of availability records application.

Organization assignments

An organizational assignment is not required for the Recompilation of availability records application.

Special features

The following special features must be taken into account for the Recompilation of availability records application:

The application cannot be opened via the user menu. You can open it via the URL https://<SYSTEM>/com.cisag.app.inventory.tools.ui.RefreshAvailabilityDetail.class. Alternatively, it can be opened via the Development objects application (application: com.cisag.app.inventory.tools.ui.RefreshAvailabilityDetail).

Starting the correction requires that no user has opened a dialog application. If a relevant application is active, the recompilationing of the availability records is aborted with an error message. The error message informs you of the affected application that has prevented the data update from being executed.

Authorizations for business partners

The Recompilation of availability records application is not released for business partners.