T24: Mandatory fields for applications/tables

[Igor Micev]

Hi All,

In T24 there are lots of applications and tables.
I want to experiment with something that it is not worthy to introduce
here.

Is it a plcace where I can see the mandatory fields for tables?.
I need to enter records only in basic applications (like CUSTOMER, not
CUSTOMER,VERSION_OF_CUS ...)
But it is not possbile to enter a record for example in CUSTOMER if a
TARGET or INDUSTRY, or ... some other fileds are not filled, either
they are not marked as mandatory.
I konw there are difficulties entering records in some applications,
but here my aim is the place where i can find the mandatory-necessary
fileds for tables.

Any ideas, suggestions, ... ?

Thanks in advacne
Igor Micev

[VK]

Hi,

it's not that easy.
Even if you don't use VERSION mandatory field status may be defined at
application level
or to be hard-coded in cross-validation template section.

For hard-coded checks you are not able to do anything without source
code analysis...

To catch the application level you can try to create "mainline"
subroutine which calls the application that you want to analyse, e.g.:

SUBROUTINE TEST.N.ARR
$INSERT I_COMMON
$INSERT I_EQUATE

V$FUNCTION = 'TEST'
CALL CUSTOMER

and then analyse the contents of N array.

Rules for N array see in I_RULES or in "Template programming" guide
from Temenos.

VK

[Igor Micev]

Hi VK,

Thanks for the help, this is quite useful.
I know it is not that easy, but will try to do something, maybe using
some advanced techniques.

Igor

[VK]

Hi Igor,
if you succeed with any other technique let me know

[Igor Micev]

Yes sure,
I'm still making some analysis about something i want to realize.
Once i succeed with that I'll send it to you. This mail is marked, so will not forget.
Igor

--
Igor Micev

[Ahmet Baysa]

Hi Igor,

For the CUSTOMER table there is CUSTOMER.DEFAULT table where you can define mandatory fields in addition to the ones defined in the source codes. FYI

 

Regards,

Ahmet Baysa