MEIS & VE01 Error

[Former Member]

Hi All,

I've been browsing some ideas on how to deal with the error message we are facing with the MEIS & VE01 report.

Would you be so kind to please advise how to fix the errror

Error in VE01.(Similar kind of ERROR in MEIS report)

"Characteristic was not maintained in the FT data of the document header."Message no. EIP010

"Characteristic was not maintained in the FT data of the document item" Message no. EIP011

Maintain the characteristic Procedure in the Foreign Trade data of document XXXX in item XXXX

Maintain the characteristic Bus.transaction type in the Foreign Trade data of document XXXX item XXXX

What is this Characteristics,where & how to maintain this.

Thanks a lot in advance!

Any assistance will be highly appreciated.

Regards,

[JL23]

one field is the import Procedure

the other field is Bus.transaction type

the document is your billing document in SD (for VE01)

and the purchase order in MM (for MEIS)

in both documents you have some foreign trade data field on header and on item level.

if you dont want or cant anymore maintain it in the documents, then you have to add it directly in VEFU transaction to your database for reporting.

[Former Member]

Hi Jurgen,

Thanks for your reply. I was expecting a reply from you, as you have replied to related queries in this forum.

Can you be bit specific where i can update the details in PO & Billing document. I tried, but not able to find teh feild.

Hard Luck.

Can you assist.

Do revert.

Regards.

[JL23]

open ME22N

open the item detail

goto import tab

open the second tab "origin... within the import tab

here you find the 2 fields

open billing doc in VF02

choose from menu GOTO > ITEM > ITEM Foreign Trade data

open the second tab "origin... within the import tab

here you find the 2 fields

maybe you cannot maintain it in VF02, then you have to cancel the invoice, then you have to go into the delivery with VL02N

choose from menu GOTO > ITEM > Foreign Trade data

open the second tab "origin... within the import tab

here you find the 2 fields

[Former Member]

Hi Jurgen,

Thanks for your detailed explanations.

We checked the related sales billing documents, Dispatch ctry (EIPO-VERLD) is filled in, but the Region of origin (EIPO-HERKR) is left blank.

When we check Table EIPO the field HERKL(Ctry of origin) is not filled in for all error document

Is this cases the error or something else.

Also as per your suggestion, we cant reverse the Sales & Purchase documents as they are posted in previous month.

Can you kindly suggest any workaround for posting these documents.

If we use VEFU, will it make any impact on the FI Posting, as we have already closed our book for previous period.

Note: We are executing VE01 & MEIS for Jan 2012.

Do suggest.

Regards,

[JL23]

VEFU is just maintaining a data base created specifically for Intrastat, it does no effect anything else than the Intrastat report itself.

But when you use VEFU to maintain data manually, then you have to be more careful with MEIS and VE01.

MEIS and VE01 create this database, depending on the settings made in the selection screen they can delete everything when running it again for the same period. if you maintained values, then you usually want keep those but recreate others, so you have to choose the right indicator for deletion. (leaving the field empty will cause that you loose all your manually made changes)

[Former Member]

Hi,

VEFU is sensitive T.Code and we dont want to create more problems using VEFU.

Is there any other way to overcome this error.

Do suggest

Regards,

[JL23]

No, VEFU is the usual table maintenance transation, SAP has not provided any other method to maintain records for VEIAV table,.

I hope it will be a one-time event to correct your situation. if your customizing and master data is correct, then you do not need to use VEFU again.

[Former Member]

Hi,

Thanks for your immediate response.

As we don't have much experience executing VEFU and as per you info its risky T.Code.

So, is it possible for you let us know or any way for us to find which field has not been updated in Table VEIAV, for which error has been displayed by system.

We will discuss with Basis people and ask them to update those field directly in the Table VEIAV itself, to fix this error as of now.

We don't want to make things more complicate by executing VEFU and leaving some field blank or with wrong info.

Can you assist.

Do revert.

Reagrds,

[JL23]

I have never said that VEFU is risky.

I said that you have to take care with MEIS and VE01 if you have done changes with VEFU

the changes are done to VEIAV records.

if you do those changes with VEFU, or if you ask your basis team to do it with whatever method, it is the same for a second execution of MEIS or VE01. You will loose those changes if you execute with a blank deletion indicator in MEIS or VE01.

From this point of view MEIS and VE01 are risky, but certainly not VEFU.