SAP FKC_API_BLK_CC_PC_REQ_IN Function Module for CC Provider Contract message processing

Search SAP Function Modules

FKC_API_BLK_CC_PC_REQ_IN is a standard fkc api blk cc pc req in SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CC Provider Contract message processing 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 fkc api blk cc pc req in FM, simply by entering the name FKC_API_BLK_CC_PC_REQ_IN into the relevant SAP transaction such as SE37 or SE38.

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

Function FKC_API_BLK_CC_PC_REQ_IN 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 'FKC_API_BLK_CC_PC_REQ_IN'"CC Provider Contract message processing
  EXPORTING
   IS_HEADER =  "BulkIDMessageHeader
   IS_DATA =  "Proxy Structure (generated)
   IS_XI_MESSAGE_GUID =  "XI: Message ID
   IS_REQUEST_HEADER =  "Business information from the perspective of the sender appl

 IMPORTING
   RETURN_TAB =  "Return table

.

IMPORTING Parameters details for FKC_API_BLK_CC_PC_REQ_IN

IS_HEADER - BulkIDMessageHeader

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

IS_DATA - Proxy Structure (generated)

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

IS_XI_MESSAGE_GUID - XI: Message ID

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

IS_REQUEST_HEADER - Business information from the perspective of the sender appl

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

EXPORTING Parameters details for FKC_API_BLK_CC_PC_REQ_IN

RETURN_TAB - Return table

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

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

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