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.PON_OPEN_INTERFACE_PVT dependencies on PON_CP_INTRFAC_TO_TRANSACTION

Line 2380: print_log('create_lines_with_children before calling PON_CP_INTRFAC_TO_TRANSACTION.SYNCH_FROM_INTERFACE');

2376: END LOOP;
2377:
2378: --g_module_prefix := g_module_prefix || 'create_lines_with_children';
2379: --print_log('Entered create_lines_with_children procedure');
2380: print_log('create_lines_with_children before calling PON_CP_INTRFAC_TO_TRANSACTION.SYNCH_FROM_INTERFACE');
2381: /*
2382: This api will have code for both adding and updating(amendments/new rounds) lines and its children like
2383: attributes, cost factors etc. While updating any line, it is expected to insert all children data
2384: in respective interface tables. The children that are missing from previous amendments

Line 2387: PON_CP_INTRFAC_TO_TRANSACTION.SYNCH_FROM_INTERFACE(p_batch_id,

2383: attributes, cost factors etc. While updating any line, it is expected to insert all children data
2384: in respective interface tables. The children that are missing from previous amendments
2385: are assumed as to-be-deleted children and will be deleted from main txn tables.
2386: */
2387: PON_CP_INTRFAC_TO_TRANSACTION.SYNCH_FROM_INTERFACE(p_batch_id,
2388: p_auction_header_id,
2389: g_user_id,
2390: l_trading_partner_id,
2391: 'N',

Line 2399: print_log('create_lines_with_children returned from PON_CP_INTRFAC_TO_TRANSACTION.SYNCH_FROM_INTERFACE with x_error_message '|| x_error_message);

2395: x_result,
2396: x_error_code,
2397: x_error_message
2398: );
2399: print_log('create_lines_with_children returned from PON_CP_INTRFAC_TO_TRANSACTION.SYNCH_FROM_INTERFACE with x_error_message '|| x_error_message);
2400: IF (x_error_message <> 'S') THEN
2401: x_return_status := FND_API.G_RET_STS_ERROR;
2402: FND_MESSAGE.SET_NAME('PON','PON_IMPORT_CREATE_LINES_ERR');
2403: FND_MESSAGE.SET_TOKEN('BATCH_ID',p_batch_id);

Line 2427: PON_CP_INTRFAC_TO_TRANSACTION.SYNCH_FROM_INTERFACE will calculate the attribute sequence number

2423:
2424: print_log('CP 0001');
2425: /*
2426: this loop will be used for amendments. Because for amendments
2427: PON_CP_INTRFAC_TO_TRANSACTION.SYNCH_FROM_INTERFACE will calculate the attribute sequence number
2428: for new attributes instead of taking value from interface tables.
2429: so we will have to update interface tables with new sequence number
2430: */
2431: IF (l_auction_round_number > 0 OR l_amendment_number > 0) THEN

Line 2465: /* PON_CP_INTRFAC_TO_TRANSACTION.SYNCH_FROM_INTERFACE api would have already inserted attributes

2461:
2462: print_log('create_lines_with_children validation scores');
2463:
2464: -- Insert scores for attributes
2465: /* PON_CP_INTRFAC_TO_TRANSACTION.SYNCH_FROM_INTERFACE api would have already inserted attributes
2466: But scores are not yet inserted. Also the above api inserts zero for weight and scores
2467: in attributes table. This needs to be corrected
2468: */
2469: VAL_ATTR_SCORES(

Line 2552: PON_CP_INTRFAC_TO_TRANSACTION.SYNCH_PAYMENTS_FROM_INTERFACE(

2548: UPDATE pon_auc_payments_interface papi
2549: SET papi.auction_Header_id = p_auction_header_id
2550: WHERE papi.batcH_id = p_batch_id;
2551:
2552: PON_CP_INTRFAC_TO_TRANSACTION.SYNCH_PAYMENTS_FROM_INTERFACE(
2553: p_batch_id,
2554: p_auction_header_id,
2555: x_result,
2556: x_error_code,