Below are some possible reasons for INSMK change without direct log
1. System-Driven Update via Inspection Lot
Even if the inspection lot shows no issues, closing or usage decision on the lot can trigger a change in stock type (e.g., from quality to unrestricted). This update may reflect back on the production order’s stock assignment without logging a direct change in the order itself.
2. Indirect Change via Goods Movement (MB31 / MIGO)
A goods receipt or reversal posted against the production order could alter the stock type. These movements update INSMK but do not trigger a change log in the production order header or status.
3. Background Job or Enhancement Logic
Some systems have custom logic or user exits that adjust INSMK during batch jobs or cleanup routines. If such logic was triggered in the current year, it could silently update the stock type.
4. Change via CO02 Without Logging
If someone accessed the order via CO02 and changed the stock type on the goods receipt tab, it may not generate a change log unless the header or status was altered.
5. Archiving Pre-Check Logic
The archiving job may internally validate stock type and skip orders with non-standard INSMK values, even if the order is technically closed.
To investigate further
- Check Goods Movement History: Use MB51 or COOIS to trace any movements linked to the order in the current year.
- Review Inspection Lot Events: Use QA03 to see if any usage decisions or lot closures occurred recently.
- Audit Enhancements: Review any custom logic in CO02, MB31, or archiving pre-check routines.
- Use Table AUFK / AFKO: Compare timestamps and stock type fields to detect silent updates.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.