DYNP_VALUES_READ - Read screen field values before PAI field transport

General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book
Preliminary comment

This function module has been released.

The documentation is being revised so that it conforms to the requirements for released function modules.

Function module: DYNP_VALUES_READ

Purpose: Read field contents on screen and transport field to help
processor

Function group: SHL2 - Help functions

Release: released for customers

Documentation

Functionality

This function module reads screen field contents that are to

be processed by the help modules.

Example:

data: dyname like d020s-prog value 'TESTPROG',
dynumb like d020s-dnum value '100'.
data: begin of dynpfields occurs 3.
include structure dynpread.
data: end of dynpfields.
move 'TABNAME' to dynpfields-fieldname.
append dynpfields.
move 'FIELDNAME' to dynpfields-fieldname.
append dynpfields.
call function 'DYNP_VALUES_READ'
exporting
dyname = dymame
dynumb = dynumb
translate_to_upper = 'X'
tables
dynpfields = dynpfields
exceptions
invalid_abapworkarea = 01
invalid_dynprofield = 02
invalid_dynproname = 03
invalid_dynpronummer = 04
invalid_request = 05
no_fielddescription = 06
undefind_error = 07.

Notes:

The field contents read into DYNPFIELDS are being used by the following function modules for the external Help
HELP_VALUES_GET_WITH_TABLE_EXT and
HELP_VALUES_GET_WITH_DD_NAME (also ..NO_DD_NAME). The values are returned via
DYNP_VALUES_UPDATE.

The field names in DYNPFIELDS can be user-defined as in the above example, where fields TABNAME and FIELDNAME occur on the screen. A Data Dictonary reference of these fields (... like ...) is not affected.

All exceptions are caused by the C function HELP_GET_FIELDS.

To retain the current line in step loops, you must call function module DYNP_GET_STEPL before calling DYNP_VALUES_READ.

Description of parameters

Parameter Reference field/structure Default value

Import parameter
DYNAME D020S-PROG
DYNUMB D020S-DNUM
TRANSLATE_TO_UPPER SPACE

Table parameter
DYNPFIELDS DYNPREAD

Exceptions:
INVALID_ABAPWORKAREA
INVALID_DYNPROFIELD
INVALID_DYNPRONAME
INVALID_DYNPRONUMMER
INVALID_REQUEST
NO_FIELDDESCRIPTION
UNDEFINED_ERROR

  • Import parameter:
  • DYNAME: Name of program (of calling screen)
    Meaning: Name of program from which the function module is
    called. Do not set any SY-fields, because these
    are filled dynamically during the call of function
    modules.
    Value set: None
    Preallocation: None

  • DYNUMB: Number of calling screen
    Meaning: Number of screen from which the function module is
    called. Do not set SY-DYNNR.
    sy-dynnr gesetzt werden.
    Value set: None
    Preallocation: None

  • TRANSLATE_TO_UPPER: For conversion to upper case
    Meaning: If set, then the field contents read will be
    converted to upper case letters, even if lower case
    id defined for the domain in the Data Dictionary.
    If not set, then the field contents will be treated
    according to the definition of the domain in the
    Data Dictionary.

  • Table parameter:
  • DYNPFIELDS: Table to read the current screen values.
    Meaning: Before the call of the function module, the table
    contains the name of the screen fields to be read.
    After the call, it also contains the values read
    and the step loop lines, if it is a step loop
    screen.

  • Exceptions:
  • INVALID_ABAPWORKAREA: No work area
    Meaning: No valid ABAP/4 work area exists.

  • INVALID_DYNPROFIELD: No valid screen field
    Meaning: The specified field does not exist on the screen.

  • INVALID_DYNPRONAME: No valid screen name.
    Meaning: The specified program does not exist.

  • INVALID_DYNPRONUMMER: No valid screen number
    Meaning: The specified screen does not exist or has
    not been generated.

  • INVALID_REQUEST: General request error
    Meaning: An error occurred during the system function call to
    read the screen.

  • NO_FIELDDESCRIPTION: No field description exists
    Meaning: There is no description for the specified screen
    field.

  • UNDEFINED_ERROR: Undefined error
    Meaning: An unknown error occurred during the system function
    call.





Parameters

DETERMINE_LOOP_INDEX
DYNAME
DYNPFIELDS
DYNUMB
PERFORM_CONVERSION_EXITS
PERFORM_INPUT_CONVERSION
REQUEST
SEARCHPATH_OF_SUBSCREEN_AREAS
SEARCH_OWN_SUBSCREENS_FIRST
START_SEARCH_IN_CURRENT_SCREEN
START_SEARCH_IN_MAIN_SCREEN
START_SEARCH_IN_STACKED_SCREEN
START_SEARCH_ON_SCR_STACKPOS
TRANSLATE_TO_UPPER

Exceptions

DOUBLE_CONVERSION
INVALID_ABAPWORKAREA
INVALID_DYNPROFIELD
INVALID_DYNPRONAME
INVALID_DYNPRONUMMER
INVALID_PARAMETER
INVALID_REQUEST
NO_FIELDDESCRIPTION
STEPL_NOT_FOUND
UNDEFIND_ERROR

Function Group

SHL2

Fill RESBD Structure from EBP Component Structure   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.


Length: 10449 Date: 20140728 Time: 061212     sap01-206 ( 43 ms )

consolut Transport Check

The consolut Transport Check is a simple and reliable tool that helps you identify dependencies between transport orders.

consolut Transport Check