Deploying a first IAL fails on a line that calls a standard API function inside the SELECT statement (like Shop_Ord_API.Get_State), even though &AO.. is correctly used to prefix the table/view references elsewhere in the same query — is the &AO.. prefix required somewhere else too, or are API calls just not allowed in an IAL at all?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

API calls need the &AO.. prefix too, not just table and view references — for example, &AO..Shop_Ord_API.Get_State(...), not just Shop_Ord_API.Get_State(...) on its own. At runtime, &AO.. gets substituted with the actual application-owner schema that owns the database objects (tables, views, and API packages alike); omitting it on an API call makes the query look for that package under your own querying user's schema instead, which doesn't have it — producing exactly the kind of deployment error you'd see from a genuinely missing/invalid object reference.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions