MEIS Arrival INTRASTAT without GR / IR

[Former Member]

Hello All,

In our business scenario we use regular Schedule agreement (LPA) for INTRASTAT Arrivals declarations at Germany plant (DE)for which goods shipped from France country (FR) plant.

We have a very particular scenario where in there is no GR / IR done on the schedule agreement. Instead we call user exit to do transfer posting using MB1B 301 movement.

Since its a cross broder goods receipt, there MUST be INTRASTAT declaration at Germany plant.

There are SAP std settings as below

Table: V_T609IS Foreign Trade: Declarations to Auth: Data Selection Control

Goods receipt and invoice will be considered

A Shipping notification and invoice will be considered

B Only invoice will be considered

C Report: GR / Import Data: MM Purchase Order

I understand that atleast there is a GR or IR required to declare Arrivals INTRASTAT.

Question: Is there a technical possibility by user exit / program change to by-pass the above checks and still able to declare MEIS Arrivals file?

Any possibilities of MEIS Arrivals generating file without GR and IR as I described above?

Really appreciate your valuable inputs.

Thanks

[former_member209632]

This message was moderated.

[JL23]

If you call a user exit to perform MB1B with a 301 movement anyway, why dont you call BAPI_GOODSMVT_CREATE instead and post a 101 receipt?

Why dont you like to have a 101 with reference to the schedule agreement?

What are you doing with your schedule agreement? it will never close, it will not have a movement history, it is good for almost nothing.

If you dont follow the process, then you may need to use VEFU to create a record for INTRASTAT manually.

[JL23]

from OSS Note 481600 - FAQ: Import data in purchasing:

Why is no statistical value determined in a scheduling agreement?
Answer:
The cause for this is that in general the scheduling agreement uses master conditions (time-dependent conditions).The statistical value, however, can only be determined from document conditions.
Which condition type is used in the scheduling agreement can be set depending on the document type in Customizing.In order to use document conditions for a certain document type, you must call Transaction OLME (Purchasing Customizing) and follow the menu path: Purchasing -> Scheduling Agreement -> Define Document Types.Remove flag 'time-dependent conditions' for the particular document type.
Also refer to Note 83964.

[former_member182673]

How are you doing this material transfer. In case the scenario is like the following.

Your vendor is sending the goods to your warehouse in France and then you do a 301 from FR warehouse to your German plant, then to get this transfer into INTRASTAT you have to create an STO between the warehouse and the german plant, then transactions posted againtst these STOs will automatically appear in INTRASTAT arrivals report.

If the scenario is something else, then ideally you should revisit the scenario on how this transaction is posted and why it is posted this way?

[Former Member]

Hi

Appreciate any thoughts on this?

-

---

In our scenario we have sales process and Purchasing process as well. From purchasing perspective Vendor Scheduling agreement created part of standard Buy/selll relationship instead of TSA/STO between two plants (FR and DE plants) under same company code.

To avoid addtional financial postings b/w two plants under same CoCd, MB1B is done 301 movement via user exit from Inbound delivery processing perspective (instead of regular 601 SD and 101 MM mvmnts)

from Arrivals INTRASTAT perpective Vendor SA will be used for declaration and there will be NO goods movement / Invoice (GR / IR)

Foreign Trade/Customs --> Periodic Declarations --> Data Selection Control --> Data Selection Control

Foreign Trade: Declarations to Auth: Data selection control

Goods receipt and invoice will be considered

A Shipping notification and invoice will be considered

B Only invoice will be considered

C Report: GR / Import Data: MM Purchase Order

Q) With above options only possible, is it feasible to still to achieve INTRASTAT Arrivals at DE.

Q) Any technical / functional options to by pass above check as there is No GR/IR.

-

---

Now, we have created new custom t-code ZMEIS which by pass the check for GR ( which we do 301 movement via user exit) and report picking the VEIAV entries. We have put logic to calculate Invoice value = Delivery Qty (No good movement) * gross price A016

while calculating Statistical value (maintained MEK1 @ incoterms) how to pull the respective GRWR condition value at program level to arrive at Statistical value = GRWR * Total invoice value and similarly how to calculate tare mass value.

Really appreciate your inputs!!

Thanks

Edited by: Siva Prasad Jetti on Aug 2, 2011 1:19 AM

[former_member182673]

One thing is clear is strangely you are using scheduling agreement for no purpose as it is not used for posting GR & IR. Given this is the case instead of going for an enhancement to report the movements under INTRASTAT, use VEFU and direcly add these transactions for reporting into VEIAV table, then when you run MEIS, these transactions will appear in the report.