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.PA_IC_INV_UTILS dependencies on PA_PLSQL_DATATYPES

Line 177: ( P_BILL_TO_ADDRESS_ID IN PA_PLSQL_DATATYPES.IdTabTyp ,

173: -- X_BILL_TO_SITE_STATUS VARCHAR2
174: -- X_SHIP_TO_SITE_STATUS VARCHAR2
175: --
176: PROCEDURE Get_active_sites
177: ( P_BILL_TO_ADDRESS_ID IN PA_PLSQL_DATATYPES.IdTabTyp ,
178: P_SHIP_TO_ADDRESS_ID IN PA_PLSQL_DATATYPES.IdTabTyp ,
179: P_NO_OF_RECORDS IN NUMBER,
180: P_CUST_CREDIT_HOLD IN OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp,
181: X_BILL_TO_SITE_USE_ID OUT NOCOPY PA_PLSQL_DATATYPES.IdTabTyp,

Line 178: P_SHIP_TO_ADDRESS_ID IN PA_PLSQL_DATATYPES.IdTabTyp ,

174: -- X_SHIP_TO_SITE_STATUS VARCHAR2
175: --
176: PROCEDURE Get_active_sites
177: ( P_BILL_TO_ADDRESS_ID IN PA_PLSQL_DATATYPES.IdTabTyp ,
178: P_SHIP_TO_ADDRESS_ID IN PA_PLSQL_DATATYPES.IdTabTyp ,
179: P_NO_OF_RECORDS IN NUMBER,
180: P_CUST_CREDIT_HOLD IN OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp,
181: X_BILL_TO_SITE_USE_ID OUT NOCOPY PA_PLSQL_DATATYPES.IdTabTyp,
182: X_SHIP_TO_SITE_USE_ID OUT NOCOPY PA_PLSQL_DATATYPES.IdTabTyp,

Line 180: P_CUST_CREDIT_HOLD IN OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp,

176: PROCEDURE Get_active_sites
177: ( P_BILL_TO_ADDRESS_ID IN PA_PLSQL_DATATYPES.IdTabTyp ,
178: P_SHIP_TO_ADDRESS_ID IN PA_PLSQL_DATATYPES.IdTabTyp ,
179: P_NO_OF_RECORDS IN NUMBER,
180: P_CUST_CREDIT_HOLD IN OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp,
181: X_BILL_TO_SITE_USE_ID OUT NOCOPY PA_PLSQL_DATATYPES.IdTabTyp,
182: X_SHIP_TO_SITE_USE_ID OUT NOCOPY PA_PLSQL_DATATYPES.IdTabTyp,
183: X_BILL_TO_SITE_STATUS OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp,
184: X_SHIP_TO_SITE_STATUS OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp);

Line 181: X_BILL_TO_SITE_USE_ID OUT NOCOPY PA_PLSQL_DATATYPES.IdTabTyp,

177: ( P_BILL_TO_ADDRESS_ID IN PA_PLSQL_DATATYPES.IdTabTyp ,
178: P_SHIP_TO_ADDRESS_ID IN PA_PLSQL_DATATYPES.IdTabTyp ,
179: P_NO_OF_RECORDS IN NUMBER,
180: P_CUST_CREDIT_HOLD IN OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp,
181: X_BILL_TO_SITE_USE_ID OUT NOCOPY PA_PLSQL_DATATYPES.IdTabTyp,
182: X_SHIP_TO_SITE_USE_ID OUT NOCOPY PA_PLSQL_DATATYPES.IdTabTyp,
183: X_BILL_TO_SITE_STATUS OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp,
184: X_SHIP_TO_SITE_STATUS OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp);
185:

Line 182: X_SHIP_TO_SITE_USE_ID OUT NOCOPY PA_PLSQL_DATATYPES.IdTabTyp,

178: P_SHIP_TO_ADDRESS_ID IN PA_PLSQL_DATATYPES.IdTabTyp ,
179: P_NO_OF_RECORDS IN NUMBER,
180: P_CUST_CREDIT_HOLD IN OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp,
181: X_BILL_TO_SITE_USE_ID OUT NOCOPY PA_PLSQL_DATATYPES.IdTabTyp,
182: X_SHIP_TO_SITE_USE_ID OUT NOCOPY PA_PLSQL_DATATYPES.IdTabTyp,
183: X_BILL_TO_SITE_STATUS OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp,
184: X_SHIP_TO_SITE_STATUS OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp);
185:
186:

Line 183: X_BILL_TO_SITE_STATUS OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp,

179: P_NO_OF_RECORDS IN NUMBER,
180: P_CUST_CREDIT_HOLD IN OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp,
181: X_BILL_TO_SITE_USE_ID OUT NOCOPY PA_PLSQL_DATATYPES.IdTabTyp,
182: X_SHIP_TO_SITE_USE_ID OUT NOCOPY PA_PLSQL_DATATYPES.IdTabTyp,
183: X_BILL_TO_SITE_STATUS OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp,
184: X_SHIP_TO_SITE_STATUS OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp);
185:
186:
187: -- This procedure will write the message in the PL SQL log file

Line 184: X_SHIP_TO_SITE_STATUS OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp);

180: P_CUST_CREDIT_HOLD IN OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp,
181: X_BILL_TO_SITE_USE_ID OUT NOCOPY PA_PLSQL_DATATYPES.IdTabTyp,
182: X_SHIP_TO_SITE_USE_ID OUT NOCOPY PA_PLSQL_DATATYPES.IdTabTyp,
183: X_BILL_TO_SITE_STATUS OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp,
184: X_SHIP_TO_SITE_STATUS OUT NOCOPY PA_PLSQL_DATATYPES.Char1TabTyp);
185:
186:
187: -- This procedure will write the message in the PL SQL log file
188: -- p_log_msg VARCHAR2 Yes