SYNTAX_ERROR in MAM30_001_GETLIST and MAM30_001_GETDETAIL

[florianbus]

Hello,

I hope someone can help me to resolve this problem. I tried to send orders to my client but I get some I-Errors. After that I tried MAM30_001_GETLIST and MAM30_001_GETDETAIL in se37 and received the following errors:

<b>MAM30_001_GETLIST</b>

Short text

Syntax error in program "/MRSS/CL_IM_RSG_ALM_ME_001====CP ".

What happened?

Error in the ABAP Application Program

The current ABAP program "CL_EXIT_MASTER================CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program

"/MRSS/CL_IM_RSG_ALM_ME_001====CP " in include

"/MRSS/CL_SOS_NODE=============CU " in

line 8:

"Class "/MRSS/CL_SOS_ORDER_SCHEDULER" is unknown."

" "

" "

" "

The include has been created and last changed by:

Created by: "MALCHEREK "

Last changed by: "MALCHEREK "

Error analysis

The following syntax error was found in the program

/MRSS/CL_IM_RSG_ALM_ME_001====CP :

"Class "/MRSS/CL_SOS_ORDER_SCHEDULER" is unknown."

" "

" "

" "

Trigger Location of Runtime Error

Program CL_EXIT_MASTER================CP

Include CL_EXIT_MASTER================CM002

Row 15

Module type (METHOD)

Module Name INSTANTIATE_IMP_CLASS

Source Code Extract

Line SourceCde

1 METHOD instantiate_imp_class .

2

3 DATA: abs_type_classname TYPE string,

4 imp_obj TYPE imp_obj_type.

5

6 * Look for objects that have been created for this class

7 READ TABLE imp_obj_tab INTO imp_obj

8 WITH TABLE KEY imp_name = imp_name

9 calling_obj = caller.

10 IF sy-subrc = 0.

11 instance = imp_obj-obj.

12 ELSE.

13 CONCATENATE '\CLASS=' imp_class INTO abs_type_classname.

14 ***** dynamic object creation *******************************

>>>>> CREATE OBJECT instance TYPE (abs_type_classname).

16 ******************************************************************

17 imp_obj-imp_name = imp_name.

18 imp_obj-calling_obj = caller.

19 imp_obj-obj = instance.

20 INSERT imp_obj INTO TABLE imp_obj_tab.

21 ENDIF.

22 ENDMETHOD.

<b>MAM30_001_GETDETAIL</b>

Short text

Syntax error in program "/MRSS/CL_IM_RSG_ALM_ME_001====CP ".

What happened?

Error in the ABAP Application Program

The current ABAP program "CL_EXIT_MASTER================CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program

"/MRSS/CL_IM_RSG_ALM_ME_001====CP " in include

"/MRSS/CL_SOS_NODE=============CU " in

line 8:

"Class "/MRSS/CL_SOS_ORDER_SCHEDULER" is unknown."

" "

" "

" "

The include has been created and last changed by:

Created by: "MALCHEREK "

Last changed by: "MALCHEREK "

Error analysis

The following syntax error was found in the program

/MRSS/CL_IM_RSG_ALM_ME_001====CP :

"Class "/MRSS/CL_SOS_ORDER_SCHEDULER" is unknown."

" "

" "

" "

Trigger Location of Runtime Error

Program CL_EXIT_MASTER================CP

Include CL_EXIT_MASTER================CM002

Row 15

Module type (METHOD)

Module Name INSTANTIATE_IMP_CLASS

Short text

Syntax error in program "/MRSS/CL_IM_RSG_ALM_ME_001====CP ".

What happened?

Error in the ABAP Application Program

The current ABAP program "CL_EXIT_MASTER================CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program

"/MRSS/CL_IM_RSG_ALM_ME_001====CP " in include

"/MRSS/CL_SOS_NODE=============CU " in

line 8:

"Class "/MRSS/CL_SOS_ORDER_SCHEDULER" is unknown."

" "

" "

" "

The include has been created and last changed by:

Created by: "MALCHEREK "

Last changed by: "MALCHEREK "

Error analysis

The following syntax error was found in the program

/MRSS/CL_IM_RSG_ALM_ME_001====CP :

"Class "/MRSS/CL_SOS_ORDER_SCHEDULER" is unknown."

" "

" "

" "

Trigger Location of Runtime Error

Program CL_EXIT_MASTER================CP

Include CL_EXIT_MASTER================CM002

