SAP JBD_EXP_CHGPTR_PROCESS Function Module for Verarbeitung der Änderungszeiger









JBD_EXP_CHGPTR_PROCESS is a standard jbd exp chgptr process SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Verarbeitung der Änderungszeiger 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 jbd exp chgptr process FM, simply by entering the name JBD_EXP_CHGPTR_PROCESS into the relevant SAP transaction such as SE37 or SE38.

Function Group: JBD_EXP
Program Name: SAPLJBD_EXP
Main Program: SAPLJBD_EXP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function JBD_EXP_CHGPTR_PROCESS 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 'JBD_EXP_CHGPTR_PROCESS'"Verarbeitung der Änderungszeiger
EXPORTING
* I_LOGHANDLE = "Anwendungs-Log: Handle eines Protokolls
I_TAB_CHGPTRS = "Änderungszeiger IDs
* I_BLOCKSIZE = "Interne Tabellen, aktueller Zeilenindex

IMPORTING
E_PROCESSED_CNT = "Datenbankzugriffe, Anzahl der bearbeiteten Tabellenzeilen
E_ERRORS_CNT = "Datenbankzugriffe, Anzahl der bearbeiteten Tabellenzeilen
E_TAB_ERRORS = "Schlüssel der fehlerhaften Exportobjekte
E_MESSAGES = "Nachrichtensammler
E_PROCESSED_CPIDS = "Änderungszeiger IDs
E_EXPOBJTYPE = "Exportobjekttyp
.



IMPORTING Parameters details for JBD_EXP_CHGPTR_PROCESS

I_LOGHANDLE - Anwendungs-Log: Handle eines Protokolls

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

I_TAB_CHGPTRS - Änderungszeiger IDs

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

I_BLOCKSIZE - Interne Tabellen, aktueller Zeilenindex

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

EXPORTING Parameters details for JBD_EXP_CHGPTR_PROCESS

E_PROCESSED_CNT - Datenbankzugriffe, Anzahl der bearbeiteten Tabellenzeilen

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

E_ERRORS_CNT - Datenbankzugriffe, Anzahl der bearbeiteten Tabellenzeilen

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

E_TAB_ERRORS - Schlüssel der fehlerhaften Exportobjekte

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

E_MESSAGES - Nachrichtensammler

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

E_PROCESSED_CPIDS - Änderungszeiger IDs

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

E_EXPOBJTYPE - Exportobjekttyp

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

Copy and paste ABAP code example for JBD_EXP_CHGPTR_PROCESS 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_i_loghandle  TYPE BALLOGHNDL, "   
lv_e_processed_cnt  TYPE SY-DBCNT, "   
lv_e_errors_cnt  TYPE SY-DBCNT, "   
lv_i_tab_chgptrs  TYPE JBD_TAB_TABCHGPTRS, "   
lv_i_blocksize  TYPE SY-TABIX, "   
lv_e_tab_errors  TYPE JBD_TAB_TABKEYS, "   
lv_e_messages  TYPE JBD_TAB_TABMESG, "   
lv_e_processed_cpids  TYPE JBD_TAB_TABCPIDS, "   
lv_e_expobjtype  TYPE JBD_DTE_EXPOBJ. "   

  CALL FUNCTION 'JBD_EXP_CHGPTR_PROCESS'  "Verarbeitung der Änderungszeiger
    EXPORTING
         I_LOGHANDLE = lv_i_loghandle
         I_TAB_CHGPTRS = lv_i_tab_chgptrs
         I_BLOCKSIZE = lv_i_blocksize
    IMPORTING
         E_PROCESSED_CNT = lv_e_processed_cnt
         E_ERRORS_CNT = lv_e_errors_cnt
         E_TAB_ERRORS = lv_e_tab_errors
         E_MESSAGES = lv_e_messages
         E_PROCESSED_CPIDS = lv_e_processed_cpids
         E_EXPOBJTYPE = lv_e_expobjtype
. " JBD_EXP_CHGPTR_PROCESS




ABAP code using 7.40 inline data declarations to call FM JBD_EXP_CHGPTR_PROCESS

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 DBCNT FROM SY INTO @DATA(ld_e_processed_cnt).
 
"SELECT single DBCNT FROM SY INTO @DATA(ld_e_errors_cnt).
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_i_blocksize).
 
 
 
 
 


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!