Claims wagetype /563

Hi All,
When retroactive accounting is triggered in payroll the wage type amounts from IT0014 is getting added to claims wage type /563 in the present period, Hence the IT0014 amount is getting deducted twice.
Is there any way i can remove wage types from IT0014 to be calculated in retroactive accounting. can it be done from processing class or editing any PCR.
Pls help.

Dear Neharika,
If you want wagetypes in IT0014 to be completely ignored by the retro, try making settings in infotype atrributes table V_T582A. make it as "infotype is not relevant for retro accounting.
hope this helps
Cheers

Similar Messages

Wagetypes /561(Claim) and /563(Claim from Previous month

Hi,
Please explain the wagetypes /561(Claim) and /563(Claim from Previous month). and thier relevance.
I know that the difference between /561 and /563 shows the net amount that SAP has reclaimed from the overpayment in a single month.
What in case these wagetypes occur in case of a LEAVER? Then how this should be dealt with.

Hi Srijit,
Thanks for replying.
My case is of an employee who left the company in June08. His last payroll was run in June.
Now when the salary of february was processed it came to notice that Rs388/- was posted into employee suspense account. His salary statement shows Take Home pay as Zero.
The posting shows the following:
/552 ( stat net adj) ( amount)388.00 (credit)
/561 (claim) (amount)50,390.00 ( debit)
/563(claim from prev month) (amount) 50,002.00( credit)
This is the scenario.
Edited by: dips on Feb 27, 2009 7:32 AM
Edited by: dips on Feb 27, 2009 7:33 AM
Edited by: dips on Feb 27, 2009 7:36 AM

Payroll issue regarding the Claims - /561 and /563

Hi Payroll Experts,
I have a payroll issue regarding the Claims - /561 and /563 (October PY Run)
When i m runnning the Current month Payroll(October PY Run), Total Earning - total deductions are not matching with Net Pay. later i came to know that the system creates the WT /561 and deducts from the Net Pay.
But as per the Employee Payment Details , there is no recovery required from the employee for the past one year. But even then the system creates the WT /561. and deducts the same from NET Pay.
The followng are the WT details
IN - Period
OCT 2011
     /101 Total gross amount     118,897.00
     /110 Net payments/deductions     76,070.00-
     /550 Statutory net pay     95343
     /551 Stat.net recalc.diff.     37,692.00-
     /552 Stat.net subs.adjustment      37,692.00-
     /559 Bank transfer                                                   34,317.00
     /560 Net pay     37,218.00
     /563 Claim from previous month     5,609.00
FOR Period
Sept- Oct
     /101 Total gross amount     49,213.00
     /110 Net payments/deductions      31,721.00-
     /550 Statutory net pay     41,529.00
     /551 Stat.net recalc.diff.     14,591.00
     /552 Stat.net subs.adjustment     23,101.00-
     /553 Recalc.diff.to last payr.     37,692.00
     /559 Bank transfer                                                   14,591.00
     /560 Net pay     14,591.00
     /561 Claim     5,609.00
I request some body to throw siome light on the same.

Hi Experts,
Thanks for everyone for replying to my query ,
I have a doubt that If you check the WTs /551 and /552 in the IN PRD, the negative sign is coming for both the WTs
Is it correct?
And also, Assume that there may be a master data changes like Bank details and other deduction Wts happened in the month of Aug and now i m going to run the payroll for the month of Nov,
some of the employees having differences in the Net Pay, Eventhough the employee is having sufficient balances.
So how do i handle this issue
IS ther any way to solve this differences?
Please Let me know how to solve this issue.
Thanks

Problem with /561 /563 Claims

Hi
I have aproblem in Claims. There is a difference between the finance posting Net pay value and Pay slip Net Pay value. In the Payslip deductions side Claims displaying as negative value with this the total deductions got reduced and net pay got increased. Where as in the FI Posting document there is no negative claim amount.
How to correct the Payslip
Request for solution
Thanks & Regards
EKP Yadav

This is how claims will be formed
________PAYROLL________
________Period 1 in 1________
___________Earn________Ded
Bonus______10000________
Tax____________________3000
Net____________________7000
________Period 1 in Period 2________
__________Earn________Ded
Bonus________0________
Tax________________3000
Net________________7000
/561________10000________
________Per 2 in 2________
___________Earn________Ded
Basic______5000________
Tax___________________1500
/563__________________10000
/561_______6500________
________Posting for period 1 in 1________
____________________________Dr________Cr
GL1 - Expense- Bonus________10000________
Gl12- Balance sheet -Tax________________3000
Gl3- Balance sheet or acc -Net________________7000
________Period 1 in Period 2________
________________________________Dr________Cr
GL1 - Expense- Bonus_____________0________
Gl12- Balance sheet -Tax___________________3000
Gl3- Balance sheet or acc -Net______________7000
Gl4- Balance sheet or acc -advance__10000________
________Per 2 in 2________
_____________________________________Dr________Cr
GL1 - Expense- Basic_________________5000________
Gl12- Balance sheet -Tax__________________________1500
Gl4- Balance sheet or acc -advance_________________10000
Gl4- Balance sheet or acc -advance______6500__________
In the next period when the remaining 6500 is recovered, the claims will be cleared in GL. First understand the logic of claims and check your GL posting.Then try to use the standard form to display right amount, understand the payslip.
Then if required correct your payslip.

Claim status report - PC00_M40_REMS

Hi experts
Claims status report PC00_m40_rems is showing incorrect balance. That is, for example, eligibility is Rs. 50000
Step1: Claim for the month for April is Rs.5000. Claim processed through PC00_M40_REMP. The claim status was successfull.
After the above step, REMS report shows Eligibility Rs.50, 000/- Claim payment - 0, claim due - Rs.5000/-, balance Rs.45000/- and no.of claim 1
Step2: Claim was processed through offcycle payroll - PC00_m40_calc. After this process, the REMS report shows - Eligibility Rs.50000/-, claim payment - Rs.5000, claim due - Rs.5000/-, balance Rs.40,000/- and no. of claim 2
Step3: Then regular payroll was run. After the regular payroll, REMS is showing correct details i.e. Eligibility Rs.50,000/- Claim payment Rs.5000/-, Claim due - 0, balance Rs.45,000/- and no. of claim 1
I suppose, the balance should show correct balance of Rs.45,000/- after the second step mentioned above.
I have maintained bank details - Main bank and Main bank for offcycle.
Kindly guide me.
with regards

hi Sikindar,
In that table SMED has been assigned against my customised wagetype & also has been assigned aginst 00M0 wt;But In PC00_m40_REMP report it is showing calculation only against OOMO wt
Thanks
Sur

Payroll retro issue - related to /563

Hi PY experts,
Problem:
I have one PY retro issue.
Issue reported in December is :- One employee has a /563 claim of $18.45 (Claim from prev mth).
Why is here a deduction shown for this payslip?.
Issue reported in Jan 2010 is :- same employee has $99.3 (Claim from prev mth).
My analysis and details are as follows:-
December retro triggered for Oct,Nov.
Jan 10-retro triggered for June 09 onwards.
/561(amt employee owes to employer) in Nov in December run:- 18.45.
/561 in Nov in Jan'10 run:-117.75
So,
/563(claims from previous month) in December in december run:-18.45
/563 in December in Jan'10 run:-117.75
So,
99.30 SGD shown in Jan 2010 is the difference between the figures which was displayed in the last month.Ies (117.75 - 18.45 ) =99.30 .
-But my understanding is /561 will get formulated only in case the /110+/550 is negative.
But in this employee's scenario this amount is not coming as negative.Then how /561 is getting formulated even though( /110+/550 ) is not negative?
There is only difference between different runs of payroll of /101 . here is no difference in /110 amounts for same months in different runs.
So retro triggered thru the payment wage types(Cumilation 01).So I have run the wage type reoprt for comparing these wage types.(I can fwd this to email)
My doubts /help required areas are :-
1) How /561 is getting formulated even though( /110+/550 ) is not negative?
2) I can forward the details in proper excel format(easy to compare kind) -monthly wage type comparison report
which is related to (/101) wise reoprt , pls help me to find out how the exact amount is getting formulated.
Regards
Thomas
Edited by: tomspadiyara on Jan 10, 2010 7:00 AM
Edited by: tomspadiyara on Jan 11, 2010 3:19 AM

