Journal Entry with GLID 1512 Is Created When Not Expected (Doc ID 2988754.1)

Last updated on MAY 01, 2024

Applies to:

Symptoms

In a system with wholesale billing feature enabled, it is seen that during billing the General Ledger ID (GLID) 1512 (which is meant as GLID for rounding errors) is impacted with incorrect charges. Below is the detailed scenario where this issue is witnessed:

1. Business parameters:
   wholesale_billing_system = 1
   generate_journal_epsilon = 1
   deferred_tax_journaling = 2
2. Pricing configuration:
   create charge offer with monthly cycle forward event (MCF), amount=300$, create bundle and package p1, consider this is for parent account
   create charge offer MCF, amount=100$, create bundle and package p2, consider this is for child account
3. from Billing Care, create account and purchase p1, invoice pay type, consider this is parent account
   • edit bill unit and add business profile as ‘Wholesale’ from the list of values
4. from Billing Care, create account and purchase p2, no payment method, consider this is child account
   • edit payment method and change to ‘paid by parent’
     Note: ITEM_CLASS field of item_t for child becomes 1 from 0.
5. go to bill date, go to pin_billd directory, run billing for child and parent using following commands (the xml files contain details of the account to be billed):
   pin_bill_accts -file child.xml -verbose
   pin_bill_accts -file parent.xml -verbose
6. see journal entries:
   
   select ITEM_OBJ_TYPE, GL_ID , RESOURCE_ID, DB_AR_NET_AMT from journal_t where account_obj_id0=2166059; --parent
   /item/cycle_forward 0 840 300
   /item/cycle_forward 1512 840 200
   
   
7. Issue is that on the parent account, see that there is a journal entry created with 1512 GLID (this is the GLID for rounding errors), this row is not expected.

Cause

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