1 PACKAGE HZ_BES_BO_TRACKING_PVT AS
2 /*$Header: ARHBOTVS.pls 120.0 2005/07/29 00:01:56 smattegu noship $ */
3
4 /*
5 PROCEDURE create_bot
6 Scope: This is the public procedure that is called by other teams to populate BOT
7
8 DESCRIPTION
9 This creates child, parent entries in BOT.
10 Input Parameters
11 p_init_msg_list Initialize message stack
12 p_CHILD_BO_CODE Child entity BO code. validated by HZ_BUSINESS_OBJECTS lookup type
13 P_CHILD_TBL_NAME Child entity database table name
14 p_CHILD_ID Child identifier,
15 p_child_opr_flag Operation performed on child record - I for insert and U for update.
16 P_CHILD_UPDATE_DT Child entity record last update date,
17 p_PARENT_BO_CODE Parent entity BO code. validated by HZ_BUSINESS_OBJECTS lookup type
18 P_PARENT_TBL_NAME Parent entity database table name
19 p_PARENT_ID Parent identifier,
20 p_parent_opr_flag Operation performed on parent record - I for insert and U for update.
21 p_GPARENT_BO_CODE Grand Parent entity BO code. validated by HZ_BUSINESS_OBJECTS lookup type
22 P_GPARENT_TBL_NAME Grand Parent entity database table name
23 p_GPARENT_ID Grand Parent identifier
24
25 Output Parameters
26 x_return_status OUT NOCOPY VARCHAR2,
27 x_msg_count OUT NOCOPY NUMBER,
28 x_msg_data OUT NOCOPY VARCHAR2
29
30
31 Validations:
32
33 1. Mandatory Input parameters are:
34 p_init_msg_list
35 P_CHILD_TBL_NAME
36 p_CHILD_ID
37 p_child_opr_flag
38 P_CHILD_UPDATE_DT
39 P_PARENT_TBL_NAME
40 p_PARENT_ID
41
42 2. If the entity table name is in the following list, ensure that the
43 grand parent info is passed. Otherwise, error out.
44 a. RA_CUST_RECEIPT_METHODS
45 b. IBY_FNDCPT_PAYER_ASSGN_INSTR_V
46 c. HZ_PER_PROFILES_EXT_VL
47 d. HZ_PARTY_SITES_EXT_VL
48 e. HZ_ORG_PROFILES_EXT_VL
49 f. HZ_LOCATIONS_EXT_VL
50
51 Called by:
52 1. This procedure is called by iPayment team to populate the BOT with
53 bank assignment (child), Customer Account (parent), party(grand parent).
54 2. This procedure is also called by TCA Extensibility EOs for
55 Org, Person, Localtion and PS.
56 In both cases, this procedure will write two records into BOT.
57 First record will have child, parent info.
58 Second record will have parent info as child info and grand parent record as parent info in BOT.
59
60 Example: iPayement APIs populating BOT by calling this procedure
61 create_bot(
62 p_CHILD_BO_CODE => NULL,
63 P_CHILD_TBL_NAME => 'IBY_FNDCPT_PAYER_ASSGN_INSTR_V',
64 p_CHILD_ID => <VALUE for instr_assignment_id >,
65 p_child_opr_flag => <'I' or 'U'>,
66 P_CHILD_UPDATE_DT => <last_update_date of instrument_assignment_rec>,
67 p_PARENT_BO_CODE => <'CUST_ACCT' or 'CUST_ACCT_SITE_USE'>,
68 -- based on whether instrument is a child of cust_acct or acct_site_use
69 P_PARENT_TBL_NAME => <'HZ_CUST_SITE_USES_ALL' or 'HZ_CUST_ACCOUNTS'>,
70 p_PARENT_ID => <value of ACCT_SITE_USE_ID or CUST_ACCOUNT_ID >,
71 p_parent_opr_flag => NULL,
72 p_GPARENT_BO_CODE => <'ORG_CUST' or 'PERSON_CUST'>,
73 -- based on party type of the party for which the customer account is associated with.
74 P_GPARENT_TBL_NAME => 'HZ_PARTIES',
75 p_GPARENT_ID => <value of party_id for which the customer account is associated with>,
76 x_return_status => x_ret_status,
77 x_msg_count => xmsg_ct,
78 x_msg_data => xmsg_data
79 );
80
81 */
82 PROCEDURE create_bot(
83 p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
84 p_CHILD_BO_CODE IN VARCHAR2,
85 P_CHILD_TBL_NAME IN VARCHAR2,
86 p_CHILD_ID IN NUMBER,
87 p_child_opr_flag IN VARCHAR2,
88 P_CHILD_UPDATE_DT IN DATE,
89 p_PARENT_BO_CODE IN VARCHAR2,
90 P_PARENT_TBL_NAME IN VARCHAR2,
91 p_PARENT_ID IN NUMBER,
92 p_parent_opr_flag IN VARCHAR2,
93 p_GPARENT_BO_CODE IN VARCHAR2,
94 P_GPARENT_TBL_NAME IN VARCHAR2,
95 p_GPARENT_ID IN NUMBER,
96 x_return_status OUT NOCOPY VARCHAR2,
97 x_msg_count OUT NOCOPY NUMBER,
98 x_msg_data OUT NOCOPY VARCHAR2
99 );
100 END HZ_BES_BO_TRACKING_PVT;
[Home] [Help]