topic Re: Exclude SOD-handler for SAP_ALL-users? in Application Development and Automation Discussions

Exclude SOD-handler for SAP_ALL-users?

former_member192774 — Fri, 24 Aug 2012 09:25:24 GMT

Hi, GRC-team.

Is there someway for:

SAP Adapter has a problem, SOD violations will not be checked !!!

Please check with your system Administrator

Technical Info:

java.lang.NullPointerException

Violations exceeds the threshold limit:THRESOLD:40000DETAIL:154996:SUM

when su01/pfcg with sap_all user?

Regards

Vlad

Re: Exclude SOD-handler for SAP_ALL-users?

Former Member — Fri, 24 Aug 2012 09:31:44 GMT

Hi Vlad,

Please refer to the below mentioned SAP notes for your reference:-

1145048

1490894

1562774

I hope this will help you.

Regards,

Yukti

Re: Exclude SOD-handler for SAP_ALL-users?

Sam_Minocha — Fri, 24 Aug 2012 09:33:51 GMT

Hi Vlad,

Kindly also check SAP note 1270413.

Kind Regards,

Saksham

Re: Exclude SOD-handler for SAP_ALL-users?

Former Member — Fri, 24 Aug 2012 09:35:48 GMT

Hi Vlad,

Please refer to the sap note-1062037 and Kindly check that you have configured the Adapter as

per the note.

Best Regards,

Nandita

Re: Exclude SOD-handler for SAP_ALL-users?

Former Member — Fri, 24 Aug 2012 09:39:44 GMT

Hi Vlad,

Also, while defining the connector kindly uncheck the check box for unicode system and save the connector. After saving the connector, go to SAP Adapter in RAR application and make it green for that system.

After making these changes kindly restart the J2EE server and check for the issue.

Regards,

Yukti

Re: Exclude SOD-handler for SAP_ALL-users?

former_member192774 — Fri, 24 Aug 2012 13:13:14 GMT

Yes!!

TST solution work! Should not rush

Java - slow elephant!

goto PRD

Thanks for your's time

Vlad

p.s. do not goodbye until...

Re: Exclude SOD-handler for SAP_ALL-users?

former_member192774 — Sat, 25 Aug 2012 06:39:23 GMT

1062037 is released internally only

may by email?

Re: Exclude SOD-handler for SAP_ALL-users?

former_member192774 — Sat, 25 Aug 2012 08:56:51 GMT

1145048 is released internally only

Re: Exclude SOD-handler for SAP_ALL-users?

Former Member — Sun, 26 Aug 2012 15:08:33 GMT

Hi Vlad,

1. Make sure that you have configured the SAP Adapter as per the sap

note- 1060673.

2. Check for the JCO Connection and make sure that the Model and Meta

data corresponding to the JCO Connection are properly configured and is

connecting your backend system with the Frontend application.

3. Restart your J2EE Engine after performing the above steps.

Best Reards,

Nandita

Re: Exclude SOD-handler for SAP_ALL-users?

former_member192774 — Tue, 28 Aug 2012 06:05:28 GMT

28.08.2012 - 07:40:17 CET - Info for SAP by Vladislav Rusakov

Hi, Nandita

note 1060673 hasn't enough information.

For purity of the experiment
1.I cleared unused Jco (unset outbound connection). As result in list
SAP Adapters remained one.
2.Set VIRSAHR*MODEL VIRSAHR*METADATA Maxpoolsize=50 Maxconnection=100
3. Check sm59 RFC - CCRISKANALYSIS, RAR-Configuration JCo test, check
tx RSGWLST - programm ok.
4. Set configtool: -Djrfc.trace=1
5. Set SM59 RFC CCRISKANALYSIS trace on.
6. Restart RAR, SAP Adaptor.
7. su01 - change last_name (other points closed - CUA active)
window comes up with: SAP Adapter has a problem, SOD violations will
not be checked"
java.lang.NullPointerException" or "unknown RFC error".
I close this window and programm check violation continue.
====================
I didn't found reasons for this situation now.

peace of dev_rfc.trc (SM59):

