App_query.append Usage (RPM)

When the item is checked against a form error, it is found that when using App_query.append, the query logs to a certain number of times: the number or value error. Later found on the Matalink after the original use app_query.append time, where statement inside the byte must be "2000, when greater than this number of bytes will overflow."

So by the way, I took a look at some of the functions inside the app_query and made the following notes.
App_query.append (' Block name ', User_where_clause): In the form, add a new where statement to the block query.
E.g: Add app_query.append in Pre-query (' ORDER ', ' oe_order_headers_v.order_type_id <> 1 '); The limit type is not one at the time of the query
App_query.reset (' Block name '): The first time the query condition is set to default_where. In form because of the security control, when using the App_query.append will limit the user to add the WHERE statement length = 2000 bytes, Once the 2000 is exceeded, an overflow error occurs: Number or character error, data not found ..., so you need to use App_query.reset to reset the where statement before using App_query.append
App_query.query_foreign_key (Block_name VARCHAR2,
Db_field VARCHAR2,
Non_db_field VARCHAR2,
TABLE_NAME VARCHAR2,
Id_column VARCHAR2,
Name_column VARCHAR2,
Extra_where_clause VARCHAR2 DEFAULT NULL): Used to add subqueries to non-database items in the corresponding view of the database
For example: App_query.query_foreign_key (' GROUPS ', ' application_id ', ' application_name ', ' fnd_application_vl ', ' APPLICATION_ ' ID ', ' application_name ');
After adding such a statement, the query is incremented: application_id in (the Select ' Application from FND_APPLICATION_VL where application_name = Groups.application_name | | Extra_where_clause)

FUNCTION Join (Clause1 VARCHAR2,
Clause2 VARCHAR2): Connects two where statements, returns CLAUSE1 and Clause2

App_query.append Usage (RPM)