Hierarchy
⤷ FI-GL-REO (Application Component) General Ledger Reorganization
⤷ FAGL_REORGANIZATION_FW (Package) Reorganization - Framework
Basic Data
Data Element | FAGL_R_JOB_PARTN_RATIO |
Short Description | Obsolete |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | FAGL_R_JOB_PARTN_RATIO | |
Data Type | NUMC | Character string with only digits |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
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 | Percentage |
Medium | 20 | Reduction Percentage |
Long | 30 | Reduction Percentage |
Heading | 5 | % |
Documentation
Definition
Percentage by which the partition size of an object type is reduced per hierarchy level.
Use
You can run the following mass activities in parallel:
- Generate object list
- Reassignment
- Transfers
When one of the above activities is called, the system runs a dispatching program that divides the account assignment objects for processing into subpackages of a defined size.
During processing by hierarchy, the reduction percentage controls by what percentage the specified partition size is reduced per hierarchy level, that is, how many objects are combined into a subpackage.
You can influence the overall performance of a parallel process by selecting a subpackage size that enables the data to be processed to be distributed more or less evenly. For example, you can group very frequently assigned materials together while grouping less frequently assigned materials together. As a general rule: The smaller the subpackages, the more evenly the processing effort is distributed across the jobs to be run. However, very small subpackages can negatively affect performance because parallel processing itself then needs to be managed (involving the distribution of work packages and database accesses, and so on).
If you do not specify a reduction percentage, the system applies a generic reduction percentage for parallel processing.
In an unfavorable structure of account assignment objects, however, it is possible that some jobs are finished while one or more jobs continue processing, for a considerable amount of time, subpackages in which frequently used objects are processed, for example.
If this is the case, you need to decrease the reduction percentage, which may be restricted for the affected account assignment objects.
Dependencies
The reduction percentage is used to determine the size of a partition of objects for processing. This is the size of a partition for a single hierarchy level (that is, excluding any dependent objects of a reorganized account assignment).
Example
For the object Materials, you have specified a partition size of 1000 objects and a reduction percentage of 50%.
- If materials only are selected for processing, the amount of materials for processing is split up into packages of 1000 and then processed in parallel using the jobs generated.
- If not only the materials but also the assigned purchase items are selected for processing, the amount of materials for processing is split up into packages of 500 (50% of 1000) and then processed in parallel using the jobs generated. A smaller package size has to be selected because, in the activity Change Account Assignment, for example, not only the materials are determined and reassigned but all the assigned purchase items as well.
- If not only the materials but also the assigned purchase items as well as the invoice items generated from the purchase items are selected for processing, the amount of materials for processing is split up into packages of 250 (50% of (50% of 1000)) and then processed in parallel using the jobs generated. A smaller package size has to be selected because, in the activity Change Account Assignment, for example, not only the materials are determined and reassigned but all the assigned purchase items and the invoice items generated from the purchase items as well.
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in | 605 |