Benefits Plans Enrollment Problem in ECC

Hi All,
I have two insurance plans and i configured two insurance plans and i attached to one insurance plan type and i am able to see my insurance plans in my Benefits Enrollment screen (HRBEN0001).
Now my problem is: i am not able to enroll two plans one after another, if i am able to enroll one plan then i am not able to enroll in another plan, so only one plan is allowed to enroll.
Could you please some one tell me where did i mistake, and i am new to this Benefits configuration.
Thanks in Advance.
Regards,
Abhi.

Hi,
You have probably configure both plan under same plan category and that only allow to enroll a person in just one. You have to configure it in different category under the same attributes.
There is also an activity in spro under Flexible Administration called Prerequisites and Corequisites. Check that out, but the issue may be in what I mentión aboved.
Regards,
Edoardo

Similar Messages

Error in Benefits Plan Enrollment

Hi,
I am receiving an error when executing HRBEN0001 transaction to enroll employees in spouse Life plan for MOLGA 10. This error happens in case the EE does not have a spouse (IT0021 subtype 1). The error details are as below.
Spouse's birth date could not be determined
Message no. HRBEN00FMODULES159
For EE who have a spouse, we do not get this error.
The coverage and cost variants for this plan are configured in IMG for Age determination relevant data from SPOUSE.
How do I prevent this error. Ideally, would not like this plan to be eligible in case no spouse is present. Could not figure out how this would be done.
Appreciate any assistance. ECC 6.0
Thanks
Sumeet
Edited by: SUMEET MEHTA on May 16, 2008 12:38 PM
Please, can somebody reply. This is urgent. If not specifically this error msg, can you tell how to prevent eligibility to a spouse life plan when no spouse is present in IT0021.

Hi Anand,
I tried using dependent/beneficiary and RLPGR but it did not work. Would this not be used to control eligibility in the dependents/beneficiary tabs.
What the client wants is to control Employee eligibility to the plan. If spouse is not present then EE must not be eligible for spouse life plan. How would this be achieved through standard customizing without using PBEN0006 and ABAP coding.
Thanks
Sumeet
Edited by: SUMEET MEHTA on May 20, 2008 8:53 PM

Benefits Management Enrollment problem

Hi.
I'm doing on Benefits Management, Health Plans.
I have finished doing all the configuration under spro for health plans. But under Enrollment, i can't find any of my health plans. And so i can't enroll..
When i click on the error list, it said that 'No entry found in the adjustment authorization table'.
Can i know whether anyone knows how to solve it? Thanks.

Hi,
You have probably configure both plan under same plan category and that only allow to enroll a person in just one. You have to configure it in different category under the same attributes.
There is also an activity in spro under Flexible Administration called Prerequisites and Corequisites. Check that out, but the issue may be in what I mentión aboved.
Regards,
Edoardo

Benefits - NewHire enrollment default plans

Hi,
In new hire enrollment form (t-code HRBEN0005), i need to display the default plans for which the employee is eligible(as new hire is not enrolled in any plan till now)
but I am not able to find the table from where i can get the plan types and bplans which are default for the new hire.
Can anyone please tell met the table name where this info is stored.
Regards
Manu

Hi,
To expand on the previous answer a bit, first the employee would have to default to the correct Benefit Area via Feature BAREA. Then he would have to default to the correct First and Second Program groupings (BENGR and BSTAT) via those Features. This is all recorded in IT0171. Then the new hire should have an IT0378 for the adjustment reason New Hire.
In Benefits --> Flexible Administration --> Programs in the IMG, you have to create the Program for the benefits plans that you want the individual to be eligible for. You may also create eligibility rules in that area.
If all is done correctly, the employee can enroll via ESS or HRBEN0001after selecting the "New Hire" reason and the correct benefit plans will be available.
Paul

ESS Webdynpro Benefits Open Enrollment

We currently have the ITS application for benefits open enrollment (PZ14) up and running. We are trying to setup the Webdynpro service for Open Enrollment.
We are on ECC 6.0, EP 7.0 latest SPs and we are using XSS 600 webdynpro Software Components.
Problem:
When we click on Open Enrollment service (Webdynpro), the following message comes up:
No plan selections could be prepared for the specified enrollment reason. Contact your Benefits Administrator for assistance.
The same service works fine with the ITS service for the same PERNR. The ITS service is able to show up the Open Enrollment without any problem.
Even if I include an entry in Infotype 0378 Adjustment Reasons, the new enrollment reason can be seen under the ITS Service but not under the webdynpro service.
Is there any additional customization (configuration) required for the Webdynpro Service for Open Enrollment.
thanks,

