SAP JITOUT06_READ_MULTI_PVBE_1 Function Module for NOTRANSL: Lesen der Produktionsversorgungsbereiche









JITOUT06_READ_MULTI_PVBE_1 is a standard jitout06 read multi pvbe 1 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: Lesen der Produktionsversorgungsbereiche 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 jitout06 read multi pvbe 1 FM, simply by entering the name JITOUT06_READ_MULTI_PVBE_1 into the relevant SAP transaction such as SE37 or SE38.

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



Function JITOUT06_READ_MULTI_PVBE_1 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 'JITOUT06_READ_MULTI_PVBE_1'"NOTRANSL: Lesen der Produktionsversorgungsbereiche
EXPORTING
* WERKS_IT = "Plant
* RGVER_IT = "Table Type for Person Responsible
* LGORT_IT = "Storage Location Range

IMPORTING
PVBE_ET = "Table Type for Production Supply Area

EXCEPTIONS
NO_ENTRY_FOUND = 1
.



IMPORTING Parameters details for JITOUT06_READ_MULTI_PVBE_1

WERKS_IT - Plant

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

RGVER_IT - Table Type for Person Responsible

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

LGORT_IT - Storage Location Range

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

EXPORTING Parameters details for JITOUT06_READ_MULTI_PVBE_1

PVBE_ET - Table Type for Production Supply Area

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

EXCEPTIONS details

NO_ENTRY_FOUND - No Entry Found

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

Copy and paste ABAP code example for JITOUT06_READ_MULTI_PVBE_1 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_pvbe_et  TYPE PVBEX, "   
lv_werks_it  TYPE JITO_WERKS_RANGE_TT, "   
lv_no_entry_found  TYPE JITO_WERKS_RANGE_TT, "   
lv_rgver_it  TYPE JITO_RGVER_RANGE_TT, "   
lv_lgort_it  TYPE JITO_LGORT_RANGE_TT. "   

  CALL FUNCTION 'JITOUT06_READ_MULTI_PVBE_1'  "NOTRANSL: Lesen der Produktionsversorgungsbereiche
    EXPORTING
         WERKS_IT = lv_werks_it
         RGVER_IT = lv_rgver_it
         LGORT_IT = lv_lgort_it
    IMPORTING
         PVBE_ET = lv_pvbe_et
    EXCEPTIONS
        NO_ENTRY_FOUND = 1
. " JITOUT06_READ_MULTI_PVBE_1




ABAP code using 7.40 inline data declarations to call FM JITOUT06_READ_MULTI_PVBE_1

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!