cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Identifying slow moving items IBP

0 Likes
1,366

We are implementing IBP for Inventory and we have a requirement to identify slow moving items. If shipment history (IOSALES) is less than 500 cases per month, then indicate that product as a slow moving item and use quantity (cases) instead of days for the shipment history. However, the indicator to mark it as a 1 in the month, not week, for the slow moving item is not working. Right now we have the below configured but it’s not putting a 1 when there is < 500 cases in the current monthly bucket. Do you know what could be wrong with the below equation?

IF(“PERIODID1” = “$$PERIOD1CU$$”, IF(“IOSALES@PERPRODLOC”) < 500, 1, 0), NULL)

Accepted Solutions (1)

Accepted Solutions (1)

0 Likes

Hi All,

We decided to use the Manage ABC/XYZ Segmentation tile and using the ABC and XYZ segment thresholds to fulfill this requirement.

Thanks,

Melanie

Answers (7)

Answers (7)

Irmi_Kuntze
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi Melanie

can you share which time buckets you have available at all, just week and month?

Than periodid0 would be weeks and periodid1 would be month, and your formula should be ok.

And I understand your PER means months?

But if you have in addition e.g. year and quarter, than periodid1 would be the year and not the month, quarter would be periodid2 and month would be periodid3, and your formula would be on the wrong level.

Irmi

AyanBishnu
Active Contributor
0 Likes

You should use the AND operator for this kind of requirement. and you expression was also wrong. Please use the expression provided below and let me know the outcome.


IF("PERIODID1" = "$$PERIODID1CU$$" AND IF("IOSALES@PERPRODLOC" < 500, 1,0))

ankpatel
Contributor
0 Likes

Melanie, yes if you dont have WKPRODLOC configured it won't work as there will be inconsistency and it will require to change for corresponding input and output KF.
Can you share a screenshot of PERPRODLOC planning level, as I would like to see what is selected in it.

0 Likes

Hi Ankur,

We don't have the planning level for WKPRODLOC as the configuration is all at PER not WK. Week is our lowest time profile level. When I try adding WKPRODLOC to the calculation, I get the error "the planning level for the output key figure and the planning level for the input key figure must match in the calculation definition."

Thanks,

Melanie

ankpatel
Contributor
0 Likes

Hi Melanie,

Can you try using below calculation, change planning level of IOSALES.

IF(“PERIODID1” = “$$PERIOD1CU$$”, IF(“IOSALES@WKPRODLOC”) < 500, 1, 0), NULL)

Regards

Ankur

0 Likes

Hi Anurag,

Apologies, below is actually how it is configured without the extra parenthesis. Do you know what else could be wrong with it? I'm not sure why the 1 isn't taking when the cases are < 500 for the given month.

IF(“PERIODID1” = “$$PERIOD1CU$$”, IF(“IOSALES@PERPRODLOC” < 500, 1, 0), NULL)

Thanks,

Melanie

gurucharanscm
Contributor
0 Likes

Hi Melanine -

Please don't mind me asking, I hope you are aware the logic you wrote works only for the current month and that you are not expecting the 1's or NULLs across the entire historical planning scope?

Thanks,

Regards - Guru

0 Likes

Hi Melanie,

I see the syntax mismatch in the calc logic , There is an extra ")" in the calc.

Didn't ypu get any error?

Regards,

Anurag