Transaction date determination rules

Topic overview

The Transaction date determination rules application is used to define criteria on the basis of which the transaction data of an item is determined.

This article describes how the application Transaction date determination rules application is structured. For instructions on how to use transaction date determination rules, e.g. how to edit rules, refer to the article Procedures: Transaction date determination rules.

Display via the cockpit

The rules used in the application Transaction date determination rules application are required to determine the last transaction date of an item. You can display the relevant data via the Cockpit: Transaction dates application.

Application description

Using the Transaction date determination rules application, you can define rules according to which the last transaction date of an item is determined using the posting date of the relevant inventory postings. The rules can take into account inventory management organizations, inventory owners or voucher types, among other things.

The Transaction date determination rules application consists of an identification pane and a work pane.

Identification pane

The identification pane contains the fields that uniquely identify a transaction date determination rule.

Below is a detailed description of the fields:

Transaction date determination rule – enter an identification for the transaction date determination rule in the Transaction date determination rule field. The identification uniquely identifies the determination rule within an OLTP database. The identification can consist of numbers, letters or a combination of numbers and letters and can be freely selected the first time it is entered.

Status – a transaction date determination rule can have the following statuses:

  • Active – if the Active status is set, the tooltip for the icon also shows you whether data has already been determined. The following data determination statuses can be displayed:
    • Data not determined
    • Data determination in progress: (timestamp)
    • Data determined: (timestamp)

The respective time stamp provides information on when the data determination has been running or when the data was last determined.

  • Inactive – if the Inactive status is set, the rule is not taken into account.

Only determination rules with the status Active can be used to determine the last transaction date of an item.

Description – the name serves as an additional identifier. It can consist of freely selectable text. Enter a meaningful and, if possible, unique name to make it easier to search for.

Determination level – you can specify the level at which the last transaction date of an item is to be determined. Select one of the following levels:

  • Item
  • Item + warehouse
  • Item + inventory owner
  • Item + warehouse + inventory owner
Note
If a determination level without a warehouse is selected, the time zone cannot be determined. If these being the cases, the client’s time zone is used.
Note
If a determination level without an inventory owner is selected, a total inventory cannot be determined.

Work pane

In the work pane, you will find the Inventory posting characteristics grouping, in which you define the characteristics for determining the last transaction date.

Inventory posting characteristics grouping

Below is a detailed description of the fields:

Posting key – if required, enter one or more posting keys in this field. To determine the last transaction date, the inventory postings that contain one of the entered posting keys are taken into account. If you do not enter a posting key, inventory postings are taken into account for determining the last transaction date regardless of the posting key contained.

Inventory item – in this field, enter one or more inventory items for which the last transaction date is to be determined. If you do not enter an inventory item, the last transaction date is determined for all inventory items.

Warehouse – enter one or more storage locations in this field. The inventory postings that contain one of the entered storage locations are taken into account when determining the last transaction date. If you do not enter a storage location, inventory postings are taken into account regardless of the storage location when determining the last transaction date.

Note
If a determination level without a warehouse is selected, the time zone cannot be determined. If these being cases, the client’s time zone is used.

Warehouse category – specify whether inventory postings for a specific warehouse category should be taken into account when determining the last transaction date. Select at least one of the following warehouse types:

  • Physical (internal)
  • Physical (external)
  • Virtual

Inventory owner – enter one or more inventory owners in this field. When determining the last transaction date, only the inventory postings that contain one of the entered inventory owners are taken into account, and therefore only the items that belong to the respective inventory owner are considered. If you do not enter an inventory owner, inventory postings are taken into account regardless of the inventory owner when determining the last transaction date.

Note
If a determination level without an inventory owner is selected, a total inventory cannot be determined.

Inventory owner category – specify whether inventory postings should be taken into account for the update of the last transaction date if the inventory owner is an internal partner (Company organization type) or an external partner (customer, supplier). Select at least one of the following inventory owner categories:

  • Internal
  • External

Process – specify which inventory posting transactions are to be taken into account when determining the last transaction date. Select at least one of the following processes:

  • Receipt
  • Issue
  • Transfer receipt posting
  • Issue transfer posting
  • Receipt revaluation
  • Issue revaluation
  • Correction
Note
Please note that only those inventory postings are taken into account that also comply with the other specifications of the same rule.

Process category – specify which inventory posting process categories are to be taken into account when determining the last transaction date. Select at least one of the following processes:

  • Primary process
  • Special process

Quantity transaction – specify whether inventory postings with or without quantity transactions should be taken into account when determining the last transaction date. Select at least one of the following entries:

  • Yes
  • No
  • Ignore

