There could be a few reasons why the graph is not showing data.The first is that the graph is based on a snapshot of data, the offsets of which can be set via Resource Basic Data. Expectations would be that the snapshot is refreshed via a reoccurring scheduled task and would only need to be manually refreshed in specific circumstances. The second is that the graph can also be filtered based on your user's Resource Analysis Parameters, for example by a specific company, a specific status, a specific project or group of projects etc. As you have already checked that the demand information is available in Resource Activity and that there is a corresponding Resource Activity Load then it should be one of these others that would be impacting what data is available in the graph.
One possible explanation is the way that the demand's load is spread. Due to rounding and summing there is an adjustment demand made on the first day of the linear spread period (even of non-linear profile spreads they are broken down into linear periods). Therefore if the spreading results in relatively small daily amounts that need to be adjusted for rounding then it is possible for a negative amount to be created in order to adjust for differences due to rounding.So for example imagine that 7.5 hours were planned over 100 working days – this would result in a linear spread of 0.075 hrs per day – this is rounded to 0.08 hrs per day and when checked summed this results in 8 hrs being spread – therefore to adjust for this a correction demand is created for the first day of the linear spread period of -0.42 hrs – as in screenshotsSo it possible for some demands to appear to be negative – do not know if this would be the cause in your case.
Hi @paguin ,I cannot be certain but I am guessing it is a limitation within the IFS Enterprise Explorer framework that the percentage format is not recognised when the number format is using English(India).I tested this within the Aurena client by setting the browser to use English(India) and it displayed the percentages correctly.So it relates to the client and this seems to be an application-wide issue, not just for this specific form - for instance here is a screenshot of Document Revisions when using the English(India) format - the Progress field is using the percentage format. But using English(United Kingdom) it shows correctly formatted Oddly when running a query it correctly coverts it, i.e. the query can be written as the percentage value rather than the decimal so the query dialog seems to be correctly converting the percentage format just not when it is being displayed in the form.So a little more digging shows that the only difference in the India format to the UK format is
Hi @paguin I am a bit confused over the scenario, therefore to clarify, are you saying that this is device based and that using the same user on one machine works correctly but using that same user on another machine it does not work correctly?If it was user specific it could have been User Profile/Custom Field related but if it is device/machine specific then I am not sure what might be causing it unless there was something within the device's Regional Settings but I did not think that covered the percentage format.So unfortunately I do not think I can give any further suggestions as to what may be the cause of this formatting issue. Thanks and regardsHugh
Hi @paguin I suppose any solution depends on why the client being used is not using the Percentage format.The core client looks like it is using this format correctly therefore is the core client being used?If not then has the client being used been customised or configured at all?If so then you will most likely need to arrange for this to be investigated further by whoever did that customisation.Thanks and regardsHugh
Hi Pankaj,In the core Apps10 application this field has a percentage format applied to it. The function associated with the field returns a decimal but in the client, due to it having the percentage format applied, this is displayed as required also showing the '%' sign too. Therefore the assumption from that is the client being used in your example does not have the percentage format being applied to the field.Thanks and regardsHugh
As has been suggested the default Resource for the Project Time Reporting is picked up from the Primary Parent Resource defined against the employee's resource for the project's company.When it comes to editing the Resource on the project transaction then this is only possible if the Company Property of EDTRESPT has been set to TRUE - accessible via the Company Details form. Doing this should then allow the Resource ID to be both visible and editable within the Job Details available via the 'Details on Current Row…' context menu.For the specific issue of a missing LOV and the value disappearing when saving then I am assuming from the earlier screenshot and the highlighted field that the header of Resource Group related to the Work Order lines and that there is no corresponding mapping for this field for the Project lines.Hopefully a combination of these pieces of information will give you a resolution.
Hi RobertJust for clarification, how have the intervals for the Day Type used in the Schedule been configured?Thanks and regardsHugh
When drilling down into Resource Activity Load Detail it is normally from a specific section in the chart - therefore the details seen initially relate to that specific demand, whether it is Project Planning, Work Task, Absence etc.Therefore as the demands are treated as separate records then so is the capacity.So in order to see the capacity values in Resource Activity Load Detail then either drill down from the graph by clicking the capacity line point or, within Resource Activity Load Detail, query for records where either the Activity Origin or the Origin LU is 'Resource Capacity'.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
