on 03-23-2009 10:05 AM
Hi Gurus,
I am facing the following error in the standard ess implementation.
we have EP7.0 and ess BusinessPackage1.0 SP12.In this when ever i am editing the PerminentAddress
Under PersonalInformation--> Address and click of the save button it is giving the following error.
Screen output without connection to user., error key: RFC_ERROR_SYSTEM_FAILURE:
In this forum i have got some solutions for this, even thoung i hav applied those, still my problem was not
solved.
JCO Connections are working fine.
SSO is working Fine.
Is there any thing to do with user Authorizations.
Regards
Surya
Hi All,
This probelm is solved.
this is the problem with user created in R/3 which dont have proper parameters and it's values.
su01->Parametes tab you can see all the para meters assigned to the user.
Regards
Surya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Satya,
It is issue with HR Functional setting Address application.
Ask your HR Functional Consultant to check use-case settings and other config setings (Conformation page and Detached Frame work classes..etc)
Regards
-SS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bala
I am very thankful to your quick reply.
i have already checked the dump in st22 , From the dump i understand that while executing the
function module it is refering some NULL value. I have asked my abap to look in to this.
Bala is there any other setting we have to do , other than tracing the function module.
Currently EA-HR patch level is 28.
Regards
Surya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Surya,
did you check the logs in st22
Thanks
Bala Duvvuri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
This is because of some problem with the BAPI's used in processing the screen. Please check this with your ABAP team.
We had the same problem once. Our ABAP team rectified the BAPIs and the error was resolved.
Regards,
Sai
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
8 | |
7 | |
4 | |
4 | |
3 | |
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.