SAP Knowledge Base Article

Symptom

l 'All Part1 entries have been canceled for the excise invoice' error occurs when J1IEX is executed. l Cannot cancel the excise invoice via J1IEX.  l Cannot post the excise invoice in J1IEX.   l Excise values are appearing against "Credit due" field in J1IEX. 

Environment

l SAP Release Independent l This is relevant for India Localisation or Country India version (CIN) component l This is relevant for CIN Materials Managment(MM) module

Reproducing the Issue

Scenario 1

1. Goto Transaction J1IEX. 2. Select option POST. 3. Enter excise invoice number/internal document number. 4. Press Enter. 5. Error 'All part1 entries have been canceled for the excise invoice' occurs.

Scenario 2

1. Goto transaction J1IEX. 2. Select option CANCEL. 3. Enter excise invoice number/internal document number. 4. Press Enter. 5. Error 'All part1 entries have been canceled for the excise invoice' occurs.

Cause

l Excise invoice number or excise invoice date has been changed. l Excise invoice year in J_1IEXCDTL and J_1IGRXREF table is not the same. l Excise captured in MIGO via 103 movement which is for blocked stock.

Resolution

1. Check in J_1IGRXREF and J_1IPART1 table if there is any cancelation entry available for that EXNUM/MBLNR. 

2. Check for excise invoice number(EXNUM), excise invoice date(EXDAT) and excise year(EXYEAR) fields in J_1IEXCDTL and J_1IGRXREF tables. The field values should match otherwise it will lead to this error. If the field values are not matching then you should update the values in J_1IGRXREF table as per the values in J_1IEXCDTL table by writing a small Z program or via direct table updation SE16N(If allowed to do so).

3. Once the excise invoice is captured and referred in MIGO, the excise invoice no(EXNUM) and excise invoice date(EXDAT) should not be changed. To disable Excise invoice no and excise invoice date fields in J1IEX, the following SAP Notes are released and it SHOULD be applied. 1285986   Excise amount appears wrongly in Credit due column in J1IEX 1346926   Disabling Excise invoice no & date in change mode in J1IEX 1406505   Disabling Excise invoice no & date in change mode in J1IEX

4. Excise invoice should not be captured or captured and posted via MIGO 103 movement, because 103 movement is for blocked stock and stock is not actually received. It should be captured via MIGO 105 only.  If the excise is already captured via MIGO 103 then it should be canceled and redone via MIGO 105.

5. Also J_1IPART1 table should not be updated for MIGO 103 movement. 'No excise entry' should be done in MIGO 103.

6. Ensure that there is a blank entry set for the movement types(101, 102, 105, 106,etc.,) in J_1IMVMT table as below - 101         << 101  RG23A 101  RG23C 101  RG1

7. For account assigned POs, below SAP Notes should be applied 864981    Error 4F113 during J1IEX_P for A/C Assigned PO 805752    4F113 error during J1IEX_P for a/c assigned PO

8. Below SAP Note should also be applied to avoid such inconsistencies in future-

    1710179 - All Part1 entries have been canceled for excise invoice in transaction J1IEX , 4F113 error  

Version   1     Validity: 20.04.2012 - active   Language   English

1706543   Incorrect Excise year for previous fiscal year posting-MIGO

 

See Also

1596377  Error 4F-113 while excise invoice posting in J1IEX_P-CIN4.0A

 

Keywords

Part2, Posting, Vendor excise

Header Data

Product

This document is not restricted to a product or product version

References

Released On 04.10.2012 15:55:03

Release Status Released to Customer

Component XX-CSC-IN-MM Materials Management

Priority Normal

Category Problem