on 07-01-2014 7:14 PM
Dear Experts,
I am running SAP Work Manager 6.0 with Agentry Server v6.1.4.179 and SAP ECC 6.0 with SMFND 610_700 SP01 and SMERP 610_700 SP01 and Agentry Client v6.1.3.10200 on an iPhone.
When I display from the iPhone the "Valve Water Flow in m3/h" counter, the UOM is represented as "***"
The "Pump Bearing Oil Level in mm" counter UOM is displayed properly.
The Measuring Points are associated to a FLOC. A work Order with this FLOC has been transmitted to mobile device.
Thanks for your help.
Didier.
Reading Points definition in SAP:
Reading Points on iPhone:
Tags edited by: Michael Appleby
Dider,
That is how Apple displays text that is too large for the available space. I suspect the UOM "M3/H" won't fit in the space so Apple uses the *** to indicate it is too large for the field. You can try going into the editor and increasing the size of the field or modifying the style to reduce the font size so it can be displayed.
--Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bill,
Thanks for your reply. In fact , I have the same problem with the WPF client and if I enter a reading value, I will get the following error message during the transmit. "Unit *** is not created in language EN"
WPF client display:
Transmit error:
Agentry log:
readDataObjectMeasuringPoint::begin
BAPI::begin
User::getString::begin
User::getString::Property: transaction.point = 26
User::getString::begin
User::getString::Property: transaction.shortText =
User::getString::begin
User::getString::Property: transaction.reading = 0
User::getString::begin
User::getString::Property: transaction.UOM = ***
User::getString::begin
User::getString::Property: transaction.referenceObjectNumber = OR000004000293
User::getString::begin
User::getString::Property: transaction.prevCodeGroup =
User::getString::begin
User::getString::Property: transaction.prevCatalogType =
User::getString::begin
User::getString::Property: transaction.ValuationCode =
User::getString::begin
User::getString::Property: transaction.isCounter = False
User::getString::begin
User::getString::Property: transaction.codeTextOnly not found, returning empty s
tring
User::getString::Property: transaction.codeTextOnly =
User::getString::begin
User::getString::Property: transaction.description = Pump Bearing Temperature
User::getString::begin
User::getString::Property: transaction.skipReading = False
User::getString::begin
User::getString::Property: transaction.status not found, returning empty string
User::getString::Property: transaction.status =
User::getString::begin
User::getString::Property: transaction.IsNotRead = False
User::getString::begin
User::getString::Property: transaction.tmpReading not found, returning empty str
ing
User::getString::Property: transaction.tmpReading =
User::getString::begin
User::getString::Property: transaction.CodeGroup not found, returning empty stri
ng
User::getString::Property: transaction.CodeGroup =
User::getString::begin
User::getString::Property: transaction.code not found, returning empty string
User::getString::Property: transaction.code =
readDataObjectMeasuringPoint::SkipReading=False
User::getString::begin
User::getString::Property: transaction.point = 26
User::getString::begin
User::getString::Property: transaction.shortText =
User::getString::begin
User::getString::Property: transaction.reading = 0
User::getString::begin
User::getString::Property: transaction.UOM = ***
User::getString::begin
User::getString::Property: transaction.referenceObjectNumber = OR000004000293
User::getString::begin
User::getString::Property: transaction.prevCodeGroup =
User::getString::begin
User::getString::Property: transaction.prevCatalogType =
User::getString::begin
User::getString::Property: transaction.ValuationCode =
User::getString::begin
User::getString::Property: transaction.isCounter = False
User::getString::begin
User::getString::Property: transaction.codeTextOnly not found, returning empty s
tring
User::getString::Property: transaction.codeTextOnly =
User::getString::begin
User::getString::Property: transaction.description = Pump Bearing Temperature
User::getString::begin
User::getString::Property: transaction.skipReading = False
User::getString::begin
User::getString::Property: transaction.status not found, returning empty string
User::getString::Property: transaction.status =
User::getString::begin
User::getString::Property: transaction.IsNotRead = False
User::getString::begin
User::getString::Property: transaction.tmpReading not found, returning empty str
ing
User::getString::Property: transaction.tmpReading =
User::getString::begin
User::getString::Property: transaction.CodeGroup not found, returning empty stri
ng
User::getString::Property: transaction.CodeGroup =
User::getString::begin
User::getString::Property: transaction.code not found, returning empty string
User::getString::Property: transaction.code =
create::/SMERP/PM_DOMEASUREMENTDOC_CRT Connection ID: com.sap.mw.jco.JCO$Client@
42499d6d
create::Function /SMERP/PM_DOMEASUREMENTDOC_CRT created
setImportParameters::TIMESTAMP_FROM_MOBILE=20140701214858
setImportParameters::COMMIT_WAIT=X
setImportParameters::MOBILE_USER=MJONES
setImportParameters::USER_GUID=005056913EE61EE3B5A27E3E2BC46F0D
setImportParameters::MIDDLEWARE_CALL=X
setParameters::begin
setParameters::POINT=26
setParameters::IDATE=20140701
setParameters::ITIME=172024
setParameters::MDTXT=
setParameters::READR=MJONES
setParameters::RECDV=0
setParameters::RECDU=***
setParameters::RECDVI=X
setParameters::CODGR=
setParameters::VLCOD=
setParameters::CODCT=
setParameters::IV_WORK_ORDER_OBJECTNR=OR000004000293
execute::::MJONES::before BAPI execute: /SMERP/PM_DOMEASUREMENTDOC_CRT
User::rethrowException::begin
User::rethrowException::Exception caught: Unit *** is not created in language EN
Dider,
This is a known issue and the resolution is under SAP note:
From your logs above:
..
..
User::getString::Property: transaction.UOM = ***
..
..
The release of the SAP note is as follows:
2032579 - Measuring Point Unit of Measure (UOM) shows *** from complex table and is causing measurment document to fail while transmitting form mobile.
This should resolve your issue. Have a good day.
Regards,
Mark Pe
SAP Senior Support Engineer (mobility)
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.