SAP ISM_PD_CONS_VALIDATE Function Module for Validate CONS Postal Data









ISM_PD_CONS_VALIDATE is a standard ism pd cons validate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Validate CONS Postal Data 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 ism pd cons validate FM, simply by entering the name ISM_PD_CONS_VALIDATE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_PD_CONS_VALIDATE 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 'ISM_PD_CONS_VALIDATE'"Validate CONS Postal Data
  EXPORTING
   PD_COUNTRY =  "Country Key
*  X_CHECK_PRECOND_DISS = 'X' "Checkbox Field
   PD_POST_VERSION_ID =  "
*  COMMIT_CNT = 1000 "Commit Counter
*  GROUP_ID =  "Logon/Server Group Name
*  NOCT = 1 "
*  CHECK_VALID_FROM = SY-DATUM "Valid From Date
*  CHECK_VALID_TO = '99991231' "Valid to Date
   X_REGARD_MAN_OBJ =  "
*  X_CHECK_PRECOND_RAW = 'X' "Checkbox Field

 IMPORTING
   CNT_TASK =  "
   MESSAGE =  "IS-M: Message Data
   LT_OBJ_MESSAGES =  "
.



IMPORTING Parameters details for ISM_PD_CONS_VALIDATE

PD_COUNTRY - Country Key

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

X_CHECK_PRECOND_DISS - Checkbox Field

Data type: XFELD
Default: 'X'
Optional: No
Call by Reference: Yes

PD_POST_VERSION_ID -

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

COMMIT_CNT - Commit Counter

Data type: I
Default: 1000
Optional: No
Call by Reference: Yes

GROUP_ID - Logon/Server Group Name

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

NOCT -

Data type: I
Default: 1
Optional: No
Call by Reference: Yes

CHECK_VALID_FROM - Valid From Date

Data type: GUELTIGVON
Default: SY-DATUM
Optional: No
Call by Reference: Yes

CHECK_VALID_TO - Valid to Date

Data type: GUELTIGBIS
Default: '99991231'
Optional: No
Call by Reference: Yes

X_REGARD_MAN_OBJ -

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

X_CHECK_PRECOND_RAW - Checkbox Field

Data type: XFELD
Default: 'X'
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for ISM_PD_CONS_VALIDATE

CNT_TASK -

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

MESSAGE - IS-M: Message Data

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

LT_OBJ_MESSAGES -

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

Copy and paste ABAP code example for ISM_PD_CONS_VALIDATE 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:
lv_cnt_task  TYPE I, "   
lv_pd_country  TYPE LAND1, "   
lv_x_check_precond_diss  TYPE XFELD, "   'X'
lv_message  TYPE RJMSG, "   
lv_pd_post_version_id  TYPE STRING, "   
lv_commit_cnt  TYPE I, "   1000
lv_lt_obj_messages  TYPE RJMSG_TAB, "   
lv_group_id  TYPE RZLLI_APCL, "   
lv_noct  TYPE I, "   1
lv_check_valid_from  TYPE GUELTIGVON, "   SY-DATUM
lv_check_valid_to  TYPE GUELTIGBIS, "   '99991231'
lv_x_regard_man_obj  TYPE XFELD, "   
lv_x_check_precond_raw  TYPE XFELD. "   'X'

  CALL FUNCTION 'ISM_PD_CONS_VALIDATE'  "Validate CONS Postal Data
    EXPORTING
         PD_COUNTRY = lv_pd_country
         X_CHECK_PRECOND_DISS = lv_x_check_precond_diss
         PD_POST_VERSION_ID = lv_pd_post_version_id
         COMMIT_CNT = lv_commit_cnt
         GROUP_ID = lv_group_id
         NOCT = lv_noct
         CHECK_VALID_FROM = lv_check_valid_from
         CHECK_VALID_TO = lv_check_valid_to
         X_REGARD_MAN_OBJ = lv_x_regard_man_obj
         X_CHECK_PRECOND_RAW = lv_x_check_precond_raw
    IMPORTING
         CNT_TASK = lv_cnt_task
         MESSAGE = lv_message
         LT_OBJ_MESSAGES = lv_lt_obj_messages
. " ISM_PD_CONS_VALIDATE




ABAP code using 7.40 inline data declarations to call FM ISM_PD_CONS_VALIDATE

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.

 
 
DATA(ld_x_check_precond_diss) = 'X'.
 
 
 
DATA(ld_commit_cnt) = 1000.
 
 
 
DATA(ld_noct) = 1.
 
DATA(ld_check_valid_from) = SY-DATUM.
 
DATA(ld_check_valid_to) = '99991231'.
 
 
DATA(ld_x_check_precond_raw) = 'X'.
 


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!