SAP MAM25_050_GETDETAIL Function Module for NOTRANSL: Detaildaten zum Partner lesen









MAM25_050_GETDETAIL is a standard mam25 050 getdetail 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: Detaildaten zum Partner lesen 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 mam25 050 getdetail FM, simply by entering the name MAM25_050_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.

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



Function MAM25_050_GETDETAIL 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 'MAM25_050_GETDETAIL'"NOTRANSL: Detaildaten zum Partner lesen
  EXPORTING
   PARTNER_KEY =  "Associated Partner Key

 IMPORTING
   PARTNER_HEADER =  "Partner Header Data

TABLES
*  CONTRACTS =  "Contract Header
*  CONTACT_PERSONS =  "Contact Person
*  CE_PARTNER_HEADER =  "Copy user-speific fields to the mobile device
*  CE_CONTRACTS =  "Copy user-speific fields to the mobile device
*  CE_CONTACT_PERSONS =  "Customer Enhancement for Contact Person
*  RETURN =  "Return Parameter
*  WSAP_EXTENSION =  "SAP Enhancement
.



IMPORTING Parameters details for MAM25_050_GETDETAIL

PARTNER_KEY - Associated Partner Key

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

EXPORTING Parameters details for MAM25_050_GETDETAIL

PARTNER_HEADER - Partner Header Data

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

TABLES Parameters details for MAM25_050_GETDETAIL

CONTRACTS - Contract Header

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

CONTACT_PERSONS - Contact Person

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

CE_PARTNER_HEADER - Copy user-speific fields to the mobile device

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

CE_CONTRACTS - Copy user-speific fields to the mobile device

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

CE_CONTACT_PERSONS - Customer Enhancement for Contact Person

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

RETURN - Return Parameter

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

WSAP_EXTENSION - SAP Enhancement

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

Copy and paste ABAP code example for MAM25_050_GETDETAIL 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_contracts  TYPE STANDARD TABLE OF MAM_25_CONTRACT_HEADER, "   
lv_partner_key  TYPE MAM_25_PARTNER_HEADER-PARTNER_KEY, "   
lv_partner_header  TYPE MAM_25_PARTNER_HEADER, "   
lt_contact_persons  TYPE STANDARD TABLE OF MAM_25_CONTACT_PERSON, "   
lt_ce_partner_header  TYPE STANDARD TABLE OF ALM_ME_CUSTOMER_ENHANCEMENT, "   
lt_ce_contracts  TYPE STANDARD TABLE OF ALM_ME_CUSTOMER_ENHANCEMENT, "   
lt_ce_contact_persons  TYPE STANDARD TABLE OF ALM_ME_CUSTOMER_ENHANCEMENT, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_wsap_extension  TYPE STANDARD TABLE OF ALM_ME_SAP_EXTENSION. "   

  CALL FUNCTION 'MAM25_050_GETDETAIL'  "NOTRANSL: Detaildaten zum Partner lesen
    EXPORTING
         PARTNER_KEY = lv_partner_key
    IMPORTING
         PARTNER_HEADER = lv_partner_header
    TABLES
         CONTRACTS = lt_contracts
         CONTACT_PERSONS = lt_contact_persons
         CE_PARTNER_HEADER = lt_ce_partner_header
         CE_CONTRACTS = lt_ce_contracts
         CE_CONTACT_PERSONS = lt_ce_contact_persons
         RETURN = lt_return
         WSAP_EXTENSION = lt_wsap_extension
. " MAM25_050_GETDETAIL




ABAP code using 7.40 inline data declarations to call FM MAM25_050_GETDETAIL

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 PARTNER_KEY FROM MAM_25_PARTNER_HEADER INTO @DATA(ld_partner_key).
 
 
 
 
 
 
 
 


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!