Parameter | Reference | Type | Length | Default | Optional | Text |
---|---|---|---|---|---|---|
CLIENT_FOR_UPGRADE | SYST-MANDT | C | 3 | ' ' | X | Client for Comparison/Adjustment |
COMPLEX_SELCONDS_USED | TVDIR-FLAG | C | 1 | ' ' | X | Flag: Selection Tabs Contain Complex Select. Cond. |
CORR_NUMBER | E070-TRKORR | C | 20 | ' ' | X | Correction Number for Changes Made |
FCODE | 0 | 'RDED' | X | Required Function of the Module | ||
NO_WARNING_FOR_CLIENTINDEP | 0 | ' ' | X | Flag: No Warning for Cross-Client Objects | ||
OC_INST | REF TO CL_VIEWFIELDS_ORG_CRIT | 0 | X | Organizational Criteria View Fields | ||
RFC_DESTINATION_FOR_UPGRADE | RFCDES-RFCDEST | C | 32 | ' ' | X | RFC Dest. of System for Comparison/Adjustment |
VIEW_ACTION | 0 | 'S' | X | View/Table Action: Display/Change/Transport | ||
VIEW_NAME | DD02V-TABNAME | C | 30 | Name of View/Table |
Parameter | Reference | Type | Length | Text |
---|---|---|---|---|
ACTION_OUT | SYCHAR01 | C | 1 | Valid Action Found: U/S/T |
CORR_NUMBER | E070-TRKORR | C | 20 | Correction Number for Changes Made |
LAST_ACT_ENTRY | SYST-TABIX | I | 4 | Index of Cursor Position in Display Table |
UCOMM | 0 | Last User Command in View Maintenance | ||
UPDATE_REQUIRED | 0 | Flag: Entries Changed. Save |
Parameter | Reference | Length | Optional | Text |
---|---|---|---|---|
CORR_KEYTAB | E071K | 282 | Table with Keys of Entries to be Transported | |
DBA_SELLIST | VIMSELLIST | 712 | Database Access Selection Conditions | |
DPL_SELLIST | VIMSELLIST | 712 | Display Selection Conditions | |
EXCL_CUA_FUNCT | VIMEXCLFUN | 23 | Table of User Interface Functions Not to be Activated | |
EXTRACT | 0 | Display Table | ||
TOTAL | 0 | Table with all Data Read from the Database | ||
X_HEADER | VIMDESC | 1556 | Control Block Table for the View/Table | |
X_NAMTAB | VIMNAMTAB | 520 | Control Block Table for the View/Table Fields |
Exception | Text |
---|---|
FUNCTION_NOT_FOUND | Function Module Not Found for View/Table |
MISSING_CORR_NUMBER | Correction Number Missing |
NO_VALUE_FOR_SUBSET_IDENT | No Default Value for a 'SUBSET' Field |
SAVING_CORRECTION_FAILED | Correction Entries Save Error |
INCLUDE 'DOCU_HAS_TO_BE_ELABORATED' OBJECT DOKU ID TX With the parameter CORR_NUMBER, you can pass a correction number.This correction number is only required in connection with theaction transport (parameter VIEW_ACTION). If you have not passed a correction number, the user is prompted in aPopup to enter acorrection number, when the transport function is called. On return, this field contains the last position of the cursor inthe table EXTRACT (important for user processing). On return from the function module, the parameter UCOMM contains thelast user maintenance command. The following commands must be handledby the calling program: SAVE --> write the data in the database ORGL --> reset all marked entries in EXTRACT ORGD --> reset the header entry in EXTRACT ANZG --> change the processing mode: Change -> Display AEND --> change the processing mode: Display/Transport -> Change TRSP --> change the processing mode: Change -> Transport ENDE --> end processing ATAB --> get another view for processing BACK --> return to calling point xxxx --> user-specific code, realised in user modules in thefunction module screens Flag which on return indicates whether data have been changed and musttherefore be saved (flag not equal to SPACE). With the parameter CORR_NUMBER, you can pass a correction number.This correction number is only required in connection with theaction transport (parameter VIEW_ACTION). If you have not passed a correction number, the user is prompted in aPopup to enter acorrection number, when the transport function is called. You pass the code of the desired function to the parameter FCODE. Validcodes are: READ --> read the data from the database EDIT --> edit the data RDED --> read and edit the data SAVE --> write the data in the database ORGL --> reset all marked entries in EXTRACT ORGD --> reset the header entry in EXTRACT With the parameter VIEW_ACTION you determine the processing action to becarried out. Possible actions are: S = Display U = Change T = Transport The table CORR_KEYTAB passes the table entry keys for the currentcorrection (parameter CORR_NUMBER). It has the structure of the tableE071K and is only significant for the transport mode (parameterVIEW_ACTION = 'TRSP'). If the table is passed empty, it is filled in the function module. Onreturn from the function module, the table contains the entries made inthe function module as well as those passed when calling, but not thedeleted entries. So it is possible to read the entries belonging to thecorrection and save in the calling program. The table DBA_SELLIST contains the selection conditions for thedatabase access. The following fields must be filled: Field name Contents NEGATION NOT, if the condition is to be negated SPACE otherwise VIEWFIELD Name of the field for which the condition is to apply OPERATOR logical operator of the condition (e.g. 'EQ','NE',...) VALUE Comparison value of the condition in external format AND_OR AND, if the next line of the condition is to be connected to the current line by a logical AND OR, if the next line of the condition is to be connected to the current line by a logical OR SPACE, if no further line follows DDIC S, if the view field in DD was flagged as a sub-set field (PM = 'S') SPACE otherwise TABIX Index of the view field in the Nametab of the view Notes: Allowed operators are: (see also ABAP doc.) EQ - equals NE - not equal GT - greater than GE - greater than or equal to LT - less than LE - less than or equal to CA - only for strings: contains at least one character of thecomparison string CN - only for strings: negation of CA CO - only for strings: contains only characters from the comparisonstring NA - only for strings: negation of CO CP - only for strings: contains the pattern in the comparison string NP - only for strings: negation of CP CS - only for strings: contains the string in the comparison string NS - only for strings: negation of CS LK - corresponds to the LIKE operator in a SELECT ... WHERE clause The function module does not (yet) check whether the selectionconditions passed here are compatible with any conditions specified inthe view definition in the Data Dictionary. The caller is responsiblefor only specifying conditions which are compatible with the DataDictionary. The table DPL_SELLIST contains the selection conditions for thecreation of a sub-work-area for further processing. The followingfields must be filled: Field name Contents NEGATION NOT, if the condition is to be negated SPACE otherwise VIEWFIELD name of the field for which the condition is to apply OPERATOR logical operator of the condition (e.g. 'EQ','NE',...) VALUE comparison value of the condition in external format AND_OR AND, if the next line of the condition is to be connected to current one with a logical AND OR , if the next line of the condition is to be connected to the current one with a logical OR SPACE, if no further line follows DDIC S, if the view field in DD was flagged as a sub-set field (PM = 'S') SPACE otherwise TABIX Index of the view field in the Nametab of the view Notes: Allowed operators are: (see also ABAP doc.) EQ - equals NE - not equal GT - greater than GE - greater than or equal LT - less than LE - less than or equal CA - only for strings: contains at least one character of thecomparison string CN - only for strings: negation of CA CO - only for strings: only contains characters from the comparisonstring NA - only for strings: negation of CO CP - only for strings: contains the pattern in the comparison string NP - only for strings: negation of CP CS - only for strings: contains the string contained in the comparisonstring NS - only for strings: negation of CS LK - corresponds to the LIKE operator in a SELECT ... WHERE clause The function module does not (yet) check whether the selectionconditions passed here are compatible with any conditions specified inthe view definition in the Data Dictionary. The caller is responsiblefor only passing conditions which are compatible with the DataDictionary. Table with user interface functions which are to be de-activateddynamically. This is useful e.g. for the following functions, which cannot be handled unambiguously in cluster maintenance: ANZG --> Change processing mode: Change -> Display is meaningless in a maintenance cluster AEND --> Change processing mode: Display -> Change is meaningless in a display cluster xxxx --> other user-specified functions. The table must have the structure VIMEXCLFUN, which is as follows:
contains the function codes which are to be dynamically de-activated Auxiliary field for the on-line help (not yet supported) Display work table (sub-work-area). On returnthe table contains the display data of the last selection (e.g.marked records or selection by contents, etc.). Table for all data (work area) |