Hi,
I got the answers for the questions..
Can anybody pls help me by a document how all the technical wage types are getting formulated: ies
/140
/254 etc etc kind
This will help me for a faster derivation of the figure came in /563

How to process a cross year claim?

Hi everyone -
I have a situation where my client is looking at the possibility of processing claims that cross over from one calendar year to the next. I understand that the MCOR wage type is set up to assist with this but what exactly are the processing steps for continuing a claim across years? Do we clear the claim at the end of the prior year and then set up the custom version of the MCOR wage type to take deductions in the new year? Would we set up the MCOR wage type to act like a balancing wage type? Would we still see a /561 in the RT?
Any instructions on exactly what the process should be would be greatly appreciated. Thank you.

Hi
There can be more than one approach for this.But i will tell you how we handles in for UK payroll
Aproach 1:
Replicate the employee in your test system figure out how much should be employees taxes, social security , other deductions and net pay to arrive at exact amount employee owes .
Process employee in current year and deduct so much of the monies from the pay. Better to use deduction wagetypes just so you do not fall in to the minimum pay conditions etc
Now main thing would be to adjust employee for end of year : Based on employees results you have to adjust end of year results(here i am assuming that you will have these wagetypes)
From FI postings point of view you may have to make few manual postings for the adjustment.
Hope this helps
Regards
Ajay

