2.9.1 Sub System Pickup/Processing

This topic describes about the sub system pickup/processing.

Subsystem pickup refers to the process of picking up the values in sub systems. Normally values in sub systems will be defaulted based on the data given in the main screen of the online form.

  1. Defaulting of sub system: After providing values in the main screen, user may click on any sub system to view or change the value. On clicking the sub system for the first time, sub system values will be defaulted based on the values provided in the main screen. Action code passed will be SUBSYSPKP. The code for defaulting will have to written by the developer in corresponding hook packages in function.

    Fn_Post_Subsys_Pickup

    In this case SUBSYSSTAT for all subsystems will go as ‘D’ and processing done based on this flag for each sub system (call form). Note that SUBSYSPKP action will default values for all subsystems and not only the sub system being launched

    Example:MICTRMIS:D;ISCTRSTL:D;TACTRTAX:D;CSCTRUDF:D;CFCTROCH:D;CSCTRADV:D;FTCCGCLM:D;

    If user saves the contract without visiting any call forms, then all the subs systems will be defaulted before saving

  2. Uploading of sub system: If after launching the subsystem with defaulted values; User changes the value in subsystem; the new user input values has to be uploaded to the system. Hence while saving, the subsystems which has been modified by user will be uploaded while others will be defaulted.In this case SUBSYSSTAT for the subsystem which has been modified will go as ‘U’ .Developer has to write code for processing based on the flag.
    • Example: if user changes MIS details (MICTRMIS) from what was defaulted; then SUBSYSSTAT will go as
    • MICTRMIS:U;ISCTRSTL:D;TACTRTAX:D;CSCTRUDF:D;CFCTROCH:D;CSCTRADV:D;FTCCGCLM:D;
  3. Re-defaulting of sub system: After launching and changing subsystem values; if user changes any values in main screen which are dependent field for the subsystem: subsystem values will have to be defaulted again based on the new main screen values. Hence the sub system will be re defaulted. In this case value entered by the user in subs system will be lost.In this case SUBSYSSTAT for the subsystem whose dependent fields has been modified will go as ‘R’. Developer has to write code for processing based on the flag.
    • Example: In a Funds Transfer Contract Input Screen, assume that charge subsystem (CFCTROCH) is dependent on the values entered for debit and credit account. After launching the sub system and changing the charges manually; if user changes the account again the charges will have to re defaulted. The manually entered charges will not be considered. SUBSYSSTAT will go as
    • MICTRMIS:U;ISCTRSTL:D;TACTRTAX:D;CSCTRUDF:D;CFCTROCH:R;CSCTRADV:D;FTCCGCLM:D;

    Values for other subsystems will depend on each of their dependencies