SAP Time Constraint in HR Infotypes

Time Constraint Value

1 = Record must have no gaps, no overlappings
2 = Record may include gaps, no overlappings
3 = Record may include gaps, can exist more than once
A = Infotype exists just once from Jan.1 1800 to Dec.12 9999
B = IT exists for maximum of once from Jan.1 1800 to Dec.12 9999
T = Time constraint is based on subtype or subtype table
Z = Time constraint for time management infotypes -> T554Y

Time Constraint Definition
A time constraint indicates whether more than one infotype record may be available at one time. The following time constraint indicators are permissible:

1 = An infotype record must be available at all times. This record may have no time gaps. You may not delete the record last stored on the database because all records of this infotype would otherwise be deleted.
2 = Only one record may be available at one time, but time gaps are permitted.
3 = Any number of records may be valid at one time, and time gaps are permitted.

Other possible time constraint indicators are as follows:

A = Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.
View V_T582B Infotypes Which are Created Automically controls whether the system automatically creates the infotype record for an employee hiring or an applicant data entry action.
Infotypes with time constraintA may not be deleted.

B = Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.
Infotypes with time constraint B may be deleted.

T = The time constraint varies depending on the subtype.
Z: Refers to time management infotypes. The time constraint for these infotypes depends on the time constraint class defined in view V_T554S_I Absence: General Control. Collision checks are defined in view V_T554Y Time Constraint Reaction.

The Concept of Collision Checks

When you enter a new record, the system carries out a check to ensure that there are no contradictory records for that particular employee and time period.

It is not possible, for example, to enter an absence record if there is already an attendance record in the system for the same employee and time period.

When you customize the system, you can determine the system reaction if time data records collide. There are four possible reactions:

    1. An employee is on Leave from Monday to Friday, but is required to interrupt the vacation and return to work on Wednesday.
    2. System reaction:

      When you enter this data for the attendance type Attendance hours, the system draws your attention to the fact that a leave record already exists for the period. The leave record is automatically delimited if you proceed to save the attendance record.

    3. You try to enter a Substitution record for an employee who is on leave.
    4. System reaction:

      The system does not allow this particular constellation, as it is not logical to assign a substitution to an employee who is not at work. An error message is displayed and the system rejects the record.

    5. You try to enter substitution data for an employee who already has an overtime record for the same day.
    6. System reaction:

      This combination is in fact permitted. Overtime and substitution records are not mutually exclusive. The substitution may involve the employee working different hours from normal, however. If this is the case, it may be that the new working time coincides with the period in which the employee is authorized to work overtime.
      It is therefore preferable that the system draws your attention to the collision so that you can check your entries.

    7. An employee is assigned to work a substitution, which involves longer hours than usual. You try to record the absence quota Time off for overtime.

System reaction:

This constellation is allowed, since substitutions and absence quotas are not mutually exclusive. There is no time correlation between these two subtypes. The system therefore accepts the absence quota without drawing your attention to the existing substitution record.

10 Responses to “SAP Time Constraint in HR Infotypes”

  1. boaz Says:

    Happy Birthday pak Harry…
    semoga sukses terus dan tercapai segala cita-citanya…
    Amin…

  2. harrypoe Says:

    Makasih ya Boaz🙂
    Sukses selalu dan salam buat keluarga.

  3. aRi Says:

    Wah… ulang taun yah…
    Selamat ulang taun ya…😀
    Panjang umurnya & semoga sukses selalu …

  4. Anonime Says:

    Karena komentar untuk Gross Up PPH sudah ditutup, maka saya komentar di sini saja. Maaf sebelumnya.

    Ternyata rumus untuk menghitung grossup tersebut bermasalah untuk contoh berikut :
    Gaji sebulan 2,100,000
    Status Tidak Kawin
    Tidak ada pengurang untuk gaji.

    Hasil yg diperoleh dengan menerapkan rumus adalah 47,105
    Jika dihitung kembali setelah dapat tunjangan pajak sebesar 47,105 ternyata potongan pajak adalah 46,987.
    Jadi ada selisih antara tunjangan pajak dengan potongan pajak.

  5. harrypoe Says:

    Mungkin lebih enaknya kalo bisa dijelaskan bagaimana cara pak anonime menghitung besaran tunjangan pajak nya, jadi kita bisa membahasnya bersama.

  6. harrypoe Says:

    Makasih ya Rie..wah dah lama nih kita semua gag ngumpul..he..he

  7. Anonime Says:

    Saya mengikuti rumus yang ada dalam tulisan tsb,
    sebagai berikut. Mungkin saya salah menerapkan ?

    Gaji 2,100,000
    Gaji setahun 25,200,000
    PTKP 13,200,000 (TK)
    Biaya Jabatan 1,260,000 didapat dari Gaji setahun * 0.05
    PKP 10,740,000
    Pph 565,263 didapat dari PKP kali 0.05
    Pph/12 47,105

    Untuk mengujinya, dihitung sebagai berikut :

    Gaji 2,147,105 ini gaji setelah dapat tunjangan pajak melalui perhitungan di atas
    Gaji setahun 25,765,263
    PTKP 13,200,000 (TK)
    Biaya Jabatan 1,288,263 didapat dari Gaji setahun * 0.05
    PKP 11,277,000
    Pph 563,850 didapat dari PKP kali 0.05
    Pph/12 46,988

    Begitu perhitungannya.

  8. anieta Says:

    Hi Harry,

    Kenalkan saya Anieta. Syarikat kami membutuhkan SAP specialists dalam semua module.
    Moga Bapak bisa melanjutkan tawaran kerja ini kepada rakan-rakan yang ingin bekerja di Kuala Lumpur, Malaysia.

    Sekian.
    Terima kasih.

  9. harrypoe Says:

    Hi Anieta,
    Terimakasih atas infonya. Untuk lebih detilnya bisa dikirimkan ke alamat email saya: ih_poerno@yahoo.com

    Thx & Rgrds,
    Harry Poernomo

  10. ria Says:

    hi
    bisa tolongin aku gak

    aku pake rumus tunjangan pajak itu untuk skripsiku

    dosenku minta rumus tersebut dijelaskan dari mana asalnya

    yang perhitungan cepat bisa tolong dijelaskan

    Thanks


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: