How to Delete Concurrent Program and Program Executable

When there is a need to delete/purge a concurrent program, we can do it from the back end.
Check first to see if the program exists by using

 Begin

declare 
v_exists  Boolean;

v_exists := fnd_program.program_exists(program => 'XX_SN',
                                           application =>'XXCUST');

if v_exists is true then 

BEGIN
   fnd_program.delete_program (program_short_name    =>'XX_SN',
                                                     application           =>'XXCUST');
   COMMIT;
END;


BEGIN
   fnd_program.delete_executable (executable_short_name    =>'XX_SN',
                                                         application           =>'XXCUST');
   COMMIT;
END;


End if;

End;

 Commit is the key here.

 You can use fnd_program.executable to register an executable from the back end.
Provide the parameters:
                 executable                     IN VARCHAR2,
                 application                  IN VARCHAR2,
                 short_name                      IN VARCHAR2,
                 description                     IN VARCHAR2 DEFAULT NULL,
                 execution_method                IN VARCHAR2,
                 execution_file_name             IN VARCHAR2 DEFAULT NULL,

You can use fnd_program.register to register an executable from the back end.

 Provide the parameters:
            program                      IN VARCHAR2,
            application          IN VARCHAR2,
            enabled             IN VARCHAR2,
            short_name              IN VARCHAR2,
            description            IN VARCHAR2 DEFAULT NULL,
            executable_short_name    IN VARCHAR2,
            executable_application    IN VARCHAR2
the rest of the parameters are Default Null.

 Explore fnd_program API for more options

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