Skip to Content
avatar image
Former Member

JMAN condition type

Dear Experts

I have used JMAN condition type to enter the manual excise details in my Factory Pricing Procedure.

There are a few questions I had:

1.  The condition type JMAN has a condition class of Taxes.  Should this condition be maintained in my tax procedure as it is missing there?

2. When the std pricing procedure for factory sale - JINFAC was checked this condition type did not have any Account Key assigned - Should an account key be assigned by us to ensure the values hit the excise G/Ls? - I tried assigning EXD to the JMAN condition type but during billing am getting this error

"Error in account determination: table T030K key LKR EXD - Message no. FF709"

3. Can I create a seperate manual excise condition for AED values too?  This is an "As such" scenario wherein I need to pass on exact excise values to my customer.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    May 08, 2013 at 10:10 AM


    As per my understanding, JMAN condition is a manual excise condition used in SD for entering the excise values manually and value you enter here automatically adopts to your A/R BED condition.

    and you maintain the G/L accounts for your excise accounts in the transaction - VKOA.

    Only for VAT/CST you have maintain the GL against the account key in transaction - OB40.

    Hope it is clear.

    Please elaborate your scenario so that you can get the best solution.

    Thanks n Regards,

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Dear Himavanth

      I created two new manual condition types for inputting the "As Such" excise values.  I kept the condition Class as"Discount/Surcharge" and it works.

      The process followed for anyone with similar issue was:

      1. Create two new condition types with the condition class as "Discount/Surcharge"

      2. Assign the same to the Pricing Procedure which in the above scenario was derived from JINFAC,

      3. Assign Account Key to the condition the above instance the account key assigned was "EXD"

      4. Assign the condition types to Classify Condition Types as BEDARTOT A/R BED TOT and AEDARTOT A/R AED TOT

      5. Assign the movement type used in delivery to the "Specify Which Movement Types Involve Excise Invoices".



  • May 08, 2013 at 08:35 AM


    Maintain settings in OB40



    Add comment
    10|10000 characters needed characters exceeded