SAP CO_XT_COMPONENT_FOLLOW_UP_ADD Function Module for NOTRANSL: Add follow-up component in case of APO 4.0 Interchangeability
CO_XT_COMPONENT_FOLLOW_UP_ADD is a standard co xt component follow up add SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Add follow-up component in case of APO 4.0 Interchangeability 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 co xt component follow up add FM, simply by entering the name CO_XT_COMPONENT_FOLLOW_UP_ADD into the relevant SAP transaction such as SE37 or SE38.
Function Group: COXT
Program Name: SAPLCOXT
Main Program: SAPLCOXT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CO_XT_COMPONENT_FOLLOW_UP_ADD 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 'CO_XT_COMPONENT_FOLLOW_UP_ADD'"NOTRANSL: Add follow-up component in case of APO 4.0 Interchangeability.
EXPORTING
IS_ORDER_KEY = "
* I_CUOBJ = "
* I_CUOBJX = "
* I_BATCH_SEL_CUOBJ = "
* I_BATCH_SEL_CUOBJX = "
I_POSTP = "Item category (bill of material)
* I_XFEHL = "Missing Part
* I_XFEHLX = "
I_POSNO = "Item Number of an I/O Node in APO
I_REF_RSNUM = "Number of Reservation / Dependent Requirement
I_REF_RSPOS = "Item Number of Reservation/Dependent Requirement
I_MATERIAL = "
IS_REQU_QUAN = "
* IS_CONF_QUAN = "
* IS_CONF_QUANX = "
IS_STORAGE_LOCATION = "
IS_STORAGE_LOCATIONX = "
* I_BATCH = "
* I_BATCHX = "
IMPORTING
ES_AFPO = "Document structure for order items
ES_ISSUEDATE = "
ES_BAPIRETURN = "
E_ERROR_OCCURRED = "Generic Type
ES_RESBD_CREATED = "Reservation/Dependent Requirements
TABLES
* RESBT_EXP = "Document Table for Order Components
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLCOXT_001 DE-EN-LANG-SWITCH-NO-TRANSLATION
EXIT_SAPLCOXT_002 DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING Parameters details for CO_XT_COMPONENT_FOLLOW_UP_ADD
IS_ORDER_KEY -
Data type: COXT_ORD_KEYOptional: No
Call by Reference: Yes
I_CUOBJ -
Data type: COXT_CONFIG_OBJECTOptional: Yes
Call by Reference: Yes
I_CUOBJX -
Data type: COXT_CONFIG_OBJECTXOptional: Yes
Call by Reference: Yes
I_BATCH_SEL_CUOBJ -
Data type: COXT_CONFIG_OBJECTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BATCH_SEL_CUOBJX -
Data type: COXT_CONFIG_OBJECTXOptional: Yes
Call by Reference: Yes
I_POSTP - Item category (bill of material)
Data type: RESB-POSTPOptional: No
Call by Reference: Yes
I_XFEHL - Missing Part
Data type: RESB-XFEHLOptional: Yes
Call by Reference: Yes
I_XFEHLX -
Data type: COXT_BAPIUPDATEOptional: Yes
Call by Reference: Yes
I_POSNO - Item Number of an I/O Node in APO
Data type: CIF_R3RES-POSITIONNOOptional: No
Call by Reference: Yes
I_REF_RSNUM - Number of Reservation / Dependent Requirement
Data type: CIF_R3RES-RSNUMOptional: No
Call by Reference: Yes
I_REF_RSPOS - Item Number of Reservation/Dependent Requirement
Data type: CIF_R3RES-RSPOSOptional: No
Call by Reference: Yes
I_MATERIAL -
Data type: COXT_MATERIALOptional: No
Call by Reference: Yes
IS_REQU_QUAN -
Data type: COXT_S_QUANTITYOptional: No
Call by Reference: Yes
IS_CONF_QUAN -
Data type: COXT_S_QUANTITYOptional: Yes
Call by Reference: Yes
IS_CONF_QUANX -
Data type: COXT_S_QUANTITYXOptional: Yes
Call by Reference: Yes
IS_STORAGE_LOCATION -
Data type: COXT_S_STORAGE_LOCATIONOptional: No
Call by Reference: Yes
IS_STORAGE_LOCATIONX -
Data type: COXT_S_STORAGE_LOCATIONXOptional: No
Call by Reference: Yes
I_BATCH -
Data type: COXT_BATCHOptional: Yes
Call by Reference: Yes
I_BATCHX -
Data type: COXT_BATCHXOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CO_XT_COMPONENT_FOLLOW_UP_ADD
ES_AFPO - Document structure for order items
Data type: AFPOBOptional: No
Call by Reference: Yes
ES_ISSUEDATE -
Data type: COXT_S_DATEOptional: No
Call by Reference: Yes
ES_BAPIRETURN -
Data type: COXT_BAPIRETURNOptional: No
Call by Reference: Yes
E_ERROR_OCCURRED - Generic Type
Data type: COptional: No
Call by Reference: Yes
ES_RESBD_CREATED - Reservation/Dependent Requirements
Data type: RESBDOptional: No
Call by Reference: Yes
TABLES Parameters details for CO_XT_COMPONENT_FOLLOW_UP_ADD
RESBT_EXP - Document Table for Order Components
Data type: RESBBOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for CO_XT_COMPONENT_FOLLOW_UP_ADD 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_es_afpo | TYPE AFPOB, " | |||
| lt_resbt_exp | TYPE STANDARD TABLE OF RESBB, " | |||
| lv_is_order_key | TYPE COXT_ORD_KEY, " | |||
| lv_i_cuobj | TYPE COXT_CONFIG_OBJECT, " | |||
| lv_i_cuobjx | TYPE COXT_CONFIG_OBJECTX, " | |||
| lv_i_batch_sel_cuobj | TYPE COXT_CONFIG_OBJECT, " | |||
| lv_i_batch_sel_cuobjx | TYPE COXT_CONFIG_OBJECTX, " | |||
| lv_i_postp | TYPE RESB-POSTP, " | |||
| lv_i_xfehl | TYPE RESB-XFEHL, " | |||
| lv_i_xfehlx | TYPE COXT_BAPIUPDATE, " | |||
| lv_i_posno | TYPE CIF_R3RES-POSITIONNO, " | |||
| lv_i_ref_rsnum | TYPE CIF_R3RES-RSNUM, " | |||
| lv_i_ref_rspos | TYPE CIF_R3RES-RSPOS, " | |||
| lv_i_material | TYPE COXT_MATERIAL, " | |||
| lv_es_issuedate | TYPE COXT_S_DATE, " | |||
| lv_is_requ_quan | TYPE COXT_S_QUANTITY, " | |||
| lv_es_bapireturn | TYPE COXT_BAPIRETURN, " | |||
| lv_is_conf_quan | TYPE COXT_S_QUANTITY, " | |||
| lv_e_error_occurred | TYPE C, " | |||
| lv_is_conf_quanx | TYPE COXT_S_QUANTITYX, " | |||
| lv_es_resbd_created | TYPE RESBD, " | |||
| lv_is_storage_location | TYPE COXT_S_STORAGE_LOCATION, " | |||
| lv_is_storage_locationx | TYPE COXT_S_STORAGE_LOCATIONX, " | |||
| lv_i_batch | TYPE COXT_BATCH, " | |||
| lv_i_batchx | TYPE COXT_BATCHX. " |
|   CALL FUNCTION 'CO_XT_COMPONENT_FOLLOW_UP_ADD' "NOTRANSL: Add follow-up component in case of APO 4.0 Interchangeability |
| EXPORTING | ||
| IS_ORDER_KEY | = lv_is_order_key | |
| I_CUOBJ | = lv_i_cuobj | |
| I_CUOBJX | = lv_i_cuobjx | |
| I_BATCH_SEL_CUOBJ | = lv_i_batch_sel_cuobj | |
| I_BATCH_SEL_CUOBJX | = lv_i_batch_sel_cuobjx | |
| I_POSTP | = lv_i_postp | |
| I_XFEHL | = lv_i_xfehl | |
| I_XFEHLX | = lv_i_xfehlx | |
| I_POSNO | = lv_i_posno | |
| I_REF_RSNUM | = lv_i_ref_rsnum | |
| I_REF_RSPOS | = lv_i_ref_rspos | |
| I_MATERIAL | = lv_i_material | |
| IS_REQU_QUAN | = lv_is_requ_quan | |
| IS_CONF_QUAN | = lv_is_conf_quan | |
| IS_CONF_QUANX | = lv_is_conf_quanx | |
| IS_STORAGE_LOCATION | = lv_is_storage_location | |
| IS_STORAGE_LOCATIONX | = lv_is_storage_locationx | |
| I_BATCH | = lv_i_batch | |
| I_BATCHX | = lv_i_batchx | |
| IMPORTING | ||
| ES_AFPO | = lv_es_afpo | |
| ES_ISSUEDATE | = lv_es_issuedate | |
| ES_BAPIRETURN | = lv_es_bapireturn | |
| E_ERROR_OCCURRED | = lv_e_error_occurred | |
| ES_RESBD_CREATED | = lv_es_resbd_created | |
| TABLES | ||
| RESBT_EXP | = lt_resbt_exp | |
| . " CO_XT_COMPONENT_FOLLOW_UP_ADD | ||
ABAP code using 7.40 inline data declarations to call FM CO_XT_COMPONENT_FOLLOW_UP_ADD
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.| "SELECT single POSTP FROM RESB INTO @DATA(ld_i_postp). | ||||
| "SELECT single XFEHL FROM RESB INTO @DATA(ld_i_xfehl). | ||||
| "SELECT single POSITIONNO FROM CIF_R3RES INTO @DATA(ld_i_posno). | ||||
| "SELECT single RSNUM FROM CIF_R3RES INTO @DATA(ld_i_ref_rsnum). | ||||
| "SELECT single RSPOS FROM CIF_R3RES INTO @DATA(ld_i_ref_rspos). | ||||
Search for further information about these or an SAP related objects