How to run RFWT0020 to update withholding tax data

Can anyone explain the difference between these two options when running RFWT0020 to update withholding tax data? Data Regeneration vs. Changes to Source Tax Code? I can't find any mention of the two options in the program documentation
When I do test runs with the two different options, the program is selecting difference documents to update. If we are just turning on the 1099 functionality now (beginning with the 2011 tax year), should I run the program once with Regeneration mode and once with Changes to Source Tax Code???
Thanks for any advice!
Allison

Hi,
he program enables the withholding tax code to be changed for reconciled and open items with existing withholding tax data. For this, the tax rate of the existing withholding tax data as well as the tax rate of the new withholding tax code must be 0%. The new withholding tax codes are taken from the customer or vendor master data. In the case of extended withholding tax, the withholding tax code is only changed if the related withholding tax categories are the same. The withholding tax base amount is not changed by this procedure.
Recreating or changing the withholding tax data requires that the program first be executed for invoices and then executed for payments in a subsequent step.
When you start the program, the selection screen appears. You can make selections according to vendors, tax code 1, tax code 2 (vendor master record), customers, tax code 1, tax code 2 (customer master record), company codes, document numbers and posting data. The selection determines which items are checked for possible subsequent entries in tables BSEG, BSAK, BSIK, BSAD, BSID, WITH_ITEM.
You can also decide whether only withholding tax data is to be handled for cases where the documents in question contain no withholding tax data. There is no withholding tax data if no withholding tax entries exist for the item selected in table WITH_ITEM (extended withholding tax) or the die withholding tax fields in table BSEG are not filled.
The selection can also be made in test mode. If you do this, no changes are made in the database. You are therefore advised to run the program in test mode initially.
Regards
Aditya

Similar Messages

RFWT0020 withholding tax data - Data Regen vs. Change to Source Tax Code?

Can anyone explain the difference between these two options when running RFWT0020 to update withholding tax data? Data Regeneration vs. Changes to Source Tax Code? I can't find any mention of the two options in the program documentation
When I do test runs with the two different options, the program is selecting difference documents to update. If we are just turning on the 1099 functionality now (beginning with the 2011 tax year), should I run the program once with Regeneration mode and once with Changes to Source Tax Code???
Thanks for any advice!
Allison

Hi,
he program enables the withholding tax code to be changed for reconciled and open items with existing withholding tax data. For this, the tax rate of the existing withholding tax data as well as the tax rate of the new withholding tax code must be 0%. The new withholding tax codes are taken from the customer or vendor master data. In the case of extended withholding tax, the withholding tax code is only changed if the related withholding tax categories are the same. The withholding tax base amount is not changed by this procedure.
Recreating or changing the withholding tax data requires that the program first be executed for invoices and then executed for payments in a subsequent step.
When you start the program, the selection screen appears. You can make selections according to vendors, tax code 1, tax code 2 (vendor master record), customers, tax code 1, tax code 2 (customer master record), company codes, document numbers and posting data. The selection determines which items are checked for possible subsequent entries in tables BSEG, BSAK, BSIK, BSAD, BSID, WITH_ITEM.
You can also decide whether only withholding tax data is to be handled for cases where the documents in question contain no withholding tax data. There is no withholding tax data if no withholding tax entries exist for the item selected in table WITH_ITEM (extended withholding tax) or the die withholding tax fields in table BSEG are not filled.
The selection can also be made in test mode. If you do this, no changes are made in the database. You are therefore advised to run the program in test mode initially.
Regards
Aditya

Extended withholding tax - US Error 7Q 301 updating withholding tax

Cannot get the system to allow me to change the withholding tax information on the accounting documents. Extended withholding tax has been configured. The fields in the line items have been opened to allow changes to the withholding tax data, both for K and S. The venodor has been updated for the withholding tax type and code. Program RFWT0010 does not update any records. The funny thing is it works in the sandbox but not the regular testing dev client. I have compared config and it is the same in both places. Any ideas?
Thank you.

