[Home] [Help]
20:
21: Assumptions of the Balancing API when being called:
22: 1. Each journal itself MUST be balanced by both the entered amounts and accounted amounts
23: at the header level
24: 2. Other then the normal required columns, the headers inserted into FUN_BAL_HEADERS_GT table
25: must have a status of 'OK' in order for the balancing API to process the header.
26: 3. The lines inserted into FUN_BAL_LINES_GT table must have the generated column set to 'N'.
27: 4. The calling program would have to display the errors found in FUN_BAL_ERRORS_GT to the user
28: using their own FND_MESSAGES, as the message details and the context to be displayed to the
26: 3. The lines inserted into FUN_BAL_LINES_GT table must have the generated column set to 'N'.
27: 4. The calling program would have to display the errors found in FUN_BAL_ERRORS_GT to the user
28: using their own FND_MESSAGES, as the message details and the context to be displayed to the
29: user are different for different calling programs. The calling probrams can use the
30: FUN_BAL_HEADERS_GT table to figure out which journals contain an error. A journal ended
31: in error would have its status set to 'ERROR'.
32: 5. The balancing API is currently using FND logging framework to log any other error, warning
33: or debug messages into FND log. Please note that the standard API parameter x_msg_data
34: from the journal_balancing procedure call does not return any values since it is duplicating
118:
119:
120: */
121:
122: TYPE headers_tab_type IS TABLE OF fun_bal_headers_gt%rowtype;
123: TYPE lines_tab_type IS TABLE OF fun_bal_lines_gt%rowtype;
124: TYPE results_tab_type IS TABLE OF fun_bal_results_gt%rowtype;
125: TYPE errors_tab_type IS TABLE OF fun_bal_errors_gt%rowtype;
126: TYPE inter_le_bsv_map_tab_type IS TABLE OF fun_bal_inter_bsv_map_t%rowtype;
185: not preferred because bulk loading can not be utilized. There would be 32 times processing
186: overhead in performing the loop shown below. It might be possible to use the cursor as
187: a table and perform the insertion, but it is not clear what kind of performance we would
188: get out of it.
189: TYPE headers_tab_type IS REF CURSOR RETURN fun_bal_headers_gt%rowtype;
190: TYPE lines_tab_type IS REF CURSOR RETURN fun_bal_lines_gt%rowtype;
191: TYPE results_tab_type IS REF CURSOR RETURN fun_bal_results_gt%rowtype;
192: TYPE errors_tab_type IS REF CURSOR RETURN fun_bal_errors_gt%rowtype;
193: TYPE le_bsv_map_tab_type IS REF CURSOR RETURN fun_bal_le_bsv_map_gt%rowtype;
193: TYPE le_bsv_map_tab_type IS REF CURSOR RETURN fun_bal_le_bsv_map_gt%rowtype;
194: TYPE inter_int_tab_type IS REF CURSOR RETURN fun_bal_inter_int_gt%rowtype;
195: TYPE intra_int_tab_type IS REF CURSOR RETURN fun_bal_intra_int_gt%rowtype;
196: PROCEDURE auto_test1(test_csr IN test_csr_type1) IS
197: test_csr_rec fun_bal_headers_gt%rowtype;
198: PRAGMA AUTONOMOUS_TRANSACTION;
199: BEGIN
200: LOOP
201: FETCH test_csr into test_csr_rec;
199: BEGIN
200: LOOP
201: FETCH test_csr into test_csr_rec;
202: EXIT WHEN test_csr%NOTFOUND;
203: INSERT INTO fun_bal_headers_gt values test_csr_rec;
204: END LOOP;
205: --INSERT INTO fun_bal_headers_gt SELECT * FROM test_csr;
206: COMMIT;
207: RETURN;
201: FETCH test_csr into test_csr_rec;
202: EXIT WHEN test_csr%NOTFOUND;
203: INSERT INTO fun_bal_headers_gt values test_csr_rec;
204: END LOOP;
205: --INSERT INTO fun_bal_headers_gt SELECT * FROM test_csr;
206: COMMIT;
207: RETURN;
208: END auto_test1;
209: