Incorrect Coverage Start Dates

During Open Enrollment, there was an error in our set ups for our STD plan and now several employees have incorrect coverage start dates and incorrect original enrollment dates for the plan. There are over 1000 employees affected by this error so manually overriding the dates isn't a popular option to fix this problem. Is there an API that might be useful for correcting these dates ? Any other thoughts ?
Thanks in advance for your help !
Jeff

Hi
You can review the below Metalink Note -
*Oracle Human Resources Management Systems (HRMS) Benefits Enrollment Conversion [ID 365034.1*], search '
To Create or Update Enrollments' in the Doc of this Notes.
Please let me know if you face any issue or need any informatoin, will be glad to help you.
HTH
Gaurav

Similar Messages

Enrollment - Coverage Start Date issue

Hi All,
I am facing an issue in Selfservice, where an employee can login to SSHR to insert a life event, process it and make Enrollments.
There is one Life Event - Gain Dependent - Child, when an employee adds a dependent - Child he needs to insert the life event and on Processing it he can makes the enrollments and then save them.
On doing so the Coverage Start Date for the Benefits is coming up as Today's date (assuming if the employee makes enrollments Today).
But keeping the same setup if we Process the Life Event and make Enrollments from Oracle Forms the Coverage Start Date is coming up as 1st of the current Month, which is the actual date that should be coming up as per the Fast Formula logic.
Due to the wrong Coverage Start Date, Rate Start is also getting wrongly popualted and hence employees are losing the Dollars...
Is there any way by which this can be fixed or this is an issue with Selfservice that the what the Logic FF has cannot be used in selfservice.
Anyone having any idea on this, please reply ASAP as this is the Show Stopper issue.
Thanks
Shivam.

Hi Shivam,
You have mentioned previously that Ct. is triggering the Gain Dep. LE by adding a new dependent child. This means that the person already had a life event in started status which enabled the Family Member page and allowed the user to add a dependent.
If so, then there might be a Collapsing Logic defined between the Current LE[Say New Hire or Open] and the Gain Dependent. [I have seen this setup with most of the Ct.'s].
So, there is a good chance that instead of the Gain Dependent, the Current LE will be reprocessed and hence is taking the setup of Current LE instead of GD.
You can confirm the LE processed in the Current Benefits page.
Regards,
Aneesh N

Advanced Benefits:Dependent Coverage Start Date

Hi,
I have a an employee with the following life events.
Intially the Employee has Employee Only Option
1) 28-Feb-2010 -- New Child --> Emp+Children --> Child Cvg Start Date --28-Dec-2010
2) 01-JAN-2011 -- Open --> Emp+ Children --> Emp CVg Start Date -- 01-Jan-2011 and Dep Cvg Start Date 01-jan-2011
3) 01-APr-2011 -- Marriage --> Emp+Family --> The Cvg start date of the Child is Changed to 01-APr-2011 and the Employee CVG start date also changed to 01-apr-2011
I am curious to find why did the child coverage start date changed to 01-APr-2011 and we have added spouse only in the marriage life event and changed the
option from Emp+Children to EMp-Family
Thanks for any input.
regards,
A

