My Oracle Support Banner

Queries Related To Unpost General Ledger Data In BRM (Doc ID 2086671.1)

Last updated on AUGUST 20, 2019

Applies to:

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

Purpose

The purpose of this article is to answer some questions regarding UnPost GL Data

Scenario: Automated job ran GL summary report twice by mistake.

            1) Run report from -start 09/27/2015 -end 10/28/2015
            2) Run from one day -start 10/28/2015 -end 10/29/2015

Questions and Answers

To view full details, sign in with your My Oracle Support account.

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


In this Document
Purpose
Questions and Answers
 Qn1: Can LAST_POSTED_T column (i.e. last desired run in prod, 10/28/2015) manually updated and run the unpost command again to align both dates? This will unpost unnecessary data generated for one day ( during re-run)?
 Qn2:Will unpost will delete any data generated by running pin_ledger_report apart from changing this last_posted_t? (As per documentation, the last posted date is changed to the date of the previous post)

 Qn3:If not is there any other way to delete this extra data which got generated for one day 28-29oct?

 Qn4: If column is updated from backend, and if report ran from 28th Oct to 29th Nov once again Will it be problem? since in this next cycle report for one day is already generated, so data will overlap?
 


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.