Skip to main content

How to call Autoinvoice Import Program (Program short name is RAXTRX) using FND_REQUEST.SUBMIT_REQUEST API

How to call Autoinvoice Import Program (Program short name is RAXTRX) using FND_REQUEST.SUBMIT_REQUEST API

Auto invoice Import Program takes the following parameters :

argv[0]  program name
argv[1]  parallel module name  [MAIN|PU?]
argv[2]  running mode  [V|T|P]
argv[3]  batch source id
argv[4]  batch source name
argv[5]  default date
argv[6]  concatenated transaction flexfield attribute value
argv[7]  transaction type id
argv[8]  low bill to customer number
argv[9]  high bill to customer number
argv[10]  low bill to customer name
argv[11] high bill to customer name
argv[12] low gl date
argv[13] high gl date
argv[14] low ship date
argv[15] high ship date
argv[16] low transaction number
argv[17] high transaction number
argv[18] low sales order
argv[19] high sales order
argv[20] low invoice date
argv[21] high invoice date
argv[22] low ship to customer number
argv[23] high ship to customer number
argv[24] low ship to customer name
argv[25] high ship to customer name
argv[26] Call RAXTRX from RAXMTR flag
argv[27] Base Due Date on invoice date flag
argv[28] Minimum Due Date offset from trx date
argv[29] Org_id

First, find out user_id and RESPONSIBILITY_ID through which you will submit the program to set the context :

SELECT USER_ID,RESPONSIBILITY_ID,RESPONSIBILITY_APPLICATION_ID,
SECURITY_GROUP_ID
FROM FND_USER_RESP_GROUPS
WHERE USER_ID = (SELECT USER_ID
FROM FND_USER
WHERE USER_NAME = '&user_name')
AND RESPONSIBILITY_ID = (SELECT RESPONSIBILITY_ID
FROM FND_RESPONSIBILITY_VL
WHERE RESPONSIBILITY_NAME = '&resp_name');

 
Using above query to get User ID, Resp Id and Application ID to pass in below code,
 
 
DECLARE
l_request_id NUMBER;
BEGIN
Fnd_Global.apps_initialize(userId,responsibilityId,applicationId)
-- replace the following code with correct value as get from sql above
Fnd_Global.apps_initialize(10178,50559,222);
l_request_id :=
fnd_request.submit_request
(application      => 'AR',
program          => 'RAXTRX',
description      => NULL,
start_time       => NULL,-- To start immediately
sub_request      => FALSE,
argument1        => 'MAIN',
argument2        => 'T',
argument3        => '1228',--batch_source_id
argument4        => 'LEGACY', --batch_source_name
argument5        => '2010/06/11 00:00:00', -- should be in format                                                     -- RR-MON-DD
argument6        => '',
argument7        => '',
argument8        => '',
argument9        => '',
argument10       => '',
argument11       => '',
argument12       => '',
argument13       => '',
argument14       => '',
argument15       => '',
argument16       => '',
argument17       => '',
argument18       => '63737', --sales_order low
argument19       => '63737', --sales_order high
argument20       => '',
argument21       => '',
argument22       => '',
argument23       => '',
argument24       => '',
argument25       => '',
argument26       => 'N',
argument27       => 'Y',
argument28       => '',
argument29       => '204', -- org_id
argument30       => chr(0) -- end with chr(0)as end of parameters
);
dbms_output.put_line(l_request_id);
END;





If you like please follow and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...