Hi,
Please refer to note 363650, you will see the following information;
C) Change Rules for classical and extended withholding tax If the withholding tax base amount should be changed after a
docment has been paid already, the following steps are required:
For Classical Withholding Tax and only if the withholding tax amount is zero.
Change of withholding tax base amount or withholding tax code of a cleared invoice.
If the withholding tax base amount and/or the withholding tax code needs to be changed after an invoice has been cleared please follow steps;
As you see from the above information the following quotation "only if the withholding tax amount is zero". Is this the case in your scenario?
If a withholding tax amount other than zero has been posted, you cannot change the values via transaction FB02.
Please also review the IMG documentation for transaction OB32 via spro -> Financial accounting -> Financial accounting global settings -> Document -> Line item -> Document change rules, line item. here you will see the following information;
Document Change Rules, Line Item
In this activity, you determine under which circumstances fields within posted documents can be changed.
Note
For a number of fields, the system itself determines that they can no longer be changed after posting. This includes all fields which are central to the principles of orderly accounting, for example, the amount posted and the account.
The system also prevents the update objects from being changed in documents which have already been posted, independent of the document change rules
Thus as you can see from the above description if an amount has been posted to the account you cannot change the fields despite entering in the field in OB32 as changable.
Please also be aware that the important table concerning extended withholding tax is WITH_ITEM. This is where the data found through the button 'Withholding tax Information' in FB03 is held.
(For example in the 'Withholding tax data button' If you click on the help of the field Withholding Code and select the button 'Technical information' you will see that the field name is WT_WITHCD) The fields concerned with same
WITH_ITEM-WT_QSSHB
WITH_ITEM-WT_WITHCD
should be customized in the document change rules (transaction OB32) You will also have to ensure that the posting keys in the document are set to optional (transaction ob41)
Regards
Ravinagh Boni

Create withholding tax data subsequently for reconciled and open items in c

Hi All,
Mine is a US co code and I have a vendor for which invoice and payment documents are posted. After posting the invoice i found that the vendor is subjected to classic withholding tax which i did not calculate when posting invoice, making payments.
Now i have changed the vendor master data with relevant withholding tax details.
I know the program RFWT0020 allows us to create withholding tax data subsequently for reconciled and open items in cases where vendors or customers become liable for withholding tax with a tax rate of 0 %.
It is not working out for me.
Can any body help me on this.
Thanks in advance.

Dear all,
by se38 --> report documentation, You can read carefully the following:
The auxiliary program makes it possible to convert both classic and extended withholding tax data. However, with classic withholding tax, ONLY VENDOR data can be converted.
In addition, the program enables the withholding tax code to be changed for reconciled and open items with existing withholding tax data. For this, the tax rate of the existing withholding tax data as well as the tax rate of the new withholding tax code must be 0%. The new withholding tax codes are taken from the customer or vendor master data. In the case of extended withholding tax, the withholding tax code is only changed if the related withholding tax categories are the same. The withholding tax base amount is not changed by this procedure.
Recreating or changing the withholding tax data requires that the program first be executed for INVOICES and then executed for PAYMENTS in a subsequent step.
I hope this helps You.
Mauri

1099 Withholding Tax data

hi,
how do we delete the withholding tax data for a document after it has been cleared. user has mistakenly entered the invoice as withholding but it should not.
how can we fix this.
Thanks
Sivaram

Hi
you have to reverse and reset clearing the document with FBRA and post again without witholding tax.
BR Tarik

BAPI_INCOMINGINVOICE_CREATE: Withholding tax data is not coming

Dear all,
I am using this BAPI to create Incoming Invoice. I am populating the Headerdata and Itemdata table. Then the invoice which is created doesnt have Withholding Tax Data Information.
Even I tried to populate withtaxdata table, but didnt find the soln.
The code is as shown below:
DATA: t_headerdata LIKE STANDARD TABLE OF bapi_incinv_create_header WITH HEADER LINE,
 t_itemdata LIKE STANDARD TABLE OF bapi_incinv_create_item WITH HEADER LINE,
 t_withtaxdata LIKE STANDARD TABLE OF bapi_incinv_create_withtax WITH HEADER LINE,
 t_return LIKE STANDARD TABLE OF bapiret2 WITH HEADER LINE,
 v_invoicedocnumber LIKE bapi_incinv_fld-inv_doc_no,
 v_fiscalyear LIKE bapi_incinv_fld-fisc_year,
 v_bukrs TYPE bukrs.
DATA: v_knumv LIKE konv-knumv,
 v_kschl LIKE konv-kschl.
