Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DB-DB4 (Application Component) DB2 for AS/400⤷
STU4 (Package) CCMS / AS/400
Basic Data
| Data Element | QQC103 |
| Short Description | SQL package name |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | QQC10 | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 8 | SQL pkg. |
| Medium | 15 | SQL packageName |
| Long | 16 | SQL package name |
| Heading | 10 | SQL pkg. |
Documentation
Definition
QQC103 is the name of the SQL package that contains the prepared statement used to implement the query.
The combination of QQSTN),QQC104 (QQPLIB) and QQC103 (QQPNAM) defines which statement in which SQL package was used to implement the query. QQC104 (QQPLIB) is the name of the library that contains the package.
This information is only available for records with QQRID 1000.
Note
When a query is run on an SAP System for the first time, the optimizer prepares this statement into an SQL package. In that way, when the query is run again - the host variables used in later query runs may differ from the host variables used the first time - the optimizer does not need to do all the work again, instead the access plan that was saved in the SQL package is used.
Depending on the statement identification assigned to a query, the prepared statement is stored in a specific type of SQL package.
Examples:
ABAP SQL packages: The package SAPLSTRUGJ contains prepared statements for queries run using the ABAP source SAPLSTRU.
Table packages: the package D010TFC contains prepared statements for queries performed on table D010T.
The type of SQL package determines when a the statement has to be prepared again for a query, even if one already exists in the package.
Examples:
ABAP packages: The ABAP program was regenerated after the statement was prepared into the package.
Table packages: The table was regenerated after the last statement preparation). A new package is created if the date (month/day/year) of the regeneration of the object differs from the last generation date. (Packages that are no longer useful will be deleted during the next start of the main instance).
In this way, one package can contain several prepared statements for different queries and/or the same query.
Types and Naming Conventions for SQL Packages:
The type of the SQL package specifies the object type that was used to identify the statement. Examples of types are:
0: ABAP source; 1: C program source; 2: ABAP Dynpro; 3: SAP table; and so on.
Depending on the package type, the packages are stored into different libraries.
Package library names follow the pattern: R3<SID><type><year>n
where "SID" is the SAP system ID, "type" is the type of the SQL package, "year" is a three digit number where the the century is left out and "n" indicates whether or not an overflow package exists.
SQL package names follow the pattern: <name><month><day>
where name is the name of the object (max. 8 characters) for which statements are prepared into this package, month and day are one character representations of the timestamp of the object (A = 1, B = 2, .., Z = 26, 0 = 27, 1 = 28, 2 = 29, 3 = 30, 4 = 31)
Example
QQPLIB/QQPNAM: R3C8101960/SAPLALDBAZ
means that the package is for SAP System C81 and contains all prepared statements identified by the ABAP program SAPLALDB since the the 26th January 1996 (last generation date of this program).
History
| Last changed by/on | SAP | 20070813 |
| SAP Release Created in |
