SAP IDOC_OUTPUT_CFPREQ Function Module for Freight planning request to forwarding agent
IDOC_OUTPUT_CFPREQ is a standard idoc output cfpreq SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Freight planning request to forwarding agent 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 idoc output cfpreq FM, simply by entering the name IDOC_OUTPUT_CFPREQ into the relevant SAP transaction such as SE37 or SE38.
Function Group: V56I
Program Name: SAPLV56I
Main Program: SAPLV56I
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IDOC_OUTPUT_CFPREQ 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 'IDOC_OUTPUT_CFPREQ'"Freight planning request to forwarding agent.
EXPORTING
DELIVERY = "
* ACTION_CODE = "
* CARRIER = "Number of Forwarding Agent
* SHIPPPT = "Transportation planning point
* SHIPTYP = "Transport Type
* TXTID1 = "Delivery Header Text ID for Freight Planning Transfer
* TXTID2 = "Delivery Header Text ID for Freight Planning Transfer
* TXTID3 = "Delivery Header Text ID for Freight Planning Transfer
* OUTPUTTYPE = "Condition Type
EXCEPTIONS
NO_SHIP_PLAN_PNT = 1 IDOC_NOT_TO_SEND = 2 IDOC_SETUP_FAILED = 3 WRONG_SHIP_PLAN_PNT = 4
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_SAPLV56I_001 IDOC TPSDLS: Modification of IDOC in Delivery Header Segment Group
EXIT_SAPLV56I_002 IDOC TPSDLS: Modification of IDOC in Delivery Item Group
EXIT_SAPLV56I_003 IDOC TPSDLS: Modification of IDOC in Packaging Data Group
EXIT_SAPLV56I_004 IDOC TPSDLS: Modification of Entire IDOC After Generation
EXIT_SAPLV56I_005 IDOC TPSDLS: Modification of Transport-Relevant Delivery Items
EXIT_SAPLV56I_006 IDOC TPSDLS: User-Defined Determination Routines for Loc. Sub. TPS
EXIT_SAPLV56I_010 IDOC TPSSHT01: Modification of IDOC Transportation Segments
EXIT_SAPLV56I_011 IDOC TPSSHT01: Modification of Transportation Tables, New Tables Proc.
EXIT_SAPLV56I_012 IDOC TPSSHT01: Save New Tables
EXIT_SAPLV56I_020 Modification of IDOC Control Record in SD-TPS Interface
IMPORTING Parameters details for IDOC_OUTPUT_CFPREQ
DELIVERY -
Data type: LIKP-VBELNOptional: No
Call by Reference: No ( called with pass by value option)
ACTION_CODE -
Data type: E3TPACC-ACTCDOptional: Yes
Call by Reference: No ( called with pass by value option)
CARRIER - Number of Forwarding Agent
Data type: VTSPLS-TDLNROptional: Yes
Call by Reference: No ( called with pass by value option)
SHIPPPT - Transportation planning point
Data type: VTCFPP-TPLSTOptional: Yes
Call by Reference: No ( called with pass by value option)
SHIPTYP - Transport Type
Data type: VTCFPP-SHTYPOptional: Yes
Call by Reference: No ( called with pass by value option)
TXTID1 - Delivery Header Text ID for Freight Planning Transfer
Data type: VTCFPP-CFGTX1Optional: Yes
Call by Reference: No ( called with pass by value option)
TXTID2 - Delivery Header Text ID for Freight Planning Transfer
Data type: VTCFPP-CFGTX2Optional: Yes
Call by Reference: No ( called with pass by value option)
TXTID3 - Delivery Header Text ID for Freight Planning Transfer
Data type: VTCFPP-CFGTX3Optional: Yes
Call by Reference: No ( called with pass by value option)
OUTPUTTYPE - Condition Type
Data type: VTDSTC-KSCHLOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_SHIP_PLAN_PNT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IDOC_NOT_TO_SEND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IDOC_SETUP_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_SHIP_PLAN_PNT -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for IDOC_OUTPUT_CFPREQ 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_delivery | TYPE LIKP-VBELN, " | |||
| lv_no_ship_plan_pnt | TYPE LIKP, " | |||
| lv_action_code | TYPE E3TPACC-ACTCD, " | |||
| lv_idoc_not_to_send | TYPE E3TPACC, " | |||
| lv_carrier | TYPE VTSPLS-TDLNR, " | |||
| lv_idoc_setup_failed | TYPE VTSPLS, " | |||
| lv_shipppt | TYPE VTCFPP-TPLST, " | |||
| lv_wrong_ship_plan_pnt | TYPE VTCFPP, " | |||
| lv_shiptyp | TYPE VTCFPP-SHTYP, " | |||
| lv_txtid1 | TYPE VTCFPP-CFGTX1, " | |||
| lv_txtid2 | TYPE VTCFPP-CFGTX2, " | |||
| lv_txtid3 | TYPE VTCFPP-CFGTX3, " | |||
| lv_outputtype | TYPE VTDSTC-KSCHL. " |
|   CALL FUNCTION 'IDOC_OUTPUT_CFPREQ' "Freight planning request to forwarding agent |
| EXPORTING | ||
| DELIVERY | = lv_delivery | |
| ACTION_CODE | = lv_action_code | |
| CARRIER | = lv_carrier | |
| SHIPPPT | = lv_shipppt | |
| SHIPTYP | = lv_shiptyp | |
| TXTID1 | = lv_txtid1 | |
| TXTID2 | = lv_txtid2 | |
| TXTID3 | = lv_txtid3 | |
| OUTPUTTYPE | = lv_outputtype | |
| EXCEPTIONS | ||
| NO_SHIP_PLAN_PNT = 1 | ||
| IDOC_NOT_TO_SEND = 2 | ||
| IDOC_SETUP_FAILED = 3 | ||
| WRONG_SHIP_PLAN_PNT = 4 | ||
| . " IDOC_OUTPUT_CFPREQ | ||
ABAP code using 7.40 inline data declarations to call FM IDOC_OUTPUT_CFPREQ
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 VBELN FROM LIKP INTO @DATA(ld_delivery). | ||||
| "SELECT single ACTCD FROM E3TPACC INTO @DATA(ld_action_code). | ||||
| "SELECT single TDLNR FROM VTSPLS INTO @DATA(ld_carrier). | ||||
| "SELECT single TPLST FROM VTCFPP INTO @DATA(ld_shipppt). | ||||
| "SELECT single SHTYP FROM VTCFPP INTO @DATA(ld_shiptyp). | ||||
| "SELECT single CFGTX1 FROM VTCFPP INTO @DATA(ld_txtid1). | ||||
| "SELECT single CFGTX2 FROM VTCFPP INTO @DATA(ld_txtid2). | ||||
| "SELECT single CFGTX3 FROM VTCFPP INTO @DATA(ld_txtid3). | ||||
| "SELECT single KSCHL FROM VTDSTC INTO @DATA(ld_outputtype). | ||||
Search for further information about these or an SAP related objects