Hi Shivam,
You have mentioned previously that Ct. is triggering the Gain Dep. LE by adding a new dependent child. This means that the person already had a life event in started status which enabled the Family Member page and allowed the user to add a dependent.
If so, then there might be a Collapsing Logic defined between the Current LE[Say New Hire or Open] and the Gain Dependent. [I have seen this setup with most of the Ct.'s].
So, there is a good chance that instead of the Gain Dependent, the Current LE will be reprocessed and hence is taking the setup of Current LE instead of GD.
You can confirm the LE processed in the Current Benefits page.
Regards,
Aneesh N

Converting Coverage Start Date during OAB Conversion for current elections

We have a requirement to convert the coverage start date of current elections in the Legacy System to OAB.
We are using 'BEN_ELECTION_INFORMATION.ELECTION_INFORMATION_W' api to convert current enrollments and is passing the actual coverage start date of the current enrollments to the parameter 'p_enrt_cvg_strt_dt' in this API. We have an administrative Life Event configured in OAB for converting the current enrollments with Assigned Life Event date as '29-JUN-2010' . After the Conversion API is executed for all the Enrollment records the coverage Start Date is set to '29-JUN-2010', which is not the requirement.
We also tried using the APIs 'BEN_PRTT_ENRT_RESULT_API.UPDATE_ENROLLMENT' and 'BEN_PRTT_ENRT_RESULT_API.UPDATE_PRTT_ENRT_RESULT', but they behave the same manner as 'the Legacy System to OAB. We are using 'BEN_ELECTION_INFORMATION.ELECTION_INFORMATION_W'.
Please let us know which API would allow us to convert the current elections without changing the actual coverage start date from the Legacy System.

I did run the default enrollment process, but nothing happens. I tried this with the Assign on Default check box checked and unchecked. Here is what I have setup for the enrollment details on this plan:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Program Enrollment Requirements > General > Plan
Method: Automatic
Enrollment: Current, Keep Only; New, Can Choose
Default Enrollment:
- Code: Rule
- Rule: DEV_X
- Assign on Default: Checked
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I removed the eligibility profile from the plan and it will default when running the participation process, however that does not solve the problem. I even rewrote the rule to include plan id, but that did not work either. The employee needs to be enrolled automatically when they select a given plan. Because the person is not eligible for the plan until after they select it, OAB will not know that the person is eligible until the participation process is run.
The only thing I can think is to have a separate life event that triggers at the end of the enrollment period, but I haven't figured how to do that yet. And it still doesn't quite solve the problem completely, as will be the case when enrollments are made after the enrollment period, i.e. corrections.

Suspended coverage start date

Hi All ,
I have a requirement where I have to start the suspended coverage (after certificaton is provided) . The coverge should start from 1st of next month (month after certification is provided) . I tried putting the unsuspended code(First of Month After Completed) in the "Coverage restrictions" screen in "Plan Enrollment requirements" . However is does not work and coverage does not start from 1st of next month .
Can someone please let me know , if I am something here . Any replies are appreciated .
Thanks

Hi,
if it's not first of month, then what is it getting to ?

Plan Enrollment Coverage End date

There is a plan , which has following Enrollment coverage Start date and Coverage end date code resp. ( in Plan enrollment requirements)
Enterable and 1 Day Before Event.
The plan needs to be explicitly enrolled to thru ESS.
There is a reqmt such that when employee enters end date it should be such that only sysdate or later date should be allowed to be entered. So we may need to change the above setup.This has to be acheived in configuration only.
Kindly help.
Thanks,
Sush
Edited by: user10714306 on Aug 14, 2009 6:02 AM

Hi,
To drop the plan off employees, you have to process life event for them. If it's part of the annual process, then the enrollments will drop when the open enrollment is processed. Alternately, you will have to process an "Admin" life event for these employees.
If you are using unrestricted processing, then use admin or open to achieve the same.
IF the changes are just in dev environment, I suggest removing the plan year periods from the plan instead of making it inactive. processing life events is still necessary. Plans made inactive cannot be reverted back and so, should be done as a last resort.
Regards,
Vinayaka

PP DataSource 2LIS_04_P_ARBPL - Incorrect extraction of latest scheduled start dates (SSAVD)

Hi experts,
we use the SAP Business Content Standard DataSource 2LIS_04_P_ARBPL "Work Center View PP" and need the latest scheduled start date each production order operation.
In the production order operation overview (t/code CO03) on the ERP-side we have the expected latest scheduled start (Source AFVGD-SSAVD)
But in the DataSource 2LIS_04_P_ARBPL (PSA-Table) we become the incorrect latest scheduled start dates (DataSource field SSAVD)
Any ideas or experiences why the latest scheduled start date not up-to-date?
Many thanks and best regards,
Michael

Hi,
I have tested the scenario again...
At the header level of test production order 1000381 I have changed the basic dates (Start/End) from 22.04.2014 to 24.04.2014.
As a result the start dates at operation level also changed...
After the above changes I have extracted the Data. The Delta-Queue (RSA7) for the relevant DataSource 2LIS_04_P_ARBPL looks nearly good.
For the both operations 20 and 30 the delta update for the field "Latest start date" (SSAV) works correct. But the delta update for the first operation "10" not processed.
Is it possible that the delta update only works for specific system status? Or any other ideas?
Many thanks and best regards,
Michael

PROCESS CHAIN error "Incorrect start date"

hi sap gurus,
I have parent chain in that a newly created meta chain is creating problem.I am getting error in the process chains since two days i am not able to solve this.Can anybody try to help me.
error: Incorrect start date: 00.00.0000; Start time 00:00:00 RSM 847
After that the process chain is turning red,but when i manually execute the process chain its running properly.
Please help me its urgent.

hi gurus,
Its working fine now.
Solution:
first exchange the variant with the smae and then activate and run.After that it will work in the process chain.
Thanks a lot to every body,especially MOHAN KRISHNA,

Oracle contracts generating incorrect start dates/pricing

Hi,
Oracle contracts generating incorrect start dates/pricing
Semi Annual Invoices being automatically generated with the incorrect start date/pricing.
We have 8 years of pricing instead of 6 yrs. Contracts are being terminated and recreated to correct immediate billing issues.
Please help me out Why Oracle contracts generating incorrect start dates/pricing.
Thanks In Advance,

Which Apps release is this happening in?

Download of incorrect start date using Open PS.

When project is downloaded from R/3 PS to MS Projects, and 'Download actuals' has been set in 'Object type' settings , incorrect start date gets downloaded everytime any project is downloaded.( In this case 30 Nov 99 ).
Have already checked the start date in Project definition in R/3 PS and also the Project information in MS Projects. The source of the incorrect start date remains unknown.

Hi Nidhi
In addition to my earlier reply, pl also check the following:
1. Time Settings
Microsoft Project only supports the following ISO time units: minutes, hours, days, weeks, and as of Microsoft Project 2000, months. If you use other time units in your SAP R/3 projects, you must define conversion factors.
2. .Dates
The project information in Microsoft Project is updated with the information in the project definition in SAP R/3. If the start date is not available in the SAP R/3 project definition, then the start date in Microsoft Project is the start date of the task that gets started first. If the finish date is not available in the SAP R/3 project definition, the finish date is the finish date of the task that gets completed last in Microsoft Project.
<b>If any task starts before the project start date, the project start date is pushed back to the start date of the task that begins first.</b>
<b>If any task ends after the project end date, the project end date is pushed forwards to the end date of the task that ends last.</b>
Reason for difference in dates could be above cited and hope this solve ur problem.
Enjoy SAP.....
Regards
Sudhakar
PS: Pl reward points for suitable answer

Itunes match; a) if incorrect genre etc data has been uploaded to icloud, cannot delete it or replace the track/ data b) now have 9k tracks "stuck" in icloud and cannot delete them no matter what I do. eh?

