taxl2f

7/27/2019 taxl2f

http://slidepdf.com/reader/full/taxl2f 1/106

© SAP Labs, Inc. – May 2000 - Tax Interface Workshop rel. 46x (Irene Oei) / 1

Tax Interface Release 4.6x

Intended to

SAP and SAP tax partnersCustomer Support Team

7/27/2019 taxl2f



Workshop Purpose

Facilitate the interaction between

SAP customer support team

AndSAP tax partners

Customer support team

7/27/2019 taxl2f



Workshop Objectives

• Understanding the Tax Interface System

within the SD, MM and FI Modules

• Understanding the Tax Interface System

• Understanding the Audit file On-line

Update process

7/27/2019 taxl2f



Workshop Contents

• Part 1: Basic Concepts on US Sales & Use tax

• Part 2: Basic Configuration (+ exercises )

• Part 3: Introduction to Pricing Procedure and

Condition Techniques

• Part 4: Tax calculation in SD, MM and FI (+ exercises)

• Part 5: Tax posting in SD, MM and FI

• Part 6: Audit file on-line update process

• Part 7: External Tax Document (+ exercises)

• Part 8: User-Exit

7/27/2019 taxl2f



Part 1: US Sales & Use Tax

Introduction to

US Sales & Use Tax

Legal & Business

Requirements

7/27/2019 taxl2f



Part 2: Basic Configuration

1. Set up Physical Destination

2. Activate Tax Interface System

3. Extra Requirements

7/27/2019 taxl2f

http://slidepdf.com/reader/full/taxl2f 7/106© SAP Labs, Inc. – May 2000 - Tax Interface Workshop rel. 46x (Irene Oei) / 7

Physical Destination

• Set up Physical Destination (SM59)

• Installation Method:

Application server

7/27/2019 taxl2f



• Set up Physical Destination

(SM59)

• Installation Method:

Explicit host

7/27/2019 taxl2f



• Set up Gateway:

7/27/2019 taxl2f



• Verify External Tax System version:

System Information -> Function List

7/27/2019 taxl2f


Test Remote Functions

• Test Jurisdiction Determination:RFC_DETERMINE_JURISDICTION

• Test Tax Calculation:

RFC_CALCULATE_TAXES_DOC

• Test Tax Update:

RFC_UPDATE_TAXES_DOC

• Test Tax Forced Update:

RFC_FORCE_TAXES_DOC

7/27/2019 taxl2f


1) Questions

1. When can DOC_NUMBER be blank ?

When is DOC_NUMBER always filled ?

2. What is GROUP_ID ?

3. What is the difference between PROD_CODE andGROUP_PROD_CODE ?

4. What is the difference between ITEM_NO and

POS_NO ?

5. Is there a relation between

NR_JUR_LEVELS and TXJLV ?

7/27/2019 taxl2f



1) Answers

1. DOC_NUMBER can be blank during RFC_CALCULATE_TAXES_DOC

DOC_NUMBER is always filled during RFC_UPDATE/FORCE_TAXES_DOC

2. GROUP_ID is defaulted as higher-level material item position (BOM).

3. PROD_CODE is component item ext. product code and GROUP_PROD_CODE is set itemext. product code.

4. ITEM_NO is a sequential internal numbering (starting with 1) given to each tax document

item. POS_NO is the item position number in the SD, MM or FI document.

5. Indicator for the total number of tax lines by jurisdiction level for each item returned by

external tax system (O_TAX_CAL_JUR_LEVEL_OUT).

7/27/2019 taxl2f



2) Questions

6. Is AMOUNT always equal to GROSS_AMOUNT ?

7. Is it possible to have

APAR_IND=“A” in a Purchase Order ?

8. What is the difference betweenUSER_DATA and USER_REPT_DATA ?

9. What does CURRENCY contain ?

10. Is it possible to have

TAX_PER_ITEM=“X” and NR_LINE_ITEMS>1 ?

7/27/2019 taxl2f



2) Answers

6. GROSS_AMOUNT is always defaulted by AMOUNT.

7. No, except if you had configured to use “Use Tax Codes” for a sales order/billing doc.

8. USER_DATA: it is sent during tax calculation (recommended for reporting purposes only).

USER_REPT_DATA: filled in user-exit but only for reporting/update purposes

9. CURRENCY: During RFC_CALCULATE_TAXES_DOC => document/transactioncurrency

