Getting API messages using fnd_msg_pub with output parameters p_msg_count and p_msg_data

In general, the public APIs have one or more output parameters to which error messages are written. The most typical parameters for this purpose are p_msg_data or x_msg_data. Some APIs have other error output parameters, some write messages to error tables, others just put error messages in the FND message buffer.

Example of getting API messages using fnd_msg_pub with output parameters p_msg_count and p_msg_data:

IF nvl(p_msg_count,1) = 1

THEN

dbms_output.put_line(p_msg_data);

ELSE

FOR i in 1 .. p_msg_count

LOOP

dbms_output.put_line

(fnd_msg_pub.get

(fnd_msg_pub.g_next, fnd_api.g_false) || i);

END LOOP;

END IF;

END;

Query to find API Name for oracle apps diffrent Module.

Most public APIs have the words 'pub' or 'api' in them, which helps narrow down the field. For example if you were looking for an inventory item API, you could search on the word ITEM as follows :

SELECT distinct object_name pkg, procedure$ proc

FROM dba_objects obj, sys.argument$ args

WHERE obj.object_id = args.obj#

AND obj.object_type = 'PACKAGE'

AND obj.owner = 'APPS'

AND ( obj.object_name LIKE '%API%'

OR obj.object_name LIKE '%PUB%' )

AND args.procedure$ LIKE '%ITEM%'

ORDER BY object_name, procedure$

Loading XSL files to Oracle apps

The seeded Java rule function performs the XSL transformation on the input and output messages by using the XML Gateway API, ECX_STANDARD.perform_xslt_transformation; therefore, the XSL files for the XSL transformation on input and output messages are loaded to Oracle XML Gateway using the oracle.apps.ecx.loader.LoadXSLTToClob loader.

it is process same as we are uploading LDT files.
As a result, use the following steps to perform XSL transformation during service invocation:

1. Upload the XSL files to Oracle E-Business Suite using the oracle.apps.ecx.loader.LoadXSLTToClob loader in Oracle XML Gateway.
   
2. Specify the XSL file names (such as PO_XSL_IN_2.xsl:FND:1.1) in the event or subscription parameters (WFBES_IN_XSL_FILENAME and WFBES_OUT_XSL_FILENAME) if applicable for XSL transformation on input and output messages.

For example, upload the XSL files to Oracle E-Business Suite as follows:

java oracle.apps.ecx.loader.LoadXSLTToClob apps apps 
ap601sdb:4115:owf12dev PO_XSL_IN_2.xsl FND 1.1