eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.GCS_RULES_PROCESSOR dependencies on GCS_ENTRIES_GT

Line 195: gcs_entries_gt e

191: select distinct e.tgt_line_item_id lineItem,
192: nvl(ata.number_assign_value, 1) signFactor
193: from fem_ln_items_attr lia,
194: fem_ext_acct_types_attr ata,
195: gcs_entries_gt e
196: where ata.ext_account_type_code = lia.dim_attribute_varchar_member
197: and ata.attribute_id = ataAtt
198: and ata.version_id = ataVer
199: and lia.attribute_id = liaAtt

Line 249: --getLines cursor sums the balances from gcs_entries_gt by

245: ccyMinAcctUnit number := null;
246:
247: --Changes to this cursor also require changes to lineRec
248: --jh 4.26.04: Added description
249: --getLines cursor sums the balances from gcs_entries_gt by
250: --first obtain unique source-target lines (t1) then summing
251: --the sum
252:
253: cursor getLines is

Line 317: from gcs_entries_gt

313: min(tgt_user_dim9_id) tgt_user_dim9_id,
314: min(tgt_user_dim10_id) tgt_user_dim10_id,
315: min(nvl(output_amount, 0)) output_amount,
316: min(step_name) step_name
317: from gcs_entries_gt
318: Where currency_code = contextData.currencyCode
319: And output_amount <> 0
320: Group By rule_id,
321: step_seq,

Line 1068: -- Initialize data in the GCS_ENTRIES_GT table by creating source and

1064:
1065: end modelJoinClause;
1066:
1067: --+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1068: -- Initialize data in the GCS_ENTRIES_GT table by creating source and
1069: -- target dimensions, and setting related "friendly" data like names, formula.
1070: --
1071: -- FOR TARGET-ONLY dimension sets: see proc initEntriesGT_tgtDimSet elsewhere.
1072: --

Line 1075: -- The SQL stmt used to init the gcs_entries_gt table looks like...

