In FCCS, the Data Source dimension tracks where the loaded numbers come from. The member labeled FCCS_Journal Input is specifically meant to store the journal entry data you input or upload for consolidation. This is the dataset that holds the actual transactional journal data that will be processed, posted, and then subjected to mappings, translations, and eliminations during the close. The other data source members serve different data flows—such as intercompany eliminations or scenarios where no data source is used—so they do not store the journal input data.

In Data Integration, the location you choose for an integration determines where the data will land and how its values are interpreted for that target area. The attribute that actually connects that location to the incoming data is the member mappings. These mappings define how each source data member maps to the corresponding members in the target application's dimensions for that specific location. This ensures, for example, that data for a particular entity or region is loaded into the correct entities, accounts, and other dimension members for that location. The other attributes don’t tie data to the location in the same way: the target application identifies the overall app being loaded, the scenario selects the planning/forecast context, and the data file name is just the file’s identifier.

In FCCS, the Data Source dimension marks where the data originated, so the system can apply the correct processing during consolidation. PCON data are the data produced by the PCON workflow, and there is a dedicated member for tagging those values. Using this member ensures the data are recognized as PCON data and handled with the appropriate partial-consolidation logic during calculations and reporting. The other options correspond to different input streams—Journal Input is for manual journal entries, No Data Source indicates no source attached, and Intercompany Eliminations is for elimination adjustments—so they don’t represent PCON data.

In FCCS, how you classify the data you post drives how it’s processed and posted. When you need to reverse an adjusted balance through a journal, you enter the reversal as a journal entry that uses the Journal Input data source. This signals to FCCS that the lines are journal-level adjustments, not regular data loads or system-managed values, and ensures the reversal flows through the same journal processing and auditing path as other journal activities. In a translation bypass scenario, this is exactly how you maintain proper traceability and correct posting of the reverse to the Common Stock balance. Using a data load source meant for ordinary data input would treat the reversal as just data rather than a journal adjustment, which isn’t appropriate for a reversal. The managed data source isn’t editable and wouldn’t be used for a reversal entry. The journal entry concept isn’t itself a data source for the lines; the correct way is to designate the lines as Journal Input so they behave like standard journal entries within FCCS.