SAP CACS00_SAMPLE_PRC_9800 Function Module for Data Transfer ICM -> FI-AP
CACS00_SAMPLE_PRC_9800 is a standard cacs00 sample prc 9800 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Data Transfer ICM -> FI-AP 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 cacs00 sample prc 9800 FM, simply by entering the name CACS00_SAMPLE_PRC_9800 into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS00_SAMPLE
Program Name: SAPLCACS00_SAMPLE
Main Program: SAPLCACS00_SAMPLE
Appliation area: E
Release date: 30-Nov-2004
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CACS00_SAMPLE_PRC_9800 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 'CACS00_SAMPLE_PRC_9800'"Data Transfer ICM -> FI-AP.
EXPORTING
I_DATA_HD = "Document Header
I_DOC_HD = "Incoming Invoice (Header)
IMPORTING
E_DOC_HD = "Incoming Invoice (Header)
TABLES
IT_DATA_SE = "Document Items
CT_EXTENSION = "
CT_ACC_PAY = "Incoming Invoice (Vendor)
CT_ACC_GL = "Incoming Invoice (Item)
CT_ACC_TAX = "Accounting: Taxes (Item)
CT_CUR_AMT = "Currency Fields (Item)
CT_PUR_ORDER = "Purchase Order (Item)
CT_PUR_AMT = "Commitment (Currency Fields)
CT_CRITERIA = "CO-PA Account Assignment Characteristics
CT_VAL_FIELD = "CO-PA Account Assignment Value Fields
IMPORTING Parameters details for CACS00_SAMPLE_PRC_9800
I_DATA_HD - Document Header
Data type: CACS00_S_TRANSFER_FI_HOptional: No
Call by Reference: No ( called with pass by value option)
I_DOC_HD - Incoming Invoice (Header)
Data type: BAPIACHE03Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CACS00_SAMPLE_PRC_9800
E_DOC_HD - Incoming Invoice (Header)
Data type: BAPIACHE03Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CACS00_SAMPLE_PRC_9800
IT_DATA_SE - Document Items
Data type: CACS00_S_TRANSFER_FI_POptional: No
Call by Reference: Yes
CT_EXTENSION -
Data type: BAPIEXTCOptional: No
Call by Reference: Yes
CT_ACC_PAY - Incoming Invoice (Vendor)
Data type: BAPIACAP03Optional: No
Call by Reference: Yes
CT_ACC_GL - Incoming Invoice (Item)
Data type: BAPIACGL03Optional: No
Call by Reference: Yes
CT_ACC_TAX - Accounting: Taxes (Item)
Data type: BAPIACTX01Optional: No
Call by Reference: Yes
CT_CUR_AMT - Currency Fields (Item)
Data type: BAPIACCR01Optional: No
Call by Reference: Yes
CT_PUR_ORDER - Purchase Order (Item)
Data type: BAPIACPO00Optional: No
Call by Reference: Yes
CT_PUR_AMT - Commitment (Currency Fields)
Data type: BAPIACCRPOOptional: No
Call by Reference: Yes
CT_CRITERIA - CO-PA Account Assignment Characteristics
Data type: BAPIACKECROptional: No
Call by Reference: Yes
CT_VAL_FIELD - CO-PA Account Assignment Value Fields
Data type: BAPIACKEVAOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CACS00_SAMPLE_PRC_9800 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_e_doc_hd | TYPE BAPIACHE03, " | |||
| lv_i_data_hd | TYPE CACS00_S_TRANSFER_FI_H, " | |||
| lt_it_data_se | TYPE STANDARD TABLE OF CACS00_S_TRANSFER_FI_P, " | |||
| lt_ct_extension | TYPE STANDARD TABLE OF BAPIEXTC, " | |||
| lv_i_doc_hd | TYPE BAPIACHE03, " | |||
| lt_ct_acc_pay | TYPE STANDARD TABLE OF BAPIACAP03, " | |||
| lt_ct_acc_gl | TYPE STANDARD TABLE OF BAPIACGL03, " | |||
| lt_ct_acc_tax | TYPE STANDARD TABLE OF BAPIACTX01, " | |||
| lt_ct_cur_amt | TYPE STANDARD TABLE OF BAPIACCR01, " | |||
| lt_ct_pur_order | TYPE STANDARD TABLE OF BAPIACPO00, " | |||
| lt_ct_pur_amt | TYPE STANDARD TABLE OF BAPIACCRPO, " | |||
| lt_ct_criteria | TYPE STANDARD TABLE OF BAPIACKECR, " | |||
| lt_ct_val_field | TYPE STANDARD TABLE OF BAPIACKEVA. " |
|   CALL FUNCTION 'CACS00_SAMPLE_PRC_9800' "Data Transfer ICM -> FI-AP |
| EXPORTING | ||
| I_DATA_HD | = lv_i_data_hd | |
| I_DOC_HD | = lv_i_doc_hd | |
| IMPORTING | ||
| E_DOC_HD | = lv_e_doc_hd | |
| TABLES | ||
| IT_DATA_SE | = lt_it_data_se | |
| CT_EXTENSION | = lt_ct_extension | |
| CT_ACC_PAY | = lt_ct_acc_pay | |
| CT_ACC_GL | = lt_ct_acc_gl | |
| CT_ACC_TAX | = lt_ct_acc_tax | |
| CT_CUR_AMT | = lt_ct_cur_amt | |
| CT_PUR_ORDER | = lt_ct_pur_order | |
| CT_PUR_AMT | = lt_ct_pur_amt | |
| CT_CRITERIA | = lt_ct_criteria | |
| CT_VAL_FIELD | = lt_ct_val_field | |
| . " CACS00_SAMPLE_PRC_9800 | ||
ABAP code using 7.40 inline data declarations to call FM CACS00_SAMPLE_PRC_9800
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