on 03-24-2012 12:23 PM
Dear All,
I am doing an import scenario. Now after creating the PO i did MIRO.
The MIRO accounting is right.
8 | customs office | 28.76- |
20409015 | CVD Duty Rec Basic | 20.20 |
20409015 | CVD Duty Rec Basic | 8.48 |
20409015 | CVD Duty Rec Basic | 0.08 |
After that i did MIGO(since import so there will be no taxes)
20401020 | Inv - RM- Imp | 420.28 |
10302010 | GR/IR Clearing A/c | 400.00- |
20409015 | CVD Duty Rec Basic | 20.20- |
20409015 | CVD Duty Rec Basic | 0.08- |
We can see that this entry is not coming in the migo which should have come.
I have checked the OBYC setting and also the m/08. I did not found any mistake but still i want to confirm if i did some wrong config or am i missing something.
Your accounting shown is confusing, Where are other duties in MIRO, Alltogether there should be 7 duties, apart from that CVD values are not seen in MIGO because you can take Credit for 3 CVD & 1 AED duties, Refer below link & Sublink to understand the Import Process,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi tej,
WE ARE IN THE INITIAL PHASE OF THE PROCESS MAPPING. This is done in development server. The condition types are mapped bt while creating the PO I have not given all the values. The accounting entries generated in migo and miro are the corresponding condition types for which % is maintained in PO. My concern is one of the line item is not generating in the migo accounting info. That conditon type is JC1V. IN CVD condition type. i ahve mapped all the cess and ecess and cvd in one gl account linking them with FR3 key in pricing procedure.
according to what i mapped , the entries re right in MIRO but not in migo.O
My concern is one of the line item is not generating in the migo accounting info. That conditon type is JC1V. IN CVD condition type. i ahve mapped all the cess and ecess and cvd in one gl account linking them with FR3 key in pricing procedure.
Seeing your Screen Shot I would recommend to change the Account & Accrual key of
JCDB - Basic Custom Duty to FR3 from CVD, Reason is it should hit the Inventory account,
Also in MIGO you will see only 3 duties in hitting stock account & not the 3 CVD conditions because it will hit your RG23 Part -II entries so that you can take settoff, this is standard Indian Import Setup.
Accounting at the time of MIGO will consist of only 3 below customs duties & not the CVD conditions,
JCDB, JCES, JSDB
Other 4 duties should hit the Cenvat Clearing when you Post the Part-II entries.
Thank you for your support. I have one more query: Why should i have to do J1iex because i am giving tax code v0 so what is the need of it.
what process i followed was
PO creation
miro for customs clearing
migo (with no excise entry)
miro for the goods supplier
the following scrrenshot contains the mapping of excise default and obyc seting for cvd clearing and fr3 account key as u have said.
am i missing any more config ?
pl suggest.
In case of Imports excise do not flow from Tax code but from Commercial Invoice(i.e. through Customs MIRO) as you have maintained in Excise Defaults,
You need to do J1IEX to post the 3 CVD + 1 AED values from GL assigned to CVD ti Cenvat Clearing Account so that you can take Setoff of this Values
Your Process must include the excise Posting, Since in MIGO you are not capturing Excise , then you need to do J1IEX for Excise Capture & Post,
Hi,
you have to check your condition type setting once again
check following link
http://scn.sap.com/thread/724543
http://scn.sap.com/thread/1815168
Kailas Ugale
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
In MIGO under Excise Tab you able to see this as BED
But Accounting entries will appear in J1IEX if you posted the document.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
12 | |
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.