SAP RV_XVBUK_MAINTAIN_CREDIT Function Module for NOTRANSL: Statusermittlung Kopf aus Kreditsicht

Search SAP Function Modules

RV_XVBUK_MAINTAIN_CREDIT is a standard rv xvbuk maintain credit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Statusermittlung Kopf aus Kreditsicht 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 rv xvbuk maintain credit FM, simply by entering the name RV_XVBUK_MAINTAIN_CREDIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: V45P
Program Name: SAPLV45P
Main Program: SAPLV45P
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RV_XVBUK_MAINTAIN_CREDIT 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 'RV_XVBUK_MAINTAIN_CREDIT'"NOTRANSL: Statusermittlung Kopf aus Kreditsicht
  EXPORTING
   C_VBELN =  "Number of primary document of transaction
   C_VBTYP =  "Sales Document Category
*  FREIGABE = ' ' "'X' in the release mode
*  SKVBUK = ' ' "Credit status fields
*  I_VBKLA = ' ' "Original system with release and transaction control
*  NO_CHECK = ' ' "

TABLES
   FXVBUK =  "Corresponds to XVBUK (sorted)
   FYVBUK =  "Corresponds to YVBUK

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLV45P_002 User Exit: Transfer of Conditions into Cost

IMPORTING Parameters details for RV_XVBUK_MAINTAIN_CREDIT

C_VBELN - Number of primary document of transaction

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

C_VBTYP - Sales Document Category

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

FREIGABE - 'X' in the release mode

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

SKVBUK - Credit status fields

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

I_VBKLA - Original system with release and transaction control

Data type: VBAK-VBKLA
Default: SPACE
Optional: Yes
Call by Reference: Yes

NO_CHECK -

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

TABLES Parameters details for RV_XVBUK_MAINTAIN_CREDIT

FXVBUK - Corresponds to XVBUK (sorted)

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

FYVBUK - Corresponds to YVBUK

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

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

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