SAP SDCAS_GETDETAIL_IMPL Function Module for Private implementation of method SalesSupportDocument.getDetail()









SDCAS_GETDETAIL_IMPL is a standard sdcas getdetail impl SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Private implementation of method SalesSupportDocument.getDetail() 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 sdcas getdetail impl FM, simply by entering the name SDCAS_GETDETAIL_IMPL into the relevant SAP transaction such as SE37 or SE38.

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



Function SDCAS_GETDETAIL_IMPL 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 'SDCAS_GETDETAIL_IMPL'"Private implementation of method SalesSupportDocument.getDetail()
  EXPORTING
   OBJEKTTYPE =  "BOR Object Type
*  RTF_ITF = ' ' "

TABLES
   SALESACTIVITYID =  "BOR ID Sales Support Documents
*  SALESACTIVITY =  "General data for partner sales activity
*  SALESPROMOTION =  "General data for sales promotion
*  BUSINESSPARTNER =  "Document partner
*  TEXT =  "Document text
*  BINARYRELATIONSHIP =  "Binary relationships
*  RETURN =  "Return code
.



IMPORTING Parameters details for SDCAS_GETDETAIL_IMPL

OBJEKTTYPE - BOR Object Type

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

RTF_ITF -

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

TABLES Parameters details for SDCAS_GETDETAIL_IMPL

SALESACTIVITYID - BOR ID Sales Support Documents

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

SALESACTIVITY - General data for partner sales activity

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

SALESPROMOTION - General data for sales promotion

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

BUSINESSPARTNER - Document partner

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

TEXT - Document text

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

BINARYRELATIONSHIP - Binary relationships

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

RETURN - Return code

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

Copy and paste ABAP code example for SDCAS_GETDETAIL_IMPL 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_objekttype  TYPE SWO_OBJTYP, "   
lt_salesactivityid  TYPE STANDARD TABLE OF BAPI_VBKA_BOID, "   
lv_rtf_itf  TYPE CHAR1, "   SPACE
lt_salesactivity  TYPE STANDARD TABLE OF BAPI_BUS1037_VBKAKOM_CR, "   
lt_salespromotion  TYPE STANDARD TABLE OF BAPI_VBKA_VBKAKOM, "   
lt_businesspartner  TYPE STANDARD TABLE OF BAPI_VBKA_VBPA2KOM, "   
lt_text  TYPE STANDARD TABLE OF BAPI_VBKA_TLINEKOM, "   
lt_binaryrelationship  TYPE STANDARD TABLE OF BAPI_VBKA_BINRELSHIP, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'SDCAS_GETDETAIL_IMPL'  "Private implementation of method SalesSupportDocument.getDetail()
    EXPORTING
         OBJEKTTYPE = lv_objekttype
         RTF_ITF = lv_rtf_itf
    TABLES
         SALESACTIVITYID = lt_salesactivityid
         SALESACTIVITY = lt_salesactivity
         SALESPROMOTION = lt_salespromotion
         BUSINESSPARTNER = lt_businesspartner
         TEXT = lt_text
         BINARYRELATIONSHIP = lt_binaryrelationship
         RETURN = lt_return
. " SDCAS_GETDETAIL_IMPL




ABAP code using 7.40 inline data declarations to call FM SDCAS_GETDETAIL_IMPL

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_rtf_itf) = ' '.
 
 
 
 
 
 
 


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!