got strucked with SPAM Upgrade in NUC system

[Former Member]

Dear Techies,

I got struck with Spam Upgrade SAPKD70150 from SAPKD70145....stopped at phase of DISASSEMBLE,

and getting DUMP CALL_FUNCTION_NOT_FOUND.... and its showing First import SPAM/SAINT update SAPKD70150 completely

Actually we run this in Dev successfully but unable to run in quality because of we transported one TR in to QAS...now we are unable to revert back that TR.... pls suggest in urgent !!!    

Here system details

Non unicode system

SAP VERSION 701

AIX 6.1

oracle 10g

kernel 701 patch level 150. tp and r3trans updated.....

Thanks& Regards

RAZZ R

[JPReyes · Accepted solution]

Well, can you post the dump?... you can try to send in a new transport with the corrections (whatever they are) using tp import command at OS level.

Regards, Juan

[Former Member · Accepted solution]

Hi Juan,

Thanks Juan for your quick reply...pls find below the dump....and pls suggest which transport request needs to transport to correct the errors...

Short text

Function module "OCS_CHECK_NAMING_CONVENTION" not found.

What happened?

The function module "OCS_CHECK_NAMING_CONVENTION" is called,

but cannot be found in the library.

Error in the ABAP Application Program

The current ABAP program "SAPLOCS_CORE" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

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

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was

not caught in

procedure "OCS_PATCH_DISASSEMBLER" "(FUNCTION)", nor was it propagated by a

RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

The program "SAPLOCS_CORE" contains the CALL FUNCTION statement.

The name of the function module to be called is "OCS_CHECK_NAMING_CONVENTION".

No function module exists with the name "OCS_CHECK_NAMING_CONVENTION".

All function modules are listed in the Function Library (SE37).

-

Possible reasons:

a) Wrong name specified. Pay particular attention to

upper/lower case and underscores ("_").

or

b) Transport error

c) In the case of an enqueue/dequeue module,

the lock object may not have been activated

(ABAP/4 Dictionary).

How to correct the error

Check the last transports to the SAP System.

Is the program "SAPLOCS_CORE" currently being changed?

If an enqueue/dequeue module is involved, is the activation

of the lock object missing in the ABAP/4 Dictionary?

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:

CALL_FUNCTION_NOT_FOUND "CX_SY_DYN_CALL_ILLEGAL_FUNC"

SAPLOCS_CORE or "LOCS_COREU40"

OCS_PATCH_DISASSEMBLER

Function modules with names similar to "OCS_CHECK_NAMING_CONVENTION":

OCS_CHECK_COMPONENT

OCS_CHECK_MAINTENANCE_CERT

OCS_CHECK_COMPONENT_PATCH

OCS_CHECK_DECLARATION

OCS_CHECK_ADD_ON

OCS_CHECK_LOCKED_COMPONENT

OCS_CHECK_RUNNING_UPGRADE_4_NA

OTC_INTEREST_CONVERSION_CHECK

OXT_TASK_CONVERSION_CHECK

OCS_CHECK_NOTE_CORR_UPG

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

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

The exception must either be prevented, caught within proedure

OCS_PATCH_DISASSEMBLER "(FUNCTION)", or its possible occurrence must be

declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

Thanks&Regards

RZZ

[JPReyes · Accepted solution]

Basically, if the content of the transport that went to QAS has nothing to do with the above dump, then we'll have to assume that your DEV and QAS systems were not at the same SP level or that modifications were done in QA that didn't came from DEV.

Regards, Juan

[Former Member · Accepted solution]

Please check with SE37  if this FM exists.

[Former Member · Accepted solution]

Dear Juan,

Absolutely right you are,

when we upgraded SPAM Level 45 to 47 after that we applied SNOTE 1778145 (created one workbench request) , but in QAS we done mistake that we tranported that request before we upgrading spam level. The above note saying do not transport or dont apply note when spam level 45

I try to get resolve this with modifications but unable to do , so we made database restore and again started spam upgrade...its working fine now...

Thanks to all Techies for your Quick response..

Thanks&Regards

