All Qualifications date is Maintained as 01.01.1900

[Former Member]

Hi Friends,

In Infotype 24 it is displaying as " Change profile period from 01.01.1800" and the qualifications are created from 01.01.1900. I could not understand how to change this.

In the relationships there are different dates, qualifictions are assigned to employees on the date of their birth.

Pls let me know how to change this. Even i cannot delete this relationships

Pls let me know if any one has faced similar problem

Thanks

HRuser

[Former Member · Accepted solution]

Just a question: is it really important?

[Former Member · Accepted solution]

Hi Valerie,

All my PD module is going to Short dump, i could not able to change the qualifications when ever i change qualifications it is going to short dump.

Even i tried to create new qualification but even in that if i maintain this relationship Q B 028 Business Event type is going to short dump.

Pls let me where the problem is ??

Thanks for the info

Regards

HRuser

[Former Member · Accepted solution]

I don't know much about qualification, but have a few knowledge on shortdump

Do you have details on the dump? any messages?

Did it ever run? (long time implemented or new project?)

[Former Member · Accepted solution]

Hi Valerie,

Here is the Dump Info... but it is not giving any message, even debugging mode is not working

Error dump is not giving any message.

here is the dump description

Runtime error:

Unable to write short dump.

What happened?

Error in ABAP application program.

The current ABAP program " " had to be terminated because one of the statements could not be executed.

This is probably due to an error in the ABAP program.

Unfortunately, the original cause of the error cannot be determined

because there is no suitable short dump in the table SNAP (which

records information about the point of termination).

termination).

What can you do?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer termination messages, especially those beyond their normal deletion date.

Error analysis

Unfortunately, the original cause of the error cannot be

determined, since there is no suitable short dump in table SNAP.

The table SNAP probably already contains a number of short dumps and cannot accept any more. Please check the situation using the system log.

The table SNAP contains all the short dumps for the last 7 days.

How to correct the error

Check the system log for each cause of error.

More space probably needs to be provided for table SNAP

using database means.

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

" " C

" " or " "

" "

If you cannot solve the problem yourself, please send the

following documents to SAP:

System environment

SAP Release.............. " "

Application server....... " "

Network address.......... " "

Operating system......... " "

Release.................. " "

Hardware type............ " "

Character length......... " " Bits

Pointer length........... " " Bits

Work process number...... " "

Short dump setting....... " "

Database server.......... " "

Database type............ " "

Database name............ " "

Database owner........... " "

Character set............ " "

SAP kernel............... " "

Created on............... " "

Created in............... " "

Database version......... " "

Patch level.............. " "

Patch text............... " "

Supported environment....

Database................. " "

SAP database version..... " "

User, transaction...

Client.............. " "

User................ " "

Language key........ " "

Transaction......... " "

Program............. " "

Screen.............. " "

Screen line......... " "

Information on where terminate

Contens of system fields

SY field contents.............

Active calls / events

No Dump information available

Chosen variables

No Dump information available

Application Calls

No dump information available

Application Information

No dump information available

Internal notes

The termination occurred in the function " " of the SAP

Basis System, specifically in line " " of the module " "

The internal operation just processed is " ".

The internal session was started at " ".

List of ABAP programs affected

No dump information available

List of internal tables

No dump information available

Directory of Application Tables

No dump information available

Directory of Application Tables (Administrative Information)

No dump information available

ABAP control blocks CONT

No dump information available

End of runtime analysis

This is the dump information, even we have cleared SNAP table, Basis guy has done that. event though there is no change

Even this will not be recorded in ST22

Any info on this kind of error

[Former Member · Accepted solution]

Hi,

Pls first contact w. Basis people to clear SNAP table.

Also check out the following SAP Notes:

17537

16083

Regards,

Dilek

[Former Member · Accepted solution]

Hi Dilek,

Thanks for the OSS note information, I have informed the basis guys about that and and they are working on clearing SNAP table.

Thanks for your information

Regards

HR user

[Former Member · Accepted solution]

Hi Dilek,

Thanks for the OSS note, we have cleared SNAP table now it is showing error in PAD31

is there some thing i am missing in relationships. ??

Runtime Error DBIF_RSQL_SQL_ERROR

Exception CX_SY_OPEN_SQL_DB

Occurred on 10.09.2008 at 10:48:39

An SQL error occurred when accessing a table.

What happened?

What can you do?

Make a note of the actions and input which caused the error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

Error analysis

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', wasneither

caught nor passed along using a RAISING clause, in the procedure"ADATA_DB" "FORM)"

.

Since the caller of the procedure could not have expected this exception to occcur, the running program was terminated.

The reason for the exception is:

How to correct the error

The exception must either be prevented, caught within the procedure "ADATA_DB"

"(FORM)", or declared in the procedure's RAISING clause.

To prevent the exception, note the following:

Database error text........: "ORA-01653: unable to extend table SAPR3.HRPAD31

by 80 in tablespace PSAPSTABD"

Internal call code.........: "[RSQL/INSR/HRPAD31 ]"

Please check the entries in the system log (Transaction SM21).

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself, use the following search Criteria:

-

---

"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC

"SAPLRHAP" or "LRHAPF1K"

"ADATA_DB"

-

---

System environment

SAP Release.............. "620"

Application server....... "Development"

Network address.......... "200.200.200.10"

Operating system......... "Windows NT"

Release.................. "5.2"

Hardware type............ "2x IA64 Level 3"

Character length......... 8 Bits

Pointer length........... 64 Bits

Work process number...... 1

Short dump setting....... "full"

Database server.......... "Development"

Database type............ "ORACLE"

Database name............ "VC3"

Database owner........... "SAPR3"

Character set............ "English_United State"

SAP kernel............... "640"

Created on............... "Aug 16 2007 23:23:39"

Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version......... "OCI_920_SHARE "

Patch level.............. "196"

Patch text............... " "

Supported environment....

Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE

User, transaction...

Client.............. 600

User................ "HUSER"

Language key........ "E"

Transaction......... "PP01 "

Program............. "SAPLRHAP"

Screen.............. "MP100100 6000"

Screen line......... 16

Information on where terminated

The termination occurred in the ABAP program "SAPLRHAP" in "ADATA_DB".

The main program was "MP100100 ".

The termination occurred in line 57 of the source code of the (Include) program LRHAPF1K"

of the source code of program "LRHAPF1K" (when calling the editor 570).

Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in

the procedure "ADATA_DB" "(FORM)" but was not handled locally, not declared in the RAISING clause of the procedure.

The procedure is in the program "SAPLRHAP ". Its source code starts in line 8 of the (Include) program "LRHAPF1K ".

Source code extract

Dilek is there some thing i am missing some relationship with 031

Pls advise

[Former Member · Accepted solution]

Hi Dilek,

Thanks for the response and the OSS note really helped us. I appreciate for all your help in giving me a solution..

Pints awarded

Regards

HR user