SAP TB_PAYMENT_REQUEST_BUILD_GRP2 Function Module for Structure of Grouping Field for Payment Request (from EA 2.0)









TB_PAYMENT_REQUEST_BUILD_GRP2 is a standard tb payment request build grp2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Structure of Grouping Field for Payment Request (from EA 2.0) 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 request build grp2 FM, simply by entering the name TB_PAYMENT_REQUEST_BUILD_GRP2 into the relevant SAP transaction such as SE37 or SE38.

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



Function TB_PAYMENT_REQUEST_BUILD_GRP2 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_REQUEST_BUILD_GRP2'"Structure of Grouping Field for Payment Request (from EA 2.0)
  EXPORTING
*  I_RFHA =  "Finanzgeschäft oder Vertrag
*  I_SSIGN =  "Direction of Flow
*  I_PAYGR =  "
*  I_PAY_ONLY =  "payment without posting
*  I_SECURITY_ID =  "Security ID Number
*  I_RANTYP =  "Anwendung / Vertragsart
*  I_SANLF =  "Product Category
   I_SGSART =  "Product Type
   I_SPAYRQ =  "Flag: Zahlungsanordnung erzeugen
   I_PRKEY =  "Key number for payment request
   I_SPRGRD =  "Determine Grouping Definition
*  I_SCSPAY =  "Flag: gleiche Richtung für gemeinsame Regulierung erforderlich?

 IMPORTING
   E_PAYGR =  "Grouping Field

EXCEPTIONS
   WRONG_CALL = 1    ERROR = 2
.



IMPORTING Parameters details for TB_PAYMENT_REQUEST_BUILD_GRP2

I_RFHA - Finanzgeschäft oder Vertrag

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

I_SSIGN - Direction of Flow

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

I_PAYGR -

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

I_PAY_ONLY - payment without posting

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

I_SECURITY_ID - Security ID Number

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

I_RANTYP - Anwendung / Vertragsart

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

I_SANLF - Product Category

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

I_SGSART - Product Type

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

I_SPAYRQ - Flag: Zahlungsanordnung erzeugen

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

I_PRKEY - Key number for payment request

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

I_SPRGRD - Determine Grouping Definition

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

I_SCSPAY - Flag: gleiche Richtung für gemeinsame Regulierung erforderlich?

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

EXPORTING Parameters details for TB_PAYMENT_REQUEST_BUILD_GRP2

E_PAYGR - Grouping Field

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

EXCEPTIONS details

WRONG_CALL - Bitte die Parameter überprüfen

Data type:
Optional: No
Call by Reference: Yes

ERROR - Siehe Fehlermeldung

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TB_PAYMENT_REQUEST_BUILD_GRP2 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_rfha  TYPE TB_RFHA, "   
lv_e_paygr  TYPE PAYGR, "   
lv_wrong_call  TYPE PAYGR, "   
lv_i_ssign  TYPE TB_SSIGN, "   
lv_i_paygr  TYPE PAYGR, "   
lv_i_pay_only  TYPE XFELD, "   
lv_error  TYPE XFELD, "   
lv_i_security_id  TYPE VVRANLW, "   
lv_i_rantyp  TYPE RANTYP, "   
lv_i_sanlf  TYPE SANLF, "   
lv_i_sgsart  TYPE VVSART, "   
lv_i_spayrq  TYPE TB_SPAYRQK, "   
lv_i_prkey  TYPE PRQ_KEYNO, "   
lv_i_sprgrd  TYPE TB_SPRGRD, "   
lv_i_scspay  TYPE TB_SCSPAY. "   

  CALL FUNCTION 'TB_PAYMENT_REQUEST_BUILD_GRP2'  "Structure of Grouping Field for Payment Request (from EA 2.0)
    EXPORTING
         I_RFHA = lv_i_rfha
         I_SSIGN = lv_i_ssign
         I_PAYGR = lv_i_paygr
         I_PAY_ONLY = lv_i_pay_only
         I_SECURITY_ID = lv_i_security_id
         I_RANTYP = lv_i_rantyp
         I_SANLF = lv_i_sanlf
         I_SGSART = lv_i_sgsart
         I_SPAYRQ = lv_i_spayrq
         I_PRKEY = lv_i_prkey
         I_SPRGRD = lv_i_sprgrd
         I_SCSPAY = lv_i_scspay
    IMPORTING
         E_PAYGR = lv_e_paygr
    EXCEPTIONS
        WRONG_CALL = 1
        ERROR = 2
. " TB_PAYMENT_REQUEST_BUILD_GRP2




ABAP code using 7.40 inline data declarations to call FM TB_PAYMENT_REQUEST_BUILD_GRP2

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!