Hi
I;m having so itunes match issues.
I ran itunes match. I';ve since foumd, I think:
a) if incorrect genre etc data has been uploaded to icloud, I cannot find how to delete it and reupload correct song and data. I am presently assuming that once songs are matched, the meta-data, genre, etc etc thats uploaded is now treated as 'the master' by itunes.
Question: if I want to change the genre on a track, whats the correct way to overwrite the data held in the icloud? if I delete the track i just bring down the old incorrect genres again!
b) I've deleted from the icloud all my music tracks (select all, delete, Y to delete tracks from icloud). I have turned off itunes match on my ipad, iphone, appletv mac and windows pc. I've deleted the itunes library files too from mac and pc in desperation. But hours /days later, when I turn on itunes match on mac or pc, it tells me i still have 9k tracks in icloud. All with the old, wrong meta-data ready to mess up my [now-corrected] files back on my pc!
I cannot delete them no matter what I do. The number of tracks in the cloud was 12k, now 9k so its reducing, by about 1500 tracks a day.
does it really take itunes servers that long to delete the tracks I've asked it to delete, or am i seeing garbage data?
is there a quicker way of deleting all my itunes match library, songs and data?

Thanks for the helpful replies.
My original intention was to 'upgrade' some of my tracks. In those cases, I'd iTunes matched, and the process was completed.
I later downloaded those new tracks but found during that process, the tracks I was downloading had the old metadata.
I guess the idea there is to update the local genres, 'update iTunes match' and wait. How long, I don't know but that's the current solution,yes ?
Thing is I was trying to get my local library updated and, as I thought it, back in order, but was finding my local genre updates were being overwritten. I had a lot of tracks that kept on stating they could be downloaded so I thought the new files hadn't been copied down...
I think I was trying to get match to do too many things at once.
Deleting my tracks in the cloud? Was an act of desperation to start over with all known good genres locally and to re- upload, start over. I'd read in some forum or other to do that, I guess that was wrong,
Ok so I will.. Err,
A wait and see how long it takes to delete my tracks in the cloud ie let it complete the process I'd already started.
B Correct my local tracks genres
C Wait til those changes propagate up to the iCloud ( or whatever the right term is)
Q1: How long should I wait for A and C to complete?
Q2: Is it 100% definite that local genre changes will get copied up to the cloud, when I 'update iTunes match'?
I don't see any animated cloud icon, but I will watch for it!
Thanks again
Iain