During RFC_UPDATE_TAXES_DOC => Local currency (= document currency)

During RFC_FORCE_TAXES_DOC => Local currency (not always same as document

currency)

10. NO, during RFC_CALCULATE_TAXES_DOC

YES, during RFC_UPDATE/FORCE_TAXES_DOC

7/27/2019 taxl2f



Data for the ExercisesCountry USV UST

Company Code USXV USXTControlling Area USXV USXT

Cost Centers USV1… UST2….

Plant USV1 UST1Storage Location 0001 0001

Sales Area USV1 01 01 UST1 01 01

Shipping Point USV1 UST1

Purchase Org USV1 UST1

Customer CVERTEX1… CTAXWARE1…

Vendor VVERTEX1…. VTAXWARE1…

Material MVERTEX1…. MTAXWARE1…

7/27/2019 taxl2f



Exercises 1

1. Build your own test data for tax calculation:

- Copy test data from existent Test Data Directory

- Change test data accordingly by adding more items, etc.

- Save test data in test data directory

- Test and verify results

2. Build your own test data for tax update:

- Copy from previous test data

3. Build your own test data for tax forced update:- Copy from previous test data (en test results data?…)

7/27/2019 taxl2f



Activate Tax Interface System

1. Define a tax procedure to a country

2. Activate external tax calculation (TTXD):

- RFC Destination (defined in SM59)

- Interface Version (TAXDOC00 only !!!)- Notice: Logical Destination is no longer used (TTXC)

3. Define Number Ranges for External Tax Document:

- Interval: 01 (from 000000000001 to 999999999999)

4. Activate External Tax Document

7/27/2019 taxl2f



Extra Requirements….

Define tax jurisdiction code structure:

- Only for BSET reconstruction….

- The ‘way to insert’ a tax procedure in table TTXD

- Tx In: Expand tax calculation per item (FI/MM):• Off: Aggregate per TaxCode x Jurisdiction Code

Item data such as posno, material and quantity is lost• On: Calculate for each item without losing item data

7/27/2019 taxl2f



Part 3: Pricing

7/27/2019 taxl2f



7/27/2019 taxl2f



7/27/2019 taxl2f



7/27/2019 taxl2f



7/27/2019 taxl2f



7/27/2019 taxl2f



7/27/2019 taxl2f



7/27/2019 taxl2f



7/27/2019 taxl2f



7/27/2019 taxl2f



7/27/2019 taxl2f



7/27/2019 taxl2f



7/27/2019 taxl2f



7/27/2019 taxl2f



7/27/2019 taxl2f



7/27/2019 taxl2f



Part 4: Taxes in SD/MM/FI

7/27/2019 taxl2f



Part 4: Taxes in SD/MM/FI

The 3 Tax Calculation methods:

1) SD tax calculation method for Sales Order and Billing

2) PO tax calculation method for Purchase Order

3) FI tax calculation method for IV/LIV and FI (AR/AP)

Part 4: Taxes in SD

7/27/2019 taxl2f



Sales

Order

Goods

Issue

Billing

Central TaxCentral TaxPostingsPostings

CreditMemo

Request

Credit

Memo

SD TaxSD TaxCalculationCalculation

Part 4: Taxes in SD

Tax Calculation in SD

7/27/2019 taxl2f



Tax Calculation in SD

Condition Records for UTXJ

Delivery Country : US

Customer Tax Class. : 1Material Tax Class. : 1

Tax Code : O1

Pricing Procedure: RVAXUS

UTXJ 300

XR1 301

XR2 302

….. …..

Condition Type: UTXJ

Access Sequence: UTX1

Access Sequence: UTX1

20. Domestic Taxes

Alternate

Condition Type

Formula

Tax Procedure: TAXUSX

XR1 MW1

XR2 MW2

…. …..

Tax Calculation in RVAXUS

7/27/2019 taxl2f



Tax Calculation in RVAXUS

R F C_ C A L C U L

A T E_ T

A X E S_ D

O C

Each Item is sent to the Tax System at the time:• No MAXTAX per Document

• RFC_CALCULATE_TAXES_DOC is being called for each item

with the same header

300 (UTXJ)Item 10

External

Tax Document

Tax Manager

External

Tax DocumentExternal


Tax Document

Tax System

COLLECT_AND_CALCULATE

_TAX_DATA

301 (XR1)

Item 10

