cancel
Showing results for 
Search instead for 
Did you mean: 

Issues while working with SAP Asset Manager 1911

neha_mahanty
Active Participant
0 Kudos

Dear Team,

I am working on the configuration of SAP Asset Manager 1911, This is our first implementation hence I am facing lot of issues and also have many queries about the applications.

I have followed the SAP Asset Manager Installation Guide

1. S/4 HANA 1911 had inbuilt Mobile addon for Asset manager , its activated and config panel is showing all the details. odata service test result is successful in backend

2. SAP Cloud Platform configuration is done

3. Application meta data is imported in SAP Web IDE and deployed in SAP Cloud Mobile Services

4. We are using the standard application client from Google Play Store. When I try to connect the client to Mobile service it gives error as "Offline OData Initialization Failed"

I am unable to find the cause , below are few queries , It would be great to get some guidance

Queries:

1. How do I test if the application is properly deployed in Mobile Service. In MobileServices - Native/Hybrid - App update - This shows

Operating System Type Description Revisions

Mobile Development Kit App Modeler An app modeler application 2

Does this shows that application is deployed ?

2. Can I test the Asset Manager application directly from Web IDE like we do with Fiori applications ?

3. While mapping the principal Propagation , do we need to map the cloud platform id with backend id in EXTID_DN.

How it should be , what needs to be put in Certificate subject?

External ID USER

CN = <Cloud platform ID>..... <Backend ID>

4. When I imported SAP AssetManager meta data and deployed in the services, it also created a new application package "MDKWebpackFactory, what is the significance of this .

It would be great to get some expert advice

Looking forward for your guidance

Also is there any training ( Open SAP/ Learning Hub/SAP Paid) for SAP Asset Manager , I am intrested in getting a proper training , If anyone has any idea please share

Thanks and Regards

Neha Mahanty


0 Kudos

Hi Neha,

Good Day, Did you fix Asset Manager issues? I'm trying to configure Asset Manger 2105. But my destination

DEST_SAM2105_PPROP is throwing 503 error. Can you please help on this

Accepted Solutions (0)

Answers (2)

Answers (2)

neha_mahanty
Active Participant
0 Kudos

Hi James,

Thank you very much,

As you suggested we checked all the logs and there is some settings missing from basis end like SSL certificate , thats why the connection was not established. Basis team is working on the same.

Meanwhile, Can you please confirm if I have done the proper mapping of services & destination in web ide and deployed the application please. ( We have followed the same naming convention as given in the SAM installation documents.)

Also the offline configuration is done based on SAP document

This is how the application looks in SAP Mobile Services

it would be great If you can confirm my settings are correct or require any modifications.

Thanks and Regards

Neha Mahanty

james_murphy01
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Neha,

As you are doing an initial sync from the play store client, it will first try to sync with the latest (currently SAM2005) metadata. As this is what the app store client is built and deployed with. You should get a SCPms popup/prompt to update the application. This will then push your SAM 1911 metadata down to the device. After this the application should be able to then sync provided the PProp is configured correctly.

If you are still having issues, could you check the SCPms logs for the error you are receiving.
this could give more information as to where the error is occurring. i would also recommend viewing the ICM trace file for info related to authorization and PProp cert issues.

The MDKWebpackFactory file is the MDK app bundle that is published to the SCP mobile services.
each time you publish your app your changes are bundled into this file and deployed to SCPms.

When deploying your app from WebIDE you should see a deploy successful and app revision number. Similarly as you started you can see this revision number in the app update feature in SCPms.

Currently there is no way to test the SAM app from the WebIDE/SCPms in a mock environment.
If using basic auth you can test the OData destination data via the destinations tab. however in order to use the application this needs to be switched to Principal Propagation again.

An additional feature is the Network trace. this can also help in RCA for SCPms applications. this is designed only for short term debugging and not monitoring. this traces the network traffic for your application.

-James.

neha_mahanty
Active Participant
0 Kudos

Hi James,

Thank you very much !! This is really great information.

I am using Principal Propagation setting. In Mobile Service Destination, I tried to check the Odata Destination check , it gives me error as "check the path , destination.. etc" and does not show and result

Does this test only works with Basic Authentication and not with Principal Propagation?

I connect the client and it gives me that popup "Check for updates" then after some time gives the error. I think the principal propagation setting still needs to be corrected as I can see 401 and 403 error

As you suggested I will check all the error logs .

Thanks very much

Neha Mahanty

james_murphy01
Product and Topic Expert
Product and Topic Expert

Hi Neha,
Yes, as the Principal propagation would not have a user to propagate down to the service provider. Using Basic auth we can authenticate the requests to the service provider.
If you are getting an error it is likely the Principal Propagation set up where the issue is arising.
I would recommend checking:
- ICM Trace file
- Gateway Traces

To add you can check the Service int he GW client to see if the get requests execute successfully.
The GW traces will show if any OData requests errors exist. ICM should show the auth issue or cert issues/challanges in the onprem system.

For your Certs set up have you included the KEYCERTSIGN property in the CA cert. This certificate will be used to sign the short-lived certificate that will be passed to the backend to authenticate the logged in user.

-James.