SAP BOS_SET_ORIGIN Function Module for Set Origin of Call for the Service Package
BOS_SET_ORIGIN is a standard bos set origin SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set Origin of Call for the Service Package 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 bos set origin FM, simply by entering the name BOS_SET_ORIGIN into the relevant SAP transaction such as SE37 or SE38.
Function Group: AD_BOS_SD
Program Name: SAPLAD_BOS_SD
Main Program: SAPLAD_BOS_SD
Appliation area:
Release date: 25-Jun-2001
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BOS_SET_ORIGIN 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 'BOS_SET_ORIGIN'"Set Origin of Call for the Service Package.
EXPORTING
I_VBTYP = "SD document category
IMPORTING
E_ORIGIN = "Origin of Call
EXCEPTIONS
EMPTY_ORIGIN = 1
IMPORTING Parameters details for BOS_SET_ORIGIN
I_VBTYP - SD document category
Data type: VBAK-VBTYPOptional: No
Call by Reference: Yes
EXPORTING Parameters details for BOS_SET_ORIGIN
E_ORIGIN - Origin of Call
Data type:Optional: No
Call by Reference: Yes
EXCEPTIONS details
EMPTY_ORIGIN - Document category for Services are not permitted
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BOS_SET_ORIGIN 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_vbtyp | TYPE VBAK-VBTYP, " | |||
| lv_e_origin | TYPE VBAK, " | |||
| lv_empty_origin | TYPE VBAK. " |
|   CALL FUNCTION 'BOS_SET_ORIGIN' "Set Origin of Call for the Service Package |
| EXPORTING | ||
| I_VBTYP | = lv_i_vbtyp | |
| IMPORTING | ||
| E_ORIGIN | = lv_e_origin | |
| EXCEPTIONS | ||
| EMPTY_ORIGIN = 1 | ||
| . " BOS_SET_ORIGIN | ||
ABAP code using 7.40 inline data declarations to call FM BOS_SET_ORIGIN
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 VBTYP FROM VBAK INTO @DATA(ld_i_vbtyp). | ||||
Search for further information about these or an SAP related objects