SAP MABASN_READ_RELATION_FOR_ASN Function Module for NOTRANSL: Mengenabrufe zum Avis nachlesen









MABASN_READ_RELATION_FOR_ASN is a standard mabasn read relation for asn 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: Mengenabrufe zum Avis nachlesen 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 mabasn read relation for asn FM, simply by entering the name MABASN_READ_RELATION_FOR_ASN into the relevant SAP transaction such as SE37 or SE38.

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



Function MABASN_READ_RELATION_FOR_ASN 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 'MABASN_READ_RELATION_FOR_ASN'"NOTRANSL: Mengenabrufe zum Avis nachlesen
EXPORTING
I_VBELN = "Delivery
* I_POSNR = '000000' "Delivery Item

TABLES
E_PABASN = "Kanban Summarized JIT Call and Shipping Notification

EXCEPTIONS
NOTHING_FOUND = 1 CORRUPTED_DATA = 2
.



IMPORTING Parameters details for MABASN_READ_RELATION_FOR_ASN

I_VBELN - Delivery

Data type: PABASN-VBELN
Optional: No
Call by Reference: Yes

I_POSNR - Delivery Item

Data type: PABASN-POSNR
Default: '000000'
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for MABASN_READ_RELATION_FOR_ASN

E_PABASN - Kanban Summarized JIT Call and Shipping Notification

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

EXCEPTIONS details

NOTHING_FOUND -

Data type:
Optional: No
Call by Reference: Yes

CORRUPTED_DATA -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MABASN_READ_RELATION_FOR_ASN 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_vbeln  TYPE PABASN-VBELN, "   
lt_e_pabasn  TYPE STANDARD TABLE OF CPABASN, "   
lv_nothing_found  TYPE CPABASN, "   
lv_i_posnr  TYPE PABASN-POSNR, "   '000000'
lv_corrupted_data  TYPE PABASN. "   

  CALL FUNCTION 'MABASN_READ_RELATION_FOR_ASN'  "NOTRANSL: Mengenabrufe zum Avis nachlesen
    EXPORTING
         I_VBELN = lv_i_vbeln
         I_POSNR = lv_i_posnr
    TABLES
         E_PABASN = lt_e_pabasn
    EXCEPTIONS
        NOTHING_FOUND = 1
        CORRUPTED_DATA = 2
. " MABASN_READ_RELATION_FOR_ASN




ABAP code using 7.40 inline data declarations to call FM MABASN_READ_RELATION_FOR_ASN

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 VBELN FROM PABASN INTO @DATA(ld_i_vbeln).
 
 
 
"SELECT single POSNR FROM PABASN INTO @DATA(ld_i_posnr).
DATA(ld_i_posnr) = '000000'.
 
 


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!