Error in Loan

A Loan is entered for the employee. While running payroll following error received.
Error with a loan wage type
A loan wage type in table RT should be deducted,
however the remaining net amount was too small
Wage type 9SLD
Please lower the loan repayment in infotype 0045
Choose an amount that can be deducted
Data:
Approved date: 01.03.2010
Loan Amount granted: 20,000.00
End of loan date: 30.06.2010
Loan conditions: Interest free
Rpymnt instl. 5000.00

I got the same error, I tried but can't fix.
When I ran payroll , I got this error:
Error with a loan wage type
A loan wage type in table RT should be deducted, however the
however the remaining net amount was too small
Wage type /LRP
Please lower the loan repayment in infotype 0045
Choose an amount that can be deducted
image:
http://cB6.upanh.com/22.178.29172705.1ac0/0605201124003ch.png
earning total of month is 17000 and total deduction is 4700, carry forward from last month = 0
I checked table V_T51P6 and set priority of WT /LRP to highest (A) but still get the error.
please help me.
Regards.
Virus

Similar Messages

ERROR in Loan Application

Dear All,
I am getting an error while applying for a loan in ESS
Error - "A Maximum of amount 0 can be approved for the employee no .XXXXXXXX " .
I read the earlier thread on this but it does not work even after activating the BADI.
I have activated the BADI for Loan eligibility....still the same error is coming.
Actually, I have set break point but that BADI is not getting hit when applying from portal.
Details of the BADI activated :
Enhancement SPOT --- HRPBSINLOANS
Method --- ELIG_RESULT
Please correct me if I am doing something wrong ,also suggest me any way out.
Regards,
Geet

Dear Barin / Siddhartha / Vivek,
Kind give your inputs on this issue as the error is still coming even after the activation of BADI.
Regards,
Geet

Error in Loan Configuration

Hi Friends,
I have done Loan confg for the first time , now i was trying to create a loan for the Employee, I have entered all the three tabs Basic data,conditions, when i entered payemnts . i get a error message saying
" The Employee is not elgible for the Loan 1070 on 01.05.2008".
Can you tell me what is the problem with the confgn.
Points will be rewarded.
With rgds,
Kumara

Hi
Which country payroll r u working on?
VV_T591A_4_VC506 check this table also..
check that loan grouping in T506c and maitain loan grpng for each loan type and assign that in feature 40LGR for Payscale groups or personnel number.try like this by assigning it to the personnel number..go to the path GO TO> structure> u select personnel number field.
And also maitain feature 40LSL ---> gove that loan grpng which is given the table T506c and assign wagetype like Basic , which belongs to that employee.
Thanks
Nanditha.

Error in Loan interest_SAP HCM_Payroll India

Hi All,
I have configured Loan process (Infotype 45) and followed all the process everything is working fine, now the problem is while end user is giving 0 % interest calculation on loan amount system is calculating it as 2% interest, why system is calculating this 2% ?
please do needful.
Regards,
Prasad

Hi Prasad,
Check the link, it will help you.
Error while configuring LOANs-SAP HCM Indian PT
Regards,
Naresh.KM

Error in loan processing

Experts,
Getting the error while processing a loan type
Error during cumulation No entry found in the table T512W Key 40 1LOP 20090430
I could not find the table,Please let us know

try like this
say u r haveing two loan types
1 Houseing Loan
2. Personal Loan
for IT0045 create two sub types 9001 for Houseing Loan 9002 for Personal Loan
u can chec the same in the Configuration
now
for Houseing Loan copy two wage types
9021 from /Lop Loan payment
9022 form /LRP loan Repayment
do same for Personal Loan
now go to XLOZ rule in PE02
Copy it as ZLON
under the node /LOP that is loan payment
make
add L9001 this is ur subtype for Houseing loan
under that ADDWTE9021 as this is ur wage type for Loan Payment
the same logic applicable for /LRP here u have to keep 9022

Error while maintaing a loan type for an employee

Hi gurus
This is in regard to the Loan while maintaing for an employee through PA30
" Employee 002 is not eligible for the loan 7501 on 01.10.2008" though i tried to Maintain it for different dates still iam not able to maintain.
Even i tried maintaing different loan type for the same employee its still pops with the same error message
Even i cross chked the dates of the configuration every config start date from 1990/1995
where as 7501 and 7401 are my loan types
Pls advise
Rgds
M Bharath

I have the same issue.
How you solved it?

Error while accessing ESS Loan Request.

