cancel
Showing results for 
Search instead for 
Did you mean: 

PA30 : Invalid Date of Birth

Former Member
0 Kudos

Hi ,

During transaction PA30 at the time of creating Personal data for employee system gives me error as Invalid date of Birth.

I dont want to put the date of birth of the employee as it is not required by me.

I changed the settings in SPRO for the MP00200 / 2000 wherein I mentioned DOB(P0002-GBDAT) as optional entry.But system always asks for DOB during transaction.

Is it a standard behaviour of the system to always check DOB of the personal against start date. ?

If I want to remove this check and dont want to enter DOB hw should I proceed ?

Rgds

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi

Please check whether the screen 2000 itself is getting triggered or if it has any country specific screens triggered for your employee like 2010 (USA), 2040 (india) etc. Then go to V_T588M and modify the screen properties for that country screen.

Regards

Ranganath

Former Member
0 Kudos

Hi Ranga ,

Thnks for reply

Screen 2032 is triggered and I made the changes in that screen(2032) and in every screen wherever I found P0002-GBDAT field but still the message Invalid date of birth.

Rgds

Former Member
0 Kudos

Hi

For screen 2032 your GBDAT should match the CURP number in a particular format. So here are the rules for entering CURP number to match your GBDAT,

CURP is of 18 characters.

1-4 - Can be any alphabets

5-6 - Should be year of birth (So if it is 2010 then it should be 10)

7-8 - Should be month of birth

9-10 - Should be date of birth.

11 - Should be Gender (H for Female, 'M' for Male)

12-13 - Should be for state code (Eg. AGUASCALIENTES(2) TYPE C VALUE 'AS',

BAJA_CALIFORNIA(2) TYPE C VALUE 'BC' etc)

14-16 - Should be any consonant i.e. any alphabet apart from AEIOU. Again no numbers/special characters/space are permitted.

So if your GBDAT is '20100905', then CURP should/can be 'ABCD100905'. And also first four chars cannot be any special characters as well.

Regards

Ranganath

Edited by: Ranganath Ramesh on Mar 23, 2011 1:31 PM

Former Member
0 Kudos

Please answer below questions ,

Is it a standard behaviour of the system to always check DOB of the personal against start date. ?

If I want to remove this check and dont want to enter DOB hw should I proceed ?

Former Member
0 Kudos

Hi Rasam,

This is standard system behavior.

This check is done in module pool MP000200 screen 2000 :

FORM INPUT_STATUS.

..

IF FIRST_GBDAT GT CPREL_BEGDA ....

MESSAGE W035(pg).

ENDIF.

I don't think there is a way of removing it other than repair, which is yet not advised.

Regards,

Dilek

PedroGuarita
Active Contributor
0 Kudos

That validation should issue a warning and not an error.

I think it's this code that is giving the error :


    CHAIN.
      FIELD P0002-BEGDA.
      FIELD P0002-GBDAT MODULE GBDAT ON input.     "XDPK005693
*     FIELD P0002-GBDAT MODULE GBDAT ON REQUEST.   "XDPK005693
    ENDCHAIN.
....
module gbdat input.
  if p0002-gbdat lt low_date   or                           "K11K101077
     p0002-gbdat gt sy-datum.                               "K11K101077
    message e019.                                           "K11K101077
  endif.      
...

Either way, it's like you said, needs a repair. A way to solve this, since you don't need the DOB, is to fill it by default with some value in a PBO exit with P0002-BEGDA for example.