Subject: How to Generate Receiving Transaction Debug Statements in 11.5.10 Doc ID: Note:299497.

1 Type: HOWTO Last Revision Status: 30-MAY-2006 PUBLISHED Date: In this Document
Goal Solution

Applies to:
Oracle Inventory Management - Version: 11.5.10 Information in this document applies to any platform. FORM:RCVRCERC - Enter Receipts GUI FORM:RCVTXERT - Enter Receiving Transactions GUI FORM:RCVTXECO - Enter Corrections GUI FORM:RCVTXERE - Enter Returns GUI FORM:RCVSHESH - Maintain Shipments FORM:RCVRCMUR - Match Unordered Receipts EXECUTABLE:RVCTP - Receiving Transaction Processor EXECUTABLE:RCVTPO - Receiving Transaction Manager

Goal
What setup is required to create debug statements for Receiving activities in 11.5.10, and where will I find the debug information?

Solution
1. Set the following Profiles: RCV: Debug Mode=Yes PO:Enable Sql Trace for Receiving Processor=Yes FND: Debug Log Enabled=Yes FND: Debug Log Level=Statement FND: Debug Log Module=% Note: the FND Profile names above will not include the word "Debug" if $FND_TOP/patch/115/import/US/aflogpro.ldt is version 115.11. The absence or presence of the word "Debug" does not affect the debugging process so it is not necessary to apply a patch or change the Profile names. If you have questions/concerns about the FND Profile names, please log a Service Request with the AOL group. 2. If the Destination Type=Inventory, set the following Inventory debug Profiles: TP:INV Transaction processing mode=On-line INV: Debug Trace=Yes INV:Debug Level=10 INV: Debug file=<directory path returned from "select value from v$parameter where name = 'utl_file_dir';" PLUS file name>

**User must have write privilege to this directory; be sure to include the file name at the end of the path (e.g. '/usr/tmp/invdebug.log') 3. If the transaction is for an RMA, DropShip Purchase Order or Internal Sales Order/Requisition, set the following Profiles: OM: Debug = 5 OM: Debug Log Directory = <"select value from v$parameter where name = 'utl_file_dir';"> ** User must have write privilege to this directory 4. Log off and log back in the application for the Profile settings to take place. 5. Process the transaction. 6. Obtain the debug files: a. PO: For all RCV: Processing Modes, the Purchasing debug statements are inserted into FND_LOG_MESSAGES table. For RCV: Processing Mode=Immediate/Batch, the Purchasing debug statements will also be included in the Receiving Transaction Processor Request Log (View > Requests) b. INV(if INVdebug Profiles were set as noted above): the file specified in #2 c. OM (if OM debug Profiles were set as noted above): from the directory path specified in #3 7. Upload output from the following in Excel format, including Column Headings: a. For RCV: Processing Mode=Immediate or Batch: select to_char (timestamp,'DD-MON-YY HH:MM:SS:HH'), SUBSTR (message_text,1,300), SUBSTR (module,1,30), log_sequence from fnd_log_messages WHERE trunc(timestamp) = trunc(sysdate) AND process_id = (SELECT os_process_id FROM fnd_concurrent_requests WHERE request_id = &p_request_id) AND module not like 'fnd%' ORDER BY log_sequence; **where p_request_id = the request id for the Receiving Transaction Processor Concurrent Request -ORb. RCV: Processing Mode=On-line: select to_char (timestamp,'DD-MON-YY HH:MM:SS:HH'), SUBSTR (message_text,1,300), SUBSTR (module,1,30), log_sequence from fnd_log_messages

WHERE timestamp >= to_date('DD-MON-YYYY HH:MM:00','DD-MON-YYYY HH24:MI:SS') AND timestamp <= to_date('DD-MON-YYYY HH:MM:00','DD-MON-YYYY HH24:MI:SS') **substitute appropriate date and time values for DD-MON-YYYY HH:MM:00