GET_TAX_RESULTS

_FOR_301_306

302 (XR2)Item 10

•

•

•

7/27/2019 taxl2f


Tax Manager -> Item Pricing

7/27/2019 taxl2f



Function “GET_TAX_RESULTS_FOR_301_306”:

KOMK (input):• komk-no_upd (dummy calculation flag – LTAX1…)

• komk-belnr (document number)

• komk-txjcd (tax jurisdiction code)

KOMP (input):• komp-taxps (item number for tax document)

• komp-mwskz (tax code)

XKOMV (output):• xkomv-kbetr (condition type tax rate : XR1…6)

• xkomv-kwert (condition type tax amount : XR1…6)

• xkomv-txjlv (jurisdiction level: 1…6)

Tax Manager -> Item Pricing

Tax Calculation in RVAXUD

7/27/2019 taxl2f




External

Tax Document

Tax Manager

External



Tax Document

Tax System

FV64A500

Item 10

500 (UTXD)

Item 20•

•

•

500 (UTXD)

Item 10

510 (UTXE)

CHECK_IF_TAX_INPUT

_COLLECTION

CHECK_IF_TAX

_CALCULATION

301..306(XR1…XR6)

Item 10

GET_TAX_RESULTS

_FOR_301_306

301..306(XR1…XR6)

Item 20•

•

•

R F C_ C A L C U L A T

E_ T A X E S_ D

O C


7/27/2019 taxl2f



• MAXTAX per Document

• RFC_CALCULATE_TAXES_DOC is being called

once for all items of a document

• Tax calculation happens in each ‘pricing_complete’:to view item tax results before saving the document, header

pricing has to be triggered first.


All items are sent at once to the Tax System:

Configuration in RVAXUD

7/27/2019 taxl2f



Configuration in RVAXUD

• UTXJ is replaced by UTXD

• UTXD has alternate condition formula 500:

- formula will map and store item tax input data

- is executed once for each item (in pricing complete)

• UTXE has alternate condition formula 510:- triggers tax calculation for all items

- is executed once per document (in pricing complete)

• UTXD and UTXE are statistical

• XR1…XR6 as in RVAXUS w/ formulas 301…306

Configuration for UTXD

7/27/2019 taxl2f



• UTXD required configuration:

- is a group condition

- has access sequence UTX1:

has the same access sequence as UTXJ

- has UTXJ as reference condition type:

has the same condition records as UTXJ

- has scale base formula: 500 – “init document taxes”:initialize the current tax document

- all condition record rates have the value 100%

Configuration for UTXD

Configuration for UTXE

7/27/2019 taxl2f



• UTXE required configuration:

- is a group condition

- has NO access sequence

Configuration for UTXE

Part 4: Taxes in MM

7/27/2019 taxl2f



PurchaseOrder

GoodsReceipt

InvoiceVerification


PurchaseOrder

Goods

Receipt

LogisticsInv. Verif.

Central TaxCentral TaxCalculationCalculation

Part 4: Taxes in MM

Tax Calculation in PO

7/27/2019 taxl2f




• Tax Code Determination in PO:

1. Manual entry

2. NAVS Condition Records

3. Info Record

• Tax Code Determination in IV/LIV:

1. Manual entry

2. Copy from PO


7/27/2019 taxl2f




2. NAVS Condition Records

Condition Type : NAVS

Access Sequence : 0003

Access Sequence : 0003

50. Material tax class.

PO Pricing Proc. : RM0000

NAVS $ base amount

Condition Records for NAVS

Destination Country : US

Material Tax Class. : 1

Tax Code : I1

BASB

300

XP1I 301 NVS

XP2I 302 NVS…. ….. …..


Alternate

Condition Type

Formula


7/27/2019 taxl2f



3. Info Record

PO Pricing Proc. : RM0000

NAVM $ base amount

Condition Type : NAVM

NO Access Sequence

Info Record :

Tax Code : U1

BASB

300

XP1I 301 NVSXP2I 302 NVS

…. ….. …..


Alternate

Condition TypeFormula


Part 4: Taxes in FI

7/27/2019 taxl2f



Part 4: Taxes in FI


A/P -

Vendor

Invoice

A/R -

Customer

Invoice

Central TaxCentral TaxCalculationCalculation

Central Tax Calculation

7/27/2019 taxl2f



Central Tax Calculation

7/27/2019 taxl2f