PY Issue -/563 is not deducting from Earnings

Hi Payroll experts,
My assumption is
Net pay = total earning (Current month Payments)- total deductions (Current month deductions)
But this month I have a /563 (claim from previous monthu2019s) in the deduction section of the pay slip. It is getting added up to the total deductions also.
Total earning (Current month Payments) = 1958.07
Total deductions (Current month deductions) = 578.45 (Including amount from/563 as 99.3)
Net pay should be 1958.07 - 578.45 = 1379.62
But pay slip the Net pay is displayed as 1478.92 (it didnu2019t deduct the /563 amount - 99.3 from earnings.)
Why system is behaving like this? is it a standard way?
Then where this /563 amounts will get deducted from employee on actual?
How to make /563 also to be deducted from earnings?
Regards
Thomas

Please check if the /563 is added in the deductions side of ur payslip,
                      -->Yes it is getting added up with the Total deductions (Current month deductions)
About RT
/559     Bank transfer     1,478.92
/560     Amount paid     1,478.92
Pay slip also the Net pay is displayed same as in RT as 1478.92 (it didnu2019t deduct the { /563 amount - 99.3 ) from earnings.)
Total earning (Current month Payments) = 1958.07
Total deductions (Current month deductions) = 578.45 (Including amount from/563 as 99.3)
Net pay should be 1958.07 - 578.45 = 1379.62

Claim Carry forward

Dear All,
Im looking for following functionality,
PC00_M40_REMP - Claims Disbursement if Employees has already apply the claim and its proceed, so system should not be allowed new claim for same period.
PC00_M40_REMC - Claims Balance Carry Forward: if employee has not claim full amount then only carry forward should work, partially balance should not be allowed, and remaining balance will get laps.
So please advice me how will manage this functionally.
Thanks and regards,
YUV

Hi,
the activities for SAP End users are
1.     End of the year-all tax related queries check and see the taxation part is correct by taking random employees across organization(TDS in case of India)
2.     Beginning of the year-see updated rules regarding Statutory compliance are updated by SAP,generate work schedules without fail
3.     Mid year-in case of LWF twice in year check this
4.     Quarter-TDS filing quarterly,and maintaining challans in SAP
5.     Monthly-run payroll every month and check all statutory payments to be made to authorities(PF,PTax,ESI,LWF etc) alongwith postings to FI
apart from this if required create any new wagetypes for Earn/dedn if any
The Payroll support Consultant has to be aware of all these activities and has to know the latest SPK levels of SAP and new notes updated by SAP with relevant changes if any to include those in the system
As SAP is an integrated system,though there is not much integration between HR and other Modules except FI,however one has to see the changes that may affect other modules,hence before and after updating support pack level test thoroughly in DEV and then move to QAS & PRD System.
Salil

Claims

Hi All
can anybody explain about claims and what are /561 and /563. why we use these wage types

Thisis from the documentation..
If the amount for wage type /560 (Net pay) is negative at the end of the
payroll run, a claim is made against the employee. This may, for
example, be the case if the employee was accidentally paid more than
twice his salary in the previous month. It is not possible to clear the
difference in the current payroll period by deducting it from his
salary. In this case, the amount for wage type /560 (Net pay) is marked
as negative and the +/- sign is reversed in wage type /561 (Claim) in
the payroll results.
In the following payroll period, the amount for wage type /561 (Claim)
is read from the old payroll results, transferred to wage type /563
(Claim from previous month) and deducted from the current amounts for
wage types /560 (Net pay) and /562 (Remaining net pay).
Wage type /561 (Claim) represents an offsetting entry for expenses which
are posted to credits. It is always preceded by a plus sign and is
always posted to debits. In the same way, wage type /563 (Claim from
previous month), which always has a minus sign, is posted to credits.

