Question & Answer
Question
Why collection date for CHARGE entry considers modification timestamp of AUTHORIZATION record, instead of considering create timestamp of CHARGE record in IBM Sterling Order Management?
Cause
Consolidation window is not getting used
Answer
The consolidation window is driven by number of days the authorization would be valid. So when a CHARGE is opened against an authorization the collection date for the CHARGE should not go beyond authorization's expiration date, making the auth expired and in turn would lead to failure for charge. This is the reason why consolidation time is added to the EXECUTION_DATE.
If execution date is null then product looks at the MODIFYTS. If the CHARGE is a blind charge i.e. a CHARGE without any authorization then the createts of the CHARGE is considered to calculate collection date.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg22008238