Personal Data and Address for Country Grouping 99 - error on ESS

Question

Hello All,
I have configured personal data and address infotypes in ESS for the country grouping 99.
I have done the following config
1. Assign Screen Structure to Infotype Versions
2. Define Active Subtypes and Use Case
3. Define Country-Specific Applications
4. Created a Z service and then assigned this service to subarea.
I made use of US service and copied to z.
after the config when i log on to the portal and check the personal data or address links am getting the error:
An exception occurred that was not caught., error key: RFC_ERROR_SYSTEM_FAILURE
the st22 dump is
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED_NO
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "HRXSS_PER_CLEANUP" "(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:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component.
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
I searched in the forum but still am unable to figure it out where i am wrong or missing any config or any other technical error.
Can any one pls help me

Answer 1

http://wiki.sdn.sap.com/wiki/display/ERPHCM/HowtoReuseCountryspecificapplicationsforMolga99
check the steps in above link
and also please check with some standard country like india 40 or usa 10 what use cases and time constraints have been set
INFTY - Now specifies the infotype.
USECASE - Corresponds to the value in the table V_T7XSSPERSUBTYP.
ZEITB - Corresponds to the value in the table V_T591A (V_T582A).
Page 2
SUBTYPE_TAB - Here, you will find a list of the subtypes that have
already been checked and that are correct.
You then find the subtype in METADATA-SUBTY. However, you must move up
one subroutine in the call hierarchy in advance to do this.
This data makes it easy for you to identify the infotype and the subtype
and correct the inconsistency by making entries in the tables mentioned.
ie
T_cd:SE24 >>CL_HRPA_PERNR_INFTY_XSS >> CHECK_USECASE_WITH_CONSTRAINT >>
for
usecase = A1, A4, B1, B4 (table V_T7XSSPERSUBTYP)
you need to have
zeitb = '1' OR zeitb = '2' (table V_T591A)
for
usecase = A2, A3, A5, B2, B3, B5
you need to have
zeitb = '2'
for
usecase = A6, B3
you need to have
Zeitb = '3'