LOOP AT itab1.
 tabix = 0.
 IF tabix = 0.
 LOOP AT itab2 WHERE ebeln = itab1-ebeln.
 MOVE-CORRESPONDING itab2 TO itab3.
 APPEND itab3.
 ENDLOOP.
 tabix = 1.
 ENDIF.
 SORT itab3 BY ebelp.
 count = 0.
 v_netamt = 0.
 LOOP AT itab3 WHERE ebeln = itab1-ebeln.
 v_menge = v_menge + itab3-tot_ton.
 v_dmbtr = v_dmbtr + itab3-frt_amt.
 AT END OF ebelp.
 count = count + 1.
 t_itemdata-invoice_doc_item = count.
 READ TABLE itab3 WITH KEY ebeln = itab1-ebeln
 ebelp = itab3-ebelp.
 IF sy-subrc = 0.
 t_itemdata-po_number = itab3-ebeln.
 t_itemdata-po_item = itab3-ebelp.
 t_itemdata-item_amount = v_dmbtr.
 t_itemdata-quantity = v_menge.
 t_itemdata-po_unit = itab1-meins.
 t_itemdata-item_text = itab1-text.
 t_itemdata-tax_code = 'V0'.
*Condition Type
 SELECT SINGLE knumv
 FROM ekko
 INTO v_knumv
 WHERE ebeln = itab1-ebeln.
 IF sy-subrc = 0.
 SELECT SINGLE kschl
 FROM konv
 INTO v_kschl
 WHERE knumv = v_knumv
 AND kposn = itab3-ebelp
 AND ( ( kschl = 'FRC1' ) OR ( kschl = 'FRB1' ) ).
 IF sy-subrc = 0.
 t_itemdata-cond_type = v_kschl.
 ENDIF.
 ENDIF.
 APPEND t_itemdata.
 CLEAR: v_menge, v_dmbtr.
 ENDIF.
 ENDAT.
 v_netamt = v_netamt + itab3-frt_amt.
 ENDLOOP.
 t_headerdata-invoice_ind = 'X'.
 t_headerdata-doc_date = itab1-inv_date.
 t_headerdata-pstng_date = itab1-budat.
 t_headerdata-ref_doc_no = itab1-refno.
 SELECT SINGLE bukrs INTO v_bukrs FROM ekko WHERE ebeln = itab1-ebeln.
 IF sy-subrc = 0.
 t_headerdata-comp_code = v_bukrs.
 ENDIF.
 t_headerdata-currency = itab1-waers.
 t_headerdata-gross_amount = v_netamt.
 t_headerdata-bline_date = itab1-budat.
 t_headerdata-item_text = itab1-text.
 t_headerdata-diff_inv = itab1-lifnr.
 t_headerdata-business_place = '1000'.
 APPEND t_headerdata.
 t_withtaxdata-wi_tax_type = 'C1'.
 t_withtaxdata-wi_tax_code = 'C1'.
 t_withtaxdata-wi_tax_base = v_netamt.
 APPEND t_withtaxdata.
 t_withtaxdata-wi_tax_type = 'C2'.
 t_withtaxdata-wi_tax_code = 'C2'.
 t_withtaxdata-wi_tax_base = v_netamt.
 APPEND t_withtaxdata.
 t_withtaxdata-wi_tax_type = 'C3'.
 t_withtaxdata-wi_tax_code = 'V3'.
 t_withtaxdata-wi_tax_base = v_netamt.
 APPEND t_withtaxdata.
 CLEAR: v_netamt.
 break bsfdev.
 CALL FUNCTION 'BAPI_INCOMINGINVOICE_CREATE'
 EXPORTING
 headerdata = t_headerdata
 ADDRESSDATA =
 IMPORTING
 invoicedocnumber = v_invoicedocnumber
 fiscalyear = v_fiscalyear
 TABLES
 itemdata = t_itemdata
 ACCOUNTINGDATA =
 glaccountdata =
 MATERIALDATA =
 TAXDATA =
 withtaxdata = t_withtaxdata
 VENDORITEMSPLITDATA =
 return = t_return
 CLEAR errflag.
 LOOP AT t_return.
 IF t_return-type EQ 'E'.
 it_message-text = 'Error in function'.
 it_message-text1 = t_return-message.
 it_message-po_number = itab1-ebeln.
 it_message-exnum = itab1-exnum.
 APPEND it_message.
 errflag = 'X'.
 ELSE.
 ENDIF.
 ENDLOOP.
 IF errflag IS INITIAL.
 COMMIT WORK AND WAIT.
 IF sy-subrc NE 0.
 it_message-po_number = itab1-ebeln.
 it_message-text = 'Error in updating'.
 it_message-text1 = t_return-message.
 APPEND it_message.
 EXIT.
 ELSE.
