Hierarchy
SEM-BW (Software Component) SEM-BW: Strategic Enterprise Management⤷
FIN-BAC (Application Component) Business Accounting⤷
UR_REALIGNMENT_TOOL (Package) Realignment Tool
Basic Data
| Data Element | UR_SCHED_REAL |
| Short Description | Scheduling Realignment Runs |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Delta |
| Medium | 15 | Delta |
| Long | 20 | Delta |
| Heading | 10 | Delta |
Documentation
Definition
Start parameter for realignment run.
Use
The parameters in the popup can be used to influence the runtime of realignment runs.
Parallel Jobs:
Given the large quantities of data, the runtime for realignment runs is normally quite considerable. This can be shortened by distribution to several parallel jobs.
Package Size:
The package size determines the maximum quantity of data that a job can edit at one time. After a package is completed, a new job is created once the current one has finished, provided that one or more packages have not yet been processed. As all the data in a package is committed in a database transaction, the package size should not be set too high.
Test Mode for Realignments
In test mode, processing takes place in the foreground and is not parallelized. The realignments are carried out, but not saved in the database.
Activate Trace for Realignments:
All characteristic changes are logged in the trace. With live runs, the quantity of data created can be very large, which can be problematic.
Realignments without Transaction Delta:
With the 'full' mode, no delta is created for transaction data. Instead, only the object changes are carried out. If the object changes are replicated to the object table, the InfoProvider must be re-initialized. The full mode is therefore recommended if the quantity of data affected by the realignment is particularly large.
Dependencies
Example
History
| Last changed by/on | SAP | 20041006 |
| SAP Release Created in | 1.1 |