**** Trace file opened at 20120828 094104 Pakistan Standard Time, by disp+work
**** Versions SAP-REL 720,0,312 RFC-VER U 3 1350538 MT-SL
>>>> [5] CCRISKANALYSIS : TCP <ac: 25> K %%RFCSERVER%% >>> READ (34952040)
-{91CAF0E1-5DF1-F181-A8FD-002655F397EE}
{root-id=002655F397EE1EE1BC99118381D848FD}_{conn-id=00000000000000000000
{root-id=002655F397EE1EE1BC99118381D848FD}_{conn-id=91CAF0E15DF1F180A8FD
000000	01010008 01020105 04010002 01010103	................
000010	00040000 020B0103 0106000B 04010002	................
000020	01060200 00002301 06000700 16003100	......#.......1.
000030	30002E00 31003100 37002E00 39002E00	0...1.1.7...9...
000040	34003100 07001100 02005200 11001200	4.1.......R.....
000050	06003600 34003500 12001300 08003700	..6.4.5.......7.
000060	32003000 20001300 08001000 6B007000	2.0. .......k.p.
000070	6F007300 61007000 30003100 08000600	o.s.a.p.0.1.....
000080	1C004300 43005200 49005300 4B004100	..C.C.R.I.S.K.A.
000090	4E004100 4C005900 53004900 53000605	N.A.L.Y.S.I.S...
0000a0	140010E1 F0CA91F1 5D81F1A8 FD002655	...áðÊ.ñ].ñ¨ý.&U
0000b0	F397EE05 14040300 24005200 46004300	ó.î.....$.R.F.C.
0000c0	5F004500 58005400 45005200 4E004100	_.E.X.T.E.R.N.A.
0000d0	4C005F00 41004200 4F005200 54040304	L._.A.B.O.R.T...
0000e0	02000004 02FFFF00 00FFFF00 00000000	.....ÿÿ..ÿÿ.....
Received RFCHEADER [5]: 01/BIG/IEEE/SPACE-U2/4102
Received UNICODE-RFCHEADER [5]: cp:4102/ce:IGNORE/et:6/cs:2/rc:0x00000023
K-CodePages: default=4103, logon_lang=4103, curr_locale=4103, front_locale=4110, - may be into?
UUID: ab_rfccheck_uuid compare uuid's {91CAF0E1-5DF1-F181-A8FD-002655F397EE}
======>
ABAP Programm: /VIRSA/SAPLPFCG (Transaction: SU01)
Called function module: /VIRSA/RT_JAVA_RISK_ANALYSIS
User: TEST_GRC (Client: 100)
Destination: CCRISKANALYSIS (Handle: 5, DtConId: 91CAF0E15DF1F180A8FD002655F397E
EPP RootContextId: 002655F397EE1EE1BC99118381D848FD, ConnectionId: 0000000000000
EPP TransactionId: 63CAF0E12CB8F1A4A8FD002655F397EE
>>>> [5] CCRISKANALYSIS : TCP <ac: 26> K %%RFCSERVER%% >>> FREE abrfcio.c 3602
-{91CAF0E1-5DF1-F181-A8FD-002655F397EE}
{root-id=002655F397EE1EE1BC99118381D848FD}_{conn-id=00000000000000000000
{root-id=002655F397EE1EE1BC99118381D848FD}_{conn-id=91CAF0E15DF1F180A8FD
>>>> [5] CCRISKANALYSIS : TCP <ac: 27> K %%RFCSERVER%% >>> CLOSE abrfcio.c 3291
-{91CAF0E1-5DF1-F181-A8FD-002655F397EE}
{root-id=002655F397EE1EE1BC99118381D848FD}_{conn-id=00000000000000000000
{root-id=002655F397EE1EE1BC99118381D848FD}_{conn-id=91CAF0E15DF1F180A8FD

Regards

Vlad

Re: Exclude SOD-handler for SAP_ALL-users?

former_member192774 — Tue, 25 Sep 2012 05:19:08 GMT

Hi, Nandita.

"back to GRC".

----------------------------------------

I found differences in roles!

Background administrator ID - N/*

Transaction Code - to erase SU50-52

----------------------------------------

debug call FM /VIRSA/RT_JAVA_RISK_ANALYSIS return "System error" when add ZSAP_BC_ENDUSER role. But SAP_BC_ENDUSER role is added to user without problem!

p.s. ZSAP_BC_ENDUSER is a copy SAP_BC_ENDUSER.

---

Regards

Vlad