1071: -- FOR TARGET-ONLY dimension sets: see proc initEntriesGT_tgtDimSet elsewhere.
1072: --
1073: -- FOR STANDARD dimension sets:
1074: --
1075: -- The SQL stmt used to init the gcs_entries_gt table looks like...
1076: --
1077: -- INSERT INTO GCS_ENTRIES_GT (
1078: -- rule_id, step_seq, formula_text,
1079: -- ad_input_amount, pe_input_amount, ce_input_amount, ee_input_amount,

Line 1077: -- INSERT INTO GCS_ENTRIES_GT (

1073: -- FOR STANDARD dimension sets:
1074: --
1075: -- The SQL stmt used to init the gcs_entries_gt table looks like...
1076: --
1077: -- INSERT INTO GCS_ENTRIES_GT (
1078: -- rule_id, step_seq, formula_text,
1079: -- ad_input_amount, pe_input_amount, ce_input_amount, ee_input_amount,
1080: -- output_amount,
1081: -- ,

Line 1290: entriesStmt := 'INSERT INTO GCS_ENTRIES_GT (

1286: logString(eventLogLevel, procedureName, 'section', '2');
1287: --=======================================================
1288:
1289: -- Start the statement
1290: entriesStmt := 'INSERT INTO GCS_ENTRIES_GT (
1291: rule_id, step_seq, step_name, formula_text, rule_step_id, offset_flag,
1292: sql_statement_num, currency_code, ad_input_amount, pe_input_amount,
1293: ce_input_amount, ee_input_amount, output_amount, entity_id,
1294: ytd_credit_balance_e, ytd_debit_balance_e' ||

Line 2005: FROM GCS_ENTRIES_GT E

2001: /*
2002: entriesStmt := entriesStmt || '
2003: AND NOT EXISTS(
2004: SELECT 1
2005: FROM GCS_ENTRIES_GT E
2006: WHERE E.ENTITY_ID = B.ENTITY_ID
2007: AND ( E.RULE_ID = :rid
2008: AND E.STEP_SEQ = :seq)' || adtColumnList ||'
2009: )';

Line 2089: -- Initialize data in the GCS_ENTRIES_GT table by creating source and

2085: end initEntriesGT_stdDimSet;
2086:
2087: --Bugfix 4928211: Added initEntriesGT: Used for performance purposes for consolidation rules
2088: --+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2089: -- Initialize data in the GCS_ENTRIES_GT table by creating source and
2090: -- target dimensions, and setting related "friendly" data like names, formula.
2091: --
2092: -- FOR TARGET-ONLY dimension sets: see proc initEntriesGT_tgtDimSet elsewhere.
2093: --

Line 2096: -- The SQL stmt used to init the gcs_entries_gt table looks like...

2092: -- FOR TARGET-ONLY dimension sets: see proc initEntriesGT_tgtDimSet elsewhere.
2093: --
2094: -- FOR STANDARD dimension sets:
2095: --
2096: -- The SQL stmt used to init the gcs_entries_gt table looks like...
2097: --
2098: -- INSERT INTO GCS_ENTRIES_GT (
2099: -- rule_id, step_seq, formula_text,
2100: -- ad_input_amount, pe_input_amount, ce_input_amount, ee_input_amount,

Line 2098: -- INSERT INTO GCS_ENTRIES_GT (

2094: -- FOR STANDARD dimension sets:
2095: --
2096: -- The SQL stmt used to init the gcs_entries_gt table looks like...
2097: --
2098: -- INSERT INTO GCS_ENTRIES_GT (
2099: -- rule_id, step_seq, formula_text,
2100: -- ad_input_amount, pe_input_amount, ce_input_amount, ee_input_amount,
2101: -- output_amount,
2102: -- ,

Line 2640: outputStmt := 'UPDATE gcs_entries_gt

2636: end if;
2637:
2638: --Bugfix 5075451: Added paranthesis around setOutput so calculation is done first then currency rounding
2639:
2640: outputStmt := 'UPDATE gcs_entries_gt
2641: SET output_amount = round((' || setOutput ||
2642: ') / :currPrecision) * :currPrecision
2643: WHERE rule_id = :rule_id
2644: AND step_seq = :seq';

Line 2722: -- Initialize data in the GCS_ENTRIES_GT table by creating source and

2718:
2719: end initEntriesGT;
2720:
2721: --+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2722: -- Initialize data in the GCS_ENTRIES_GT table by creating source and
2723: -- target dimensions and setting related outfile data like rule_id, names.
2724: --
2725: -- FOR STANDARD TARGET SETS: see proc initEntriesGT_stdDimSet elsewhere.
2726: --

Line 2729: -- We only have to insert into the gcs_entries_gt table the single

2725: -- FOR STANDARD TARGET SETS: see proc initEntriesGT_stdDimSet elsewhere.
2726: --
2727: -- FOR TARGET-ONLY dimension sets:
2728: --
2729: -- We only have to insert into the gcs_entries_gt table the single
2730: -- target DVS template, which must be a complete set of detail values...
2731: --
2732: -- The SQL stmt used to init the gcs_entries_gt table looks like...
2733: --

Line 2732: -- The SQL stmt used to init the gcs_entries_gt table looks like...

2728: --
2729: -- We only have to insert into the gcs_entries_gt table the single
2730: -- target DVS template, which must be a complete set of detail values...
2731: --
2732: -- The SQL stmt used to init the gcs_entries_gt table looks like...
2733: --
2734: -- INSERT INTO GCS_ENTRIES_GT (
2735: -- rule_id, step_seq, formula_text,
2736: -- input_amount, output_amount, )

Line 2734: -- INSERT INTO GCS_ENTRIES_GT (

2730: -- target DVS template, which must be a complete set of detail values...
2731: --
2732: -- The SQL stmt used to init the gcs_entries_gt table looks like...
2733: --
2734: -- INSERT INTO GCS_ENTRIES_GT (
2735: -- rule_id, step_seq, formula_text,
2736: -- input_amount, output_amount, )
2737: -- SELECT :rid, :seq, :ftx,
2738: -- 0, 0,

Line 2852: entriesStmt := 'INSERT INTO GCS_ENTRIES_GT (

2848: logString(eventLogLevel, procedureName, 'section', '3');
2849: --=======================================================
2850:
2851: -- Start the statement
2852: entriesStmt := 'INSERT INTO GCS_ENTRIES_GT (
2853: rule_id, step_seq, step_name, formula_text, rule_step_id,
2854: currency_code,ad_input_amount, pe_input_amount,
2855: ce_input_amount, ee_input_amount, output_amount' ||
2856: tgtColumnList || ')

Line 2972: -- to formulas, updating GCS_ENTRIES_GT with the results.

2968: end initEntriesGT_tgtDimSet;
2969:
2970: --+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2971: -- Use balances from FEM_Balances, GCS_AD_Trail_balances or both as inputs
2972: -- to formulas, updating GCS_ENTRIES_GT with the results.
2973: --
2974: -- PARAMETERS:
2975: -- stepSeq IN Number the step_seq value to process
2976: --

Line 3004: -- GCS_ENTRIES_GT e

3000: -- 0 ce_AMT,
3001: -- sum(ee.ytd_debit_balance_e - ee.ytd_credit_balance_e) EE_AMT
3002: -- FROM gcs_ad_trial_balances t1,
3003: -- fem_balances b,
3004: -- GCS_ENTRIES_GT e
3005: -- WHERE t1.ad_transaction_id = :xns
3006: -- AND t1.trial_balance_seq = 1
3007: -- AND b.entity_id = :eid
3008: -- AND b.dataset_code = :dci

Line 3207: FROM gcs_entries_gt

3203: varList := stepData(stepSeq).compiled_variables;
3204:
3205: SELECT count(*)
3206: INTO lRowCount
3207: FROM gcs_entries_gt
3208: WHERE rule_id = stepData(stepSeq).rule_id
3209: AND step_seq = stepSeq
3210: AND offset_flag = 'N';
3211:

Line 3467: UPDATE GCS_ENTRIES_GT

3463: --Update the ENTRIES table
3464: if row_id.FIRST IS NOT NULL then
3465:
3466: FORALL r IN row_id.FIRST .. row_id.LAST
3467: UPDATE GCS_ENTRIES_GT
3468: SET output_amount = decode(offset_flag,
3469: 'N',
3470: targetAmt(r),
3471: -1 * targetAmt(r)),

Line 3502: -- The result of this procedure is a GCS_ENTRIES_GT table with the fully

3498:
3499: end execFormulas;
3500:
3501: --+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
3502: -- The result of this procedure is a GCS_ENTRIES_GT table with the fully
3503: -- resolved dimension member combinations for every line of every dimension
3504: -- member set for each step for the rule. The table will have the source
3505: -- and target dimensions, the input and out values for the formula, the
3506: -- step name and friendly formula text, etc.

Line 3668: -- initialize a row in GCS_ENTRIES_GT for each source/target dim combo pair

3664: logString(eventLogLevel, procedureName, 'section', '3');
3665: --=======================================================
3666:
3667: --Loop through each step and...
3668: -- initialize a row in GCS_ENTRIES_GT for each source/target dim combo pair
3669: -- execute the formula for the step and update GCS_ENTRIES_GT for the result
3670: i := stepData.FIRST;
3671: While i IS NOT NULL Loop
3672:

Line 3669: -- execute the formula for the step and update GCS_ENTRIES_GT for the result

3665: --=======================================================
3666:
3667: --Loop through each step and...
3668: -- initialize a row in GCS_ENTRIES_GT for each source/target dim combo pair
3669: -- execute the formula for the step and update GCS_ENTRIES_GT for the result
3670: i := stepData.FIRST;
3671: While i IS NOT NULL Loop
3672:
3673: --=======================================================

Line 3680: -- Initialize rows in gcs_entries_gt for all steps

3676: 'step',
3677: 'begin ' || to_char(i));
3678: --=======================================================
3679:
3680: -- Initialize rows in gcs_entries_gt for all steps
3681: ruleStepId := stepData(i).rule_step_id;
3682:
3683: -- Fill the Dims arrays for this rule scope
3684: selectDims.DELETE;

Line 4130: -- Entry lines are an aggregation from the gcs_entries_gt table

4126: 'parameter',
4127: 'Currency Minimum Accountable Unit = ' ||
4128: to_char(ccyMinAcctUnit));
4129:
4130: -- Entry lines are an aggregation from the gcs_entries_gt table
4131: Open getLines;
4132: Fetch getLines Bulk Collect
4133: Into linesData;
4134:

Line 4147: -- in the GCS_ENTRIES_GT table. Then we can store the value

4143: --[xtd|ytd]_balances_e columns.
4144:
4145: -- To know what multiplier to use we have to get an attribute
4146: -- of an attribute of the line_item_id for every distinct lii
4147: -- in the GCS_ENTRIES_GT table. Then we can store the value
4148: -- onto the linsData.balance_factor record for use in the bulk
4149: -- insert that writes entry lines to GCS_ENTRY_LINES.
4150:
4151: --Get the attribute_id and version_id for the EXTENDED_ACCOUNT_TYPE

Line 5145: --into the GCS_ENTRIES_GT table for use in creating worksheet entries

5141: --Flag whether this is the STAT iteration, i.e., x = 2
5142: ruleIteration := x;
5143:
5144: --Run the rule step-by-step, storing the full details of the process
5145: --into the GCS_ENTRIES_GT table for use in creating worksheet entries
5146: --and writing the execution report
5147: processRuleSteps;
5148:
5149: --Use the very detailed output stored in the GCS_ENTRIES_GT table

Line 5149: --Use the very detailed output stored in the GCS_ENTRIES_GT table

5145: --into the GCS_ENTRIES_GT table for use in creating worksheet entries
5146: --and writing the execution report
5147: processRuleSteps;
5148:
5149: --Use the very detailed output stored in the GCS_ENTRIES_GT table
5150: --to create worksheet entries summarized across dimensions, and
5151: --balance any unbalanced entries where applicable
5152:
5153: BEGIN