Issue with SharePoint foundation 2010 to use Claims Based Auth with Certificate authentication method with ADFS 2.0

I would love some help with this issue. I have configured my SharePoint foundation 2010 site to use Claims Based Auth with Certificate authentication method with ADFS 2.0 I have a test account set up with lab.acme.com to use the ACS.
When I log into my site using Windows Auth, everything is great. However when I log in and select my ACS token issuer, I get sent, to the logon page of the ADFS, after selected the ADFS method. My browser prompt me which Certificate identity I want
to use to log in and after 3-5 second
and return me the logon page with error message “Authentication failed”
I base my setup on the technet article
http://blogs.technet.com/b/speschka/archive/2010/07/30/configuring-sharepoint-2010-and-adfs-v2-end-to-end.aspx
I validated than all my certificate are valid and able to retrieve the crl
I got in eventlog id 300
The Federation Service failed to issue a token as a result of an error during processing of the WS-Trust request.
Request type: http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue
Additional Data
Exception details:
Microsoft.IdentityModel.SecurityTokenService.FailedAuthenticationException: MSIS3019: Authentication failed. ---> System.IdentityModel.Tokens.SecurityTokenValidationException:
ID4070: The X.509 certificate 'CN=Me, OU=People, O=Acme., C=COM' chain building failed. The certificate that was used has a trust chain that cannot be verified. Replace the certificate or change the certificateValidationMode. 'A certification chain processed
correctly, but one of the CA certificates is not trusted by the policy provider.
at Microsoft.IdentityModel.X509CertificateChain.Build(X509Certificate2 certificate)
at Microsoft.IdentityModel.Tokens.X509NTAuthChainTrustValidator.Validate(X509Certificate2 certificate)
at Microsoft.IdentityModel.Tokens.X509SecurityTokenHandler.ValidateToken(SecurityToken token)
at Microsoft.IdentityModel.Tokens.SecurityTokenElement.GetSubject()
at Microsoft.IdentityServer.Service.SecurityTokenService.MSISSecurityTokenService.GetOnBehalfOfPrincipal(RequestSecurityToken request, IClaimsPrincipal callerPrincipal)
--- End of inner exception stack trace ---
at Microsoft.IdentityServer.Service.SecurityTokenService.MSISSecurityTokenService.GetOnBehalfOfPrincipal(RequestSecurityToken request, IClaimsPrincipal callerPrincipal)
at Microsoft.IdentityServer.Service.SecurityTokenService.MSISSecurityTokenService.BeginGetScope(IClaimsPrincipal principal, RequestSecurityToken request, AsyncCallback callback, Object state)
at Microsoft.IdentityModel.SecurityTokenService.SecurityTokenService.BeginIssue(IClaimsPrincipal principal, RequestSecurityToken request, AsyncCallback callback, Object state)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceContract.DispatchRequestAsyncResult..ctor(DispatchContext dispatchContext, AsyncCallback asyncCallback, Object asyncState)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceContract.BeginDispatchRequest(DispatchContext dispatchContext, AsyncCallback asyncCallback, Object asyncState)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceContract.ProcessCoreAsyncResult..ctor(WSTrustServiceContract contract, DispatchContext dispatchContext, MessageVersion messageVersion, WSTrustResponseSerializer responseSerializer, WSTrustSerializationContext
serializationContext, AsyncCallback asyncCallback, Object asyncState)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceContract.BeginProcessCore(Message requestMessage, WSTrustRequestSerializer requestSerializer, WSTrustResponseSerializer responseSerializer, String requestAction, String responseAction, String
trustNamespace, AsyncCallback callback, Object state)
System.IdentityModel.Tokens.SecurityTokenValidationException: ID4070: The X.509 certificate 'CN=Me, OU=People, O=acme., C=com' chain building
failed. The certificate that was used has a trust chain that cannot be verified. Replace the certificate or change the certificateValidationMode. 'A certification chain processed correctly, but one of the CA certificates is not trusted by the policy provider.
at Microsoft.IdentityModel.X509CertificateChain.Build(X509Certificate2 certificate)
at Microsoft.IdentityModel.Tokens.X509NTAuthChainTrustValidator.Validate(X509Certificate2 certificate)
at Microsoft.IdentityModel.Tokens.X509SecurityTokenHandler.ValidateToken(SecurityToken token)
at Microsoft.IdentityModel.Tokens.SecurityTokenElement.GetSubject()
at Microsoft.IdentityServer.Service.SecurityTokenService.MSISSecurityTokenService.GetOnBehalfOfPrincipal(RequestSecurityToken request, IClaimsPrincipal callerPrincipal)
thx
Stef71

