Method "SET_SCHEMA_NAMESPACE" is unknown error after SP Upgrade

[former_member190939]

Hi,

Issue Details:

We were actually running our Development - SAP Netweaver Gateway System with SP07. Then We upgraded the system to SP10.

But the problem now is that whenever we transport a service from development landscape to quality, we are receiving the following error. Please note that our Quality landscape remains in SP07 for some reasons.

The error details are:

And also i am getting syntax errors in MPC and DPC classes.

Error in MPC:

Error in DPC:

We suspect that this is happening due to the difference in the IW_BEP node.

/IWBEP/IF_MGW_CORE_TYPES – Development:

/IWBEP/IF_MGW_CORE_TYPES – Quality:

My service execution gives the following exception in ST22:

/sap/opu/odata/sap/ZNW_UI5_TBC_TRC_Q00013_SRV/$metadata

Can you please advise how to solve this issue?

Best Regards,

SEYED ISMAIL

[Former Member]

Hello Seyed,

We are also facing the same problem in our system.

Could you please tell me the proper solution for this.

[former_member190939]

Hi Riya,

No other way. You need to keep all the systems in the same version.

[Former Member]

Hello Seyed,

Can we create Z type for TY_S_MGW_RESPONSE_ENTITY_CNTXT

And then we will use that Z data type in class

Will that work fine?

[former_member190939]

HI Riya

you can try. But it may be series of such corrections

try and let me know

[Former Member]

Hello Seyed,

We are using same version in both the system.

But may be during SP upgrade namespace ----/IWBEP is not imported properly.

[former_member190939]

Then Ok. Are the SP versions same for IWBEP across all the systems? You can check in transaction SPAM - PACKAGE LEVEL.

[Former Member]

Hello Seyed,

Yes we are having same SP version in all the system.

[former_member190939]

You can also try to increase you IWBEP SP version.

For example, if you are IWBEP version SP10, you can upgrade to SP 11.

I Think that's the perfect solution

[Former Member]

Hello Seyed,

AS per SAP

• The service of the external model must exist on the SAP NetWeaver Gateway and be up and running.
• The ID of the service and the name of the model have to be provided to the method.

As you rightly suspected about the component IW_BEP.

Please refer following SAP help link,

/IWBEP/IF_MGW_ODATA_MODEL - SAP NetWeaver Gateway - SAP Library

You can ignore component version while moving transport but it might not give you desired results.

Regards

Anand

[former_member190939]

Yes, it didn't help. I tried already.

Thank you Anand.

[kammaje_cis]

Seyed,

Problem is because SPs are not in sync. You should  have you entire landscape in sync. You should not move any transport before you upgrade your Quality/Prod.

[former_member190939]

Thanks Krishna, But currently I don't think we will be able to do this for Quality/Production. Are there anything you can help me with? Are there any work arounds?

Thank you.

Ismail MAC

[kammaje_cis]

Workaround is tedious.

You need to see each syntax error in Quality, and solve it by redefining the method in Dev and ensure that only SP7 artefacts are used. Then move this transport to Quality.

[former_member190939]

But I fear that I cannot modify standard objects. 😞

[kammaje_cis]

I am not talking about standard objects. Because problem is not with standard objects. You need to change the generated Z*MPC_EXT and Z*DPC_EXT classes and redefine methods from Z*MPC and Z*DPC classes.

[former_member190939]

May be.

For example, it says  TY_S_MGW_RESPONSE_ENTITY_CNTXT is unknown in the below line:

!ES_RESPONSE_CONTEXT type /IWBEP/IF_MGW_APPL_SRV_RUNTIME=>TY_S_MGW_RESPONSE_ENTITY_CNTXT

In this case, I can't add this type to standard obj /IWBEP/IF_MGW_APPL_SRV_RUNTIME. Right?

Ismail MAC.

[kammaje_cis]

Change this

/IWBEP/IF_MGW_APPL_SRV_RUNTIME=>TY_S_MGW_RESPONSE_ENTITY_CNTXT

to

ZIF_MGW_APPL_SRV_RUNTIME=>TY_S_MGW_RESPONSE_ENTITY_CNTXT