Time management status and Payroll

Experts,
   We are using TMS as 9 (Time evaluation of planned time) in IT0007. What does it mean in TM?
   What is it's impact in Payroll.
Regards
Sk
Edited by: s k on Nov 17, 2008 10:24 AM

You can assign the following Time Management statuses in the Planned Working Time infotype (0007):
Time evaluation with planned times (0): Employees with this status are not selected for time evaluation. They cannot therefore be processed in time evaluation. The employeeu2019s time wage types are determined in Payroll time data processing.
Time Management Status for processing time data in Time Evaluation and passing on time wage types formed there to Payroll
Time evaluation of actual times (1) and Time Evaluation PDC (2): Employees with these statuses have all their actual times, that is, all attendance and absence data, recorded*. It makes no difference whether attendance times are recorded at time recording terminals or in the Attendances infotype (2002).
Time evaluation with planned times (9): These employees have only the deviations from their work schedule recorded for them. The employeesu2019 planned working times from their personal work schedule are used as the basis for time evaluation.
Time Management Status for processing time data in Time Evaluation without passing on time wage types formed there to Payroll
Time evaluation without integration with Payroll (7): You use this status to run time evaluation to handle special time accounts u2013 to accrue absence quotas, for example. It makes no difference whether all of the employeesu2019 actual times are recorded or only the deviations from the work schedule.
The system stores the results of this time evaluation run in cluster B2, which enables you to run reports on the data, for example. The results are not passed on to Payroll. The time data processing part of Payroll treats the employees as if they had the time management status No time evaluation (0).
External services (8): Status for external employees. It makes no difference whether all of the employeesu2019 actual times are recorded or only the deviations from the work schedule. The results of time evaluation are transferred to Materials Management (MM-SRV), and are not passed on to
and also check the feature TMSTA once  in peo3
Edited by: Sikindar on Nov 17, 2008 3:01 PM

