Fox - initial values & compounding

[tom_francis2]

Dear All,

I'm struggling with a fox function in Integrated planning. The function uses characteristics that are compounded, but that can contain initial values. Depending on the situation the system sometimes needs: #, '' or '000' as initial value, however in my opinion the usage is always the same.

Even more, if I reactivate the level for some reason it can be that the fox function that previously worked with # suddenly needs '' as initial value.

Are there any ideas/guidelines on how to tackle this issue?

thanks in advance,

Tom

[Former Member]

Hi,

Ideally you should keep the compounded field in "Fields to be changed". I think you have done dat. I suggest you go and check the such records which where accepting # before in transaction info cube. I think their value have changed.

If you still find it confusing, if you are in dev system just delete requests from the cube from the point after # values are not acceptable. Try running FOX again. See what happens.

For any confusion always see what is a actually available in Transactional Info Cube in RSA1 for that particular function.

Thanks,

Mihir