K_CODOC_COEJA_FILL SAP Function module

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

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

Pattern for FM K_CODOC_COEJA_FILL - K CODOC COEJA FILL

CALL FUNCTION 'K_CODOC_COEJA_FILL' "
  EXPORTING
    p_item =                    " coeja
*   p_coep_x =                  " coep_x
*   p_posting_possible =        "
*   p_new_bw_item_group =       "
  TABLES
    pt_coiob =                  " coiob
  CHANGING
    p_new_line =                "
  EXCEPTIONS
    NUMBER_ERROR = 1            "
    .  "  K_CODOC_COEJA_FILL

ABAP code example for Function Module K_CODOC_COEJA_FILL

The ABAP code below is a full code listing to execute function module K_CODOC_COEJA_FILL 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_pt_coiob  
 
 TYPE STANDARD TABLE OF COIOB,"TABLES PARAM
wa_pt_coiob
 
 LIKE LINE OF it_pt_coiob
.


DATA(ld_p_new_line) = 'some text here'.

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

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

DATA(ld_p_posting_possible) = 'some text here'.

DATA(ld_p_new_bw_item_group) = 'some text here'.
 

"populate fields of struture and append to itab
append wa_pt_coiob to it_pt_coiob.
.

CALL FUNCTION 'K_CODOC_COEJA_FILL'
  EXPORTING
    p_item =                     ld_p_item
*   p_coep_x =                   ld_p_coep_x
*   p_posting_possible =         ld_p_posting_possible
*   p_new_bw_item_group =        ld_p_new_bw_item_group
  TABLES
    pt_coiob =                   it_pt_coiob
  CHANGING
    p_new_line =                 ld_p_new_line
  EXCEPTIONS
    NUMBER_ERROR =               1
    .  "  K_CODOC_COEJA_FILL

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_p_new_line
 
 TYPE STRING ,
ld_p_item
 
 TYPE COEJA ,
it_pt_coiob
 
 TYPE STANDARD TABLE OF COIOB ,
wa_pt_coiob
 
 LIKE LINE OF it_pt_coiob,
ld_p_coep_x
 
 TYPE COEP_X ,
ld_p_posting_possible
 
 TYPE STRING ,
ld_p_new_bw_item_group
 
 TYPE STRING .


ld_p_new_line = 'some text here'.
ld_p_item = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_pt_coiob to it_pt_coiob.
ld_p_coep_x = 'Check type of data required'.
ld_p_posting_possible = 'some text here'.
ld_p_new_bw_item_group = 'some text here'.