Modelo 340 - Correction invoices (opkey D)

Hello,
In modelo 340 for VAT - Spain: in cases of correction invoices (operation key D), in the correction invoice row how can I indicate the invoice nº of the original modified invoice? Field IDINVMD of report RFIDESM340 is for this purpose?
how do I have to customize to get this information in the 340?
I will regard with points as it is urgently needed
Thanks and regards,
Victor

page 23 MODELO_340_2009_EN.pdf note 1304756
Key D u2013 Correction invoice
The correction invoices are updated in the Model 340 with the key D. In order to be identified
is necessary used or a document type or a tax indicator or both. The normal use is a document type
because the correction invoices must have a range and this is achieved in SAP using a document
type different form the one used in the invoices.
The invoices and the tickets must have the operation key A and B (see that part) due to it is
not possible to use a key different because the third party could not be identified and also because it
makes no sense a correction invoice from a summary posting (yes for individual postings).
If you want that the reversal documents will be considered as correction invoices is necessary
customized the document type with a document type different than the original one and included this
class in the operation key table with key u201CDu201D.
Hope it clarifies
kind Regards
davide

Similar Messages

Modelo 340 RFIDESM340 no operation key "I" in tax report

Dear All,
From 2011 we have to change the parametrization for the presentation to the Spanish tax authorities for the MODELO 340 (RFIDESM340)
In our company we decided to create new tax codes for 2011, 3 Tax codes of acquisitions of goods/svs, to their proper value in the EU. Code (5, 7 or 8)
One of the requirements its that all operations related to these 3 new indicators have to drag operation key "I" (Latin capital letter I), indicating that they are a operating reverse charge invoice.
What i have done, its to inform in transaction FTXP, the new tax codes with
a.ESA Acquisition Tax Cred at 18%
ESE Acquisition Tax Deb. 18%
b. Do not define the line of 0% VST, since they no longer should appear the supplier's invoice without the VAT
and Exclude VAT charged line of Model 340, excluding in the transaction lor the GL account at TCODE_RFIDESM340 - TRANSACTION CODE FOR RFIDESM340
but still, i get the report with the operation key in blank, can you please tell me if i am missing somethig?
thanks in advance

I was missing a entry in custo
Financial accounting  Global settings  Tax on sales and purchases  Basic Settings  Spain  Define operations keys for Model 340

Intracomunitary Acquisitions in Modelo 340 for Spain

Hi,
The guide of the transaction for modelo 340 in Spain, says that it is necessary to run transaction without ESA operations. If we run 340 modelo without ESA operations, for the intracomunitary acquisitions(that have the 16% on debit and the 16%on credit), in modelo 340 only appears the 16% of the debit. The real rate ("cuota") should be 0% and not 16%, isn't it?
Thank you very much,
Ariana
Edited by: Ariana Landaluce on Jun 9, 2009 7:44 PM
Edited by: Ariana Landaluce on Jun 10, 2009 10:05 AM

Hi Madhu Garu
Many thanks for your suggestion.
we had successfully implemented the notes, but had the file format layout problem.
we are still in contact with SAP,
These are the errors we are getting:-
1) VATDATE
It is correct for u201CCLAVE TIPO DE LIBROu201D = E because the VATDATE =
Doc.date but it is incorrect in the case u201CCLAVE TIPO DE LIBROu201D = R
because the VATDATE = Posting date.
2) Tax base amount (BASE IMPONIBLE) in case intracomunitario P has to
be = u201CIMPORTEu201D total.
3) We need two column:
1.- Cuota del impuesto: S1, S2, S3, N1,N2,N3
2.- Cuota deducible: Only S1, S2 S3
4) We need a sequential number of the vat register.
5) Problem during the upload in web site www4.aeat.es with error u201CEl
fichero contiene registros de longitude incorectau201D .
once again Thank you very much for your co-opeartion
Kind Regards
Ravi.K

Modelo 340 España. Compra proveedor extranjero

Buenos días,
tengo dudas en el registro de operaciones de compra a un proveedor extranjero y que estas se trasladen correctamente al fichero del modelo 340.
Supongamos el siguiente ejemplo:
Compro a un proveedor extranjero por 100.000€
El transitario declara una base de 130.000€. Gastos de gestión del transitario de 1.000€.
¿alguien me puede detallar como introducir las operaciones y que estas queden correctamente reflejadas en el modelo 340?
Gracias

Hi,
This is SAP Business one forum for English user. Please find correct forum and repost your question to get quick answer.
Kindly close this thread here.
Thanks & Regards,
Nagarajan

AR correction invoice - other warehouse in "should be"

Hi all!
I've got a problem with adding correction invoice with changed warehouse.
My client sells fruits to a coustomer from warehouse A (goods). Customer sends back part or all goods because they are perished.
We need to do AR Correction invoice, but perished fruits should be received on warehouse B (perished fruits).
When I'm trying to change warehouse in "should be" inn AR Correction invoice I get this message:
"Warehouse code must be the same on corresponding "was" and "should be" rows.
Did anyone got the same problem and solved it?
Any ideas?
Thanks in advance!

I believe you need two transactions to reflect your business process. First is the AR correction invoice to the same warehouse. Then an Inventory Transaction to move them to the right warehouse.
Thanks,
Gordon

Correction Invoice - Poland/Hungary

We are facing the following problem in Correction Invoice (RK)
eg: Sales Order /Delivery/ Invoice (A) created for 100 pieces. Due to the material fault 50 pieces are returned and the credit note (B)is given for that 50 pieces. Later after few weeks we would like to give the price correction for the remaining pieces.
Here, I create the RK , with reference to the original Invoice (A). By default you get two line is the RK , First the original line from the Invoice and the second line for making any corrections. The Issue is the original line has 100 pieces and this cannot be changed. So any corrections you make refers to 100 pieces , but not for 50 pieces. as the credit (B) to the customer had already been given to the customer for the return of 50 pieces. This results in totally wrong values .
Please let me know if there is any possibility that the quantity 100 can be changed to reflect only 50 pieces. or How can this scenario be handled?
Regards,
Rahul

                    vCorrReversal.Lines.ItemCode = "00012"
                    'vCorrReversal.Lines.Price = 10
                    'vCorrReversal.Lines.Quantity = 10
                    vCorrReversal.Lines.CorrectionInvoiceItem = SAPbobsCOM.BoCorInvItemStatus.ciis_ShouldBe
                    vCorrReversal.Lines.BaseType = 165
                    vCorrReversal.Lines.BaseEntry = vDocEntry
                    vCorrReversal.Lines.BaseLine = 0
                    'vCorrReversal.Lines.LineTotal = 100
                    vCorrReversal.Lines.Add()
                    vCorrReversal.Lines.ItemCode = "00012"
                    'vCorrReversal.Lines.Price = 9
                    'vCorrReversal.Lines.Quantity = 10
                    vCorrReversal.Lines.CorrectionInvoiceItem = SAPbobsCOM.BoCorInvItemStatus.ciis_Was
                    vCorrReversal.Lines.BaseType = 165
                    vCorrReversal.Lines.BaseEntry = vDocEntry
                    vCorrReversal.Lines.BaseLine = 0
                    'vCorrReversal.Lines.LineTotal = 90
                    RetVal = vCorrReversal.Add
                    'Check the result
                    If RetVal <> 0 Then
                        vCmp.GetLastError(ErrCode, ErrMsg)
                        MsgBox(ErrCode + " " + ErrMsg)
                    Else
                        vCmp.GetNewObjectCode(vDocEntry)
                    End If
                End If

Correction Invoice and "invalid document structure" problem

Hello!
Can anybody explain what properties are obligatory for correction invoices? I'm trying to add() one and it always say -5002: invalid document structure.
In the CSI1 table I see linenum has to be unique, every baseline is twice. Do I make any stupid mistake? If so - where? What's wrong? Something is ommitted?...
                                                                                Thanks in advance!
                                                                                This is a snippet (two loops are unnecessary, I was looking for other ways). I'm trying just to zero the invoice. Should quantity in was lines be negative? It does not matter - everytime -5002...
     @Test
     public void testSAPCorrectionInvoice() throws SBOCOMException {
          ICompany company = sapConnector.getCompany();
          // Integer srcDocEntry = 6457;
          Integer srcDocEntry = 7084;// this one has no batches
          logger.debug("Creating correction to: " + srcDocEntry);
          // source doc
          IDocuments srcDoc = SBOCOMUtil.getDocuments(company,
                    SBOCOMConstants.BoObjectTypes_Document_oInvoices, srcDocEntry);
          logger.debug("srcDoc: " + srcDoc.getDocObjectCode() + ", "
                    + srcDoc.getDocNum());
          IDocuments sapDoc = SBOCOMUtil.newDocuments(company,
                    SBOCOMConstants.BoObjectTypes_Document_oCorrectionInvoice);
          // header:
          sapDoc.setHandWritten(SBOCOMConstants.BoYesNoEnum_tNO);
          sapDoc.setSeries(317);
          sapDoc.setDocType(SBOCOMConstants.BoDocumentTypes_dDocument_Items);
          sapDoc.setCardCode(srcDoc.getCardCode());
          sapDoc.setCardName(srcDoc.getCardName());
          sapDoc.setAddress(srcDoc.getAddress());
          String federalTaxID = srcDoc.getFederalTaxID();
          if (federalTaxID.length() > 0)
               sapDoc.setFederalTaxID(federalTaxID);
          sapDoc.setDocDate(new Date());
          sapDoc.setDocDueDate(new Date());
          sapDoc.setSalesPersonCode(srcDoc.getSalesPersonCode());
          sapDoc.setDocCurrency(srcDoc.getDocCurrency());
          sapDoc.setPaymentGroupCode(srcDoc.getPaymentGroupCode());
          sapDoc.setTransportationCode(srcDoc.getTransportationCode());
          sapDoc.setContactPersonCode(srcDoc.getContactPersonCode());
          // sapDoc.setDiscountPercent(0.0);
          sapDoc.setComments("zwrot towaru");
          // sapDoc.setDocTotal(0.0);
          sapDoc.setVatDate(srcDoc.getVatDate());
          // items
          IDocument_Lines lines = sapDoc.getLines();
          int lineno = 0;
          IDocument_Lines srcLines = srcDoc.getLines();
          for (int i = 0; i < srcLines.getCount(); i++) {
               srcLines.setCurrentLine(i);
               logger.debug("line " + i + ", item: " + srcLines.getItemCode());
               if (lineno > 0)
                    lines.add();
               lines.setCurrentLine(lineno++);
               lines.setItemCode(srcLines.getItemCode());
               lines.setItemDescription(srcLines.getItemDescription());
               lines.setWarehouseCode(srcLines.getWarehouseCode());
               lines.setPrice(srcLines.getPrice());
               lines.setDiscountPercent(srcLines.getDiscountPercent());
               lines.setTaxCode(srcLines.getTaxCode());
               lines.setBaseEntry(srcDocEntry);
               lines.setBaseType(srcDoc.getDocObjectCode());
               lines.setBaseLine(i);
               lines.setVatGroup(srcLines.getVatGroup());
               lines
                         .setCorrectionInvoiceItem(SBOCOMConstants.BoCorInvItemStatus_ciis_Was);
               double quantity_was = srcLines.getQuantity();
               lines.setQuantity(quantity_was);
          for (int i = 0; i < srcLines.getCount(); i++) {
               srcLines.setCurrentLine(i);
               logger.debug("line " + i + ", item: " + srcLines.getItemCode());
               if (lineno > 0)
                    lines.add();
               lines.setCurrentLine(lineno++);
               double quantity_diff = 0;
               lines.setItemCode(srcLines.getItemCode());
               lines.setWarehouseCode(srcLines.getWarehouseCode());
               lines.setPrice(srcLines.getPrice());
               lines.setDiscountPercent(srcLines.getDiscountPercent());
               lines.setTaxCode(srcLines.getTaxCode());
               lines.setBaseEntry(srcDocEntry);
               lines.setBaseType(srcDoc.getDocObjectCode());
               lines.setBaseLine(i);
               lines.setVatGroup(srcLines.getVatGroup());
               lines
                         .setCorrectionInvoiceItem(SBOCOMConstants.BoCorInvItemStatus_ciis_ShouldBe);
               double quantity_was = srcLines.getQuantity();
               double quantity_is = 0; //quantity_was - quantity_diff;
               lines.setQuantity(quantity_is);
          int result = sapDoc.add();
          String info = company.getLastErrorDescription();
          logger.debug("res = " + result + ", info: " + info);
          if (result != 0)
               throw new EBladKorektyNrPartii(
                         "Cannot create document: " + info);
Edited by: WodzGalopujacySkleroz on Jul 4, 2011 5:03 PM

Hello,
Maybe it's an old thread, and you might have the solution or workaround for this. Nonetheless i try to answer, it might be useful for those trying to find a solution for the same problem.
The two loops are necessary indeed. DI API expects only this structure: Start with all the "ShouldBe" lines, and follow them with all the "Was" lines. So your code is almost good, but you should have swap the two loops with each other.

Create AR Correction Invoice

Hi All,
I need create AR Correction Invoice link to AR Invoice, abt system display error "Invalid structure document"
oDoc = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oInvoice)
oDoc.GetByKey(XXX)
_oOCSI = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oCorrectionInvoice)
If _oRecSet.RecordCount <> 0 Then
   _oOCSI.CardCode = oDoc.CardCode
   _oOCSI.DocDate = oDoc.DocDate
_oOCSI.DocDueDate = oDoc.DocDate
oOCSI.DocType = SAPbobsCOM.BoDocumentTypes.dDocumentService
For i = 1 To _oRecSet.RecordCount
      If i > 1 Then
        _oOCSI.Lines.Add()
      End If
      oDoc.Lines.SetCurrentLine(i - 1)
      _oOCSI.Lines.BaseEntry = oDoc.DocEntry
      _oOCSI.Lines.BaseLine = oDoc.Lines.LineNum
      _oOCSI.Lines.BaseType = SAPbobsCOM.BoObjectTypes.oInvoices
      oOCSI.Lines.CorrectionInvoiceItem = SAPbobsCOM.BoCorInvItemStatus.ciisWas
      _oOCSI.Lines.Add()
       _oOCSI.Lines.BaseEntry = oDoc.DocEntry
       _oOCSI.Lines.BaseLine = oDoc.Lines.LineNum
       _oOCSI.Lines.BaseType = SAPbobsCOM.BoObjectTypes.oInvoices
      _oOCSI.Lines.LineTotal = 0
       oOCSI.Lines.CorrectionInvoiceItem = SAPbobsCOM.BoCorInvItemStatus.ciisShouldBe
      _oRecSet.MoveNext()
   Next i
   lErrCode = _oOCSI.Add
Please Help me.

Simply change the order of lines you are adding. First you'll have to create ShouldBe items, than the Was items.
Dim _oOCSI As SAPbobsCOM.Documents
        _oOCSI = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oCorrectionInvoice)
        _oOCSI.CardCode = "12121212212"
        _oOCSI.DocDate = Now()
        _oOCSI.DocDueDate = Now()
        _oOCSI.DocType = SAPbobsCOM.BoDocumentTypes.dDocument_Service
        _oOCSI.Lines.CorrectionInvoiceItem = SAPbobsCOM.BoCorInvItemStatus.ciis_ShouldBe
        _oOCSI.Lines.LineTotal = 0
        _oOCSI.Lines.BaseType = 13
        _oOCSI.Lines.BaseEntry = 122
        _oOCSI.Lines.BaseLine = 0
        _oOCSI.Lines.Add()
        _oOCSI.Lines.CorrectionInvoiceItem = SAPbobsCOM.BoCorInvItemStatus.ciis_Was
        _oOCSI.Lines.BaseType = 13
        _oOCSI.Lines.BaseEntry = 122
        _oOCSI.Lines.BaseLine = 0
        lErrCode = _oOCSI.Add()