Inventory valuation – specify whether inventory postings with or without inventory valuation should be taken into account when determining the last transaction date. Select at least one of the following entries:

  • Yes
  • No
  • Ignore

Inventory posting voucher category – in this field, select which inventory posting voucher categories are to be taken into account when determining the last transaction date. You can choose between the following inventory posting voucher categories:

  • Delivery order
  • Customer invoice
  • Picking order
  • Production order
  • Receipt of goods
  • Supplier invoice
  • Inventory order
Note
Please note that a manual inventory posting is saved without an inventory posting voucher, as it was entered manually and not created by a process. Only automatically generated inventory postings are based on an inventory posting voucher. Select all inventory posting voucher types if you also want to take manual inventory postings into account. Also note the setting in the Inventory posting origin field.

Original voucher category – in this field, select which source voucher categories that are linked to the inventory posting are to be taken into account when determining the last transaction date. You can choose between the following entries:

  • Delivery order
  • Picking order
  • Production order
  • Inventory requisition
  • Purchase order
  • Receipt of goods
  • Sales order
  • Supplier contract
  • Distribution order
  • Consignment withdrawal declaration
Note
Please note that a manual inventory posting can be saved without a source voucher. Select all original voucher categories if you also want to take manual inventory postings without an original voucher into account. Also note the setting in the Inventory posting origin field.

Inventory posting origin – specify whether inventory postings of a certain origin should be taken into account when determining the last transaction date. Select at least one of the selectable origins:

  • Manual inventory posting
  • Inventory count
  • Inventory count valuation
  • Receipt of goods
  • Delivery order
  • Production order
  • Supplier invoice
  • Inventory order
  • Loading unit
  • Import
  • Loading unit from inventory count
  • Customer invoice
  • Goods receipt correction
  • Transfer posting to production warehouse from picking
  • Automatic issue postings upon receipt of goods at Production
  • Return of goods
  • Merge/split
  • Package/unpack
  • Change loading unit

General ledger entry source – specify whether inventory postings with a specific general ledger posting source should be taken into account when determining the last transaction date. Select at least one of the selectable sources.

Note
This field is only available if the Financials and General ledger entries functions have been activated for at least one company in the Customizing application.

Site – if required, enter one or more sites in this field. To determine the last transaction date, the inventory postings that contain one of the recorded sites are taken into account. If you do not enter a site, inventory postings are taken into account regardless of the site for determining the last transaction date.

The following application-related actions are available in the Transaction date determination rules application:

Activate transaction date determination rule

This action is used to activate the open transaction date determination rule. Only active rules automatically determine the last transaction date for items after each affected inventory posting in accordance with the rule’s specifications.

Please note that after activating a transaction date determination rule, the batch application Determine last transaction date must be executed at least once in order to take existing inventory postings into account. If you want to update the data regularly, use the batch application’s series function.

Deactivate transaction date determination rule

This action is used to deactivate the open transaction date determination rule. The transaction date is then no longer determined and the transaction data that has already been determined based on the rule is deleted.

Determine last transaction date

This action is used to have the system determine the last transaction date of an item. If you click on the action, a dialog window opens for the execution of the associated batch application Determine last transaction date, which is used to determine the data.

Note
The same batch application can also be found in the user menu in the navigation pane.

To run the batch application, you can define the date from which the inventory postings are taken into account and the transaction date determination rules according to which the system should determine the last transaction date. The open, activated transaction date determination rule is proposed in the Transaction date determination rule field. If you leave this field empty, the data for all active transaction date determination rules will be determined.

Depending on the scope of the inventory postings to be taken into account, determining the last transaction date can take more or less time and use up resources. It is therefore recommended that the action, and therefore the batch application, is executed at a time when few interactive users are working with the system.

If you want to determine the last transaction date repeatedly, you can start the processing job for executing this batch application as a series.

Customizing

For the application Transaction date determination rules application, no settings need to be defined in the Customizing application.

Business entities

For the Transaction date determination rules application, the following business entity is relevant, which you use, for example, to

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

Rules for the last transaction date: com.cisag.app.inventory.obj.LastTransactionDataRule

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

There are no special capabilities for the Transaction date determination rules application.

Organization assignments

If the Content-related authorizations function is activated in the Customizing application, a person can use the Transaction date determination rules application only if an organization has been assigned to them in the partner master data that is integrated into at least one of the following organizational structures:

  • Inventory management

Special features

There are no special features for the Transaction date determination rules application.

Authorizations for business partners

The Transaction date determination rules application is not released for business partners.

Czy ten artykuł był pomocny?

Wyślij opnie