*Fill Temporary table
 LOOP AT itab3.
 IF v_invoicedocnumber <> space.
 it_message1-po_number = itab3-ebeln.
 it_message1-po_item = itab3-ebelp.
 it_message1-doc_number = itab3-belnr.
 it_message1-invoicedocno = v_invoicedocnumber.
 it_message1-exnum = itab1-exnum.
 APPEND it_message1.
 zpending_challan-po_number = itab3-ebeln.
 zpending_challan-po_item = itab3-ebelp.
 zpending_challan-doc_number = itab3-belnr.
 zpending_challan-exnum = itab3-exnum.
 zpending_challan-invoicedocno = v_invoicedocnumber.
 zpending_challan-menge = itab3-tot_ton.
 zpending_challan-dmbtr = itab3-frt_amt.
 zpending_challan-budat = itab3-budat.
 INSERT zpending_challan FROM zpending_challan.
 COMMIT WORK.
 CLEAR: zpending_challan.
 ENDIF.
 ENDLOOP.
 ENDIF.
 ENDIF.
 IF errflag IS INITIAL.
 count = count + 1.
 CONCATENATE count 'Purchase Order Posted Out of ' no_recs1
 INTO text1 SEPARATED BY space.
 CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
 EXPORTING
PERCENTAGE = 0
 text = text1
 CONCATENATE 'Invoice Document No' v_invoicedocnumber 'generated'
 INTO text1 SEPARATED BY space.
 CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
 EXPORTING
PERCENTAGE = 0
 text = text1
 ENDIF.
 CLEAR: t_headerdata[], t_headerdata,
 t_itemdata[], t_itemdata,
 itab3[], itab3.
ENDLOOP.
Kindly help. Its very urgent.
Thanks.
Vinod.

Not used any more

Problem creating A/R Invoice with Withholding tax data via DI-Server

Hi!
Using the following SOAP Request to the DI-Server, I wanted to create an A/R Invoice having a withholding tax data but it always respond with an error saying
Total taxable amount of all rows exceeds the base amount [INV5.TaxbleAmnt][line: 1]
SOAP Request:
<?xml version="1.0" encoding="UTF-16"?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Header>
 <SessionID>203A3C01-7808-4638-8322-2307DF3C0F8F</SessionID>
</env:Header>
<env:Body>
 <dis:Add xmlns:dis="http://www.sap.com/SBO/DIS">
 <Service>InvoicesService</Service>
 <Document>
 <DocType>dDocument_Items</DocType>
 <HandWritten>tNO</HandWritten>
 <DocDate>2010-02-08</DocDate>
 <DocDueDate>2010-02-08</DocDueDate>
 <TaxDate>2010-02-08</TaxDate>
 <VatDate>2010-02-08</VatDate>
 <CardCode>NPI</CardCode>
 <Comments>test di-server soap message 1</Comments>
 <DocumentLines>
 <DocumentLine>
 <ItemCode>TRC</ItemCode>
 <Quantity>1</Quantity>
 <Price>1000</Price>
 <TaxCode>OVAT</TaxCode>
 <VatGroup>OVAT</VatGroup>
 <TaxLiable>tYES</TaxLiable>
 <WTLiable>tYES</WTLiable>
 </DocumentLine>
 </DocumentLines>
 <WithholdingTaxDataCollection>
 <WithholdingTaxData>
 <WTCode>C140</WTCode>
 <TaxableAmount>1000</TaxableAmount>
 <WTAmount>100</WTAmount>
 </WithholdingTaxData>
 </WithholdingTaxDataCollection>
 </Document>
 </dis:Add>
</env:Body>
</env:Envelope>
OVAT rate above is 10%.
The withholding tax code C140 is setup as
rate=10,
Category=Payment,
Base Type=Net,
% Base Amount = 100,
Rounding Type = Commercial Values.
We are using the New Zealand/Australia localization in SAP B1 2007A PL49.
The above code can be successful only if I set the <WithholdingTaxDataCollection> node to:
 <WithholdingTaxDataCollection>
 <WithholdingTaxData>
 <WTCode>C140</WTCode>
 <TaxableAmount>0</TaxableAmount>
 <WTAmount>100</WTAmount>
 </WithholdingTaxData>
 </WithholdingTaxDataCollection>
setting TaxableAmount equal to 0 which is not desired.
Can anyone extend me some help, please?
Thanks.

Albert,
Did you try adding this via the DI API and not the DI Server? Do you get the same error? Please see this SAP Note ...
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=0001303019
Eddy

Note for TW withholding tax data

Hi,
Who knows is the note about the latest uploading format of withholding tax data for Taiwan published?