Experiencing the same issue. Did someone find a solution to this?
Thanks!

ESS Benefits Generic Enrollment - Different behavior backend v/s portal

We are using the ESS Benefits generic enrollment service for enrollment kicking off the adjustment reasons on IT 0378.
Here is the configuration set up, trying to simplify to explain the matter. We are on ECC 6.0 with EHP2.
1. Configured one plan type in savings category.
2. Within this plan type, configured 2 plans.
3. Configured all other related configuration to set up the 2 plans.
4. Configured the adjustment reason and the appropriate plan type created in step 2.
5. Created the required adjustment reason on 378.
In HRBEN0001 transaction via backendwe can see the 2 plans configured within the plan type.
But when Trying to enroll from ESS - only one plan can be seen for that plan type, the other plan is not shown at all.
OK - eventually, debugged and found this piece of code in FM HR_BEN_ESS_FILL_SELECTION_DISP. The 2 different plans are there until this piece of code takes one of them Off...
CODE -
3.) Reduce entries to one entry per type and period
delete adjacent duplicates from selection_display_gt
    comparing pernr
              barea
              bpcat
              pltyp
              begda
              sprps.
CODE -
This FM is called only for ESS application and not for backed program.
What we do not understand is why is it behaving differntly on backend v/s portal.
Any information or experience with this form any one of you will be highly appreciated.
Thanks.

Siddharth,
Thanks for your reply. Yes ESS has its own FMs. The UI, user exits, BADIs etc are different for backend v/s front end.
What we are not clear with, is the different behavior in core functionality -- i.e. When the adjustment reason is processed from the backend using HRBEN0001 - The 2 plans within the Plan Type are available for elections. BUT the same adjustment reason for the same penr when processed from ESS - there is just one plan available for elections.
It's clear from the code, that it is deleting one plan and this code is within the FM which is called only from ESS. But we are still not sure why it should behave differently i.e. 2 plans via backend v/s one plan via ESS.
Wanted to see if anyone can share any information if they have a similar benefits set up .. 2 plans within one plan type FOR savings plan category and then having a adjustment reason set up.
Regards.

ESS Benefits open enrollment - Issue

Hi,
When we click on the benefits open enrollment link, we do not want some of the plans to be displayed to the ess user. Is there any way to control it ( SPRO or BAdI ).
Env - EP 7.0, ECC6.0
Thanks,
Ravi

I posed the same question to an ESS consultant who responded with the following:
"The plans presented in benefits enrollment (PZ14) and Participation Overview (PZ07) are list output from ABAP. You can go into the program and select or exclude some of them based on certain criteria. I've seen customers extend the Plan infotype to add a flag field to make it configurable to show, not show a given plan."
Since specific instructions weren't given, I wouldn't consider the issue answered.
However, I can provide the following work around:
Due to the fact that different populations have different open enrollment period timeframes, and all populations have been configured under one benefit area...we decided to create an "Open Enrollment Adjustment Reason" for each group instead. Thus, the Adjustment Reason permissions will only display the plans we want the employee to see via ESS. Prior to the open enrollment period for the population, we will run the Mass Adjustment Reason report to create IT378 for all relevant employees. The OE offer will appear as another Adjustment Reason under the Enrollment service in ESS.

Dependents from IT0021 are not appearing in IT0167 for Benefits Plans

Hi All,
Our client upgraded developement and QA client from 4.6 to 6.0 version. While assigning benefieries to the benefits plans in Dependents tab(IT0167) list of dependents are not appearing. Where in in Production system dependents are appearing, production is still in 4.6 version.
Regards,
Karunakar

Dear,
It is always required to read the dependent data as on the start date of IT0167. This is because for each plan, there is some dependent eligibility associated and to calculate eligibility, the data come from infotype 0021.
I would advice you to go through the note 947172. By implementing this note, you will be able to allow employee to edit the existing dependent record instead of delimiting and creating a new dependent record.
Best Regards,
Deepak..

Benefit plan enrollment