This is perfectly correct on my case I was not adding the root properly you must add the CA and the ADFS as well, which is twice you can see below my results.
on my case was :
PS C:\Users\administrator.domain> $root = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2("C:\
cer\SP2K10\ad0001.cer")
PS C:\Users\administrator.domain> New-SPTrustedRootAuthority -Name "domain.ad0001" -Certificate $root
Certificate : [Subject]
CN=domain.AD0001CA, DC=domain, DC=com
[Issuer]
CN=domain.AD0001CA, DC=portal, DC=com
[Serial Number]
blablabla
[Not Before]
22/07/2014 11:32:05
[Not After]
22/07/2024 11:42:00
[Thumbprint]
blablabla
Name : domain.ad0001
TypeName : Microsoft.SharePoint.Administration.SPTrustedRootAuthority
DisplayName : domain.ad0001
Id : blablabla
Status : Online
Parent : SPTrustedRootAuthorityManager
Version : 17164
Properties : {}
Farm : SPFarm Name=SharePoint_Config
UpgradedPersistedProperties : {}
PS C:\Users\administrator.domain> $cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2("C:\
cer\SP2K10\ADFS_Signing.cer")
PS C:\Users\administrator.domain> New-SPTrustedRootAuthority -Name "Token Signing Cert" -Certificate $cert
Certificate : [Subject]
CN=ADFS Signing - adfs.domain
[Issuer]
CN=ADFS Signing - adfs.domain
[Serial Number]
blablabla
[Not Before]
23/07/2014 07:14:03
[Not After]
23/07/2015 07:14:03
[Thumbprint]
blablabla
Name : Token Signing Cert
TypeName : Microsoft.SharePoint.Administration.SPTrustedRootAuthority
DisplayName : Token Signing Cert
Id : blablabla
Status : Online
Parent : SPTrustedRootAuthorityManager
Version : 17184
Properties : {}
Farm : SPFarm Name=SharePoint_Config
UpgradedPersistedProperties : {}
PS C:\Users\administrator.PORTAL>

Internal server error while raising a claim request.

Dear All,
I am using claims and we have implemented badi for finding the approver and sending the request.
Here after implementing the Badi, i am getting internal server error as this.
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error in module RSQL of the database interface., error key: RFC_ERROR_SYSTEM_FAILURE
    at java.lang.Throwable.<init>(Throwable.java:179)
    at java.lang.Error.<init>(Error.java:37)
    at com.sap.pcuigp.xssfpm.java.FPMRuntimeException.<init>(FPMRuntimeException.java:46)
    at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:103)
    at com.sap.ess.in.claims.fc.FcPowerClaims.callRFC_Emp_Action(FcPowerClaims.java:421)
    ... 53 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; GTB5; QS 4.2.2.3; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648)
