Professional Documents
Culture Documents
Oracle Work in Process (WIP) - Release 11.5
Oracle Work in Process (WIP) - Release 11.5
Common Requirements......................................................................................................................... 3
Background means..........................................................................................................................11
Background means..........................................................................................................................14
Background means..........................................................................................................................16
Background means..........................................................................................................................20
MOBILE.....................................................................................................................................................22
WORKBENCH
Job Creation / If WIP:Discrete Job Definition Form is If WIP:Discrete Job Definition
Scheduling Issues ‘Interactive Definition’, change it to Form is ‘Concurrent Definition’ get
‘Concurrent Definition’ and follow us
steps for the Background Mode. The log file of WIP Concurrent
Exploder request
Raw and tkprofed trace file of WIP
Concurrent Explider
OTHERS/MISC N/A Log file for Concurrent request for
Lead Time LeadTime Calculation
Calculation
OTHERS/MISC Log file and trace files for Concurrent Log file for Concurrent request for
Close Jobs request for ‘Close Jobs’ ‘Close Jobs’
OTHERS/MIS Log file and trace files for Concurrent Log file for Concurrent request for
Purge Jobs request for ‘Purge Jobs’ ‘Purge Jobs’
Using the Application Release 11.5 standard CGI cartridge configuration file and
base HTML, it is possible to pass the parameters in the URL, since records and
collect are both defined in the appsweb.cfg file and the base HTML. For example,
For 11.5.10 and above, the WIP debug log files will be created if
1. FND: Debug Log Filename = (Make sure this is null)
2. FND: Debug Log Enabled = Yes
3. FND: Debug Log Level = Statement
4. FND: Debug Log Module = WIP%
To get the log file, run the following SQL script. This will create an output called
MoveON.txt
set pagesize 500
col message_text format a99
spool MoveON.txt
select message_text
from fnd_log_messages
where audsid=(select oracle_session_id
from fnd_concurrent_requests
where request_id =
&MOVE_TRNX_WORKER_REQUEST_ID)
order by log_sequence;
spool off;
For 11.5.9 and prior, there will be NO WIP log files generated for online cases.
For 11.5.10 and above, the WIP debug log files will be created if
1. FND: Debug Log Filename = (Make sure this is null)
2. FND: Debug Log Enabled= Yes
3. FND: Debug Log Level = Statement
4. FND: Debug Log Module = WIP%
To get the log file, run the following SQL script. This will create an output called
MoveBG.txt
set pagesize 500
col message_text format a99
spool MoveBG.txt
select message_text
from fnd_log_messages
where audsid=(select oracle_session_id
from fnd_concurrent_requests
where request_id = &MOVE_TRNX_WORKER_REQUEST_ID)
order by log_sequence;
spool off;
For 11.5.9 and prior, the WIP debug log files will be created if
1. TP: WIP Concurrent Message Level = Message Level 2
2. TP: WIP Debug Directory = <valid directory from v$parameter>
You can use the following query to find out a valid directory.
select value
from v$parameter
where name=’utl_file_dir’;
Note:
1. Log file will be generated in the last directory specified in v$parameter
select value
from v$parameter
where name=’utl_file_dir’;
2. File name generated will be of format ctoDDHH24MISS.dbg where DD is
the date, HH24MISS is the hour, minute and seconds.
Background means
TP: WIP Move Transaction = Background processing
TP: INV Transaction processing mode = Background Processing
script:
set pagesize 500
col message_text format a99
spool MoveON.txt
select message_text
from fnd_log_messages
where audsid=&audsid
order by log_sequence;
spool off
3. Upload the MoveON.txt generated from the above sql script
4. Upload the INV transaction log file from the directory specified in INV: Debug
file profile option.
Note: If you are having difficulties generating debug log files for ONLINE cases,
please set the profiles to background and provide the logs.
select message_text
from fnd_log_messages
where audsid=&audsid
order by log_sequence;
spool off
3. Upload the MoveBG.txt generated from the above sql script
4. Upload the INV transaction log file from the directory specified in INV: Debug
file profile option.
Background means
TP: WIP Completion Material Processing = Background processing
TP: INV Transaction processing mode = Background Processing
3. Upload the INV transaction log file from the directory specified in INV: Debug
file profile option.
Note: If you are having difficulties generating debug log files for ONLINE cases,
please set the profiles to background and provide the logs.
Background means
TP: WIP Material Transaction Form = Background processing
TP: INV Transaction processing mode = Background Processing
3. Upload the INV transaction log file from the directory specified in INV: Debug
file profile option.
Note: If you are having difficulties generating debug log files for ONLINE cases,
please set the profiles to background and provide the logs.
Cost Manager CMCTCM The Cost Manager invokes the material cost
manager and if WIP is installed, the resource cost
manager.
Material cost CMCMCW This subroutine polls the transaction table for
transaction uncosted transactions, and costs them by calling
worker the cost_trx library function.
Actual Cost CMCACW This actual cost worker processes material
Worker transactions that are assigned by the actual cost
manager in chronological order based on the
transaction_date and transaction_id. Depending
on the transaction origination (INV or WIP), the
appropriate cost processing routine will be
invoked.
Resource Cost CMCCTW Processes transactions that are assigned by the
Worker transaction manager through the group_id. The
type specifies the type of transactions within a
group.
TYPE 2 - Overhead
Operation CSTPOYLD CSTPOYLD.process_op_yield
Yield
Processor
To Enable Debug for Cost Manager, Stop the Cost Manager and set the following profile
options, and relaunch the Cost Manager.
Please provide the Cost Manager, Material Cost Transaction worker, Resource Cost
Worker, and Overhead Cost worker concurrent log files.
Background means
TP: WIP Work Order-less Completion Transaction Form = Background processing
TP: INV Transaction processing mode = Background Processing
Note: If you are having difficulties generating debug log files for ONLINE cases,
please set the profiles to background and provide the logs.
MOBILE
Start mobile server on a new port for logging a particular transaction, connect to this new
port, perform the transaction, reproduce the issue, exit from the mobile device and bring
down the port.
The following log files will be available in the location specified under wma.logdir
<portno>/System.log
<portno>.WIP.log
<portno>.INV.log
<portno>.WMS.log
Based on the type of transaction performed, only some of the above list of log files could
be generate and that is normal.
For generating trace for mobile transactions, see Metalink note 277655.1.