[Home] [Help]
164: The plan:
165:
166: Set default values: status=N, industry=N, others null
167:
168: First, try to get exactly one row from FND_PRODUCT_INSTALLATIONS
169: for the product
170:
171: if found exactly one row,
172: return TRUE with values from that row
175: if more than one row,
176: go on to next step
177:
178: At this point we know we have multiple rows for the product
179: in FND_PRODUCT_INSTALLATIONS.
180:
181: NOTE: In R11 this condition should never
182: occur and therefore the remaining logic should be removed then.
183: Also note that in R11, the function get_app_info_other is obsolete
187:
188: Next, if install_group_num is null then get the install_group_num from
189: fnd_oracle_userid for the current user.
190:
191: Next, try to get exactly one row from FND_PRODUCT_INSTALLATIONS
192: for the product, install_group_num pair
193:
194: if found exactly one row,
195: return TRUE with values from that row
247: fpi.tablespace,
248: fpi.index_tablespace,
249: fpi.temporary_tablespace,
250: fpi.sizing_factor
251: from FND_PRODUCT_INSTALLATIONS FPI,
252: FND_ORACLE_USERID FOU,
253: FND_APPLICATION FA
254: where fpi.application_id = fa.application_id
255: and fpi.oracle_id = fou.oracle_id
327: -- that has been installed in more than one schema.
328: --
329: -- If we had been looking for a SOA product, we would have found it
330: -- already, because SOA products (install_group_num = 0) never have
331: -- more than one row in FND_PRODUCT_INSTALLATIONS.
332: --
333: -- If our reference schema is another MOA product account, or some other
334: -- schema registered with install_group_num != 0, we should find
335: -- exactly one row (or no rows) using the query below. In this case,
366: fpi.tablespace,
367: fpi.index_tablespace,
368: fpi.temporary_tablespace,
369: fpi.sizing_factor
370: from FND_PRODUCT_INSTALLATIONS FPI,
371: FND_ORACLE_USERID FOU,
372: FND_APPLICATION FA
373: where fpi.application_id = fa.application_id
374: and fpi.oracle_id = fou.oracle_id