Knowledge Management

Question:
Problem Definition
When AP invoices are created on Developmet Box with tax element and posted, the tax portion is not uploaded to the VERTEX dB.
Co. Code : T01B
Plant : COF1
Tax Procedure : TAXUSX
Tax Code : A1
Inbound invoices when recorded with Tax element, TIF_UPDATE_AUDIT_FILE queue doesn’t pick up the tax documents for transfer to vertex db.
The Account Type being used is NVV.
Our ANALYSIS ON the Problem
We have gone through all configurations required for external tax system and they were found to be in line with specifications in document.
The entire program where interaction with external system takes place was debugged. We found that the function module to calculate taxes using external system was being called by the program. But, the functions to update external system are not being called.
The following modifications done for the tax code A1, country US using transaction FTXP:
· Account Type MW1 was modified to calculate tax and transfer at 100% using condition type XPU1.
· The above account type was mapped to G/L Account 110362.
· The tax documents were seen to be forcefully updated to VERTEX.
After the above modification to the tax code, it was seen that the external system does get updated but the updation is by force rather than a normal updation. The program was debugged and it was seen that the consistency check for the external system fails - hence the updation is a forced updation instead of a normal updation.
Inference
1) Before the modification to the tax code, A/c Type NVV was not configured to separate tax portion on Inbound Invoices. The tax portion was combined with product prices and included in the inventory costs. After the modification, since a separate tax account was being used for the tax portion, this got updated on to the external system.
2) It was found that the consistency check on external system fails, hence an enforced update occurs instead of a normal one.
Recommendation/Further action
1) Understand the Business Need to have separate Tax accounts for inbound invoices. Based on such needs and if found necessary, configuration of tax code may be amended.
2) VERTEX DB may need to be configured to handle taxes on inbound invoices.
3) The cause for the Consistency Check failure needs further investigation – this could not be analyzed by IGSI as we do not know how the external system works and what are the processes taking place on the external system.
Note::
I faced the above said problem for a quite sometime.I need help from u people for the probelm ASAP.
Regards
RANGA M
Answer:
this doesn't sound to be a R/3 issue but rather a VERTEX issue. if you manage to prove that the data sent in your download file is clean the VERTEX responsible should be able to pick it up and trigger their DB updates. the way those updates are carried are usually out of our control.
from past experiences i noticed that R/3 usually assumes a very passive attitude in what interfaces is concerned, e.g. when dealing with a Laboratory Information Management System (LIMS) it seats and waits for LIMS to trigger the download of any relevant QM data instead of taking the initiative to send those new records once they are created.
dp