Anything can be done, it's just a matter of time and money...

No tax calculation function in FI/CO BAPIs – Solution

Jan19
2012 Leave a Comment Written by Pavel

Symptom (as described in SAP OSS Note 367175)

During the posting to accounting via BAPIs or IDocs you expect that analogous to posting transactions in FI the tax can be calculated. These are the following BAPIs / IDocs:

  • BAPI_ACC_INVOICE_RECEIPT_POST
  • BAPI_ACC_BILLING_POST
  • IDoc message types ACLPAY, ACLREC, ACC_INVOICE_RECEIPT, ACC_BILLING

 

Additional key words

BAPI, IDoc, FB01, FB60

Cause and prerequisites

In general the calculation of taxes does not belong to the BAPI processing function. No other line item is generated after an FI/CO BAPI is called.

Explanation

So that tax can be calculated and posted correctly the SAP system requires far more information than just tax code, tax base amount and tax account. Transaction FB60 offers far more hidden information for the tax calculation, for example whether the net or gross amount should be used. In order to pass on all the necessary data to the BAPIs the interfaces would have to be oversized. In addition the implementation of a tax calculation function would cause the risk of possible inconsistencies in the posted tax amounts. Also it would not be possible to distinguish whether the taxes were calculated in the SAP system or in an external system (for example for an SD invoice for which the taxes are calculated in the external system).

Solution

A solution does not exist! The tax data must be determined before the BAPI is called and in the tax line items they must be passed on to the BAPI/IDoc.

My example code:

************************************************************************
*         Calculate tax                                                *
************************************************************************
DESCRIBE TABLE gt_curr_acc LINES gv_tax_tabix. ”No. of lines in currency table
LOOP AT gt_inp_data INTO gs_inp_data.
gv_tax_tabix = gv_tax_tabix + 1. ”Actual tax line*   Run calculation
CALL FUNCTION ’CALCULATE_TAX_FROM_NET_AMOUNT’
EXPORTING
i_bukrs           = gs_inp_data-bukrs
i_mwskz           = gs_inp_data-mwskz
i_waers           = ’AUD’
i_wrbtr           = lv_wrbtr
TABLES
t_mwdat           = lt_mwdat
EXCEPTIONS
bukrs_not_found   = 1
country_not_found = 2
mwskz_not_defined = 3
mwskz_not_valid   = 4
ktosl_not_found   = 5
kalsm_not_found   = 6
parameter_error   = 7
knumh_not_found   = 8
kschl_not_found   = 9
unknown_error     = 10
account_not_found = 11
txjcd_not_valid   = 12
OTHERS            = 13.
IF sy-subrc <> 0.
*   Add your error handling here
*   (CALL FUNCTION ’SWO_TEXT_FUNCTION_EXCEPTION’)
ENDIF.

*  Continue with processing => Tax acc table
CLEAR: ls_mwdat, gs_e1bpactx01.
READ TABLE lt_mwdat INTO ls_mwdat INDEX 1.
gs_e1bpactx01-itemno_acc = gv_tax_tabix.
gs_e1bpactx01-acct_key = ls_mwdat-ktosl.
gs_e1bpactx01-tax_code = gs_inp_data-mwskz.
gs_e1bpactx01-cond_key = ls_mwdat-kschl.

CLEAR gs_edidd.
gs_edidd-segnam = zidoc_segnam-e1bpactx01.
gs_edidd-sdata  = gs_e1bpactx01.
APPEND gs_edidd TO gt_tax_acc.

*   Currency acc table
CLEAR gs_e1bpaccr01.
gs_e1bpaccr01-itemno_acc = gv_tax_tabix.
gs_e1bpaccr01-currency   = gs_inp_data-waers.
gs_e1bpaccr01-amt_base = gs_inp_data-wrbtr.
gs_e1bpaccr01-amt_doccur = ls_mwdat-wmwst.

ENDLOOP.

 

Posted in ABAP tips, SAP - Tagged , ,

Direct posting to tax account with AC BAPIs

Jan19
2012 Leave a Comment Written by Pavel
Symptom

When you carry out a direct posting to a tax account, the system generates error message FF747: “The tax amount must not be greater than the tax base”.

Other terms

AC interface, taxes, BSET-FWBAS BAPI_ACC_DOCUMENT_POST, BAPI_ACC_DOCUMENT_CHECK, BAPI_ACC_BILLING_POST, BAPI_ACC_BILLING_CHECK, BAPI_ACC_INVOICE_RECEIPT_POST, BAPI_ACC_INVOICE_RECEIPT_CHECK, BAPI_ACC_GOODS_MOVEMENT_POST, BAPI_ACC_GOODS_MOVEMENT_CHECK

