Active (ValidFor) vs. Inactive (FrozenFor)

[Former Member]

Hello Experts,

I am encountering unusual behaviour on the active (ValidFor) status of our items.

I discovered this when trying to create a report on ValidFor field but was not retrieving certain records that I knew were active.

The problem was that records which appeared active on the UI (radio botton toggled on Active) were still holding an N value for ValidFor despite also holding a FrozenFor value of N.

This seemed incorrect but I did some reading which demonstrated how items could be both active = N and inactive = N and that FrozenFor is the manager for whether items can be used in marketing docs, reports, etc.

However, the unexpected behaviour is that when I update the particular item which has ValidFor = N and FrozenFor = N in any way whatsoever (an update to the description etc. NOT the status) and click update. The ValidFor field is automatically switched to Y which accurately reflects the true status of the item and what the user sees in the UI.

Secondary observations are that new item codes have a default value of ValidFor = Y and that the item records in question ARE being actively used in marketing documents which did not cause the value to change to Y.

I am thinking it may be an inconsistency derived from 2007 to 8.8 conversion long ago that went undetected. I am considering using DTW to switch ValidFor to Y on these items to improve the data's integrity for reporting.

Thus, I am wondering if this is expected SAP behaviour that Item Update causes the field to change and whether I should update all my records to reflect the actual status?

Any thoughts would be appreciated.

Thanks very much,

Richard

[jitin_chawla · Accepted solution]

Hi,

The Active (validfor) field displays 'N' even if you have the active field radio button marked for the item in the table.

The items when updated changes the field (validfor) to 'Y' and then you can get the correct status.

Check this query for detecting the Active Items :

SELECT T0.[ItemCode], T0.[ItemName] FROM OITM T0 WHERE
T0.[ValidFor] = 'Y' or T0.[ValidFor] = 'N' and T0.[FrozenFor] ='N'

Check if this helps.

Kind Regards,

Jitin

SAP Business One Forum Team

[former_member711498 · Accepted solution]

Is this condition as

T0.[ValidFor]='Y'or ( T0.[ValidFor]='N'and T0.[FrozenFor]='N' )

is this applicable for OCRD table too?

[Johan_H · Accepted solution]

Hi,

Yes, it works the same way.

Regards,

Johan

[Former Member]

Hi Richard,

Active (ValidFor) field is not a common filed to be used in the first place. It is only for certain special items that has default to be only valid for a short periods.

It should be 'N' for most of the items if no use of this feather.

Thanks,

Gordon

[Former Member]

Thank you for the responses. I can see the intended function of ValidFor now.

Given this, I still find it very strange then that the field automatically changes to Y when an update is made on the Item Master of any particular item. It does not seem to fit with the logic of ValidFor. Can anyone comment on this last point?

[Former Member]

My option will be not use it at all if this feature is not applying to your business.

In what report you need this field?

[jitin_chawla]

Hi,

Validfor field is available to define the Item (special/normal) to be available for selection on the Choose from List and when selected as active it is available for creation of documents and other inventory related posting.

The default display of the field value is 'N', when the same is updated you get 'Y' displayed as the same is updated.

If you see , you have the similar sort of working in the G\L Account field (OACT table).

Kind Regards,

Jitin

SAP Business One Forum Team

[Former Member]

Hello,

You are correct. What we need is 'not equal to' FrozenFor as the purpose is to display items that are NOT inactive which I thought ValidFor would have displayed.

Problem solved, thank you.

Richard