SAP BAPI_CRMCASE_GETCASEDOC Function Module for Get a document (Metadata and Content) linked to the case.









BAPI_CRMCASE_GETCASEDOC is a standard bapi crmcase getcasedoc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get a document (Metadata and Content) linked to the case. 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 bapi crmcase getcasedoc FM, simply by entering the name BAPI_CRMCASE_GETCASEDOC into the relevant SAP transaction such as SE37 or SE38.

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



Function BAPI_CRMCASE_GETCASEDOC 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 'BAPI_CRMCASE_GETCASEDOC'"Get a document (Metadata and Content) linked to the case.
  EXPORTING
   GUID =  "Technical Case Key (Case GUID)
   IO =  "KW Framework: Object Key
*  INCLUDE_CONTENT =  "New Input Values

 IMPORTING
   LOIO =  "KW Framework: Object Key

TABLES
*  PROPERTIES =  "Document Property
*  PROPERTIES_ATTR =  "Attribute Property
*  FILE_ACCESS_INFO =  "File Access Info
*  FILE_CONTENT_ASCII =  "Document content (ASCII)
*  FILE_CONTENT_BINARY =  "Document content (binary)
   PHIOS =  "Case CM document structure.
   RETURN =  "Return Parameter
.



IMPORTING Parameters details for BAPI_CRMCASE_GETCASEDOC

GUID - Technical Case Key (Case GUID)

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

IO - KW Framework: Object Key

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

INCLUDE_CONTENT - New Input Values

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

EXPORTING Parameters details for BAPI_CRMCASE_GETCASEDOC

LOIO - KW Framework: Object Key

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

TABLES Parameters details for BAPI_CRMCASE_GETCASEDOC

PROPERTIES - Document Property

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

PROPERTIES_ATTR - Attribute Property

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

FILE_ACCESS_INFO - File Access Info

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

FILE_CONTENT_ASCII - Document content (ASCII)

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

FILE_CONTENT_BINARY - Document content (binary)

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

PHIOS - Case CM document structure.

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

RETURN - Return Parameter

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

Copy and paste ABAP code example for BAPI_CRMCASE_GETCASEDOC 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_guid  TYPE BAPISCMGCASE-CASE_GUID, "   
lv_loio  TYPE BAPICASEDOC, "   
lt_properties  TYPE STANDARD TABLE OF BAPISDOKPROPTY, "   
lv_io  TYPE BAPICASEDOC, "   
lt_properties_attr  TYPE STANDARD TABLE OF BAPIATTRPROP, "   
lv_include_content  TYPE BAPISDOKFILACI-BINARY_FLAG, "   
lt_file_access_info  TYPE STANDARD TABLE OF BAPISDOKFILACI, "   
lt_file_content_ascii  TYPE STANDARD TABLE OF BAPISDOKCNTASC, "   
lt_file_content_binary  TYPE STANDARD TABLE OF BAPISDOKCNTBIN, "   
lt_phios  TYPE STANDARD TABLE OF BAPICASEDOC, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'BAPI_CRMCASE_GETCASEDOC'  "Get a document (Metadata and Content) linked to the case.
    EXPORTING
         GUID = lv_guid
         IO = lv_io
         INCLUDE_CONTENT = lv_include_content
    IMPORTING
         LOIO = lv_loio
    TABLES
         PROPERTIES = lt_properties
         PROPERTIES_ATTR = lt_properties_attr
         FILE_ACCESS_INFO = lt_file_access_info
         FILE_CONTENT_ASCII = lt_file_content_ascii
         FILE_CONTENT_BINARY = lt_file_content_binary
         PHIOS = lt_phios
         RETURN = lt_return
. " BAPI_CRMCASE_GETCASEDOC




ABAP code using 7.40 inline data declarations to call FM BAPI_CRMCASE_GETCASEDOC

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 CASE_GUID FROM BAPISCMGCASE INTO @DATA(ld_guid).
 
 
 
 
 
"SELECT single BINARY_FLAG FROM BAPISDOKFILACI INTO @DATA(ld_include_content).
 
 
 
 
 
 


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!