SAP POS_CONDITION_POINTER_ANALYSE2 Function Module for POS-Schnittstelle: Analyse der Änderungen für Konditionen.









POS_CONDITION_POINTER_ANALYSE2 is a standard pos condition pointer analyse2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for POS-Schnittstelle: Analyse der Änderungen für Konditionen. 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 condition pointer analyse2 FM, simply by entering the name POS_CONDITION_POINTER_ANALYSE2 into the relevant SAP transaction such as SE37 or SE38.

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



Function POS_CONDITION_POINTER_ANALYSE2 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_CONDITION_POINTER_ANALYSE2'"POS-Schnittstelle: Analyse der Änderungen für Konditionen.
  EXPORTING
*  PI_DATAB = '00000000' "Beginndatum des Betrachtungszeitraums
*  PI_DATP3 = '00000000' "Bis-Datum 'letztes Versenden'. (Nur für POS)
*  PI_DATBI = '99991231' "Ende des Betrachtungszeitraums
*  PI_MODE = ' ' "'P'= POS, 'A'= Additionals,' ' (--> F2)
*  PI_VKORG =  "Verkaufsorganisation (nur für Additionals)
*  PI_VTWEG =  "Vertriebsweg (nur für Additionals)
*  PI_PARALLEL =  "Kennzeichen: Aufbereitung parallel.
*  PI_USE_INTERNAL_PCKG = ABAP_FALSE "= 'X': use internal packaging with prefetches

TABLES
*  PET_ARTSTM_OBJECTS =  "Filialabhängige Ergebnistabelle (--> F2)
   PIT_KONDART =  "POS-relevante Kond.arten pro Filiale. (--> F2)
   PIT_FILIA =  "POS-relevante Filialen (--> F2).
*  PET_BB_OBJ =  "Ergebnistabelle Sortimentsliste (--> F2).
*  PET_ARTSTM_OBJECTS_2 =  "Filialunabhängige Ergebnistabelle (--> F2)
*  PET_BB_OBJ_2 =  "Filialunabhängige Ergebnistabelle SL (--> F2)
   PIT_WIND =  "Zu analysierende Konditionen
.




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_SAPLWPDA_001 POS Interface: Modification of the IDoc Data Material Groups
EXIT_SAPLWPDA_002 POS Interface: Modification of IDoc Data for Material Master
EXIT_SAPLWPDA_003 POS Interface: Modification of IDoc Data for EAN/UPC References
EXIT_SAPLWPDA_004 POS Interface: Modification of IDoc Data for Set Assignments
EXIT_SAPLWPDA_005 POS Interface: Modification of IDoc Data for Follow-On Items
EXIT_SAPLWPDA_006 POS Interface: Modification of IDoc Data for Exchange Rates
EXIT_SAPLWPDA_007 POS Interface: Modification of IDoc Data for Taxes
EXIT_SAPLWPDA_008 POS Interface: Modification of IDoc Data for Personal Data
EXIT_SAPLWPDA_009 POS Interface: Additional Change Pointer Analysis for WP_PLU
EXIT_SAPLWPDA_010 POS Interface: Additional Change Pointer Analysis for WPDSET
EXIT_SAPLWPDA_011 POS Interface: Additional Change Pointer Analysis for WPDNAC
EXIT_SAPLWPDA_012 POS Interface: Additional Change Pointer Analysis for WPDWGR
EXIT_SAPLWPDA_013 POS Interface: Additional Change Pointer Analysis for WP_PER
EXIT_SAPLWPDA_015 POS Outbound: Additional Filter Option in Condition Pointer Analysis
EXIT_SAPLWPDA_016 POS Interface: Modification of IDoc Data for Promotion Discounts
EXIT_SAPLWPDA_017 POS Interface: Additional Change Pointer Analysis for WPDREB

IMPORTING Parameters details for POS_CONDITION_POINTER_ANALYSE2

PI_DATAB - Beginndatum des Betrachtungszeitraums

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

PI_DATP3 - Bis-Datum 'letztes Versenden'. (Nur für POS)

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

PI_DATBI - Ende des Betrachtungszeitraums

Data type: WPSTRUC-DATUM
Default: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PI_MODE - 'P'= POS, 'A'= Additionals,SPACE (--> F2)

Data type: WPSTRUC-MODUS
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

PI_VKORG - Verkaufsorganisation (nur für Additionals)

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

PI_VTWEG - Vertriebsweg (nur für Additionals)

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

PI_PARALLEL - Kennzeichen: Aufbereitung parallel.

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

