SAP VALID_BTYPE Function Module for Check of the payroll category and customers or vendors with venture o

Search SAP Function Modules

VALID_BTYPE is a standard valid btype SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check of the payroll category and customers or vendors with venture o 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 valid btype FM, simply by entering the name VALID_BTYPE into the relevant SAP transaction such as SE37 or SE38.

Function Group: GJA1
Program Name: SAPLGJA1
Main Program: SAPLGJA1
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VALID_BTYPE 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 'VALID_BTYPE'"Check of the payroll category and customers or vendors with venture o
  EXPORTING
*  I_BLDAT = SY-DATUM "
   I_VNAME =  "
   I_BSCHL =  "
   I_BTYPE =  "
*  I_BUKRS = ' ' "
   I_EGRUP =  "
   I_KOART =  "
   I_KUNNR =  "
   I_LIFNR =  "
   I_UMSKZ =  "

EXCEPTIONS
   NO_ENTRY = 1 

.

IMPORTING Parameters details for VALID_BTYPE

I_BLDAT -

Data type: BKPF-BLDAT
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_VNAME -

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

I_BSCHL -

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

I_BTYPE -

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

I_BUKRS -

Data type: BSEG-BUKRS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_EGRUP -

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

I_KOART -

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

I_KUNNR -

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

I_LIFNR -

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

I_UMSKZ -

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

EXCEPTIONS details

NO_ENTRY -

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

Copy and paste ABAP code example for VALID_BTYPE 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.

ABAP code using 7.40 inline data declarations to call FM VALID_BTYPE

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