The question is regarding the Time Schema:
We run Time Schema to generate quota in Infotype 2006. For some business special case, we need correct the quota generated through creating a quota correction record in Infotype 2013. The correction record then correct existing quota (Increase, reduce or replace) in IT2006 when the schema run.
Sometime, we have to load correction records in IT2013 first before the corrected quota is created in IT2006. Due to IT2013 was created first, when Time Schema run, there is no IT2006 record for the correction, therefore, SAP creates a new quota in IT2006 instead. The issue is that the validity period (Infotype start / end) of the new created quota does not follow the quota validity rule while the quota deduction period (“deduction from” and “deduction to”) does. The validity period was always set to the same day (quota correction date). Does anyone has clue on why this happen and how to fix. Or would that be SAP bug? Thanks.
We run Time Schema to generate quota in Infotype 2006. For some business special case, we need correct the quota generated through creating a quota correction record in Infotype 2013. The correction record then correct existing quota (Increase, reduce or replace) in IT2006 when the schema run.
Sometime, we have to load correction records in IT2013 first before the corrected quota is created in IT2006. Due to IT2013 was created first, when Time Schema run, there is no IT2006 record for the correction, therefore, SAP creates a new quota in IT2006 instead. The issue is that the validity period (Infotype start / end) of the new created quota does not follow the quota validity rule while the quota deduction period (“deduction from” and “deduction to”) does. The validity period was always set to the same day (quota correction date). Does anyone has clue on why this happen and how to fix. Or would that be SAP bug? Thanks.