SAP J_1BSA_COMPONENT_CHECK Function Module for Component Check (South America)









J_1BSA_COMPONENT_CHECK is a standard j 1bsa component 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 Component Check (South America) 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 j 1bsa component check FM, simply by entering the name J_1BSA_COMPONENT_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: FLOC
Program Name: SAPLFLOC
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function J_1BSA_COMPONENT_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 'J_1BSA_COMPONENT_CHECK'"Component Check (South America)
EXPORTING
* COMPONENT = "Component to be checked

EXCEPTIONS
COMPONENT_NOT_INSTALLED = 1
.



IMPORTING Parameters details for J_1BSA_COMPONENT_CHECK

COMPONENT - Component to be checked

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

EXCEPTIONS details

COMPONENT_NOT_INSTALLED - Component not installed

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

Copy and paste ABAP code example for J_1BSA_COMPONENT_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_component  TYPE STRING, "   
lv_component_not_installed  TYPE STRING. "   

  CALL FUNCTION 'J_1BSA_COMPONENT_CHECK'  "Component Check (South America)
    EXPORTING
         COMPONENT = lv_component
    EXCEPTIONS
        COMPONENT_NOT_INSTALLED = 1
. " J_1BSA_COMPONENT_CHECK




ABAP code using 7.40 inline data declarations to call FM J_1BSA_COMPONENT_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



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!