on 06-18-2011 10:15 AM
Hi
When taking consistency check in APO it is showing " Version 000 in planning area PRODUCTS_PA_NOS locked by user ALEREMOTE" . Have checked all the back ground process and nun of the job is pending / schedule in Aleremote.
What could be the reason, why it is showing this message.
Regrds
VS
As the ALEREMOTE user is usually used for connectivity between different SAP Systems, it is worth checking to see if there is any activity via one of your RFC Destinations. For example, a blocked CIF queue from R/3 or an issue with a BW Extract.
Regards
Ian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all got the issue resolved, thnx a lot to all. It was because of incosistency in SM12 which dose not show n e block entry but actually that entry was blocked. After removing inconsistency in SM12 it got resolved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
When do you usuall run consistency check job? Check if any users are doing something in the foreground when you run the job. They may be running some custom programs in R/3 that make an RFC call to the APO system and retrieves some info from planning area . ALEREMOTE id indicates that some activity in R/3 that accesses APO objects is causing this issue. Take help from basis and they will be able to solve the issue
Thanks
Aparna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Vikas,
May be you can see in SM04 transcation if any RFC call is active in system and also can check in SM12 transaction for any extra system locks. If nothing is shown there and still your job fails then you might ask Basis to check at system level.
Thanks
Deepak
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
15 | |
4 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.