Hi All,
Please help me in the following :
As per my Business requirement i need to delimit a Benefit plan becuase that plan is no longer existed in their business effective form 01.01.2009. So as per their requirement i have deleted the master data records existed after 01.01.2009. Now i need to do some functional configuration so that end user will never enter the data for the "Actions" done through PA40.
This plan is not coming any actions performed enrollment. before the changes itseld this plan is not enrolling. i need to show my user that plan is not active in the enrollment for any of the actions through PA40. and note that this is "Default Offer plan".
I can delimit and closed the plan effective form 01.01.2009. Before that i have to make sure that this plan enrollment is possible if plan is
"OPEN".
Can any one help me how can i show this plan into the action.
Thanks & Regards,
Naga

problem solved

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

Is there any Data Mapping document Between S&OP ( model that uses supply planning operator ) and SAP ECC that I will help the client in Data Mapping activity.

Hello All,
Is there any Data Mapping document Between S&OP ( model that uses supply planning operator ) and SAP ECC that I will help in Data Mapping activity.
Thanks,
Mownesh

There are standard templates in HCI data sources.
e.g. 1) Customer Master data template is SOP_MD_CustomerMaster for extracting master data from SAP ECC and load it to S&OP
KNVP is the table for customer in ECC from that you can select the fields as required
KUNNR for customer Number
ADRNR for Address
List of a few commonly used table names of ECC:
Product Related:
MARA – Material Master (MATNR)
MARC – Material Master with Plant Data (MATNR, WERKS)
MARD – Material Master with Storage Location Data (MATNR, LGORT, WERKS)
MAKT – Material Master Material Descriptions (MATNR, MATKL)
MBEW – Material Valuation Data (MATNR, BWTAR)
MVKE – Material Master : Sales related Data
MDKP, MDTB – MRP related Data( Header, Item)
MCHA, MCHB – Material Batches (Header, Item) (MATNR, WERKS, LGORT, CHARG)
Vendor/Supplier related:
LFA1 – vendor data (LIFNR)
LFB1 -- Company Code Segment : Vendor Data(LIFNR, BUKRS)
LFC1 -- FI Related Vendor Data (LIFNR, BELNR)
LFM1 – Pur. Orgn. Related Vendor Data (LIFNR, EKORG)
PReq/PO, BOM Related:
EBAN – Pur. Req. Data( BANFN, BNFPO, BADAT, MATNR)
EINA – Purchase Info. Record(General Data)(INFNR, MATNR, LIFNR)
EINE – Purchase Info. Record (pur. Orgn. Data) (INFNR, EKORG)
ELBK, ELBN, ELBP – Vendor Evaluation Related Data
EKKO – PO Data (Header) (EBELN, BSTYP, BSART)
EKPO – PO Data (Item) (EBELN, EBELP, MATNR)
Pur. Req., RFQ and PO are differentiated by Doc Type (BSTYP) in EKKO table.
For RFQ it is ‘A’ and for PO it is ‘F’
MKPF – GRN Data (Header) (EBELN, BLDAT, BUDAT, XBLNR, BKTXT)
MSEG – GRN Data(Item) MBLNR, BWART, LIFNR, MATNR, EBELN)
Apart from this there are lot of tables which begin with ‘M’ & ‘E’, but we
use the following very often.
EQUK – Quota (Header)(QUNUM, MATNR)
EQUP – Quota (Item) (QUNUM, QUPOS, LIFNR)
EKBE – PO History Data (EBELN, EBELP, BELNR, BLDAT, MATNR, VGABE)
EKBZ – PO History with Delivery Costs(EBELN, BELNR, LIFNR, XBLNR)
EKET – Schedule lines data of a PO(EBELN, EINDT, SLFDT)
EKES – Vendor Confirmations Data (EBELN, EBTYP, EINDT, XBLNR)
T163F – Confirmation Texts (EBTYP, EBTXT)
T156 – Movement Types (BWARE)
T024 – Purchasing Groups
T024E – Purchase Organizations
T163 – Item Category’s in Purchasing Documents(PSTYP)
T149D – Valuation Types
T134 – Material Types
FVLK – Delivery Types
STKO, STPO – BOM(Bill Of Material) related Data (Header & Item)
STPU, STPN, STST, STZU – BOM Related Tables
RKPF, RBKP, RSEG (Header & Item) – MM – FI Related Data
KONO, KONH – Pricing data
T006 – Basic Unit Of Measurements
Customer/Sales Order Related:
VBAK : Sales Document(Header Data) (VBELN)
VBAP : Sales Document(Item Data) (VBELN, POSNR, MATNR, ARKTX, CHARG)
Enquiry, Quotation, Sales Order are differentiated based on Doc.
Type(VBTYP Field) in VBAK, VBAP Tables for Enquiry VBTYP = A, for Quotation ‘B’ & for Order it is ‘C’.)
LIKP : Delivery Table(Header Data) (VBELN, LFART, KUNNR, WADAT, INCOL)
LIPS : Delivery Table(Item Data)(VBELN, POSNR, WERKS, LGORT, MATNR, VGBEL)
(LIPS – VBGELN = VBAK- VBELN, LIPS-VGPOS = VBAP-POSNR)
VTTK : Shipment Table(Header Data) (TKNUM)
VTTP : Shipment Table (Item Data)(TKNUM, TPNUM, VBELN)
(VTTP – VBELN = LIKP – VBELN)
VBRK : Billing Table(Header Data) (VBELN, FKART, BELNF)
VBRP : Billing Table(Item Data) (VBELN, POSNR, FKIMG, NEWR, VGBEL, VGPOS)
(VERP – AUBEL = VBAK- VBELN, VBRP – VBEL = LIKP – VBELN)
Apart from these tables there are lot of other tables which starts with ‘V’, but we use the
following tables frequently.
VBUK: All Sales Documents status & Admn. Data(Header) (VBELN, VBTYP)
VBTYP = ‘C’ (Sales Order) VBTYP = ‘L’(Delivery) VBTYP = ‘M’(Invoice)
VBUP: Sales Documents status & Admin. Data(Item) (VBELN, POSNR)
VBEP : Sales Document Schedule Lines Data (VBELN, POSNR, EDATU, WMENG)
VBKD: To get sales related Business data like Payment terms etc.(VBELN, ZTERM)
VBFA: Sales Document flow data(VBELV, VBELN, POSNV, VBTYP)
VBPA: Partner functions Data(VBELN, PARVW, KUNNR, LIFNR)
TVLKT: Delivery Type: Texts(LFART, VTEXT)
KNA1, KNB1, KNC1 : Customer Master Data and Other Partner’s Data(KUNNR,
NAME1,LAND1)
KNVK: Customer Master Contact Person(PARNR, KUNNR)
KNVV: Customer Master Sales Data.
LFA1, LFB1, LFC1: Vendor Master Data(To get Transporter data)(LIFNR, NAME1, ORT01)
MARA, MARC, MARD : Material Master Data(Basic, Plant, St. Location Views)
TVKO: Sales Organizations(VKORG)
TVKOV: Distribution Channels(VTWEG)
TVTA: Divisions(SPART)
TVKBZ: Sales Office(VKBUR)
TVBVK: Sales Group(VKGRP)
T077D: Customer Account Group(KTOKD)
T001W: Plants(WERKS)
T001L: Storage Locations(LGORT)
TWLAD: To get address of Storage Location and Plant(LGORT, ADRNR)
TVAU: Sales Document (Order) Types
KONV: Condition Types (pricing) (KNUMV, KSCHL, KWETR)
T685T: Condition Types Texts.
ADRC: To get Addresses of Partners
VBBE, VBBS: Sales Requirements Data
VBKA: Sales Activities Data
VBPV: Sales Document Product Proposal
Based on the functionality you can search ECC table names and fields
Hope this information is helpful for you.
Thanks and Regards,
Anjali

