Skip to end of metadata
Go to start of metadata

xApp Mobile Asset Management Frequently Asked Questions

How can I estimate the communication cost of synchronizing over an external network like GPRS?

Valid For: xMAM 2.5

Please refer to the xMAM Client Data Calculator available in the Service Marketplace.

back to top

How can I estimate the client data volume for xMAM?

Valid For: xMAM 2.5

Please refer to the xMAM Client Data Calculator available in the Service Marketplace.

back to top

Are there any release restrictions for xMAM 2.5?

Valid For: xMAM 2.5

Yes. Every service release of xMAM 2.5 has a release restriction OSS note. See below:

786841 - Release restriction note SAP Mobile Asset Management 2.5 SR1

848799 - Release restriction note SAP Mobile Asset Management 2.5 SR2

901772 - Release restriction note SAP Mobile Asset Management 2.5 SR3

945240 - Release restriction note SAP Mobile Asset Management 2.5 SR4

1000836 - Release restriction note SAP Mobile Asset Management 2.5 SR5

1076860 - Release restriction note SAP Mobile Asset Management 2.5 SR6

back to top

Are there any release restrictions for xMAM 3.0?

Valid For: xMAM 3.0

Yes. Every service release of xMAM 3.0 has a release restriction OSS note. See below:

901607 - Release restriction note SAP Mobile Asset Management 3.0 SR0

937916 - Release restriction note SAP Mobile Asset Management 3.0 SR1

952998 - Release restriction note SAP Mobile Asset Management 3.0 SR2

992628 - Release restriction note SAP Mobile Asset Management 3.0 SR3

1046823 - Release restriction note SAP Mobile Asset Management 3.0 SR4

back to top

What are the minimum requirements for xMAM 2.5?

Valid For: xMAM 2.5

The minimum requirements for xMAM 2.5 are:

Front End

Pocket PC 2003, Win CE based devices, or Win 32 based laptops/Tablet PCs

MI Client:

  • xMAM 2.5 with R/3 4.6 B, C, 4.7 use ME 2.1 SP03 (w/WebAS 6.20)
  • mySAP ERP (with xMAM 2.5) use MI 2.5 (w/ WebAS 6.40)

MRI 1.0 (Mobile RFID Interface for RFID integration)

Middleware

MI Middleware:

  • For R/3 4.6B, C, 4.7: WebAS 6.20; J2EE Server; Java Connector (JCO)
  • For mySAP ERP: WebAS 6.40

xMAM 2.5 Sync BO definition

Backend

R/3 4.6 B,C w/ PI2003.1_4.6B,C & PI2004.1_4.6C

R/3 Enterprise (4.70x1.10/2.00) w/ PI2003.1_4.70 & PI2004.1_4.70

ECC (Enterprise Core Component within mySAP ERP) w/ PI2004.1_5.0

Recommended devices

PPC 2003 Xscale Processor (PXA255) 400MHZ w/ at least 64 MB RAM

RFID related information

The front end device must be RFID enabled (RFID readers) with an SAP certified interface

Recommended RF Tag size to be used with xMAM 2.5 is 256Bits

back to top

Is RFID supported with xMAM 2.5?

Valid For: xMAM 2.5

Yes. xMAM 2.5 does support RFID. xMAM 2.5 has 3 scenarios that use RFID. The scenarios are as follows:

  1. Work order on the mobile device is locked and cannot be accessed until the user reads the RFID tag of the technical object.
  2. After the completion of an order, service related information is written onto the RFID tag.
  3. The creation of a new order / notification is supported by using the master data stored on the RFID tag.

In order to successfully employ the xMAM RFID Management functionality, 3rd party vendor RFID driver software is required to be installed to the hardware RFID-reader device.

Please see OSS note 734102 - RFID 3rd Party Software Installation/Deployment for more detailed information.

Also more related OSS notes to RFID are:

809355 - xMAM RFID Tag Structure Enhancement Guide

793100 - xMAM RFID tag initialization instruction

791037 - SAP Mobile RFID Interface Software Installation/Deployment

back to top

What are the composite OSS notes for xMAM?

Valid For: xMAM 2.0; xMAM 2.5; xMAM 2.0

The composite notes for xMAM are central locations that help you locate all related topics, corrections and documentation to the specific releases of xMAM. They are as follows:

xMAM 2.0 : OSS 617494 xMAM 2.5 : OSS 723380 xMAM 3.0 : OSS 833458

Also, each service release such as xMAM 2.5 SR2 has a release note. The release note in this case is OSS 848799

back to top

How can I make the client xMAM application synchronize synchronously?

Valid For: xMAM 2.5; xMAM 3.0

Synchronization is defaulted to perform in a 2-step sync process. The initial sync is required to prepare the data on the SAP MI web application server and the second sync is required to download the data onto the client. A repetitive sync add-on may be deployed on the client device to modify this behavior (see OSS Note 745316). Alternatively, you can modify the ALMConfig.properties file (located in \MI_installation_directory \ webapps \MAM25 \WEB-INF \classes) in order to enable a 1-step sync process. To do so, comment out the original UPD_SYNCTYPE and DWN_SYNCTYPE lines and edit their copies as shown below: #UPD_SYNCTYPE=ASYNC UPD_SYNCTYPE=SYNC #DWN_SYNCTYPE=ASYNC DWN_SYNCTYPE=SYNC
Note that this is an application setting and to activate a 1-step sync process, you must perform the changes mentioned above, restart the Mobile Infrastructure, log into Mobile Infrastructure, and access the xMAM application home page. This will ensure that the synchronization process is ready and when synchronization is triggered, it will perform a 1-step sync process.

