SAP HR Benifits - Urgent

Question

Hi,
This is important and urgent.
I have created a benifit health plan for IT0167. The entry for this is through T-Code <b>HRBEN0001 </b>.
When I go to PA30 and make an entry by selecting the IT0167, it works fine. But this is not appearing in Enrollment (HRBEN0001). Can any one tell me how do I add the plan in here? Is there any config node that I have missed?
Please reply ASAP.
Thanks,
Vivek.
Points shall be rewarded!!!

Answer 1

Hi Vivek
PA30 should not be used for benefits administration. Please refer to the following information from note 124934:
The eligibility rules are not checked when the user enrolls an employee  to a plan using the transaction 'Maintain Personal Administration'  (PA30).
  Solution
  Generally we distinguish between 'Plan data' and 'Administrative data'.
  With plan data all information about a plan itself is meant, e.g. plan
  type, cost or contribution limits, while administrative data means all
  information about the EE participation in a plan (eligibility,
  enrollment, programs). If persons are enrolled via PA90 (Release 3.x) or
  HRBEN0000 (Releases 4.x), the consistency of both the plan and the
  administrative data is checked, and e.g. enrollment is forbidden for a
  person which is not eligible. However, transaction PA30 cannot exploit
  the full functionality of the administrative side of the benefits
  module, so that in general we do not recommend using PA30 at all. If
  PA30 is used, however, we only perform the plan data check with error
  messages since in this transaction only the plan data is fully and
  consistently available.
  In general, we advise all customers to use the Benefit transactions PA90
  (Releases 3.x) / HRBEN0000 (Releases 4.x) instead of transaction PA30,
  because the administrational plan data (Eligibility, Co- and
  Pre-requisites, Permissions) are NOT checked in PA30.
  There are two reasons why the administrative data is not checked when
  using PA30:
   1.) Not all Administrative Data is available in PA30. For example, it
        will not be possible, anyway, to configure co-requisite plans in
        PA30, because these plans cannot be created simultaneously in
           PA30.
      2.) Some customers may want to have a possibility to circumvent
           administrative (such as eligibility) rules for enrollment
           of certain employees in some special cases (e.g. an employee
           with a special contract shall be allowed to participate in a
           plan prior to the expiration of the eligibility waiting period).
           This is not possible to be realized in the Benefit transaction,
           but using PA30.
     This problem may arise when the customer wants to create or update many
     Benefit infotypes via Batch Input. This is only possible using PA30, so
     that customers probably cannot circumvent using PA30. A possible
     solution of this issue could be to remove the illegal records out of the
     batch file, either by performing the checks already on creation of the
     batch files or by modifying the files with a customer specific report.
Hope it is helpful
Regards,
Jun