SAP FMCA_TXOBLGN_LVYTP_BY_BP Function Module for









FMCA_TXOBLGN_LVYTP_BY_BP is a standard fmca txoblgn lvytp by bp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fmca txoblgn lvytp by bp FM, simply by entering the name FMCA_TXOBLGN_LVYTP_BY_BP into the relevant SAP transaction such as SE37 or SE38.

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



Function FMCA_TXOBLGN_LVYTP_BY_BP 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 'FMCA_TXOBLGN_LVYTP_BY_BP'"
EXPORTING
* IV_PARTNER = "Business Partner Number
* IV_PSOBKEY = "Identification Key for Contract Object

IMPORTING
ET_LEVYTYPE = "Table of FMCA_TXOBLGN_LEVY_TYPE

EXCEPTIONS
ERR_FACTS_RETRIEVAL = 1 ERR_CREATE_TAXOBLIGATION_KEY = 2 ERR_NO_DATA_FOUND = 3
.



IMPORTING Parameters details for FMCA_TXOBLGN_LVYTP_BY_BP

IV_PARTNER - Business Partner Number

Data type: GPART_KK
Optional: Yes
Call by Reference: Yes

IV_PSOBKEY - Identification Key for Contract Object

Data type: PSOBKEY_PS
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FMCA_TXOBLGN_LVYTP_BY_BP

ET_LEVYTYPE - Table of FMCA_TXOBLGN_LEVY_TYPE

Data type: FMCA_TXOBLGN_LEVY_TYPE_T
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERR_FACTS_RETRIEVAL -

Data type:
Optional: No
Call by Reference: Yes

ERR_CREATE_TAXOBLIGATION_KEY -

Data type:
Optional: No
Call by Reference: Yes

ERR_NO_DATA_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FMCA_TXOBLGN_LVYTP_BY_BP 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_iv_partner  TYPE GPART_KK, "   
lv_et_levytype  TYPE FMCA_TXOBLGN_LEVY_TYPE_T, "   
lv_err_facts_retrieval  TYPE FMCA_TXOBLGN_LEVY_TYPE_T, "   
lv_iv_psobkey  TYPE PSOBKEY_PS, "   
lv_err_create_taxobligation_key  TYPE PSOBKEY_PS, "   
lv_err_no_data_found  TYPE PSOBKEY_PS. "   

  CALL FUNCTION 'FMCA_TXOBLGN_LVYTP_BY_BP'  "
    EXPORTING
         IV_PARTNER = lv_iv_partner
         IV_PSOBKEY = lv_iv_psobkey
    IMPORTING
         ET_LEVYTYPE = lv_et_levytype
    EXCEPTIONS
        ERR_FACTS_RETRIEVAL = 1
        ERR_CREATE_TAXOBLIGATION_KEY = 2
        ERR_NO_DATA_FOUND = 3
. " FMCA_TXOBLGN_LVYTP_BY_BP




ABAP code using 7.40 inline data declarations to call FM FMCA_TXOBLGN_LVYTP_BY_BP

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!