Posting server

Topic overview

This document describes the Posting server application. A posting server is used for processing postings, transferring Controlling-relevant data and determining the payment history that are generated by applications from the Financial Accounting, Asset Accounting and Controlling framework. Every framework represents a system in the Posting server application to which one or more posting servers are assigned. Only one posting server should be active per each subsystem used. In the posting dialog of the Financial Accounting, for example, the postings entered are posted directly only if the posting server is started or active in the Financial Accounting subsystem.

A posting server can be locked automatically by an application. This prevents other applications from generating postings at the same time. The posting servers of the subsystems Financial Accounting, Deferments, Automatic follow-up posting and Balances, for example, are blocked by the following applications:

  • Rebuild balances
  • Rebuild open items per period
  • Delete Financial Accounting balance carried forward (if an open fiscal year with balance carried forward, but without postings, is reset to the status Open Budget)

Application description

With this application, you can define posting servers for posting activities. The posting servers are assigned to a subsystem through selection. You can use actions for starting or stopping a posting server or for removing a lock set.

The Posting server application consists of an identification pane and a work pane.

Identification pane

In the identification pane of the application, you can enter the identification of the posting server and the related description.

Detailed description of fields:

  • Name – here, enter the name for the posting server that you want to create or edit.
  • Description – the description serves as an additional distinguishing characteristic. It can consist of any user-defined text. Enter a meaningful, memorable description that is as unique as possible to facilitate searches for it. The description can be entered in several languages.
  • Processing queue – in this field, enter the queue that should be used by this posting server. In the processing queue, one or more batch jobs are queued until processing.
  • Application server – here, enter the application server to be used.
  • Sub system – select the subsystem under which the posting server should run. The following subsystems can be selected:
    • Financial Accounting (for postings within the Financial Accounting)
    • Controlling (for postings within the Controlling)
    • Asset Accounting (for postings within the Asset Accounting)
    • Transfer to Controlling (transfer of postings from the Financial Accounting to the Controlling. For example, postings with cost types for optional dimensions)
    • Payment history (for determining the payment history).
    • Liquidity management (e.g. for creating the extrapolation data).
    • Deferments (for postings of deferments)
    • Automatic follow-up posting (for the creation of automatic follow-up postings)
    • Balances (for determining and posting the balances)
    • Additional distribution (for additional distribution of e.g. cash discount on additional optional dimensions)
  • Check voucher – this label is available only for posting servers that are assigned to the Financial Accounting subsystem. If you activate this label, it will be verified whether the vouchers in the Financial Accounting add up to Zero. Only a user, who has the appropriate capability, can activate the indicator (see Special capabilities).

Note: This label must be always activated.

Work pane

The work pane of the Posting server application displays the status information of the posting server. The work pane of the application consists of the following fields:

Open vouchers –this field displays the count of vouchers that have not been processed yet.

  • Executed vouchers – this field displays the count of vouchers that have already been processed.
  • Status – this field displays the current status of the posting server. If the posting server is started, this field contains the Running value.
  • Last posting – this field contains information, such as date and time, about the last posting processed.
  • Lock status – this field displays whether the posting server is locked.
  • Action – if the posting server is locked by an application, the application is displayed here.
  • Point in time – this field displays the time point at which the posting server was called up for processing.
  • Start time point – if the server is started, the date and time of the starting time point are displayed here.
  • Operation time – for an active posting server, this field indicates for how long the server has been active already.
  • Application server – this field displays the assigned application server.
  • Status of the batch job – this field displays the current status for the batch jobs.
  • Serial pattern – if the posting server was started time-controlled in the background, the serial pattern used is displayed in this field.

Application-based actions

The following application-based actions are available in the Posting server application:

Start posting server

Via the action role in the standard toolbar, you can start the posting server with the Start posting server action. If batch jobs exist, they will be processed after the start.

The action is only active when the user has the appropriate capability (see Special capabilities).

Note
Only one posting server should be active per subsystem.

Start posting server in batch

You can use this action to create a previously selected posting server as a background job. This enables you to start and stop the posting server on a time-controlled basis.

Stop posting server

Via the action role in the standard toolbar, you can stop the posting server with the Stop posting server action. If batch jobs still exist, they will be stopped.

The action is only active when the user has the appropriate capability (see Special capabilities).

Customizing

The Posting server application does not need any specific settings in Customizing.

Business entities

The following business entity is relevant for the Posting server application that you use, for example, in order to:

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

Posting server

com.sem.ext.app.fin.general.obj.PostingBatchServer

Authorizations

Authorizations can be assigned by means of authorization roles as well as through a content-based authorization (by assignment to organizations). The authorization concept is described in the Authorizations article.

Note
In some circumstances, the authorizations in Financials override the authorizations described in the technical documentation. Thus, to start the posting server, in addition to the special capabilities, the user needs the ADMINISTRATORS authorization role in any case.

 Special capabilities

The following special capabilities exist for The Posting server application that relate to actions of the application. For these capabilities, you can assign authorizations in the application Authorization roles.

  • Start and stop posting server

com.sem.ext.app.fin.general.batchserver.StartStopPostingServer

If a user has this capability, he can start or stop the posting server.

  • Activation for voucher check

com.sem.ext.app.fin.general.CheckVoucher

If a user has this capability he can enable the voucher check for the posting process.

Organizational assignments

Organizational structures are used to control which data can be viewed, used, or edited. The Content-based authorizations function must be activated in the Customizing application for this purpose.

To ensure that the Posting server application is displayed for a person in the user menu, the user must be assigned to an organization that is connected to one of the following organization structures:

  • Financials

Special features

The Posting server application has no special features.

Authorizations for business partners

The Posting server application is not released for business partners.

Czy ten artykuł był pomocny?