SAP ISP_POSTCODE_TEXT_READ Function Module for

Search SAP Function Modules

ISP_POSTCODE_TEXT_READ is a standard isp postcode text read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 isp postcode text read FM, simply by entering the name ISP_POSTCODE_TEXT_READ into the relevant SAP transaction such as SE37 or SE38.

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

Function ISP_POSTCODE_TEXT_READ 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 'ISP_POSTCODE_TEXT_READ'"
  EXPORTING
*  BFS =  "
*  BUNDFERTART =  "
*  FERTART =  "
   LAND =  "
   PLZ =  "
*  DRERZ =  "
*  PVA =  "
*  LFARTLOG =  "
*  VERSANDDATUM =  "
*  NETZ =  "
*  WERK =  "

 IMPORTING
   PLZ_BEZ =  "
   AMTNR =  "

EXCEPTIONS
   WRONG_INPUT = 1 

.

IMPORTING Parameters details for ISP_POSTCODE_TEXT_READ

BFS -

Data type: JVTBUND-BFS
Optional: Yes
Call by Reference: No ( called with pass by value option)

BUNDFERTART -

Data type: JVTFRGLART-BUNDRGLART
Optional: Yes
Call by Reference: No ( called with pass by value option)

FERTART -

Data type: TJV70-ART_FERTIG
Optional: Yes
Call by Reference: No ( called with pass by value option)

LAND -

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

PLZ -

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

DRERZ -

Data type: JRTABLG-DRERZTAT
Optional: Yes
Call by Reference: No ( called with pass by value option)

PVA -

Data type: JRTABLG-PVATAT
Optional: Yes
Call by Reference: No ( called with pass by value option)

LFARTLOG -

Data type: JRTABLG-LFARTLOG
Optional: Yes
Call by Reference: No ( called with pass by value option)

VERSANDDATUM -

Data type: JRTABLG-VERSANDDAT
Optional: Yes
Call by Reference: No ( called with pass by value option)

NETZ -

Data type: JRTABLG-NETZ
Optional: Yes
Call by Reference: No ( called with pass by value option)

WERK -

Data type: JRTABLG-DRUCKEREI
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISP_POSTCODE_TEXT_READ

PLZ_BEZ -

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

AMTNR -

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

EXCEPTIONS details

WRONG_INPUT -

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

Copy and paste ABAP code example for ISP_POSTCODE_TEXT_READ 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.

ABAP code using 7.40 inline data declarations to call FM ISP_POSTCODE_TEXT_READ

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.

Search for further information about these or an SAP related objects