Automatic Benefit Plans based on Date Types in IT0041

Hi
I am having an issue with a re-hired employee. We have two date types in IT0041. Current Hire date and Service Award Date. If somebody is hired for 1st time, both the date types are same( e.g 12/12/2008). and this case the automatic benefit plans follow the config rules properly and some start from the hire date and some from the 1st of following month as per the config ruel.
But If we are re-hiring an employee, in this case Current Hire date( 12/12/2008) would be different from Service award date ( because of his previous experience with this employer). In this case all the automatic plans are starting from the date when the re-hire action is performed, not even the re-hire date and do not follow the config rule at all.
We have never made any dependency of benefit plan on IT0041 anywhere in config, but why this is happening? Any suggestion would be appreciated,
Thanks
Wills

Nope. we never configured the dynamic eligibility part. So that makes it more strange. Because if all the date are same it works fine , but if the dates are different, it gives wrong result

Similar Messages

  • Defaulting Date Types in IT0041

    Hi All,
    I have a issue in defaulting Date Types in IT0041,
    There is a feature DATAR for defaulting Date Types in IT0041. When I create new IT0041 by PA30, values from feature DATAR is getting defaulted.
    But, when i run Hiring Action and at that time vaules from feature DATAR is not being called, its defaulting some other date types.
    Is there any other place where Date Types are defaulted?
    Please let me know if you want any more information
    With Regards
    Shyam

    Hi All,
    Current problem is rectified,
    Solution : I have used INSS instead of INS. In this case values from DATAR is getting defaulted
    New issue is there,
    Some dynamic action is automatically updating with Date Types those which are not there in DATAR. I dont know from where these values are being picked....
    I will continued my research and let you guys know the status.
    I request others to share their thoughts..
    Regards
    Shyam V

  • Default date type for IT0041 in action

    Hi,
    I configure feature DATAR to set 01 as default date type for IT0041, but when I do hiring action, default date type will be 01,02,12.
    Don't know where to change the default.

    Hi,
    Please verify if there is any dynamic action in table V_T588Z set-up for same which may cause override over default.
    Also, verify if your DATAR feature is set up correctly for relevant country grouping and activated.
    Thanks,
    Ameet

  • User exit for adding more date types into IT0041

    Hi all,
    I have a requirement where in HCM infotype IT0041 I need to add couple more custom date types besides standard date types in IT0041. So if I use user exit, what are the steps to do this? what enhancement name should be used?
    Thanks,

    Ben - Unfortunately I haven't implemented a BAdI as I do more functional work.  I found a few documents on line that may help (gotta love Google!).  Maybe someone on SDN who is more technical can provide additional information.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0456c54-0901-0010-f0b3-cd765fb99702?quicklink=index&overridelayout=true
    http://sapient.wordpress.com/2007/05/25/implementing-business-add-ins-badi/
    http://it.toolbox.com/wiki/index.php/Document_on_BADI#BADI_Implementation
    Good luck!
    Thanks,
    Danialle

  • Planning Reverse Fails: "Data Type" dimension

    One of my colleagues received the following error message in ODI when attempting to reverse a Planning application:
    org.apache.bsf.BSFException: exception from Jython:
    Traceback (innermost last):
    File "<string>", line 41, in ?
    com.hyperion.odi.common.ODIHAppException: Failed to import the models into ODI repository.      at com.hyperion.odi.common.ODIModelImporter.importModels(Unknown Source)      at sun.reflect.GeneratedMethodAccessor37.invoke(Unknown Source)      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)      at java.lang.reflect.Method.invoke(Method.java:585)      at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java)      at org.python.core.PyMethod.__call__(PyMethod.java)      at org.python.core.PyObject.__call__(PyObject.java)      at org.python.core.PyInstance.invoke(PyInstance.java)      at org.python.pycode._pyx18.f$0(<string>:41)      at org.python.pycode._pyx18.call_function(<string>)      at org.python.core.PyTableCode.call(PyTableCode.java)      at org.python.core.PyCode.call(PyCode.java)      at org.python.core.Py.runCode(Py.java)      at org.python.core.Py.exec(Py.java)      at org.python.util.PythonInterpreter.exec(PythonInterpreter.java)      at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:144)      at com.sunopsis.dwg.codeinterpretor.k.a(k.java)      at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)      at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)      at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)      at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)      at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)      at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)      at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)      at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)      at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)      at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)      at com.sunopsis.dwg.cmd.e.i(e.java)      at com.sunopsis.dwg.cmd.h.y(h.java)      at com.sunopsis.dwg.cmd.e.run(e.java)      at java.lang.Thread.run(Thread.java:595) Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_REV_COL'. Cannot insert duplicate key in object 'dbo.SNP_REV_COL'.      at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:196)      at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1454)      at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:388)      at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:338)      at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4026)      at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1416)      at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:185)      at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:160)      at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate(SQLServerPreparedStatement.java:306)      at com.hyperion.odi.common.ODIModelImporter.importTable(Unknown Source)      ... 31 more
    com.hyperion.odi.common.ODIHAppException: com.hyperion.odi.common.ODIHAppException: Failed to import the models into ODI repository.
         at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
         at com.sunopsis.dwg.codeinterpretor.k.a(k.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
         at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
         at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
         at com.sunopsis.dwg.cmd.e.i(e.java)
         at com.sunopsis.dwg.cmd.h.y(h.java)
         at com.sunopsis.dwg.cmd.e.run(e.java)
         at java.lang.Thread.run(Thread.java:595)
    After spending time with Oracle support we were told that the reason why it would continually error out was due to a dimension named "Data Type". This is apparently a reserved word in ODI, and affects only the Planning reverse (not Essbase). After renaming the dimension to Data_Type, the Planning reverse worked fine. We have also been told that Essbase reverses are not affected by this issue. Has anyone seen this before?
    FYI - the environment includes ODI 10.1.3.5.0 and Planning 11.1.1.3 as well as Essbase 11.1.1.3. We have recommended that they patch ODI to at least 10.1.3.5.5.

    Thank you - this is very helpful. I was getting the same error when trying to reverse the planning application.
    Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_REV_COL'. Cannot insert duplicate key in object 'dbo.SNP_REV_COL'.
    Low and behold, there is a dimension in the planning application I am trying to migrate called "Data Type". I haven't changed the name in the HSP_OBJECTS table yet to see if it resolves the issue when I attempt the reverse again but looks to be the same problem.
    Thanks,
    Chris

  • Medicare Benefit Plan - storing related data in Infotypes

    We want to send a medical plan interface (HIPAA 834) to one of our vendors and it is a Medicare plan.  There is specific information required that is currently not stored in SAP, such as the HICN, date of enrollment in Medicare A/B, ESRD indicator, signature dates.  Does anyone have experience with storing this information on a specific infotype?  For the HICN and ESRD, I think it has to be on IT0021 for the dependent and 0002 for the retiree.  For the specific medicare dates, I was thinking on the plan itself 0167. 
    Thank you,
    Martha

    The issue is reolved.
    VG

  • User Exit QAAT0001 to select insp. plan based on movement type during stock

    Hello,
    I am have a scenario mentioned in subjectline and would be thankful if somebody can share some detail about it.
    I created one more Inspection type Z1 apart from 08. Assigned it to insp. origin 08 as variant 03.
    Created Z1 usage that i am using in my inspection plan. Assigned 08 and Z1 inspection types in material master and two insp. plans with usage 08 and Z1.
    Now wanted to use user exit QAAT0001to select insp. plan. It would be a greatr help to me if somebody let me know the steps I am doing are correct and what could be the ABAP CODE for that Exit.
    Thanks in anticipation

    Hi,
    use EXIT_SAPLQAAT_002 under importing parameters ...unser I_TQ32 ...check the values....
    and try to modify E_NO_INSPECTION under exporting parameters .
    Thanks,
    Shailaja Ainala.

  • Automatically open file based on MIME type and file extension

    We have an app that is registered to handle custom MIME type and file extension. This works perfectly on IE and FireFox causing them to download the file to a temp folder and then launch our app associated with MIME type and file extension with command line to the downloaded file. On Safari however this does not work. It opens up a download window and shows that it has downloaded the file with no option to open it.

    hello, you can file a bug on bugzilla.mozilla.org if you want to include your plugin in the plugin finder service...
    [https://wiki.mozilla.org/PFS]

  • Advice needed for using date type in leave quota generation.

    Requirement:   Seniority for quota generation of long service leave must be based on date "02" in IT0041.
    Although all the relevant config has been done using the date type 02, the quota is still being generated based on date type 01. 
    My Question:  What is required to make this scenario work?
    Thanks
    Maureen.

    Validity/Deduction
    Validity:  Valid From = Date type 02 -1Days; Valid To =  Date Type 02 999Months
    Deduction: From = Start of Val +1Day, To =  End of Val +999 Months
    Base Entitlement:
    Rule: 002
    Sequence 001; Seniority = 0 - 5 years; Constant= 5 days; Related to = Accrual period
    Sequence 002; Seniority = 5 - 999 years; Constant=10 days; Related to = Accrual period
    Selection Rules:
    Applicability:  default values
    Accrual Period: Rel to date type = 02; Length = 60 Months
    Base Entitlement: Rule = 002; Key for seniority = For exact day
    Accrual Entitlement: No pro-rata calc
    Transfer time:  Upon accrual
    All fields not mentioned are standard defaults.
    Employee:
    IT0041
    Date Type 01 = 01/09/2005
    Date Type 02 = 06/04/1995
    IT0000
    Current position:  Begda: 01/02/2009 - 31/12/9999
    Previous position:  Begda: 01/03/2008 = 31/01/2009
    Testing by running Time Evaluation till 31/09/2012
    Result:
    5 days accrued on 05/04/2010
    IT2006:  Deduction from = 06/04/2009 To 31/12/9999;  Validity from = 05/04/2009 To 31/12/9999
    Please note I've used different dates in an attempt to clearly illustrate the problem. Hope it doesn't serve to confuse.
    Thanks for the help.

  • Reference data types in interface objects?

    How do you create reference data type based on data type in interface object??

    First create the reference DT1 in IR then create a new data type DT2 and if you want to create a reference to DT1 then in  the editor select Type (3rd coloum) as the DT1 which you can get by double click on Type and then you select "search help" and select DT1 from the list.
    Cheer's

  • IT0041 - employee with more than 12 date types;

    Has anyone had an instance where an employee has had more than 12 valid Date Types on IT0041?  If so, how did you enter their 13th date type?  We have just created our 12th date type in the table and we will probably be creating a 13th date type in the near future.  We have a number of employees who already use 11 date types and could use the 2 new ones as well.  I tried to create a new Subtype for my new Date Type - but the new Subtype requires that Date Type 01 be entered.  I am not comfortable with having two identical Date Type 01s in IT0041 (one on Subtype 0001 and one on Subtype 0098). 
    Has anyone used more than one Subtype on IT0041?

    Thank you for your responses.  I don't think changing the Time Constraint class is the best solution for our organization.  We did look at that option.  I don't want to have multiple valid records; I want the ability to have more than 12 date types (values) on one record.  Also, if we allow more than one record, SAP forces us to have Date Type 01 on both valid records - I would be concerned that these values may not match, and then Time Eval would bomb. 
    I'm also still curious if anyone has used more than one Subtype on IT0041?  Again, we did try this, but SAP forces a Date Type 01 on both Subtypes.

  • Reg: benefit plan-insurance info type

    hi ,
    when  i am trying with inbound  certain employee data  into sap, some insurance plans gets updated smoothly but some plans not uploaded. when i am working on this error its shows that it purely depend on benefit  salary on insurance coverage tab.
    my question  is  how they determine the benefit salary field of the employee.(certain plans its determined automatically for some plans not)
    regards
    muthuraman.d
    Edited by: muthuraman d on Apr 2, 2010 4:24 PM
    Edited by: muthuraman d on Apr 2, 2010 5:23 PM

    Hi Muthu,
    To answer your question.....how is Benefit Salary (BSAL) determined........
    A Benefit salary wage type BSAL is needed to calculate the annual salary of the employee for calculations required for Benefit Plans. For Coverage levels and salary groups for cost, contribution, credit and other Benefit calculations, BSAL is required.
    This BSAL is estimated by the configuration entries in ITs 0008, 0014, 0015 for the WTs specified in table T539J, for the module (e.g. ANSAL) which has to be assigned to the Benefit salary wage type BSAL in table T511.
    And to know as of which date the records are processed, check this definition:
    [http://help.sap.com/saphelp_46c/helpdata/en/35/28eb87e8aa5570e10000009b38f983/content.htm]
    Hope this helps !!!!
    Kumarpal Jain.

  • Not Able to Load the data type "Non Currency"in Planning accounts dimension

    Dear All,
    We are building Meta data in planning using HAL 9.2 ...while construction of accounts we were able to assign "Currency" Data Type ,but were unable to add the "Non Currency" data types to account members.
    We have mentioned "Non Currency" in the the Data Type Field.
    Thanks in Advance.

    Hi Guys my issue is resolved..... just wanted to let you know that you will need to write "Non-Currency" in the field name in the csv for marking accounts as Non currency data type.

  • Planning 9.3.1 - Date (data type)

    Hi,
    Has anyone used the feature Date data type for an account that is available in planning 9.3.1?
    I am trying to load and/or display it in the form and i keep getting invalid entry as an error even though i have made the account of Date data tpye and set format for date in user preferences.
    Any help is appreciated.
    Thanks,
    Sri

    Hi Sri
    We had issues getting Date data type to work if we wanted to use standard UK date format (DD/MM/YYYY). However, it does seem to work fine if we use American date format (MM/DD/YYYY).
    Not sure if this is a bug?
    The date setting is on the Administration > Application Settings menu, choose Application Defaults and then Display Options to find the place that this is set. It is also manageable on individual users Preferences that is found using File > Preferences > Display Options.
    Hope that this helps
    Stuart Game
    www.analitica.co.uk

  • Issue with Data type 'Date' in Hyperion Planning V11.1.2.2

    Hi,
    I have created members with data type date. However when I save the date, it either disappears or comes up with a random date? Has any one come across this kind of problem before?
    If so can you share the fix.
    Thanks in advance for your help.
    Cheers,
    XXX

    Hi
    This problem is linked to you not having a consistent setting for your date input type.
    So, go to application administration and set the date format to MM/DD/YYYY in application settings and display options, under current application defaults. Then after you have done this as a user go to User Preferences and display options and on the date format select the same. Or remove the Automatically detect.
    I have seen this behaviour if you have Automatically Detect on the user preferences
    Thanks
    Anthony

Maybe you are looking for