Hi Experts,
While accessing ESS Loan request for Country grouping 40 India am getting below mentioned error saying that 500 Internal Server Error.
I have maintained the settings for Leave request and maintained Infotype 45 Loans for employee.
But it is giving the below mentioned error.
500   Internal Server Error
SAP NetWeaver Application Server 7.00/Java AS 7.00
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
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.dictionary.runtime.DdException: Type com.sap.model.loan.types.Extdl does not exist
    at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
    at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:596)
    at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:296)
    at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:94)
    at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
    ... 74 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2)
Version null
DOM version null
Client Type msie8
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.0205.20100813133935.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:28:44[UTC], changelist=91834, host=pwdfm256), build date: Fri Feb 11 16:31:03 IST 2011
J2EE Engine 7.02 PatchLevel 91789.
Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_28-b03, vendor: Sun Microsystems Inc.
Operating system Windows Server 2008 R2, version: 6.1, architecture: amd64
Session & Other
Session Locale en_US
Time of Failure Fri Feb 18 11:17:24 IST 2011 (Java Time: 1298008044828)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0205.20100813133727.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:18:36[UTC], changelist=91776, host=PWDFM256.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0205.20100813133727.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:18:40[UTC], changelist=91776, host=PWDFM256.wdf.sap.corp)
SapGenerationFrameworkCore 7.0205.20100813133737.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:08:53[UTC], changelist=91781, host=PWDFM256.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0205.20100813133926.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:22:53[UTC], changelist=91832, host=PWDFM256.wdf.sap.corp)
SapMetamodelCommon 7.0205.20100813133815.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:09:28[UTC], changelist=91800, host=PWDFM256.wdf.sap.corp)
SapMetamodelCore 7.0205.20100813133815.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:09:25[UTC], changelist=91800, host=PWDFM256.wdf.sap.corp)
SapMetamodelDictionary 7.0205.20100813133729.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:16:20[UTC], changelist=91777, host=PWDFM256.wdf.sap.corp)
SapMetamodelWebDynpro 7.0205.20100813133929.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:20:37[UTC], changelist=91833, host=PWDFM256.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0205.20100813133935.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:30:09[UTC], changelist=91834, host=pwdfm256)
SapWebDynproGenerationCore 7.0205.20100813133926.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:22:57[UTC], changelist=91832, host=PWDFM256.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0205.20100813133935.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:30:09[UTC], changelist=91834, host=pwdfm256)
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.sap.model.loan.types.Extdl could not be loaded: com.sap.dictionary.runtime.DdException: Type com.sap.model.loan.types.Extdl does not exist
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:268)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:231)
     at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
     at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
     at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:940)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:141)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createBLCComponentUsage(FPMComponent.java:761)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
     at com.sap.ess.in.loan.overview.VcOverviewESS.onInit(VcOverviewESS.java:244)
     at com.sap.ess.in.loan.overview.wdp.InternalVcOverviewESS.onInit(InternalVcOverviewESS.java:611)
     at com.sap.ess.in.loan.overview.VcOverviewESSInterface.onInit(VcOverviewESSInterface.java:162)
     at com.sap.ess.in.loan.overview.wdp.InternalVcOverviewESSInterface.onInit(InternalVcOverviewESSInterface.java:144)
     at com.sap.ess.in.loan.overview.wdp.InternalVcOverviewESSInterface$External.onInit(InternalVcOverviewESSInterface.java:220)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     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:876)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:222)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1355)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:357)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:597)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:870)
     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:333)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     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 java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.dictionary.runtime.DdException: Type com.sap.model.loan.types.Extdl does not exist
     at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
     at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:596)
     at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:296)
     at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:94)
     at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
     at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:260)
     ... 72 more
Please suggest me the solution for this.
Regards,
Ksanj.

Please   check that the ESS/ERP packages fit together according to
the page
https://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACK+
MISMATCH+ISSUES
Please check again the componentinfo and the SPlevels of the testlandsca
pe, that the same level is used on the prod landscape.
So ensure you are on correct levels!

Error while configuring LOANs-SAP HCM Indian PT

Dear Consultants,
As per my client requirement I have created a Loan type it is coming in the Infotype 45 and subtype. but when I want to create a Loan in the CONDITIONS tab Loan Condition says nothing to select, Please let me know what is the tcode to create new leave conditions.
Regards,
Naresh

