SAP TB_PAYMENT_ALLOCATION Function Module for Define All Assignments to Payment Details









TB_PAYMENT_ALLOCATION is a standard tb payment allocation SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Define All Assignments to Payment Details 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 tb payment allocation FM, simply by entering the name TB_PAYMENT_ALLOCATION into the relevant SAP transaction such as SE37 or SE38.

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



Function TB_PAYMENT_ALLOCATION 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 'TB_PAYMENT_ALLOCATION'"Define All Assignments to Payment Details
EXPORTING
BUKRS = "Company Code
PARTNR = "Partner
WAERS = "Currency
ZAHLVID = "Payment Details

EXCEPTIONS
ALLOCATION_FOUND = 1
.



IMPORTING Parameters details for TB_PAYMENT_ALLOCATION

BUKRS - Company Code

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

PARTNR - Partner

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

WAERS - Currency

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

ZAHLVID - Payment Details

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

EXCEPTIONS details

ALLOCATION_FOUND - Assignment Exists

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

Copy and paste ABAP code example for TB_PAYMENT_ALLOCATION 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_bukrs  TYPE VTBSTC1-BUKRS, "   
lv_allocation_found  TYPE VTBSTC1, "   
lv_partnr  TYPE VTBSTC1-PARTNR, "   
lv_waers  TYPE VTBSTC1-WAERS, "   
lv_zahlvid  TYPE VTBSTC1-ZAHLVID. "   

  CALL FUNCTION 'TB_PAYMENT_ALLOCATION'  "Define All Assignments to Payment Details
    EXPORTING
         BUKRS = lv_bukrs
         PARTNR = lv_partnr
         WAERS = lv_waers
         ZAHLVID = lv_zahlvid
    EXCEPTIONS
        ALLOCATION_FOUND = 1
. " TB_PAYMENT_ALLOCATION




ABAP code using 7.40 inline data declarations to call FM TB_PAYMENT_ALLOCATION

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 BUKRS FROM VTBSTC1 INTO @DATA(ld_bukrs).
 
 
"SELECT single PARTNR FROM VTBSTC1 INTO @DATA(ld_partnr).
 
"SELECT single WAERS FROM VTBSTC1 INTO @DATA(ld_waers).
 
"SELECT single ZAHLVID FROM VTBSTC1 INTO @DATA(ld_zahlvid).
 


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!