Error table T030 when posting invoice

Hi Expert,
I'm having error when posting invoice :
"Table T030 : Entry HASA WRX AA_____4000 does not exist"..
Is there anything missing in config? Please guide me to fix the problem.
Thanks

Hi
May be looking at the entries, account modifier is blank. Were you able to post GR for this PO, if your invoice is in reference to a PO.
Thanks !
E.Avudaiappan

Similar Messages

Make changes to auto generated line items when posting invoice thru MIRO?

Hi All,
My requirement is to make some changes in line items data when posting invoice through MIRO transaction.
I have written a substitution for the same, The issue is that some line items get automaticaly created (i.e inter company posting). I need to make changes to these line items as well but substitution is not being triggered for these auto generated line items.Is there any way by which I can update in these line items as well ?
further do we have any internal table which holds all the line items at runtime....to which I can refer and make the changes. I have searched but could not find one.
Can anybody provide some inputs on this.
Thanks,
Lucky.

Hi Kaushik,
Thanks for your reply.
I am using BADI INVOICE_UPDATE but here we will not be having line items which are auto generated.
When we do inter company posting, line items are automatically created and these are not avaliable in the BADI. I am not sure if we can trap these line items any where.....the possible alternative which I can think of is to use memory reference and modify the internal table which holds all the items but unfortunately I am not able to find any such internal table to refer to at run time ...have u got any idea on this?
Thanks,
Lucky.

Enhancement to summarize FI entries when posting invoice

Is there a way we can summarize line item totals (have one debit for 100 service lines) when posting invoices via enhancement based on a characteristic, such as cost center?
I can maintain summarization via OBCY, but this is not an option.

Hi ,
IS it Vendor/Customer Invoices ? , as per my knowledge u can do it thru Config.
Regards
Prabhu

Error message when posting invoice : Day-end closing not defined

Hi,
In our training environment we migrated from FAGLFLEXT to FMGLFLEXT and activated fund management.
Now when posting an invoice the system provides an error message: "FQ252 Day end closing not defined".
There is no configuration related to F845 but we are prevented from posting the document due to this error message.
Any idea of where this could come from and of what need to be done to prevent this from happening?
Rgds
Sophie

Hi Sophie,
Can you check if you have entries in either PSO43 or PSO43USER tables (can be accessed via F8O2 transaction)?
Regards,
Eli

Error when posting invoice for Asset purchase order

Hi,
we are getting the errore message account determination for asset posting with keys not defined in chart of accounts,when posting an invoice for asset purchase order.
Can any one see why this error is coming and what will be the solution.
Nagesh

Hi Prabhakar,
Here is the reply,
we have 10 line items,in which 3 items are freight related and other 7 items are related to goods reciept.
i am trying to enter invoice for 3 line items at a time with two relevant to goods reciept and other related to non goods receipt(freight related).
accounting entries generated after the GR are as follows,
asset under construction account,and GR/IR account.
Let me know the details is sufficient or not.

IDoc error M8(183) in posting invoice from SRM to ECC

Hi everybody,
I am posting invoice in SRM against GR done in ECC. But the corresponding IDoc is in error when it reaches ECC. I am using MM-SUS scenario with SRM7.0, PI7.0, ECC6.0. Message types used are InvoiceRequest_Out and INVOIC.INVOIC01.
1) Error message: "M8(183) : Delivery note/service entry sheet & & does not exist".
2) First I applied note 1063742, but it did not resolve the problem. When I went into further detail, I found that the XML payload generated for the invoice in SRM does not contain GR number of ECC, but the corresponding GR number generated in SRM is passed onto ECC.
3) This SRM GR number is available in field BELNR of IDoc segment E1EDP02 (segment 12).
My question is, how to enable the invoice generated in SRM to carry the ECC GR document number, so that the corresponding IDoc in ECC recognises the GR number against which it was made. Please let me know if any alternative exists, also.
regards,
biplab

Hi everyone,
Able to solve the problem by applying note 1344626 (GR based invoice not updated in backend PO).
biplab

Default due date , payment method when posting invoice with Special G/L

Hi Gurus,
I have a question is when I am posting an invocie to a vendor (FB60), Due On date, payment method are automatically calculated based on the defaulted baseline date and the payment term in the vendor master. But when I am posting the invocie to the same vendor with Special G/L indicator, Due On date, payment method are not automatically calculated and system are expecting me to enter this date manually. Is there a way we can default this Due On date, payment thod based on payment term like it happens when posting to other invoices without Sp GL indicator ?
Thanks
Edited by: Ngoc Hoang on Nov 29, 2011 8:30 AM

Dear Ngog,
In general, special G/L transactions are used to map special processes
to be stated separately in the balance sheet.So if you use special GL
indicator, the fields relevant to payment terms (including baseline
date) are not displayed. This is not controlled by field status.
To make the fields You need ready for input for posting
with special G/L indicator, the following Customizing setting is
necessary:
Financial Accounting -> Accounts Receivable and Accounts Payable
->Business Transactions -> Outgoing Payments -> Automatic Outgoing
Payment-> Payment Method/Bank Selection -> Configure payment program ->
All company codes -> double-click on corresponding company code -> under
Vendor -> 'Sp. G/L transactions to be paid' you should enter the special
G/L indicator A,B, etc.
As explained in SAP note 4683, the only standard possibility to get the
field payment terms on creating a posting with a special G/L indicator
is by setting in the payment program configuration (trans. FBKP) for
'All company codes' for customers/vendors 'Sp. G/L transaction to be
paid'.
Mauri

Why is vendor negative when posting invoice in MIRO

Hi all,
I have a very basic question.
When posting an invoice in MIRO, why is the vendor GL account negative? I assume this is vendor A/P, so shouldn't it increase in an invoice?
ie.. vendor 5.00-
GR/IR 5.00 +
If you have a website to redirect me on this topic so I can learn more about it, it would be most helpful.
Thanks,

Pistal,
Must say nice name
When posting an invoice in MIRO, why is the vendor GL account negative? I assume this is vendor A/P, so shouldn't it increase in an invoice?
ie.. vendor 5.00-
GR/IR 5.00 +
Thease is because The vendor is your Crediator , You have to pay him the amount
It Is like u went to hotel have sum food, then wheather you will pay to hotel or hotel will pay to you? and from whhoes wallet will losse money urs or hoteler?
I guess that was the easiest ex any 1 can gave

Meve PO Number to table FBICRC002A when posting MIGO

Hello,
I have a requirement to find out where in ABAP code PO number and PO item are moved to table FBICRC002A durring posting in MIGO. So I've used a trace and now I know that it is done by Function Module G_GLDB_POSTING_A. But this function module is called in Update task (I think so) by form VB_CALL_FUNC in program RSM13000. And I don't know how table FBICRC002A (variable INT_FBICRC002A) is passed to FM G_GLDB_POSTING_A. Any ideas? Any help?
I will be gratefull.
Thanks for help.
Best Regards,
Mikolaj

see any where in the sqr or in sqc for the string "begin-select". begin-select is the command that will fetch the data from the peoplesoft tables. so somewhere you must see "begin-select".
In that begin-select try to locate any of the data(column of the table) which is getting printed right now on the invoice and see that table name(locate the from in that begin-select, you can see the table name). go to app designer and see if that has PO_ID. if that has PO_ID then modify the begin-select to get this extra column.
Hope this helps.

Runtime Error when Posting Invoice with text added (MIRO)

Hi Gurus,
We are getting a shortdump (runtime error) when we post certain invoices in MIRO. This happens when we input some text in the text field or add some text to the NOTE tab.
We are having exception ERROR_DP raised in the program c_textedit_control.
If the text field is blank and nothing is writing in the NOTE tab, the invoice gets posted with no problem.
Has anyone come accross this issue before and how did you solve it please.
Thanks.

are u processing thru BADI, then it is very easy there are interfaces and methods for handling texts. u sud not get any error and plz never write commit work in BADI.
May be i cud provide more help if u share more details but let me tell more but let me share one recent development that i did.
In ME59n when we do PR TO PO then texdts sud be copied to header text in PO and get reflected in PO. the coding is like below may be can give some clues wid ur MIRO stuff.
METHOD if_ex_me_process_po_cust~process_header.
* Author        : Prasenjit Bist                                          *
* ID            : PRBIST                                                  *
* Date          : 04.08.2011                                              *
* Changes       : New Devlopment                                          *
* Change Request:                                                         *
* Description: To copy LSP information in PO                               *
TYPES:
        BEGIN OF ty_text,
          auto_pr_po TYPE zman_auto_pr_po,
          plant TYPE zman_plant,
          vendor TYPE zman_vendor,
          lsp_vendor TYPE zman_lsp_name,
          contract_no_text TYPE zman_contract_no_text,
        END OF ty_text.
