Topic overview

The batch application Update deman data is used to update demand data. Below you will find, among other things, descriptions of how to use this batch application. You will also be informed about the effects.

Definitions of terms

Background application
A background application is an application that is run without interaction with a user. It can be opened either by a batch job, a CORBA call-up, or another application.

Reservation
A reservation is a guarantee that a certain good will be deliverable at a specific date. Reservations represent the link of a demand origin (element) to a demand coverage (element). A reservation is only possible if both items and warehouses match between demand origin (element) and demand coverage (element).

Demand origin (element)
Demand origin (element) generates a demand for a demand date that is satisfied by demand coverage (element). Sales orders, for example, are included in demand origin (element).

Demand coverage (element)
Demand coverage (element) satisfies the demand originating with demand origin (element). Demand coverage (element) includes the inventory and planned receipts that arise from purchase orders, for example.

Application description

The batch application Update demand data checks in the Compile and Compile and delete modes whether the demand data corresponds to the customizing and master data settings. If this is not the case, the demand data is regenerated. The data to be checked can be narrowed down using parameters so that, for example, only the demand data for a specific order type or a specific item is checked and updated. Demand data of the non-order type, such as voucherless demand, are not updated by this application.

In Delete and recompile order related mode, the demand data and reservations for an order are removed and recompiles using the customizing and master data settings.

Procedures

The data is updated in several steps. Each step is carried out in a separate background process that is created specifically for this step.

In the first step, customizing and master data settings are determined for affected sites. The settings determined are used to generate background processes for each site, which determine the demand coverage or demand origins for which the demand data is to be updated. In the final step, the demand data is updated. This update also takes place in a separate background process. If a large amount of data needs to be updated, several batch jobs are executed.

The steps are described in more detail below. Depending on the action selected, the steps Compile demand data and Delete demand data are carried out in a different order.

Starting update

The application can only be started once for an OLTP database at a time. The application should be run at a time when few users are using the system as, depending on the data constellation, a lot of data may be updated and mutual interference may occur. In addition, the database may be heavily utilized as the data is obtained via the availability table, which usually contains a large number of entries.

Compiling demand data

Demand data is generated if reservations have been made for the item and the warehouse in accordance with the Customizing and master data settings.

If the [Compile] or [Compile and delete] action is selected, the demand data is only created for those demand origins and requirements coverers that do not yet have any demand data. Existing demand data is not changed and is not regenerated. This means that the demand data is not recompiled.

If the [Delete and recompile order related] action is selected, the demand data for the specified order is recompiled. This means that the demand data for the order is first deleted and then the demand data is recompiled.

For all actions, only demand data is generated, but no reservations are made. Exceptions to this are warehouse vouchers, which are immediately reserved against inventory, and order-related purchasing, where both orders are also immediately reserved against each other. If a subsequent reservation of the newly generated demand data is desired, the batch application Automatic reservation can be executed after updating the demand data.

When setting up the demand data, any existing identifier reservations are deleted.

Deleting demand data

If the [Compile and delete] action is executed and no reservations are planned for the item and the warehouse in accordance with the customizing and master data settings, the demand data of the demand coverage and demand origins are no longer required and are therefore deleted.

If the [Delete and recompile order related] action is executed, the demand data for the specified order is always deleted first.

When the demand data is deleted, identifier reservations may be generated. The identifier reservation is made for all order categories for which an identifier is specified.

Updating demand origin

When the demand data is compiled and deleted, the references to the demand data in the demand origins are updated. Before the update, the usual lock is requested, which prevents several users from changing order data at the same time. If the lock cannot be set for an origin, the associated demand data is not updated.

Status messages

The application issues messages that provide information about the number of updated demand data as well as possible causes if data could not be updated. These messages can be viewed in the Message logs application.

Parameters

The batch application Update demand data has the following parameters:

Action – in this field, select the action to be carried out when updating the demand data.
Information on the individual steps of the update can be found in under Procedures.
The following selection options are available:

• [Compile]
  The demand data is generated. Use this action, for example, if you have newly activated the Reservations function and no demand data is available yet.
• [Compile and delete]
  If they do not already exist, the demand data is regenerated and any existing identifeir reservations are deleted. Existing demand data is not changed and is not regenerated. The demand data that is no longer required due to the changes to the reservation settings is deleted. Use this action, for example, if you are already working with the Reservations function and the reservation setting has been changed in the master data of items or warehouses.
• [Delete and recompile order related]
  The demand data is reconstructed, i.e. first the demand data and any existing identifier reservations for the specified order are deleted and then the demand data is recreated using the customizing and master data settings. Use this action, for example, if the demand data for a specific order is incorrect.

Site – enter a site if required. When updating the demand data, only the data whose sites match the selection criterion is taken into account. If you do not specify a site, the data update is not restricted to the site.

Inventory owner – enter an inventory owner if required. When updating the demand data, only the data whose owner matches the selection criterion is taken into account. If you do not enter an inventory owner, the data update is not restricted to the inventory owner.

Warehouse – enter a warehouse if required. When updating the demand data, only the data whose warehouses match the selection criterion is taken into account. If you do not enter a warehouse, the update of the data is not restricted to the warehouse.

Item – enter an item if required. When updating the demand data, only the data whose items match the selection criterion is taken into account. If you do not specify an item, the data update is not restricted to the item.

Order category – in this field, select the order categories for which the demand data is to be updated. You must select at least one order category. If you want to update the demand data for a specific order, you must select the appropriate order category. The following options are available:

• Sales quotation
• Sales order
• Production order
• Inventory requisition
• Picking order
• Delivery order
• Purchasing RFQ
• Purchase order
• Receipt of goods
• Distribution order

Order number – if you select the [Delete and recompile order related] action, enter the number of the order whose demand data is to be recompiled in this field. You must also select the appropriate order category in the Order category field.

Affected business objects

The following business objects are affected by the application:

• Name: Demand: com.cisag.app.inventory.reservation.obj.DemandOrigin
• Description: Demand line item: com.cisag.app.inventory.reservation.obj.DemandOriginDetail
• Title: Demand coverage: com.cisag.app.inventory.reservation.obj.DemandCoverage
• Description: Demand coverage line item: com.cisag.app.inventory.reservation.obj.DemandCoverageDetail
• Name: Reservation: com.cisag.app.inventory.reservation.obj.FixedReservation
• Name: Inventory data (reserved): com.cisag.app.inventory.obj.InventoryOnhandReservation
• Name: Change in availability: com.cisag.app.inventory.obj.AvailabilityDetail
• Description: Inventory and reservation data of serial numbers: com.cisag.app.inventory.obj.SerialNumberOnhand
• Description: Line items of all selectable orders: com.cisag.app...OrderDetail

Customizing

No settings need to be defined in the Customizing application for the Update demand data application.

Business entities

For the Update demand data application, the following business entity is relevant, which you use, for example, to

• assign authorizations,
• set up activity definitions or
• import or export data.

Change in availability: com.cisag.app.inventory.obj.AvailabilityDetail

Authorizations

Authorizations can be assigned using the authorization roles as well as by assigning an organization. The authorization concept can be found in the technical article Authorizations.

Special capabilities

The following special capability exists for the Update demand data application, which relates to actions. You can assign authorizations for this capability in the Authorization roles application.

Description: Execute the Update demand data application: com.cisag.app.inventory.reservation.log.UpdateDemandData

A user can only run the batch application Update demand data if this capability is assigned to them.

Organization assignments

For the Update demand data application, an organizational assignment is not required.

Special features

There are no special features for the Update demand data application.

Authorizations for business partners

The Update demand data application is not released for business partners.