SAP Note 216364 - Blocked queue / No

update to external tax system

Symptom

Please follow the steps in this note with appropriate care if you encounter
the following scenarios:
o You want to resend documents to the external tax system.
o The tRFC queue TIF_UPDATE_AUDIT_FILE is blocked by a document.
o The tRFC queue TIF_UPADTE_AUDIT_FILE has version lower than
6.20.045, supplement 9 and contains a blocking transaction which
was caused by an update termination. The STATUS is WAITUPDA. Please
have a look at note 525318 and 438015.
It is recommended that you contact SAP Support to verify that no data gets
lost, especially if you are not certain of the cause of the blocked queue.

More Terms
Vertex, Taxware, Sabrix, external tax system, no update

Cause and Prerequisites

o Symptom 1
Documents have been accidentally deleted from the audit database in the external tax
system.

o Symptom 2
Or, documents had to be deleted because they were waiting in the tRFC queue (see details
under step 1) and could not be executed manually.

o Symptom 3
Or, documents are waiting in the queue with status 'Transaction recorded' and block the
queue because the queue was temporarily locked and needs to be reactivated.

o Symptom 4
Transactions are updated into the queue even though the actual transaction was not posted
due to an update termination. The queue has the status WAITUPDA. When you drill down on
the column ENTRIES, the top hanging transaction shows the message 'Transaction recorded
(LUW with update records)' in the column 'StatusText'. This problem should be resolved
with higher kernels (please see details in note 722339).

o Symptom 5
The queue stops with error 'SYSFAIL'. When you drill down, the status shows 'CPICERR-
Connection Closed'. The hanging document cannot be processed manually and gives error
''Target system/gateway not active'
'Message no. SY 358'.

The reason why the documents do not get processed could vary:

o Cause A
Data being sent is not consistent with the data format expected from the external tax
system. An error message should be displayed in transaction SMQ1. Please see attached
notes 329191 and 329193.

o Cause B
The connection to the external tax interface was temporarily broken or the queue was
stopped (SMQ1/Execute Queue name TIF_UPDATE_AUDIT_FILE/ Edit: Lock queue (F7) or
Edit: Generic queue/Lock). As a consequence, transactions are getting recorded, but not
processed.

o Cause C
The qRFC/tRFC version has errors (see note 442478).

o Cause D
Vertex specific: please find described in note 645527 the issue that after the upgrade of R/3
to 4.6C or 4.7 the queue hangs if the RFCs used contain the old calls
(RFC_CALCULATE_TAXES and RFC_CALCULATE_TAXES1) and the new call
(RFC_CALCULATE_TAXES_DOC).

o Cause E
Vertex specific: the queue stops in mode RUNNING, but no transaction is being updated to
the Vertex Register. The queue cannot be activated, there is no response from the Vertex
side.
This can happen after a hardware change and if Win2000 or Win2003 is used.

Please note that you have to be very conscious if you delete entries
from the tRFC. There is no log. The display program (RFYTXDISPLAY)
thinks that the document has been successfully sent to the external
system (because no longer in queue). Contact SAP Support if you need
further clarification in addition to this note.

Solution

Symptoms 1 and 2:
Step 1
Reset the update status of those documents so they can be resent to the external tax
system.
Create a custom reset program based on the attached program template
Z_CUSTOMER_REPORT. (The template program is not tested. SAP does not provide support
for this program.)

Determine the hanging transaction:

o Enter transaction SMQ1, specify queue name TIF_UPDATE_AUDIT_FILE, leave default * in
queue destination and execute (F8).

o Double click on column ENTRIES. A list of all transactions still to be processed in the tRFC
queue and the data to be sent is displayed. An error message should be displayed in the
column STATUS TXT.
The top one is the document which could not be processed and caused that the sequential
processing of all remaining transactions was held up. The document number of the
document can be found when you double-click on the column 'QUEUE NAME' under
I_TAX_UPD_HEAD_IN
or
I_TAX_FRC_HEAD_IN
Parameter Value
XXX11122223333333333CUR
XXX = System name
111 = client
2222 = company code
3333333333 = document number
CUR = currency key

o Verify that the DOCSTATUS of this document is set to UPDATED in table ETXDCH with
transaction SE16.

o Reset the blocking document with the custom reset program. After the reset, the field
ETXDCH-DOCSTATUS should hold the value HASGLDATA.

Step 2
Run program RFYTXUPDATE. It will automatically select those documents that have not yet
been updated and will (again) update to the external system with the tRFC. Please note,
this program is meant as a template and should be copied to a custom named program. It
serves a workaround tool if the automatic update fails.

Step 3
If the transactions still cannot be transferred to the external tax system even when resent,
contact SAP development support and the external tax vendor in order to have the cause
determined.

Symptom 3

Activate the queue again.

o SMQ1/Queue name TIF_UPDATE_AUDIT_FILE /Execute/Place cursor on the queue and hit
F6 'Activate queue'. With F9 'Refresh', you can see that the number of entries are getting
smaller. The transactions are processed sequentially again.

Symptom 4
o Before deleting the blocking entry from the queue, verify with VF03, FB03 or MIR4 that
the document number does not exist. Check this also with transaction SE16 for table
ETXDCH. Check in the update log (SM13) if the transaction is recorded. So, after having
made sure that the hanging transaction indeed was caused through an update termination,
delete the record from the queue and activate it again. NO record needs to be re-updated to
the external tax interface as the entry was a faulty one.

Symptom 5
o Vertex specific: The Vertex register database (type: ISAM) has a file size limitation of
2GB. If this size is reached, transactions are no longer updated from the queue. The file is
called ''RegPreGn.dbf' and is located under /vertex/DB/Register directory.
It contains all the tax information recorded in Vertex.
 Solution:
Archive data from the Register Database with Vertex specific tools:

o Step 1: Create a control card for the dates you want to archive the data. (Refer to control
card templates provided by Vertex)
o Step 2: Transfer the data from PreReturn to PostReturns.
o Step 3: Unload the data (archive the data from PostReturns)
o Step 4: Purge PostReturn Table
o Step 5: Quit.
o As Reports cannot be run over the archived data, it needs to be reloaded
o if needed for reporting.

Symptom 6
o Create a c:\temp directory on the SAP application server if the translink.reg specifies the
following for the LockFile and IDFile:
"LockFile"="c:\\temp\\verrfc.lck"
"LockTryMax"="180"
"LockTrySleep"="1000"
"IDFile"="c:\\temp\\verrfc.tid"
This is necessary on Windows 2000 machines because there is no c:\temp directory by
default. Vertex delivers the translink.reg entries as above and they need to be edited to a
valid directory.
Windows NT has a c:\temp directory by default, so this issue can only appear with Win2000
and Win2003.
You might also like:
 SAP Note 216952 - Service Data Control Center (SDCC) - FAQ
 SAP Note 216952 - Service Data Control Center (SDCC) - FAQ
 SAP Note 195442 - Language import and Support Packages
 SAP Note 1280664 - Distribution of maintenance certificates: Troubleshooting
 SAP Note 821875 - Security settings in the message server
LinkWithin