Version null
DOM version null
Client Type msie7
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0017.20080829103545.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:14:54[UTC], changelist=499141, host=pwdfm101), build date: Fri Mar 13 11:09:42 IST 2009
J2EE Engine 7.00 patchlevel 112614.44
Java VM Classic VM, version:1.4, vendor: IBM Corporation
Operating system OS/400, version: V6R1M0, architecture: PowerPC
Session & Other
Session Locale en_US
Time of Failure Thu Apr 23 18:47:54 IST 2009 (Java Time: 1240492674705)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0017.20061002105236.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:01:31[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0017.20061002105236.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:01:37[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0017.20060719095755.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:48:53[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0017.20080801093115.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:07:06[UTC], changelist=495367, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0017.20061002105432.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:49:40[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0017.20061002105432.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:49:34[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0017.20060719095619.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:58:48[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0017.20080801093120.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:03:59[UTC], changelist=495368, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0017.20080829103545.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:16:41[UTC], changelist=499141, host=pwdfm101)
SapWebDynproGenerationCore 7.0017.20080801093115.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:07:12[UTC], changelist=495367, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0017.20080829103545.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:16:41[UTC], changelist=499141, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/pb_api
SapDictionaryGenerationCore 7.0017.20061002105236.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:01:31[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0017.20061002105236.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:01:37[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0017.20060719095755.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:48:53[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0017.20080801093115.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:07:06[UTC], changelist=495367, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0017.20061002105432.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:49:40[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0017.20061002105432.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:49:34[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0017.20060719095619.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:58:48[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0017.20080801093120.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:03:59[UTC], changelist=495368, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0017.20080829103545.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:16:41[UTC], changelist=499141, host=pwdfm101)
SapWebDynproGenerationCore 7.0017.20080801093115.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:07:12[UTC], changelist=495367, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0017.20080829103545.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:16:41[UTC], changelist=499141, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error in module RSQL of the database interface., error key: RFC_ERROR_SYSTEM_FAILURE
     at java.lang.Throwable.<init>(Throwable.java:179)
     at java.lang.Exception.<init>(Exception.java:29)
     at com.sap.exception.BaseException.<init>(BaseException.java:145)
     at com.sap.tc.cmi.exception.CMIException.<init>(CMIException.java:65)
     at com.sap.tc.webdynpro.progmodel.model.api.WDModelException.<init>(WDModelException.java:68)
     at com.sap.tc.webdynpro.modelimpl.rfcadapter.WDRFCException.<init>(WDRFCException.java:54)
     at com.sap.tc.webdynpro.modelimpl.rfcadapter.WDExecuteRFCException.<init>(WDExecuteRFCException.java:57)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException.<init>(WDDynamicRFCExecuteException.java:71)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException.<init>(WDDynamicRFCExecuteException.java:43)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
     at com.sap.ess.in.claims.fc.FcPowerClaims.callRFC_Emp_Action(FcPowerClaims.java:392)
     at com.sap.ess.in.claims.fc.FcPowerClaims.performEmpAction(FcPowerClaims.java:1988)
     at com.sap.ess.in.claims.fc.wdp.InternalFcPowerClaims.performEmpAction(InternalFcPowerClaims.java:8022)
     at com.sap.ess.in.claims.fc.FcPowerClaimsInterface.performEmpOperation(FcPowerClaimsInterface.java:398)
     at com.sap.ess.in.claims.fc.wdp.InternalFcPowerClaimsInterface.performEmpOperation(InternalFcPowerClaimsInterface.java:3440)
     at com.sap.ess.in.claims.fc.wdp.InternalFcPowerClaimsInterface$External.performEmpOperation(InternalFcPowerClaimsInterface.java:3616)
     at com.sap.ess.in.claims.vc.powerrequestdetail.VcPowerRequestDetail.aH_Send(VcPowerRequestDetail.java:739)
     at com.sap.ess.in.claims.vc.powerrequestdetail.wdp.InternalVcPowerRequestDetail.aH_Send(InternalVcPowerRequestDetail.java:2947)
     at com.sap.ess.in.claims.vc.powerrequestdetail.VcPowerRequestDetailView.onActionSend(VcPowerRequestDetailView.java:1423)
     at com.sap.ess.in.claims.vc.powerrequestdetail.wdp.InternalVcPowerRequestDetailView.wdInvokeEventHandler(InternalVcPowerRequestDetailView.java:1650)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
     at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1299)
     at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:326)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:868)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:101)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Error in module RSQL of the database interface., error key: RFC_ERROR_SYSTEM_FAILURE
     at java.lang.Throwable.<init>(Throwable.java:179)
     at java.lang.Exception.<init>(Exception.java:29)
     at com.sap.aii.util.misc.api.BaseException.<init>(BaseException.java:96)
     at com.sap.aii.proxy.framework.core.FaultException.<init>(FaultException.java:34)
     at com.sap.aii.proxy.framework.core.SystemFaultException.<init>(SystemFaultException.java:29)
     at com.sap.aii.proxy.framework.core.BaseProxyException.<init>(BaseProxyException.java:39)
     at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
     at com.sap.ess.in.claims.newmodel.HRXSS_IN_NEWCLMS_MODEL.hrxss_In_Cl_Emp_Action(HRXSS_IN_NEWCLMS_MODEL.java:475)
     at com.sap.ess.in.claims.newmodel.Hrxss_In_Cl_Emp_Action_Input.doExecute(Hrxss_In_Cl_Emp_Action_Input.java:137)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
     ... 54 more
Appreciate any quicker help on this.
Regards,
Rajasekar

Hi,
Can u give me full details ....
What is the name of the BADI and ....coding tht you have written in method.
Cheers
Vivek

Firefox prompted me to download an incompatible update that its website claims is compatible with my operating system (Mac OS 10.4.11). Why prompt an incompatible download AND claim it is compatible?

I have an iMac and use OS 10.4.11 & Firefox 3.6.19. Firefox prompted me to download an update (to 7.0.1). I looked up the system requirements on your website, and it stated the update is compatible with OS 10.4.11. But after I downloaded and installed the update, it failed to work on grounds of incompatibility. Hence 2 questions: (1) Why did Firefox prompt me to download an incompatible update? (2) Why did your website claim the update is compatible with my operating system when it is not?

Sorry, it's because Firefox 4+ are only compiled for the Intel processors.
There is a separate project for PPC Macs called Ten Four Fox. You might give it a spin when you're tired of 3.6.
http://www.floodgap.com/software/tenfourfox/

Can not get access files from Windows 7 to Claims-based file authorization share

We have AD level 2012R2, DCs running 2012R2 of course, and we have clustered File Server (3 FSNodes running 2012R2).
We enabled 2 policies
KDC Support for claim
Kerberos support for claim
We created 1 claim type in ADAC (For example "Division" Source Property). Filled this property to all IT AD Accounts by our value "IT"
On FS made a share folder ITDivision:
- set permissions Domain Users can Modify if User.Division equals "IT"
so on Windows 8 IT Users can access files on this share and on Windows 7 they cant
=\ . We know from many presentations about Dynamic Access Control that File Server must enroll user claims if client do not support this claims (Service-for-User-To-Self)

Hi,
>>so on Windows 8 IT Users can access files on this share and on Windows 7 they cant
=\ . We know from many presentations about Dynamic Access Control that File Server must enroll user claims if client do not support this claims (Service-for-User-To-Self)
How is it going? Was there any error message? As far as I know, Dynamic Access Control (DAC) should work for downlevel clients. It’s backwards compatible. As Florain explains in the following blog:
For non-Windows 8 and non-Windows Server 2012 boxes accessing DAC-protected file shares, the users do not carry any claims. For them, the Server 2012-based file share will query Active Directory and proxy the claims request to figure out what claims
the user and machine bring. The file server checks in the name of the user, whether they should have claims. With that information, the file server evaluates the access to the file share. So yeah – DAC works for downlevel clients, too. It’s backwards compatible.
And totally transparent to Windows 7.
Questions regarding Dynamic Access Control (FAQ)
http://www.frickelsoft.net/blog/?p=293
In addition, regarding dynamic access control, the following blog can also be referred to for more information.
Dynamic Access Control in Windows Server 2012
http://www.infoq.com/news/2012/10/Dynamic-Access-Control
Please Note: Since the above two website are not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Best regards,
Frank Shen

Erro de Inutilização 563

Bom dia!
Estou com uma situação similar à dessa thread: http://forums.sdn.sap.com/thread.jspa?threadID=1893297
Tenho uma nota cuja inutilização foi rejeitada com erro "563:Já existe pedido de Inutilização com a mesma faixa de inutilização" da SEFAZ do Ceará e não foi marcada flag de estorno no ECC.
Entretanto, ao acessar o Web Monitor do GRC, logo abaixo do código de rejeição há o botão
Finalizar "Ignorar"
Minhas dúvidas são:
1) Esse botão Finalizar "Ignorar", ele vai finalizar o estorno da nota no ECC, é a tal opção standard que não havia antes?
2) Caso não solucione, como deveria proceder, levando em conta que é uma nota em ambiente produtivo? Abrir chamado mesmo?

Tiago, vc pode consultar a nota no SEFAZ com o CNPJ do emitente.
Vc deve ir em consultar inutilização , e procurar o numero da nota , e depois vc entrar com o numero log data e hora que foi homologado a inutilização.
Nesse caso o ECC ainda esta aguardando a resposta do GRC para continuar o processo no ECC, a nota deve estar com 2 3 C no status.
Abraços

Claims wagetype /563

Similar Messages

Maybe you are looking for