Error 'Specify time within permitted value range' in standard SAP Work Manager 6.5

[former_member286937]

Hi All,

I am getting this error 'Specify time within permitted value range' while syncing Work Manager 6.5 after completing an Work Order Operation. Below is the screenshot.

Need an advice on this.

Thanks

Abhilasha

[mark_pe]

Abhilasha,

Hello. Error 13 is a generic error tied to an error in your "Transaction". A transaction is normally a capture of what was filled out on the screens on all the fields. The actual error which states: "Specify time within permitted value range" is claiming that one of the fields (of property type dates or time or duration) was entered which lies beyond or outside the expected business value in the backend.

For example:

1) If you have a start schedule or planned start of February 22, 2019 at 8:00AM and a duration or expected finish time of February 22, 2019 at 12:00PM then you need to have completed the operation or order within those limits. <-- Please note this is just a theoretical example and your system may have a particular workflow or business rule that needs to be carried out.

To resolve this issue, you need to figure out in the main transmit logs or smpservername-smp-server.log (with details or debug enabled) the transmit or completed time. Compare this to what is expected in the backend for your actual time. Most likely the time indicated could be outside the scope of what your business rule expects.

What could be the root cause?

A) Either you have worked on the operation or workorder for a long time and the system just lost track of all the updates of time without you synching to the backend. (Example of issue: You start, hold, start, hold, start, hold, start, hold and so forth without transmitting for a long time - this could technically have a limit and may sometime just use the transmit time instead to be the official time submitted to the backend which could already be out of scope of your expected finish time).

B) You can have some time zone issue wherein you have a device that may be using a shared time zone or an operative/user who crosses time zone between routes/destination without properly setting up what time zone to use or something in the time zone issue (Under TimeZoneAlias or TimeZoneName category).

C) Another theory is that your system allowed an "Edit" <-- normally not allowed by default as this could be a customization on a completed work wherein the user tried editing a time at a later date. The time/date timestamp is normally captured during the time when you click complete. Editing at a later time may have problems unless the application was highly customized to accept editing.

The above are some of the scenarios that may happen.

Hopefully this could help you out.

Regards,

Mark