SAP ABAP Data Element HRSVERBU (Number of data records to be posted)
Hierarchy
☛
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR
⤷
PT (Application Component) Personnel Time Management
⤷
PTIM (Package) HR Time Management Application Development
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PT (Application Component) Personnel Time Management⤷
PTIM (Package) HR Time Management Application Development
Basic Data
| Data Element | HRSVERBU |
| Short Description | Number of data records to be posted |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUM4 | |
| Data Type | NUMC | Character string with only digits |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| 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 | No.records |
| Medium | 20 | Number of Records |
| Long | 40 | Number of data records to be posted |
| Heading | 0 |
Documentation
Definition
Posting time events in Time Management is started by a single posting request. The time events are posted in data packets; each packet is a logical processing unit (LUW) (see Transaction processing).
Determine how many time events should be included in one data packet.
If there are problems with saving or locking data, you can reduce this number.
If you enter the value 0, all time events are posted simultaneously.
One posting request is sufficient to post all time events.
Recommendation
The value should not be too low. 1000 time events per packet is a realistic value.
History
| Last changed by/on | SAP | 19940316 |
| SAP Release Created in |