Correction Invoice Poland, 2. Returns

Dear all!
I have a problem with a returns in poland.
If they book the first returnshipment, the correction invoice is okay (quantity and amount).
But, if the customer brings goods back again to the same invoice, SAP show me the wrong amount.
I will explain it on an example:
Customer get 100 pcs for 100 EUR.
If he bring 20 pcs back, the correction invoice looks like this:
Credit item    100 pcs      total 100 EUR
Debit item        80 pcs     total - 80 EUR
Difference                                 20 EUR
Everything is okay!
But now, if the customer bring back 20 pcs again, the correction invoice looks like this:
Credit item        80 pcs     total 100 EUR
Debit item         60 pcs      total -60 EUR
Difference                                   40 EUR
This is wrong, but I can't change the amount in the first line, there must be 80 EUR!
I checked the Copying Control, but I can't change the pricing type ....
Does anyone have an idea?
Thank you for your help!
Have a nice day...
Zita

Hi,
The Correction Invoice is in the Area CZ, HU, PL, SK.
here is brief info;
Vendors are legally obligated to issue an A/R correction invoice if:
Rebates and discounts were given after the original invoice was issued
Goods were returned
The prices of goods and services were changed after the original invoice was issued
There was a mistake in price, tax rate, tax amount, net value, gross value, quantity, or unit of measure in any invoice item
An A/R correction invoice usually refers to an A/R invoice or another A/R correction invoice. However, the system allows you to enter a correction invoice without any reference to a preceding document. Such a situation can occur if the original document has not been entered to the system, for example, a document from a legacy system.
The system automatically performs all relevant posting in financial accounting, as well as performing changes in the inventory module, such as stock quantity.
A/R Correction Invoice is also displayed separately in the Banking module. You can link particular payments directly to it. If there are several correction invoices (one correcting the other) you will see all of them together with all invoices related to the business partner. The payment process is the same as with invoices.
The functionality and screen layouts are very similar to Purchase Correction Invoice. For more information, see A/P Correction Invoice - Creation Procedure.
Country-Specific Information: Hungary
This information refers to the specific print layout for Hungary, and to the printing of correction invoices.
To print the number of copies of a printed A/R correction invoice correctly, you must print the correction invoice directly from the A/R Correction Invoice form (click (Print)). Do not print the correction invoice by displaying it via (Print Preview); otherwise, the number of copies will not be printed correctly.
Rgds,

Correction Invoice with Items TreeType != iNotATree

Hi,
I want to create Correction Invoice document with Items which TreeType = SAPbobsCOM.BoItemTreeTypes.iSalesTree
When I'm adding Correction with reference to some document (BaseType = 13 or 165, BaseEntry=... and BaseLine = ...) then everything is OK,
But when I try add Correction without ref. (no set BaseType,BaseEntry and BaseLine) then I get error:
"Wystąpił błąd wewnętrzny (-5002)"
"Internal error (exception) occurred (-5002)"
When all Items on Correction has TreeType = iNotATree then I can add this Correction without any reference.
The property correction.Lines.TreeType default value is iNotATree, but this property is ReadOnly.
How can I add this document?
Edited by: Dariusz Maron on Jun 4, 2009 12:07 PM

Hello Wolf
1) This was an issue in older releases but has been corrected (supposedly) since 4.5 B
Take a look at OSS note: 146091 - Invoice correction: new pricing not possible
But I am sure you are in a much higher release. Review it any ways.
2) Did you try with 'B" or ""C" for the second pricing type? The help says 'You should give a new pricing type to the debit memo item'.
3) Also is the invoice type you are copying from- does it have a 'M" in the SD document category.? T code VOFA. I believe this is prerequisite
4) Check how the item cats are set up (G2N/L2N): The Returns field in Business data should be selected for credit items but not for debit items.
5) Finally the culprit could be the way you set up PR00 (V/06). Check what changes can be done: Are you allowing manual entries? Just a thought.

