2014年All_Modulel_Maintable_relation.pptVIP

* MTL_MATERIAL_TXN_ALLOCATIONS This table stores the repetitive schedules charged by a material transaction. Each row contains the quantity transacted to each schedule for a given transaction. Oracle Work in Process uses this information to report changes to individual schedules for multischedule material transactions. The primary key is TRANSACTION_ID, REPETITIVE_SCHEDULE_ID, ORGANIZATION_ID. * WIP_TRANSACTIONS This table stores information about each resource transaction in Oracle Work in Process. Oracle Work in Process uses this information to track resources and to calculate values stored in WIP_TRANSACTION_ACCOUNTS. The primary key is TRANSACTION_ID. WIP_MOVE_TRANSACTIONS WIP_MOVE_TRANSACTIONS stores information about shop floor move transactions. Each row represents a single move transaction and includes a unique transaction ID, a transaction date, the job or repetitive schedule in which the move occurs, the quantity moved, the from and to operation sequence numbers, operation codes, and intraoperation steps. Oracle Work in Process uses this information to track move transactions. The primary key is TRANSACTION_ID. WIP_MOVE_TXN_ALLOCATIONS This table stores Move quantity information for single shop floor Move transactions that transcend multiple repetitive schedules. The primary key is TRANSACTION_ID, REPETITIVE_SCHEDULE_ID. WIP_TXN_ALLOCATIONS WIP_TXN_ALLOCATIONS stores resource information for single resource cost transactions that transcend multiple repetitive schedules. Oracle Work in Process allocates resource charges to repetitive schedules based on a FIFO algorithm. The primary key is TRANSACTION_ID,REPETITIVE_SCHEDULE_ID. * WIP_TRANSACTION_ACCOUNTS WIP_TRANSACTION_ACCOUNTS holds the accounting information for each resource transaction in WIP_TRANSACTIONS. These tables are joined by the TRANSACTION_ID column, and there are at least two rows (debit and credit) for each transaction of a costed resource. Oracle Work in Process uses this information to