Planning Refresh problem?

Hi All,We have a planning refresh problem. Environment:Oracle repositories on UnixPlanning Server on Win2003Essbase on Win2000When we kicked a planning refresh, it shows that the database is refreshed and when pressed OK, it shows the following error" Object is not allowed when object is closed 3704".Thanks

hi
i found a solution for the Problem in another Forum
http://businessintelligence.ittoolbox.com/groups/technical-functional/hyperion-admin-l/dynamic-calc-formulas-not-refreshed-1719379?cv=expanded
The suggestion is
1. change the Member from Dynamic Calc to Store
2. Refresh (After these Step the Formulas where still out of sync)
3. change the Member from Store to Dynamic Calc
4. Refresh
After these Steps the Formulas are in sync again.
Kevin Kraft
Edited by: Kevin Kraft on Mar 25, 2009 12:33 PM

ESS - Benefits - Open enrollment (Concurrent employment is enabled)

We are trying to set up ESS open enrollment. After adding/editing/changing plans --> review enrollment --> Save.
On saving, getting an error "rfc_error_system_failure" on the ESS screen.
Checked with ST22 for the error details. The name of runtime error is "uncaught exception" and the exception is "CX_HRPA_VIOLATED_PRECONDITION".
Based on a Similar thread on the forums --> Link : [Re: CX_HRPA_VIOLATED_PRECONDITION using HR_INFOTYPE_OPERATION to insert rec; and Sap note # 493984 , the error seems to be related with concurrent empoyment.
Analysis:
1. If CE is disabled, there is no error - open enrollment works fine both in R/3 (HRBEN0001) and via ESS
2. If CE is enabled," open enrollment" in R/3 using HRBEN0001 - there is no error.
3. Error occurs only when "open enrollment" is accessed through ESS, when CE is enabled.
Would like to know if some one can share their experience on using ESS open enrollment when CE is switched on?
Version details: ECC 6.0 (support pack level 22 for SAP-HR and EA-HR), EP 7.0 , ESS BP 1.0
Thanks,
Javed.

Problem solved after deploying note # 1020389

Regd:Benefits Open Enrollment Issue

Hi SAP,
I have problem in Open Enrollment which is in ESS.
We have used the Portal Navigation for designing the Navigation instead of Homepage Framework.
When we were using Homepage frame work the open Enrollment works fine(ie) it will be highlighted when the period is opened and it will be glared when the period is closed.
But now after changing the navigation design it is working fine when the period is open but its not getting blared or disabled when it is closed instead it gives me the error.
I need to make it disable when the period is closed.
Is there any configuration that I have to do.
Please put me some light on it.
Its very urgent.

I posed the same question to an ESS consultant who responded with the following:
"The plans presented in benefits enrollment (PZ14) and Participation Overview (PZ07) are list output from ABAP. You can go into the program and select or exclude some of them based on certain criteria. I've seen customers extend the Plan infotype to add a flag field to make it configurable to show, not show a given plan."
Since specific instructions weren't given, I wouldn't consider the issue answered.
However, I can provide the following work around:
Due to the fact that different populations have different open enrollment period timeframes, and all populations have been configured under one benefit area...we decided to create an "Open Enrollment Adjustment Reason" for each group instead. Thus, the Adjustment Reason permissions will only display the plans we want the employee to see via ESS. Prior to the open enrollment period for the population, we will run the Mass Adjustment Reason report to create IT378 for all relevant employees. The OE offer will appear as another Adjustment Reason under the Enrollment service in ESS.

ESS: Benefits: OPEN ENROLMENT NOT VISIBLE in ESS

Hi Gurus,
This is regarding a SAP HR implementation for US.
Open Enrollment Service is giving a dump with error
u201CNo Correct Adjustment Reason Specifiedu201D.
Following has been checked, still unable to view it in ESS.
u2022     Employees are configured for running Open Enrollment for employees.
u2022     Employees are assigned to appropriate PA and PSA. Country grouping for both the employees is USA: 10.
u2022     Maintained appropriate data in Infotype 0171(General Benefits Information). Correct benefit program grouping is done for both employees ie maintained first and second program grouping for both employees.
u2022     Maintained Benefit Adjustment Reasons for both the employee i.e. Infotype 0378(Adjustment Reason Data).
u2022     Maintained Open Enrollment Offer for employees between 09.13.2008 and 10.13.2008. (MM/DD/YYYY).
u2022     Program HRBEN001 is running correctly in backend. Both employees are able to choose different benefit plans during the open enrollment period.
u2022     User is having SAP_ALL authorizations.
u2022     Resources and Services are correctly defined and linked in the backend.
u2022     HR_BEN_ESS_RFC_ENRO_REASONS is a SAP defined function module to fetch benefit data from Benefit module and post it to ESS internal tables. Testing it in the background using transaction se37 gives correct results in the backend. It is displaying Open Enrollment as one of the Benefit Reasons.
Kindly help with any pointers at the earliest.
Thanks & Regards
Kumarpal Jain

Kumarpal,
did you check this thread
https://forums.sdn.sap.com/click.jspa?searchID=17218337&messageID=6299502
Thanks
Bala Duvvuri

Benefits Plans Enrollment Problem in ECC

Similar Messages

Maybe you are looking for