Similar Messages

  • Time management status "0"and "7"

    Hi Team,
    Kindly can you let me if we  can use Time management status "7" when there is no TE instead of "0"?
    My client is using "7" as Time management status and they don't have TE.
    Regards,
    Vimal

    Hi Vimal,
    The Time Management Status plays an importnat and effets as to how u want the time Process in ur company.
    Time Management Staus 0 : No time Evaluation which means no PT60 or RPTIME00 all u have to do is run The Quotas with the report RPTQTA00 if any.
    And Time Management 7 is Time Evaluation without Payroll integration.But u said that u dont have Time Evaluation then why 7? It should be 0 but the other possibilty to have Time Management Status 7 is you can use RPTIME00 with schema TQTA for generation of time quota and that is without time evaluation.
    So its better to have TMSTA 7 as u can use RPTQTA00 and RPTIME00 with TQTA both for generation of time quota.
    Regards
    Swati

  • Query on Time Management Status

    Dear Team,
    Scenario:
    We have some employees wherein the time evaluation will be evaluated for the status of 9 in Planned Working Time Infotype. After a period of time, these employees will be sent for education and no leaves are entitled. In this case, the time management status will be changed to 0. No time evaluation.
    The accrued leaves will still be available for the employee while going to this education for example 20 days.
    We have customized a rule, which will carry forward the last year balance to the current year balance on every 1st of the year.
    In the above case, if an employee completes his education and returns back in the middle of the year other than the 1st day of the year, in this case, the carry forward of leave is not taking place.
    My assumptions:
    I would like to know an operation which would query the Previous Day Time Management Status and Current Day Time Management Status. If I can able to do this, if it is YES, the last old previous balance to be carried forward....
    Please let me know if any other alternative method.
    Thanks and Regards
    Team Member.
    Edited by: Patlolla Mallikarjun on Apr 26, 2010 8:35 PM

    Hello Mallikarjun,
    If you are planning on controlling thru a rule in schema, you can approach this way. Whenever an EE returns from education, change IT0007 time mgmt status to 9 along with additional time indicator say 'ED'. You can query the additional time indicator status in a rule thru the operation 'OUTWPATIND'. Hope this helps your requirement.
    Best Regards,
    Sunny

  • Waht does time management status 0 without payroll integration mean

    In our project, the client does not want to use time evaluation and so, we have set the time management status value as 0 (no time evaluation). Also, the client is not implementing (at least now) SAP-Payroll, as they are processing payroll through a different software. We have configured work schedules ( they need just 4 different work schedules) and assigned appropriate ork schedules to all employees in infotype 0007. We have also configured one absence quota (Earned Leave of 20 days per year).
    My query is how will the system behave now with time management status value as 0? Can we process absence quotas? What is the use of work schedules, in this context, as any way the system does not evaluate employee time in Time Management. Neither the time wage types are evaluted in Payroll, as SAP Payroll is not implemented.
    -Shambhvi

    My thanks to all of you. I would like to summarize the answer for my query:
    Since time management status = 0, there won't be any time evaluation, which means attendance and absence data, even if entered won't be evaluated in Time Management. Since Payroll is not implemented, the question of time data getting evaluated in Payroll does not exist. However, absence quotas can be maintained, irrespective of the value of time managment status.
    Please correct me, if my understanding is wrong
    -Shambhvi

  • Time Management Status 7 without Payroll Integration.

    Dear All,
    when do we go about Time Management Status - 7 - without Payroll Integration.
    In this case how the process goes on SAP. what do we do in this status. do we record employees attendances in 2002 IT
    actually what happens.
    Regards
    kvn

    Hi KVN,
    You are using time management status 7 which means that no integration to payroll.Now as far as ur Quotas are considered then please use RPTQTA00 which is just a program and RPTIME00 or PT60 which will run time evaluation and if u want your Quotas to generate in time evaluation then just change V_556A_B in this table to increase so with time evaluation and no generation for Quotas to be with time evaluation.
    The client may ask sometimes for few Quotas to be prorated on a daily basis and so on in that case go with TE Quota generation
    else RPTQTA00 is ok.So see ur business and use either of it
    Let me know if u have any further Questions.
    Thanks
    Swati

  • Time management status  doubt

    Hi Friends,
    what is the difference between time management status 0 and 9. when we can use 0 and 9.
    Thanks in advance
    Venkat

    Hi,
    Time management status  0  means - Employee's actual times are not recorded, and his/her time data is not accounted using the time evalulation program. here the time wgetypes are formed by payroll.
    Time management status  9  means - Employees for whom only exceptions to the work schedule are recorded. In this case, the employees' actual times are not recorded, but they do participate in time evaluation.ie (.Evaluation of planned times.)
    Hope this will help
    Manoj.

  • Change Time Management status

    Hi All,
    We have presently uploaded all the employes in the system with Time management status - zero.  We would like to change the status from zero to 7 now.
    Please suggest me the best possible way to achieve this. Total employees in the system are close to 70k.
    Thanks,
    Binu

    Hey Binu,
    As Rashid said correctly, TMSTA feature is used to default Time Management Status i.e when you create or change then it will default the TMSTA value. Its of no use to you.
    I would recommend BDC method because for LSMW you will have to create a file and upload it.
    Write the BDC using below logic.
    1. Select the Active employees using PA0001-PERSK = 1.
    2. Change (MOD) the TMSTA of IT 0007 to your requirement
    Selection screen can have employee numbers.
    Ask you ABAPer to record the screen using SHDB for changing the IT 0007 i.e
    1. PA30 - select your EE - IT 0007 - Change
    2. On IT 0007 you change TMSTA and SAVE
    IT should be done in no time.
    cheers
    Ajay

  • Infotype 0007:Time management status

    Hi Experts,
    In Infotype 0007 , in the time management status field i have maintained the value as " Time Evaluation of planned times".
    What does this mean ? ....
    Does it mean that absences and attendences are not necessary to create. Kindly help me how the evaluation takes places
    in this scenario.
    Thanks in Advance,
    Balaji

    Hi,
    This is SAP explanation:
    Indicator 0 or BLANK:
    The employee's actual times are not recorded, and his/her time data is not accounted using the time evalulation program.
    Indicator 1:
    The employee's actual times are recorded and he/she participates in time evaluation.
    Example:
    The employee's actual times are recorded at a time recording terminal.
    The employee's actual times are recorded in the Attendances infotype (2002).
    Indicator 2:
    Employees' actual times are recorded and they take part in plant data collection. Their time data is accounted using the time evaluation program.
    Example:
    Employees' actual times are recorded using PDC systems.
    Employees' actual times are recorded in the Attendances infotype (2002).
    Indicator 8:
    This indicator is intended for external employees. The employee's actual times are not recorded, attendances are recorded in the Attendances infotype (2002), and time data is accounted in time evaluation.
    Indicator 9:
    You can use indicator 9 for employees for whom only exceptions to the work schedule are recorded. In this case, the employees' actual times are not recorded, but they do participate in time evaluation.
    Cheers

  • Time Management Status

    Hi Experts,
    Im relatively new to this fourm, and also to Time Management Module.
    We are implementing Negative Time Management for our client.
    Have a clarification with Time Management Status.
    I have suggested '0' to be defaulted as it is going to be Negative time management.
    Just for my understanding would like to know the difference between the time management status 0, 7 & 9.
    Also we have LWOP and Holiday Wages in place.
    your expert answers awaited...
    Cheers,
    Sri...

    Indicator 0 or BLANK:
    The employee's actual times are not recorded, and his/her time data is not accounted using the time evalulation program.
    Indicator 1:
    The employee's actual times are recorded and he/she participates in time evaluation.
    Example:
    The employee's actual times are recorded at a time recording terminal.
    The employee's actual times are recorded in the Attendances infotype (2002).
    Indicator 2:
    Employees' actual times are recorded and they take part in plant data collection. Their time data is accounted using the time evaluation program.
    Example:
    Employees' actual times are recorded using PDC systems.
    Employees' actual times are recorded in the Attendances infotype (2002).
    Indicator 8:
    This indicator is intended for external employees. The employee's actual times are not recorded, attendances are recorded in the Attendances infotype (2002), and time data is accounted in time evaluation.
    Indicator 9:
    You can use indicator 9 for employees for whom only exceptions to the work schedule are recorded. In this case, the employees' actual times are not recorded, but they do participate in time evaluation.
    I hope it helps you!!!
    CheerS!!

  • Time Management Status Default

    Hi All - Prior to employees being onboarded we enter an 'Initial Hire' action that creates a few infotypes for them including IT0007 (Planned Working Time). The business wants the Time Management Status to default on IT0007. However, we can't default it in TMSTA because they are set up with the same PA/PSA/EG/ESG as they are during their 'Completed Hire' action. We are attempting to default this in dynamic actions but have been unsuccessful (see below). Does anyone have any suggestions?
    0000 6 423 P PSPAR-MASSN='ZA'
    0000 6 425 W P0007-ZTERF= '0'

    Hi,
    You need the insert statement too. Try this:
    0000 6 423 P PSPAR-MASSN='ZA'
    0000 6 425 I INS,0007,,,(P0000-BEGDA),(P0000-ENDDA)
    0000 6 427 W P0007-ZTERF= '0'
    Feature TMSTA information:
    It uses structure PME01 and that only contains action reason (MASSG), so you could build your decision tree based on action reason. You may want to have a unique reason code tied only to your ZA action. Iu2019d imagine you would only have one reason code for this initial entry action as it is only for a temporary use.
    Alternatively, you can change the structure of feature TMSTA from PME01 to PME04. You would then have action (MASSN) and action reason (MASSG) available for building the feature.
    Hope this helps.
    Donnie

  • Time management status for Negative time management

    Hi,
    what time management status has to be maintained in 0007 for negative time management
    regards
    bala

    Its
    9 - Time Evaluation of Planned times
    cheers
    Ajay

  • Document on Positive Time Management & Integration with payroll

    Hi,
    Can any one suggest me any link from where I will get the IMG steps of Positive time management implemetation, time evaluation, time wagetype detail as well as the steps of integration with payroll..
    Thanks in advance.
    Ajay

    Hi Chandrashekar,
    Can you please advise how actually the transfer of clock times from time recording terminals to SAP R/3 will work?
    I read from help.sap.com that there is a SAP certified CC1 interface (BAPI based) which can be used for this purpose. However, in such a case, the time recording terminals should be SAP CC1 certified.
    If the time recording terminals are not SAP CC1 certified, then what is the method to be used? Will we write a custom BDC program in this scenario and what all should be considered in functional specification of such a BDC program.
    Please advise.
    Thanks and warm regards,
    Vianshu

  • Time management doubts and orientation

    Hi experts!
    I'm trying to customize the Time Management module in SAP. At the moment we only have running the Personnel Administration and Payroll modules.
    We would like customized the time management modules with this requirements:
    -Employees will have Planned Working Time. This working Time will be theroical.
    -Every day employee goes to work and for every thay each employ will have a record with the real time entrance and real time output.
    -We want compare the theorical time with the real time and in some cases maybe the delayed time should be descounted of the amount in payroll, only in some cases if manager thinks so. Otherwise not should be discounted.
    Therefor we have some doubts:
    -After customizing the time management module how we should set the infotype 0007-Planned Working Time?
    -In some place I have read something about positive and negative time recording. I think we should use the negative time recording, do you think it's correct?
    -What we should change on the payroll schema if we want discount the delayed or not allowed absences?
    -We need customized the time evaluation schema or it is not necessary because we will use negative time recording?
    Do you know where I can find more documentation to help me?
    Kind regards,
    Julian.

    Please use Help portal provided by sap as well  go through  every node of Time management in SPRO
    http://help.sap.com/saphelp_erp2004/helpdata/en/3a/ec0fc8dd7811d396fb00a0c930669b/frameset.htm
    or please check the best practice document from this link ( some time it required user name and password)
    http://help.sap.com/bp_hcm604/HCM_US/HTML/Content_Library_HCM_EN_US.htm

  • PLM7.02: Status & Release Management/ Status and Action Management

    Hello,
                    I´d like to know if anybody worked with Status & Release Management. And has some example to how we can customize: SAM (Status and Action Management) in “Define Status Scheme” transaction.
                    How it´s works the relationship with: Status: Attributes, Status: Field values, Scheme Definition, Attributes: Definition.
                    I´ll appreciated if you could give me a simple example of this functionality.
                    Thanks in advance.
                    Best Regards from Brazil.
                    Rodrigo Arai

    Hi Rodrigo,
    in a nutshell:
    - you can define status network based on objects (w.g. material)
    - Define Attributes: you can define attributes like DELETION_ALLOWED or LOCKED_FOR_CHANGE and you can implement preconditions in custom classes when should it happen
    - Define Status Field: you can define some fields which are related to the status. e.g. in recipe management RCP_USAGE
    - Status: you can define the different statuses (e.g. in process, completed..) with attributes
    - Scheme Definition: you can define the logic between statuses. E.g. you would like to swith from status In Process to Completed and from New to In Process. Then switching from New to Completed is not possible for the user.
    - Subobject Type Scheme only applied if you have subobjects
    here you can find the customizing documentation, there are some examples as well:
    Define Status Scheme
    Use
    In this Customizing activity, you define statuses and status schemes for object types and corresponding attributes.
    For each status, you can define which attributes are allowed to be set for an object with this status assigned.
    The status scheme defines the initial status and the possible transitions from one status to another.
    Activities
    You define status schemes as follows:
    1. Select the required object type and enter the following:
    a) An identifier
    b) An object type class (Note: this class should implement the interface class)
    c) A subobject type search help
    The search help provides a list of all possible subobject types. This feature enhances the usability while  maintaining status schemes at subobject-type level.
    d) If the
    Status
    tab page shall be visible on the PLM Web UI, select the
    Status Tab
    checkbox
    Status and action management is a reusable object. It has been modeled as a dependent object. The prerequisites to enable status and action management for any new objects are:
    Add the Status and Action Management tab page on the UI.
    Enable the Status Tab checkbox in this Customizing activity.
    2. Select the required object type and define the following attributes for it:
    a) An object type
    b) An attribute identifier
    c) An attribute description
    d) An attribute type
    e) Select a precondition class (Note: This class should implement the '/PLMB/IF_SAM_PRECONDITION' interface)
    3. Define the technical status field name.
    When you change the object status, the system updates the technical status field names to the new values made in these settings.
    4. Select object type and define corresponding statuses.
    a) Select the status and define the corresponding object type, an identifier, description, and status icon.
    Note:
    You cannot define new statuses for materials and material BOMs. For these objects, all values should be transferred from the back-end system.
    You can import the status values from the back-end system as follows:
    b) Select the object type that represents a material or a MatBOM.
    c) Select
    Status
    in the dialog structure.
    d) Choose the
    New Entries
    pushbutton.
    e) Choose the
    Import Status
    pushbutton.
    Note
    The system imports the following status values into SAM:
    For material: the
    X-plant matl status
    (cross-plant material status)
    For MatBOM: the header status
    Although you cannot change the imported value for a material or a MatBOM, you can change its name and description to conform to SAM terminology.
    You can differentiate between the following cases for objects whose status values are imported from the back-end system:
    The object was not created on the PLM Web UI, but in the back-end system; no SAM status scheme or status was assigned, but a status value was set in the back-end system.
    If you assign a SAM status scheme to this object later on that contains the equivalent imported status values, the SAM status value is set accordingly, even if any precondition check results of the SAM status scheme may exist.
    The object was created in the back-end system or on the Web UI and a SAM status scheme is assigned to the object on the PLM Web UI.
    If the corresponding status value is changed in the back-end system, then existing SAM preconditions for this status transition and allowed status transitions are checked. If the preconditions are not fulfilled, a message is raised and the new status cannot be saved.
    5. Specify which attributes are allowed for each object type when the chosen status is set.
    a) Select a status and open the
    Attributes
    screen.
    b) Choose an object type.
    c) Choose an attribute.
    6. Define whether values from other technical fields are affected by setting this status.
    a) Select a status and open the
    Field Values
    screen.
    b) Select an object type.
    c) Select a technical field name.
    7. Specify the status scheme. The status scheme defines the initial status and status transition for the object type. For example, below is a list of standard status schemes defined for iPPE object types.
    Assembly Header - PLM_PPEAH
    Assembly Item - PLM_PPEAI
    Product Item Variant - PLM_PPEPIV
    Product Variant - PLM_PPEPV
    You can also create schemes for the object type as follows:
    a) Specify an identifier and description for the status scheme and set one of the statuses defined above as the initial status.
    b) Select the status scheme and open the
    Transitions
    screen. Enter all possible status transitions by specifying the source (
    Status From
    ) and target status (
    Status To
    c) Select the
    Long Text
    checkbox if you want the system to open the long text editor on the
    Status
    tab in the PLM Web UI. You can use the long text editor to create notes for this transition.
    8. Define the scheme at subobject-type level by entering following parameters:
    a) Object type
    b) Subobject type (You can choose from the list of subobject types you have specified when defining the search help in step 1)
    Alternatively, you can define a default status scheme that is automatically displayed on the
    Status
    tab.
    The following statuses are included in the standard delivery:
    10 -  In Work
    20 - For Approval
    LINKED_DIR
    LINKED_MAT
    LOCKED_FOR_CHANGE
    REPLACE_PH_ASSEMBLY (only in the PLM_PPEAI assembly item and the PLM_PPEPIV product item variant)
    30 - Released For Planning
    LOCKED_FOR_CHANGE
    40 - Released
    RELEASED
    SUB_ITEM_STATUS
    The following status transitions are possible:
    FROM
    TO
    Long Text checkbox (dialog box for notes)
    10
    20
    20
    30
    30
    40
    20
    40
    20
    10
    X
    30
    10
    X
    40
    10
    X
    More on SAP help:
    Status and Action Management on the Web UI - SAP Library
    Best regards
    Tamas

  • Virtual Connect Manager Status and Stacking Link Error

    I have three C7000 Enclosures / chassis running on each environment, each chassis have a redundant VC (Flex-10 Enet) bay 1-2 and ( 8Gb 24-Port FC ) Bay3-4, everything seem working but there is a Domain status and stacking link errors "One or more of a domain's subsystems are not properly operating, causing serious impact to domain functions." and "Some VC-Enet modules are not properly connected via stacking links please verify stacking cable connections"

    Sorry, but your question is far beyond the intended scope of the Global Consumer support forum.  I suggest posting this to the HP Enterprise business forum.
    ****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
    2015 Microsoft MVP - Windows Experience Consumer

Maybe you are looking for