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.JG_JOURNAL_ALLOCATIONS_PKG dependencies on FND_VSET

Line 301: l_vset fnd_vset.valueset_r;

297: | Main |
298: --------------------------------------------------------------------- */
299: PROCEDURE get_segments_info IS
300: l_segment_type fnd_flex_key_api.segment_type;
301: l_vset fnd_vset.valueset_r;
302: l_fmt fnd_vset.valueset_dr;
303: BEGIN
304: JG_UTILITY_PKG.log( '> JG_JOURNAL_ALLOCATIONS_PKG.get_segments_info');
305: --

Line 302: l_fmt fnd_vset.valueset_dr;

298: --------------------------------------------------------------------- */
299: PROCEDURE get_segments_info IS
300: l_segment_type fnd_flex_key_api.segment_type;
301: l_vset fnd_vset.valueset_r;
302: l_fmt fnd_vset.valueset_dr;
303: BEGIN
304: JG_UTILITY_PKG.log( '> JG_JOURNAL_ALLOCATIONS_PKG.get_segments_info');
305: --
306: -- Below info required if the zero-fill option is used for the segment method

Line 388: FND_VSET.get_valueset(G_acct_flex_segmt_arr(j).segment_vset_id,

384: l_segment_type := FND_FLEX_KEY_API.find_segment(JG_JOURNAL_ALLOCATIONS_PKG.G_flexfield_type,
385: JG_JOURNAL_ALLOCATIONS_PKG.G_structure_type,
386: G_acct_flex_segmt_arr(j).segment_name);
387: G_acct_flex_segmt_arr(j).segment_vset_id := l_segment_type.value_set_id;
388: FND_VSET.get_valueset(G_acct_flex_segmt_arr(j).segment_vset_id,
389: l_vset,
390: l_fmt); -- format type stored in here
391: G_acct_flex_segmt_arr(j).segment_vset_fmt_type := l_fmt.format_type;
392:

Line 436: l_vset fnd_vset.valueset_r;

432: -- l_zero_string VARCHAR2(25) := RPAD('0', 25, '0'); Default values not allowed in init.
433: l_zero_value VARCHAR2(25);
434: l_found BOOLEAN;
435: l_row NUMBER;
436: l_vset fnd_vset.valueset_r;
437: l_fmt fnd_vset.valueset_dr;
438: l_value fnd_vset.value_dr;
439: BEGIN
440: JG_UTILITY_PKG.log('> JG_JOURNAL_ALLOCATIONS_PKG.validate_have_zero_fills');

Line 437: l_fmt fnd_vset.valueset_dr;

433: l_zero_value VARCHAR2(25);
434: l_found BOOLEAN;
435: l_row NUMBER;
436: l_vset fnd_vset.valueset_r;
437: l_fmt fnd_vset.valueset_dr;
438: l_value fnd_vset.value_dr;
439: BEGIN
440: JG_UTILITY_PKG.log('> JG_JOURNAL_ALLOCATIONS_PKG.validate_have_zero_fills');
441: --

Line 438: l_value fnd_vset.value_dr;

434: l_found BOOLEAN;
435: l_row NUMBER;
436: l_vset fnd_vset.valueset_r;
437: l_fmt fnd_vset.valueset_dr;
438: l_value fnd_vset.value_dr;
439: BEGIN
440: JG_UTILITY_PKG.log('> JG_JOURNAL_ALLOCATIONS_PKG.validate_have_zero_fills');
441: --
442: -- consider each segment separately

Line 461: FND_VSET.get_valueset(G_acct_flex_segmt_arr(j).segment_vset_id,

457: -- Need to retrieve the valueset record structure for the current segment as we cannot store
458: -- PLSQL tables of composite structures such as this one. Consequently, the table
459: -- G_acct_flex_segmt_arr in Get_Segments_Info doesn't hold the valueset record.
460: --
461: FND_VSET.get_valueset(G_acct_flex_segmt_arr(j).segment_vset_id,
462: l_vset,
463: l_fmt); -- format type stored in here
464:
465: JG_UTILITY_PKG.debug( 'segment position num = '||TO_CHAR(j));

Line 469: FND_VSET.get_value_init(l_vset, TRUE);

465: JG_UTILITY_PKG.debug( 'segment position num = '||TO_CHAR(j));
466: JG_UTILITY_PKG.debug( 'max size = '||TO_CHAR(l_fmt.max_size));
467: FOR k IN REVERSE 1..l_fmt.max_size LOOP
468: l_zero_value := SUBSTR(RPAD('0', 25, '0'), 1, k); --l_zero_string replaced
469: FND_VSET.get_value_init(l_vset, TRUE);
470: FND_VSET.get_value(l_vset, l_row, l_found, l_value);
471: WHILE l_found LOOP
472: IF l_zero_value = l_value.value THEN
473: JG_JOURNAL_ALLOCATIONS_PKG.G_zero_fill_arr(j).zero_string := l_value.value;

Line 470: FND_VSET.get_value(l_vset, l_row, l_found, l_value);

466: JG_UTILITY_PKG.debug( 'max size = '||TO_CHAR(l_fmt.max_size));
467: FOR k IN REVERSE 1..l_fmt.max_size LOOP
468: l_zero_value := SUBSTR(RPAD('0', 25, '0'), 1, k); --l_zero_string replaced
469: FND_VSET.get_value_init(l_vset, TRUE);
470: FND_VSET.get_value(l_vset, l_row, l_found, l_value);
471: WHILE l_found LOOP
472: IF l_zero_value = l_value.value THEN
473: JG_JOURNAL_ALLOCATIONS_PKG.G_zero_fill_arr(j).zero_string := l_value.value;
474: JG_JOURNAL_ALLOCATIONS_PKG.G_zero_fill_arr(j).segment_col_name := G_acct_flex_segmt_arr(j).segment_col_name;

Line 477: FND_VSET.get_value(l_vset, l_row, l_found, l_value);

473: JG_JOURNAL_ALLOCATIONS_PKG.G_zero_fill_arr(j).zero_string := l_value.value;
474: JG_JOURNAL_ALLOCATIONS_PKG.G_zero_fill_arr(j).segment_col_name := G_acct_flex_segmt_arr(j).segment_col_name;
475: GOTO value_found;
476: ELSE
477: FND_VSET.get_value(l_vset, l_row, l_found, l_value);
478: END IF;
479: END LOOP;
480: FND_VSET.get_value_end(l_vset);
481: END LOOP;

Line 480: FND_VSET.get_value_end(l_vset);

476: ELSE
477: FND_VSET.get_value(l_vset, l_row, l_found, l_value);
478: END IF;
479: END LOOP;
480: FND_VSET.get_value_end(l_vset);
481: END LOOP;
482: FND_MESSAGE.SET_NAME(JG_JOURNAL_ALLOCATIONS_PKG.G_JG_appln_short_name, 'JG_ZZ_ZERO_FILL_INVALID');
483: RETURN FALSE;
484: <>