[Home] [Help]
[Dependency Information]
| Object Name: | GL_AUTO_ALLOC_BATCH_HISTORY |
|---|---|
| Object Type: | TABLE |
| Owner: | GL |
| FND Design Data: | SQLGL.GL_AUTO_ALLOC_BATCH_HISTORY
|
| Subobject Name: | |
| Status: | VALID |
GL_AUTO_ALLOC_BATCH_HISTORY stores, for every run of an allocation set, one row for each batch in the allocation set. Each row includes a unique auto_alloc_batch_id, as well as a batch_name, a batch_type, owner, and allocation method. This table is required as batches included in the allocation set can be modified after the request submission and before the request is executed.
For step-down allocation set, the STEP NUMBER specifies the sequence in which the batch should be generated and posted. BATCH_TYPE_CODE is either 'A', 'B', 'E', 'R' or 'P' for MassAllocation, MassBudgets, Encumbrances, Recurring, or Projects batch respectively.
ALLOCATION_METHOD_CODE is 'I' for incremental allocation or 'F' for full allocation method. Owner represents the role name, defined in WF_ROLES table, who will receive the notification, for this particular batch, when any error occurs in step-down allocation run.
| Tablespace: | APPS_TS_TX_DATA |
|---|---|
| PCT Free: | 10 |
| PCT Used: |
| Index | Type | Uniqueness | Tablespace | Column |
|---|---|---|---|---|
| GL_AUTO_ALLOC_BATCH_HISTORY_U1 | NORMAL | UNIQUE |
APPS_TS_TX_IDX
|
REQUEST_ID
BATCH_ID
BATCH_TYPE_CODE
GENERATED_JE_BATCH_ID
|
| GL_AUTO_ALLOC_BATCH_HISTORY_U2 | NORMAL | UNIQUE |
APPS_TS_TX_IDX
|
REQUEST_ID
STEP_NUMBER
GENERATED_JE_BATCH_ID
|
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| REQUEST_ID | NUMBER | Yes | Auto allocation concurrent request id | |
| BATCH_ID | NUMBER | (15) | Yes | Defining column for Massalocation batch, Recurring Journal batch, MassBudget batch, or Project batch. |
| BATCH_TYPE_CODE | VARCHAR2 | (1) | Yes | Batch Type (Massallocations, MassBudgets, MassEncumbrances, Recurring Journals, or Project Allocations) |
| LAST_UPDATE_DATE | DATE | Yes | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Yes | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Yes | Standard Who column |
| CREATION_DATE | DATE | Yes | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Yes | Standard Who column |
| STEP_NUMBER | NUMBER | Sequence in which batch is to be generated for step-down set. | ||
| OWNER | VARCHAR2 | (100) | The owner/role specified for an Allocation batch who will receive notifications when any errors occur in Allocations | |
| ALLOCATION_METHOD_CODE | VARCHAR2 | (1) | Allocation method used for batch generation. | |
| GENERATED_JE_BATCH_ID | NUMBER | (15) | Defining column for generated journal batch | |
| PA_ALLOCATION_RUN_ID | NUMBER | (15) | Defining column for generated project rule id | |
| STATUS_CODE | VARCHAR2 | (150) | Run status of each step in the allocation set | |
| COMPLETE_FLAG | VARCHAR2 | (1) | Flag to indicate that step is generated and posted | |
| ALL_HEADERS_REVERSED | VARCHAR2 | (1) | Flag to indicate that all headers for the generated batch are reversed during rollback |
Cut, paste (and edit) the following text to query this object:
SELECT REQUEST_ID
, BATCH_ID
, BATCH_TYPE_CODE
, LAST_UPDATE_DATE
, LAST_UPDATED_BY
, LAST_UPDATE_LOGIN
, CREATION_DATE
, CREATED_BY
, STEP_NUMBER
, OWNER
, ALLOCATION_METHOD_CODE
, GENERATED_JE_BATCH_ID
, PA_ALLOCATION_RUN_ID
, STATUS_CODE
, COMPLETE_FLAG
, ALL_HEADERS_REVERSED
FROM GL.GL_AUTO_ALLOC_BATCH_HISTORY;
GL.GL_AUTO_ALLOC_BATCH_HISTORY does not reference any database object
GL.GL_AUTO_ALLOC_BATCH_HISTORY is referenced by following:
GL
GL_AUTO_ALLOC_BATCH_HISTORY#
|
|
|
|