Error Missing Export Data

This error popped up when client updating a customer's country after creating sales order.

Apparently the error appears due to differences between Sales Organization Country & Ship to Party Country. This is how to fixed it. Taken from a good answer at SAP Community Network posted by Reazuddin MD http://forums.sdn.sap.com/thread.jspa?threadID=1551384.

Check- Incompletion procedure what are the fields maintained for Header / Item

IMG - SD- Foreign trade/Customs - Incompleness Schemas for Foreign trade data (VI29) & Foreign trade data in MM&SD (VI49)

if you dont want to maintain any fields in billing, Create new incompletion procedure for Header & Item, dont maintain any fields.
Assign this incompletion procedure in VI49.

Also posted by Calauz Artur :

In VF02 check the log for export data at heather level and item level, and fill those fields, the accounting document will be created.

the nature of LSMW

LSMW - Legacy System Migration Workbench

This is the common tool used in SAP R3's data migration. Supposedly 2 tools available : LSMW and BAPI. However, BAPI is a function, therefore we need to develop an ABAP program which includes the selected BAPI function before we can use it.

LSMW on the other hand is a ready to use migration tool. There are 4 import methods available in LSMW :

- Standard Batch/Direct Input - using the standard batch

- Batch Input Recording

- Business Object Method (BAPI)

- IDoc (Intermediate Document)

As for me, i'd prefer using Batch Input Recording which means i recorded the transaction manually and so the field which i fill is only the mandatory field and those i chose during the recording session.

LSMW also server dependent. Once you created an LSMW object in one server, it can be use in any clients available in the server. To copy one LSMW object or project from one server to another, we use the Export-Import option. First export the selected object (including the recorded object) to your local computer then Import the file at the other server.

FI Period and Authorization Group

Got a problem today :D Users can not create postings on FI transaction with error "No authorization for posting period 002 2011".

Looking from the error, i'm pretty sure the error comes from wrong settings on the Open/Close Period (OB52).

When I check on the settings, this is what i got :

Apparently users tried to set special open period only for those in ADM authorization group. I guess it means adjustment to previous period can only be done by some people.

It is true that to fulfill this requirement, we have to make entries on both posting periods (1 & 2) and the authorization group. However, authorization group only linked to posting period 1 (first 4 columns).

For example ,if you want users with authorization group ADM can post to period 13.2010-16.2010 while other users can only post to period 01.2011 - 02.2011. Then the setting should be shown as below :

Asked the users to change the setting and pouff! No more posting error :P

ALE migration and number range

This is the first time I'm using ALE (Application Link Enabling) as a tool to migrate data from one SAP client to another SAP client.

After finding the trouble i mentioned on my previous post. I decided to check the number range on vendor and customer master data. Result : the last number on the number range status didn't match the last number created in real. This conclude that ALE treating the document or master data's number as an external number and did not create any update at the number range status.

This can lead to an error during operational transactions. Be sure to check and update the number range status manually after you migrated data using ALE.

I'm not really sure if this applies to every ALE program, but at least i checked on Purchasing Info Record, Customer Master Data and Vendor Master Data. If you have time, better go and check on yours too ;)

ME 807: System error: error during insert in table EINA

System error! hahaha. I was surprised to find that i cannot create Purchase Order, even though i had created the Purchase Requisition neatly.

It was funny to see that the system showing that "Document created by number 7xxxxxxxx" after i create a PO from ME21N. But when i checked at the Display option from ME23N, i found NOTHING. Lol. I tried to check at the EKKO table and no document created by that number. I tried several times and it didnt work.

It is said that the problems come from the Purchasing Info Record's number range. I just realized that when we create a PO, although we didn't fill the Purchasing Info Record, system will automatically create a new PIR if the button "Info Update" in the tab Item Detail > Material Data is thicked.

This is not the main problem. The main problem comes from the PIR number range. We migrated the data from other SAP client using standard ALE. Apparently when we using ALE, the system didn't automatically update the number range status. Thus the number range status of last document number is not updated and creating an error.

Solution :

Change the PIR number range status using tcode OMEO. Refer to the last document number created already on table EINA.

It works well :D and now time to go home!