Prev
Next
Forums Integration / Customization S3 Customization/Development

SQL to Lawson Data Types

 2 Replies
 0 Subscribed to this topic
 17 Subscribed to this forum
Sort:
Author
Messages
Ari
Veteran Member
Posts: 49
Veteran Member
5/1/2012 10:52 PM
    I am creating a Drill that will be able to drill back into a foreign system from the GLTRANS Table. I have set up all the necessary drill info(file defs, relations, indexes, .or file descriptions, etc.) for the tables in the foreign system. The Lawson app database and the foreign system database are SQL Server.  I have created a separate Database Space for the tables with Is View to YES so that Lawson will not try to manage the foreign tables.( I am using a synonym rather than a view but it should be the same)

    What I would like to know is if there is documentation on the translations of the database data types to the lawson dbdef data types. (as in int to numeric)

    Normally you are defining files(Tables) up in dbdef and then creating them with dbreorg. The dbreorg utility takes care of defining the datatypes in the database for you. I already have the tables but I still need to define them correctly in dbdef so that Lawson can use them in the Drill.

    Any information on this would be appreciated.
    Woozy
    Veteran Member
    Posts: 709
    Veteran Member
    5/2/2012 5:08 PM
      Hi Ari,

      So you are just trying to determine what data types your view will need to have in order to map correctly?

      Though it would be nice to have the document you are asking about, what I would do is use dbdef to temporarily create a custom table that includes the fields/elements you will have in your view.  After you use blddbdict to generate it you should be able to look at the table in SQL to see how it was created.  After you get the information you can just delete that table again.

      Kelly
      Kelly Meade
      J. R. Simplot Company
      Boise, ID
      Ari
      Veteran Member
      Posts: 49
      Veteran Member
      5/3/2012 6:20 PM
        Thanks for the reply.

        The problem is that what I have is not really a VIEW. It is a Synonym. The Foreign Table already exists. The Synonym just points to the Foreign Table from the Lawson App Database. I can't alter the Data Types in the Foreign Table because there are other applications that use the Table. I need to define the fields in dbdef for the Table that already exists.

        An example of the problem is one of the fields in the Table in the Database is defined as data type "Money". I defined that field in dbdef as "Currency". After I ran the blddbdict and did a dbreorg I ran the verifymsf2000 utility against the Table. The output came back clean telling me on mismatches. When I then set up the Drill I get problems when I use this field in the drill output. If I leave that field out the drill works fine. I am pretty sure it is causing a problem in the translation. Now I am in a situation where I have to try other data types in dbdef and then do blddbdict and dbreorg. Of course I have to stop the WebSphere application servers to run the dbreorg. This becomes a rather cumbersome trial and error method to get the data type correct. A chart of the data type translations would go a long way in resolving this.