Hello
The SAP note number is 1662886 -2011 Changes on Taiwan Tax Medium File.
The note is currently in state "Inprocess" and have not yet been released.
Please check the sap service market place "www.service.sap.com/notes" for the note release status.
Thanks and Kind Regards
Ramana

How to clear line items with withholding tax manually

hi Experts,
i posted a vendor invoice with withholding tax and i made payment as well but not through f-58.
now i wanted to clear these two through f-44 but it gives the message withholding tax information ignored and didnt display the invoice as open item.
how do i clear both the trasactions
regards
suresh

hi Praisty,
thanks for the reply
i have a second opinion on your statement that no matter whatever tcode you use for payment it will clear the open item. Even in F-58, if u make partial payment it will not clear you open item. But i didnt use f-58 as i said earlier.
i used FBV1 for parking the document through which i entered the payment details...ofcourse it doesnt have the option for clearing the open items, cheque printing and it will not update your cheque register. i posted the parked document through FBV0. for all practical purposes, this is my payment document but it didnt clear my open item, in order to clear it i now used f-44.
regards
suresh

Report RFWT0010 to update withholding tax in open items

Hi gurus!
I'm facing a problem with report RFWT0010 after modifying withholding tax information in the vendor master record.
If I delete a complete line (Withholding Tax Type, W/Tax Code, Liable and so on) when I run report RFWT0010 open items are pulled and updated correctly.
However, if I have a scenario in which I only need to modify the Withholding Tax Code (leaving WIthholding Tax Type and Liable Flag like they were before) when I run report RFWT0010 no open items are pulled.
Can anyone indicate me if RFWT0010 is meant only for withholding tax type changes?? or is it a program error??
Thanks!
Federico

Withholding tax is not supported by SAP here...

Regarding Withholding Tax data updation

I have posted a AB document using FB1K.Whenever i go to FB1K transaction & put the vendor and click on Process open items,i am getting 1 pop-up saying "Withholding tax ignored". Then i will post the open items. This will create a AB document type.
Then if i go to FB03 for this document,there will be zero amount updated for both the line items. This is happening eventhough the vendor is liable for Withholding tax.
But if i post any other document like KR,RE,KG,its properly updating the withholding tax.
Can someone help me how AB document is getting updated with zero amount.
Thanks,
Aparna.

check with holding tax posting configration in SPRO
1)Define Withholding Tax Type for Payment Posting
2)Define Withholding Tax Type for Invoice Posting

When updating withhold tax window error---"This Property Cannot be Updated"

Dear All,
We have upgraded SAP 8.8 PL14 from SAP 2007B. With respect to TDS, we have upgraded based on the TDS Utiltiy Upgrade. Everything upgraded Properly. But, when we try to edit or change on Withholding tax definition or TDS account, an error is coming "This Property Cannot be Updated". Becoz of this we are not able to continue the entry on Particular Section. We are not able to add new WH Code also, since the same error is coming.
Pl help and sugges how to solve this.
Thanks.
Komanduri

DEAR
if u still face teh error then i would request you to please raise a support ticket for ant Case related to TDS as that would be supported by sap only however the other way around but that would not be correct is to make a new WT code with the differnt code but by doing this when the user would sit down for reconciliation he would not be able to do so as the error would be somewhat "cannot use two WT code category
Regards,
Manish

F110: how to pay an invoice with Withholding Tax and a credit memo?

Hi All,
in my SAP I've defined a Withholding Tax type for Payment Posting.
I've posted a vendor invoice with with Withholding Tax.
Later I've posted a credit memo with Withholding Tax which must compensate the prevuois invoice.
When I launch t.code F110, SAP, in the right manner, proposes to pay the invoice less the amount of the credit memo.
But the calculation of the Withholding Tax (that it should post al the payment time) is wrong: SAP proposes to post the amount of the Withholding Tax recorded in the table WITH_ITEM at the moment of the posting of the invoice. Instead, from it, SAP should detract the amount of the Withholding Tax recorded in the table WITH_ITEM at the moment of the posting of the credit memo.
Why does SAP doesn't consider the amount of the Withholding Tax of the credit memo?
Could anyone help me?
Thanks

Dear Rossi,
if You defined the WT TYPE at the payment time this means that the WT amount will be calculated at posted during the F110 run as per the invoice as per the credit memo.
If they are the same amounts and refer to the same wt type and code, when You run F110, they should match even for the WT calculation. It is clear that if You inserted manually the WT base amount or the WT amount into the invoice, the system will not do any automatic calculation but it will use these amounts that can be different from the one auto matically calculated by the system for the credit memo.
I hope this can help You.
Mauri

