Topic overview

Transaction flags are used in controlling to structure the database into direct and secondary data. Secondary data is determined based on the direct data.

This document describes the Transaction flags application.

The procedures for using Transaction flags correspond to the general procedures for spreadsheet applications, which can be found in the article General Procedures for Table applications.

Definition of terms

Primary costs

Primary costs are all costs that can be assigned directly to a cost accounting object. Primary costs posted to a cost center are caused and accounted for by this center.

Secondary costs

Secondary costs are costs that are initially posted (as primary costs) to an auxiliary cost center and then apportioned to the main cost centers using secondary cost methods (allocations). As a rule, these secondary costs are not caused by the recipients, and in particular they are not their responsibility, but they should be borne by them.

Application description

This application is used to display all or individual transaction flags for direct and secondary data. In addition, new transaction flags can be entered for secondary data or existing transaction flags can be revised.

The Transaction flags application consists of a query pane and a work pane.

Query pane

If necessary, you can enter search criteria in the query pane and then use the Update action to retrieve the data from the system and have it displayed in the work pane.

The fields in detail:

• Transaction flag – transaction flags are used to display the possible combinations of “direct” and “secondary data” (Field Direct / secondary) with the four transaction types “Ratio“, “Price“, “Quantity”, “Amount” in the field ‘Type’ within the movement data. So you can identify precisely the desired combination with this transaction flag.
• Description – the description serves as an additional identifier. It may consist of user defined text. Enter a meaningful, memorable and possibly a unique name, to make the search easier. A homonymous name can exist.
• Transaction type – definition of present transaction data. This flag affects the summation within classifications and within evaluation periods. This allows for example to add up prices but not ratios. The following settings are available:
  • Amount
  • Quantity
  • Ratio
  • Rate
• Direct/secondary – direct data are actually incurred transaction data. Secondary data will be generated on the basis of direct data from the application generate secondary costs.
  • The following settings are available:
  • Direct data
  • Secondary data

Work pane

In the work pane of the application, you enter a new transaction type or edit an existing transaction type. The work pane consists of a table with the following fields:

• Transaction flag – transaction flags are used to display the possible combinations of “direct” and “secondary data” (Field Direct / secondary) with the four transaction types “Ratio”, “Price”, “Quantity”, “Amount” in the field ‘Type’ within the movement data. So you can identify precisely the desired combination with this transaction flag.
• Description – the description serves as an additional identifier. It may consist of user defined text. Enter a meaningful, memorable and possibly a unique name, to make the search easier. A homonymous name can exist.
• Transaction type – definition of present transaction data. This flag affects the summation within classifications and within evaluation periods. This allows for example to add up prices but not ratios. The following settings are available:
  • Amount
  • Quantity
  • Ratio
  • Rate
• Direct/secondary – direct data are actually incurred transaction data. Secondary data will be generated on the basis of direct data from the application generate secondary costs. The following settings are available:
  • Direct data
  • Secondary data

Customizing

No settings need to be made for the Transaction flags application in the Customizing application.

Business entities

The following business entity is relevant for the Transaction flags application that you use, for instance, for:

• Assign authorizations
• Set up activity definitions
• Import or export data

Transaction flag

com.sem.ext.app.fin.controlling.obj.TransactionFlag

The business entity is part of the following business entity group:

com.sem.ext.app.fin.controlling.MasterData

Authorizations

Authorizations can be assigned by means of authorization roles as well as by assigning an organization. More about the authorization concept can be found in the articlet Authorizations.

Special capabilities

The Transaction flags application has no special capabilities.

Organizational assignments

If the Content-based authorizations function is activated in the Customizing application, a person can only use the Transaction flags application if an organization that is linked to at least one of the following organizational structures has been assigned to him or her in the partner master data:

• Financial accounting

Special features

There are no special features for the Transaction flags application.

Authorizations for business partners

The Transaction flags application is not released for business partners.