eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.WIP_MOVPROC_PRIV dependencies on WIP_TXN_ALLOCATIONS

Line 3333: * WIP_TXN_ALLOCATIONS IF needed

3329: /*****************************************************************************
3330: * This procedure is equivalent to witpsar_auto_resources in wiltps2.ppc
3331: * This procedure is used to insert auto-resources associated with move txn
3332: * This procedure insert the record into WIP_COST_TXN_INTERFACE and
3333: * WIP_TXN_ALLOCATIONS IF needed
3334: ****************************************************************************/
3335: PROCEDURE insert_auto_resource(p_gib IN group_rec_t,
3336: x_returnStatus OUT NOCOPY VARCHAR2) IS
3337:

Line 4302: | Generate transaction_id for WIP_TXN_ALLOCATIONS |

4298: IF(l_move.rsrcItem = WIP_CONSTANTS.YES OR
4299: l_move.rsrcLot = WIP_CONSTANTS.YES) THEN
4300:
4301: /*------------------------------------------------------------+
4302: | Generate transaction_id for WIP_TXN_ALLOCATIONS |
4303: +------------------------------------------------------------*/
4304: UPDATE wip_cost_txn_interface
4305: SET transaction_id = wip_transactions_s.nextval
4306: WHERE group_id = p_gib.group_id

Line 4332: | Columns to insert into WIP_TXN_ALLOCATIONS |

