PIN_COLLECT Job is not Taking DST Change

(Doc ID 2146174.1)

Last updated on JANUARY 05, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


On : 7.4MPS2 version, Collections

PIN_COLLECT job is not reflecting DST correctly , due to which Day 3 and Day 7 calculation are going wrong.

Running the pin_collect utility as

pin_collect -active -start 7 -end 7 -pay_type 10003 -vendor cs -verbose

pin_collect -active -start 3 -end 3 -pay_type 10003 -vendor cs -verbose

Before DST change dates were getting calculated correctly , after DST change it is taking 1 day extra i.e Day 4 and Day 8 .



Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms