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

Similar Messages

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

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

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

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

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

Withholding taxes not updated when program run in background

Hi,
in a z1 report i do:
SUBMIT z2
VIA JOB lc_jobname
   NUMBER v_jobcount
     WITH p_fecha = p_fecha
     WITH p_file   = v_file_in
     WITH p_e_file = p_efile
     WITH p_client = p_client
     WITH p_test   = p_test
      AND RETURN.
within this z2 report i do:
          PERFORM mrm_invoice_create_call(saplmrm_bapi)     USING     s_rbkpv
                                                       tab_frseg[]
                                                       tab_co[]
                                                       tab_ma[]
                                                       c_rbstat_posted
                                                       space
                                             CHANGING invoicedocnumber
                                                       fiscalyear
                                                       return[]
                                                       f_subrc.
          IF test IS INITIAL.
            COMMIT WORK AND WAIT.
          ELSE.
            ROLLBACK WORK.
          ENDIF.
the question is that if i run z1 report online there is no problem but if
i run z1 report in background, withholding taxes are not calculated.
After debugging this is what i´ve found out:
1.- in PERFORM mrm_invoice_create_call(saplmrm_bapi) there is a call to fm FI_WT_POST IN UPDATE TASK
2.- in FI_WT_POST table WITH_ITEM is updated
i guess this could be due to a delay in updating the table so i´m considering doing a WAIT UP TO X SECONDS.
why is it working in online mode but not in background mode?
any idea?
Best regards.

Hi,
in case someone is interested this is how i solved the question:
i had badi MRM_WT_SPLIT_UPDAT implemented.
in this badi implementation i had this code (among other checks too):
CHECK sy-tcode = 'MIR4' OR sy-tcode = 'MIR7'.
this code avoided the background job case.
It seems that In a background job sy-tcode is empty.
so i just needed to add this:
CHECK sy-tcode = 'MIR4' OR sy-tcode = 'MIR7' OR sy-batch = 'X'.
and then withholding taxes reappeared again.
(so sad, so true... one day of debugging, sigh)
Best regards.
Edited by: Pablo Casamayor on Feb 2, 2012 4:53 PM

Clear Withholding tax data while posting customer invoice

Gurus,
I am trying to post Customer invoice document using FB01 transaction.
If the customer has with holding tax information available in Customer Master the corresponding information is getting posted into invoice document.
Is there any user exit, enhancement or substitution available to clear this with holding tax data.
Please do share if any code examples on this issue.
Appreciate your quick response.
Thanks,
Suneel

Dear AMD008
were you maintain properly in OB40 MWS (out put tax) relevant GL Account
Note: are you using NEW GL please conform me
Regards
shankar

1099: Withholding tax not updating 1099

Hello SAP Guru's,
We updating the Withholding Tax Code under vendor master, then we ran the RFWT0010 program and confirmed the updates were made and now we are trying to re-print the 1099 via S_P00_07000134 and the 1099 still shows the value in the wrong tax code field.
What is the problem?

Just to clarify-
I updated the tax code from 07 to 01 and after updated via the program and try to re-print the 1099, it is still showing as 07. I need it to say 01 like it shows in cleared items.
I need to be able to re-print 1099 using S_P00_07000134 with changes. I thought by executing the program and reprinting via S_P00_07000134, it would do that. It still shows amount in tax code 07 and not 01 which it was changed too.
I appreciate your help!
Edited by: AMS on Apr 26, 2010 5:23 PM

Can any one tell me Regarding Withholding Tax

Actually ,While making a transaction in A/P invoice ,I have activativated the subject to withholding tax in the BP Master Data.And in the item master data tab page for the particular item I have also activated thebwithholding tax liable.So the real problem after providing all the information is the Wht liable it is not changing from no to yes .
My question is how I can TURN YES TO WITH HOLDING TAX LIABLE FIELD CAN ANY ONE please give me systematic steps or whether I have missed out any other place to activate withholding tax.
thankingyou
ARIJIT DEVROY

Hi Arijit,
Are you using the TDS Addon from Citixsys, if so you can get the documentation from ftp://ftp.citixsys.net, use the username national with password national

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>

MIRO - Change Withholding tax data at save dinamically

Hi dear all ,
We will have an Z table to be used as parameter to input an WHT code at MIRO automaticaly.
Some vendors and services must be taxed by certain codes. So we need change the currently code at MIRO WHT screen to new one.
Could I do this thru user exit at MIRO without end user put their hands ? could I change bases too ?
I found user exit 'EXIT_SAPLMR1M_004' but I'm sure if is possible do it !
best regards,
Ale

Try using this BADI along with ABAP person.
MRM_WT_SPLIT_UPDATE
You can write your own code here and sent default whereever you do not wish.
Hemant

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

Regarding Withholding Tax data updation

Similar Messages

Maybe you are looking for