SAP J_1S_STRPRO_UPDATE Function Module for IS-M/SD CH: Update Postal Unit Street for Table J_1SSTRPRO
J_1S_STRPRO_UPDATE is a standard j 1s strpro update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/SD CH: Update Postal Unit Street for Table J_1SSTRPRO 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 j 1s strpro update FM, simply by entering the name J_1S_STRPRO_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: J1S0
Program Name: SAPLJ1S0
Main Program: SAPLJ1S0
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_1S_STRPRO_UPDATE 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 'J_1S_STRPRO_UPDATE'"IS-M/SD CH: Update Postal Unit Street for Table J_1SSTRPRO.
EXPORTING
*CHSTRPRO = "
CHSTRPRO = "
EXCEPTIONS
NO_UPDATE = 1
IMPORTING Parameters details for J_1S_STRPRO_UPDATE
*CHSTRPRO -
Data type: J_1SSTRPROOptional: No
Call by Reference: No ( called with pass by value option)
CHSTRPRO -
Data type: J_1SSTRPROOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_UPDATE - Unsuccessful
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for J_1S_STRPRO_UPDATE 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_*chstrpro | TYPE J_1SSTRPRO, " | |||
| lv_no_update | TYPE J_1SSTRPRO, " | |||
| lv_chstrpro | TYPE J_1SSTRPRO. " |
|   CALL FUNCTION 'J_1S_STRPRO_UPDATE' "IS-M/SD CH: Update Postal Unit Street for Table J_1SSTRPRO |
| EXPORTING | ||
| CHSTRPRO | = lv_ chstrpro | |
| CHSTRPRO | = lv_chstrpro | |
| EXCEPTIONS | ||
| NO_UPDATE = 1 | ||
| . " J_1S_STRPRO_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM J_1S_STRPRO_UPDATE
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