SAP BAPI_CAR_PRVD_ROUTING Function Module for Make Express Delivery Company's Routing Info Available









BAPI_CAR_PRVD_ROUTING is a standard bapi car prvd routing SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Make Express Delivery Company's Routing Info Available 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 bapi car prvd routing FM, simply by entering the name BAPI_CAR_PRVD_ROUTING into the relevant SAP transaction such as SE37 or SE38.

Function Group: VVTR
Program Name: SAPLVVTR
Main Program: SAPLVVTR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_CAR_PRVD_ROUTING 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 'BAPI_CAR_PRVD_ROUTING'"Make Express Delivery Company's Routing Info Available
  EXPORTING
   IDENTIFICATION =  "ID of User who Called up Transaction
*  LAST_UPDATE =  "Last Update of Route Info Data
*  TEST_FLAG =  "Test Mode

 IMPORTING
   NEXT_UPDATE =  "Next Update of Route Info Data

TABLES
*  ROUTING_POST_CODE =  "Routing Information per Postal Code
*  ROUTING_POST_CODE_RANGE =  "Routing Information per Postal Code
*  ROUTING_CITY =  "Routing Information per Postal Code
   BAPI_RETURN =  "Return parameter
.



IMPORTING Parameters details for BAPI_CAR_PRVD_ROUTING

IDENTIFICATION - ID of User who Called up Transaction

Data type: BAPICARSHPACCT
Optional: No
Call by Reference: No ( called with pass by value option)

LAST_UPDATE - Last Update of Route Info Data

Data type: VXSITD-ROUTELDAT
Optional: Yes
Call by Reference: No ( called with pass by value option)

TEST_FLAG - Test Mode

Data type: TESTFLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_CAR_PRVD_ROUTING

NEXT_UPDATE - Next Update of Route Info Data

Data type: VXSITD-ROUTENDAT
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_CAR_PRVD_ROUTING

ROUTING_POST_CODE - Routing Information per Postal Code

Data type: BAPICARRT
Optional: Yes
Call by Reference: Yes

ROUTING_POST_CODE_RANGE - Routing Information per Postal Code

Data type: BAPICARRTR
Optional: Yes
Call by Reference: Yes

ROUTING_CITY - Routing Information per Postal Code

Data type: BAPICARRTC
Optional: Yes
Call by Reference: Yes

BAPI_RETURN - Return parameter

Data type: BAPIRET2
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BAPI_CAR_PRVD_ROUTING 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_next_update  TYPE VXSITD-ROUTENDAT, "   
lv_identification  TYPE BAPICARSHPACCT, "   
lt_routing_post_code  TYPE STANDARD TABLE OF BAPICARRT, "   
lv_last_update  TYPE VXSITD-ROUTELDAT, "   
lt_routing_post_code_range  TYPE STANDARD TABLE OF BAPICARRTR, "   
lv_test_flag  TYPE TESTFLAG, "   
lt_routing_city  TYPE STANDARD TABLE OF BAPICARRTC, "   
lt_bapi_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'BAPI_CAR_PRVD_ROUTING'  "Make Express Delivery Company's Routing Info Available
    EXPORTING
         IDENTIFICATION = lv_identification
         LAST_UPDATE = lv_last_update
         TEST_FLAG = lv_test_flag
    IMPORTING
         NEXT_UPDATE = lv_next_update
    TABLES
         ROUTING_POST_CODE = lt_routing_post_code
         ROUTING_POST_CODE_RANGE = lt_routing_post_code_range
         ROUTING_CITY = lt_routing_city
         BAPI_RETURN = lt_bapi_return
. " BAPI_CAR_PRVD_ROUTING




ABAP code using 7.40 inline data declarations to call FM BAPI_CAR_PRVD_ROUTING

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 ROUTENDAT FROM VXSITD INTO @DATA(ld_next_update).
 
 
 
"SELECT single ROUTELDAT FROM VXSITD INTO @DATA(ld_last_update).
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!