SAP Function Modules

comments icon Comments

NL_CREATE_TOKEN_FILE SAP Function module







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

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


Pattern for FM NL_CREATE_TOKEN_FILE - NL CREATE TOKEN FILE 





CALL FUNCTION 'NL_CREATE_TOKEN_FILE' "
  EXPORTING
    i_senderid =                " c
    i_atag =                    " rfpdo1-fordatag
    i_dtyp =                    " rfpdo-forddtyp
    i_filename =                " c
    i_text =                    " c
*   i_trtype =                  " n
*   i_path =                    " rfpdo2-fordnamd
  IMPORTING
    i_tokenfilnam =             " c
    i_renum =                   " regut-renum
    i_name =                    " c
  TABLES
    i_reguh =                   " reguh
    i_regut =                   " regut
    .  "  NL_CREATE_TOKEN_FILE

ABAP code example for Function Module NL_CREATE_TOKEN_FILE





The ABAP code below is a full code listing to execute function module NL_CREATE_TOKEN_FILE 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_i_tokenfilnam    TYPE C
,
ld_i_renum    TYPE REGUT-RENUM
,
ld_i_name    TYPE C
,
it_i_reguh    TYPE STANDARD TABLE OF REGUH,"TABLES PARAM
wa_i_reguh  LIKE LINE OF it_i_reguh
,
it_i_regut    TYPE STANDARD TABLE OF REGUT,"TABLES PARAM
wa_i_regut  LIKE LINE OF it_i_regut
.




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


DATA(ld_i_atag) = Check type of data required


DATA(ld_i_dtyp) = some text here

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

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

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


DATA(ld_i_path) = some text here
 

"populate fields of struture and append to itab
append wa_i_reguh to it_i_reguh.
 

"populate fields of struture and append to itab
append wa_i_regut to it_i_regut.
.

CALL FUNCTION 'NL_CREATE_TOKEN_FILE'
  EXPORTING
    i_senderid =                 ld_i_senderid
    i_atag =                     ld_i_atag
    i_dtyp =                     ld_i_dtyp
    i_filename =                 ld_i_filename
    i_text =                     ld_i_text
*   i_trtype =                   ld_i_trtype
*   i_path =                     ld_i_path
  IMPORTING
    i_tokenfilnam =              ld_i_tokenfilnam
    i_renum =                    ld_i_renum
    i_name =                     ld_i_name
  TABLES
    i_reguh =                    it_i_reguh
    i_regut =                    it_i_regut
    .  "  NL_CREATE_TOKEN_FILE

IF SY-SUBRC EQ 0.
  "All OK
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_i_tokenfilnam  TYPE C ,
ld_i_senderid  TYPE C ,
it_i_reguh  TYPE STANDARD TABLE OF REGUH ,
wa_i_reguh  LIKE LINE OF it_i_reguh,
ld_i_renum  TYPE REGUT-RENUM ,
ld_i_atag  TYPE RFPDO1-FORDATAG ,
it_i_regut  TYPE STANDARD TABLE OF REGUT ,
wa_i_regut  LIKE LINE OF it_i_regut,
ld_i_name  TYPE C ,
ld_i_dtyp  TYPE RFPDO-FORDDTYP ,
ld_i_filename  TYPE C ,
ld_i_text  TYPE C ,
ld_i_trtype  TYPE N ,
ld_i_path  TYPE RFPDO2-FORDNAMD .




ld_i_senderid = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_i_reguh to it_i_reguh.

ld_i_atag = Check type of data required 

"populate fields of struture and append to itab
append wa_i_regut to it_i_regut.

ld_i_dtyp = some text here
ld_i_filename = 'Check type of data required'.
ld_i_text = 'Check type of data required'.
ld_i_trtype = 'Check type of data required'.

ld_i_path = some text here

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 NL_CREATE_TOKEN_FILE or its description.


   
 

NL_CREATE_TOKEN_FILE - 
NLS_WORD_ENABLE - Should MSWORD be enabled
NLS_WORD_CF_HIDEDINFO - Flag to send char formats as hided info from ITF->MS Word
NLS_VISUAL_CHARLEN - Visual length of the 1st char in string
NLS_THAI_CHARLEN - 
NLS_TCP0C_PLATFORM_CONS_CHECK - TCP0C entries consistency check