Organization Name:
Project Maverick
Description:
Intercompany transactions are booked on both sides (receiver and provider/seller)
in the Oracle Fusion source system and integrated into FDI via the standard data
pipeline. However, JE Nomenclature (JEN) only populates on one line per side in FDI,
resulting in 2 total appearances per intercompany batch instead of the expected 4
(2 lines per side). The requested enhancement is for FDI to carry JE Nomenclature
through to all journal lines associated with the intercompany transaction — consistent
with how Intercompany Batch Number already behaves and consistent with the source
system booking.
Use Case and Business Need:
The client's tax and finance team uses JE Nomenclature as a direct filter in FDI
to isolate intercompany journal entries by transaction type. Because JEN is missing
on one line per side, filtered reports return an incomplete population. This prevents
the client from using JEN-based filtering as intended and requires a workaround of
filtering by Intercompany Batch Number (LPYN) instead.
Resolving this is necessary for the client to leverage FDI intercompany reporting
as a reliable and auditable data source.
