SAP ISP_TRANSFERRED_PARTNER_SAVE Function Module for IS-M/SD: Save Business Partner (Subscriber) During Data Transfer
ISP_TRANSFERRED_PARTNER_SAVE is a standard isp transferred partner save 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: Save Business Partner (Subscriber) During Data Transfer 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 isp transferred partner save FM, simply by entering the name ISP_TRANSFERRED_PARTNER_SAVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: JG40
Program Name: SAPLJG40
Main Program: SAPLJG40
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISP_TRANSFERRED_PARTNER_SAVE 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_TRANSFERRED_PARTNER_SAVE'"IS-M/SD: Save Business Partner (Subscriber) During Data Transfer.
EXPORTING
IJGTADRA = "
KNA1_ANLEGEN = "
KNB1_ANLEGEN = "
KNVI_ANLEGEN = "
KNVK_ANLEGEN = "
KNVV_ANLEGEN = "
GP_SATZART = "
JPARVW = "
IABLAUF = "
KNVD_ANLEGEN = "
IJGTGPNR = "
IJGTSADR = "
IKNA1 = "
IKNB1 = "
IKNB5 = "
IKNVK = "
IKNVV = "
JGT_ANLEGEN = "
IMPORTING
OJGTGPNR = "
TABLES
TJGTADRA_H = "
TKNVI = "
TKNVP = "
TKNBK = "
TVCNUM = "
TVCKUN = "
TJGTBKVW = "
TJGTBKEZ = "
TKNVD = "
EXCEPTIONS
NO_ABLAUF = 1
IMPORTING Parameters details for ISP_TRANSFERRED_PARTNER_SAVE
IJGTADRA -
Data type: JGTADRAOptional: No
Call by Reference: No ( called with pass by value option)
KNA1_ANLEGEN -
Data type: JGTGPNR-XGPSPEOptional: No
Call by Reference: No ( called with pass by value option)
KNB1_ANLEGEN -
Data type: JGTGPNR-XGPSPEOptional: No
Call by Reference: No ( called with pass by value option)
KNVI_ANLEGEN -
Data type: JGTGPNR-XGPSPEOptional: No
Call by Reference: No ( called with pass by value option)
KNVK_ANLEGEN -
Data type: JGTGPNR-XGPSPEOptional: No
Call by Reference: No ( called with pass by value option)
KNVV_ANLEGEN -
Data type: JGTGPNR-XGPSPEOptional: No
Call by Reference: No ( called with pass by value option)
GP_SATZART -
Data type: RJGAU-GP_SATZARTOptional: No
Call by Reference: No ( called with pass by value option)
JPARVW -
Data type: RJGAU-JPARVWOptional: No
Call by Reference: No ( called with pass by value option)
IABLAUF -
Data type: JGD00_ABLAUFOptional: No
Call by Reference: No ( called with pass by value option)
KNVD_ANLEGEN -
Data type: JGTGPNR-XGPSPEOptional: No
Call by Reference: No ( called with pass by value option)
IJGTGPNR -
Data type: JGTGPNROptional: No
Call by Reference: No ( called with pass by value option)
IJGTSADR -
Data type: JGTSADROptional: No
Call by Reference: No ( called with pass by value option)
IKNA1 -
Data type: KNA1Optional: No
Call by Reference: No ( called with pass by value option)
IKNB1 -
Data type: KNB1Optional: No
Call by Reference: No ( called with pass by value option)
IKNB5 -
Data type: KNB5Optional: No
Call by Reference: No ( called with pass by value option)
IKNVK -
Data type: KNVKOptional: No
Call by Reference: No ( called with pass by value option)
IKNVV -
Data type: KNVVOptional: No
Call by Reference: No ( called with pass by value option)
JGT_ANLEGEN -
Data type: JGTGPNR-XGPSPEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISP_TRANSFERRED_PARTNER_SAVE
OJGTGPNR -
Data type: JGTGPNROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISP_TRANSFERRED_PARTNER_SAVE
TJGTADRA_H -
Data type: JGTADRAOptional: No
Call by Reference: No ( called with pass by value option)
TKNVI -
Data type: KNVIOptional: No
Call by Reference: No ( called with pass by value option)
TKNVP -
Data type: KNVPOptional: No
Call by Reference: No ( called with pass by value option)
TKNBK -
Data type: KNBKOptional: No
Call by Reference: No ( called with pass by value option)
TVCNUM -
Data type: VCNUMOptional: No
Call by Reference: No ( called with pass by value option)
TVCKUN -
Data type: VCKUNOptional: No
Call by Reference: No ( called with pass by value option)
TJGTBKVW -
Data type: JGTBKVWOptional: No
Call by Reference: No ( called with pass by value option)
TJGTBKEZ -
Data type: JGTBKEZOptional: No
Call by Reference: No ( called with pass by value option)
TKNVD -
Data type: KNVDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_ABLAUF -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_TRANSFERRED_PARTNER_SAVE 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_ijgtadra | TYPE JGTADRA, " | |||
| lv_ojgtgpnr | TYPE JGTGPNR, " | |||
| lv_no_ablauf | TYPE JGTGPNR, " | |||
| lt_tjgtadra_h | TYPE STANDARD TABLE OF JGTADRA, " | |||
| lv_kna1_anlegen | TYPE JGTGPNR-XGPSPE, " | |||
| lv_knb1_anlegen | TYPE JGTGPNR-XGPSPE, " | |||
| lv_knvi_anlegen | TYPE JGTGPNR-XGPSPE, " | |||
| lv_knvk_anlegen | TYPE JGTGPNR-XGPSPE, " | |||
| lv_knvv_anlegen | TYPE JGTGPNR-XGPSPE, " | |||
| lv_gp_satzart | TYPE RJGAU-GP_SATZART, " | |||
| lv_jparvw | TYPE RJGAU-JPARVW, " | |||
| lv_iablauf | TYPE JGD00_ABLAUF, " | |||
| lv_knvd_anlegen | TYPE JGTGPNR-XGPSPE, " | |||
| lt_tknvi | TYPE STANDARD TABLE OF KNVI, " | |||
| lv_ijgtgpnr | TYPE JGTGPNR, " | |||
| lt_tknvp | TYPE STANDARD TABLE OF KNVP, " | |||
| lv_ijgtsadr | TYPE JGTSADR, " | |||
| lv_ikna1 | TYPE KNA1, " | |||
| lt_tknbk | TYPE STANDARD TABLE OF KNBK, " | |||
| lv_iknb1 | TYPE KNB1, " | |||
| lt_tvcnum | TYPE STANDARD TABLE OF VCNUM, " | |||
| lv_iknb5 | TYPE KNB5, " | |||
| lt_tvckun | TYPE STANDARD TABLE OF VCKUN, " | |||
| lv_iknvk | TYPE KNVK, " | |||
| lt_tjgtbkvw | TYPE STANDARD TABLE OF JGTBKVW, " | |||
| lv_iknvv | TYPE KNVV, " | |||
| lt_tjgtbkez | TYPE STANDARD TABLE OF JGTBKEZ, " | |||
| lt_tknvd | TYPE STANDARD TABLE OF KNVD, " | |||
| lv_jgt_anlegen | TYPE JGTGPNR-XGPSPE. " |
|   CALL FUNCTION 'ISP_TRANSFERRED_PARTNER_SAVE' "IS-M/SD: Save Business Partner (Subscriber) During Data Transfer |
| EXPORTING | ||
| IJGTADRA | = lv_ijgtadra | |
| KNA1_ANLEGEN | = lv_kna1_anlegen | |
| KNB1_ANLEGEN | = lv_knb1_anlegen | |
| KNVI_ANLEGEN | = lv_knvi_anlegen | |
| KNVK_ANLEGEN | = lv_knvk_anlegen | |
| KNVV_ANLEGEN | = lv_knvv_anlegen | |
| GP_SATZART | = lv_gp_satzart | |
| JPARVW | = lv_jparvw | |
| IABLAUF | = lv_iablauf | |
| KNVD_ANLEGEN | = lv_knvd_anlegen | |
| IJGTGPNR | = lv_ijgtgpnr | |
| IJGTSADR | = lv_ijgtsadr | |
| IKNA1 | = lv_ikna1 | |
| IKNB1 | = lv_iknb1 | |
| IKNB5 | = lv_iknb5 | |
| IKNVK | = lv_iknvk | |
| IKNVV | = lv_iknvv | |
| JGT_ANLEGEN | = lv_jgt_anlegen | |
| IMPORTING | ||
| OJGTGPNR | = lv_ojgtgpnr | |
| TABLES | ||
| TJGTADRA_H | = lt_tjgtadra_h | |
| TKNVI | = lt_tknvi | |
| TKNVP | = lt_tknvp | |
| TKNBK | = lt_tknbk | |
| TVCNUM | = lt_tvcnum | |
| TVCKUN | = lt_tvckun | |
| TJGTBKVW | = lt_tjgtbkvw | |
| TJGTBKEZ | = lt_tjgtbkez | |
| TKNVD | = lt_tknvd | |
| EXCEPTIONS | ||
| NO_ABLAUF = 1 | ||
| . " ISP_TRANSFERRED_PARTNER_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM ISP_TRANSFERRED_PARTNER_SAVE
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 XGPSPE FROM JGTGPNR INTO @DATA(ld_kna1_anlegen). | ||||
| "SELECT single XGPSPE FROM JGTGPNR INTO @DATA(ld_knb1_anlegen). | ||||
| "SELECT single XGPSPE FROM JGTGPNR INTO @DATA(ld_knvi_anlegen). | ||||
| "SELECT single XGPSPE FROM JGTGPNR INTO @DATA(ld_knvk_anlegen). | ||||
| "SELECT single XGPSPE FROM JGTGPNR INTO @DATA(ld_knvv_anlegen). | ||||
| "SELECT single GP_SATZART FROM RJGAU INTO @DATA(ld_gp_satzart). | ||||
| "SELECT single JPARVW FROM RJGAU INTO @DATA(ld_jparvw). | ||||
| "SELECT single XGPSPE FROM JGTGPNR INTO @DATA(ld_knvd_anlegen). | ||||
| "SELECT single XGPSPE FROM JGTGPNR INTO @DATA(ld_jgt_anlegen). | ||||
Search for further information about these or an SAP related objects