SAP BORRT_SHIPMENT_DETERMINE Function Module for NOTRANSL: Regeltoure: Transporte ermitteln
BORRT_SHIPMENT_DETERMINE is a standard borrt shipment determine 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: Regeltoure: Transporte ermitteln 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 borrt shipment determine FM, simply by entering the name BORRT_SHIPMENT_DETERMINE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BORRT
Program Name: SAPLBORRT
Main Program: SAPLBORRT
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BORRT_SHIPMENT_DETERMINE 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 'BORRT_SHIPMENT_DETERMINE'"NOTRANSL: Regeltoure: Transporte ermitteln.
EXPORTING
IF_DATE = "Delivery Date
* IT_SCHEDULE = "
IMPORTING
ET_SHIPMENT = "
IMPORTING Parameters details for BORRT_SHIPMENT_DETERMINE
IF_DATE - Delivery Date
Data type: LIKP-LFDATOptional: No
Call by Reference: No ( called with pass by value option)
IT_SCHEDULE -
Data type: BORRT_T_SCHEDULEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BORRT_SHIPMENT_DETERMINE
ET_SHIPMENT -
Data type: BORRT_T_SHIPMENTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BORRT_SHIPMENT_DETERMINE 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_if_date | TYPE LIKP-LFDAT, " | |||
| lv_et_shipment | TYPE BORRT_T_SHIPMENT, " | |||
| lv_it_schedule | TYPE BORRT_T_SCHEDULE. " |
|   CALL FUNCTION 'BORRT_SHIPMENT_DETERMINE' "NOTRANSL: Regeltoure: Transporte ermitteln |
| EXPORTING | ||
| IF_DATE | = lv_if_date | |
| IT_SCHEDULE | = lv_it_schedule | |
| IMPORTING | ||
| ET_SHIPMENT | = lv_et_shipment | |
| . " BORRT_SHIPMENT_DETERMINE | ||
ABAP code using 7.40 inline data declarations to call FM BORRT_SHIPMENT_DETERMINE
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 LFDAT FROM LIKP INTO @DATA(ld_if_date). | ||||
Search for further information about these or an SAP related objects