To prevent the entry of new intercompany transactions for a specific period, you should close the period in the Intercompany subledger. Each subledger, including Intercompany, has its own set of accounting periods that can be managed independently of the General Ledger periods. Closing the Intercompany period changes its status to "Closed," which prohibits the creation of any new transactions within that period. This provides precise control over intercompany transaction entry without affecting other modules.

A: Freezing the journal source in GL only prevents posting to GL; it does not stop transaction creation in the Intercompany subledger itself.

C: Closing all subledger periods is overly broad and would unnecessarily halt operations in modules like Payables, Receivables, and Assets.

D: Closing the General Ledger period prevents posting to the general ledger but does not stop transaction creation in the source subledgers.

1. Oracle Fusion Applications Cloud, Implementing Intercompany, Release 13 (Update 24B), Chapter 4: Intercompany System Options and Periods, Section: "Intercompany Periods". "You can open and close intercompany periods to control intercompany transaction entry... When the intercompany period is closed, no new intercompany transactions can be entered."

2. Oracle Help Center, Financials for General Ledger, Chapter: Period Close, Section: "Subledger Period Close". "You must close the subledgers before closing the General Ledger." This highlights the independence of subledger period statuses.