GRWR incl. or excl. freight for intrastat and ec sales list

[former_member553601]

Hi experts,

I need a hint from a foreign trade specialist for the european union (germany)...

We use the standard condition GRWR for all incoterms with 100% of the net-value.

As far as I know this condition is used for intrastat as well as for the EC-sales-list. Am I right so far?

Actually the value of the EC sales list includes freight-costs ecc. which is not correct.

Now I have the request to subtract the freight-costs for the EC sales list.

If I subtract the freight-costs in GRWR, do I get any problems with intrastat or any other foreign trade themes?

Thanks in advance for your kind help!

Nicole

[Former Member]

GRWR will be used only for INTRASTAT reporting for EU. GRWR uses Requirement 8 and Alt Cond Base value 2. If the net value is zero you need to take cost as base to determine the GRWR value.

If you need to determine the Sales list , better to use a different condition type for this purposes. Iin your pricing condition type you can determine "Net Value" before applying the freight and Tax. Send the "Net value" to sub total 4 and read that sub total to get the list price before freight.

Regards

Sai

[Former Member]

Hello Nicole

To your first question, yes, Statistical Value as computed form GRWR is used for all kinds of Declarations and reports to authorities.

This is a measure of the actual value of the goods imported or exported and does not include the value added tax (VAT) or all of the transportation and insurance costs.

But I don't see why you should do additional work on your own, by now SAP should have included it in the standard.So if you are using Alternative formula for condition base value '2'- Routine FV63A002- Net value - for GRWR and it does not meet your requirements, then go ahead and change it to 6 ( KZWI2) - Routine FV63A006- which is pure net value for an item. But check once with your SD/MM colleagues from other companies as I strongly feel this should have been taken care of in the standard.

Hope this helps.

[Former Member]

Hi,

In general You need to maintain condition type GRWR in pricing procedure and give requirement as 8, make it statistcal and give value as 2 for alternative condition base value

For your information. This infor is there in the help

A company sells and procures products domestically as well as internationally. Every item that it imports or exports must have a statistical value associated with it when it passes through customs. The statistical value is the net domestic value (fair market value) of a product when it crosses a border. The statistical value is printed on the appropriate customs documents such as the Single Administrative Document (SAD) in the EC, the Shipper's Export Declaration (SED) in the US, and the export report in Japan. Within the standard delivered R/3 system, condition type GRWR is available to calculate the statistical value in the pricing procedure. Pricing requirement '8' should be assigned to this condition type in the pricing procedure so that it is only calculated if the document is relevant for export / import.

some useful threads -

regards,

Raj

[Former Member]

Hi,

It would be easier to explain a scenario on a standard process.

So it is hard to find out if your problem has to do with the differences and does work in normal process, or it does not work at all.

Why is the PO value 200 and why the GR value 180?

Why would you run the report with the same business case in September and in August ?

The general way (which may vary from country to country) is :

-if the goods movement was in January - and the invoice posted in January - then the movement is listed in the Intrastat report for January using the value from the invoice and taking into account the GRWR percentage to calculate the statistical value.

- if the goods movement was in January - and the invoice was not received when you execute the Intrastat report for January, then the movement is not included in the January report .

- if the movement was in January, and invoice receipt was after the January intrastat run, then the movement will be considered in the February report, using the value from the invoice and taking into account the GRWR percentage to calculate the statistical value.

- if the movement was in January, and invoice receipt was not even done when the February intrastat run is executed, then SAP reports the january movement in February report but valuated with the PO value, and taking into account the GRWR percentage to calculate the statistical value.

Check in table VEIAV either with SE16 or VEFU transaction what statistical value you can see there for your PO.

-

---

the GRWR cross border value is determined via a percentage

depending on your incoterms it is either deducted or added to the PO price.

if your plant is directly at the border, then your statistical value is always a 100 % of the invoice value.

Depending on the EU country a statistical cross border value has to be reported or not.

-

---

Regards,

Raj