on 04-25-2014 7:36 AM
Hi All,
I have a query in access sequence.
My situation was i was trying to do MIRO when system issued me message
I referred to forum and some where it was told that try out access sequence MWST for the condition type i am using. I was using JMOP and access sequence was JST1. The moment i changed it to MWST the issue was resolved but it left me with question that why cannot i use JST1 for it. Its after all an access sequence only and i can modify it to any extent to meet my requirement. For that i do not have to give country code. In JST1 the fields were plant/ material group. While creating the tax code V0 i have given county as IN. I have maintained FV11 and given plant and material group. So logically it should work but it did not . Now in an implementation scenario i cannot always use MWST for all condition types. Or whatever field i give , is it mandatory to give IN as one of the field also to overcome this error? As per my knowledge access Sequence is used to determine the entities entered and system will automatically propose the matching values. Then why not in this?
Please note that this discussion is not based on error but what i observed.?
Gurus could you please share your experience in it.
Message was edited by: G Lakshmipathi
Please use the subject effectively. Dont type the entire text there
HI,
Hope you are using condition based excise determination.
Assign the tax code to company code in the path: SPRO - Logistics - General - Tax on Goods Movements - India - Basic Settings - Determination of Excise Duty - Condition-Based Excise Determination - Assign Tax Code to Company Codes.
Maintain the settings, use the tax code with access sequence JST1 and test the scenario again.
Regards,
AKPT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Refer the KBA: 2003668 - Error message FF713 is issued when posting document due to blank percentage rate of tax co...
Also check the note: 1559145 - Frequently asked questions for Procurement in India: CIN
MIRO - Question Num 1
Regards,
AKPT
Hi,
It is due to inconsistency in condition tables. Did you check the note: 2003668 - Error message FF713 is issued when posting document due to blank percentage rate of tax co... The note suggests some correction report to correct the issue. Please check the note and proceed accordingly.
Regards,
AKPT
Hi AKPT MM,
Yes , Both Mr. lakshmipati and you were right. As per the note's resolution i found the exact similar entries in the tables A003, konp and Konh. And with the sample report i removed the entries with specific input parameters(through modifying the sample program). But after that when i did MIRO the same error came again. I did not expected this to happen. Please note i did not create any fresh PO or gr. I used the existing one.
This query is not related to CIN but related to MM and hence, moved from Internationalization and Unicode to SAP ERP - Logistics Materials Management (SAP MM)
G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think when you use JST1 access sequence , you wont specify any tax rates in the tax code while creating thru FTXP; those are maintained thru fv11. I suppose when the access sequence is MWST, the rates are specified in FTXP.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I believe when you use condition based process you maintain every detail in FV11 irrespective of any kind of access sequence. In my case i have maintained zero values as it is V0 zero input tax. I mapped the condition type JMOP with GL account. The same i did for JST1. If you use taxinn and you do not use condition record after using access sequence then in PO invoice tab try clicking the invoice tab. It wont open.
So you do not maintain rates in tax codes. The same is mapped in fv11/fv12 based on access sequence.
In that case i have not maintained in both cases in tax codes however i have maintained in fv11/fv12 for both cases. MWST also has place for price too.
Do refer the below OSS Notes explain clearly about your situation..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
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.