SAP POS_CHANGE_POINTERS_READ Function Module for Lesen von Änderungszeigern









POS_CHANGE_POINTERS_READ is a standard pos change pointers read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Lesen von Änderungszeigern 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 change pointers read FM, simply by entering the name POS_CHANGE_POINTERS_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function POS_CHANGE_POINTERS_READ 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_CHANGE_POINTERS_READ'"Lesen von Änderungszeigern
  EXPORTING
*  PI_ACTIVATION_DATE_HIGH = ' ' "Aktivierungsdatum obere Grenze
*  PI_ACTIVATION_DATE_LOW = ' ' "Aktivierungsdatum untere Grenze
*  PI_ACTIVATION_TIME_HIGH = '000000' "Aktivierungszeit obere Grenze
*  PI_ACTIVATION_TIME_LOW = '000000' "Aktivierungszeit untere Grenze
*  PI_CREATION_DATE_HIGH = ' ' "Erzeugungsdatum obere Grenze
*  PI_CREATION_DATE_LOW = ' ' "Erzeugungsdatum untere Grenze
*  PI_CREATION_TIME_HIGH = '000000' "Erzeugungszeit obere Grenze
*  PI_CREATION_TIME_LOW = '000000' "Erzeugungszeit untere Grenze
*  PI_MESSAGE_TYPE =  "Nachrichtentyp

TABLES
   PET_CHANGE_POINTERS =  "Änderungszeiger
*  PIT_MESSAGE_TYPES =  "Tabelle mit Nachrichtentypen

EXCEPTIONS
   ERROR_IN_DATE_INTERVAL = 1    ERROR_IN_TIME_INTERVAL = 2    MESSAGE_TYPE_NEEDED = 3
.




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_CHANGE_POINTERS_READ

PI_ACTIVATION_DATE_HIGH - Aktivierungsdatum obere Grenze

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

PI_ACTIVATION_DATE_LOW - Aktivierungsdatum untere Grenze

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

PI_ACTIVATION_TIME_HIGH - Aktivierungszeit obere Grenze

Data type: SY-UZEIT
Default: '000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PI_ACTIVATION_TIME_LOW - Aktivierungszeit untere Grenze

Data type: SY-UZEIT
Default: '000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PI_CREATION_DATE_HIGH - Erzeugungsdatum obere Grenze

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

PI_CREATION_DATE_LOW - Erzeugungsdatum untere Grenze

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

PI_CREATION_TIME_HIGH - Erzeugungszeit obere Grenze

Data type: SY-UZEIT
Default: '000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PI_CREATION_TIME_LOW - Erzeugungszeit untere Grenze

Data type: SY-UZEIT
Default: '000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PI_MESSAGE_TYPE - Nachrichtentyp

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

TABLES Parameters details for POS_CHANGE_POINTERS_READ

PET_CHANGE_POINTERS - Änderungszeiger

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

PIT_MESSAGE_TYPES - Tabelle mit Nachrichtentypen

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

EXCEPTIONS details

ERROR_IN_DATE_INTERVAL - Fehler im Datumintervall

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

ERROR_IN_TIME_INTERVAL - Fehler im Zeitintervall

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

MESSAGE_TYPE_NEEDED - Es wurde kein Nachrichtentyp mitgegeben.

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

Copy and paste ABAP code example for POS_CHANGE_POINTERS_READ 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_pet_change_pointers  TYPE STANDARD TABLE OF BDCP, "   
lv_error_in_date_interval  TYPE BDCP, "   
lv_pi_activation_date_high  TYPE SY-DATUM, "   SPACE
lt_pit_message_types  TYPE STANDARD TABLE OF BDMSGTYP, "   
lv_error_in_time_interval  TYPE BDMSGTYP, "   
lv_pi_activation_date_low  TYPE SY-DATUM, "   SPACE
lv_message_type_needed  TYPE SY, "   
lv_pi_activation_time_high  TYPE SY-UZEIT, "   '000000'
lv_pi_activation_time_low  TYPE SY-UZEIT, "   '000000'
lv_pi_creation_date_high  TYPE SY-DATUM, "   SPACE
lv_pi_creation_date_low  TYPE SY-DATUM, "   SPACE
lv_pi_creation_time_high  TYPE SY-UZEIT, "   '000000'
lv_pi_creation_time_low  TYPE SY-UZEIT, "   '000000'
lv_pi_message_type  TYPE BDMSGTYP-MESTYP. "   

  CALL FUNCTION 'POS_CHANGE_POINTERS_READ'  "Lesen von Änderungszeigern
    EXPORTING
         PI_ACTIVATION_DATE_HIGH = lv_pi_activation_date_high
         PI_ACTIVATION_DATE_LOW = lv_pi_activation_date_low
         PI_ACTIVATION_TIME_HIGH = lv_pi_activation_time_high
         PI_ACTIVATION_TIME_LOW = lv_pi_activation_time_low
         PI_CREATION_DATE_HIGH = lv_pi_creation_date_high
         PI_CREATION_DATE_LOW = lv_pi_creation_date_low
         PI_CREATION_TIME_HIGH = lv_pi_creation_time_high
         PI_CREATION_TIME_LOW = lv_pi_creation_time_low
         PI_MESSAGE_TYPE = lv_pi_message_type
    TABLES
         PET_CHANGE_POINTERS = lt_pet_change_pointers
         PIT_MESSAGE_TYPES = lt_pit_message_types
    EXCEPTIONS
        ERROR_IN_DATE_INTERVAL = 1
        ERROR_IN_TIME_INTERVAL = 2
        MESSAGE_TYPE_NEEDED = 3
. " POS_CHANGE_POINTERS_READ




ABAP code using 7.40 inline data declarations to call FM POS_CHANGE_POINTERS_READ

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 SY INTO @DATA(ld_pi_activation_date_high).
DATA(ld_pi_activation_date_high) = ' '.
 
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_pi_activation_date_low).
DATA(ld_pi_activation_date_low) = ' '.
 
 
"SELECT single UZEIT FROM SY INTO @DATA(ld_pi_activation_time_high).
DATA(ld_pi_activation_time_high) = '000000'.
 
"SELECT single UZEIT FROM SY INTO @DATA(ld_pi_activation_time_low).
DATA(ld_pi_activation_time_low) = '000000'.
 
"SELECT single DATUM FROM SY INTO @DATA(ld_pi_creation_date_high).
DATA(ld_pi_creation_date_high) = ' '.
 
"SELECT single DATUM FROM SY INTO @DATA(ld_pi_creation_date_low).
DATA(ld_pi_creation_date_low) = ' '.
 
"SELECT single UZEIT FROM SY INTO @DATA(ld_pi_creation_time_high).
DATA(ld_pi_creation_time_high) = '000000'.
 
"SELECT single UZEIT FROM SY INTO @DATA(ld_pi_creation_time_low).
DATA(ld_pi_creation_time_low) = '000000'.
 
"SELECT single MESTYP FROM BDMSGTYP INTO @DATA(ld_pi_message_type).
 


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!