When the program performs the first I/O Rule associated with the first flow level, it increments the value in the isa_out_no field in the trading partner table and the value in the gs_no field in the trade agreement table and stores these values in memory. At this point, it loads information from the company file/table into WIX_* system variables and information from the trading partner database into the system variables that hold trading-partner and trade agreement information.
In the Before Rule associated with the first flow level, the user can assign values to system variables, overriding the system-assigned values and causing the program to use the user-assigned values instead. This gives the user control over envelope fields that are loaded from system variables; some fields are loaded from other program variables.
Before performing the After Rule associated with the first flow level, the program populates the outbound EDI envelope fields with values from either system variables (user-assigned or system-assigned) or other program variables.
During processing – each time that the trading partner changes (regardless of whether the transaction changes), the program loads the interchange and group control numbers stored in memory into the appropriate database fields (ISA_OUT_NO and GS_NO) and increments the values stored in memory by 1.
Each time that the transaction changes (regardless of whether the trading partner changes), the program loads the group control number stored in memory into the GS_NO field in the trade agreement database and increments the value stored in memory by 1.
