Archived Journal Import References
The Archived Journal Import References view object contains individual transactions from subledgers that are summarized in Oracle General Ledger journal entry lines through the Import Journals process.
Data Store Key : FscmTopModelAM.FinExtractAM.FinArchiveBiccExtractAM.ArchiveGlImportReferenceExtractPVO
Primary Keys : JeBatchId
Initial Extract Date : CreationDate
Incremental Extract Date :
Attributes
This table provides the list of exposed attributes and their descriptions.
| Name | Description |
|---|---|
| CreatedBy | The user who created the journal import references. |
| CreationDate | The date and time when the journal import reference was created. |
| GlSlLinkId | The unique identifier of the link that's associated with the subledger transaction. |
| GlSlLinkTable | The name of the table that stores associated subledger data. |
| JeBatchId | The unique identifier of the journal batch. This is a foreign key of the Journal Batches view object. |
| JeHeaderId | The unique identifier of the journal. This is a foreign key of the Journals view object. |
| JeLineNum | The unique identifier of the journal Line. This is a foreign key of the Journal Lines view object. |
| LastUpdateDate | The date when the journal import reference row was last updated. |
| LastUpdateLogin | The session login associated with the user who last updated the journal import reference. |
| LastUpdatedBy | The user who last updated the journal import reference. |
| ObjectVersionNumber | The number of times the journal import reference row has been updated. |
| PartitionGroupCode | The code that identifies the partition group. The partition grouping information, when combined with the period, determines the database partition where the journal batch will be stored. |
| PeriodName | The name of the accounting period. |
| Reference1 | The journal import reference column. This is used by respective subledgers to store specific values related to the source transaction. |
| Reference10 | The journal import reference column. This is used by respective subledgers to store specific values related to the source transaction. |
| Reference2 | The journal import reference column. This is used by respective subledgers to store specific values related to the source transaction. |
| Reference3 | The journal import reference column. This is used by respective subledgers to store specific values related to the source transaction. |
| Reference4 | The journal import reference column. This is used by respective subledgers to store specific values related to the source transaction. |
| Reference5 | The journal import reference column. This is used by respective subledgers to store specific values related to the source transaction. |
| Reference6 | The journal import reference column. This is used by respective subledgers to store specific values related to the source transaction. |
| Reference7 | The journal import reference column. This is used by respective subledgers to store specific values related to the source transaction. |
| Reference8 | The journal import reference column. This is used by respective subledgers to store specific values related to the source transaction. |
| Reference9 | The journal import reference column. This is used by respective subledgers to store specific values related to the source transaction. |
| SubledgerDocSequenceId | The unique identifier of the import journal document sequence. |
| SubledgerDocSequenceValue | The document sequence value of the importing journal. |