SAP CRM_CONTRACT_GET_ELIGIBLE_NODE Function Module for Finden aller abrufberechtigter Knoten der Hierarchien









CRM_CONTRACT_GET_ELIGIBLE_NODE is a standard crm contract get eligible node SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Finden aller abrufberechtigter Knoten der Hierarchien 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 crm contract get eligible node FM, simply by entering the name CRM_CONTRACT_GET_ELIGIBLE_NODE into the relevant SAP transaction such as SE37 or SE38.

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



Function CRM_CONTRACT_GET_ELIGIBLE_NODE 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 'CRM_CONTRACT_GET_ELIGIBLE_NODE'"Finden aller abrufberechtigter Knoten der Hierarchien
  EXPORTING
   IV_SOLD_TO_PARTY =  "Partner Number
   IV_SALES_ORG =  "Sales Organization
   IV_DIS_CHANNEL =  "Distribution Channel
   IV_DIVISION =  "Division
   IV_RELEASE_DATE =  "Time Stamp (Date and Time)
   IV_TARGET_PROCESS_TYPE =  "Business Transaction Type
   IT_SOURCE_OBJECT_TYPES =  "Table of Object Types

 IMPORTING
   ET_ELIGIBLE_TREE =  "Table of Release-Authorized Hierarchies with Nodes
.



IMPORTING Parameters details for CRM_CONTRACT_GET_ELIGIBLE_NODE

IV_SOLD_TO_PARTY - Partner Number

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

IV_SALES_ORG - Sales Organization

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

IV_DIS_CHANNEL - Distribution Channel

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

IV_DIVISION - Division

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

IV_RELEASE_DATE - Time Stamp (Date and Time)

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

IV_TARGET_PROCESS_TYPE - Business Transaction Type

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

IT_SOURCE_OBJECT_TYPES - Table of Object Types

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

EXPORTING Parameters details for CRM_CONTRACT_GET_ELIGIBLE_NODE

ET_ELIGIBLE_TREE - Table of Release-Authorized Hierarchies with Nodes

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

Copy and paste ABAP code example for CRM_CONTRACT_GET_ELIGIBLE_NODE 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_et_eligible_tree  TYPE CRMT_ELIGIBLE_TREE_T, "   
lv_iv_sold_to_party  TYPE CRMT_PARTNER_NO, "   
lv_iv_sales_org  TYPE CRMT_SALES_ORG, "   
lv_iv_dis_channel  TYPE CRMT_DISTRIBUTION_CHANNEL, "   
lv_iv_division  TYPE CRMT_DIVISION, "   
lv_iv_release_date  TYPE CRMT_TIMESTAMP, "   
lv_iv_target_process_type  TYPE CRMT_PROCESS_TYPE, "   
lv_it_source_object_types  TYPE CRMT_SWO_OBJTYP_PROCESS_TAB. "   

  CALL FUNCTION 'CRM_CONTRACT_GET_ELIGIBLE_NODE'  "Finden aller abrufberechtigter Knoten der Hierarchien
    EXPORTING
         IV_SOLD_TO_PARTY = lv_iv_sold_to_party
         IV_SALES_ORG = lv_iv_sales_org
         IV_DIS_CHANNEL = lv_iv_dis_channel
         IV_DIVISION = lv_iv_division
         IV_RELEASE_DATE = lv_iv_release_date
         IV_TARGET_PROCESS_TYPE = lv_iv_target_process_type
         IT_SOURCE_OBJECT_TYPES = lv_it_source_object_types
    IMPORTING
         ET_ELIGIBLE_TREE = lv_et_eligible_tree
. " CRM_CONTRACT_GET_ELIGIBLE_NODE




ABAP code using 7.40 inline data declarations to call FM CRM_CONTRACT_GET_ELIGIBLE_NODE

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



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!