SAP ISH_N2_DOCPART_COMPLETE_DATA Function Module for

Search SAP Function Modules

ISH_N2_DOCPART_COMPLETE_DATA is a standard ish n2 docpart complete data 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 ish n2 docpart complete data FM, simply by entering the name ISH_N2_DOCPART_COMPLETE_DATA into the relevant SAP transaction such as SE37 or SE38.

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

Function ISH_N2_DOCPART_COMPLETE_DATA 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_N2_DOCPART_COMPLETE_DATA'"
  EXPORTING
   IM_APICONTROL =  "IS-H*MED: Control Options for MedDoc-APIs
   IM_DOC_KEY_SOURCE =  "
*  IM_DOCDATA_PART =  "Doc Management Data for Creating a Document Part

 IMPORTING
   EX_WORST_MSGTY =  "IS-H: Most Severe Message Type Generated
   EX_DOCDATA =  "IS-H*MED: All DocManagement Data - W/O Movement,Svce,Request

TABLES
*  EXT_RETURN =  "Return Parameter(s)

.

IMPORTING Parameters details for ISH_N2_DOCPART_COMPLETE_DATA

IM_APICONTROL - IS-H*MED: Control Options for MedDoc-APIs

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

IM_DOC_KEY_SOURCE -

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

IM_DOCDATA_PART - Doc Management Data for Creating a Document Part

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

EXPORTING Parameters details for ISH_N2_DOCPART_COMPLETE_DATA

EX_WORST_MSGTY - IS-H: Most Severe Message Type Generated

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

EX_DOCDATA - IS-H*MED: All DocManagement Data - W/O Movement,Svce,Request

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

TABLES Parameters details for ISH_N2_DOCPART_COMPLETE_DATA

EXT_RETURN - Return Parameter(s)

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

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

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