TYPES:
       BEGIN OF ty_address,
         ort01      TYPE ort01_gp, " city
         ort02      TYPE ort02_gp, " district
         pfach      TYPE pfach,     " PO Box
         pstlz      TYPE pstlz,     " Postal code
         region     TYPE regio,     "Region (State, Province, County)
         telf1      TYPE telf1,     "1st telephone number
         telf2      TYPE telf2,     "2nd telephone number
         telfx      TYPE telfx,     "Fax number
         land1      TYPE land1,
       END OF ty_address.
DATA:
   get the header level details
        ls_mepoheader TYPE mepoheader,
        lt_purchase_order_items TYPE purchase_order_items,
        ls_purchase_order_items LIKE LINE OF lt_purchase_order_items,
   get the line item details
        lt_mepoitem TYPE STANDARD TABLE OF mepoitem,
        ls_mepoitem TYPE mepoitem,
        lt_textlines TYPE mmpur_t_textlines,
        ls_textlines LIKE LINE OF lt_textlines,
TEXT TYPES
        lt_texttypes TYPE mmpur_t_texttypes,
        ls_texttypes LIKE LINE OF lt_texttypes.
DATA: l_name TYPE thead-tdname,
        ls_header TYPE thead,
        lt_lines TYPE STANDARD TABLE OF tline,
        ls_lines TYPE tline,
        l_tdobject TYPE thead-tdobject,
        l_metafield TYPE mmpur_metafield.
DATA: ls_text TYPE ty_text,
        l_text(50).
DATA: l_continue(1).
DATA: l_pass_vendor TYPE lifnr,
        l_pass_plant TYPE werks,
        l_name1(35).
fetch the address
DATA: ls_address TYPE ty_address,
        l_landx    TYPE landx.
CONSTANTS: lc_id TYPE thead-tdid     VALUE 'F01',
             lc_langu TYPE thead-tdspras VALUE 'E',
             lc_object TYPE thead-tdobject VALUE 'EKKO'.
CONSTANTS: lc_set(1) VALUE 'X',
             lc_vendor(11) VALUE 'Vendor:    ',
             lc_lsp_vendor(11) VALUE 'LSP Vendor:',
             lc_contract_no_text(14) VALUE 'Contract Text:'.
CLEAR: l_continue.
IF sy-uname EQ 'PRBIST'.
Read the header data
    ls_mepoheader = im_header->get_data( ).
read teh item level data.
   break prbist.
    lt_purchase_order_items = im_header->get_items( ).
    LOOP AT lt_purchase_order_items INTO ls_purchase_order_items.
The item attribute of the structure is reference to line item
      ls_mepoitem = ls_purchase_order_items-item->get_data( ).
      APPEND ls_mepoitem TO lt_mepoitem.
    ENDLOOP.
CHECK VENDOR IS THE ONE WE WANT.
    SELECT SINGLE name1 FROM lfa1 INTO l_name1 WHERE lifnr = ls_mepoheader-lifnr.
First read the vebdor name based on LIFNR.
    TRANSLATE l_name1 TO UPPER CASE.
    IF ( l_name1 EQ 'LSP1' ) OR ( l_name1 EQ 'LSP2' ).
      LOOP AT lt_mepoitem INTO ls_mepoitem.
        TRANSLATE ls_mepoitem-werks TO UPPER CASE.
        IF ls_mepoitem-werks EQ 'FI01'.
          l_continue = lc_set.
          l_pass_vendor = ls_mepoheader-lifnr.
          l_pass_plant = ls_mepoitem-werks.
          EXIT.
        ENDIF.
      ENDLOOP.
    ENDIF.
    IF l_continue EQ lc_set AND sy-tcode EQ 'ME21N'.
Call the POP UP screen to display LPS information.
      CALL FUNCTION 'ZMAN_LSP_POP_UP'
        EXPORTING
          im_vendor = l_pass_vendor
          im_plant = l_pass_plant
        IMPORTING
          ex_text   = l_text.
GET Text Object (TTXOB)
      im_header->if_longtexts_mm~get_textobject(
                    IMPORTING ex_tdobject = l_tdobject
                              ex_metafield = l_metafield ).
GET TEXT IDS
      im_header->if_longtexts_mm~get_types(
                    IMPORTING ex_texttypes = lt_texttypes ).
CHECK TEXT TYPE 'F01' EXISTS.
      READ TABLE lt_texttypes INTO ls_texttypes WITH KEY tdid = lc_id.
      IF sy-subrc EQ 0.
UPDATING ITEM TEXT.
        MOVE: l_tdobject TO ls_textlines-tdobject,
              ls_texttypes-tdid TO ls_textlines-tdid,
              '*' TO ls_textlines-tdformat.
     break prbist.
        ls_text = l_text.
     CONCATENATE l_text ls_texttypes-tdtext INTO ls_textlines-tdline.
       CONCATENATE ls_text-vendor
                   ls_text-plant
                   ls_text-lsp_vendor
                   ls_text-contract_no_text
                                           INTO ls_textlines-tdline SEPARATED BY space.
       APPEND ls_textlines TO lt_textlines.
      INSERT VENDOR
       CLEAR ls_textlines-tdline.
       CONCATENATE lc_vendor ls_text-vendor INTO ls_textlines-tdline SEPARATED BY space.
       APPEND ls_textlines TO lt_textlines.
      INSERT LSP VENDOR
        CLEAR ls_textlines-tdline.
        CONCATENATE lc_lsp_vendor ls_text-lsp_vendor INTO ls_textlines-tdline SEPARATED BY space.
        APPEND ls_textlines TO lt_textlines.
      INSERT CONTRACT TEXT.
        CLEAR ls_textlines-tdline.
        CONCATENATE lc_contract_no_text ls_text-contract_no_text INTO ls_textlines-tdline SEPARATED BY space.
        APPEND ls_textlines TO lt_textlines.
     INSERT A BLANK LINE.
        CLEAR ls_textlines-tdline.
        APPEND ls_textlines TO lt_textlines.
INSERT addreSS CAPTION.
        CLEAR ls_textlines-tdline.
        MOVE 'Address:' TO ls_textlines-tdline.
        APPEND ls_textlines TO lt_textlines.
        break prbist.
READ THE ADDRESS
        SELECT SINGLE   ort01      " city
                        ort02      " district
                        pfach      " PO Box
                        pstlz      " Postal code
                        regio      "Region (State, Province, County)
                        telf1      "1st telephone number
                        telf2      "2nd telephone number
                        telfx      "Fax number
                        land1      "COUNTRY
        FROM lfa1 INTO ls_address WHERE lifnr = ls_mepoheader-lifnr.
GET COUNTRY
        SELECT SINGLE landx FROM t005t INTO l_landx WHERE spras = 'E' AND land1 = ls_address-land1.
INSERT ADDRESS DETAILS.
        CLEAR ls_textlines-tdline.
        CONCATENATE ls_address-ort01 ls_address-ort01 INTO ls_textlines-tdline SEPARATED BY space.
        APPEND ls_textlines TO lt_textlines.
INSERT COUNTRY.
        CLEAR ls_textlines-tdline.
        MOVE l_landx TO ls_textlines-tdline.
        APPEND ls_textlines TO lt_textlines.
TELEPHONE DETAILS
        CLEAR ls_textlines-tdline.
        CONCATENATE 'Tel:' ls_address-telf1 '/' ls_address-telf2 INTO ls_textlines-tdline.
        APPEND ls_textlines TO lt_textlines.
FAX DETAILS.
        CLEAR ls_textlines-tdline.
        CONCATENATE 'Fax:' ls_address-telfx INTO ls_textlines-tdline.
        APPEND ls_textlines TO lt_textlines.
      SAVE THE HEADER LONG TEXT.
        im_header->if_longtexts_mm~set_text(
                      EXPORTING im_tdid = ls_texttypes-tdid
                                im_textlines = lt_textlines ).
      ENDIF.
    ELSEIF l_continue EQ lc_set AND sy-tcode EQ 'ME59N'.
No need to display POPUP simply read the values and show.
if not
    ENDIF. "(l_continue = 'X' and transaction code is ME21N or ME59N)
    CLEAR l_continue.
ENDIF. "(sy-uname)
ENDMETHOD.
Edited by: Prasenjit Singh Bist on Aug 14, 2011 10:15 AM
Edited by: Prasenjit Singh Bist on Aug 14, 2011 10:21 AM

Invoice Verification causes error "Table T030 ECOA WRX entry is missing"

I have manage to find a solution to the error message above that appears during Invoice Verification process. However, the solution (using Tcode FBKP) seems to work only with new purchase order document created after the solution was applied. Existing purchase order documents are still causing the error message when Invoice Verification process is perform on them. Any idea why this is happening and how to solve this?
"ECOA" is our Chart of Accounts.
Thanks for your help.
PLLim

Hi Lim,
Not sure why this problem occurs because P.O doesnot check WRX settings. In usual scenario, if ur PO is GR based IV (invoice tab), then u have to do MIGO (GR) first and then do MIRO. So if WRX setting is not there MIGO itself is not possible. Since u r not sure abt MIGO it can be non GR based IV also. But i don't have the answer why it is checking OBYC with a retrospective setting. Sorry.. Let's wait for other consultants.
Best Regards
Vimal