7/27/2019 taxl2f



7/27/2019 taxl2f



Form 300 Program Flow

7/27/2019 taxl2f



Relevant for tax system? (1)

Configuration consistent? (2)

Check exemption and copy flag (4)

Return to pricing.

Yes

YesNo

No

Error message.

no copy, no exempt exempt

Error

Error message.

OK

Return to pricing.

Map input data and (3)

Customer user exit.

Store tax amounts in

External Tax Document.

RFC to external system. (5) Set tax amounts to 0. (5) Fill tax amounts w/ XKOMV.

(5)

copy, no exempt

Form 300 Program Flow

Form 300 Program Flow I

7/27/2019 taxl2f



Form 300 Program Flow I

Relevant for tax system? (1)

Return to pricing.

No Yes

Class (se24):

CL_XTAX_RULES_CONFIGURATION

Methods:

- check_display_mode

- check_calculation_relevancy

Configuration consistent?

Form 300 Program Flow II

7/27/2019 taxl2f



o 300 og a o

Class (se24):


Methods:

check_tax_configuration

Configuration consistent? (2)

No Yes

Error message. Map input data and

Customer user exit.

Form 300 Program Flow III

7/27/2019 taxl2f



Configuration consistent?

No Yes

Error message.Map input data and (3)

Customer user exit.

Class (se24):

CL_XTAX_RULES_CALCULATION

Methods:

add_input_data_header

add_input_data_item

handle_user_exit

g

Form 300 Program Flow IV

7/27/2019 taxl2f



Map input data and

Customer user exit.

Check exemption and copy flag (4)

g

Class (se24):


Methods:

check_taxes_defaulted

Form 300 Program Flow V

7/27/2019 taxl2f



Check exemption and copy flag

No copy, no exempt

RFC to external system.

Class (se24):

CL_XTAX_RULES_RFC

Methods:

rfc_calculate_taxes_doc

g

(5)

Form 300 Program Flow VI

7/27/2019 taxl2f




exempt

Set tax amounts to 0.

Class (se24):


Methods:

check _if_tax_exempt

g

(5)

Form 300 Program Flow VII

7/27/2019 taxl2f




Fill tax amounts w/ xkomv.

Class (se24):


Methods:

check _if_copy_pricing

Copy, no exempt

g

(5)

Form 300 Program Flow VIII

7/27/2019 taxl2f



RFC to external system. Set tax amounts to 0.Fill tax amounts

w/ xkomv.

OK Error

Error message. Store tax amounts in


(6)

Class (se24):

CL_XTAX_DOCUMENT

Methods:

get_input_data_and_calculate

set break-point at: ‘store_output_from_calculation’

g

Exercises 2A

7/27/2019 taxl2f



Customer is asking SAP why the tax rates/amounts are ….

1. Set break-point right after the call to the external tax system in:Method: RFC_CALCULATE_TAXES_DOC

in Class: CL_XTAX_RULES_RFC

2. Create a SD, MM or FI transaction

3. Verify the External System tax results during the break-point(let it be, DO NOT press CONTINUE)

4. Open another session and using Single Test functionality for

Function Module: RFC_CALCULATE_TAXES_DOC,

simulate the above transaction by inputting the same input parameters (copy/paste) and executing the Test.

Do you get the same tax results as with debugging?

Exercises 2B

7/27/2019 taxl2f



Check the tax exempt indicator and if taxes are being copy

from a reference (previous) document.

1. Set break-point at methods: - check_if_copy_pricing

- check_if_tax_exempt

in class: CL_XTAX_RULES_CONFIGURATION

2. Create a credit memo request (Doc. Type: G2 – trans: VA01):- At break-point, verify if copy pricing and the tax exempt ind.

- Press ‘Continue’ and save the document

3. Change the document:

- Change customer or material tax classification to non-taxablein the credit memo request itself. Verify again the 2 indicators.

4. Post the credit memo from previous document (VF01).

Verify again the 2 indicators. NOTE your results.

Part 5: Tax Postings SD/MM/FI

7/27/2019 taxl2f



g

Before…

7/27/2019 taxl2f



The three stages in the life of a Tax Document

I) Application SD/MM/FI:

Calculate taxes, prepare for TTXY.

II) RW interface “Post”:

Convert and compress tax data,

insert into Database (TTXY and

BSET).

III) Tax update program:

Check tax data from TTXY and

