SAP ASH_MM_MATBEL_READ Function Module for NOTRANSL: Datenbeschaffung Archive MATBEL

Search SAP Function Modules

ASH_MM_MATBEL_READ is a standard ash mm matbel 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 NOTRANSL: Datenbeschaffung Archive MATBEL 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 ash mm matbel read FM, simply by entering the name ASH_MM_MATBEL_READ into the relevant SAP transaction such as SE37 or SE38.

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

Function ASH_MM_MATBEL_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 'ASH_MM_MATBEL_READ'"NOTRANSL: Datenbeschaffung Archive MATBEL
  EXPORTING
*  I_ARCHIVEKEY =  "Key for Archive File
*  I_OFFSET =  "Offset of data object in archive file
*  I_BORIDENT =  "Object Relationship Service: BOR Object Identifier

TABLES
*  ET_MKPF =  "Header: Material Document
*  ET_MSEG =  "Document Segment: Material
*  ET_SADR =  "Address Management: Company data
*  ET_ADDR1_VAL =  "Address Return Structure

EXCEPTIONS
   NOT_IN_INFOSTRUCTURE = 1    NOT_IN_ARCHIVE = 2    NO_INSTRUCTURE_DEFINED = 3 

.

IMPORTING Parameters details for ASH_MM_MATBEL_READ

I_ARCHIVEKEY - Key for Archive File

Data type: ADMI_FILES-ARCHIV_KEY
Optional: Yes
Call by Reference: Yes

I_OFFSET - Offset of data object in archive file

Data type: ARCH_IDX-OFFSET
Optional: Yes
Call by Reference: Yes

I_BORIDENT - Object Relationship Service: BOR Object Identifier

Data type: BORIDENT
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for ASH_MM_MATBEL_READ

ET_MKPF - Header: Material Document

Data type: MKPF
Optional: Yes
Call by Reference: Yes

ET_MSEG - Document Segment: Material

Data type: MSEG
Optional: Yes
Call by Reference: Yes

ET_SADR - Address Management: Company data

Data type: SADR
Optional: Yes
Call by Reference: Yes

ET_ADDR1_VAL - Address Return Structure

Data type: ADDR1_VAL
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NOT_IN_INFOSTRUCTURE - Does not exist in the info structure

Data type:
Optional: No
Call by Reference: Yes

NOT_IN_ARCHIVE - Does not exist in the archive

Data type:
Optional: No
Call by Reference: Yes

NO_INSTRUCTURE_DEFINED - No infostructure defined for the deliveries

Data type:
Optional: No
Call by Reference: Yes

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

ABAP code using 7.40 inline data declarations to call FM ASH_MM_MATBEL_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.

Search for further information about these or an SAP related objects