Intrastat GR consolidation wrong when there is a cancelation mvt 102

[mouaz_benredjeb]

Hello everybody,

We are running the intrastat extractor RMIMST00 and we are meeting a problem with cancelation movement 102.

Indeed, the intrastat extractor will try to match the mvt 102 against mvt 101 in order to "clear" the quantities that have been canceled but this cancelation mvt 102 will be re-used accross many periods and hence cleared several times...

Here is an example that will help you understand the issue we have:

In period n, goods receipt (mvt 101) of 1000 pc and afterwards cancelation of 400 pc (mvt 102) hence the Intrastat extractor will match mvts 101 and 102 and display a goods receipt of 600 pc. So far so good...

The issue appears in the next reporting period (n1) where the cancelation mvt 102 is again used and matched against the goods receipts of period n1.

If we continue using the same example, say we do a goods receipt of 2000 pc in period n1 (and there are no goods mvt cancelation in the same period) then the Intrastat report will report a qty of 1600 pc (GR of 2000 pc in period n1 MINUS 400 pc coming from the cancelation in period n).

The calculation of the reported qtys in period n+1 is hence wrong...

I have tried to look for OSS notes and SDN threads about this issue but couldn't find anything... and it seems weired that this has not been spoted before....

We are about to send an OSS note to SAP but before that I wished to know if anyone had come accross the same issue ? If yes, how did you fix the problem ?

Thanks and regards.

Mouaz

Edited by: Mouaz BEN REDJEB on May 31, 2011 7:52 PM

[JL23 · Accepted solution]

If you have a problem in Intrastat, then always mention the country. Even it is a Euroean requirment, it is in detail quite different from country to country.

Please describe what you entered in your selection screen of transaction MEIS and what checkmarks are set.

[mouaz_benredjeb · Accepted solution]

Hello,

Actually we are using transaction /SAPSLL/IS_MM which shares 95% of its code with transaction MEIS. Indeed, both transactions use the same program (RMIMST00) and same routines (RMIMSELS). That is why I have given as a reference the program name (RMIMST00) instead of the transaction name.

When calling transaction /SAPSLL/IS_MM, we populate:

- Company code

- Purchasing organization

- Reporting month/year

- Reporting country

- Test mode = Yes

The issue with the cancelation mvt 102 is encountred for ANY reporting country. The issue is not specific to any country.

After analysis from our side (debugging), we believe the issue is in form "gr_cancellation_consolidate" in include "RMIMSELS".

Thanks for your help.

[JL23 · Accepted solution]

If no invoice exists for a goods receipt following the reporting month, the declaration of goods is postponed until the following month. If no invoice has been received a month later, the system uses the purchase order to determine the value of the goods and the goods movement is reported.

This was the general rule, but is done different per country now.

RMIMSELS has several coding lines that are very country specific like this for example:

  IF pv_reporting_country_iso2 = gc_country_iso2_germany.

you see the word germany there?

So these are already 2 justifications why I am asking for a country.

The text from the help file already tells you that SAP is looking for purchase orders and invoices, it does not directly lookup 102 movements.

Best you find the PO with this issue and analyze (or post here) what you see in the PO history like receipts, cancellationsm invoices, etc along with its posting date.

Further mention the value entered in Reporting month/year

[mouaz_benredjeb · Accepted solution]

I do understand that Intrastat reports vary from one country to another.

However, for our problem, we have the same issue for any reporting country...

In order to understand better the issue, here is a real life example that we have:

======================

FIRST PERIOD - 11/2010

======================

We have the following goods movements for scheduling agreement X in period 11/2010:

Movement Quantity

101 100500

101 36000

101 68435

101 168000

101 168000

102 -168000

101 168000

101 40500

Program /SAPSLL/IS_MM is executed for period 11/2010, Country = Romania.

In our example, there was no other cancelation movement 102 in previous periods before 11/2010.

Therefore the system is reporting only the goods receipts of the period 11/2010 which is OK for us. The cancelation movement 102 is taken into in the next period.

=======================

SECOND PERIOD - 12/2010

=======================

We have the following goods movements for scheduling agreement X in period 12/2010:

Movement Quantity

101 100300

101 150000

101 54000

101 177900

Program /SAPSLL/IS_MM is executed for period 12/2010, Country = Romania.

For this period, the system will take into account the GR cancelation in previous period.

Hence the Intrastat extractor will report following quantities:

(100300 + 150000 + 54000 + 177900) (- 168000) which gives the correct calculation at the end (i.e. cancelation mvt from period 1 is cleared in period 2).

======================

THIRD PERIOD - 01/2011

======================

We have the following goods movements for scheduling agreement X in period 01/2011:

101 216000

101 37500

101 65650

101 21000

101 21000

101 21000

101 15000

101 30000

101 21000

101 30000

101 30000

101 198000

Program /SAPSLL/IS_MM is executed for period 01/2011, Country = Romania.

In this period we only have goods receipts and no cancelations (no movement 102).

For this period, program /SAPSLL/IS_MM should be reporting the totality of the goods receipts of this period.

However, as the program still retrieves and uses the cancelation movement of period 11/2010, the last goods receipt (mvt 101) of 198000 pieces is reduced by 168000 pc and is reported as a GR of 30000 pc.

We believe that the program should be reporting a qty of 198000 pc not 30000 pc for this GR as the cancelation in 1st period was already cleared in the 2nd period calculation. However the system uses again the same cancelation for the 3rd period calculation (and all following periods...) which leads to incorrect calculation results.

After analysis of the problem from our side, we believe the issue comes from program "RMIMSELS" form "gr_cancellation_consolidate".

[JL23 · Accepted solution]

I am not using scheduling agreements, so I have no experience on their specifics in regard to Intrastat.

SAP recently fixed a bug with OSS Note 1436820 - Intrastat arrivals: Duplicate declaration of goods receipt

Please read this note to understand what SAP does in the selection in case of cancellations.

Maybe there is a site effect.

You should report your issue to SAP directly.

[mouaz_benredjeb · Accepted solution]

Thanks Jurgen for your answer.

I have seen this OSS note before but discarded it as we are in SP SAPKH60408 and the note is included in SP SAPKH60407.

However, thanks to your message, I had a closer look to the correction to implement in this OSS note and, as you said, the issue we have is may be a side effect of this correction.

We will get in touch with SAP today and I hope to post in the thread a feedack soon (with comments on the correction I hope...).

Thanks a lot.

[mouaz_benredjeb]

Issue is fixed by OSS note 1562102.

Thread is closed.

Thanks and regards.