PI_USE_INTERNAL_PCKG - = 'X': use internal packaging with prefetches

Data type: ABAP_BOOL
Default: ABAP_FALSE
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for POS_CONDITION_POINTER_ANALYSE2

PET_ARTSTM_OBJECTS - Filialabhängige Ergebnistabelle (--> F2)

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

PIT_KONDART - POS-relevante Kond.arten pro Filiale. (--> F2)

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

PIT_FILIA - POS-relevante Filialen (--> F2).

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

PET_BB_OBJ - Ergebnistabelle Sortimentsliste (--> F2).

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

PET_ARTSTM_OBJECTS_2 - Filialunabhängige Ergebnistabelle (--> F2)

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

PET_BB_OBJ_2 - Filialunabhängige Ergebnistabelle SL (--> F2)

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

PIT_WIND - Zu analysierende Konditionen

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

Copy and paste ABAP code example for POS_CONDITION_POINTER_ANALYSE2 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_pi_datab  TYPE WPSTRUC-DATUM, "   '00000000'
lt_pet_artstm_objects  TYPE STANDARD TABLE OF WPARTSTM, "   
lv_pi_datp3  TYPE WPSTRUC-DATUM, "   '00000000'
lt_pit_kondart  TYPE STANDARD TABLE OF WPKONDART, "   
lv_pi_datbi  TYPE WPSTRUC-DATUM, "   '99991231'
lt_pit_filia  TYPE STANDARD TABLE OF WDL_FIL, "   
lv_pi_mode  TYPE WPSTRUC-MODUS, "   ' '
lt_pet_bb_obj  TYPE STANDARD TABLE OF WPARTSTM2, "   
lv_pi_vkorg  TYPE WPSTRUC-VKORG, "   
lt_pet_artstm_objects_2  TYPE STANDARD TABLE OF WPAOT2, "   
lv_pi_vtweg  TYPE WPSTRUC-VTWEG, "   
lt_pet_bb_obj_2  TYPE STANDARD TABLE OF WPARTSTM2, "   
lt_pit_wind  TYPE STANDARD TABLE OF WINDVB, "   
lv_pi_parallel  TYPE WPSTRUC-PARALLEL, "   
lv_pi_use_internal_pckg  TYPE ABAP_BOOL. "   ABAP_FALSE

  CALL FUNCTION 'POS_CONDITION_POINTER_ANALYSE2'  "POS-Schnittstelle: Analyse der Änderungen für Konditionen.
    EXPORTING
         PI_DATAB = lv_pi_datab
         PI_DATP3 = lv_pi_datp3
         PI_DATBI = lv_pi_datbi
         PI_MODE = lv_pi_mode
         PI_VKORG = lv_pi_vkorg
         PI_VTWEG = lv_pi_vtweg
         PI_PARALLEL = lv_pi_parallel
         PI_USE_INTERNAL_PCKG = lv_pi_use_internal_pckg
    TABLES
         PET_ARTSTM_OBJECTS = lt_pet_artstm_objects
         PIT_KONDART = lt_pit_kondart
         PIT_FILIA = lt_pit_filia
         PET_BB_OBJ = lt_pet_bb_obj
         PET_ARTSTM_OBJECTS_2 = lt_pet_artstm_objects_2
         PET_BB_OBJ_2 = lt_pet_bb_obj_2
         PIT_WIND = lt_pit_wind
. " POS_CONDITION_POINTER_ANALYSE2




ABAP code using 7.40 inline data declarations to call FM POS_CONDITION_POINTER_ANALYSE2

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.

"SELECT single DATUM FROM WPSTRUC INTO @DATA(ld_pi_datab).
DATA(ld_pi_datab) = '00000000'.
 
 
"SELECT single DATUM FROM WPSTRUC INTO @DATA(ld_pi_datp3).
DATA(ld_pi_datp3) = '00000000'.
 
 
"SELECT single DATUM FROM WPSTRUC INTO @DATA(ld_pi_datbi).
DATA(ld_pi_datbi) = '99991231'.
 
 
"SELECT single MODUS FROM WPSTRUC INTO @DATA(ld_pi_mode).
DATA(ld_pi_mode) = ' '.
 
 
"SELECT single VKORG FROM WPSTRUC INTO @DATA(ld_pi_vkorg).
 
 
"SELECT single VTWEG FROM WPSTRUC INTO @DATA(ld_pi_vtweg).
 
 
 
"SELECT single PARALLEL FROM WPSTRUC INTO @DATA(ld_pi_parallel).
 
DATA(ld_pi_use_internal_pckg) = ABAP_FALSE.
 


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!