Journal Source Security on a Journal with reversal ON
Any users have implemented journal source security and tested it with any journal with reversal ON ? It doesn't seems to be working at all (creates reversal journal when cutoff crossed & marks original journal as post incomplete).
Just checking if We are the first customer to explore it and hit with a problem or anyone else faced the same. If already saw the problem is there a way anyone find to avoid it ? [FYI , we have already a defect logged to Oracle for this and still under investigation] Looking for any inputs from customers who have already implemented Journal Source Security feature.