BSET, update external system.

FV64A300

US_TAXES_UPDATE_TABLE

……..

RFYTXU00

RFYTXF00

Update Programs…

7/27/2019 taxl2f



Application

RW Interface

Update Program

BSET TTXY

Tax Interface:

Calculation

Tax Interface:Posting

Tax Memory Actual Tax Data

Compressed

FI Tax data

Tax System

Taxes for

reporting

Tax Data

I)

II)

III)

Tax

Data

Tax Tables: BSET and TTXY

7/27/2019 taxl2f



• TTXY: (logistics) document data

– output of external system (COM_TAX)

– per document item

• BSET: tax data of accounting document

– taxes in local AND document currency

– G/L account number

– per tax code, jurisdiction code, tax level

TAX storage: BSET v.s. TTXY

Different Views

7/27/2019 taxl2f



B S E T

T T X Y

Tax data

Projection on TTXY and BSET

7/27/2019 taxl2f



Taxes per document item and level

BSET

TTXY

Level Tax code Jur. Code Tax amount

1 O1 CA0000000 18.75

2 O1 CA9440401 3

3 O1 CA9440401 0

1 O0 CA0000000 0

2 O0 CA9440401 0

3 O0 CA9440401 0

Item Tax code Jur. Code Tax Amt 1 Tax Amt 2 Tax Amt 3

10 O1 CA9440401 6.25 1 020 O0 CA9440401 0 0 0

30 O1 CA9440401 12.5 2 0

Item No. Level Tax code Jur. Code Tax amount

10 1 O1 CA9440401 6.25

2 O1 CA9440401 1

3 O1 CA9440401 0

20 1 O0 CA9440401 0

2 O0 CA9440401 0

3 O0 CA9440401 0

30 1 O1 CA9440401 12.52 O1 CA9440401 2

3 O1 CA9440401 0

Relationship BSET - TTXY

7/27/2019 taxl2f



BSET TTXY

Accounting

document

Logistics

document

BSET

BSET

TTXY

TTXY

BSET, TTXY and Headers

7/27/2019 taxl2f



TTXYBSET

TTXIBKPF

mn

n

11

11

m

Accounting data Logistics data

Keys of BKPF and TTXI

7/27/2019 taxl2f



• BKPF – Primary key:

• Company code BUKRS

• Accounting document number BELNR

• Fiscal year GJAHR

• TTXI: – Primary key:

• Object type of calling application AWTYP• Reference document number AWREF

• Reference organizational units AWORG

From TTXI to BKPF?

7/27/2019 taxl2f



• Secondary index BKPF (unique): – AWTYP Object type of calling application

– AWKEY Object key

• Map as follows:

– BKPF-AWTYP = TTXI-AWTYP

– BKPF-AWREF = TTXI-AWREF ⊕ TTXI-AWORG

Update Tax Register Audit File

7/27/2019 taxl2f



• Programs RFYTXU00 and RFYTXF00

• Update in batch

– performance

– no accounting document yet during taxcalculation

• Source: TTXI/TTXY – output data of last tax calculation

Normal Update

7/27/2019 taxl2f



• Following checks have to be passed:

– Configuration data must still be correct

– Tax amounts TTXY consistent with G/L – Tax amounts TTXY consistent tax system

Check Configuration Data

7/27/2019 taxl2f



• Configuration data – Company code, country, jurisdiction structure

• Necessary document data

– Accounting document must exist (BKPF) – G/L tax data must exist (BSET)

• → No update to tax system

– document flagged as “Error”

Internal Consistency

7/27/2019 taxl2f



• Check amounts BSET - TTXY – “Internal consistency”

– Per tax code and jurisdiction code

• Reasons for inconsistency: – document in foreign currency

– amounts manually overwritten

• → Force BSET to tax system

– taxes copied from BSET without recalculation

– document flagged as “Forced”

Consistency with General Ledger

External Consistency

7/27/2019 taxl2f



• Check TTXY - recalculated amounts – “External consistency”

– Per TTXY entry

• Reasons for inconsistency:

– configured as exempt in SAP

• → Force TTXY to tax system – taxes copied from TTXY without recalculation

– document flagged as “Forced”

Consistency with tax system

RFYTXU00: Normal Update

7/27/2019 taxl2f



RFYTXU00

Not UpdatedUFLAG <> U, F Not UpdatedUFLAG <> U, F

