cancel
Showing results for 
Search instead for 
Did you mean: 

job SM:SYNCHRONIZE USER DATA FOR NOTIFICATION canceled

Former Member
0 Kudos

Dear SAP Guru,

The BG job SM:SYNCHRONIZE USER DATA FOR NOTIFICATION is canceled every day and it´s

generating shortdump. Our system is SAP EHP1 for SAP Solution manager.

SAP ABA and SAP BASIS components are release 701 level 3.

ST is release 400 level 19

ST-PI is release 2008_1_700 level 1

ST-A/PI is release 01L_CRM570

Pls look on this shortdump.

Runtime Errors RAISE_EXCEPTION*

Date and Time 22.03.2010 06:50:11

*----


*

*----


*

|Short text |

| Exception condition "CUSTOMIZING_NOT_FOUND" raised. |

*----


*

*----


*

|What happened? |

| The current ABAP/4 program encountered an unexpected |

| situation. |

*----


*

*----


*

|What can you do? |

| Note down which actions and inputs caused the error. |

| |

| |

| To process the problem further, contact you SAP system |

| administrator. |

| |

| Using Transaction ST22 for ABAP Dump Analysis, you can look |

| at and manage termination messages, and you can also |

| keep them for a long time. |

*----


*

*----


*

|Error analysis |

| A RAISE statement in the program "SAPLDSWP_UTILITY" raised the exception |

| condition "CUSTOMIZING_NOT_FOUND". |

| Since the exception was not intercepted by a superior |

| program, processing was terminated. |

| |

| Short description of exception condition: |

| |

| |

| For detailed documentation of the exception condition, use |

| Transaction SE37 (Function Library). You can take the called |

| function module from the display of active calls. |

| - |

*----


*

*----


*

|How to correct the error |

| |

| If the error occures in a non-modified SAP program, you may be able to |

| find an interim solution in an SAP Note. |

| If you have access to SAP Notes, carry out a search with the following |

| keywords: |

| |

| "RAISE_EXCEPTION" " " |

| "SAPLDSWP_UTILITY" or "LDSWP_UTILITYU19" |

| "DSWP_GET_GLOBAL_CUSTOMIZING" |

| |

| or |

| |

| "SAPLDSWP_UTILITY" "CUSTOMIZING_NOT_FOUND" |

| |

| or |

| |

| "RDSWP_NM_SYNC_USER_DATA " "CUSTOMIZING_NOT_FOUND" |

| If you cannot solve the problem yourself and want to send an error |

| notification to SAP, include the following information: |

| |

*|

*----


*

|System environment |

| SAP-Release 701 |

| |

| Application server... "crsgrant" |

| Network address...... "10.128.32.175" |

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

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

| Hardware type........ "2x Intel 801686" |

| Character length.... 8 Bits |

| Pointer length....... 32 Bits |

| Work process number.. 13 |

| Shortdump setting.... "full" |

| |

| Database server... "CRSGRANT" |

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

| Database name..... "SM1" |

| Database user ID.. "SAPSM1" |

| |

| Terminal.......... " " |

| |

| Char.set.... "Czech_Czech.28592" |

| |

| SAP kernel....... 701 |

| created (date)... "Apr 12 2009 22:43:15" |

| create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00" |

| Database version. "OCI_10201_SHARE (10.2.0.4.0) " |

| |

| Patch level. 39 |

| Patch text.. " " |

| |

| Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.." |

| SAP database version. 701 |

| Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows |

| NT 6.0" |

| |

| Memory consumption |

| Roll.... 8112 |

| EM...... 4181184 |

| Heap.... 0 |

| Page.... 24576 |

| MM Used. 873664 |

| MM Free. 170296 |

*----


*

*----


*

|User and Transaction |

| |

| Client.............. 001 |

| User................ "SOLMAN" |

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

| Transaction......... " " |

| Transactions ID..... "C27635DF574FF121B0470050569757E9" |

| |

| Program............. "SAPLDSWP_UTILITY" |

| Screen.............. "SAPMSSY0 1000" |

| Screen line......... 6 |

*----


*

*----


*

|Information on where terminated |

| Termination occurred in the ABAP program "SAPLDSWP_UTILITY" - in |

| "DSWP_GET_GLOBAL_CUSTOMIZING". |

| The main program was "RDSWP_NM_SYNC_USER_DATA ". |

| |

| In the source code you have the termination point in line 22 |

| of the (Include) program "LDSWP_UTILITYU19". |

| The program "SAPLDSWP_UTILITY" was started as a background job. |

| Job Name....... "SM:SYNCHRONIZE USER DATA FOR NOT" |

| Job Initiator.. "SOLMAN" |

| Job Number..... 00104000 |

Have you some solution or advice?

Best Regards

Jakub

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Please could you check the following ?

- Please ensure that the latest version of note 1172948 has been implemented

- Please follow the recommendation in note 1314587.

- Check table 'DSWPGLOBALCUSTOM' and ensure that the entry 'DTMLOG' is available. Create the entry if missing.

These procedures will solve this issue.

Former Member
0 Kudos

Thanks for very helpful answer,

Problem was solved by creating DTMLOG record.

Regards

JV

Former Member
0 Kudos

Correct answer. In my case the entry in the table solved the problem.

Former Member
0 Kudos

Correct answer.. in my case adding entry "DTMLOG" in the table "DSWPGLOBALCUSTOM" solved the problem..

Thanks Mateus

Answers (1)

Answers (1)

hrollizo
Active Participant
0 Kudos

Hi,

If you have solman 7.1 or 7.2, check de SAP Note 1961736 - Solman workmode cannot be set for the managed systems - Error: Exception condition "CUSTOMIZING_NOT_FOUND"

Goto SE16

Table name DSWPGLOBALCUSTOM

Enter

F8 to execute

F5 to create new entry

FELD: DTMLOG

INHALT:  X

Goto to SM37 and copy the job SM:SYNCHRONIZE USER DATA FOR NOT, release it, and check the Status (Finished), or wait to the next scheduled execution (daily)

Regards