SAP CRM_ORDER_PODC_EXECUTE_CHECK Function Module for









CRM_ORDER_PODC_EXECUTE_CHECK is a standard crm order podc execute check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 order podc execute check FM, simply by entering the name CRM_ORDER_PODC_EXECUTE_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function CRM_ORDER_PODC_EXECUTE_CHECK 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_ORDER_PODC_EXECUTE_CHECK'"
EXPORTING
IV_ORDER_GUID = "GUID of a CRM Order Object
IV_ORDER_KIND = "Object Type
IV_PO_NUMBER_SOLD = "Sold-To Party's External Reference Number

IMPORTING
ET_HEADER_GUID = "

EXCEPTIONS
FAILED = 1
.



IMPORTING Parameters details for CRM_ORDER_PODC_EXECUTE_CHECK

IV_ORDER_GUID - GUID of a CRM Order Object

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

IV_ORDER_KIND - Object Type

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

IV_PO_NUMBER_SOLD - Sold-To Party's External Reference Number

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

EXPORTING Parameters details for CRM_ORDER_PODC_EXECUTE_CHECK

ET_HEADER_GUID -

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

EXCEPTIONS details

FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CRM_ORDER_PODC_EXECUTE_CHECK 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_failed  TYPE STRING, "   
lv_iv_order_guid  TYPE CRMT_OBJECT_GUID, "   
lv_et_header_guid  TYPE CRMT_OBJECT_GUID_TAB, "   
lv_iv_order_kind  TYPE CRMT_OBJECT_KIND, "   
lv_iv_po_number_sold  TYPE CRMT_PO_NUMBER_SOLD. "   

  CALL FUNCTION 'CRM_ORDER_PODC_EXECUTE_CHECK'  "
    EXPORTING
         IV_ORDER_GUID = lv_iv_order_guid
         IV_ORDER_KIND = lv_iv_order_kind
         IV_PO_NUMBER_SOLD = lv_iv_po_number_sold
    IMPORTING
         ET_HEADER_GUID = lv_et_header_guid
    EXCEPTIONS
        FAILED = 1
. " CRM_ORDER_PODC_EXECUTE_CHECK




ABAP code using 7.40 inline data declarations to call FM CRM_ORDER_PODC_EXECUTE_CHECK

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!