4328: | per lot
4329: +------------------------------------------------------------*/
4330:
4331: /*------------------------------------------------------------+
4332: | Columns to insert into WIP_TXN_ALLOCATIONS |
4333: | |
4334: | transaction_id, |
4335: | repetitive_schedule_id, organization_id, |
4336: | last_update_date, last_updated_by, creation_date, |

Line 4343: INSERT INTO wip_txn_allocations

4339: | transaction_quantity, |
4340: | primary_quantity, |
4341: | |
4342: +------------------------------------------------------------*/
4343: INSERT INTO wip_txn_allocations
4344: (transaction_id,
4345: repetitive_schedule_id,
4346: organization_id,
4347: last_update_date,

Line 4448: fnd_message.set_token('ENTITY2', 'WIP_TXN_ALLOCATIONS');

4444: -- IF debug message level = 2, write statement below to log file
4445: IF (l_logLevel <= wip_constants.full_logging) THEN
4446: fnd_message.set_name('WIP', 'WIP_INSERTED_ROWS');
4447: fnd_message.set_token('ENTITY1', SQL%ROWCOUNT);
4448: fnd_message.set_token('ENTITY2', 'WIP_TXN_ALLOCATIONS');
4449: l_msg := fnd_message.get;
4450: wip_logger.log(p_msg => l_msg,
4451: x_returnStatus => l_returnStatus);
4452: END IF;

Line 4486: * This procedure insert the record into WIP_TXN_ALLOCATIONS

4482: /*****************************************************************************
4483: * This procedure is equivalent to wipiara in wiltca.ppc
4484: * This procedure is used to allocate per-item auto-resouce according to the
4485: * material allocation in the coresponding move transactions.
4486: * This procedure insert the record into WIP_TXN_ALLOCATIONS
4487: * This procedure must be called only after move allocation is successfully
4488: * completed
4489: ****************************************************************************/
4490: PROCEDURE insert_txn_alloc(p_gib IN group_rec_t,

Line 4513: WIP_TXN_ALLOCATIONS.

4509: /*---------------------------------------------------------------------+
4510: For each pENDing automatic per-item resource transaction in the group,
4511: the allocator uses the transaction associated material allocation in
4512: WIP_MOVE_TXN_ALLOCATION to insert one or more allocation records into
4513: WIP_TXN_ALLOCATIONS.
4514: +--------------------------------------------------------------------*/
4515: INSERT INTO wip_txn_allocations
4516: (transaction_id,
4517: repetitive_schedule_id,

Line 4515: INSERT INTO wip_txn_allocations

4511: the allocator uses the transaction associated material allocation in
4512: WIP_MOVE_TXN_ALLOCATION to insert one or more allocation records into
4513: WIP_TXN_ALLOCATIONS.
4514: +--------------------------------------------------------------------*/
4515: INSERT INTO wip_txn_allocations
4516: (transaction_id,
4517: repetitive_schedule_id,
4518: organization_id,
4519: last_update_date,

Line 4590: fnd_message.set_token('ENTITY2', 'WIP_TXN_ALLOCATIONS');

4586: -- IF debug message level = 2, write statement below to log file
4587: IF (l_logLevel <= wip_constants.full_logging) THEN
4588: fnd_message.set_name('WIP', 'WIP_INSERTED_ROWS');
4589: fnd_message.set_token('ENTITY1', SQL%ROWCOUNT);
4590: fnd_message.set_token('ENTITY2', 'WIP_TXN_ALLOCATIONS');
4591: l_msg := fnd_message.get;
4592: wip_logger.log(p_msg => l_msg,
4593: x_returnStatus => l_returnStatus);
4594: END IF;

Line 4625: * WIP_COST_TXN_INTERFACE and WIP_TXN_ALLOCATIONS IF needed

4621:
4622: /*****************************************************************************
4623: * This procedure is equivalent to witpsdo_dept_overheads in wiltps3.ppc
4624: * This procedure is used to insert department overhead info into
4625: * WIP_COST_TXN_INTERFACE and WIP_TXN_ALLOCATIONS IF needed
4626: ****************************************************************************/
4627: PROCEDURE insert_dept_overhead(p_gib IN group_rec_t,
4628: x_returnStatus OUT NOCOPY VARCHAR2) IS
4629:

Line 5591: | Generate transaction_id for WIP_TXN_ALLOCATIONS |

5587: END IF; -- Per order basis type for repetitive
5588:
5589:
5590: /*------------------------------------------------------------+
5591: | Generate transaction_id for WIP_TXN_ALLOCATIONS |
5592: +------------------------------------------------------------*/
5593: UPDATE wip_cost_txn_interface
5594: SET transaction_id = wip_transactions_s.nextval
5595: WHERE group_id = p_gib.group_id

Line 5618: | Columns to insert into WIP_TXN_ALLOCATIONS |

5614: | per lot
5615: +------------------------------------------------------------*/
5616:
5617: /*------------------------------------------------------------+
5618: | Columns to insert into WIP_TXN_ALLOCATIONS |
5619: | |
5620: | transaction_id, |
5621: | repetitive_schedule_id, organization_id, |
5622: | last_update_date, last_updated_by, creation_date, |

Line 5629: INSERT INTO wip_txn_allocations

5625: | transaction_quantity, |
5626: | primary_quantity, |
5627: | |
5628: +------------------------------------------------------------*/
5629: INSERT INTO wip_txn_allocations
5630: (transaction_id,
5631: repetitive_schedule_id,
5632: organization_id,
5633: last_update_date,

Line 5719: fnd_message.set_token('ENTITY2', 'WIP_TXN_ALLOCATIONS');

5715: -- IF debug message level = 2, write statement below to log file
5716: IF (l_logLevel <= wip_constants.full_logging) THEN
5717: fnd_message.set_name('WIP', 'WIP_INSERTED_ROWS');
5718: fnd_message.set_token('ENTITY1', SQL%ROWCOUNT);
5719: fnd_message.set_token('ENTITY2', 'WIP_TXN_ALLOCATIONS');
5720: l_msg := fnd_message.get;
5721: wip_logger.log(p_msg => l_msg,
5722: x_returnStatus => l_returnStatus);
5723: END IF;

Line 9723: -- per item exist (insert into WIP_TXN_ALLOCATIONS)

9719: raise fnd_api.g_exc_unexpected_error;
9720: END IF; -- check return status
9721:
9722: -- Only call the cost allocation IF schedule transactions and auto resource
9723: -- per item exist (insert into WIP_TXN_ALLOCATIONS)
9724: IF(l_move.scheTxn = WIP_CONSTANTS.YES AND
9725: l_move.rsrcItem = WIP_CONSTANTS.YES) THEN
9726:
9727: insert_txn_alloc(p_gib => p_gib,