cancel
Showing results for 
Search instead for 
Did you mean: 

Missing values of linear data in Work Order, while in Functional Location - values present.

0 Kudos

When setting unit of measurement in KM (kilometers), displaying values of linear data in functional location via work order shows blanks instead of values.
When displaying Functional Location directly via search, values are displayed correctly.

If you change that linear data on functional location to have measurement unit M (meter) instead of KM (kilometer), than case with Work Order is also shown correct.

Possibly issue is related to localization?
Please advise what can correct this behaviour.

With Work Orders tab

When you enter WM client, click on the tab Work Orders, pick work order number 400000082, in the details click on the link for Functional location as shown on next screenshot

On the next dialog click on Linear as shown below

And you get this dialog with linear data…

With Functional Locations tab

When you enter WM client, click on the tab Functional Location and than on ->Search.

…and click Finish. Tick the checkbox for the mentioned functional location on the next screen and again on the right corner ->Add selected. Now in Functional location tab you will have something like this

Now click on Linear as shown below

And you get linear data

If you change that linear data on functional location to have measurement unit M (meter) instead of KM (kilometer), than case with Work Order is also shown correct.

Accepted Solutions (0)

Answers (1)

Answers (1)

mark_pe
Active Contributor
0 Kudos

Hello from SAP!

Let us dive through the way you describe the question to help the community analyze it as a team:

Given: When setting unit of measurement in KM (kilometers) <-- At this point let UOM = KM,
displaying values of linear data in functional location via work order shows blanks instead of values.

Result:

Screen: Point Location
Linear: _____KM <-- Only UOM and no values
~~~~~~~~~~~~~~~~

When displaying Functional Location directly via search <-- Using search (filtering), values are displayed correctly.

Linear: 123 KM

If you change that linear data on functional location to have measurement unit M (meter) instead of KM (kilometer) (Variable UOM is now M versus KM), than case with Work Order is also shown correct.

Theories:

The Data coming from a Work Order tab or screen is tied to the Object Properties that it came with when pre-populating the screen during transmission or fetching of the object.

Workorder Object
|______Linear Property

|____- Linear prop <-- this data is from the Object property

Searching could be a property of what exist in a Table that is pre-populated with values is one thing to consider and why this is working versus the Workorder Object is from a read/fetch of the Object Properties.

So at this point, if the issue is with the actual data tied to the Object then it may be that the original values that came during fetching the WorkOrder Object tied to Functional Location may have it save as the basic UOM of Meters versus KM.

There is a chance that there is a rule that could have been missed to pre-populate the value or convert the value from meters to KM in that same screen.

Suggestion is to look at the field for the Linear:____ <-- To see if there are any rules that can help with the conversion of different UOM.

This may require an analysis of the Work Manager editor to look at the value if there are any rules that could be modified or improve or just missing and may explain why M works and KM is lacking values. Also you may look at the backend for the actual values of the Workorder object if it is by default M or KM.

Best Regards,

Mark

0 Kudos

Thanks for the answer, Mark.

Probably issue is in our old SMP - 3.0.8. We are going to update it to the latest SP/PL.

We do not really have an experienced Syclo developer. So we hoped publishing a standard application will be smooth. This is why we decided first to go via easier for us way of getting the latest environment.
So far e opened 2 messages for SAP support 32477/2018 (LAM UOM and 34095/2018 (Android WM 6.4 vs 6.5).

We installed also latest Eclipse Oxygen with latest Agentry Editor. Could this be helpful to publish application via this latest editor or this does not have relation to the problem? And we should dig into the standard SAP application and modify it?

So far we test app on the WPF client. While having multiple issues on Android and impossibility to work with iOS client from App Store. Would upgrading to WM 6.5 be helpful to get Android 7.0 and iOS 11 devices working? Can WM 6.5 this be installed in parallel with WM 6.4 on the same SMP 3.0 server?

Many questions....Thanks Mark.

mark_pe
Active Contributor
0 Kudos

Andrei,

Just some answers tied to your follow up questions:

Q#1: We installed also latest Eclipse Oxygen with latest Agentry Editor. Could this be helpful to publish application via this latest editor or this does not have relation to the problem? And we should dig into the standard SAP application and modify it?

A#1: The issue presented here could be a variety of factors. As stated, one may need to review the logic inside the Editor to see what could be presented in there if it is a logic issue or a limitation issue. Simply upgraded the IDE (Eclipse) may be limited to fully fix the functionality unless the issue is a deprecation of functionality on older/newer system.

Q#2: While having multiple issues on Android and impossibility to work with iOS client from App Store. Would upgrading to WM 6.5 be helpful to get Android 7.0 and iOS 11 devices working?

A#2:

Each Agentry OS client are their own existing executable designed to work in the OS they have been branded with. If you have issues tied to Android and/or iOS they may exist in those client based on the current limitation/functionality of their software tied to that OS. What I mean is either the condition of failure may only exist in that type of OS and not the other.

In general, all newer patches are tied to reported issues in SAP. The more the users in the field test different functionality there could be reports of issues and the newer the client and release the likelihood of a fix will also exist. So upgrading to newer client device are for newer reported issues that were fixed or fixes tied to newer OS (or backlog of issues that still yet needs to be fixed). Sometimes an upgrade could also not be warranted if the OS of your mobile devices are older which requires older version of the client.

Q#3: Can WM 6.5 this be installed in parallel with WM 6.4 on the same SMP 3.0 server?

A#3: Based on reports of issues, I mean based on past history of people who reported an issue or a ticket to SAP support, if there is a library collision of the same methods called against the same backend (ERP or CRM) there is a risk of collision. From a platform perspective, the developers will say it is okay (SMP 3.0). From a product perspective (SAP Work Manager team), they may claim that there may be a risk. From an SAP support perspective, I just shared you the answer to the above.

Reference: https://blogs.sap.com/2016/06/15/best-practice-smp-30-agentry-updating-cockpit-deployment-patching-b... (Please also see the other references in the KBA listed here).

Best Regards,

Mark Pe
SAP