How to create A/R Invoice having Withholding Tax Data using DI-Server?

Hi Experts,
I want to create an A/R Invoice having a Withholding Tax line
through DI-Server (SAP Business One 2005B PL43) using the following
SOAP Request (Method 1 and Method 2) but both generated an 'Invalid
XML' error response. If I exclude the WithholdingTaxData tag (or the
WithholdingTaxDataCollection tag) from the SOAP request, the invoice
is successfully created but without the Withholding Tax entry in the
table INV5.
I've had success in the past using the "<SerialNumbers>"
and "<DocumentsAdditionalExpenses>".

In the SOAP Requests below, what is wrong with the usage of
"<WithholdingTaxData>" or
"<WithholdingTaxDataCollection>"?
Is it possible at all to create a document having Withholding Tax
entries using the DI-Server SOAP Request?
Thank you very much.
 

Method 1:
SOAP REQUEST (Using AddObject command):
<?xml version="1.0" encoding="UTF-16"?> <env:Envelope
xmlns:env="<A HREF="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</A>"> <env:Header> <SessionID>08C5BB21-34E3-468E-952F-EEC1CBE19272</SessionID> </env:Header> <env:Body> <dis:AddObject
xmlns:dis="<A HREF="http://www.sap.com/SBO/DIS">http://www.sap.com/SBO/DIS</A>"> <BOM><BO> <AdmInfo> <Object>oInvoices</Object> </AdmInfo> <Documents> <row> <DocDate>20090520</DocDate> <DocDueDate>20090619</DocDueDate> <TaxDate>20090520</TaxDate> <DocCurrency>EUR</DocCurrency> <CardCode>MULTICURRBP</CardCode> <ContactPersonCode>0</ContactPersonCode> <Comments>Withholding
Tax
Liable</Comments> <SalesPersonCode>1</SalesPersonCode> </row> </Documents> <Document_Lines> <row> <ItemCode>MON001</ItemCode> <Quantity>1.00</Quantity> <WarehouseCode>cag01</WarehouseCode> <UnitPrice>65.57</UnitPrice> <Currency>EUR</Currency> <VatGroup>SO</VatGroup> <WTLiable>tYES</WTLiable> </row> </Document_Lines> <WithholdingTaxData> <row> <WTCode>S<WTCode> <WTAmountFC>14.43<WTAmountFC> <TaxableAmountFC>65.57<TaxableAmountFC> <GLAccount>207032<GLAccount> </row> </WithholdingTaxData> </BO></BOM> </dis:AddObject> </env:Body> </env:Envelope>
 

SOAP RESPONSE (Using AddObject command):
<?xml version="1.0"?> <env:Envelope
xmlns:env="<A HREF="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</A>"> <env:Body> <env:Fault> <env:Code><env:Value>env:Sender</env:Value></env:Code> <env:Reason><env:Text
xml:lang="en">Invalid
XML</env:Text></env:Reason> <env:Detail> <ErrorList> <Error>System
Id = 18023032, Line Number = 1, Column Number = 1064, Description =
Expected end of tag
'GLAccount'</Error> </ErrorList> </env:Detail> </env:Fault> </env:Body> </env:Envelope>
 

Method 2:
SOAP REQUEST (Using Add Service command):
<?xml version="1.0" encoding="UTF-16"?> <env:Envelope
xmlns:env="<A HREF="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</A>"> <env:Header> 
<SessionID>1F6C7E11-CC5B-A5F3-0206-D1F4A8B9D84A</SessionID> </env:Header> <env:Body> <dis:Add
xmlns:dis="<A HREF="http://www.sap.com/SBO/DIS">http://www.sap.com/SBO/DIS</A>"> <Service>InvoicesService</Service> <Document> <DocDate>2009-05-20</DocDate> <DocDueDate>2009-06-19</DocDueDate> <TaxDate>2009-05-20</TaxDate> <DocCurrency>EUR</DocCurrency> <CardCode>MULTICURRBP</CardCode> <ContactPersonCode>0</ContactPersonCode> <Comments>Withholding
Tax
Liable</Comments> <SalesPersonCode>1</SalesPersonCode> <DocumentLines> <DocumentLine> <ItemCode>MON001</ItemCode> <Quantity>1.00</Quantity> <WarehouseCode>cag01</WarehouseCode> <UnitPrice>65.57</UnitPrice> <Currency>EUR</Currency> <VatGroup>SO</VatGroup> <WTLiable>tYES</WTLiable> </DocumentLine> </DocumentLines> <WithholdingTaxDataCollection> <WithholdingTaxData> <WTCode>S<WTCode> <WTAmountFC>14.43<WTAmountFC> <TaxableAmountFC>65.57<TaxableAmountFC> <GLAccount>207032<GLAccount> </WithholdingTaxData> </WithholdingTaxDataCollection> </Document> </dis:Add> </env:Body> </env:Envelope>
 

