Oracle EBS Create Accounting for Third Party Merge "Partial Merger" (PARTIAL_MERGE) the source of accounting events

      Oracle EBS version: R12.1.3   

      The previous article " Oracle EBS AR closes the accounting period exception reminder: APP-AR-294571: XXX-XXX cannot be closed due to some unprocessed accounting events or untransmitted journal entries " mentioned that a request needs to be submitted" Create Accounting for Third Party Merge" ( create accounting titles for third party merger ). Bringing greater doubts to customers, why we did not operate customer mergers and supplier mergers, but there are always similar accounting events automatically generated ?

In response to the customer's problem, find out the corresponding SQL from the background according to the concurrent request parameter "event":

SELECT Xe.Event_Id
      ,Gl.Name                      "Ledger Name"
       ,Xe.Event_Date                "Merge Date"
       ,Xtpv1.Third_Party_Number     "Original Party Number"
       ,Xtpsv1.Third_Party_Site_Code "Original Site Code"
       ,Xtpv2.Third_Party_Number     "New Party Number"
       ,Xtpsv2.Third_Party_Site_Code "New Site Code"
       ,Hp1.Customer_Name
       ,Hp2.Customer_Name
       ,Xte.*
       ,Xe.*
  FROM Xla_Events               Xe
      ,Xla_Transaction_Entities Xte
      ,Gl_Ledgers               Gl
      ,Xla_Third_Parties_v      Xtpv1
      ,Xla_Third_Parties_v      Xtpv2
      ,Xla_Third_Party_Sites_v  Xtpsv1
      ,Xla_Third_Party_Sites_v  Xtpsv2
      ,Ar_Customers             Hp1
      ,Ar_Customers             Hp2

 WHERE Xe.Entity_Id = Xte.Entity_Id
   AND Xe.Application_Id = 222
   AND Xe.Application_Id = Xte.Application_Id
   AND Xe.Event_Type_Code IN ('FULL_MERGE', 'PARTIAL_MERGE')
   AND Xte.Ledger_Id = Gl.Ledger_Id
   AND Xe.Process_Status_Code <> 'F'
   AND Xe.Reference_Num_1 = Xtpv1.Third_Party_Id
   AND Xe.Reference_Char_1 = Xtpv1.Third_Party_Type
   AND Xe.Reference_Num_3 = Xtpv2.Third_Party_Id
   AND Xe.Reference_Char_1 = Xtpv2.Third_Party_Type
   AND Xe.Reference_Num_1 = Xtpsv1.Third_Party_Id(+)
   AND Xe.Reference_Num_2 = Xtpsv1.Third_Party_Site_Id(+)
   AND Xe.Reference_Char_1 = Xtpsv1.Third_Party_Type(+)
   AND Xe.Reference_Num_3 = Xtpsv2.Third_Party_Id(+)
   AND Xe.Reference_Num_4 = Xtpsv2.Third_Party_Site_Id(+)
   AND Xe.Reference_Char_1 = Xtpsv2.Third_Party_Type(+)
   AND Xtpv1.Third_Party_Id = Hp1.Customer_Id(+)
   AND Xtpv2.Third_Party_Id = Hp2.Customer_Id(+)

The example data is as follows: customer account 2337 is merged into customer new account 10662. The relevant source data fields are all empty, and the relevant business documents cannot be found retrospectively.

The SR official did not give valuable reference information. You can only find out the business logic through the code, and find out how the data is generated from the event type keywords, as in the following SQL:

Select * from dba_source s where s.owner ='APPS' And S.TEXT like '%PARTIAL_MERGE%'

Find out which package call generated the data, such as: arp_acct_event_pkg.update_cr_dist>xla_third_party_merge_pub. third_party_merge>XLA_THIRD_PARTY_MERGE.third_party_merge.
Since the package was arp_acct_event_pkg.update_cr_dist, it was not known which function called it. It is currently speculated that there are several situations that may cause a merger event:
1. The customer and the supplier are merged
2. The sales order of the customer account A is returned by the customer account B
3. The AR transaction processing of the customer account A is written off by the receipt of the customer account B
No similar business situation was found through data inspection.
Finally, check the package arp_acct_event_pkg.update_cr_dist code:

there is a section related to the update of the data in the table ar_distributions_all , and the preliminary judgment based on the data in the table is the data generated by AR collection .

Therefore, the AR collection was created, modified, written off, cancelled, written off, billed and canceled, etc., and finally found to be caused by the modification of the AR collection operation, and the summary is as follows:
Prerequisite: The
        same customer must To have two accounts to
reappear (EVENT_TYPE_CODE='PARTIAL_MERGE') part of the merge event is as follows :
1. Create a collection CXP_190331, Customer name: Wuhan XXXX Co., Ltd. number: 10662
2. Modify the collection CXP_190331, Customer name: Wuhan XXXX Co., Ltd. number: 2337, at this time, some consolidated accounting events will be generated through the background search.

At the same time, this is also the difference between R12.1.3 and R12.1.1.