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 3204: * WIP_TXN_ALLOCATIONS IF needed

3200: /*****************************************************************************
3201: * This procedure is equivalent to witpsar_auto_resources in wiltps2.ppc
3202: * This procedure is used to insert auto-resources associated with move txn
3203: * This procedure insert the record into WIP_COST_TXN_INTERFACE and
3204: * WIP_TXN_ALLOCATIONS IF needed
3205: ****************************************************************************/
3206: PROCEDURE insert_auto_resource(p_gib IN group_rec_t,
3207: x_returnStatus OUT NOCOPY VARCHAR2) IS
3208:

Line 4173: | Generate transaction_id for WIP_TXN_ALLOCATIONS |

4169: IF(l_move.rsrcItem = WIP_CONSTANTS.YES OR
4170: l_move.rsrcLot = WIP_CONSTANTS.YES) THEN
4171:
4172: /*------------------------------------------------------------+
4173: | Generate transaction_id for WIP_TXN_ALLOCATIONS |
4174: +------------------------------------------------------------*/
4175: UPDATE wip_cost_txn_interface
4176: SET transaction_id = wip_transactions_s.nextval
4177: WHERE group_id = p_gib.group_id

Line 4203: | Columns to insert into WIP_TXN_ALLOCATIONS |

4199: | per lot
4200: +------------------------------------------------------------*/
4201:
4202: /*------------------------------------------------------------+
4203: | Columns to insert into WIP_TXN_ALLOCATIONS |
4204: | |
4205: | transaction_id, |
4206: | repetitive_schedule_id, organization_id, |
4207: | last_update_date, last_updated_by, creation_date, |

Line 4214: INSERT INTO wip_txn_allocations

4210: | transaction_quantity, |
4211: | primary_quantity, |
4212: | |
4213: +------------------------------------------------------------*/
4214: INSERT INTO wip_txn_allocations
4215: (transaction_id,
4216: repetitive_schedule_id,
4217: organization_id,
4218: last_update_date,

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

4315: -- IF debug message level = 2, write statement below to log file
4316: IF (l_logLevel <= wip_constants.full_logging) THEN
4317: fnd_message.set_name('WIP', 'WIP_INSERTED_ROWS');
4318: fnd_message.set_token('ENTITY1', SQL%ROWCOUNT);
4319: fnd_message.set_token('ENTITY2', 'WIP_TXN_ALLOCATIONS');
4320: l_msg := fnd_message.get;
4321: wip_logger.log(p_msg => l_msg,
4322: x_returnStatus => l_returnStatus);
4323: END IF;

Line 4357: * This procedure insert the record into WIP_TXN_ALLOCATIONS

4353: /*****************************************************************************
4354: * This procedure is equivalent to wipiara in wiltca.ppc
4355: * This procedure is used to allocate per-item auto-resouce according to the
4356: * material allocation in the coresponding move transactions.
4357: * This procedure insert the record into WIP_TXN_ALLOCATIONS
4358: * This procedure must be called only after move allocation is successfully
4359: * completed
4360: ****************************************************************************/
4361: PROCEDURE insert_txn_alloc(p_gib IN group_rec_t,

Line 4384: WIP_TXN_ALLOCATIONS.

4380: /*---------------------------------------------------------------------+
4381: For each pENDing automatic per-item resource transaction in the group,
4382: the allocator uses the transaction associated material allocation in
4383: WIP_MOVE_TXN_ALLOCATION to insert one or more allocation records into
4384: WIP_TXN_ALLOCATIONS.
4385: +--------------------------------------------------------------------*/
4386: INSERT INTO wip_txn_allocations
4387: (transaction_id,
4388: repetitive_schedule_id,

Line 4386: INSERT INTO wip_txn_allocations

4382: the allocator uses the transaction associated material allocation in
4383: WIP_MOVE_TXN_ALLOCATION to insert one or more allocation records into
4384: WIP_TXN_ALLOCATIONS.
4385: +--------------------------------------------------------------------*/
4386: INSERT INTO wip_txn_allocations
4387: (transaction_id,
4388: repetitive_schedule_id,
4389: organization_id,
4390: last_update_date,

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

4457: -- IF debug message level = 2, write statement below to log file
4458: IF (l_logLevel <= wip_constants.full_logging) THEN
4459: fnd_message.set_name('WIP', 'WIP_INSERTED_ROWS');
4460: fnd_message.set_token('ENTITY1', SQL%ROWCOUNT);
4461: fnd_message.set_token('ENTITY2', 'WIP_TXN_ALLOCATIONS');
4462: l_msg := fnd_message.get;
4463: wip_logger.log(p_msg => l_msg,
4464: x_returnStatus => l_returnStatus);
4465: END IF;

Line 4496: * WIP_COST_TXN_INTERFACE and WIP_TXN_ALLOCATIONS IF needed

4492:
4493: /*****************************************************************************
4494: * This procedure is equivalent to witpsdo_dept_overheads in wiltps3.ppc
4495: * This procedure is used to insert department overhead info into
4496: * WIP_COST_TXN_INTERFACE and WIP_TXN_ALLOCATIONS IF needed
4497: ****************************************************************************/
4498: PROCEDURE insert_dept_overhead(p_gib IN group_rec_t,
4499: x_returnStatus OUT NOCOPY VARCHAR2) IS
4500:

Line 5462: | Generate transaction_id for WIP_TXN_ALLOCATIONS |

5458: END IF; -- Per order basis type for repetitive
5459:
5460:
5461: /*------------------------------------------------------------+
5462: | Generate transaction_id for WIP_TXN_ALLOCATIONS |
5463: +------------------------------------------------------------*/
5464: UPDATE wip_cost_txn_interface
5465: SET transaction_id = wip_transactions_s.nextval
5466: WHERE group_id = p_gib.group_id

Line 5489: | Columns to insert into WIP_TXN_ALLOCATIONS |

5485: | per lot
5486: +------------------------------------------------------------*/
5487:
5488: /*------------------------------------------------------------+
5489: | Columns to insert into WIP_TXN_ALLOCATIONS |
5490: | |
5491: | transaction_id, |
5492: | repetitive_schedule_id, organization_id, |
5493: | last_update_date, last_updated_by, creation_date, |

Line 5500: INSERT INTO wip_txn_allocations

5496: | transaction_quantity, |
5497: | primary_quantity, |
5498: | |
5499: +------------------------------------------------------------*/
5500: INSERT INTO wip_txn_allocations
5501: (transaction_id,
5502: repetitive_schedule_id,
5503: organization_id,
5504: last_update_date,

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

5586: -- IF debug message level = 2, write statement below to log file
5587: IF (l_logLevel <= wip_constants.full_logging) THEN
5588: fnd_message.set_name('WIP', 'WIP_INSERTED_ROWS');
5589: fnd_message.set_token('ENTITY1', SQL%ROWCOUNT);
5590: fnd_message.set_token('ENTITY2', 'WIP_TXN_ALLOCATIONS');
5591: l_msg := fnd_message.get;
5592: wip_logger.log(p_msg => l_msg,
5593: x_returnStatus => l_returnStatus);
5594: END IF;

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

9446: raise fnd_api.g_exc_unexpected_error;
9447: END IF; -- check return status
9448:
9449: -- Only call the cost allocation IF schedule transactions and auto resource
9450: -- per item exist (insert into WIP_TXN_ALLOCATIONS)
9451: IF(l_move.scheTxn = WIP_CONSTANTS.YES AND
9452: l_move.rsrcItem = WIP_CONSTANTS.YES) THEN
9453:
9454: insert_txn_alloc(p_gib => p_gib,