SOAP RESPONSE (Using Add Service command):
<?xml version="1.0"?> <env:Envelope
xmlns:env="<A HREF="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</A>"> <env:Body> <env:Fault> <env:Code><env:Value>env:Sender</env:Value></env:Code> <env:Reason><env:Text
xml:lang="en">Invalid
XML</env:Text></env:Reason> <env:Detail> <ErrorList> <Error>System
Id = 134112056, Line Number = 1, Column Number = 1076, Description =
Expected end of tag
'GLAccount'</Error> </ErrorList> </env:Detail> </env:Fault> </env:Body> </env:Envelope>

Hi Experts,
My apologies for the truncated message.
Here's the full one.
I want to create an A/R Invoice having
a Withholding Tax line through DI-Server (SAP Business One 2005B
PL43) using the following SOAP Request (Method 1 and Method 2) but
both generated an 'Invalid XML' error response. If I exclude the
WithholdingTaxData tag (or the WithholdingTaxDataCollection tag) from
the SOAP request, the invoice is successfully created but without the
Withholding Tax entry in the table INV5.
I've had success in the past using the
"<SerialNumbers>" and
"<DocumentsAdditionalExpenses>".

In the SOAP Requests below, what is
wrong with the usage of "<WithholdingTaxData>" or
"<WithholdingTaxDataCollection>"?
Is it possible at all to create a
document having Withholding Tax entries using the DI-Server SOAP
Request?
Thank you very much.
 
Method 1:
 
SOAP REQUEST (Using AddObject command):
<?xml version="1.0"
encoding="UTF-16"?>
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
 <env:Header>
 <SessionID>08C5BB21-34E3-468E-952F-EEC1CBE19272</SessionID>
 </env:Header>
 <env:Body>
 <dis:AddObject
xmlns:dis="http://www.sap.com/SBO/DIS">
 <BOM><BO>
 <AdmInfo>
 <Object>oInvoices</Object>
 </AdmInfo>
 <Documents>
 <row>
 <DocDate>20090520</DocDate>
 <DocDueDate>20090619</DocDueDate>
 <TaxDate>20090520</TaxDate>
 <DocCurrency>EUR</DocCurrency>
 <CardCode>MULTICURRBP</CardCode>
 <ContactPersonCode>0</ContactPersonCode>
 <Comments>Withholding Tax
Liable</Comments>
 <SalesPersonCode>1</SalesPersonCode>
 </row>
 </Documents>
 <Document_Lines>
 <row>
 <ItemCode>MON001</ItemCode>
 <Quantity>1.00</Quantity>
 <WarehouseCode>cag01</WarehouseCode>
 <UnitPrice>65.57</UnitPrice>
 <Currency>EUR</Currency>
 <VatGroup>SO</VatGroup>
 <WTLiable>tYES</WTLiable>
 </row>
 </Document_Lines>
 <WithholdingTaxData>
 <row>
 <WTCode>S<WTCode>
 <WTAmountFC>14.43<WTAmountFC>
 <TaxableAmountFC>65.57<TaxableAmountFC>
 <GLAccount>207032<GLAccount>
 </row>
 </WithholdingTaxData>
 </BO></BOM>
 </dis:AddObject>
 </env:Body>
</env:Envelope>
 

SOAP RESPONSE (Using AddObject
command):
<?xml version="1.0"?>
<env:Envelope
xmlns:env="http://www.w3.org/2003/05/soap-envelope">
 <env:Body>
 <env:Fault>
 <env:Code><env:Value>env:Sender</env:Value></env:Code>
 <env:Reason><env:Text
xml:lang="en">Invalid XML</env:Text></env:Reason>
 <env:Detail>
 <ErrorList>
 <Error>System Id = 18023032,
Line Number = 1, Column Number = 1064, Description = Expected end of
tag 'GLAccount'</Error>
 </ErrorList>
 </env:Detail>
 </env:Fault>
 </env:Body>
</env:Envelope>
 

 

Method 2:
 

