SAP CIF_SHP_DATA_CHECK Function Module for NOTRANSL: Mappinng von APO Transporten zu LES Transporten
CIF_SHP_DATA_CHECK is a standard cif shp data check 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: Mappinng von APO Transporten zu LES Transporten 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 cif shp data check FM, simply by entering the name CIF_SHP_DATA_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: LE_TRA_R3_TO_APO
Program Name: SAPLLE_TRA_R3_TO_APO
Main Program: SAPLLE_TRA_R3_TO_APO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CIF_SHP_DATA_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 'CIF_SHP_DATA_CHECK'"NOTRANSL: Mappinng von APO Transporten zu LES Transporten.
EXPORTING
IS_SHIPMENT = "
IMPORTING
EV_SHP_OK = "
TABLES
ET_APOSHP_HDR = "VS: Communication Layer: Shipment Header Data
ET_APOSHP_HDR_DLINE = "VS: Communication Layer: Shipment Deadlines Header Data
ET_APOSHP_ITM = "VS: Communication Layer: Shipment Item Data
ET_APOSHP_STG = "VS: Communication Layer: Shipment Deadline Stages
ET_APOSHP_STG_DLINE = "VS: Communication Layer: Shipment Deadline Stages
ET_APOSHP_IOS = "VS Communication Layer: Deliveries in Stages
ET_APOSHP_VEH = "VS: Communication Layer: Vehicle Data as HU
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_SAPLLE_TRA_R3_TO_APO_001 User Exit for Shipments R/3 -> APO
EXIT_SAPLLE_TRA_R3_TO_APO_002 User Exit for Shipments To Be Deleted from R/3 -> APO
IMPORTING Parameters details for CIF_SHP_DATA_CHECK
IS_SHIPMENT -
Data type: CXSHIPMENTOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CIF_SHP_DATA_CHECK
EV_SHP_OK -
Data type: COptional: No
Call by Reference: Yes
TABLES Parameters details for CIF_SHP_DATA_CHECK
ET_APOSHP_HDR - VS: Communication Layer: Shipment Header Data
Data type: VSRSHP_HDROptional: No
Call by Reference: No ( called with pass by value option)
ET_APOSHP_HDR_DLINE - VS: Communication Layer: Shipment Deadlines Header Data
Data type: VSRSHP_HDDOptional: No
Call by Reference: No ( called with pass by value option)
ET_APOSHP_ITM - VS: Communication Layer: Shipment Item Data
Data type: VSRSHP_ITMOptional: No
Call by Reference: No ( called with pass by value option)
ET_APOSHP_STG - VS: Communication Layer: Shipment Deadline Stages
Data type: VSRSHP_STGOptional: No
Call by Reference: No ( called with pass by value option)
ET_APOSHP_STG_DLINE - VS: Communication Layer: Shipment Deadline Stages
Data type: VSRSHP_STDOptional: No
Call by Reference: No ( called with pass by value option)
ET_APOSHP_IOS - VS Communication Layer: Deliveries in Stages
Data type: VSRSHP_IOSOptional: No
Call by Reference: No ( called with pass by value option)
ET_APOSHP_VEH - VS: Communication Layer: Vehicle Data as HU
Data type: VSRSHP_VEHOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CIF_SHP_DATA_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_ev_shp_ok | TYPE C, " | |||
| lv_is_shipment | TYPE CXSHIPMENT, " | |||
| lt_et_aposhp_hdr | TYPE STANDARD TABLE OF VSRSHP_HDR, " | |||
| lt_et_aposhp_hdr_dline | TYPE STANDARD TABLE OF VSRSHP_HDD, " | |||
| lt_et_aposhp_itm | TYPE STANDARD TABLE OF VSRSHP_ITM, " | |||
| lt_et_aposhp_stg | TYPE STANDARD TABLE OF VSRSHP_STG, " | |||
| lt_et_aposhp_stg_dline | TYPE STANDARD TABLE OF VSRSHP_STD, " | |||
| lt_et_aposhp_ios | TYPE STANDARD TABLE OF VSRSHP_IOS, " | |||
| lt_et_aposhp_veh | TYPE STANDARD TABLE OF VSRSHP_VEH. " |
|   CALL FUNCTION 'CIF_SHP_DATA_CHECK' "NOTRANSL: Mappinng von APO Transporten zu LES Transporten |
| EXPORTING | ||
| IS_SHIPMENT | = lv_is_shipment | |
| IMPORTING | ||
| EV_SHP_OK | = lv_ev_shp_ok | |
| TABLES | ||
| ET_APOSHP_HDR | = lt_et_aposhp_hdr | |
| ET_APOSHP_HDR_DLINE | = lt_et_aposhp_hdr_dline | |
| ET_APOSHP_ITM | = lt_et_aposhp_itm | |
| ET_APOSHP_STG | = lt_et_aposhp_stg | |
| ET_APOSHP_STG_DLINE | = lt_et_aposhp_stg_dline | |
| ET_APOSHP_IOS | = lt_et_aposhp_ios | |
| ET_APOSHP_VEH | = lt_et_aposhp_veh | |
| . " CIF_SHP_DATA_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM CIF_SHP_DATA_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