FI_TAX_SERVICES_CALCULATE

[chvreddy67]

Hi ABAPer's

We are calling FM - FI_TAX_SERVICES_CALCULATE in UPDATE TASK of a BADI to get the ACCOUNTTAX lines and it is giving short dump saying "Statement "CALL_SCREEN" is not allowed in this form." did debug and yes it is coming across CALL SCREEN statement and leading to short dump in case the same FM called from normal task then it works great. If anyone came across such please throw some light any alternatives to FM - FI_TAX_SERVICES_CALCULATE ?

Regards,

Venkat Channa

[abo]

The fm itself is most likely not the source of your trouble. Chances are, there is a custom enhancement somewhere that uses CALL SCREEN without checking that there is indeed a GUI connected.

[chvreddy67]

Thank You Andrea for the response CALL SCREEN is getting called in the standard SAP code no custom exists.

[chvreddy67]

capture.jpg

[RaymondGiuseppi]

Consider using method FI_TAX_SERVICES=>CALCULATE

Also you wrote "in UPDATE TASK" but in your Abap stack, there is a BAPI call, that shoudn't be possible/allowed, could you describe your actual process?

[chvreddy67]

Hello Raymond..Using VL02N we are doing PGI and during this process after creating material document we need to create corresponding accounting document. So BADI MB_DOCUMENT_BADI is implemented and in this we are writing our logic in method IF_EX_MB_DOCUMENT_BADI~MB_DOCUMENT_UPDATE. So before calling BAPI_ACC_DOCUMENT_POST we are calling FM FI_TAX_SERVICES_CALCULATE to populate accounttax internal table populate and then pass the same into BAPI_ACC_DOCUMENT_POST as per SAP note 2070697. And as you suggested to use FI_TAX_SERVICES=>CALCULATE actually FM FI_TAX_SERVICES_CALCULATE will internally call this FI_TAX_SERVICES=>CALCULATE.capture.jpg

[chvreddy67]

Here is the solution we have to use below SAP support link and it worked perfectly to get the account tax data. We have to make data declarations are global.

https://help.sap.com/doc/abapdocu_751_index_htm/7.51/en-US/abapcall_function_starting.htm#!ABAP_ADDI...

data P_task(32) type c

MOVE '0000000001' TO p_task.
CALL FUNCTION 'FI_TAX_SERVICES_CALCULATE'
STARTING NEW TASK p_task
DESTINATION 'NONE'
CALLING acct_data ON END OF TASK
EXPORTING
documentheader = gs_bapi_header
CHANGING
currencyamount = gt_bapi_currency_amnt
accountgl = gt_bapi_gl_items
accounttax = gt_bapi_account_taxes
return = gt_return_tax.
WAIT UP TO 1 SECONDS.

METHOD acct_data.
RECEIVE RESULTS FROM FUNCTION 'FI_TAX_SERVICES_CALCULATE'
IMPORTING
documentheader = gs_bapi_header
CHANGING
currencyamount = gt_bapi_currency_amnt
accountgl = gt_bapi_gl_items
accounttax = gt_bapi_account_taxes
return = gt_return_tax.
ENDMETHOD.

[hagit]

@raymond_giuseppi

I called method fi_tax_services=>calculate as you suggested.

The behavior of the method and FB60 is different for the following scenario:

1. There is a vendor line without tax code (MWSKZ is initial)
2. There is a GL line without tax code (MWSKZ is initial)
3. 'calculate tax' is checked

The method updates the tax code to a value that means no tax.

FB60 raises a blocking  error: 'G/L account xxxxxx requires a valid tax code'

 How can I force the method to behave as standard?

The call to the method is:

  CALL METHOD fi_tax_services=>calculate
    EXPORTING
      documentheader    = gs_doc_header
      accountpayable    = gt_accountpayable
      accountreceivable = gt_accountreceivable
*     distribute_deduct = SPACE
*     taxamount         =
    IMPORTING
      return_code       = lv_subrc
    CHANGING
      currencyamount    = gt_currencyamount
      accountgl         = gt_accountgl
      accounttax        = gt_accounttax
      return            = lt_return.

Thankyou in advance

Hagit