SAP ISU_S_PERCEPTION_LINES_CREATE Function Module for Create Perception Document









ISU_S_PERCEPTION_LINES_CREATE is a standard isu s perception lines create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Perception Document processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for isu s perception lines create FM, simply by entering the name ISU_S_PERCEPTION_LINES_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: EARG
Program Name: SAPLEARG
Main Program: SAPLEARG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISU_S_PERCEPTION_LINES_CREATE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'ISU_S_PERCEPTION_LINES_CREATE'"Create Perception Document
  EXPORTING
*  I_DO_ARGENTINA_CHECK = 'X' "
*  I_CREATE_SEP_DOC = ' ' "
*  I_HERKF =  "Document Source Key
*  I_TAXES_INCLUDED = ' ' "
*  I_ACTVT = '01' "Activity

 IMPORTING
   E_PERC_FKKKO =  "Header Data in Contract Accounting Document
   E_PERC_BETRW =  "

TABLES
   T_FKKOPK =  "G/L Account Items in Open Item Account Document
   T_FKKOP =  "Business Partner Items in Contract Account Document
*  T_PERC_FKKOP =  "Business Partner Items in Contract Account Document
*  T_PERC_FKKOPK =  "G/L Account Items in Open Item Account Document
.



IMPORTING Parameters details for ISU_S_PERCEPTION_LINES_CREATE

I_DO_ARGENTINA_CHECK -

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_CREATE_SEP_DOC -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_HERKF - Document Source Key

Data type: FKKKO-HERKF
Optional: Yes
Call by Reference: Yes

I_TAXES_INCLUDED -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ACTVT - Activity

Data type: TACT-ACTVT
Default: '01'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISU_S_PERCEPTION_LINES_CREATE

E_PERC_FKKKO - Header Data in Contract Accounting Document

Data type: FKKKO
Optional: No
Call by Reference: No ( called with pass by value option)

E_PERC_BETRW -

Data type: FKKOP-BETRW
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ISU_S_PERCEPTION_LINES_CREATE

T_FKKOPK - G/L Account Items in Open Item Account Document

Data type: FKKOPK
Optional: No
Call by Reference: Yes

T_FKKOP - Business Partner Items in Contract Account Document

Data type: FKKOP
Optional: No
Call by Reference: Yes

T_PERC_FKKOP - Business Partner Items in Contract Account Document

Data type: FKKOP
Optional: Yes
Call by Reference: Yes

T_PERC_FKKOPK - G/L Account Items in Open Item Account Document

Data type: FKKOPK
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for ISU_S_PERCEPTION_LINES_CREATE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lt_t_fkkopk  TYPE STANDARD TABLE OF FKKOPK, "   
lv_e_perc_fkkko  TYPE FKKKO, "   
lv_i_do_argentina_check  TYPE BOOLE-BOOLE, "   'X'
lt_t_fkkop  TYPE STANDARD TABLE OF FKKOP, "   
lv_e_perc_betrw  TYPE FKKOP-BETRW, "   
lv_i_create_sep_doc  TYPE BOOLE-BOOLE, "   SPACE
lv_i_herkf  TYPE FKKKO-HERKF, "   
lt_t_perc_fkkop  TYPE STANDARD TABLE OF FKKOP, "   
lt_t_perc_fkkopk  TYPE STANDARD TABLE OF FKKOPK, "   
lv_i_taxes_included  TYPE BOOLE-BOOLE, "   SPACE
lv_i_actvt  TYPE TACT-ACTVT. "   '01'

  CALL FUNCTION 'ISU_S_PERCEPTION_LINES_CREATE'  "Create Perception Document
    EXPORTING
         I_DO_ARGENTINA_CHECK = lv_i_do_argentina_check
         I_CREATE_SEP_DOC = lv_i_create_sep_doc
         I_HERKF = lv_i_herkf
         I_TAXES_INCLUDED = lv_i_taxes_included
         I_ACTVT = lv_i_actvt
    IMPORTING
         E_PERC_FKKKO = lv_e_perc_fkkko
         E_PERC_BETRW = lv_e_perc_betrw
    TABLES
         T_FKKOPK = lt_t_fkkopk
         T_FKKOP = lt_t_fkkop
         T_PERC_FKKOP = lt_t_perc_fkkop
         T_PERC_FKKOPK = lt_t_perc_fkkopk
. " ISU_S_PERCEPTION_LINES_CREATE




ABAP code using 7.40 inline data declarations to call FM ISU_S_PERCEPTION_LINES_CREATE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_do_argentina_check).
DATA(ld_i_do_argentina_check) = 'X'.
 
 
"SELECT single BETRW FROM FKKOP INTO @DATA(ld_e_perc_betrw).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_create_sep_doc).
DATA(ld_i_create_sep_doc) = ' '.
 
"SELECT single HERKF FROM FKKKO INTO @DATA(ld_i_herkf).
 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_taxes_included).
DATA(ld_i_taxes_included) = ' '.
 
"SELECT single ACTVT FROM TACT INTO @DATA(ld_i_actvt).
DATA(ld_i_actvt) = '01'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!