Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Manual Condition type in Purchase order

Former Member
0 Kudos

Hi Experts,

  We are using ZTAXINN procedure, I want to enter the excise condition type values manually in ME21N.

  I have removed the access sequence for those condition types, Still i am unable to enter the condition values manually.

  Please guide me to resolve the issue.

Regards,

Narendra

11 REPLIES 11

Lakshmipathi
Active Contributor
0 Kudos

Removing access sequence alone wont help you.  You also need to carry out the following changes

  • In Pricing (M/08) Procedure, for that condition type, check the box for "Manual"
  • For Condition Type (M/06), maintain blank field for "Manual entries"

Now retry the process and update here

G. Lakshmipathi

0 Kudos

Thanks for your replay.

I want enter the excise condition types JMOP,JECP etc manually in the purchase order.

0 Kudos

Hi narendra,

JMOP &JECP are related to tax condition types. percentage values for your condition types are based on "FTXP".

Go to FTXP enter your country & tax code. Against your condition type for particular tax code enter your value in percentage...

You don't need to enter percentage manually, it automatically fetches from FTXP..Try to maintain condition records in fv11.

Regards

Subbu.

0 Kudos

Thanks for your reply.

My requirement, I want to enter the tax values(JMOP =Rs 1240etc ) manually in the purchase order.

Regards,

Narendra

0 Kudos

Hi narendra,

You cannot enter value directly in the purchase order, it will be coming directly from FTXP for your particular tax code. or you have to maintain condition record for your particular condition type example (JMOP) in FV11.

Regards

Subbu.

0 Kudos

Instead of trying to enter the manual excise in the tax procedure, make it a pricing condition type (ZMOP) using M/06, allow manual entries and add it to your pricing procedure using M/08. Here tick 'manual' to allow manual input.

Advise the user that whenever he uses these Manual condition types in the schema, he should choose a 0% tax code, to avoid double tax calculation.

0 Kudos

What is the requirement to enter the Excise conditions manually? You can maintain the condition records in FV11 and the said conditions will automatically flow into your Purchase order.

If the Excise bifurcation is not known you can make use of JEXC manual excise condition type from PO condition tab and enter the lumpsum amount. When you receive the excise invoice alongwith goods, you can enter the Excise duties as per invoice.

Pre requisite is to Maintain the Condition records for JMOP, JMX1 etc with Zero rate and 100% respectively.

Check and revert back with your observations.

Former Member
0 Kudos

hii Narendra... u cannot enter conditions manually in PO... it comes the tax code given in invoice tax..... u can define the tax code in ftxp and maintain the percentage in fv11 and check...assign points if useful....

Regards,

Abhay

Former Member
0 Kudos

Hi,

You can not enter manual condition in Taxinn, better define new condition type in M/06 and assign it to M/08.

So in MM pricing you can use manual condition related to tax

0 Kudos

Thanks for your reply.

If i will create the new condition type in m/06 and assigning in the m/08.

What about the account keys?

Shall i use the same account key which i am using in ZTAXINN?

Prasoon
Active Contributor
0 Kudos

Hi,

    You may use the standard condition type JEXC (Manual Excise) in MM pricing procedure. Maintain JEXC as statistical condition and maintain subtotal as 5 against JEXC  in M/08.

Now, go to OBQ3 and maintain  calculation type as 355 against JMOP.

   Now system will copy the JEXC value from MM pricing to JMOP in tax procedure.

Note: 1. Tax code should be assigned to company code.

          2. JMOP condition type should be maintained correctly in "classify condition type" configuration.

Test the scenario and revert back.

Regards,

AKPT