UPS_PLSEQNEW_EXECUTE SAP Function module - Copy of the identically named report to the synchronous execution

UPS_PLSEQNEW_EXECUTE 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 UPS_PLSEQNEW_EXECUTE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: UPS_FRAMEWORK
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM UPS_PLSEQNEW_EXECUTE - UPS PLSEQNEW EXECUTE

CALL FUNCTION 'UPS_PLSEQNEW_EXECUTE' "Copy of the identically named report to the synchronous execution
  EXPORTING
    plseqnew =                  " rspls_seqnm   Planning Sequence
    plseqnewvariant =           " rsparamnm     Technical Name of Parameterization
    teilplan =                  " ups_y_teilplan  Subplan in STS
    version =                   " ups_y_version  Planning Session/Version
    orgvl =                     " ups_y_orgvl   Org. Value for Status and Tracking System
  TABLES
    et_return =                 " bapiret2      Return Parameter(s)
  EXCEPTIONS
    ERROR_EXECUTE = 1           "               Error during Execute via API
    .  "  UPS_PLSEQNEW_EXECUTE

ABAP code example for Function Module UPS_PLSEQNEW_EXECUTE

The ABAP code below is a full code listing to execute function module UPS_PLSEQNEW_EXECUTE 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:
it_et_return  
 
 TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM
wa_et_return
 
 LIKE LINE OF it_et_return
.


DATA(ld_plseqnew) = 'Check type of data required'.

DATA(ld_plseqnewvariant) = 'Check type of data required'.

DATA(ld_teilplan) = 'Check type of data required'.

DATA(ld_version) = 'Check type of data required'.

DATA(ld_orgvl) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_et_return to it_et_return.
.

CALL FUNCTION 'UPS_PLSEQNEW_EXECUTE'
  EXPORTING
    plseqnew =                   ld_plseqnew
    plseqnewvariant =            ld_plseqnewvariant
    teilplan =                   ld_teilplan
    version =                    ld_version
    orgvl =                      ld_orgvl
  TABLES
    et_return =                  it_et_return
  EXCEPTIONS
    ERROR_EXECUTE =              1
    .  "  UPS_PLSEQNEW_EXECUTE

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_plseqnew
 
 TYPE RSPLS_SEQNM ,
it_et_return
 
 TYPE STANDARD TABLE OF BAPIRET2 ,
wa_et_return
 
 LIKE LINE OF it_et_return,
ld_plseqnewvariant
 
 TYPE RSPARAMNM ,
ld_teilplan
 
 TYPE UPS_Y_TEILPLAN ,
ld_version
 
 TYPE UPS_Y_VERSION ,
ld_orgvl
 
 TYPE UPS_Y_ORGVL .


ld_plseqnew = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_et_return to it_et_return.
ld_plseqnewvariant = 'Check type of data required'.
ld_teilplan = 'Check type of data required'.
ld_version = 'Check type of data required'.
ld_orgvl = 'Check type of data required'.