SAP /SAPAPO/DBOR_MAPN_JOIN_CHPTR Function Module for Read External Representation Using Join









/SAPAPO/DBOR_MAPN_JOIN_CHPTR is a standard /sapapo/dbor mapn join chptr SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read External Representation Using Join 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 /sapapo/dbor mapn join chptr FM, simply by entering the name /SAPAPO/DBOR_MAPN_JOIN_CHPTR into the relevant SAP transaction such as SE37 or SE38.

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



Function /SAPAPO/DBOR_MAPN_JOIN_CHPTR 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 '/SAPAPO/DBOR_MAPN_JOIN_CHPTR'"Read External Representation Using Join
EXPORTING
* IV_SIMVERSION = GC_ACTIVE_VERSION "Name der Planversion
IV_LOGSYS = "Logisches System
* IV_R3OBJ = "Typ des OLTP-Objektes
* IV_PROCESSTYPE = "Auftragsnummer aus dem angeschlossenen OLTP-System
* IT_DATE = "Auftragsposition
* IT_PROCESSTIME = "Tabelle für Ranges mit Zeitstempel

IMPORTING
ET_CHPTR = "Tabellentyp zu /SAPAPO/CHPTR Tabelle
ET_DBORMAPN = "Tabellentyp für /SAPAPO/DBORMAPN

EXCEPTIONS
NO_ENTRIES_FOUND = 1 PARAMETER_ERROR = 2
.



IMPORTING Parameters details for /SAPAPO/DBOR_MAPN_JOIN_CHPTR

IV_SIMVERSION - Name der Planversion

Data type: /SAPAPO/VRSIOID
Default: GC_ACTIVE_VERSION
Optional: Yes
Call by Reference: Yes

IV_LOGSYS - Logisches System

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

IV_R3OBJ - Typ des OLTP-Objektes

Data type: /SAPAPO/R3OBJ
Optional: Yes
Call by Reference: Yes

IV_PROCESSTYPE - Auftragsnummer aus dem angeschlossenen OLTP-System

Data type: /SAPAPO/RSP_PROCESSTYPE
Optional: Yes
Call by Reference: Yes

IT_DATE - Auftragsposition

Data type: /SAPAPO/TSTMP_TAB
Optional: Yes
Call by Reference: Yes

IT_PROCESSTIME - Tabelle für Ranges mit Zeitstempel

Data type: /SAPAPO/TSTMP_TAB
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for /SAPAPO/DBOR_MAPN_JOIN_CHPTR

ET_CHPTR - Tabellentyp zu /SAPAPO/CHPTR Tabelle

Data type: /SAPAPO/CHPTR_INT
Optional: No
Call by Reference: Yes

ET_DBORMAPN - Tabellentyp für /SAPAPO/DBORMAPN

Data type: /SAPAPO/DBORMAPN_TAB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_ENTRIES_FOUND - keine Einträge gefunden

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

PARAMETER_ERROR - grgdrsf

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for /SAPAPO/DBOR_MAPN_JOIN_CHPTR 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_et_chptr  TYPE /SAPAPO/CHPTR_INT, "   
lv_iv_simversion  TYPE /SAPAPO/VRSIOID, "   GC_ACTIVE_VERSION
lv_no_entries_found  TYPE /SAPAPO/VRSIOID, "   
lv_iv_logsys  TYPE LOGSYS, "   
lv_et_dbormapn  TYPE /SAPAPO/DBORMAPN_TAB, "   
lv_parameter_error  TYPE /SAPAPO/DBORMAPN_TAB, "   
lv_iv_r3obj  TYPE /SAPAPO/R3OBJ, "   
lv_iv_processtype  TYPE /SAPAPO/RSP_PROCESSTYPE, "   
lv_it_date  TYPE /SAPAPO/TSTMP_TAB, "   
lv_it_processtime  TYPE /SAPAPO/TSTMP_TAB. "   

  CALL FUNCTION '/SAPAPO/DBOR_MAPN_JOIN_CHPTR'  "Read External Representation Using Join
    EXPORTING
         IV_SIMVERSION = lv_iv_simversion
         IV_LOGSYS = lv_iv_logsys
         IV_R3OBJ = lv_iv_r3obj
         IV_PROCESSTYPE = lv_iv_processtype
         IT_DATE = lv_it_date
         IT_PROCESSTIME = lv_it_processtime
    IMPORTING
         ET_CHPTR = lv_et_chptr
         ET_DBORMAPN = lv_et_dbormapn
    EXCEPTIONS
        NO_ENTRIES_FOUND = 1
        PARAMETER_ERROR = 2
. " /SAPAPO/DBOR_MAPN_JOIN_CHPTR




ABAP code using 7.40 inline data declarations to call FM /SAPAPO/DBOR_MAPN_JOIN_CHPTR

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.

 
DATA(ld_iv_simversion) = GC_ACTIVE_VERSION.
 
 
 
 
 
 
 
 
 


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!