Drop down enquiry based on condition.

-


Description:

We need to generate different drop downs on a version field based on another version field. We tried to populate the T array of the target field by making it as a Hot field Validation field, but it did not help. So to resolve this we created a Nofile enquiry and attached it to the target field. As this is a Nofile enquiry we can manage what to display in the field.

Below are the details:

There are 2 associated multi value fields and are,

1) THIRD.PARTY - YES or NO Field
2) APPL.TRANS - Normal Field

Version Validation:

IF THIRD.PARTY = NO THEN
ONLY 8 TRANSACTION TYPES SHOULD COME IN DROP DOWN IN THE
TRANSACTION.TYPE FIELD
END ELSE
ONLY 3 TRANSACTION TYPES SHOULD COME IN DROP DOWN IN THE
TRANSACTION.TYPE FIELD
END

To achieve the code is written as below and attached with the field THIRD.PARTY:

THIRD.PARTY = COMI
IF THIRD.PARTY EQ 'YES' THEN
T (QTC.CBD.APPL.TRANS) <2> = "Withdrawal_Earning _Distribution_Loan Advances"
END ELSE
T (QTC.CBD.APPL.TRANS) <2>
= "All_Deposit_Withdrawal_Interest_Payment_Drawdown_Repayment_Scheduled
_Repayment (DSP)_None_Guarantee_Fees"
END

Note: This above code was not working.

Resolved Steps:

Hence this task is achieved by including one Nofile enquiry and then this enquiry is attached
with the field APPL.TRANS.
SS Record

Version Record
Note: THIRD.PARTY is previous field and THIRD.FLAG is Enquiry Selection Field.
Routine:
$INCLUDE T24.BP I_COMMON
$INCLUDE T24.BP I_EQUATE
$INCLUDE T24.BP I_ENQUIRY.COMMON
$INCLUDE QTC.BP I_F.QTC.CUST.BANK.DTLS
*
GOSUB PROCESS
*
RETURN
*
*--------------------------------------------------------------------------------
PROCESS:
*-----------*
ENQ.DATA = ''
FN.QTC.CUST.BANK.DTLS = 'F.QTC.CUST.BANK.DTLS'
F.QTC.CUST.BANK.DTLS = ''
CALL OPF (FN.QTC.CUST.BANK.DTLS, F.QTC.CUST.BANK.DTLS)
THIRD.PARTY = D.RANGE.AND.VALUE<1>
IF THIRD.PARTY EQ 'YES' THEN
ENQ.DATA<-1> = 'Withdrawal*'
ENQ.DATA<-1> = 'Interest Payment (Earning Distribution)*'
ENQ.DATA<-1> = ‘Drawdown (Loan Advances)*'
END ELSE
ENQ.DATA<-1> = 'All*'
ENQ.DATA<-1> = 'Deposit*'
ENQ.DATA<-1> = 'Withdrawal*'
ENQ.DATA<-1> = 'Interest Payment*'
ENQ.DATA<-1> = 'Drawdown'
ENQ.DATA<-1> = 'Repayment'
ENQ.DATA<-1> = 'Scheduled Repayment (DSP)*'
ENQ.DATA<-1> = 'None*'
ENQ.DATA<-1> = 'Guarantee*'
ENQ.DATA<-1> = 'Fees*'
END
RETURN
END

Comments

Post a Comment

Popular posts from this blog

Current Variables in T24

-
CURRENT VARIABLE Introduction In addition to the system common variables that can be used in ENQUIRY and VERSION there is a feature where the user can populate a variable of their own and use it later. There are now a series of new system variables and a much wider option for users to create and use their own which are: CURRENT.CUSTOMER CURRENT.ARRANGEMENT CURRENT.EXTERNAL.USER These may be set on login by an external user and cleared when they logout. This means that ENQUIRY & VERSION can be tailored to accept the content of the variable instead of forcing a user to enter their own customer number or arrangement etc. Similarly in VERSION you can now default a field content by using the !CURRENT.CUSTOMER to populate a customer field with the current content of the variable. So the variable could be set in one Enquiry and used in either another Enquiry linked to it; or via VERSION to populate fields in an application triggered from the Enquiry. Note: ...
Read more

All accounting entries of an T24 account

-
There is a core routine that will return all the accounting entries for an account it is EB.ACCT.ENTRY.LIST Syntax: EB.ACCT.ENTRY.LIST(ACCOUNT.NUMBER,FROM.DATE,END.DATE,YID.LIST,OPENING.BAL,ER) Passed Parameters. ACCOUNT.NUMBER :- Account for which balance & entries is to be returned. FROM.DATE :- Start date for opening balance and entries. END.DATE :- The last date to be considered. Outgoing : YID.LIST :- List of statement entry ids. OPENING.BAL :- Opening balance on the startt date. ER :- Any errors found
Read more

SQL queries in JBase

-
The query Language of Jbase is really restrictive. Data analysis and comparison between two table is not possible without the use of spreadsheet software. I recently came to know that Jbase is providing a command called SQLSELECT through which you can actually issue SQL query command directly on Jbase tables. A sample would be like SQLSELECT * FROM FBNK.ACCOUNT WHERE SHORT_NAME LIKE '%PETER%' AND CATEGORY = 6601 Limitations: The command though have serious limitations such as  The table you query should not have dot charecter for example you cannot query FBNK.CUSTOMER.ACCOUNT with this command. But there is a workaround for the above drawback. Make a copy of the VOC record FBNK.CUSTOMER.ACCOUNT into a new one without ID in its ID. For Example: COPY FROM VOC FBNK.CUSTOMER.ACCOUNT,FBNK.CUSACC SQLSELECT * FROM FBNK.CUSACC; will work. The field name should not have dot character. You can overcome this by changing the dot character to underscore. For...
Read more