Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-HR (Application Component) Cross-Application Objects in HR⤷
BP (Package) Cross-Application Objects in HR
Basic Data
| Data Element | BEGDA |
| Short Description | Start Date |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DATUM | |
| Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | FROM_DATE | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 6 | Start |
| Medium | 10 | Start date |
| Long | 20 | Start date |
| Heading | 10 | Start date |
Supplementary Documentation - BEGDA 0000
Use
By making an entry in this field, you can limit the number of records to be selected by the system for all functions except 'Create' and 'List'. When a record is created, the relevant value is transferred to the correct field on the next screen.
Table T582A defines, for each infotype, the interval from which records are selected if no, one or two date fields are filled.
Procedure
Example
Dependencies
Supplementary Documentation - BEGDA 0001
Use
Start date of the leave year. The start and end dates of a leave year define the period during which the employee is entitled to take leave.
Procedure
Example
Dependencies
Supplementary Documentation - BEGDA 0002
Use
The start date is automatically set by the system and cannot, therefore, be changed manually.
This date depends on the data that is stored in this infotype. The following data has an effect on the start date:
- the pregnancy notification date
- the expected date of delivery
- the actual date of delivery
- the earliest start date of a recorded absence
These functions ensure that all absences of a particular record are within the validity period of this record.
Procedure
Example
Dependencies
Supplementary Documentation - BEGDA 0003
Use
Infotype 0083 (Leave Entitlement Compensation) uses specific key dates. Therefore, this field only contains a date that is used to import and process the infotype in payroll.
Supplementary Documentation - BEGDA 0004
Use
Date as of which the cumulation rule for averages is valid.
Supplementary Documentation - BEGDA 0005
Use
Date as of which the basic wage type is valid.
Supplementary Documentation - BEGDA 0006
Use
Enter a key date. Validity periods are not supported. (T558A-BEGDA = T558A-ENDDA).
Procedure
Example
Dependencies
Supplementary Documentation - BEGDA 0007
Use
Start date for selecting data from the Recurring Payments and Deductions infotype (0014).
Procedure
Examples
Dependencies
Supplementary Documentation - BEGDA 0008
Use
Start date for selecting data from the Additional Payments infotype (0015).
Procedure
Examples
Dependencies
Supplementary Documentation - BEGDA 0009
Use
Start date for selecting data from the Company Insurance infotype (0026).
Procedure
Examples
Dependencies
Supplementary Documentation - BEGDA 0010
Use
Defines the key date on which date-related tables are accessed (T511K, T512W, T5C1K).
Supplementary Documentation - BEGDA 0011
Use
Enter the start date of the first period to be generated. If your payroll periods are monthly, the date you enter is normally the first of the month. If your payroll periods are weekly, you can enter a different date.
Dependencies
Example
Supplementary Documentation - BEGDA 0012
Use
The validity period of this infotype must always be within one calendar year (January 1 to December 31).
Supplementary Documentation - BEGDA 0020
Use
Test für selection screen
Procedure
Examples
Dependencies
Supplementary Documentation - BEGDA 0100
Use
Procedure
This date defines the first day on which the new infotype view technique should be activated.
The system then delimits the last valid infotype records for which you want to activate a view and copies them to the new start date. This allows you to precisely delimit the new functions offered by the infotype views.
Examples
Dependencies
Supplementary Documentation - BEGDA 0118
Procedure
When you create a new child allowance record, the start and end dates are chosen according to the authorization reason.
Examples
- The employee has worked at an enterprise since 07/01/1991. His/her child is born on 11/4/1993. The start date of the child allowance record is 11/4/1993. The system proposes the end date and the authorization reason for children who have not reached the age of 16.
- An employee joins an enterprise on 8/1/1993. His/her child was born on 7/1/1974 and began studies on 3/1/1994. In this case, you would enter 3/1/1994 as the record's start date, and 09 as the authorization reason (over 16/student). The end of the record should be the end date of the course of studies.
Supplementary Documentation - BEGDA 0119
Procedure
The child allowance must always be recalculated if the number of children to be taken into account has changed. You can determine the correct start and end dates by pressing function key F8 in infotype 0118. Records must be created in infotype 0119 for all periods that appear here.
Supplementary Documentation - BEGDA 0194
Definition
This field should contain the date on which the court declares that employee wages may be garnished to fulfill payment obligations. Rather than the date that the document is entered into the system, this field should contain the date that the garnishment document takes effect.
Exceptions
Within payroll, new garnishments can take effect only during the current pay period. As a result, if the garnishment was established in a previous pay period, then the date in this field cannot reflect the actual date that the garnishment took effect. In such cases, this field should contain the first date of the current pay period.
Procedure
In this field, enter the date that the garnishment takes effect, if that date lies in the current pay period. Otherwise, enter the first date of that period here.
The default entry for this field is the current date.
Supplementary Documentation - BEGDA 0195
Definition
This field should contain the effective start date of the garnishment order. Depending upon the repayment schedule established by the court, the start date of the order may coincide with each payroll period, or it may occur on a less frequent basis.
Exceptions
Within payroll, new garnishment orders can take effect only during the current pay period. As a result, if the garnishment was established in a previous pay period, then the date in this field cannot reflect the actual date that the garnishment took effect. In such cases, this field should contain the first date of the current pay period.
Procedure
In this field, enter the date on which processing of the garnishment order should begin. Since a distinct garnishment order should exist for each payment, the date you enter here will depend upon the date you remit payments to the vendor.
The default entry for this field is the current date.
Supplementary Documentation - BEGDA 0510
Use
In this case, the start date defines the date of the standard pay increase. The percentage increase is valid for all average value bases that are cumulated before this date.
Procedure
Examples
Dependencies
Supplementary Documentation - BEGDA 1001
Procedure
Enter the new effective date for all records in the taxability model. This effective date will also apply to entries you have added in the past that have a begin date later than the new effective date.
Examples
You added a tax class for California on May 1 and regenerated the taxability model. You later realize that you forgot to change some tax class definitions for Texas that should be effective January 1. When you regenerate the taxability model with the effective date of January 1, the new tax class you added to California on May 1 will now also be effective from January 1.
What to do
In this case, you will have to remove the extra tax class you added to California and regenerate the taxability model with an effective date of January 1. This will ensure retrocalculations carried out between January 1 and May 1 are correct for California. You then need to reinsert the new California tax class and regenerate the model with the effective date of May 1.
Dependencies
Supplementary Documentation - BEGDA 1111
Use
You can define the validity period for all infotype records which are stored in the batch input session.
If you want to create a variant in which the current date is the default validity date, flag Variable under ZDATUM in the transaction for maintaining variants. Then select Selection
variables. You can then define a date according to the program
start and save it in a variant.
This is particularly recommendable for background processing.
Procedure
Examples
Dependencies
Supplementary Documentation - BEGDA 4545
Use
Enter a validity period for the loan. The end date must come after the expected repayment end date.
Procedure
Examples
Dependencies
Supplementary Documentation - BEGDATUM 0120
Supplementary Documentation - BEGDATUM 0220
Use
Use this field to identify when the relationship between two objects begins. (By moving objects, you are creating new relationships among objects in a structure.)
The system automatically inserts a default start date, but you may overwrite it. To do so:
- type in a date
Supplementary Documentation - BEGDATUM 0510
Use
Enter a period in these fields to select objects you want to edit.
Objects whose validity date lies within the period you specify are offered for editing.
Procedure
To specify a period, either
- enter a date manually
or - press F4 to display a calendar from which you can then select a date.
NOTE: The dates specified in the current window are proposed by the system as default values for the validity period.
Supplementary Documentation - BEGDATUM 0511
Use
Use the Selection period fields to choose the objects you want to work with in Quick Setup, by naming a selection period. A selection period consists of a start date and end date. All objects that are valid at ANY point during the selection period are available in Quick Setup.
Procedure
Use this field to enter a start date, for the selection period. To do so:
- type in an appropriate date
Supplementary Documentation - BEGDATUM 0520
Use
Enter the start date for your root organizational unit in this field. The system automatically proposes the smallest date (usually the current date). You may overwrite this date.
To complete the field, either:
- enter a date manually
or - press F4 to display a calendar from which you can choose a date.
Supplementary Documentation - BEGDATUM 0525
Use
Use this field to setup a default validity period for Quick Setup. The default will be applied within Quick Setup only, and you will always have the opportunity to override it.
Procedure
The system automatically inserts its default minimum date (usually the current date). You may enter a different date. To do so:
- manually type in a date, or
- press F4 to select from a calendar (double click on the desired date)
Supplementary Documentation - BEGDATUM 0535
Use
Enter the validity period for the relationship between the position and job in these fields.
To do so, either:
- enter a date manually
or - press F4 to display a calendar from which you can choose a date.
Supplementary Documentation - BEGDATUM 0556
Use
In CREATE mode, use this field to identify when the relationship between two objects should start.
The system automatically inserts a default minimum date. You can enter a different date. To do so:
- manually type in a date, or
- press F4 to select from a calendar (double click on the desired date)
NOTE: The start date assigned to the relationship record cannot begin before the start dates of either object involved.
In CHANGE mode, the field cannot be edited. (It is not possible to change start dates once they are established.)
Supplementary Documentation - BEGDATUM 0558
Use
This field displays the start date of the selected object or relationship. This date cannot be changed.
Supplementary Documentation - BEGDATUM 0560
Use
Use this field to identify when the relationship between a position and a holder of a position begins. The system automatically inserts the default start date, but you may overwrite it. To do so:
- type in a date
Supplementary Documentation - BEGDATUM 0570
Use
When renaming objects, enter the start date of the new object abbreviation or name in this field. The system automatically proposes the smallest date. You may overwrite this entry.
To complete the field, either:
- enter a date manually
or - press F4 to display a calendar from which you can choose a date.
Supplementary Documentation - BEGDATUM 0590
Use
In CREATE mode, use this field to identify the date when the relationship between two objects becomes valid. (A Relationship infotype record is automatically created when you establish new objects in Simple Maintenance and Graphics.)
The system automatically inserts a default minimum date. You may overwrite the date.
To do so either:
- manually type in a date, or
- press F4 to select from a calendar (double click on the desired date)
Supplementary Documentation - BEGDATUM 0591
Use
In CREATE mode, use this field to identify the date when the object you are creating becomes valid.
The system automatically inserts a default start date. You may overwrite it. To do so either:
- manually type in a date, or
- press F4 to select from a calendar (double click on the desired date)
Supplementary Documentation - BEGDATUM 0701
Use
Start dat from which position (or organizational unit) is assigned.
Procedure
Examples
Dependencies
Supplementary Documentation - BEGDATUM 0702
Supplementary Documentation - BEGDATUM 2000
Use
In CREATE mode:
Use this field to identify the date when a new object should become valid. (The system automatically inserts the default minimum date, but you may overwrite it.)
In CHANGE mode:
You cannot edit this date.
Supplementary Documentation - BEGDATUM 2001
Use
In CREATE mode:
Use this field to identify the date when a infotype record should become valid. The system automatically inserts a default minimum date, but you may overwrite it.
To complete the field either:
- manually type in a date, or
- press F4 to select from a calendar (double click on the desired date)
In CHANGE mode:
You cannot edit this date.
Supplementary Documentation - BEGDATUM 5100
Use
In CHANGE, DISPLAY, LIST and DELETE modes:
Use the field to select the objects or infotype records you want to work with, by naming a timeframe.
Objects or infotype records that are valid at any point in the stated period are selected.
NOTE: The system also considers the plan version, object abbreviation, object name and infotype status, when records are selected.
In CREATE mode:
The validity period shown here does NOT determine the validity period applied to new objects or infotype records. You apply validity periods to objects and infotype records in the respective infotype windows.
Supplementary Documentation - BEGDATUM 7001
Use
Start date for room search.
The start date of the period in which the system searches for a free and/or occupied room. If you do not enter an end date, the system only searches for a room on the start date.
Procedure
Make sure you use the correct date format.
Examples
24.09.2015
Dependencies
Supplementary Documentation - BEGDATUM 7002
Use
The date for which the system searches for a room or room reservations, or
The start date of a period in which the system searches for a room or room reservations. In this case, you must also enter an end date.
If room reservation data is displayed, this date represents the date of the business event.
Supplementary Documentation - BEGDATUM 7003
Use
Start of event.
When events are rebooked and copied, the new start date for the period of the rebooked or copied event is specified here.
Procedure
Examples
24.09.2015
Dependencies
Supplementary Documentation - BEGDATUM 7004
Use
Start of selection period for events.
Procedure
Examples
24.09.2015
Dependencies
Supplementary Documentation - BEGDATUM 7005
Use
Date from which equipment should be available.
Procedure
Examples
Dependencies
Supplementary Documentation - BEGDATUM 7661
Use
Start date for potential controlling.
This field indicates the date from which a piece of data is valid. The parameter defines the point in time from which potential controlling has to be carried out, i.e. this is the way in which the selection period for potentials is defined:
Parameter <= Selection period <= Key date
Procedure
Examples
Dependencies
Supplementary Documentation - BEGDA_RP 0001
Use
Only such records whose posting date is between this date and the selection end date are selected for the update
This posting date is P2010-BEGDA or P2002-BEGDA, for example. If this entry is not made, 01/01/0000 is set.
Procedure
Examples
Dependencies
Supplementary Documentation - BEGDA_RP 0002
Use
By specifying the start date and the end date, you determine a period. The time events of the period are displayed.
Procedure
Examples
Dependencies
Supplementary Documentation - BEGDA_RP 0003
Use
The date you enter in this field determines the minimum period for recalculation. If you do not make an entry in this field, the first day of the recalculation is determined automatically according to the data saved for every personnel number.
Procedure
Examples
Dependencies
Supplementary Documentation - BEGDA_RP 0004
Use
Enter the date on which time evaluation must end in this field. If you do not make an entry, the system sets the current date.
Procedure
Examples
Dependencies
Supplementary Documentation - BEGDA_RP 0005
Use
The system updates only records whose posting date is between the selection start date and the date specified in this field. If you do not make an entry, the end date is set to 12/31/9999.
Procedure
Examples
Dependencies
Supplementary Documentation - BEGDA_RP 0006
Use
If you enter a date in the 'Error before' field, the system displays only those personnel numbers with errors before this date.
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 19980909 |
| SAP Release Created in |