Reason and Prerequisites

Due to the business transaction, this direct posting is only possible with BAPI_ACC_BILLING_POST. Otherwise this function is not provided.

Solution

Apply OSS Note 487064.
For this purpose, the structures in the BAPI have to be filled as follows:

Example call with 16 EUR and base amount 100 EUR:
  • ACCOUNTPAYABLE must at least contain the item number (ITEMNO_ACC) and the vendor (VENDOR). The amount in structure CURRENCYAMOUNT is to be: AMT_DOCCUR = 16;CURRENCY = EUR;ITEMNO_ACC = 1.
  •  ACCOUNTGL is only provided as a dummy line item and is deleted in the AC interface. ITEMNO_ACC (2?) and G/L account (GL_ACCOUNT) are required entry fields. In CURRENCYAMOUNT, you only have to fill ITEMNO_ACC
  • ACCOUNTTAX must contain ITEMNO_ACC (3?), tax account (GL_ACCOUNT) and tax code (TAX_CODE). The currency information in CURRENCYAMOUNT must contain AMT_DOCCUR = 16; CURRENCY = EUR and AMT_BASE = 100 with identical ITEMNO_ACC (3?).
Posted in ABAP tips, SAP, Uncategorized - Tagged

Quick Tips and tricks on Web Dynpro for ABAP – How to use ALV and Pop Ups

Aug22
2011 Leave a Comment Written by Pavel

Quick Tips andTtricks on Web Dynpro for ABAP – How to use ALV and Pop Ups.

Posted in WebDynpro for ABAP

Use field symbols for better performance in internal tables

Aug19
2011 Leave a Comment Written by Pavel

Full text & code of this article on: Use field symbols for better performance in internal tables.

Author:
James Vander Heyden

Do you want to squeeze more performance out of your Internal Table processing? The new ABAP object extensions in SAP require internal table definitions to look a little different. With this new style of definition comes many options for better performance like hash tables and sorted tables. The use of field symbols takes this performance concept one step further.

The new style of definition of internal tables usually doesn’t include a header area for the internal table. Furthermore, ABAP Objects will not allow internal tables with header lines. For added performance, instead of declaring a work area–use a field symbol. The work area concept and header line format both require data to be moved from the internal table to the work area or header area. A field symbol is just a pointer that will point to the proper line of the itab. With field symbols, no data needs to be moved. The field symbol just stores the proper memory address to point at the right line. The field symbol can have structure and be made up of fields similar to a work area or header line. Because no data needs to be copied, processing is much faster.

The keys to the usage are:

1) Defining the table records and the field symbol in a similar type.

* just an ordinary standard table

TYPES: BEGIN OF it_vbak_line,
vbeln LIKE vbak-vbeln,
vkorg LIKE vbak-vkorg,
vtweg LIKE vbak-vtweg,
spart LIKE vbak-spart,
kunnr LIKE vbak-kunnr,
END OF it_vbak_line.

DATA: it_vbak TYPE TABLE OF it_vbak_line.
FIELD-SYMBOLS: <it_vbak_line> TYPE it_vbak_line.

* or as a screaming fast hash table for keyed reads

TYPES: BEGIN OF it_vbpa_line,
vbeln LIKE vbak-vbeln,
kunnr LIKE vbak-kunnr,
END OF it_vbpa_line.

DATA: it_vbpa TYPE HASHED TABLE OF it_vbpa_line
WITH UNIQUE KEY vbeln.
FIELD-SYMBOLS: <it_vbpa_line> TYPE it_vbpa_line.

2) In ITAB processing, utilize the ASSIGNING command.

* loop example

LOOP AT it_vbak ASSIGNING <it_vbak_line>.

* look at records – populate it_zpartner
* read example

READ TABLE it_vbpa ASSIGNING <it_vbpa_line> WITH TABLE KEY vbeln = <it_vbak_line>-vbeln.

3) Refer to the field symbol’s fields in the loop or after the read.

wa_zpartner-vkorg = <it_vbak_line>-vkorg.
wa_zpartner-vtweg = <it_vbak_line>-vtweg.
wa_zpartner-spart = <it_vbak_line>-spart.
wa_zpartner-kunag = <it_vbak_line>-kunnr.
wa_zpartner-kunwe = <it_vbpa_line>-kunnr.