Incorrect number of data lines in TST03

Hi,
one of our scheduled jobs is being cancelled with no errors but those found on SP12 - Consistency Check:
Incorrect number of data lines in TST03
Any idea of what might be happening?
SM21 reports the following:
Error 13 for write/read access to a file. File =
Error at DB commit, return code 016384
SAP Commit Failed
Stop Workproc20, PID 9915
Start Workproc20, 4 times since system startup. PID 10255
Invalid object name for TemSe object: " "
Failed to create log for job /SAPAPO/BACKGROUND_SCHEDULING
Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
Delete session 001 after error 023
Thanks
Antonio

Hi Naveen...
yes, the problem was solved but it had nothing to do with SAP itself...
We have our APO system on two servers: the message server (and DB) runs on an iSeries and the application server and LiveCache server on a SuSE Linux machine. This last server has several iSeries shared (NFS) folders mounted and all TemSE objects are created on one of these folders.
Now the problem is we use a Vision solution for our HA. Whenever Vision is "touching" a file, Linux can't "see" the lock status due to NFS limitations. So, when it is trying to access the same file, a "permission denied" error message is issued to SAP, causing the job to abort and the TemSE object to become inconsistent.
One solution is to change from NFS to Samba.
Another one, much faster to implement, is stopping the Vision job during the night period, when those SAP jobs run. Since then, we didn't had any more problems.
Of course, this is simply a workaround and not a permanent solution!
Could this be your scenario as well?
I hope you can solve your problem...
Merry Christmas and a Happy 2009 for everyone!
Antonio

Runtime Error during Phase Start Data Selection

Hello Forums,
We are using TDMS (2006_1_700) to extract a year's worth data from one client into a new client on the same ERP EhP4 system.
All the systems - central, sender and receiver are at the same DMIS levels(SP16) and all necessary notes have been applied.
During the Step 'Start Data Selection' of the Data Transfer Phase, we see around 60 of the ~12000 sub tasks abort with the below error:
Batch job for access plan calculation in sender system ended with errors
Message no. DMC_UTIL_MSG021
Diagnosis
The access plan calculation was executed as a background job in the sender system. In this background job, an error occurred.
Procedure
Check if a short dump occurred in the sender system while the access plan was calculated. If existing, this short dump contains further information about the cause of the problem.
A frequent error is that selection criteria for data reduction (for example selection groups) are wrongly defined which causes the database access that consideres these selection criteria to fail.
The corresponding dump in the Sender system is as below:
Runtime Errors         SAPSQL_WHERE_PARENTHESES
Exception              CX_SY_DYNAMIC_OSQL_SYNTAX
Error analysis                                                                                |
|    An exception occurred that is explained in detail below.                                      |
|    The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX', was not                |
|     caught in                                                                                |
|    procedure "/1CADMC/DMCACS00P000000001" "(FUNCTION)", nor was it propagated by a               |
|     RAISING clause.                                                                              |
|    Since the caller of the procedure could not have anticipated that the                         |
|    exception would occur, the current program is terminated.                                     |
|    The reason for the exception is:                                                              |
|    The current ABAP program has tried to execute an Open SQL statement                           |
|    which contains a dynamic condition. The part of the condition specified                       |
|    at runtime is incorrectly parenthesized.
Please suggest in case any of you have encountered similar error and possible resolution.
Thanks in advance,
Srikishan