TTXI-UFLAG:

Update status

Error UFLAG = E

Updated

UFLAG = U

Flagged for

forced update.

UFLAG = V

TTXI/TTXY

RFYTXF00: Forced Update

7/27/2019 taxl2f



RFYTXF00

Error UFLAG = E

UpdatedUFLAG = F

Flagged for

forced update.UFLAG = V

TTXI/TTXY

RFYTXD00: Display List

7/27/2019 taxl2f



RFYTXU00

TTXI

RFYTXD00

RFYTXF00

Display document

Tax Postings SD/MM/FI

7/27/2019 taxl2f



After…

7/27/2019 taxl2f



The two stages in the life of a Tax Document

I) Application SD/MM/FI:

Calculate taxes,

create External Tax Document.

II) RW interface “Post”:

1. Fill External Tax Document

with posting data.

2. Update external system with


FV64A300

FV64A500/510

CL_XTAX_RULES_POSTINGMethods:

- map_document_posting_data

- map_item_posting_data

CL_XTAX_RULES_RFCMethods:

- trfc_update_taxes_doc

- trfc_force_taxes_doc

NO Update Programs!!!

7/27/2019 taxl2f



Application

RW Interface

BSET

Tax Interface:Calculation

Tax Interface:

Posting

Actual Tax Data/

Tax Parameters

CompressedFI Tax data

Tax System

Taxes for reporting

Tax Data

I)

II)FI Tax

data

Tax Data/

Parameters

Part 6: On-line Update

7/27/2019 taxl2f



• Update occurs during document post to accounting

• Update is done through Transactional RFC (tRFC)

• Determination of Normal vs. Forced update is done

prior to updating the external tax system (tRFC).

Transactional RFC (tRFC)

7/27/2019 taxl2f



• Remote Function Call in background task CL_XTAX_RULES_RFC

method:

trfc_update_taxes_doc

trfc_force_taxes_doc

• Assigned to a Transactional ID (TID)One unique TID for each commit work (~one LUW)

Usually, but not always, one accounting document per commit work

• Each TID is assigned to a queueQueue name: ‘TIF_UPDATE_AUDIT_FILE’

View documents still in the queue with transaction: ‘SMQ1’

View Document Update Status

7/27/2019 taxl2f



tRFC Queue

7/27/2019 taxl2f



View tax documents in tRFC queue:

Transaction: SMQ1

Queue name: TIF_UPDATE_AUDIT_FILE

Document Holding the Queue

7/27/2019 taxl2f



View the RFC call which is holding up the queue:

Part 7: External Tax Document

7/27/2019 taxl2f



View External Tax Documents and its update status:

Update Status

7/27/2019 taxl2f



Green Light:

Tax data sent to the external tax system audit file

Yellow Light:

Tax data waiting to be sent (no error, in the tRFC queue)

Red Light:

Tax data could not be sent to the external tax systemError has occurred during tRFC

This document will hold up the queue

What Is Forced Update?

7/27/2019 taxl2f



• Updating the audit file with GL tax rates/amounts

• Original input data is being updated without loss of info- Ship-to, Ship-from, POA, POO Jurisdiction Code

- Material number, Product Code

- Credit indicator (per document item!)

• External tax system output data is not being updated- TXJCD_IND, EXMATFLAG, EXCUSFLG

- TAXBAS, EXAMT

è No major harm when document is force updated!

Why Forced Update?

7/27/2019 taxl2f



• When is a document being Force Updated?

GL tax amounts differs from External System tax amounts

AND/OR

External System tax amounts differs during recalculation

• Causes for Forced Update?

Internal Consistency and/or External Consistency fail

Consistency Check Rules

7/27/2019 taxl2f



Internal Consistency fails if:

A. Document Currency differs from Local CurrencyB. Manually entered tax amounts/rates

External Consistency fails if:

A. Default Reason:

1. Tax amounts/rates were copied from reference document

2. Tax Code property has ‘relevant to tax indicator = 2 ‘.

3. Tax base amount is zero.

4. Tax rates/amounts are manually set to 0.5. Non-taxable transaction (OBCL).

B. No Default Reason => Configuration has been changed

Exercises 3C t d t k h d t i h ldi th

7/27/2019 taxl2f



Customer needs to know why a document is holding the

tRFC queue…

1. Reproduce the problem by resetting the Update Status:

