SAP ERPSLS_DOC_FROM_PARTNER_INDEX Function Module for NOTRANSL: Vertriebsbelege über Partnerindex selektieren
ERPSLS_DOC_FROM_PARTNER_INDEX is a standard erpsls doc from partner index SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Vertriebsbelege über Partnerindex selektieren 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 erpsls doc from partner index FM, simply by entering the name ERPSLS_DOC_FROM_PARTNER_INDEX into the relevant SAP transaction such as SE37 or SE38.
Function Group: ERP_SLS_DOC01
Program Name: SAPLERP_SLS_DOC01
Main Program: SAPLERP_SLS_DOC01
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ERPSLS_DOC_FROM_PARTNER_INDEX 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 'ERPSLS_DOC_FROM_PARTNER_INDEX'"NOTRANSL: Vertriebsbelege über Partnerindex selektieren.
EXPORTING
IV_TRVOG = "Transaction Group
* IT_RG_VKGRP = "Range Table: CHAR3
* IT_RG_ERNAM = "Range Table: CHAR12
* IT_RG_KUNNR = "Range Table: CHAR10
* IV_ZPAVW = "Partner Role
* IT_RG_ZPERS = "Range Table: NUMC8
* IT_RG_AUART = "Range Table: CHAR4
* IT_RG_VKORG = "Range Table: CHAR4
* IT_RG_VTWEG = "Range Table: CHAR2
* IT_RG_SPART = "Range Table: CHAR2
* IT_RG_VKBUR = "Range Table: CHAR4
TABLES
ET_VAKPA = "Sales Index: Orders by Partner Function
EXCEPTIONS
EX_NO_DOCTYPE = 1 EX_NO_PARTNER = 2 EX_NO_INDEX = 3
IMPORTING Parameters details for ERPSLS_DOC_FROM_PARTNER_INDEX
IV_TRVOG - Transaction Group
Data type: TRVOGOptional: No
Call by Reference: Yes
IT_RG_VKGRP - Range Table: CHAR3
Data type: TRG_CHAR3Optional: Yes
Call by Reference: Yes
IT_RG_ERNAM - Range Table: CHAR12
Data type: TRG_CHAR12Optional: Yes
Call by Reference: Yes
IT_RG_KUNNR - Range Table: CHAR10
Data type: TRG_CHAR10Optional: Yes
Call by Reference: Yes
IV_ZPAVW - Partner Role
Data type: PARVWOptional: Yes
Call by Reference: Yes
IT_RG_ZPERS - Range Table: NUMC8
Data type: TRG_NUMC8Optional: Yes
Call by Reference: Yes
IT_RG_AUART - Range Table: CHAR4
Data type: TRG_CHAR4Optional: Yes
Call by Reference: Yes
IT_RG_VKORG - Range Table: CHAR4
Data type: TRG_CHAR4Optional: Yes
Call by Reference: Yes
IT_RG_VTWEG - Range Table: CHAR2
Data type: TRG_CHAR2Optional: Yes
Call by Reference: Yes
IT_RG_SPART - Range Table: CHAR2
Data type: TRG_CHAR2Optional: Yes
Call by Reference: Yes
IT_RG_VKBUR - Range Table: CHAR4
Data type: TRG_CHAR4Optional: Yes
Call by Reference: Yes
TABLES Parameters details for ERPSLS_DOC_FROM_PARTNER_INDEX
ET_VAKPA - Sales Index: Orders by Partner Function
Data type: VAKPAOptional: No
Call by Reference: Yes
EXCEPTIONS details
EX_NO_DOCTYPE -
Data type:Optional: No
Call by Reference: Yes
EX_NO_PARTNER -
Data type:Optional: No
Call by Reference: Yes
EX_NO_INDEX -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ERPSLS_DOC_FROM_PARTNER_INDEX 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: | ||||
| lt_et_vakpa | TYPE STANDARD TABLE OF VAKPA, " | |||
| lv_iv_trvog | TYPE TRVOG, " | |||
| lv_ex_no_doctype | TYPE TRVOG, " | |||
| lv_it_rg_vkgrp | TYPE TRG_CHAR3, " | |||
| lv_it_rg_ernam | TYPE TRG_CHAR12, " | |||
| lv_it_rg_kunnr | TYPE TRG_CHAR10, " | |||
| lv_ex_no_partner | TYPE TRG_CHAR10, " | |||
| lv_iv_zpavw | TYPE PARVW, " | |||
| lv_ex_no_index | TYPE PARVW, " | |||
| lv_it_rg_zpers | TYPE TRG_NUMC8, " | |||
| lv_it_rg_auart | TYPE TRG_CHAR4, " | |||
| lv_it_rg_vkorg | TYPE TRG_CHAR4, " | |||
| lv_it_rg_vtweg | TYPE TRG_CHAR2, " | |||
| lv_it_rg_spart | TYPE TRG_CHAR2, " | |||
| lv_it_rg_vkbur | TYPE TRG_CHAR4. " |
|   CALL FUNCTION 'ERPSLS_DOC_FROM_PARTNER_INDEX' "NOTRANSL: Vertriebsbelege über Partnerindex selektieren |
| EXPORTING | ||
| IV_TRVOG | = lv_iv_trvog | |
| IT_RG_VKGRP | = lv_it_rg_vkgrp | |
| IT_RG_ERNAM | = lv_it_rg_ernam | |
| IT_RG_KUNNR | = lv_it_rg_kunnr | |
| IV_ZPAVW | = lv_iv_zpavw | |
| IT_RG_ZPERS | = lv_it_rg_zpers | |
| IT_RG_AUART | = lv_it_rg_auart | |
| IT_RG_VKORG | = lv_it_rg_vkorg | |
| IT_RG_VTWEG | = lv_it_rg_vtweg | |
| IT_RG_SPART | = lv_it_rg_spart | |
| IT_RG_VKBUR | = lv_it_rg_vkbur | |
| TABLES | ||
| ET_VAKPA | = lt_et_vakpa | |
| EXCEPTIONS | ||
| EX_NO_DOCTYPE = 1 | ||
| EX_NO_PARTNER = 2 | ||
| EX_NO_INDEX = 3 | ||
| . " ERPSLS_DOC_FROM_PARTNER_INDEX | ||
ABAP code using 7.40 inline data declarations to call FM ERPSLS_DOC_FROM_PARTNER_INDEX
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