Urgent - Price correction invoice got hold upon validation

Hi
In AP, I entered a standard type invoice for upword price revision. I checked the price reivision check box and entered the invoice reference. I also entered the relevant receipt number as well.
For the matching line I entered the Qty and incremental unit rate for the increase and clicked on match.
Coming back on invoice header I checked the distribution and vlidated the invoice.
This ended up on a hold - Invoice price exceeds purchase order price.
I did not undertand why the invoice would go on this hold when I had checked the price correction box while matching and entering the increamental increase as well?
Please let me know if any action is missing or incorrect understanding from my side
Thanks in Adv
Shanks

Hi
Found the answer to this -
As it was exceeding the tolerance that put the price correction invoice on hold :-(
Thanks
Shanks

Correction invoices for rebate agreements in Poland

I am currenty working in Poland on rebate agreements. There is a legal requirement that every change in the invoiced and VAT value has to be corrected via a correction invoice , mentioning the original invoice line, updated line and the delta. However the rebate settlement only generates a standard credit note to pay the rebate. The credit note that is generated
for the rebate contains the settlement material.
In Poland the correction invoice should have the original quantity ,real material number and invoice value. Does
anybody have experience in how to create a correction invoice instead of the standard credit note for the rebates ?
Many thanks in advance
Evert Nooijen

Hello everybody,
The requirement to create correction invoices might look weird and very painful but I really think it is a legal requirement.
I have searched the internet and find contradictory information on whether the correction invoice is mandatory for rebate payments in Poland.
For example the SAP country specifics mention that a correction invoice is needed for rebates:
"You are required to create a correction tax invoice whenever you need to correct a tax invoice, for example:
·        To grant a customer a discount or rebate or increase the price of goods or services
·        To correct a tax invoice, for example, if it contains an error in any of the prices, tax rates, tax amounts, net values, gross values, quantities, or units of measure
·        When a customer returns some goods to you"'
However I also found another document that gives me the impression that the Polish regulations on correction invoices have been changed in November 2009 (Polish jurisdiction)
See the text below that is part of the changes in Poland:
" The WSA in Wrocław ruled on 12 November 2009 (case ref. I SA/Wr 1155/09) that a rebate causing a reduction
of the tax base for VAT may be documented not only by invoice but also by other documents.
The taxpayer received rebates directly from his suppliers and by proxy of a company which negotiated terms of delivery in his
name. The rebates received directly from suppliers were backed by correction invoices. Those received from the
intermediary were documented by credit notes. The tax authorities took the view that rebates could only be documented by
correction invoices. However, the WSA ruled that a rebate could be documented otherwise, for example, by credit note. Such
a document must be supplemented with additional information which shows who gave whom the rebate and in what amount."
HOWEVER: I am told by the local Polish organisation that this decision from the court in Wrocław, and not necessarily valid in other areas like Warsaw.
Then I had contacted Price Waterhouse in Poland and have asked them for an advice: I have received the following answer from PWC:
""Pursuant to the Polish VAT regulations post-transaction rebates should be documented with the correction invoices referring to the original invoice. Therefore, we recommend that the system is appropriately adjusted to include the discussed functionality. Please note this is a standard in Poland that SAP allows for creation of such correction invoices."'
So as mentioned, I think we have to enable the correction invoices for Poland, however I don't think we cannot create those in correctoin invoice requests (e.g. document type RK) in standard SAP by the rebate settlement program. We cen build a program to do it automatically, but I was hoping for a standard SAP program that was linked to the rabete functions in SD (automatically as part of the rebate settlement.).
Hopefully somebody has any recommendation.
Regards,
Evert Nooijen
Edited by: Evert Nooijen on Apr 4, 2010 12:01 PM
Edited by: Evert Nooijen on Apr 4, 2010 12:03 PM

How to contact Adobe billing support to get correct invoice without VAT

We have bought Adobe Creative Cloud for Teams but were billed incorrectly. The invoice includes VAT. VAT should not be included as both Ireland and Lithuania (my country) are in EU.
I've been trying to reach Adobe support for 3 days now without success. All help links just go to local support dealer. Email for that dealer doesn't work at all. Phone support cannot help me as they do not have access to customer invoices on Adobe.com.
Can somebody help me to reach Adobe? I need correct invoice badly.

It is after hours on friday. there is no chat. I am getting error messages and can not post to my BC site.
What is the move?
Can not upload my updated MUSE paid site using MUSE > PUBLISH.
When attempting to upload my MUSE site i get
"Unknown Adobe BC error has occurred. Status: 0, 0."
This is going on for 5 hours now. Need to get back into the site.
Please advise what to do or how to work around.
-Farley Allen [email protected]
BC_MUSE_ERROR_SCREEN_WHEN.AT
Thanks.

Print correction Invoice with Advance Layout Designer

Dear All,
we will use the Correction invoice in the System.
But i couldn't find a possibility to create a Layout for this document Type.
The Document Type is OCSI but this i couldn't find it in the Define Layouts List.
Thanks and best regards
Serkan

Thank you for the info, but this message don't answer my question.
i search a way to create a Layout with the Advance Layout Designer for the correction Invoice.
i cant open the designer for that. just can create the standard Layout from the system..
do you know if the Advance Layout are supported wit the 8.8 Version?
Thank you very much!
Serkan

Request: Warehouse change at A/R Correction Invoice

Currently there is no such funcionality in SAP B1 (2007A), i.e. A/R Correction Invoice does not allow to make warehouse changes (an error message pops out). However there is a need for a funcionality that would allow A/R Correction Invoice to return/withdraw some goods into/from another warehouse they was taken from.
I'll explain it by an example:
BP "Smith" has received an Invoice along with a stock of 100 kg tomatoes, but 20 kg turned out to be spoiled. He returns those 20 kg with a demand for an Invoice Correction. His demand is accepted and Correction Invoice is applied, but for obvious reasons the spoiled tomatoes cannot be returned to the same warehouse they were taken from. Correction Invoice allows only for return of goods to the same warehouse as it was at Invoice. Since these items are valuated by FIFO method, they cannot be moved from the same FIFO layer (which is imperative) using Inventory Transfer in case of a goods return, even if they are managed by batches.
If there is a possibility to make any functionality changes in future patches of SAP B1 versions, changing warehouse in "Should be" line at A/R Correcion Invoice should result in adding or removing quantity difference into/from selected warehouse and revaluating stock accounts. Please let me know if there is any chance for that.
best regards
Thomas Staron

Hi Tomasz,
I checked your scenario and let me comment it.
The basic behavior of Correction Invoice is that in WAS section displays the data from original document and SHOULD BE section says how the data should look like originally.
In your case Correction Invoice works correctly as company sold 100kg but it should sale only 80 kg. It represents the situation as if the 20 kg would remain on the original warehouse. There is no place where to specify the additional warehouse on Correction Invoice.
For your scenario better would be the scenario of Credit Memo, because on Credit Memo you specify what quantity is returned and to which warehouse.
It seems to me that the issue with scenario is rather in the Warehouse transfer functionality than in the modification of Correction Invoice.
Best Regards,
Martin Slavik
SAP Business One Solution Manager

Modelo 340 - Correction invoices (opkey D)

Similar Messages

Maybe you are looking for