Automatically fill Conversion of Applications

Use caution when running this function. If you fill the Conversion of Applications table automatically, the existing records can be overwritten. Therefore, the Enterprise Modeler password is required.

  1. Start the Conversion of Applications (tgbrg5150m000) session.
  2. Click New Group on the toolbar and specify a source and destination Infor component.
  3. From the appropriate menu start session Fill Conversion of Applications (tgbrg5250m000).
  4. Specify this information:
    • The source and the destination to specify between which components the conversion takes place.
    • Overwrite Existing Records specifies if the existing records are overwritten. If this check box is selected, the existing records with the same source session code as the imported session code is overwritten. Otherwise, the imported session code does not overwrite existing session codes
    • Initially, only the source-side of the table is filled. The destination-side is also filled if the Write Values Also in Destination check box is selected.
    • If both the Write Source Applications also in Destination check box and the Convert Applications According to Coding Standards check box are selected, these adjustments are made to the inserted records:

      • The source-side values are translated to the destination-side values for the session code and authorization, according to the Infor LN or Baan standards.
      • If the source session is present in the destination Infor environment and the seventh character of the session code is equal to five. The authorization is Display. If the seventh character is not equal to five, no authorization is given. The session code does not change.
    • If the source session is not present in the destination Infor environment and the seventh character of the session code is equal to one. A check is done to see if the same code with a five as the seventh character exists in the destination Infor environment. If so, the destination code is changed to the new session code and the authorization is set to Full Authorization. If not, the No Destination code is generated and the authorization is No Authorization.
    • If the source session has the format xxxxxx1xxmxxx, and the destination session has the format xxxxxx5xxmxxx. Another record is inserted with the same source session and with the destination session of the xxxxxx1xxsxxx format if this code exists in Infor LN or Baan.
  5. Click Fill. The Conversion of Session Codes (tgbrg550) table is now filled with initial values.
    If you look at the results you see three types of replacements:
    • Multiple replacement (1:N), first and second row:

      For each source session code, multiple destination session codes exist. At conversion, the source session code is replaced with the destination session code with the lowest sequence number.

    • Single replacement (1:1), third row:

      For each source session code, exactly one destination session code exists. At conversion, the source session code is replaced with the destination session code.

    • No replacement (1:0), fifth row:

      No destination session codes are defined for the source session code. This record is not executed at conversion.

    Another type of replacement exists:

    • Complete replacement (1:1), sixth column:

      You can apply the Complete Replacement type in case of Multiple Replacement or Single Replacement. Complete replacement indicates that the functionality of the destination session includes the functionality of the source session.

    Note:  In addition, some specific mapping functionality is used. The system maps:
    • tcedi sessions to ecedi sessions
    • tcqms sessions to qmptc sessions
    • tiitm sessions to tiipd sessions
    • tpprc sessions to tfgld sessions
    • tuxch sessions to daxch sessions