SAP GTR_CRM_CASE_CONVERT_GTRFIBILL Function Module for Retrieve Attributes for Grantor Billing Document

Search SAP Function Modules

GTR_CRM_CASE_CONVERT_GTRFIBILL is a standard gtr crm case convert gtrfibill SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Retrieve Attributes for Grantor Billing Document 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 gtr crm case convert gtrfibill FM, simply by entering the name GTR_CRM_CASE_CONVERT_GTRFIBILL into the relevant SAP transaction such as SE37 or SE38.

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

Function GTR_CRM_CASE_CONVERT_GTRFIBILL 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 'GTR_CRM_CASE_CONVERT_GTRFIBILL'"Retrieve Attributes for Grantor Billing Document
  EXPORTING
   IV_BORTYPE =  "Object type
   IV_BORKEY =  "Object ID

 IMPORTING
   EV_FIELD1 =  "
   EV_FIELD2 =  "
   EV_FIELD3 =  "
   EV_FIELD4 =  "
   EV_FIELD5 =  "

EXCEPTIONS
   INVALID_INPUT_DATA = 1 

.

IMPORTING Parameters details for GTR_CRM_CASE_CONVERT_GTRFIBILL

IV_BORTYPE - Object type

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

IV_BORKEY - Object ID

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

EXPORTING Parameters details for GTR_CRM_CASE_CONVERT_GTRFIBILL

EV_FIELD1 -

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

EV_FIELD2 -

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

EV_FIELD3 -

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

EV_FIELD4 -

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

EV_FIELD5 -

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

EXCEPTIONS details

INVALID_INPUT_DATA -

Data type:
Optional: No
Call by Reference: Yes

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

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