SAP for Utilities Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and collaborate on building a sustainable energy future. Join the discussion.
cancel
Showing results for 
Search instead for 
Did you mean: 

short dump while creating a new tax code

Former Member
0 Kudos
328

Hi All,

I am trying to create a new tax code. But system is giving short dump like "Express document terminate".

I will explain the steps which I followed for creating the new tax code. Please validate.

  1. I created a new transaction MW6 using tcode OBCN. set properties as output tax and seperate line item.
  2. I maintained posting settings for new transaction MW6 using tcode OB40. Assigned tax G/L account, posting keys--Debit :40 and Credit :50 and also posting rules.
  3. I created new condition type JRC5. Access sequence assigned as TAXJ
  4. I changed the taxing procedure TAXCAJ by including the new condition type JRC5 as a new step and assigned account key MW6.
  5. Using FTXP tcode I created the new tax code G6 with settings as output tax and check id checkbox selected
  6. Using FQZ8 I assigned the new tax account to the new tax code. combination is like tax code G6 Transaction MW6.
  7. Now I assigned my tax code to the tax determination id; G6 tax code assigned to tax det id G6
  8. I maintained Tax percentage for the new tax code using FTXP.
  9. once I save the new tax code in FTXP system gives short dump and a popup is displayed saying Express document "Update was terminated"
  10. I tried to assign tax percentage using FV11 by using condition type and tax code, there also I am getting same short dump.

When I analyzed the short dump it occured at the time of database update to A053 table.

Please help me .. Is there anything wrong with the config steps or am I missing any step.

Please let me know.

Regards,

Suresh

1 ACCEPTED SOLUTION

Former Member
0 Kudos
174

Issue resolved. Followed instructions provided in SAP-note 686357.

View solution in original post

1 REPLY 1

Former Member
0 Kudos
175

Issue resolved. Followed instructions provided in SAP-note 686357.