DBA Data[Home] [Help] [Dependency Information]


TABLE: GME.GME_BATCH_HEADER

Object Details
Object Name: GME_BATCH_HEADER
Object Type: TABLE
Owner: GME
FND Design Data: TableGME.GME_BATCH_HEADER
Subobject Name:
Status: VALID


Batch/FPO header. This table stores the header information for both Firm Planned Orders (FPOs) and Batches, including the plant, the validity rules, formula, and routing on which the batch was based, and the planned and actual start and completion dates.


Storage Details
Tablespace: TablespaceAPPS_TS_TX_DATA
PCT Free: 10
PCT Used:
Indexes
Index Type Uniqueness Tablespace Column
GME_BATCH_HEADER_PK NORMAL UNIQUE TablespaceAPPS_TS_TX_IDX ColumnBATCH_ID
GME_BATCH_HEADER_N1 NORMAL NONUNIQUE TablespaceAPPS_TS_TX_IDX ColumnORGANIZATION_ID
ColumnBATCH_NO
ColumnBATCH_STATUS
GME_BATCH_HEADER_N2 NORMAL NONUNIQUE TablespaceAPPS_TS_TX_IDX ColumnBATCH_CLOSE_DATE
GME_BATCH_HEADER_U1 NORMAL NONUNIQUE TablespaceAPPS_TS_TX_IDX ColumnORGANIZATION_ID
ColumnBATCH_NO
ColumnBATCH_TYPE
Columns
Name Datatype Length Mandatory Comments
BATCH_ID NUMBER (10) Yes Unique Identifier for batches to FPO or batch
PLANT_CODE VARCHAR2 (4)
Obsolete in R12. New column is organization_id
BATCH_NO VARCHAR2 (32) Yes Batch or FPO number.
BATCH_TYPE NUMBER (5) Yes Differentiates between Firm Planned Order(10) and batches (0).
PROD_ID NUMBER (10)
Reserved for future use.
PROD_SEQUENCE NUMBER (5) Yes Reserved for future use. Batch sequence in campaign/prod order.
RECIPE_VALIDITY_RULE_ID NUMBER (10)
Surrogate key to the Recipe Validity Rule Id the batch or FPO was based on.
FORMULA_ID NUMBER (10)
FK to formula on which batch or FPO is based. This value can be derived from the Recipe_Validity_Rule_Id
ROUTING_ID NUMBER (10)
FK to routing used.
PLAN_START_DATE DATE
Yes Planned release date/time for batch.
ACTUAL_START_DATE DATE

Actual start date/time for batch. Entered at the time the batch is released, can be entered by the user or current system date.
DUE_DATE DATE
Yes Required batch completion date/time, national.
PLAN_CMPLT_DATE DATE
Yes Planned batch completion date/time. POC data is used to derive this date, the length of time required for each step is added to the planned start date/time. This is updated at the time the batch is created. If POC data is not specified then the lead times specified to the production rules are used to calculate the expected completion date.
ACTUAL_CMPLT_DATE DATE

Actual completion date. This is updated at the time the batch is certified. The user can enter the date or the current system date is used.
BATCH_STATUS NUMBER (5) Yes Batch or FPO status. -3 = Converted FPO, -1 = Cancelled, 1 = Pending, 2 = WIP, 3 = Completed, 4 = Closed
PRIORITY_VALUE NUMBER
Yes Not currently used.
PRIORITY_CODE VARCHAR2 (4) Yes Not currently used.
PRINT_COUNT NUMBER (5) Yes Number of times batch ticket was printed.
FMCONTROL_CLASS VARCHAR2 (8)
Not currently used.
WIP_WHSE_CODE VARCHAR2 (4)
Warehouse used to cost production activity
BATCH_CLOSE_DATE DATE

