SAP POS_INFO_GET Function Module for NOTRANSL: Lesen Listungsabhängige Daten WWS für Verteilungs-Vorgänge

Search SAP Function Modules

POS_INFO_GET is a standard pos info get 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 Listungsabhängige Daten WWS für Verteilungs-Vorgänge 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 pos info get FM, simply by entering the name POS_INFO_GET into the relevant SAP transaction such as SE37 or SE38.

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

Function POS_INFO_GET 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 'POS_INFO_GET'"NOTRANSL: Lesen Listungsabhängige Daten WWS für Verteilungs-Vorgänge
  EXPORTING
   PI_ARTICLE =  "Material
*  PI_DATAB = '00000000' "Entries valid from
*  PI_DATBI = '00000000' "Entries valid to
   PI_FILIA =  "Store
   PI_VKORG =  "Sales organization
*  PI_VRKME =  "Sales unit
   PI_VTWEG =  "Distribution channel
*  PI_NO_EAN_CHECK =  "
*  BUFFER_WLK2_FILIA_ENTRIES = ' ' "Indicator: reset buffer for Material_Pre_Fetch

TABLES
   PET_WLK2_INFO =  "Valid listing conditions found

EXCEPTIONS
   VRKME_NOT_FOUND = 1    POS_INFO_NOT_FOUND = 2 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLWSOT_001 User Exit for Controling Listing Condition Maintenance

IMPORTING Parameters details for POS_INFO_GET

PI_ARTICLE - Material

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

PI_DATAB - Entries valid from

Data type: WLK1-DATAB
Default: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PI_DATBI - Entries valid to

Data type: WLK1-DATBI
Default: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PI_FILIA - Store

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

PI_VKORG - Sales organization

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

PI_VRKME - Sales unit

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

PI_VTWEG - Distribution channel

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

PI_NO_EAN_CHECK -

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

BUFFER_WLK2_FILIA_ENTRIES - Indicator: reset buffer for Material_Pre_Fetch

Data type: MTCOM-KZRFB
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for POS_INFO_GET

PET_WLK2_INFO - Valid listing conditions found

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

EXCEPTIONS details

VRKME_NOT_FOUND - Sales unit not allowed (T006U)

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

POS_INFO_NOT_FOUND -

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

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

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