02-02-2015 8:14 AM
Hi,
We are facing an issue with Stock Transfer of Excisable Goods from an excisable depot to another excisable depot which had arrived from an excisable manufacturing plant.
We are following the below steps:
1. Create STO PO at Depot A (ME21N)
2. Delivery of Goods from Depot B (VL10B)
3. Create Depot Excise Invoice at Depot B with reference to Orginal Manufacturing Excise Invoice (J1IJ)
4. Goods Receipt at Depot A (MIGO)
5. Capture Excise at Depot A (J1IG)
We are getting stuck at Step 5. When we are performing J1IG and entering Depot Excise Invoice or Original Manufacturing Excise Invoice, we are getting an error message as "Excise invoice does not exist in Supplying Plant".
Kindly suggest how to capture excise at Depot A.
Regards,
Debarshi
02-02-2015 11:16 AM
02-09-2015 11:10 AM
Dear G. Lakshmipathi,
We have tried your solution but we are still stuck at the same place.
In J1IG, if we enter the Depot B excise invoice and press enter, we are getting the message "Excise invoice does not exist in Supplying Plant".
If we enter the Original Manufacturing excise invoice and press enter, then also we are getting the message "Excise invoice does not exist in Supplying Plant".
If we enter the Depot B excise invoice and give a tick in the "Depot Excise Invoice" and press enter, we are getting into an infinite loop.
Kindly suggest how we can capture the excise at Depot A.
Regards,
Debarshi
02-02-2015 12:17 PM
Hi Debarshi,
SAP Note is available for Depot to Depot scenario.
You need to implement this note for the issue.
1028677 - J1IG- Depot to depot transfer using Depot Excise
Invoice
Regards
Binoy
02-09-2015 11:16 AM
Hi Binoy,
We have checked and found that the suggested Note has already been implemented.
We have also incorporated the following Notes and code corrections as suggested by SAP to better the performance of CIN:
413446: Indexes for CIN tables for performance improvement
1960247: Runtime error DYNPRO_FIELD_CONVERSION displayed while
capturing excise invoice
But still the issue persists.
Please help.
Regards,
Debarshi
02-09-2015 12:38 PM
Have you reported this to SAP. I think in this case you need to report this case through SAP Service market Place.
Regards
Binoy
02-09-2015 1:16 PM
We have raised the incident to SAP but they have also not been able to provide any solution to the above incident.
Thus, we are trying to find if anyone faced such issue and had resolved through certain solution.
Regards,
Debarshi
02-09-2015 1:26 PM
Try debugging it and see if you can find out the rootcause. Please post some supporting screenshots also.
If you are working in Dev environment, try to update RG23D during GRN at depot itself and see if this is working fine with MIGO transaction.
In addition, SAP suggest that you ensure that the supplying plant#s official document number and date are given as reference and not the internal document number.
Message was edited by: Ashok Kumar Telugu
02-09-2015 2:01 PM
Have a look at the following note though it is not related to Depot but STO between plants.
Though the note talks about the error message skips, your ABAP team can still go through the coding and compare the same with your system so that definitely, you will get some inputs from there
G. Lakshmipathi