Question:
Hi everybody,
I need your help with this situation:
I have defined a resource on APO which has a wide open calendar (365 days as working days). I need to define or create a specific time interval to indicate non working days during 2 specifics weeks)
I just see the option to create time intervals for working days but not for non working days period (similar as you can do it on R/3)
Can I do this on APO ? How I can do it without touching the Plant Calendar Definition ?
Any help will be wellcome,
Regards,
abetanco
Answer:
Adimas
The simplest way to mark days as unavailable against a resource (especially if it is for s defined period) is to create the period as downtime on the resource. In transaction /SAPAPO/RES01 you can select the "Downtimes" tab for your resource and enter the start and end dates of your non-working time there. Also you can right-click on the resource in both the PPT and DSPB and assign non-working times there.
Regards
Parksy
Answer:
He's right you know but what Parksy has said does not require a capacity variant that you mentioned in your msg title. You use a capacity variant only when you wish to use more detailed capacity profiling like shift sequences. From your description of the problem I would suggest that you do what Parksy mentioned and ensure that you do not have a capacity variant quoted.
Mark
Answer:
I saw your recomendations and it looks good for us except for the fact that if this situation is bigger than we can predict the planned will need to manually create these downtimes periods many many times during the year.
Could be another easy way to do this ? Any other idea ? like create intervals or something similar ?
Regards,
Adimas
Answer:
You could also creat a detailed planning calendar assigned solely to that resource. If you want to take it to a detailed level and have a good idea in advance of when the downtime will be this is a possibility. We did it where a specific shift pattern determined availability of this resource (one of three shifts was not qualified to operate the machine). We knew the shift pattern at the start of the year and so could plan it out. Since that pattern was not regular we decided not to use shift allocation, but I do have to say that entering a detailed calendar for a full year is still quite a lot of work and only really useful for us as we only had to do it once a year.
hope this helps.