WSH_DEBUG_SV

Using WSH_DEBUG_SV package for a better Debug method for Order Management and Shipping modules.

Use wsh_debug_sv.start_debugger procedure to get the debug messages at
Performance
Statement
Procedure
Event
Exception
Error
Unexpected Error level

Define the profile option WSH:Debug Enabled at User Level.
Define the profile option  WSH:Debug Level at one of the values mentioned above
The default value is at Procedure, but for the user level you can set this at any level.

Create a directory on the application server and set up a directory for the debug log.
Define the profile option WSH:Debug Log Directory  to the directory created.


When using in the code Define the parameters

      file_name                   VARCHAR2 (100);
      return_status               VARCHAR2 (10);
      msg_count                   NUMBER;
      msg_data                    VARCHAR2 (3000);


      wsh_debug_sv.start_debugger (file_name,
                                                        return_status,
                                                        msg_count,
                                                        msg_data);

wsh_debug_sv.stop_debugger;

Right before the end of the code use the stop_debugger . You can use dbms_output of fnd_file to display the file name to find out the log file and look in the directory defined above.

Comments

Post a Comment

Popular posts from this blog

Create attachments and attach them to Sales Order Header or Order Lines

Use the API below to create the attachment. This could be a limited text that you want on the order header or line. OE_FND_ATTACHMENTS_PUB.CREATE_SHORT_TEXT_DOCUMENT (1.0, --version P_SHORT_TEXT, --Text to be added as attachment P_CATEGORY_ID, -- Attachment category id P_DESCRIPTION, -- Attachment description NULL, V_SECURITY_ID, --The value is 4 for no security NULL, 'Y', 'O', -- One time usage SYSDATE, NULL, NULL, V_DOCUMENT_ID , -- Document id returned by the API V_RETURN_STATUS_CS, V_MSG_COUNT_CS, V_MSG_DATA_CS); Pass V_DOCUMENT_ID from above API into below second API OE_FND_ATTACHMENTS_PUB.ADD_ATTACHMENT (1.0, P_ENTITY_NAME, --Value of this parameter would be 'OE_ORDER_HEADERS' for header level attachment -- and 'OE_ORDER_LINES' for line level attachment P_PK1_VALUE, --line id or header id (For line level or header level attachment) NULL, NULL, NULL, NULL, 'N', NULL, V_DOCUMENT_ID , --Document id from above ap...
Read more

Link XLA Tables With AR Tables To Get Information From GL

There is   no one-to-one mapping between AR, XLA and GL. The data that actually posts to the GL is the XLA table data, not AR. Depending on the AAD rules you have defined, one row that appears in AR could become 10 in XLA_DISTRIBUTION_LINKS, but when the data is posted into the GL, the accounts of the same type and ccid are merged to a single entry. For example, a transaction could have 34 gl_dist rows, but 201 rows in ar_distribution_links, but when it actually posts, consolidates to 9 rows in gl_import_references. The main link to bind information together is the gl_sl_link_id. It will show in the gl_je_lines, gl_import_refernces and xla_ae_lines table. Also, the XLA_DISTRIBUTION_LINKS table contains the application_id, event_id, ae_header_id, ae_line_num from the XLA Tables and source_distribution_id_num_1 will be the cust_trx_line_gl_dist_id in the case of a transaction. ACTION: COMPLETE TRANSACTION : RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID = RA_CUST_TRX_LINE_GL_DIST_ALL.CUS...
Read more