× Discuss about Archiving, Close of Business, Delivery Setup, Security Management System, Global Processing etc…

OFS string for the multiple associated application

  • sailen
  • Topic Author
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 116
  • Thank you received: 0

sailen created the topic: OFS string for the multiple associated application

Hi,

How can the OFS string be prepared for the version that has the associated versions too? Say if I need to create an OFS message to pass the values to LD.LOANS.AND.DEPOSITS and based on the value of ANNUITY.PAY.METHOD (field of LD.LOANS.AND.DEPOSITS) , I need to pass the values to LD.SCHEDULE.DEFINE too.
When the value of ANNUITY.PAY.METHOD = 'END', LD.SCHEDULE.DEFINE should be filled up.

Can anyone suggest me on this?

Any prompt response is highly appreciated.

Thanks in advance,
Sailen
#16781

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

  • Posts: 2845
  • Karma: 512
  • Thank you received: 647

jpb replied the topic: OFS string for the multiple associated application

you have to use // to separate LD from LD-schedule data

Loans and Deposit contracts with Payment Schedules
An LD contract with a payment schedule requires the information for the linked application LD.SCHEDULE.DEFINE. This can be done by adding the field information for LD.SCHEDULE.DEFINE to the Loans and deposits MESSAGE DATA component, separated by ‘//’ (2 forward slashes).
When using OFS to update LD.LOANS.AND.DEPOSITS with LD.SCHEDULE.DEFINE, the GTS.CONTROL field on both versions must be set to 1, overrides and accepted and errors placed on hold.
#16783

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

  • sailen
  • Topic Author
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 116
  • Thank you received: 0

sailen replied the topic: OFS string for the multiple associated application

Thanks a lot.. It does work!!!

One more query in addition to this. Can we create a version that is similar to standard LD.SCHEDULE.DEFINE,STD and link that version to some other manually created version that is similar to LD.LOANS.AND.DEPOSITS?

Currently it seems that almost all of the versions created from LD.LOANS.AND.DEPOSITS call the linked version LD.SCHEDULE.DEFINE,STD.

Thanks & Regards,
Sailendra Shrestha
#16784

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

  • Posts: 2845
  • Karma: 512
  • Thank you received: 647

jpb replied the topic: OFS string for the multiple associated application

When I remember correctly the LD.SCHEDULE.DEFINE version must have the same PGM.VERSION as the calling LD.LOANS.AND.DEPOSITS, when it's not present ,STD (for I) or ,STDAUTH (for A) are used (if they don't exist the vanilla LD.SCHEDULE.DEFINE will be launched).

e.g. if you use LD.LOANS.AND.DEPOSITS ,INPUT.NEW then define LD.SCHEDULE.DEFINE,INPUT.NEW and it will be called.
#16785

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

  • Posts: 2845
  • Karma: 512
  • Thank you received: 647

jpb replied the topic: OFS string for the multiple associated application

Found the description in LD User Guide :

Customising the Schedule Screen
The schedule definition screen is a standard application, LD.SCHEDULE.DEFINE that can be customised using the VERSION utility in the same way as with any other application.

In order to provide the flexibility of having an input VERSION that is unique or specially suited to a particular contract type, it is possible to create matching VERSION records for the main input LD.LOANS.AND.DEPOSITS and LD.SCHEDULE.DEFINE. This depends on what may be called the VERSION extension; the part of the id after the application name starting with and including the comma (i.e.,COMM).

For example a commitment contract that needs no P schedules could be simplified and use a VERSION contract LD.LOANS.AND.DEPOSITS,COMM. A schedule input VERSION called LD.SCHEDULE.DEFINE,COMM would be invoked automatically as the VERSION part of the application is the same.

The rules for use are:

If a VERSION extension for LD.LOANS.AND.DEPOSITS exists on file for LD.SCHEDULE.DEFINE, then those VERSIONS are used.
If a VERSION extension for LD.LOANS.AND.DEPOSITS does not exist on file for LD.SCHEDULE.DEFINE or no VERSION is used then
- LD.SCHEDULE.DEFINE,STD is used for Input function
- LD.SCHEDULE.DEFINE,STDAUTH is used for authorisation function.

These VERSION records are released as standard and should not be modified.
#16786

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

  • sailen
  • Topic Author
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 116
  • Thank you received: 0

sailen replied the topic: OFS string for the multiple associated application

Thanks for the information JPB. You rocks !!!. :)
#16787

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

Time to create page: 0.140 seconds