with SP16-17 we can't create support message from satellite system anymore

[Former Member]

hello,

We have implemented the support package 16 and 17 SAPKITL427 in solution manager last week-end and since then all satellite systems can not create support message anymore.

The process is perfectly working in solman itself and we don't think we have thus a process customizing issue here but who knows...

The key user creates the message with the help -> create support message

and when he saves it (clicking the mailbox button) he gets the following error

Error in Local Message System: Function not available Message was Not

Created

In fact the error Message is BCOS088

We debugged the function BCOS_CREATE_MSG and we found out that the function

DNO_OW_CREATE_NOTIFICATION is returning error code 1.

We checked out RFC connection and it looks ok

There is no dumps in ST22, no error in SLG1 in both system...a nightmare

The notification SLF1 is created in solman but the status field of the notification is empty and it looks that the record is somehow corrupted because you can't modify it with dnotifwl.

Due to the fact that the notification is not correctly created the support message is also not created.

SAP and our solman consultant are working on it since 2 days but don't have a clue. Maybe some program where no regenerated correctly ?

If you would have any idea in which direction to look, i would greatly appreciate

thanks a lot

best regards Xavier

[Former Member]

Hello Xavier,

just a query,are u update with the Basis and ABA support packs also

Rohit

[Former Member]

My provider told me to have implemented the stack 17.

the current version in Solman is the following

SAP_BASIS 700 0016 SAPKB70016 SAP Basis Component

SAP_ABA 700 0016 SAPKA70016 Cross-Application Component

PI_BASIS 2006_1_700 0006 SAPKIPYM06 Basis Plug-In (PI_BASIS) 2006_1_700

ST-PI 2005_1_700 0006 SAPKITLQI6 SAP Solution Tools Plug-In

SAP_BW 700 0018 SAPKW70018 SAP NetWeaver BI 7.0

SAP_AP 700 0012 SAPKNA7012 SAP Application Platform

BBPCRM 500 0012 SAPKU50012 BBPCRM

CPRXRPM 400 0013 SAPK-40013INCPRXRPM SAP xRPM/cProjects/cFolders 4.00 (ABAP)

ST 400 0017 SAPKITL427 SAP Solution Manager Tool

ST-A/PI 01K_CRM560 0000 - Application Servicetools for CRM 500 510

ST-ICO 150_700 0015 SAPK-1507FINSTPL SAP Solution Manager Implementation Cont

ST-SER 700_2008_1 0004 SAPKITLOO4 SAP Solution Manager Service Tools

nothing has change on the satellite system, maybe I have to do something there also (but the ST_PI are on the same level)

thank you for your help

br Xavier

[Former Member]

what is the basis level u r running on satellite system

Rohit

[Former Member]

hi Rohit,

on the satellit I have the following versions

SAP_BASIS 700 0012 SAPKB70012 SAP Basis Component

SAP_ABA 700 0012 SAPKA70012 Cross-Application Component

PI_BASIS 2005_1_700 0012 SAPKIPYJ7C PI_BASIS 2005_1_700

ST-PI 2005_1_700 0006 SAPKITLQI6 SAP Solution Tools Plug-In

SAP_BW 700 0013 SAPKW70013 SAP NetWeaver BI 7.0

SAP_AP 700 0009 SAPKNA7009 SAP Application Platform

SAP_HR 600 0018 SAPKE60018 Human Resources

SAP_APPL 600 0010 SAPKH60010 Logistics and Accounting

EA-IPPE 400 0010 SAPKGPID10 SAP iPPE

EA-APPL 600 0010 SAPKGPAD10 SAP Enterprise Extension PLM, SCM, Financials

EA-DFPS 600 0010 SAPKGPDD10 SAP Enterprise Extension Defense Forces & Public Security

EA-HR 600 0018 SAPKGPHD18 SAP Enterprise Extension HR

EA-FINSERV 600 0010 SAPKGPFD10 SAP Enterprise Extension Financial Services

FINBASIS 600 0010 SAPK-60010INFINBASIS Fin. Basis

EA-PS 600 0010 SAPKGPPD10 SAP Enterprise Extension Public Services

EA-RETAIL 600 0010 SAPKGPRD10 SAP Enterprise Extension Retail

EA-GLTRADE 600 0010 SAPKGPGD10 SAP Enterprise Extension Global Trade

IS-PS-CA 600 0010 SAPK-60010INISPSCA IS-PUBLIC SECTOR CONTRACT ACCOUNTING

IS-OIL 600 0010 SAPK-60010INISOIL IS-OIL

IS-M 600 0010 SAPK-60010INISM SAP MEDIA

IS-H 600 0010 SAPK-60010INISH SAP Healthcare

IS-CWM 600 0010 SAPK-60010INISCWM Industry Solution Catch Weight Management

INSURANCE 600 0010 SAPK-60010ININSURANC SAP Insurance

FI-CAX 600 0010 SAPK-60010INFICAX FI-CA Extended

FI-CA 600 0010 SAPK-60010INFICA FI-CA

ERECRUIT 600 0010 SAPK-60010INERECRUIT E-Recruiting

ECC-DIMP 600 0010 SAPK-60010INECCDIMP DIMP

IS-UT 600 0010 SAPK-60010INISUT SAP Utilities/Telecommunication

SEM-BW 600 0010 SAPKGS6010 SEM-BW: Strategic Enterprise Management

LSOFE 600 0010 SAPK-60010INLSOFE SAP Learning Solution Front-End

ST-A/PI 01K_ECC600 0000 - Application Servicetools for ECC 600

APICON 1470000000 0000 - APICON GmbH, Interface Add ON

thank you Xavier

[Former Member]

Hi Xavier,

Check these steps:

1. Did you create IMG project for Service Desk Configuration? SPRO_ADMIN

2. Did you create project views for the IMG project? SPRO_ADMIN

3. Did you define Service Desk Definition in Satellite Systems?

Goto transaction SM30 in Satellite System and enter table/view as u201CBCOS_CUSTu201D.

Check whether the table/view has the following entry.

u2022 Column 1: Application: OSS_MSG

u2022 Column 2: + : W

u2022 Column 3: RFC Destination: <RFC destination to the SAP Solution Manager system>

This is a back rfc. Make sure that this is working fine.

u2022 Column 4: + : CUST620

u2022 Column 5: + : 1.0

4. Docuble check whether all the required services are activated in Solution Manager(Tcode - SPCR20). SERVICE_DESK_CHANGE_REQUEST_32A

SOLMAN40_SDESK_BASICFUNC_000

SOLMAN40_SDESK_ACT_ADVCLOSE_001

SOLMAN40_SDESK_ACTIONLOG_001

SOLMAN40_SDESK_TPI_ACT_AST_001

Hope this should help you to resolve the issue.

Regards,

Sanjai

[Former Member]

Hi,

thank you for your answer I analysed your reply but because all the process is working inside solman and that notification is created but corrupted. I just wonder what SP16 and SP17 have corrupted in the process.

the coding to create the notif is behaving differently when calling from outside or inside solman

we were running the process successfully since 9 months. Just suddently the SP installation made it wrong, this must be somewhere there....but where ?????

we didn't touch the SLF1 creation process, that is why I believe this might be a standard bug (some program were not

I have asked my service provider to regerate all source in solman to see if it changes something

br Xavier

[Former Member]

hi to all,

the problem was due to the spau operations that was not handled properly

best regards