SAP ABAP Data Element ACE_RUNTYPE (Run Type of Periodic Posting Program)

Hierarchy

☛ EA-FIN (Software Component) EA-FIN
   ⤷ FI-GL-GL-ACE (Application Component) Accrual Engine
     ⤷ ACE-PS (Package) Accrual Engine: Posting Server Basis

Basic Data

Data Element	ACE_RUNTYPE
Short Description	Run Type of Periodic Posting Program

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	ACE_RUNTYPE
Data Type	CHAR	Character String
Length	1
Decimal Places	0
Output Length	1
Value Table

Further Characteristics

Search Help: Name	ACE_RUNTYPE
Search Help: Parameters	RUNTYPE
Parameter ID
Default Component name
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Run Type
Medium	15	Run Type
Long	20	Execution Type
Heading	7	R. Type

Documentation

Definition

When posting accruals periodically, you can choose between the following run types:

1. Normal
   This can be considered the default run type.
2. Repeat run
   A repeat run is necessary if processing was not successful for all accrual objects during a normal run, that is, if Accrual Engine documents could not be created for all accrual objects.
   This could have the following causes:
1. The choice of selection options for the normal run meant that not all accrual objects were selected.
2. Errors occurred in the normal run, meaning that not all Accrual Engine documents were posted.
   Note:
   A repeat run is not required if errors occurred during the transfer of Accrual Engine documents to Accounting but all Accrual Engine documents were still posted.
3. Unplanned
   The periodic accrual runs normally have to take place on the key dates allowed on the basis of the rhythm in Accrual Engine posting control. The accrual runs have to take place for all of these key dates. For this purpose, the key dates must be processed in ascending order.
   Example:
   You have chosen "monthly" for your rhythm. This means that periodic accrual runs during 2000 are only possible on the following key dates:
   31 Jan. 2000
   29 Feb. 2000
   31 Mar. 2000
   For key date 31 Jan. 2000, you have carried out a run with run type "normal". This means that the next run should take place with key date 29 Feb. 2000. If, however, you want to skip this key date and carry out the next run with 31 Mar. 2000 as the key date, this is only possible if you choose run type "unplanned".

See the following exception to the "normal" and "repeat" run types.

History

Last changed by/on	SAP	20011120
SAP Release Created in	461