on 03-13-2007 7:28 PM
We recently upgraded our system from 3.0 to 5.0 and are experiencing new errors when act/deact material iModels.
The error reads this: "An indicator for APO relevance is not set for material", it suggests that we run report, RAPOKZFX, at a later time to fix the errors.
The diagnosis reads: "An error occurred while setting the indicator for APO relevance (APOKZ). This happened because the corresponding data record in the material master data is currently locked."
We understand what this field is but our question is why are we getting these errors in 5.0 when we were not getting them in 3.0 with no process changes? Did something change in the program? And is there something we can within our process to accommodate? Or is it some other problem.
Thanks in advance.
have you seen 201516 - Eliminating inconsistencies MARC-APOKZ? Dont know if that explains your situation
Its possible the upgrade caused the inconsistency.
Did you follow any specific process for the reactivation of the CIF models? I think there is a post on that as well
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.