Segment journal behavior in the C2 process
Segment values in the C2 process are populated in this way:
- When the setting is enabled, segment values are read from segment cubes (cubes that contain segment-level data).
- When the setting is disabled, segment values are read from non-segment cubes.
This table shows how journal segments and intersegments are populated for each combination of the setting and data source:
| Scenario | Generate Segment Journals | Data source | Segments 1-3 | Intersegments 1-3 |
|---|---|---|---|---|
| 1 | Enabled | Data Entry | Unassigned |
EXTERNAL |
| 2 | Disabled | Data Entry | Unassigned |
Unassigned |
| 3 | Enabled | Data Import | Assigned | EXTERNAL |
| 4 | Disabled | Data Import | Unassigned |
Unassigned |
Intersegments are populated as EXTERNAL when the setting is enabled. Otherwise, intersegments are Unassigned. See scenarios 1-4 in the table.
Segments 1-3 are Unassigned unless the setting is enabled and data is loaded through with assigned segment values. In this case, imported segment values are used. See scenario 3 in the table.
Data that is specified on the Data Entry page always produces Unassigned segment values because segment assignment isn't supported on the Data Entry page. See scenarios 1 and 2 in the table.
Journals contain assigned segment values only when the setting is enabled and data is imported with explicitly assigned segments through .