IBP Workng Attribut end and start date

[OliverA41]

Hello,

I have an customer attribut "Start Date" and "End Date". This attributs are in the MD product.

Now the systen should be considered this attributs. For example. the disaggregation should only work for this time range.

Exampel

Start Date: January.01
End Date. July.30

I insert 1400 pc. on year level. As result I expected 200 pc on month level (Jan until Jul.)

Is it possible, that the algorithm (Disaggregation Operator, Copy Operator, Forecast,...)can considered date attributs

Thanks in advance

Oliver

[drbanning · Accepted solution]

A blessing and a curse of IBP is that there are so many different ways to accomplish the same task, if the VBA script does what you need - sweet.

What Irmhild and I suggested keeps all the of the design within config rather than having to execute an external VBA script. But at the end of the day - if the VBA works - use it. Don't let perfection prevent progress.

[OliverA41]

Hello,

for me your solution is not clear for me.

My solution ist, that I develope an VBA script, which read the start and end date attribute. That can be working, with an planning view, which include this two attributes.

with this two dates, the VBA Script should be work as an part of Irmhild's post. I will wokr with an key figure wich content 1 and 0. and the VBA script should insert "1" between Start and End Date and the copy job can only insert Values in n Keyfigure which is not 0.

Regards

Oliver

[drbanning]

another option - would be to have 2 AAKF (example - custstarttrigger custendtrigger)

CUSTSTARTTRIGGER (value of 1) - with the time reference attribute - start date (Referenced in your post)

CUSTENDTRIGGER (value of 0) - with the time reference attribute - end date (Referenced in your post)

Then a KF at the bpl you are wanting to reference - CUSTFCSTSRC calculated - = CUSTSTARTTRIGGER + CUSTENDTRIGGER

The a KF at the BPL for your proportional factors - CUSTFCSTPROPFACTORS = IBP_LAST_SEEN ("CUSTFCSTSRC")

Use that value within your prop factors logic - store it and it will disaggregate down where you have the 1's. In the example you referenced - it would see a 1 in the start bucket and then a 0 in the end bucket. So there would be 1's from Jan1 to July 30.

KF names may change, but that logic should work to give you the forecast windows you are looking for.

Thanks,

dan

[drbanning]

As I re-read what Irmhild - very similar approaches. Like everything with IBP there are multiple ways to get to the same end point. Apologies as I should have built on Irmhild's original post rather than create a whole separate answer.

dan

[Irmi_Kuntze]

Not directly as far as I know, but you can transform that information into a readable way

For example, you could add additional time profile integer attribute to the relevant planning level (e.g. technical week) with the information of the first day of the week in the format YYYYMMDD

Then your start and end data attribute on Product level need to have same format

Now you can build your own logic by comparing these values big > or < or >= or <=

That could for example fill some other KF with value "1" when allowed and otherwise "0", and then you can start to think about how to build your copy operator

Just an idea. But the key point is the time profile attribute which enables you to check if your iteration is within the allowed time frame or not