SAP TB_DEV_PAYER_CHECK Function Module for Check and Determine Payer and Alternative Payer
TB_DEV_PAYER_CHECK is a standard tb dev payer 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 Check and Determine Payer and Alternative Payer 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 dev payer check FM, simply by entering the name TB_DEV_PAYER_CHECK 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_DEV_PAYER_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 'TB_DEV_PAYER_CHECK'"Check and Determine Payer and Alternative Payer.
EXPORTING
BUKRS = "Company Code
PAYER = "Payer/ee
* ZGP = ' ' "
* I_XMEMORY = ' ' "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* I_XWA = ' ' "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
IMPORTING
DEV_PAYER = "abweichender Regulierer
DEV_PAYER_CUSTOMER = "Debitornummer des abweichenden Regulierers
MSG_ID = "Message ID
MSG_NR = "Meldungsnummer: kein abw. Regulierer vorhanden
PAYER_CUSTOMER = "Debitornummer Regulierer
XDEV_PAYER = "Name of Alternative Payer
XPAYER = "Payer Name
EXCEPTIONS
NO_DEV_PAYER = 1 PAYER_NO_CUSTOMER = 2 PARTNER_NOT_FOUND = 3
IMPORTING Parameters details for TB_DEV_PAYER_CHECK
BUKRS - Company Code
Data type: T001-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
PAYER - Payer/ee
Data type: BP000-PARTNROptional: No
Call by Reference: No ( called with pass by value option)
ZGP -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_XMEMORY - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_XWA - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for TB_DEV_PAYER_CHECK
DEV_PAYER - abweichender Regulierer
Data type: BP000-PARTNROptional: No
Call by Reference: No ( called with pass by value option)
DEV_PAYER_CUSTOMER - Debitornummer des abweichenden Regulierers
Data type: KNA1-KUNNROptional: No
Call by Reference: No ( called with pass by value option)
MSG_ID - Message ID
Data type: SY-MSGIDOptional: No
Call by Reference: No ( called with pass by value option)
MSG_NR - Meldungsnummer: kein abw. Regulierer vorhanden
Data type: SY-MSGIDOptional: No
Call by Reference: No ( called with pass by value option)
PAYER_CUSTOMER - Debitornummer Regulierer
Data type: KNA1-KUNNROptional: No
Call by Reference: No ( called with pass by value option)
XDEV_PAYER - Name of Alternative Payer
Data type: BP000-NAME1Optional: No
Call by Reference: No ( called with pass by value option)
XPAYER - Payer Name
Data type: BP000-NAME1Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_DEV_PAYER - kein abweichender Regulierer vorhanden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PAYER_NO_CUSTOMER - Partner nicht als Debitor vorhanden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARTNER_NOT_FOUND - Partnernummer nicht vorhanden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TB_DEV_PAYER_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_bukrs | TYPE T001-BUKRS, " | |||
| lv_dev_payer | TYPE BP000-PARTNR, " | |||
| lv_no_dev_payer | TYPE BP000, " | |||
| lv_payer | TYPE BP000-PARTNR, " | |||
| lv_payer_no_customer | TYPE BP000, " | |||
| lv_dev_payer_customer | TYPE KNA1-KUNNR, " | |||
| lv_zgp | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_msg_id | TYPE SY-MSGID, " | |||
| lv_partner_not_found | TYPE SY, " | |||
| lv_msg_nr | TYPE SY-MSGID, " | |||
| lv_i_xmemory | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_i_xwa | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_payer_customer | TYPE KNA1-KUNNR, " | |||
| lv_xdev_payer | TYPE BP000-NAME1, " | |||
| lv_xpayer | TYPE BP000-NAME1. " |
|   CALL FUNCTION 'TB_DEV_PAYER_CHECK' "Check and Determine Payer and Alternative Payer |
| EXPORTING | ||
| BUKRS | = lv_bukrs | |
| PAYER | = lv_payer | |
| ZGP | = lv_zgp | |
| I_XMEMORY | = lv_i_xmemory | |
| I_XWA | = lv_i_xwa | |
| IMPORTING | ||
| DEV_PAYER | = lv_dev_payer | |
| DEV_PAYER_CUSTOMER | = lv_dev_payer_customer | |
| MSG_ID | = lv_msg_id | |
| MSG_NR | = lv_msg_nr | |
| PAYER_CUSTOMER | = lv_payer_customer | |
| XDEV_PAYER | = lv_xdev_payer | |
| XPAYER | = lv_xpayer | |
| EXCEPTIONS | ||
| NO_DEV_PAYER = 1 | ||
| PAYER_NO_CUSTOMER = 2 | ||
| PARTNER_NOT_FOUND = 3 | ||
| . " TB_DEV_PAYER_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM TB_DEV_PAYER_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.| "SELECT single BUKRS FROM T001 INTO @DATA(ld_bukrs). | ||||
| "SELECT single PARTNR FROM BP000 INTO @DATA(ld_dev_payer). | ||||
| "SELECT single PARTNR FROM BP000 INTO @DATA(ld_payer). | ||||
| "SELECT single KUNNR FROM KNA1 INTO @DATA(ld_dev_payer_customer). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_zgp). | ||||
| DATA(ld_zgp) | = ' '. | |||
| "SELECT single MSGID FROM SY INTO @DATA(ld_msg_id). | ||||
| "SELECT single MSGID FROM SY INTO @DATA(ld_msg_nr). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xmemory). | ||||
| DATA(ld_i_xmemory) | = ' '. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xwa). | ||||
| DATA(ld_i_xwa) | = ' '. | |||
| "SELECT single KUNNR FROM KNA1 INTO @DATA(ld_payer_customer). | ||||
| "SELECT single NAME1 FROM BP000 INTO @DATA(ld_xdev_payer). | ||||
| "SELECT single NAME1 FROM BP000 INTO @DATA(ld_xpayer). | ||||
Search for further information about these or an SAP related objects