ERP EHP4 causing dump when posting invoice in MIRO

I originally posted this in the MM forum but was advised to move it here.
We just implemented ERP EhP4 w/SAPAPPL603 and are now getting a dump when using MIRO to posting a vendor invoice against a PO. The error seems to involve new logic for multiple account assignment introduced with this EHP. The dump is in include LMRMBWF02 of SAPLMRMBM, and indicates that data object S_MCRBPO does not contain component XHISTMA. The lines in LMRMBWF02 are (starting at 772):
FORM bw_read_co_history_dyn_sub USING event TYPE bwmode
s_index_mcrbpo TYPE eval_iv_index_key_s
s_mcrbpo TYPE mcrbitm
CHANGING s_mcrbco TYPE mcrbco.
DATA: s_ekbe LIKE ekbe,
s_ekbz LIKE ekbz,
s_ekbz_ma TYPE ekbz_ma, "MAA EhP4
s_ekbe_ma TYPE ekbe_ma, "MAA EhP4
f_arewr TYPE ekbz-arewr, "MAA EhP4
f_areww TYPE ekbz-areww. "MAA EhP4
CASE event.
WHEN c_recompilation.
IF s_mcrbco-xunpl = space.
Not for unplanned account assignments
IF ( s_mcrbpo-exkbe = 'X' ).
Read PO history for goods item
IF s_mcrbpo-xhistma = space. "MAA EhP4
...with the last line being the culprit. The actual break in execution occurs at line 119 of SAPLMRMP, BESTELLUNG_BUCHEN where function MRM_BW_PO_HISTORY is called.
Had some other errors where tables weren't properly activated after the EHP installation, but here most everything seems to be activated properly. The exception is table EKBE, which activates but with warnings about missing enhancement categories of tables or includes/subtypes for four active dependent tables. That's the only lead I've got.
Can't find any notes or other posts about this error, any ideas would be greatly appreciated!

Hi,
the only thing i´ve found is this OSS Note:
https://service.sap.com/sap/support/notes/1105679
Best regards.

Segment derivation when posting invoice on internal order

Dear colleagues,
I have configured the New General Ledger in SAP ECC 5.0, with profit center and segment as splitting characteristics. Document splitting and segment derivation are working fine for almost all scenarios, but not for all scenarios.
When a post a vendor invoice with FB60 to only a cost center document splitting and segment derivation are working correctly: the segment is derived from the profit center (which is assigned to the cost center in the master data of the cost center) and I can post the invoice.
However, when I post the vendor invoice to both a cost center and an internal order segment derivation does not work: I get the error message GLT2201 "The field Segment marked as balancing is not filled with any value in line item 001, even after document splitting."
The reason for this is that the posting on the cost center becomes statistical and the posting on the internal order is the actual posting. In the master data of the internal order I have not defined a profit center. Because of this the DUMMY profit center is assigned to the line item.
I have assigned all profit centers to a segment (in the profit center master data), except for the DUMMY profit center. I guess this is correct?? I can easily solve this issue by assigning the dummy profit center to some kind of dummy segment, but I don't think this is the correct solution.
A solution might be to enter a profit center in the master data of the internal order (segment can then be derived from this profit center). However, I prefer not to put a profit center in the master data of the internal order.
Does any of you have experience the same kind of problem? Can anybody give me some advice how to derive the segment correctly in the aboven mentioned posting? Did I do something wrong in the customizing?
Thanks for your help in advance!
Regards,
Koert

I have already found the solution myself. In the customizing you can define a default segment that will be used in case no segment can be derived in the posting.
IMG: Financial Accounting (New) --> General Ledger Accounting (New) --> Business Transactions --> Document Splitting --> Edit constants for nonassigned processes
Regards,
Koert

Tax jurisdiction code creates a difference when posting invoice with PO ref

I have added a tax jurisdiction code since the client wants to be able to sort taxes by location. The problem now is that, I have posted a PO with a tax jurisdiction code but upon posting the invoice with reference to this PO, there's an error saying that there still exists a balance even though the balance on the screen is zero. Any ideas on how this can be solved?

Hi ,
Can you please tell us how you resolved? We do facing the same problem.
Thanks
Ganesh

Error in MIR7 when parking invoice

Hi all
I am getting the following error while i am trying to park the invoice,
*Tax code B1 in procedure is invalid
Message no. FICORE704*
i am able to post and save the same invoice.
Regards
Girish

HI Rahul
We have created the tax codes for only one country.
Regards
girish

Error table T030 when posting invoice

Similar Messages

Maybe you are looking for