[Home] [Help]
16: -- ========================================
17: PROCEDURE setup_start_end_date (
18: p_packet_id IN NUMBER,
19: p_bc_packet_id IN NUMBER,
20: p_project_id IN pa_bc_packets.project_id%TYPE,
21: p_budget_version_id IN pa_bc_packets.budget_version_id%TYPE,
22: p_time_phase_type_code IN pa_budget_entry_methods.time_phased_type_code%TYPE,
23: p_expenditure_item_date IN DATE,
24: p_amount_type IN pa_budgetary_control_options.amount_type%TYPE,
17: PROCEDURE setup_start_end_date (
18: p_packet_id IN NUMBER,
19: p_bc_packet_id IN NUMBER,
20: p_project_id IN pa_bc_packets.project_id%TYPE,
21: p_budget_version_id IN pa_bc_packets.budget_version_id%TYPE,
22: p_time_phase_type_code IN pa_budget_entry_methods.time_phased_type_code%TYPE,
23: p_expenditure_item_date IN DATE,
24: p_amount_type IN pa_budgetary_control_options.amount_type%TYPE,
25: p_boundary_code IN pa_budgetary_control_options.boundary_code%TYPE,
22: p_time_phase_type_code IN pa_budget_entry_methods.time_phased_type_code%TYPE,
23: p_expenditure_item_date IN DATE,
24: p_amount_type IN pa_budgetary_control_options.amount_type%TYPE,
25: p_boundary_code IN pa_budgetary_control_options.boundary_code%TYPE,
26: p_set_of_books_id IN pa_bc_packets.set_of_books_id%TYPE,
27: x_start_date OUT NOCOPY DATE,
28: x_end_date OUT NOCOPY DATE,
29: x_error_code OUT NOCOPY NUMBER,
30: x_err_buff OUT NOCOPY VARCHAR2,
32: x_result_code OUT NOCOPY VARCHAR2 ) ;
33:
34:
35: -----------------------------------------------------------------------------------------------------------------
36: --This Api copies the project related records from gl_bc_packets to pa_bc_packets for document type AP,PO,REQ,
37: --CONTRACT PAYMENTS. For the document types CONTRACT COMMITMENT it copies records from
38: --IGC_CC_INTERFACE table , for the document type = EXP records are inserted into pa bc packets during costing
39: ------------------------------------------------------------------------------------------------------------------
40:
34:
35: -----------------------------------------------------------------------------------------------------------------
36: --This Api copies the project related records from gl_bc_packets to pa_bc_packets for document type AP,PO,REQ,
37: --CONTRACT PAYMENTS. For the document types CONTRACT COMMITMENT it copies records from
38: --IGC_CC_INTERFACE table , for the document type = EXP records are inserted into pa bc packets during costing
39: ------------------------------------------------------------------------------------------------------------------
40:
41: -- R12 Funds Management Uptake : Renamed procedure populate_plsql_tabs to copy_gl_pkt_to_pa_pkt. This procedure
42: -- will be fired from Main GL budgetary control API.
47: x_return_code OUT NOCOPY VARCHAR2 );
48:
49: ---------------------------------------------------------------------
50: -- this api creates the burden lines for the purchase order and
51: -- supplier invoice lines in pa_bc_packets
52: ---------------------------------------------------------------------
53: FUNCTION create_ap_po_bdn_lines
54: (p_packet_id IN NUMBER,
55: p_bc_packet_id IN NUMBER,
64: p_accounted_cr IN NUMBER,
65: p_compiled_multiplier IN NUMBER
66: ) RETURN boolean ;
67: ------------------------------------------------------------------------------------------------------------------
68: --This Api insert new records into pa bc packets if the project type is burdened.If the PO is based on REQ, or
69: --Invoice is based on PO then it takes the burden amount for the REQ or PO from pa_bc_commitments table
70: --and ensures that for req or po the old burden amount is used when reversing lines are passed in gl_bc_packets
71: ------------------------------------------------------------------------------------------------------------------
72: PROCEDURE Populate_burden_cost
77: ) ;
78:
79: -------------------------------------------------------------------------------------------------------
80: --This api copies the unreserved transaction into to the packet.
81: -- when the calling mode is unreserved then copy all the transactions from pa_bc_packets
82: -- for the old packet id(which is funds cheked and approved) to new packet by swapping the amount
83: -- columns and all other columns values remain same. Approve the packets with status Approved
84: -- donot create encumbrance liquidation as GL funds checker will create reversing lines
85: -- for the old packet id and donot populate burden rows / donot check for the unreserved packet
103:
104: FUNCTION get_start_or_end_date(
105: p_packet_id IN NUMBER,
106: p_bc_packet_id IN NUMBER,
107: p_project_id IN pa_bc_packets.project_id%TYPE,
108: p_budget_version_id IN pa_bc_packets.budget_version_id%TYPE,
109: p_time_phase_type_code IN pa_budget_entry_methods.time_phased_type_code%TYPE,
110: p_expenditure_item_date IN DATE,
111: p_amount_type IN pa_budgetary_control_options.amount_type%TYPE,
104: FUNCTION get_start_or_end_date(
105: p_packet_id IN NUMBER,
106: p_bc_packet_id IN NUMBER,
107: p_project_id IN pa_bc_packets.project_id%TYPE,
108: p_budget_version_id IN pa_bc_packets.budget_version_id%TYPE,
109: p_time_phase_type_code IN pa_budget_entry_methods.time_phased_type_code%TYPE,
110: p_expenditure_item_date IN DATE,
111: p_amount_type IN pa_budgetary_control_options.amount_type%TYPE,
112: p_boundary_code IN pa_budgetary_control_options.boundary_code%TYPE,
109: p_time_phase_type_code IN pa_budget_entry_methods.time_phased_type_code%TYPE,
110: p_expenditure_item_date IN DATE,
111: p_amount_type IN pa_budgetary_control_options.amount_type%TYPE,
112: p_boundary_code IN pa_budgetary_control_options.boundary_code%TYPE,
113: p_set_of_books_id IN pa_bc_packets.set_of_books_id%TYPE,
114: p_type IN varchar2 -- START_DATE or END_DATE
115: ) return DATE ;
116:
117: -- R12:Funds Managment Uptake: Deleting obsolete PROCEDURE checkCWKbdExp definition