Posted in ABAP tips, SAP

Sanjeet Mall about SAP CRM 7.0 EhP1

Jun17
2010 Leave a Comment Written by Pavel

Gregor Wolf has posted on http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/19701 his interview with Sanjeet Mall – Vice President and Chief Solution Architect for SAP CRM.

He gives more information about new features and innovations in SAP CRM 7.0 EhP1.

It’s definitely worth seeing.

Posted in CRM, SAP - Tagged

CRM Campaing contact list overview

Apr19
2010 Leave a Comment Written by Pavel

To display overview of all the target groups and mails included in a campaign use transaction:

CRMD_EMAIL_LIST

You will get to overview of the campaigns run on the server and the number of e-mails, that are coming with each of the campaigns affected.

CRM_market_contact_list

Posted in CRM, SAP - Tagged

SAP CRM Campaign Automation Error

Apr19
2010 Leave a Comment Written by Pavel

If you try tu run campaign automation on SAP CRM Web AS, you may get an error saying “[campaign name]:Campaign has not started”.

As this is really not very helpful and there are no details included, there is a solution.

In transaction SPRO go to IMG -> CRM -> Marketing -> Marketing Planning and Campaign Management -> Campaign Automation

There are three important task to be customized:

  • 1.Maintain standard settings for SAP business flow
  • 2.Implement workflow assignment
  • 3.Implement workflow customizing

In the last one, make sure, that all workflows are set to “General task” (so that anybody can run them).

It should look like on this picture:

wf_crm_assign\

That’s it – try running the campaing once again.

Pavel

Posted in CRM, SAP - Tagged

SAP CRM 7.0 – Marketing End-to-End Videos: Part I – Part V

Apr13
2010 Leave a Comment Written by Pavel

To help provide an overview of the key capabilities that are supported by SAP CRM Marketing and how they can support marketers, I have created these 5 end-to-end videos. The videos should help those wanting to get an entry level overview of SAP CRM direct marketing functionality and how it is integrated with the customer facing interaction channels of SAP CRM.

SAP CRM 7.0 – Marketing End-to-End Videos: Part I – Part V

Posted in CRM, SAP - Tagged

SAP Query Reporting PDF E-Book

Apr13
2010 Leave a Comment Written by Pavel

SAP

SAP Query Reporting is everything an SAP user needs to know to create your own reports in SAP using Query tools, no programming required! Designed as a hands-on learning aid, you will be able to follow along and perform each new skill learned on your own SAP system. The book’s tutorial style, step-by-step instruction will teach you everything you need to know to use the SAP Query tools, including its configuration, advanced usage, and integration to Microsoft. Additionally the book gives best business practice recommendations for the technology and internal business use of the tools. Learn to:

* Understand query security, table reads, and table joins
* Perform basic and advanced calculations
* Incorporate pictures and graphics into reports
* Configure shortcuts and tran codes, schedule jobs and email PDFs
* Utilize SAP Reporting with Microsoft Office applications

Download link

Posted in SAP, Workflow

The most effective way to find a BADI

Feb20
2010 Leave a Comment Written by Pavel

SAPBusiness Add-Ins are SAP enhancement technique, based on ABAP Objects. They can be inserted to accommodate user requirements, too specific for a standard delivery. All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.

Pros:
BADIs can be used any number of times, whereas USER-EXITS can be used only one time.
BADIs are based on Object-Oriented-Programming with fixed structure -> Therefore SAP guarantees
the upward compatibility of all Business Add-In interfaces.

Cons:
It’s difficult to say, when using a transaction, whether BADI is used or not.

Solution:

1, Go to transaction SE37 and put a breakpoint on function SXV_GET_CLIF_BY_NAME.
2, Set a breakpoint on a call of the only function included.
3, Open another session and set YOUR transaction. The debugging mode opens with info
on BADIs. Name = BADI, Clif = implementation of a BADI.


FUNCTION sxv_get_clif_by_name .
*"----------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*" IMPORTING
*" VALUE(NAME)
*" VALUE(PREFIX) TYPE SEEX_CLIF_PREFIX
*" EXPORTING
*" VALUE(CLIF) TYPE SEOCLSNAME
*"----------------------------------------------------------------------
breakpointCALL FUNCTION 'SXV_ADD_PREFIX'
EXPORTING
name = name
prefix = prefix
IMPORTING
new_name = clif.
ENDFUNCTION.

Posted in ABAP tips, SAP - Tagged
« Older Entries