Steps to modify CUSTOM.PLL
Here are the steps in short to modify CUSTOM.pll file - R12


Prerequisites :

Ensure that you have following files downloaded into your local machine before working on the CUSTOM.pll file.
APPCORE.pll
APPDAYPK.pll
FNDSQF.pll                                 
Steps :

Step1 :  Download the CUSTOM.PLL file from AU/resource top.

Step2 :  Open the Oracle Forms Builder, and open the CUSTOM.pll file.

Step3 :  Double click on the CUSTOM*(Package Body)

Step4 :  Add the code for the required event and for the desired form in the Package Body

Step5 :  Save the changes.

Step6 :  Compile the CUSTOM.pll file.(CTRL + SHIFT + K)

Step7 :  Upload(File Transfer using FTP tools) the updated CUSTOM.pll file to AU/resource top

Step8  :  Login to UNIX box and navigate to AU/resource top

Step9 :  Use the following command to create executable file(*.plx)
frmcmp_batch module=CUSTOM.pll userid=/@ module_type=LIBRARY compile_all=yes


Credits to
http://oracleebsgeeks.blogspot.com/2011/04/steps-to-modify-custompll.html

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