2011 Jul 28 6:07 AM
Hello All,
I have a problem, i want to identify the reason for the difference in ISU Reco keys and R/3 G/L. How to go about it...
What are the steps to check them. Which transactions are to be used.
Regards,
Charvi
2011 Jul 28 11:42 AM
Hi Charvi,
I assume that you have the list of reco keys which are there in ISU but not in R/3.
Based on the above assumption, you can have a three step analysis process-
(a) First check whether the reco keys are closed in ISU system or not. You can use the standard program RFKKFIKEYCLOSE or t.code FPG4 to check the status of these reco keys.
(b) If nothing comes up in step (a), you can check whether there is any problem in the transfer program to R/3. (T.code-FPG1)
(c) Once the above two steps are done, check the medium through which it updates the R/3 system, like normally it is through IDOCS. Check in T.code BD87, whether any IDOCS has failed or not while going into the R/3 system
This check you have to perform both at the ISU as well as the R/3 end..
In either or in all of them, you will get some reasons for the missing reco keys.
Hope it helps...
Thanks,
Amlan
2011 Jul 28 11:42 AM
Hi Charvi,
I assume that you have the list of reco keys which are there in ISU but not in R/3.
Based on the above assumption, you can have a three step analysis process-
(a) First check whether the reco keys are closed in ISU system or not. You can use the standard program RFKKFIKEYCLOSE or t.code FPG4 to check the status of these reco keys.
(b) If nothing comes up in step (a), you can check whether there is any problem in the transfer program to R/3. (T.code-FPG1)
(c) Once the above two steps are done, check the medium through which it updates the R/3 system, like normally it is through IDOCS. Check in T.code BD87, whether any IDOCS has failed or not while going into the R/3 system
This check you have to perform both at the ISU as well as the R/3 end..
In either or in all of them, you will get some reasons for the missing reco keys.
Hope it helps...
Thanks,
Amlan