SAP Function Modules

VALIDATE_OPERATOR SAP Function module - Joint Venture Validate Operator







VALIDATE_OPERATOR is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name VALIDATE_OPERATOR into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: GJVV
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM VALIDATE_OPERATOR - VALIDATE OPERATOR





CALL FUNCTION 'VALIDATE_OPERATOR' "Joint Venture Validate Operator
  EXPORTING
    i_company =                 " lfb1-bukrs    Company Code
    i_operator =                " lfb1-lifnr    Operator
  IMPORTING
    e_record =                  " lfb1          Export : Field String - Structure LFB1
    e_valid =                   "               Export : Valid Flag - 1 = Valid, 0 = Invalid
  EXCEPTIONS
    INCOMPLETE = 1              "               Input Parameters Invalid or Incomplete
    .  "  VALIDATE_OPERATOR

ABAP code example for Function Module VALIDATE_OPERATOR





The ABAP code below is a full code listing to execute function module VALIDATE_OPERATOR including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA:
ld_e_record  TYPE LFB1 ,
ld_e_valid  TYPE STRING .


SELECT single BUKRS
FROM LFB1
INTO @DATA(ld_i_company).


SELECT single LIFNR
FROM LFB1
INTO @DATA(ld_i_operator).
. CALL FUNCTION 'VALIDATE_OPERATOR' EXPORTING i_company = ld_i_company i_operator = ld_i_operator IMPORTING e_record = ld_e_record e_valid = ld_e_valid EXCEPTIONS INCOMPLETE = 1 . " VALIDATE_OPERATOR
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_e_record  TYPE LFB1 ,
ld_i_company  TYPE LFB1-BUKRS ,
ld_e_valid  TYPE STRING ,
ld_i_operator  TYPE LFB1-LIFNR .


SELECT single BUKRS
FROM LFB1
INTO ld_i_company.


SELECT single LIFNR
FROM LFB1
INTO ld_i_operator.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name VALIDATE_OPERATOR or its description.