RAZZ

[Former Member]

Hi,

If all your system are in same version and SP level, please try with SPAM in QA also.

I  suspect system are not in sysnc.

Thanks

prabhakar...

[Former Member]

Hello,

Have you tried to ignore it and restart  the SP upgrade as par sap note 1293744?

Regards,

Vishal

[Former Member]

Hi,

Did you try to retry it,

Is your kernel same in both the system.

we transported one TR in to QAS...now we are unable to revert back that TR

What is this TR about.

Can you please post the below logs from < DIR_TRANS >/log.

SAPL*

SLOG,ALOG,ULOG

Thanks

Rishi Abrol

[Former Member]

Hi Rishi,

Please find below

SNOTE 1778145

Version 3

Processor

Processing Status In Process

Implement. Status Can be implemented

Language EN

Short Text 'UNKNOWN_ERROR' in phase Disassemble during SP import

Component BC-UPG-OCS-SPA Support Package Tools for ABAP

________________________________________________________________________

Long Text

Symptom

You import HR related Support Packages (for components SAP_HR, EA-HR, HR-CEE) and get

the error 'UNKNOWN_ERROR' in phase Disassemble. The action log show the error message:

"Internal error: No valid source context supplied"

Other terms

Support Package Manager, Add-On Installation Tool, SPAM, SAINT, UNKNOWN_ERROR

Reason and Prerequisites

This error is caused by a programming error; it may only occur during the import of HR

related Support Packages.

Solution

The error is fixed with SPAM/SAINT Version 0048.

As long as this SPAM/SAINT Version is not available, you can fix it by implementing

the attached correction instruction with the note Assistant. The note correction can

also be implemented while the Support Package queue with the HR Support Packages is

defined and stays in phase DISASSEMBLE. The Support Package Manager has to be started

anew after the correction was implemented!

Please be careful when transporting this note correction between systems with

different SPAM/SAINT Versions. For instance, transporting the function module

OCS_PATCH_DISASSEMBLER from a system with SPAM/SAINT Version 0046 (or higher) into a

system with SPAM/SAINT Version 0045 (or lower) will produce syntax errors in function

group OCS_CORE, so that the tools Support Package Manager and Add-On Installation Tool

does not work anymore. Do not do this!

Note the following: After you have imported SPAM/SAINT Version 0048, you can reset

the note to original in transaction SPAU or remove it from the modification browser

(transaction SE95). Ensure that no objects are changed when you remove the note. To do

this, deselect all objects in the traffic light dialog box.

________________________________________________________________________

we applied above note in Dev system n created a request , at that time spam updated successfully and now we tranported that request in Quality system, now its got strucked ....pls read above bold lines ...we have done this unfortunately....

____________________________________________________________________

Thanks&regards

Razz

[Former Member]

Hi,

First of all i dont see any requirment to implement this note as the fix was provided in SPAM/SAINT 48. You are deploying SP50 so that makes the use of this note not valid for you.

Now can you please go in snote ->goto -> sap note browser.

give the name of the note and execute. Now select the same note and then

SAP NOTE -> Reset SAP note implemented.

I think that you might have to open the system to do that.

Once you have done it please try ti reimport SPAM/SAINT.

Thanks

Rishi Abrol

[Reagan]

Hello

I got struck with Spam Upgrade SAPKD70150 from SAPKD70145....stopped at phase of DISASSEMBLE.

This is the problem

Please be careful when transporting this note correction between systems with different SPAM/SAINT Versions. For instance, transporting the function module OCS_PATCH_DISASSEMBLER from a system with SPAM/SAINT Version 0046 (or higher) into a system with SPAM/SAINT Version 0045 (or lower) will produce syntax errors in function group OCS_CORE, so that the tools Support Package Manager and Add-On Installation Tool does not work anymore. Do not do this!

If I were you I would try this:

Go to the development system and reset the SAP note and create a new transport request.

Release the transport request and import that into the quality.

Restart the SPAM update.

If that doesn't help then you probably need to reset the OCS queue and kick start the SPAM update again.

Regards

RB