SAP OIF_GET_LOCATION_DATA_FOR_SD Function Module for Location header data retrieval for SD modules (preload for subscreens)
OIF_GET_LOCATION_DATA_FOR_SD is a standard oif get location data for sd SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Location header data retrieval for SD modules (preload for subscreens) 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 oif get location data for sd FM, simply by entering the name OIF_GET_LOCATION_DATA_FOR_SD into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIFK
Program Name: SAPLOIFK
Main Program: SAPLOIFK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIF_GET_LOCATION_DATA_FOR_SD 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 'OIF_GET_LOCATION_DATA_FOR_SD'"Location header data retrieval for SD modules (preload for subscreens).
EXPORTING
I_OIPBL = "ID of bus. location assigned to customer
EXCEPTIONS
LOCATION_NOT_FOUND = 1 LOC_TYPE_NOT_FOUND = 2
IMPORTING Parameters details for OIF_GET_LOCATION_DATA_FOR_SD
I_OIPBL - ID of bus. location assigned to customer
Data type: OIFSPBL-PBLNROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
LOCATION_NOT_FOUND - Specified business location does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LOC_TYPE_NOT_FOUND - Specified business location type does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIF_GET_LOCATION_DATA_FOR_SD 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_i_oipbl | TYPE OIFSPBL-PBLNR, " | |||
| lv_location_not_found | TYPE OIFSPBL, " | |||
| lv_loc_type_not_found | TYPE OIFSPBL. " |
|   CALL FUNCTION 'OIF_GET_LOCATION_DATA_FOR_SD' "Location header data retrieval for SD modules (preload for subscreens) |
| EXPORTING | ||
| I_OIPBL | = lv_i_oipbl | |
| EXCEPTIONS | ||
| LOCATION_NOT_FOUND = 1 | ||
| LOC_TYPE_NOT_FOUND = 2 | ||
| . " OIF_GET_LOCATION_DATA_FOR_SD | ||
ABAP code using 7.40 inline data declarations to call FM OIF_GET_LOCATION_DATA_FOR_SD
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 PBLNR FROM OIFSPBL INTO @DATA(ld_i_oipbl). | ||||
Search for further information about these or an SAP related objects