- reset field etxdch-docstatus from ‘updated’ to ‘hasgldata’:

- run program…..zfytxreset (in U9B only)

- verify that field etxdch-docstatus is now equal to ‘hasgldata’.

2. Note the Document Number and TID which is holding up the

queue with transaction SMQ1, queue name:‘tif_update_audit_file’.

- DO NOT execute this procedure in a Production System!!!

- This procedure should ONLY BE DONE by

SAP Regional/Development Support team.

Exercises 3 – continuation…

7/27/2019 taxl2f



3. Set break-point in methods:

- TRFC_UPDATE_TAXES_DOC

- TRFC_FORCE_TAXES_DOCfrom class: CL_XTAX_RULES_RFC

4. Resend the document by running RFYTXUPDATE

Customers should not use RFYTXUPDATE.

This program is NOT SUPPORTED by SAP!!!!

5. At the break-point:

- Verify the RFC name (update or force?)

- Simulate executing a Single Test on the same RFC Functionname with SE37. Copy the input parameters (copy/paste)

- Execute Single Test and verify that error has been returned!

- Save the test in the test data directory

Solve Customer Problems…

7/27/2019 taxl2f



By contacting the appropriateTax Partner Customer Support team

And discussing why an error or an ‘undesired’ tax result

has been returned by the tax system

Using the Single Test input data simulation for:RFC_CALCULATE_TAXES_DOC

RFC_UPDATE_TAXES_DOC

RFC_FORCE_TAXES_DOC

Part 8: User-exits

7/27/2019 taxl2f



CL_XTAX_RULES_CALCULATION

Method: handle_user_exit

1. Old user-exit is processed before the new user-exit

is called

2. Old user-exit and new user-exit change only those fields

in structure TAX_ALLOWED_FIELDS (see via SE12)

3. It is recommended to enhance the new user-exit

instead of the old user-exit.

New User-exit

7/27/2019 taxl2f



• Tax interface enhancement FYTX0002

• It is possible to enhance:

Function Module: EXIT_SAPLFYTX_USER_001

“Pricing” input structure: CI_TAX_INPUT_USER

• Input parameters:i_t007A, i_ttxd, i_tax_header_input, i_tax_item_input

i_input_user (includes fields in CI_TAX_INPUT_USER)

• Output parameter:

ch_user_changed_fields (type TAX_ALLOWED_FIELDS)

Part 9: Jurisdiction in CAM

7/27/2019 taxl2f



Note 157139, 204313

=> All the previous messages are customizable for different modes

(on-line, batch, BDC mode ‘A’, ‘E’, ‘N’)

Note 207323

=> Do not call ‘Jurisdiction_determine_check’ when

field is Hidden. Function will be called if field is display only.

CAM jurisdiction functions: Non-CAM jurisdiction functions:

jurisdiction_determine_check determine_txjcd_externally

jurisdiction_help_value f_values_txjcd

CAM is used by customer, vendor, plant, etc.

– everything that has an address screen except for Cost Center.

Jurisdiction Code Function

FM J i di ti d t i h k

7/27/2019 taxl2f



FM: Jurisdiction_determine_check

IF input field TXJCD is blank

if Country is blank => Message E803(FF) – input incomplete

if tax procedure uses external system

no, do nothing

yes, if RFC connection error => E217(F2) – rfcdest not found

else if external system returns error OR no jurisdiction returned=> E792(FF) – taxjurcode not found

else if multiple jurisdiction code has been returned

AND in batch mode (NO_DI ALOG i s ‘ X’ )

=> E792(FF) – taxjurcode not unique in no dialog

ELSE

if external system is active, check if txjcd match with input address

else check if txjcd is an entry in TTXJ

if one of these checks fail => E832(F2) - invalid txjcd

Part 10: Notes for 46Bh

7/27/2019 taxl2f


Note 216368 – Error when force updating the audit file (tRFC) !!!!

Note 205145 – For AP/AR transactions, document number not updated. Note 194207 – pricing is executed only for group condition for VF02

Note216364 – Resend documents to external tax system…. be carefull!!!

Note 188732 – Incomplete customizing for RVAXUD

Note 194493 – Test tRFC (Create Z program)

Note 195112 – Customizing error: RFC destination is blank

Note 212982 - Interface Version TAXDOC00 is mandatory!!!

It will be forced in hotpackage

Note 302998 – User-exit hints

Notes up to May 10th: