× Discuss about OFS, Temenos Connectors, Various OFS modes, OFS with Versions, OFS performance, Logging, EB.PHANTOM, OFS.SOURCE etc…

Schedule generation on LD Contract using OFS

  • hamisi
  • Topic Author
  • Visitor
  • Visitor
13 years 9 months ago #6339 by hamisi
Hello all,

I have managed to create the LD contracts using OFS. However, the interest part of it is not calculated correctly. Instead, the system puts interest as 0 and shows 0 in the interest column of the LD schedule.

What is it that I am not doing correctly? Below is my OFS string:

LD.LOANS.AND.DEPOSITS,ACB.FLAT.LOANS/I/PROCESS,LMSEKENA/123456/TZ0010002,,AMOUNT=1000000.00,DRAWDOWN.ISSUE.PRC=1000000.00,AMOUNT.APPROVED:2=1000000.00,CUSTOMER.ID=734585,CATEGORY=21059,BUS.DAY.DEFN=TZ,CURRENCY=TZS,AGREEMENT.DATE=20110104,AMOUNT.APPROVED=1000000.00,LOAN.PURPOSE=12,LOAN.PURPOSE=12,VALUE.DATE=20110104,FIN.MAT.DATE=20140124,MIS.ACCT.OFFICER=1546,LD.SECTOR=1750,SOURCE.FUNDS=7,INTEREST.FREQ=M,INT.RATE=16.25,INT.START.DT=20110124,DRAWDOWN.ACCOUNT=TZS1485200010101,PRIN.LIQ.ACCT=10100570942,INT.LIQ.ACCT=10100570942,CHRG.LIQ.ACCT=10100570942,CO.CODE:1=TZ0010006



And here is the response, as you can see it puts interest at 0.
LD1100400186//1,CUSTOMER.ID=734585:1:1,CURRENCY=TZS:1:1,CURRENCY.MARKET=1:1:1,AMOUNT=1000000.00:1:1,BUS.DAY.DEFN=TZ:1:1,VALUE.DATE=20110104:1:1,FIN.MAT.DATE=20140124:1:1,LIMIT.REFERENCE=410.01:1:1,CATEGORY=21059:1:1,DRAWDOWN.ACCOUNT=TZS1485200010101:1:1,INT.RATE.TYPE=1:1:1,INTEREST.BASIS=B:1:1,INT.PAYMT.METHOD=1:1:1,INTEREST.RATE=0:1:1,CAPITALISATION=NO:1:1,TOT.INTEREST.AMT=0.00:1:1,LIQUIDATION.CODE=1:1:1,LIQUIDATION.MODE=SEMI-AUTOMATIC:1:1,POSITION.TYPE=TR:1:1,REDUCED.RATE=NORMAL:1:1,DELIVERY.LINK=1:1:1,PRIN.LIQ.ACCT=10100570942:1:1,INT.LIQ.ACCT=10100570942:1:1,CHRG.LIQ.ACCT=10100570942:1:1,MIS.ACCT.OFFICER=1546:1:1,CLEAN.RISK=NO:1:1,AGREEMENT.DATE=20110104:1:1,COUNTRY.RISK=TZ:1:1,COUNTRY.EXPOSURE=TZ:1:1,STATUS.CONTROL=AUTOMATIC:1:1,STATUS=CUR:1:1,DRAWDOWN.ISSUE.PRC=1000000.00:1:1,DRAWDOWN.NET.AMT=1000000:1:1,ISSUE.PL.AMOUNT=0:1:1,ISSUE.PRICE=100:1:1,ISSUE.ACCRUAL=NO:1:1,REIMBURSE.PRICE=100:1:1,REIMBURSE.AMOUNT=1000000.00:1:1,REIMBURSE.ACCRUAL=NO:1:1,FEE.PAY.ACCOUNT=10100570942:1:1,DRAWDOWN.ENT.DATE=20110104:1:1,ALONE.MERGE.IND=MERGE:1:1,AUTO.SCHEDS=NO:1:1,DEFINE.SCHEDS=YES:1:1,SEND.PAYMENT=NO:1:1,SEND.CONFIRMATION=NO:1:1,AMOUNT.APPROVED=1000000.00:1:1,AMOUNT.APPROVED=1000000.00:2:1,INFO.SP.LOAN=37 :1:1,INT.RATE=16.25:1:1,INTEREST.FREQ=M:1:1,REPAY.PRIN.INT=1000000.00:1:1,ROUND.INSTALL=N:1:1,INT.START.DT=20110124:1:1,CHARGE.CODE=99:1:1,LOAN.PURPOSE=12:1:1,MODIFY.TRM=N:1:1,LDVERSION=EM.GIC.SP.LOAN:1:1,SOURCE.FUNDS=7:1:1,ATM.CARD=N:1:1,APPRVD.AMT=1000000.00:1:1,LD.SECTOR=1750:1:1,CONTRACT.DUR=37 MONTHS:1:1,YIELD.METHOD=NO:1:1,SETTLEMENT.MARKET=1:1:1,CONVERSION.TYPE=MID:1:1,LAST.DAY.ACCRUAL=NO:1:1,DEFAULTED.VALUE=NO:1:1,DEALER.DESK=00:1:1,NEGATIVE.RATE=NO:1:1,FWD.PROJ=5:1:1,STMT.NO=VAL:1:1,OVERRIDE=NO.LINE}NO LINE ALLOCATED{{{{{734585{{734585.0000400.01{:1:1,RECORD.STATUS=INAU:1:1,CURR.NO=1:1:1,INPUTTER=26_MSEKENA___OFS_SALARY:1:1,DATE.TIME=1007011616:1:1,CO.CODE=TZ0010002:1:1,DEPT.CODE=1:1:1//CURRENCY=TZS:1:1,FORWARD.BACKWARD=3:1:1,BASE.DATE.KEY=1:1:1,SCH.TYPE=P:1:1,SCH.TYPE=F:2:1,DATE=20110124:1:1,DATE=20110124:2:1,AMOUNT=27027.03:1:1,AMOUNT=0.00:2:1,CHARGE.CODE=99:2:1,FREQUENCY=01M:1:1,FREQUENCY=01M:2:1,CYCLED.DATES=20110124:1:1,CYCLED.DATES=20110224:1:2,CYCLED.DATES=20110324:1:3,CYCLED.DATES=20110427:1:4,CYCLED.DATES=20110524:1:5,CYCLED.DATES=20110624:1:6,CYCLED.DATES=20110725:1:7,CYCLED.DATES=20110824:1:8,CYCLED.DATES=20110924:1:9,CYCLED.DATES=20111024:1:10,CYCLED.DATES=20111124:1:11,CYCLED.DATES=20111224:1:12,CYCLED.DATES=20120124:1:13,CYCLED.DATES=20120224:1:14,CYCLED.DATES=20120324:1:15,CYCLED.DATES=20120424:1:16,CYCLED.DATES=20120524:1:17,CYCLED.DATES=20120625:1:18,CYCLED.DATES=20120724:1:19,CYCLED.DATES=20120824:1:20,CYCLED.DATES=20120924:1:21,CYCLED.DATES=20121024:1:22,CYCLED.DATES=20121124:1:23,CYCLED.DATES=20121224:1:24,CYCLED.DATES=20130124:1:25,CYCLED.DATES=20130225:1:26,CYCLED.DATES=20130325:1:27,CYCLED.DATES=20130424:1:28,CYCLED.DATES=20130524:1:29,CYCLED.DATES=20130624:1:30,CYCLED.DATES=20130724:1:31,CYCLED.DATES=20130824:1:32,CYCLED.DATES=20130924:1:33,CYCLED.DATES=20131024:1:34,CYCLED.DATES=20131125:1:35,CYCLED.DATES=20131224:1:36,CYCLED.DATES=20140124:1:37,CYCLED.DATES=20110124:2:1,CYCLED.DATES=20110224:2:2,CYCLED.DATES=20110324:2:3,CYCLED.DATES=20110427:2:4,CYCLED.DATES=20110524:2:5,CYCLED.DATES=20110624:2:6,CYCLED.DATES=20110725:2:7,CYCLED.DATES=20110824:2:8,CYCLED.DATES=20110924:2:9,CYCLED.DATES=20111024:2:10,CYCLED.DATES=20111124:2:11,CYCLED.DATES=20111224:2:12,CYCLED.DATES=20120124:2:13,CYCLED.DATES=20120224:2:14,CYCLED.DATES=20120324:2:15,CYCLED.DATES=20120424:2:16,CYCLED.DATES=20120524:2:17,CYCLED.DATES=20120625:2:18,CYCLED.DATES=20120724:2:19,CYCLED.DATES=20120824:2:20,CYCLED.DATES=20120924:2:21,CYCLED.DATES=20121024:2:22,CYCLED.DATES=20121124:2:23,CYCLED.DATES=20121224:2:24,CYCLED.DATES=20130124:2:25,CYCLED.DATES=20130225:2:26,CYCLED.DATES=20130325:2:27,CYCLED.DATES=20130424:2:28,CYCLED.DATES=20130524:2:29,CYCLED.DATES=20130624:2:30,CYCLED.DATES=20130724:2:31,CYCLED.DATES=20130824:2:32,CYCLED.DATES=20130924:2:33,CYCLED.DATES=20131024:2:34,CYCLED.DATES=20131125:2:35,CYCLED.DATES=20131224:2:36,CYCLED.DATES=20140124:2:37,FREQ.CODE=M0124:1:1,FREQ.CODE=M0124:2:1,OVERRIDE=LD.FIN.AMT}& FINAL AMOUNT IS &{24 JAN 2014}27026.92:1:1,RECORD.STATUS=INAU:1:1,CURR.NO=1:1:1,INPUTTER=26_MSEKENA___OFS_LOANS:1:1,DATE.TIME=1007011616:1:1,CO.CODE=TZ0010002:1:1,DEPT.CODE=1:1:1

Please Log in or Create an account to join the conversation.

More
13 years 9 months ago #6345 by shanthi
Dear Hamisi,

There are few corrections in the OFS String as mentioned below:

1. INT.RATE to be changed to INTEREST.RATE
2. CO.CODE is a NOINPUT field and cannot be supplied instead put it along with the User details

Do let me know for any further clarifications.

Regards,
Shanthi

Please Log in or Create an account to join the conversation.

  • hamisi
  • Topic Author
  • Visitor
  • Visitor
13 years 9 months ago #6346 by hamisi
OK,

Let me try to change that and see what happens.

Thanks for the helping out with suggestions.

Hamisi

Please Log in or Create an account to join the conversation.

  • hamisi
  • Topic Author
  • Visitor
  • Visitor
13 years 9 months ago #6360 by hamisi
Hello Shanthi,

I did all that but in vain.

Hamisi

Please Log in or Create an account to join the conversation.

  • tadymiu
  • Visitor
  • Visitor
12 years 8 months ago #10501 by tadymiu
Hi all,
I have problem with change schedule of already LD using OFS as following:
Old schedule:
SCH.TYPE:1:=I DATE:1:=20120229 FREQUENCY:1:=M FREQ.CODE:1:=M0129

New schedule: split interest schedule in Feb 16th and remain month in frequency
SCH.TYPE:1:=I,DATE:1:=20120216
SCH.TYPE:2:=I,DATE:2:=20120329,FREQUENCY:2:=M,

My OFS message:
LD.LOANS.AND.DEPOSITS,NW/I/PROCESS,TEST/123456/VN0010187,LD0914781245,DEFINE.SCHEDS::=YES//SCH.TYPE:1:=I,DATE:1:=20120216,SCH.TYPE:2:=I,DATE:2:=20120329,FREQUENCY:2:=M,

But get msg: LD0914781245/LFS120470719253516.00/-1/NO,DATE:2:1=SCHEDULE ALREADY DEFINED UPTO OR PAST THIS DATE

I don't know how to fix that error. Can you help me? Thanks in advance.

Please Log in or Create an account to join the conversation.

More
12 years 8 months ago #10516 by s4sathish
Replied by s4sathish on topic Re: Schedule generation on LD Contract using OFS
Hello,

I hope you had checked the VERSION record used in your OFS input string.
Please ensure it doesnot have any configuration to make the INTEREST.RATE to zero(through version routines OR please check field AUT.NEW.CONTENT)

Please Log in or Create an account to join the conversation.

More
12 years 8 months ago - 12 years 8 months ago #10769 by Azizfatkh
Replied by Azizfatkh on topic Re: Schedule generation on LD Contract using OFS
Greetings,

I want to update LD schedule through OFS, for which I have this for LD

LD,VERSION,,LD1202300092,AUTO.SCHEDS::=NO,DEFINE.SCHEDS::=YES

and after update LD.SCHEDULE.DEFINE WITH

LD.SCHEDULE.DEFINE,NBU.FIZ.NBS,,LD1202300092,FORWARD.BACKWARD::=1,BASE.DATE.KEY::=1,SCH.TYPE:1:=I,DATE:1:=20120404,FREQUENCY:1:=1M,SCH.TYPE:2:=P,DATE:2:=20120404,AMOUNT:2:=44440000,

My responce message for changing the schedule in LD states this

LD1202300092//-1/NO,FORWARD.BACKWARD:1:1=INPUT MISSING,BASE.DATE.KEY:1:1=INPUT MISSING,SCH.TYPE:1:1=INPUT MISSING

and here I don't understand why is the fields from LD.SCHEDULE.DEFINE are required in LD.

During my manual input when I commit an LD after setting NO and YES to the fields AUTO.SCHEDS and DEFINE.SCHEDS consequently, I get an LD.SCHEDULE.DEFINE table for which i am presumed to input. Later I discovered that when I change an LD it gets into INAU until I input SCHEDULE, else just changes back as it was.

Hopefully I stated my situation clearly, thus I want ask a solution for it.
Thank you in advance

Aziz

ps Silly, but tried this also

LD,NBU.FIZ.NBS,,LD1202300092,AUTO.SCHEDS::=NO,DEFINE.SCHEDS::=YES,FORWARD.BACKWARD::=1,BASE.DATE.KEY::=1,SCH.TYPE:1:=I,DATE:1:=20120404,FREQUENCY:1:=1M,SCH.TYPE:2:=P,DATE:2:=20120404,AMOUNT:2:=44440000,
FORWARD.BACKWARD IS AN INVALID FIELD NAME FOR LD.LOANS.AND.DEPOSITS
Last edit: 12 years 8 months ago by Azizfatkh.

Please Log in or Create an account to join the conversation.

More
12 years 8 months ago #10779 by Azizfatkh
Replied by Azizfatkh on topic Re: Schedule generation on LD Contract using OFS
Solved my problem. For the ones who come across this problem add a // like tadymiu did!

Please Log in or Create an account to join the conversation.

More
12 years 8 months ago #10780 by jpb
User Guide OFS :


Attachments:

Please Log in or Create an account to join the conversation.

More
9 years 1 month ago - 9 years 1 month ago #18168 by dml
my case is a bit different i would like to update already existing LD by reducing the interest and then i would want the schedules to be redifined. can any one assist. Am getting this response<....LD1417750804//-1/NO,AMOUNT:1:1=LD.LSC.LEAST,SCH.TYPE:1:1=LM.RTN.P.SCHED.IS.CONTS>. how can i make it regnerate and post the new amount on an 'A' schedule type
Last edit: 9 years 1 month ago by dml.

Please Log in or Create an account to join the conversation.

Time to create page: 0.101 seconds