How to create a working Gateway service utilizing an Existing ECC Function Module?

[Usha]

Hello All,

Our ECC (Back end) has a Function module which is to be used by creating a Gateway service .Can you suggest the step by step procedure with which i can continue to expose the service?

Any help on this is much appreciated!

Thanks,

Usha

[Virinchy · Accepted solution]

please check if the below blogs can meet your requirements

[Usha · Accepted solution]

Hello Virinchy,

Thanks a lot for the response !

I started with the link : http://scn.sap.com/people/volker.drees/blog/2012/10/26/step-by-step-guide-to-build-an-odata-service-... and when tried to execute the service from TCode : /IWFND/GW_CLIENT(end of the link above),

I am facing the below error:

Error message :Model 'ZUSHA_GW_SO_MDL_0001_BE' contains errors. Contact Administrator.

Could someone guide me on how to proceed with the analysis?

Thanks,

Usha

[ChandraMahajan · Accepted solution]

Hi,

Refer where the OP was also facing same error and it was due to RFC connectivity problem with  ECC server. please check the same with your systems.

Regards,

Chandra

[Virinchy · Accepted solution]

Which version of SAP NWG are you working on ? 

When following the tutorial , have your run time objects been generated successfully ?

Also please check if system alias is configured properly..

[Usha · Accepted solution]

Hello Virinchy,

Thanks for the response.

NW version NW 7.31 SP 009.

Yes,the Run time objects were generated successfully !

System Alias is configured properly for our Backend system, but confused about the "Local app" option there.

Attached our System Alias setup: we have 2 system alias for our backend system

The above error Model 'ZUSHA_GW_SO_MDL_0001_BE' contains errors occurs when i map the system alias to FIO

When i map the System alias to FIO_800_BWF where Local app is set -- the Metadata generation is successful.

So wondering about the "Local app" flag !

Any suggestions on this ?

Thanks,

Usha

[Usha · Accepted solution]

Hello Mahajan,

Thanks for the response !

Yes ,i am checking the system configuration and doubt the Local app flag.

Could you share some suggestions on this?

Thanks,

Usha

[Andre_Fischer · Accepted solution]

Hi Usha,

the flag 'Local app' indicates where the implementation of the service is done because it can be done on the Hub or on the backend. (see my blog about deployment options ).

If you choose 'Local App' the BEP API will be called on your hub while otherwise it will be called on the backend system to which the RFC destination points to which has been maintained in your system alias definition.

Best Regards,

Andre

This is explanation offered by SAP Help:

Indicates that the System Alias is to be used by BEP

SAP NetWeaver Gateway applications can be developed either on a SAP Business
Suite backend system or on a SAP NetWeaver Gateway hub system. To access the
business logic from an SAP Business Suite backend system the software component
IW_BEP (Backend Enablement and Event Provisioning) has to be deployed in your
system landscape. IW_BEP can be deployed on the backend system or locally on the
SAP NetWeaver Gateway hub system. Communication is handled via system aliases
(RFC destinations).

Use

Set this flag if you use this system alias for an OData Channel application
that has been developed on the BEP add-on which is deployed on the SAP NetWeaver
Gateway hub system.

In this case the system alias information (such as RFC destiation, Web
service group, software version) is not used by SAP NetWeaver Gateway to
call the BEP API (it is called locally). Instead the system alias information is
passed through to the OData Channel application, so that it could then itself
make a call to the corresponding backend system.

[Andre_Fischer · Accepted solution]

when using SAP NetWeaver 7.31 and earlier the NetWeaver version does not tell you the version of SAP Gateway 2.0. For this you have to check the versions of the software components IW_BEP, GW_CORE and IW_FND.

When using SAP NetWeaver 7.40 or later the version of SAP Gateway is typically the version of the SAP Basis.

Please note that the SP levels of SAP Gateway 2.0 do not have the same numbers as the SP numbers used in SAP NetWeaver 7.40

See my document

Best Regards,

Andre

[Usha · Accepted solution]

Hello Andre,

The "Model XXXX  contains error" issue was because local app flag was not set.

i had generated the MPC &DPC classes on the Gw system planning to use  the IW_BEP in the Backend system.

So now when i set the flag the issue resolved.

Thanks ,

Usha