SAP ISH_PNT_API_MAP_PARTNER Function Module for IS-H: API Layer to Map IS-H to SAP BP Part. No. for HC Role Patient

Search SAP Function Modules

ISH_PNT_API_MAP_PARTNER is a standard ish pnt api map partner 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-H: API Layer to Map IS-H to SAP BP Part. No. for HC Role Patient 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 ish pnt api map partner FM, simply by entering the name ISH_PNT_API_MAP_PARTNER into the relevant SAP transaction such as SE37 or SE38.

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

Function ISH_PNT_API_MAP_PARTNER 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 'ISH_PNT_API_MAP_PARTNER'"IS-H: API Layer to Map IS-H to SAP BP Part. No. for HC Role Patient
  EXPORTING
*  I_OLD_PARTNER =  "IS-H: Patient Number
*  IT_OLD_PARTNER =  "Table of Business Partner Numbers For NPAT
*  IT_OLD_PARTNER_RNG =  "IS-H: Table Type General Range Structure for Patients
*  I_MAP_IND = '1' "Single-Character Indicator

 IMPORTING
   E_PARTNER =  "Primary Key for NPNT
   ET_PARTNER =  "Table of BP Numbers for Addnl. HC-Specific Data for Patient
   ET_RC =  "IS-H: Table Type for Structure BAPIRET2

.

IMPORTING Parameters details for ISH_PNT_API_MAP_PARTNER

I_OLD_PARTNER - IS-H: Patient Number

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

IT_OLD_PARTNER - Table of Business Partner Numbers For NPAT

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

IT_OLD_PARTNER_RNG - IS-H: Table Type General Range Structure for Patients

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

I_MAP_IND - Single-Character Indicator

Data type: CHAR1
Default: '1'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISH_PNT_API_MAP_PARTNER

E_PARTNER - Primary Key for NPNT

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

ET_PARTNER - Table of BP Numbers for Addnl. HC-Specific Data for Patient

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

ET_RC - IS-H: Table Type for Structure BAPIRET2

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

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

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