back to top

Are there xMAM Business Logic API's that I can reuse?

Valid For: xMAM 2.0; xMAM 2.5

Yes. xMAM 2.0 and xMAM 2.5 have business logic APIs that can be used to create custom enhancements. An xMAM enhancement document is available from service marketplace that explains a usage and provides examples:

Please see link: https://service.sap.com/~sapdownload/011000358700004089052004E/MAM_EnhG.pdf

back to top

Is there a way to view all the data that has been downloaded to the client?

Valid For: MAM 2.0; MAM 2.5; xMAM 3.0

Yes. In order to view the data on a Windows based environment:

  • From the drop-down selection list, select the syncbo id and clink on the ?View? button

back to top

Is DB2e supported with xMAM 2.5?

Valid for: xMAM 2.5

Yes. xMAM 2.5 does support IBM DB2e. During the installation of the client device, DB2e must be installed after all Mobile Infrastructure patches have been deployed and before the xMAM application is deployed. Please refer to OSS note 677476 for more information on DB2e

back to top

Is DB2e required for xMAM 3.0?

Valid for: xMAM 3.0

Yes. DB2e is required for xMAM 3.0 as explained in OSS note 960969. During the installation of the client device, DB2e must be installed after all Mobile Infrastructure patches have been deployed and before the xMAM application is deployed. Please refer to OSS note 677476 for more information on DB2e

back to top

How can I activate the order printing functionality?

Valid For: xMAM 2.0; xMAM 2.5

This functionality is available as of SR02 of xMAM 2.0 but is deactivated per default. There are two properties contained in the ALMConfig.properties file that have to be activated. SAP Note 701368 explains how to activate this properties. After changing the value of the properties mentioned above to true, there is still a problem. You get the "Order report" link in the order detail page that opens the order report to be printed. After restarting the application you get the error: "Page cannot be displayed". This is due to a bug in the web.xml file that has to be fixed. To see how to fix this problem, please see internal CSN Message 416212. This problem will be solved in future releases of the applicaiton.

back to top

How can I configure the system to delete outstanding orders from the device for which all operations for one user where finally confirmed?

Valid For: MAM 2.0; MAM 2.5

Please follow these steps:

I. Backend:

Open Operation variant in the MAM order processing profile: SPRO -> Plant Maintenance and Customer Service -> Maintenance and Service Processing -> MAM Customizing settings -> Determine order processing -> Detail view -> Selection Report Enter the value CNF (Confirmed) in the "Status exclusiv" field. Save your changes.

II. Middleware:

Start replication Job for SyncBO MAM_090 and MAM_095 for MAM 2.0 or

Start replication Job for SyncBO MAM25_090 and MAM25_095 for MAM 2.5

III. Frontend:

Start synchronization in order to download the new customizing settings to the device. Af of now when final confirming all operations assigned to one technician on the Frontend, the corresponding order will be deleted from the device after synchronizing, no matter if this order was still not completed on the backend.

back to top

After I sync an order created in the PDA it disappears from the local orders of the PDA, and in the R/3 System the order doesn't exist.

Valid For: xMAM 2.0; xMAM 2.5

(Presuming that you the server & the backend has been configured correctly as per the xMAM configuration guide)
Whenever you try to create an order on the client, the default value for 'Order type' is 'PM01' and for 'PM Acttype' (maintenance activity type) is 'Inspection'. This is an invalid combination and rejected by the backend. Hence, the order is deleted from the client on error status.Also, if the "Automatically Release Flag" is not checked for the specific order type, then it will be removed from the client device.

back to top

After deploying the xMAM application on the client, only 'User View Manager' link is visible. Do I need to do any configuration?

Valid For: xMAM 2.0; xMAM 2.5

A1.

In the Smartsync Troubleshooting guide, under 3.1.5 the xMAM User View Manager problem is described.
The guide contains a helpful 8 Point checklist for the User View Manager / No Application Data Problem in xMAM.

A2.

1. Make sure the User has been assigned data on the backend (transaction SPRO),
2. RFC destination has been properly configured on the MI server to connect to the backend
3. Run replicator for all the xMAM T01 syncBos;
(MAM25_001, MAM25_010, MAM25_016, MAM25_017, MAM25_030, MAM25_031, MAM25_040, MAM25_041, MAM25_050, MAM25_070, MAM25_090, MAM25_095). Also schedule the replicator, so that you have up to date data.

back to top

How can I install the Mobile Work Clearance Management Application?

Valid For: xMAM 3.0

Please refer to OSS note 997697.

back to top

How can I install the signature capture functionality for xMAM 3.0?

Valid For: xMAM 3.0

Please refer to OSS note 897289.

back to top

  • No labels