Dear Consultants,
Thanks for your quick reply and valuable help, My issue solved after checking the step by step configuration which referred by Mr. Narendra Chitragar .
I have maintained following steps, and able to clear my issue.
1. Check Table/view V_T7INJ1 for Section 24 deduction details,
2. Table/view V_T7INJ3 for the Loans eligibility check and limits.
3. Table/view V_T7INJ5 for the disbursement schedule.
4. Table/view V_T7INJ6 for the event codes of Loan grouping.
5. Configure feature ALOAN, which will return the grouping.
6. Table/view T506C which will give the loan condition values.
7. Table/view V_T506D
8. Table/view V_T506S,
9. The constants LMNL1, LMNL2 and LONPI should be maintained in the table V_T511k.
10. The constant LMVAL should be maintained in the table V_T511P.
Also check for below points
1. Check that the feature 40LGR is configured for India,
2. Check that the feature 40LSL is configured which will return the Salary components
Link : Loan - Error "Employee not eligible for Loan".
Thanks & Regards,
Naresh.KM

Loans document error Document header does not have a reconciliation key

Hi All,
I am trying to post a loans document through EK25 and while saving the document following erros is coming
Formal error: Document header does not have a reconciliation key
Message no. >0037
Diagnosis
You tried to post a document but a reconciliation key is missing from the document header. Since mass processing does not apply here (where the reconciliation key is automatically created) you must enter a reconciliation key.
System Response
Error message. Processing is terminated.
Procedure
Contact your system administrator.
Procedure for System Administration
If the program error occurred in an
SAP standard program, enter a problem message
Own program, correct the program
Any input appreciated.
Thanks,
VR

Hi,
You need to assign the reconcilation group to the SAP user ID you are using to post the loan document.
The reconciliation group is required if user-specific reconciliation keys are to be proposed automatically.
The reconciliation group is freely selectable.
Go to the following path in IMG-
IMG->Financial Accounting->Contract Accounts Receivable and Payable->Basic Functions->Postings and Documents->Document-.Define Default Values->Maintain Rules for Reconciliation Key Default Values->Maintain Reconciliation Groups for Default Values
Maintain the SAP User ID that you are using along with a reconciliation group.
After, you maintained the user ID and saved it, try to post the loan document again.
Hope it helps..
Thanks,
Amlan

I am trying to return finished books to the library and it comes up with an error message e-bad loan

I am trying to return finished books to the library it comes up with a message e-bad loan id

