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.WSM_SERIAL_SUPPORT_GRP dependencies on WIP_MOVPROC_GRP

Line 24: -- Or else the WIP API wip_movProc_grp.backflushIntoMTI will be invoked which would derive backflush components..

20: g_ret_unexpected varchar2(1) := FND_API.G_RET_STS_UNEXP_ERROR;
21:
22: -- This procedure will be invoked by the WIP move processor (for interface transactions)
23: -- If the transaction type is an undo/assembly return transaction populate_components will be invoked.
24: -- Or else the WIP API wip_movProc_grp.backflushIntoMTI will be invoked which would derive backflush components..
25:
26: Procedure backflush_comp(p_wipEntityID IN NUMBER,
27: p_orgID IN NUMBER,
28: p_primaryQty IN NUMBER,

Line 123: p_msg_text => 'Invoking wip_movProc_grp.backflushIntoMTI',

119:
120: IF (G_LOG_LEVEL_STATEMENT >= l_log_level) THEN
121: l_msg_tokens.delete;
122: WSM_log_PVT.logMessage (p_module_name => l_module ,
123: p_msg_text => 'Invoking wip_movProc_grp.backflushIntoMTI',
124: p_stmt_num => l_stmt_num ,
125: p_msg_tokens => l_msg_tokens ,
126: p_fnd_log_level => G_LOG_LEVEL_STATEMENT ,
127: p_run_log_level => l_log_level

Line 132: wip_movProc_grp.backflushIntoMTI ( p_wipEntityID => p_wipEntityID ,

128: );
129: END IF;
130:
131: -- else call WIP procedure.. (Please refer the WIP MED here )
132: wip_movProc_grp.backflushIntoMTI ( p_wipEntityID => p_wipEntityID ,
133: p_orgID => p_orgID ,
134: p_primaryQty => p_primaryQty ,
135: p_txnDate => p_txnDate ,
136: p_txnHdrID => p_txnHdrID ,