Row 15

Module type (METHOD)

Module Name INSTANTIATE_IMP_CLASS

Source Code Extract

Line SourceCde

1 METHOD instantiate_imp_class .

2

3 DATA: abs_type_classname TYPE string,

4 imp_obj TYPE imp_obj_type.

5

6 * Look for objects that have been created for this class

7 READ TABLE imp_obj_tab INTO imp_obj

8 WITH TABLE KEY imp_name = imp_name

9 calling_obj = caller.

10 IF sy-subrc = 0.

11 instance = imp_obj-obj.

12 ELSE.

13 CONCATENATE '\CLASS=' imp_class INTO abs_type_classname.

14 ***** dynamic object creation *******************************

>>>>> CREATE OBJECT instance TYPE (abs_type_classname).

16 ******************************************************************

17 imp_obj-imp_name = imp_name.

18 imp_obj-calling_obj = caller.

19 imp_obj-obj = instance.

20 INSERT imp_obj INTO TABLE imp_obj_tab.

21 ENDIF.

22 ENDMETHOD.

[Former Member · Accepted solution]

Hello Florian,

I don't think these are errors related to standard MAM but to the MRSS plugin... This is a plugin for multi-resource scheduling provided by SAP but this is a SAP 'development' and not a standard solution.

The program /MRSS/CL_IM_RSG_ALM_ME_001====CP you're referring to is an interface for a badi used in this plugin. If this badi is active try to deactivate this and see if it it works or check the installation of MRSS.

Kind regards,

jeroen

[florianbus · Accepted solution]

Hello Jeroen,

if I try to deactivate it using se19, I receive "No valid change license available for namespace /MRSS/". I also checked the BAdI with SE19 and I receive "Implementation class /MRSS/CL_IM_RSG_ALM_ME_001 of BAdI implementation /MRSS/RSG_ALM_ME_001 contains errors".

Any idea?

Regards,

Florian

[Former Member · Accepted solution]

Hello Florian,

In the system I'm looking the badi is inactive... So somebody activated this? Or you don't have a license for MRSS?

Which version of MRSS you're using and what's the system release and SP level?

Kind regards,

jeroen

[florianbus · Accepted solution]

Hello Jeroen,

thank you for your help!

The system I use is SAP ECC 6.0.

SAP_BASIS 700 SP9

SAP_APPL 600 SP6

...

There's no MRSS in the list.

I had to enhance the namespace to deactivate the BAdI. Now it seems to work.

Regards,

Florian

[Former Member · Accepted solution]

Hi,

I'm experiencing that same error. Can you please clarify how you enhance the namespace. Just in case I have:

SAP ECC 6.0

SAP_BASIS 700 SP10

SAP_APPL 700 SP07

Thanks,

Miguel

[former_member304703 · Accepted solution]

Hi,

MAM is integrated with SAP MRS, which stands for Multi-Resource Scheduling. This is an SAP product that allows scheduling of orders via board and is an SAP alternative to OnClick software.

This MAM-MRS integration consists of a couple of BADI implementations, icnluding order getList, get Detail and time confimarion create.

Normally this BADI should be deactivated (it is more of an example anyway).

Regards,

Larissa Limarova

[Former Member · Accepted solution]

Hi,

Yes I was trying to deactivate the BADI, but I was having the same problems discussed in the previous post, related to the license and the bad implementation. From the post I gathered that they had to enhance the namespace in order to deactivate the BADI. I'm not familiar with how to enhance the namespace and was wondering what are the actual steps needed to deactivate this BAPI.

Thanks,

Miguel

[Former Member · Accepted solution]

Hi,

I have been unable to enhance this BADI in order to deactivate it. Please what are the steps to enhance the namespace.

Thanks,

Miguel

[Former Member · Accepted solution]

Hi,

I was able to create a new implementation for the BADI using the transaction se19, but still cannot deactivate the SAP implementation. Please advise on additional steps.

Thanks,

Miguel

[former_member304703 · Accepted solution]

Hi Miguel,

I see this question is changed to "answered". Did you get a solution?

I raised this problem to MRS development team and there were supposed to release note. Did you get a solution from them becuase I didn't see note yet.

Cheers,

Larissa Limarova

[Former Member]

Hi,

We worked with SAP to solve our problem. They modified the namespace configuration in order to allow us to deactivate the implementation. I have not heard of any node regarding the issue.

Thanks,

Miguel