[Home] [Help]
The following lines contain the word 'select', 'insert', 'update' or 'delete':
| create, and delete any MRC data
|
| This procedure will call the appropriate MRC api with the
| information required.
|
| CALLS PROCEDURES / FUNCTIONS (local to this package body)
|
| PARAMETERS
| p_event_mode IN event to preform on MRC tables
| p_table_name IN Base Table Name.
| p_mode IN SINGLE /BATCH
| p_key_value IN primary key value
| p_key_value_list IN list of primarty key values
|
| KNOWN ISSUES:
|
| NOTES:
|
| MODIFICATION HISTORY
| Date Author Description of Change
| 10/03/00 Debbie Sue Jancis Created
| 02/27/01 Debbie Sue Jancis Modified due to complete rewrite of
| MRC API's.
| 07/10/01 Debbie Sue Jancis Modified due to change in parameters
| for MRC API's which include changes
| implemented to AP implementation.
| 08/27/01 Debbie Sue Jancis Modified due to changes in parameters
| for MRC API's which include performance
| changes and removal of dynamic sql.
*============================================================================*/
PG_DEBUG varchar2(1) := NVL(FND_PROFILE.value('AFLOG_ENABLED'), 'N');
| api's for insert/update and delete into the MRC tables based
| upon the base table name passed in.
|
| CALLS PROCEDURES / FUNCTIONS
|
| PARAMETERS
| p_table_name IN AR Base table name
| p_mode IN SINGLE OR BATCH
| p_key_value IN
| p_key_value_list IN
|
| KNOWN ISSUES:
| At first attempt this is a prototype for the AR_ADJUSTMENTS and
| AR_RATE_ADJUSTMENTS tables. Once the prototype is complete, the
| other tables affected by MRC trigger logic will be incorporated.
|
| NOTES:
|
| MODIFICATION HISTORY
| Date Author Description of Change
| 10/09/00 Debbie Sue Jancis Created
| 02/27/01 Debbie Sue Jancis Modified due to complete rewrite of
| MRC API's.
| 07/10/01 Debbie Sue Jancis Modified due to change in parameters
| for MRC API's which include changes
| implemented to AP implementation.
| 08/27/01 Debbie Sue Jancis Modified due to complete rewrite of
| MRC API's
|
*============================================================================*/
PROCEDURE init_struct(
p_table_name IN VARCHAR2,
p_mode IN VARCHAR2,
p_key_value IN NUMBER,
p_key_value_list IN gl_ca_utility_pkg.r_key_value_arr
) IS
BEGIN
--{BUG#4301323
NULL;
| This procedure will be called by autoinvoice to insert
| records into MRC tables using BULK processing
|
| CALLS PROCEDURES / FUNCTIONS
|
| ar_mc_info.inv_mrc_bulk_process (MRC bulk processing API
| called from AutoInvoice and copy trx
| for ar_adjustments, RA_CUSTOMER_TRX
| and ar_payment_schedules inserts)
| PARAMETERS
| p_request_id IN VARCHAR2
| p_tablename IN VARCHAR2 - AR BASE TABLE NAME
|
| KNOWN ISSUES:
|
| NOTES:
|
| For the initial coding, it was determined that this was required for
| the AR_ADJUSTMENTS table processing used in AUTOINVOICE to improve
| performance. Because a full analysis on the code has not been done
| for other tables, I am leaving in placeholders for those tables.
| if it is found that other calls will not be needed, those placeholders
| will be removed.
|
| MODIFICATION HISTORY
| Date Author Description of Change
| 07/18/01 Debbie Sue Jancis Created
| 03/11/02 Debbie Sue Jancis Modified for new strategy in calling
| MRC API once for autoinv and
| cpy trx processing. p_tablename will
| no longer represent a tablename but
| will have to represent a calling
| program. it will have RAXTRX or
| CPYTRX populated. Not changing the
| name as that would require the STUB
| program to have a change which would
| make a maintainance nightmare.
| 08/30/02 Debbie Sue Jancis Added additional program name
| 'GL_DIST' to process just the
| gl_dist lines by request id.
*============================================================================*/
PROCEDURE mrc_bulk_process (
p_request_id IN VARCHAR2,
p_table_name IN VARCHAR2
) IS
BEGIN
--{BUG4301323
NULL;