Hi Suman,
Thanks a ton. I somehow missed this when searching on the SMP.
I will implement the steps and post it back by tomorrow.
Regards,
Srikishan

Restriction of Validity start date in Scheduling agreement

Hi,
I am not able to convert the message 06 170( Start of validity period is in the past) in error message , when i am going to define attributes of system messages in purchasing and converting this message into error , system still does not give error message when i am selecting back validity start date in the header of Scheduling agreement (me32l)
What can be the possible reason.
Regards
Sachin

Hi,
I believe the message 06-170 is hard-coded in Include "MM06EFRP_EKKO-KDATE" in the Program SAPMM06E
Laufzeitbeginn in der Vergangenheit -
    IF ekko-kdatb < sy-datlo.
      MESSAGE w170 INTO gl_dummy.
      mmpur_message 'W' '06' '170' '' '' '' ''.
Please consul your ABAP Team on this to change it to Error.
But SAP does not recommend changing standard Programs, so please discuss this and see that its really required and will not have any effects to your business process, because there may be instances wherein you might require to create scheduling agreements with a past validity date sometime in future based on business requirement.
Regards
Chandra Shekhar

Change in start date of tax depreciation not for posting in mid of year

Hi Experts,
Tax depreciation area is not for posting. The fiscal year is from Jan to Dec. I want to calculate tax depreciation from May 2011 based on Net Book Value of tax depreciation as on 30.04.2011. But once I change the start date of tax depreciation in asset master to 01.05.2011, the system ignores the previous depreciation so I am not getting the NBV of tax depreciation of 30.04.2011.
Is any setting is required to get this. I can not do changes in posting rules since this tax depreciation is not for posting any thing.
The fiscal year 2010 is closed and NBV of tax depreciation as on 31.12.2010 of one asset is 80000, If I change the start date of tax depreciation from 1.1.2011 then system correcly take NBV of 31.12.2010 for further depreciation calculation. But if i change the start date of depreciation in between of year the system is calculating depreciation based on NBV of 31.12.2010 but ignores the tax depreciation from 1.1.2011 to 30.04.2011, which I previously run using AFAB.
Need your assistance to know is it feasible to do this.
Thanks and Regards,
Harshad

Hi Harshad
The behaviour of the system is very much correct, it is designed to behave that way...
One, you should not have changed the dep start date....
two, NBV in SAP is always taken to be NBV @ the start of the year....
The best wayout I can suggest here is, if you are on EhP4 and EA-FIN active
a. Change the Dep Key in the asset... You can maintain Time Dependant Dep Terms in asset master i.e. Dep Key X from Jan-Apr and Dep Key Y from MAy onwards
b. This will however, calculate dep based on NBV at the start of the year, but based on new useful life
c. Considering your eg: The system is posting more depreciation i.e. 5333 instead of 5155.... So, calculate this amount outside the system and post a Manual Write up ABZU inorder to reduce the Dep and increase the NBV
Even if you are on not on EhP4, you can follow the same approach as above.... i.e.
a. Change the Dep Key in asset master.... This will throw up new dep figure, on the basis of New Useful life and NBV at the start of the year
b. Post a write up from ABZU....
No need to do Asset to asset transfer in my opinion
Only diff between EhP4 and Non EhP4 is that the differential depreciation would be lesser if you are on EhP4... i.e. instead of 5333 now, system may throw up depreciation amount of 5666.. So, you may need to post write up of 5666-5155
br, Ajay M

Incorrect Coverage Start Dates

Similar Messages

Maybe you are looking for