on 07-13-2010 11:02 AM
Hi All
We are trying to lock the PO and system will not allow to lock the PO. We are getting the below error message 'Foreign Trade data: incompletion log.
business transaction type for foreign trade - EXART
Export/Import procedure for foreign trade - EXPRF
Country of orgin of the material - HERKL
Commodity code / import code number for foreign trade STAWN
Please help us to resolve the issue.
Regards
K.Gunasekar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Note 173411 - Incompletion procedures for foreign trade
Summary
Symptom
In a delivery or invoice, the header and item foreign trade data are
incomplete. It is unclear what the incompletion procedure checks, and
what needs to be configured to ensure completeness.
Through release 4.5B, the incompletion check for foreign trade in
deliveries and invoices was hard-coded. When the delivery or invoice
is recognized by the system as an export (i.e., the country code of the
shipping point does not equal the country code of the ship-to party),
the system invokes an incompletion procedure to ensure that the document contains the minimum data necessary for compliance in export
reporting.
By default, the following fields are checked in the incompletion
procedure:
Header
Field/Name Source (t-code)
EXPVZ Mode of transport IMG- (OVE2, OVE3), Routes: (0VTC)
ZOLLA Office of exit IMG- (OVE2, OVE3), Routes: (0VTC)
IEVER Inland mode of transport IMG- (OVE2, OVE3), Routes: (0VTC)
Item
Field/Name Source (t-code)
STAWN Commodity Code Material Master
HERKL Country of Origin Material Master
EXPRF Export procedure IMG- (OVE6, OVE7)
EXART Business Transaction Type IMG- (OVE4, OVE5)
Other terms
VF072, incompletion, EIKP, EIPO, UVALL, VL02, VF02, T609, VF01, VF04,
VF01
Reason and Prerequisites
Incomplete configuration for export documents.
Solution
Maintain configuration for foreign trade.
Beginning with release 4.5A, the incompletion procedure is now config-
urable. An incompletion schema can now be created using customizing
transactions VI29 and VI49. (NOTE: if NO schema is maintained, the
system will automatically use the hard-coded check by default).
The incompletion schema in transactions VI29 and VI49 can be maintained
in releases 40A and 40B, but does not become active until release 45A.
If one chooses, for reasons of business process, not to use the
incompletion procedure, then it can be deactivated.
For releases 3.0x through 4.6x, this is accomplished by utilizing the
user-exits contained in enhancement V50EPROP (see related note 118573).
User | Count |
---|---|
95 | |
11 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.