execute rsecnote leads to an runtime-error in program 'ssa/nsx'

[Former Member]

Hi @all,

if I try to execute tc <rsecnote>, then i keep an system-rutnime-error. I found out it's an problem during security_check in program /SSA/NXS.

following notes are completly implemented:

888889

1388729

1030838

The notes was transported from another system and there runs correctly.

here is an shortcut form system-log:

Error in ABAP application program.

The current ABAP program "/SSA/RTC" had to be

statements could not be executed.

This is probably due to an error in the ABAP program

In program "/SSA/NXS ", the following syntax e

in the Include "/SSA/NXS " in line 575:

"Feld "GC_DL_DIGITAL_SIGNATURE_PID" unknown.

I hope anybody can help!

Best regards

Alex

[Former Member]

Are you sure that both the systems are on same patch level? If this is working in system and it must work on another if both are on same patch level.

[Former Member]

Hello Sunil,

I'm sure, both systems has the same patch-level.

Actually, I could solve the problem.

Reason:

Then ST-A/PI 01M SP01 was implemented. Report /SSA/NXS and /SSA/NCA then represented the newest ST-A/PI 01M SP01 state, but two includes and other reports that were not overwritten by the support package contained the ST-A/PI 01L state.

Solution:

i) Include /SSA/INT containes a line

GC_DL_DIGITAL_SIGNATURE_PID LIKE /SSF/PTAB-PID VALUE 'NXD',

ii) Include /SSA/INS containes a line

PF_OPTION_VALUE.

iii) Report /SSA/MXS contains a lines

form security_notes_check.

iv) Reports RSECNOTE and /SSF/RSECNOTE exist

From this system I executed one transport with

R3TR PROG /SSA/INT

R3TR PROG /SSA/INS

R3TR PROG /SSA/MXS

R3TR PROG RSECNOTE

R3TR PROG /SSF/RSECNOTE

and imported this transport to the systems with ST-A/Pi 01M* SP01

where the syntax error occurs.

The syntax errror was resolved.

Best regards,

Alex

Edited by: Alexander Reichel on Dec 2, 2010 4:00 PM

[Former Member]

thanks for updating this thread with solution, please mark as answered.

[Former Member]

was facing similar problem, report u201C/SSF/SAO_UTILSu201D and option u201CRepair syntax errors in /SSA/-analysis reports by commenting" has solved our problem.

Regards,

Sreenivas .Y