Date/time the batch was closed.
POC_IND VARCHAR2 (1)
Indicates if POC data is associated with the batch.Y = Yes, POC is associated, POC must be activated before POC data is stored for the batch; i.e. steps created.N = No, not associated with POC.
ACTUAL_COST_IND VARCHAR2 (1)
Indicates if actual costing has been run against the batch data. Y = Actual costing has been run using data from this batch. If a batch is reopened, and the actual_cost_ind = Y, and the costing period used to cost the batch is still open. How do we know what costing period the batch is associated.N = Actual Costing has not been run.
UPDATE_INVENTORY_IND VARCHAR2 (1)
This indicates if a Lab batch updates inventory with inventory consumed. This indicator can only be set to Y if the organization is a Lab organization.Y = Updates inventory with consumed ingredients.N = Does not update inventory with consumed ingredients; Default value.
LAST_UPDATE_DATE DATE
Yes Standard who column
LAST_UPDATED_BY NUMBER
Yes Standard who column
CREATION_DATE DATE
Yes Standard who column
CREATED_BY NUMBER (15) Yes Standard who column
LAST_UPDATE_LOGIN NUMBER (15)
Standard who column
DELETE_MARK NUMBER (5) Yes Standard: 0 = Active record (default)1 = Marked for (logical) deletion.
TEXT_CODE NUMBER (10)
ID which joins any rows of text in this table to the Text Table for this Module
PARENTLINE_ID NUMBER (10)
For phantom batches. Surrogate key to the batch ingredient line for which this phantom batch produces product.
FPO_ID NUMBER (10)
Contains the FPO Id the batch was created for.
ATTRIBUTE1 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE2 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE3 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE4 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE5 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE6 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE7 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE8 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE9 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE10 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE11 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE12 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE13 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE14 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE15 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE16 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE17 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE18 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE19 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE20 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE21 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE22 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE23 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE24 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE25 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE26 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE27 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE28 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE29 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE30 VARCHAR2 (240)
Descriptive Flexfield
ATTRIBUTE_CATEGORY VARCHAR2 (30)
Descriptive Flexfield Cateogry
AUTOMATIC_STEP_CALCULATION NUMBER (5) Yes The value is derived from the routing and stored here for efficiency and the value could change at the routing level.Y= YesN= No.
GL_POSTED_IND NUMBER (5) Yes Indicates, if the batch has been posted to GL, 0 - Batch has not been posted, 1 - Batch has been posted'
FIRMED_IND NUMBER (5)
To indicate that the batch should not be re-scheduled by WPS; Values 0 = No, 1 = Yes.
FINITE_SCHEDULED_IND NUMBER (5)
To indicate whether the batch has been scheduled by WPS or not; Values 0 = No, 1 =Yes. Updated by WPS interface
ORDER_PRIORITY NUMBER (10)
To indicate that the batch has a higher/lower priority; No validations; User enters the /value.
ATTRIBUTE31 VARCHAR2 (240)
This column holds the flexfield data
ATTRIBUTE32 VARCHAR2 (240)
This column holds the flexfield data
ATTRIBUTE33 VARCHAR2 (240)
This column holds the flexfield data
ATTRIBUTE34 VARCHAR2 (240)
This column holds the flexfield data
ATTRIBUTE35 VARCHAR2 (240)
This column holds the flexfield data
ATTRIBUTE36 VARCHAR2 (240)
This column holds the flexfield data
ATTRIBUTE37 VARCHAR2 (240)
This column holds the flexfield data
ATTRIBUTE38 VARCHAR2 (240)
This column holds the flexfield data
ATTRIBUTE39 VARCHAR2 (240)
This column holds the flexfield data
ATTRIBUTE40 VARCHAR2 (240)
This column holds the flexfield data
MIGRATED_BATCH_IND VARCHAR2 (1)
Indicates whether the batch was migrated; Y means migrated, N or NULL means not migrated
ENFORCE_STEP_DEPENDENCY NUMBER (5)
This denotes step dependency is enforced for the batch. We will be inherit this from the FM_ROUT_HDR. 0,NULL means No and 1 means Yes.
TERMINATED_IND NUMBER (1)
Indicates if the batch has been terminated. 1 - Yes 0 - No
ENHANCED_PI_IND VARCHAR2 (1)
If enhanced PI framework is used in the recipe, N for migrated batches
LABORATORY_IND NUMBER

