FROM is to be determined as efficiently as possible. Within the functions, the existence of a specified row (not necessarily specified in full) or, forĮxample, a row number as the starting point of a subsequent sequential read using LOOP.Outside the functions, the main purpose of an explicitly specified table key is to read precisely one fully specified row.The differing behavior of the specified key outside and inside the functions line_exists and line_index is explained as follows:.If this covers the primary table key, it is used for optimized reads on sorted tables and hashed tables. Instead, the variant with a free search key can be used. Table key do not have to specify it explicitly. Table key can be used explicitly in this variant, the key must first be specified using its predefined name primary_key or an alias name. The attributes KEY_NAME and (if the table is not empty) KEY_COMP_VALUES are not filled here. Since every individual read might need to fail or succeed individually this quickly balloons out of proportion: TRY. If no row is found for the specified table key, the handleable exception CX_SY_ITAB_LINE_NOT_FOUND is Which is both longer and makes any simple read logic look incredibly complex and hard to read. Table key keyname and the key components can be specified statically or dynamically. Of the table key and the addition COMPONENTS can be omitted. Unlike the statement READ TABLE, a table expression must specify the name For both categories of secondary keys, components can be specified that are not part of the table key. A sorted table key does not have to beĬovered in full by specified components. READ TABLE and the key is joined with a table key. The search is performed as when specifying a free search key If the table expression is specified as an argument of the.The table key must be covered completely by specifying component and no components can be specified that are not part of the table key. Generally, the search is performed in exactly the same way as when specifying the table key WITH TABLE KEY.The table expression reads the row in accordance with the explicitly specified table key. The optimizations described under READ TABLE are performed when sorted tables and hashed tables are read.įree key specified, no binary searches can be forcedįor a table expression and it is not possible to specify explicit table key for optimizing searches using secondary keys. If the free key overlaps with some or all of the.The attributes KEY_NAME and KEY_COMP_VALUES are not filled here. If no row is found for the specified free key, the handleable exception CX_SY_ITAB_LINE_NOT_FOUND is usually raised. Also, compatible or convertible operands operand1 operand2. can be specified in accordance with the rules from the section In exactly the same way as when specifying the free search keyĬomp1 = operand1 comp2 = operand2. The table expression reads the row in accordance with the specified free search key. If no row exists for the specified index, the handleable exception CX_SY_ITAB_LINE_NOT_FOUND is usually raised. If the addition is used, the secondary table index of a sorted secondary key can be specified statically or dynamically. If the optional addition is not used, itab must be an Position and the optional KEY keyname INDEX is equivalent to the USING KEY keyname specified. The row is read in exactly the same way as when specifying an index, INDEX idx, in the statement READ TABLE. The table expression reads the row with the row number specified in idx with Specifies a table row in the square brackets of a table expression. ABAP - Keyword Documentation →Įxpressions and Functions for Internal Tables → (include) program "CL_AGS_RI_MONID=CM002".Ĩ3 DATA(lt_selopt) = VALUE #( -metric_parameters-low.SAP NetWeaver AS ABAP Release 750, ©Copyright 2016 SAP AG. The procedure is in program "CL_AGS_RI_MONID=CP". This exception was not handled locally or declared in the RAISINGĬlause in the procedure's signature however. The termination is due to exception "CX_SY_ITAB_LINE_NOT_FOUND" occurring in In the source code, the termination point is in line 85 of (Include) The termination occurred in ABAP program "CL_AGS_RI_MONID=CP", Row index (for "INDEX" access) / key name (for "KEY" access): 1. Since the caller of the procedure could not have anticipated thisĮxception, the current program was terminated. "GET_ALL_MONIDS" "(METHOD)", nor was it propagated by a RAISING clause. TheĮxception is assigned to class 'CX_SY_ITAB_LINE_NOT_FOUND' and was not caught Within SAP Solution Manager 7.2, attempting to update the AKF Repository for the BPA Twincubes connector instance within Business Process Improvement - Administration fails with the following shortdump:ĪBAP Program CL_AGS_RI_MONID=CPĪn exception has occurred which is explained in more detail below.
0 Comments
Leave a Reply. |