SOAP REQUEST (Using Add Service
command):
<?xml version="1.0"
encoding="UTF-16"?>
<env:Envelope
xmlns:env="http://www.w3.org/2003/05/soap-envelope">
 <env:Header>

<SessionID>1F6C7E11-CC5B-A5F3-0206-D1F4A8B9D84A</SessionID>
 </env:Header>
 <env:Body>
 <dis:Add
xmlns:dis="http://www.sap.com/SBO/DIS">
 <Service>InvoicesService</Service>
 <Document>
 <DocDate>2009-05-20</DocDate>
 <DocDueDate>2009-06-19</DocDueDate>
 <TaxDate>2009-05-20</TaxDate>
 <DocCurrency>EUR</DocCurrency>
 <CardCode>MULTICURRBP</CardCode>
 <ContactPersonCode>0</ContactPersonCode>
 <Comments>Withholding Tax
Liable</Comments>
 <SalesPersonCode>1</SalesPersonCode>
 <DocumentLines>
 <DocumentLine>
 <ItemCode>MON001</ItemCode>
 <Quantity>1.00</Quantity>
 <WarehouseCode>cag01</WarehouseCode>
 <UnitPrice>65.57</UnitPrice>
 <Currency>EUR</Currency>
 <VatGroup>SO</VatGroup>
 <WTLiable>tYES</WTLiable>
 </DocumentLine>
 </DocumentLines>
 <WithholdingTaxDataCollection>
 <WithholdingTaxData>
 <WTCode>S<WTCode>
 <WTAmountFC>14.43<WTAmountFC>
 <TaxableAmountFC>65.57<TaxableAmountFC>
 <GLAccount>207032<GLAccount>
 </WithholdingTaxData>
 </WithholdingTaxDataCollection>
 </Document>
 </dis:Add>
 </env:Body>
</env:Envelope>
 

SOAP RESPONSE (Using Add Service
command):
<?xml version="1.0"?>
<env:Envelope
xmlns:env="http://www.w3.org/2003/05/soap-envelope">
 <env:Body>
 <env:Fault>
 <env:Code><env:Value>env:Sender</env:Value></env:Code>
 <env:Reason><env:Text
xml:lang="en">Invalid XML</env:Text></env:Reason>
 <env:Detail>
 <ErrorList>
 <Error>System Id =
134112056, Line Number = 1, Column Number = 1076, Description =
Expected end of tag 'GLAccount'</Error>
 </ErrorList>
 </env:Detail>
 </env:Fault>
 </env:Body>
</env:Envelope>

How do I move prior years' Turbo Tax data from Snow Leopard computer to my new Mavericks mini?

I bought a new mini, but don't know how to transfer my old Turbo Tax returns/history/files over from
my iMac (Snow Leopard) to the mini (Mavericks). I ended up doing my 2013 taxes on my old computer
because I needed to have 2012 data imported for 2013 returns, but I would like to get all of
my Turbo Tax history on the mini. HELP (please!) Thank you!

This reminds me of an anecdote that I used to tell people to describe certain aspects of computer media and is somewhat relevant here. The story is oobviously 20 years old, and the facts have been changed to make my point:
My wife recently came back from Italy with a VHS cassette of an Italian movie that she wanted to watch on our VHS player at home.
I sent the cassette out to a local video conversion store, so that they could convert the VHS tape from PAL to NTSC.
When my wife played the newly converted tape on our home VHS player, she exclaimed: "But it is still in Italian!"
I have no experience with Turbo Tax. But I suspect that in prior years (especially prior to 2007) it was coded in PowerPC code.
In 2007, Apple converted its entire line of computers to the Intel CPU (from the PowerPC CPU), but in order to allow its existing user base to continue to use its PowerPC software, they included a transparent emulation layer in Mac OS X Tiger (Intel), Leopard, and optionally in Snow Leopard, called Rosetta.
Rosetta allowed users to continue to use their library of PowerPC apps without much problem.
Due to the expiration of its third party license, Rosetta is no longer included in Lion, Mt. Lion or Mavericks.
Moral of the Story: If the earlier versions of Turbo Tax are not Intel compliant, they will not run on your new Mac Mini, unless you install Snow Leopard Server ($20 from the Apple Store, by telephone orders only; part number: MC588Z/A) installed into Parallels ($79 retail).
If the latest version of Turbo Tax will open older Turbo Tax data files, this may not be a problem for you.
That is how I am able to continue to access my older Quicken Deluxe 2002 data files when necessary.

How to run RFWT0020 to update withholding tax data

Similar Messages

Maybe you are looking for