0 = Production Batch 1 = Lab Batch
MOVE_ORDER_HEADER_ID NUMBER

Identifier to the Invisible Move Order,NULL for migrated batches
ORGANIZATION_ID NUMBER

To identify the organization (Plant /Lab)
TERMINATE_REASON_ID NUMBER

Identifier to Terminate Reason name , NULL for migrated batches
FIXED_PROCESS_LOSS_APPLIED VARCHAR2 (1)
This is the column specifies if fixed process loss has been applied to a batch
JA_OSP_BATCH NUMBER (22)
For localization use
Query Text

Cut, paste (and edit) the following text to query this object:


SELECT BATCH_ID
,      PLANT_CODE
,      BATCH_NO
,      BATCH_TYPE
,      PROD_ID
,      PROD_SEQUENCE
,      RECIPE_VALIDITY_RULE_ID
,      FORMULA_ID
,      ROUTING_ID
,      PLAN_START_DATE
,      ACTUAL_START_DATE
,      DUE_DATE
,      PLAN_CMPLT_DATE
,      ACTUAL_CMPLT_DATE
,      BATCH_STATUS
,      PRIORITY_VALUE
,      PRIORITY_CODE
,      PRINT_COUNT
,      FMCONTROL_CLASS
,      WIP_WHSE_CODE
,      BATCH_CLOSE_DATE
,      POC_IND
,      ACTUAL_COST_IND
,      UPDATE_INVENTORY_IND
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      CREATION_DATE
,      CREATED_BY
,      LAST_UPDATE_LOGIN
,      DELETE_MARK
,      TEXT_CODE
,      PARENTLINE_ID
,      FPO_ID
,      ATTRIBUTE1
,      ATTRIBUTE2
,      ATTRIBUTE3
,      ATTRIBUTE4
,      ATTRIBUTE5
,      ATTRIBUTE6
,      ATTRIBUTE7
,      ATTRIBUTE8
,      ATTRIBUTE9
,      ATTRIBUTE10
,      ATTRIBUTE11
,      ATTRIBUTE12
,      ATTRIBUTE13
,      ATTRIBUTE14
,      ATTRIBUTE15
,      ATTRIBUTE16
,      ATTRIBUTE17
,      ATTRIBUTE18
,      ATTRIBUTE19
,      ATTRIBUTE20
,      ATTRIBUTE21
,      ATTRIBUTE22
,      ATTRIBUTE23
,      ATTRIBUTE24
,      ATTRIBUTE25
,      ATTRIBUTE26
,      ATTRIBUTE27
,      ATTRIBUTE28
,      ATTRIBUTE29
,      ATTRIBUTE30
,      ATTRIBUTE_CATEGORY
,      AUTOMATIC_STEP_CALCULATION
,      GL_POSTED_IND
,      FIRMED_IND
,      FINITE_SCHEDULED_IND
,      ORDER_PRIORITY
,      ATTRIBUTE31
,      ATTRIBUTE32
,      ATTRIBUTE33
,      ATTRIBUTE34
,      ATTRIBUTE35
,      ATTRIBUTE36
,      ATTRIBUTE37
,      ATTRIBUTE38
,      ATTRIBUTE39
,      ATTRIBUTE40
,      MIGRATED_BATCH_IND
,      ENFORCE_STEP_DEPENDENCY
,      TERMINATED_IND
,      ENHANCED_PI_IND
,      LABORATORY_IND
,      MOVE_ORDER_HEADER_ID
,      ORGANIZATION_ID
,      TERMINATE_REASON_ID
,      FIXED_PROCESS_LOSS_APPLIED
,      JA_OSP_BATCH
FROM GME.GME_BATCH_HEADER;

Dependencies

[top of page]

GME.GME_BATCH_HEADER does not reference any database object

GME.GME_BATCH_HEADER is referenced by following:

SchemaGME
ViewGME_BATCH_HEADER#