How to make JMOD,JECS,JA1X condition type as Statistical in SD pricing procedure when TAXINJ is used.

[Former Member]

In export scenario we are not paying exicse duty components as long as ARE1/Bond is there.We are using TAXINJ tax procedure,where JMOD,JECS and JA1X condition type is being used.Routine 355 and 366 is assigned to it in SD pricing procedure.WE made these condition types as statistical in pricing procedure but it appears non statistical in sales order therefore GL posting/accounting entries are generated. We dont want to generate accounting entries during excise invoice creation.When we save commercial invoice(VF01)excise invoice is generated in the background based on excise group settings.Kindly suggest.

[Former Member]

Hi NITIN,

as per my understanding you have mark as statical in tax procedure but if ou r looking in order so it will get as non statical bcoz that is picking form pricing procedure

& tax procedure into OBBG

please correct me if understanding is worng

Thanks

[Former Member]

Hi Vicky,

We have marked  JMOD,JECS and JA1X statistical in SD pricing procedure but appears non statistical in sales order item.Its a TAXINJ tax procedure and export scenario.

[Former Member]

Hi Nitin,

Did you create separate pricing procedure for Export and Domestic?

If no then please create separate pricing procedure for Export and Domestic.

Regards,

Vikas

[Former Member]

Hi Nitin ,

i agree with vikas : create seprate pricing pro. for export & if u created then assign it to your export customer in OVKK''

Thanks

[Lakshmipathi]

Not sure, which pricing procedure you are using.  The standard pricing procedure for exports process is JEXPOR.  Ideally, you should have one Series Group each for domestic and exports process.

G. Lakshmipathi

[Former Member]

Hi Lakshmipathi Ji,

JEXPOR,JINEXP not having duty condition types as we need to update duty components in ARE1 ,need to flow duty values in documents though they are notional.We are having separate pricing procedure for export sale where JEX2,JECX,JA1Y made statistical.

But when we checked tax procedure TAXINJ found that JMOD,JECS and JA1X are not statistical (having different account key than SD pricing procedure) because of that they are posting from FI though in SD pricing they are statistical.

In SAP standard TAXINJ also JMOD,JECS and JA1X are statistical or not.

Thanks to all for prompt replay.

Nitin

[Lakshmipathi]

Though your export pricing procedure dont have excise condition types, while creating an excise invoice, system will consider all those condition types from TAXINJ from OBQ3.  Please test and update here.

G. Lakshmipathi

[Former Member]

Yes.removed excise condition types in  export pricing procedure except UTXJ, but condition type JMOD,JECS and JA1X are appearing in sales order only and not in billing document so excise invoice is not having these three duty values.

Thanks.

Nitin

[phanikumar_v3]

Now the issue is resolved and in our control--Your excise amounts are not been carried to Billing from sales order--yes na.

Have you assigned your tax code to your Company code?

Check this...(IMG>>Log-General>>tax on goods movement>>India>>Basic settings>>Determination of excise duty>>Condition based excise determination>>Assign tax code to Company code)

Phanikumar

[Former Member]

Thanks for suggestion,Phanikumar,

Tax code is assigned to company code but it is not working.

Nitin

[Lakshmipathi]

I think, somewhere, your configuration went wrong and that is why, it is causing the issue.  Just go through the following note and ensure whatever configuration is recommended there, your system is in line with this note. 

• Note 821826 - Taxes Configuration for VAT Solution(TAXINJ)

G. Lakshmipathi

[phanikumar_v3]

Dear Nitin,

One thumb rule--when MM procedures is on(Like Imports)--so You need to maintain these Excise/Tax condition types as required either TAXINN/TAXINJ procedures.

If SD Procedure is on(Example In Exports)---then maintain these Excise/Tax condition types as required in your SD pricing procedures(JINEXP etc)

Hope this helps.

Phanikumar

[Former Member]

Hi Experts,

In TAXINJ,JMOD condition type is non statistical,so it is posting.As JMOD is been used in different domestic pricing procedure since many years,business dont want to change customizing of TAXINJ for export sale only.We have used an exit for this to get rid of an issue.

Thanks to all....

Regards,

Nitin