Hierarchy
⤷ PY-XX-DT (Application Component) Data Transfer
⤷ PCPO (Package) PY: Posting Transfer
Basic Data
Data Element | HRPP_ARFC_PROCMODE |
Short Description | Processing Type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | HRPP_ARFC_PROCMODE | |
Data Type | CHAR | Character String |
Length | 7 | |
Decimal Places | 0 | |
Output Length | 7 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
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 | Process. |
Medium | 19 | Processing |
Long | 25 | Processing Type |
Heading | 25 | Processing Type |
Documentation
Definition
Type of generation of posting index and posting items - in parallel or in series
Use
In this field you can specify how you want to generate the posting index and posting items, you can generate:
- the posting index and the posting items in series
- the posting index in parallel, but the posting items in series
- the posting index and the posting items in parallel
You can use the field Type of Saving to process the saving of the posting index in parallel.
In detail:
Parts of the posting transfer are suitable for parallel processing, meaning that personnel numbers are split into sets that are simultaneously processed in separate processing tasks. Other parts, however, require strict processing in series. If you choose parallel processing, it is technically realized in the form of the asynchronous RFC.
Posting transfer is divided into five processing steps that are performed in the following order:
- Generation of Posting Index: The generation of the posting index for the auditing information is suitable for parallel processing. In particular, this allows the runtime-intensive read accesses to the payroll results to be simultaneously run in the parallel running processing tasks. If possible, this step should be run in parallel for large quantities of data.
- Generation of Posting Items: The generation of the posting items from the posting index can also run in parallel, based on the set posting index generated in the first step per processing task. The set posting items generated per set and the set posting index contain provisional auditing references so that the origin of a set posting item from the items in the set posting index is known. This step should be processed in parallel because parallel processing improves performance. However, in this case there are also reasons against using parallel processing: The generation of posting items requires an extensive amount of data from Accounting that is usually obtained using RFC. The read data is buffered within the processing tasks to reduce the runtime. The efficiency of buffering depends in the size of the set. This set size and the maximum number of parallel processing tasks specifies the main memory load using the posting transfer. A main memory restriction restricts the size of the set. This is particularly relevant if the processing tasks are not distributed to various application servers during parallel operation.
- Merging and adjustment: After the second step has been performed, it is necessary to merge the set posting items with the posting items of other sets and the auditing references must also be adjusted in the set posting index. This merging and adjusting step can only take place in series in the main program.
- Saving posting index: After the merging and adjustment step, the set posting index must be saved to the database, which is possible in parallel processing tasks that are to be restarted for each set - regardless of the completed processing task for the generation of the posting index and the posting items - see Type of Saving. The efficiency of saving in parallel largely depends on the database locks that are set by the database.
- Creation of posting documents: The creation of posting documents from the posting items is only possible in series in the main program.
The steps that can be performed in parallel (that is the generation of the posting index and posting items as well as the saving of the posting items) predominantly determine the runtime of posting transfer. In contrast, the merging and adjustment step does not take very long and the creation of posting documents works only with the heavily condensed posting items information and therefore requires much less runtime.
Dependencies
Example
History
Last changed by/on | SAP | 20080505 |
SAP Release Created in | 600 |