(1) Download the Windows Installer CleanUp utility installer file (msicuu2.exe) from the following Major Geeks page (use one of the links under the "DOWNLOAD LOCATIONS" thingy on the Major Geeks page):
http://majorgeeks.com/download.php?det=4459
(2) Doubleclick the msicuu2.exe file and follow the prompts to install the Windows Installer CleanUp utility. (If you're on a Windows Vista or Windows 7 system and you get a Code 800A0046 error message when doubleclicking the msicuu2.exe file, try instead right-clicking on the msicuu2.exe file and selecting "Run as administrator".)
(3) In your Start menu click All Programs and then click Windows Install Clean Up. The Windows Installer CleanUp utility window appears, listing software that is currently installed on your computer.
(4) In the list of programs that appears in CleanUp, select any iTunes entries and click "Remove", as per the following screenshot:
(5) Quit out of CleanUp, restart the PC and try another iTunes install. Does it go through properly this time?

Loan request - ESS - Error on eligiblity

Hi
Loans are configured in R/3 and working fine .... I configured the same for ESS ( Benefits and Payments - > Loan Requests ) when i try to raise a request for a loan type in ESS , i get en error saying " The Experience of employee 00000022 is less than eligibile experience for loan" , even though i have given "null (0) " in the node - Maintain loans Eligiblity checks and limits ... have any of you come across something like this..... inputs on how to solve this would be highly appreciated.....
Cheers
Sang

Hi Sai Sree
Thanks for the reply
Even with the BADI activated, i get the same error in ESS..
In the ESS - Loan Request screen, the "Reference No." field is grayed out with '000000000000" , though i have given the number range in SPRO for the same...
Can you please let me know whether you get the reference number field correctly filled??
Thanks in advance
Cheers
Sangeetha

Loan - Years of Expereince - Eligiblity error

Hi
Loans are configured in R/3 and working fine .... I configured the same for ESS ( Benefits and Payments - > Loan Requests ) when i try to raise a request for a loan type in ESS , i get en error saying " The Experience of employee 00000022 is less than eligibile experience for loan" , even though i have given "null (0) " in the node - Maintain loans Eligiblity checks and limits ... any idea why i get this error ? .... Thanks in Advance

Hi Sai Sree
Thanks for the reply
Even with the BADI activated, i get the same error in ESS..
In the ESS - Loan Request screen, the "Reference No." field is grayed out with '000000000000" , though i have given the number range in SPRO for the same...
Can you please let me know whether you get the reference number field correctly filled??
Thanks in advance
Cheers
Sangeetha

Error when trying to post interest using FNM1 in Loan Module

Hi,
I am getting error "50 E INTEREST EXP or ZBA CONTRA ACCT cannot be replaced' when positng the interest payment for loan in loan module. The system has posted a planned record and i see it in the cash flow however when posting the planned record it is giving the above error.
Your inputs are greatly appreciated.

check loan posting scheme here:
Spro - SAP Banking - Loans management - Functions - Accounting - Define account determination
Check posting category against debit/credit posting codes and linked GL accounts for your account symbols or post here what you have defined and I couldl see what the problem is

Loan Error : Tax code .. does not exist for jurisdiction code

Dear experts,
Please help me for below issue.
I have created a loan (using FN1V) in loan management. in this loan i have maintained and interest condition. in this interest condition i have maintained tax code - IV. After that when i try to post an interest entry using t.code - FN8D, It is showing me an error as below.
Tax code IV does not exist for jurisdiction code
    Message no. FF718
Diagnosis
    You have entered tax codes and jurisdiction codes in the G/L account
    items. The amounts of these items are used as the tax base to check the
    tax amounts you have entered or to determine the taxes. The system has
    now determined that one or more of the "tax code / jurisdiction code"
    combinations do not exist in Customizing.
System Response
    Calculation of the taxes or checking of the taxes entered had to be
    terminated.Procedure
    Check the tax codes and the jurisdiction codes in the G/L account items
    or asset items. If these are correct, inform your system administrator.
Procedure for System Administration
    Change the tax jurisdictions you specified in Customizing under
    Financial Accounting -> Financial Accounting Global settings -> Tax on
    Sales/Purchases -> Basic Settings -> Define Tax Jurisdictions.
    To do this, choose Maintain entries (F5).
Please help
Regards
Gaurav Gupta

HI Gaurav,
so what do you have in Customizing under Financial Accounting -> Financial Accounting Global settings -> Tax on Sales/Purchases -> Basic Settings -> Define Tax Jurisdictions ?
BR, Tomislav

Error while applaying loan in ESS

Dear All,
I am getting an error while applying for a loan in ESS
Error - "A Maximum of amount 0 can be approved for the employee no .XXXXXXXX " .
I read the earlier thread on this but it does not work even after activating the BADI.
I have activated the BADI for Loan eligibility....still the same error is coming.
Actually, I have set break point but that BADI is not getting hit when applying from portal.
Details of the BADI's activated :
Enhancement SPOT --- HRPBSINLOANS
Method --- ELIG_RESULT
Enhancement SPOT --- HRPBSINLOANS
Method --- ADD_CUST_CHECKS
Please correct me if I am doing something wrong ,also suggest me any way out.
Regards,
Vamshidhar Naini

i placed below code in two BADI's.
DATA: fs_result TYPE pin_chk_result.
fs_result-check_type = 'E'.
fs_result-check_result = 'X'.
APPEND fs_result TO elig_chk_tab_alter.
clear fs_result.
fs_result-check_type = 'M'.
fs_result-check_result = 'X'.
APPEND fs_result TO elig_chk_tab_alter.
*& But i can find the problem in standard code where the error message is coming.
LOAN type is attached to a wage code which is directly evaluated wage code in infotype 8.
in method CHECK_MAX_LOAN_LIMIT of class CL_HRPA_INFTY_0045_IN ..
LOOP AT lsal_tab INTO wa_lsal_tab .
    LOOP AT cur_table INTO wa_cur_table WHERE paywt = wa_lsal_tab
   AND NOT inind = 'I' .
      IF sy-subrc = 0.
        leligi1 = leligi1 + lbetrg.
      ENDIF.
    ENDLOOP.
ENDLOOP.                                                 " lsal_tab
in above code variable LELIGI1 is adding to LBETRG insted of WA_CUR_TABLE-AMOUNT.
Can you please check
Regards,
Vamshidhar Naini.
Regards,
Vamshihdar

Error in Loan

Similar Messages

Maybe you are looking for