Multiple Product Lines in V10

Despite having been on Lawson for almost 20 years, we have never had more than a single product line within an LSF environment. I am familiar with the copy product line procedure and have used it successfully to copy prod to test, overlaying existing test. I see there is a similar process that creates a new product line which looks to be pretty straightforward. For the first time, we will be needing a second test product line.

But GEN and LOGAN are schemas in the DB of the original product line. Since GEN data is environment specific, where is GEN data for the additional product line stored, in the original database or in both databases? How does Lawson know where to find it? Also, I know Portal knows the product line from the user set up, but how are multiple product lines handled for ESS, RSS and MSCM?

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

We have three productlines in our one DEV environment. There is only one GEN and LOGAN database for the entire environment. In the database, we have three different tables - LSAPPS (QA), LSAPPSTEST and LSAPPSDEV. The users are all per environment, meaning it is the same user ID for all three of those product lines. You would typically name your security classes and roles to reflect the product line and that is how you know which product lines the user has access to. Like ARUserTest or ARUserDev or whatever. We don't use ESS, RSS or MSCM, so I cannot answer those questions. By the way, Infor consultants set up and hosts/manages our V10 setup and this is how they set it up. I would never ever recommend doing more than one product line in an environment again.

unknown

We have four prod lines in our dev environment. We have one set of security rules that so that all the product lines have the same security classes. As for ESS, whatever productline you assign the user in Lawson security, that is the product line that would be their default. If you change it in Lawson security (on the RM admin screen) then that is the product line they would be using in EMSS. For our super users we have modified the role xml file to allow them access to change the product line they point to on their own.

sriman-shivakoti

Is your ESS customized? Do you have a vanilla instance for any of your TEST product lines?

unknown

Is our ESS customized - yes, but you don't need to customize it because of having more than one product line. Do we have a vanilla instance of any product lines - no, we refresh them from production every couple weeks.

unknown

Thanks for the responses. But I'm still unclear. I know that the capital ORACLE file is product line specific and points to the database associated with the product line. But if you have multiple product lines within a single environment, how does Lawson know which one contains the GEN schema? And which schemas are product line specific and which are environment specific. We have GEN, LOGAN, LAWSON, TAXFACTORY and MSCM schemas in our existing database. I know LAWSON contains the product line data and GEN is environment.

richardd

There is one GEN database and one LOGAN database per environment. Each product line has it's own database. The tables in the GEN database contain PRODUCTLINE as a column. In Portal, Preferences--> User Options can be used to change the DATAAREA (Product Line).

0712131256598360.doc

unknown

Thanks. I found part of the answer - GEN and LOGAN locations (database, schema and table spaces) are defined in install.cfg, so apparently they can be anywhere, either in any one of the product line databases or in their own database. I think the MSCM schema has to exist for each product line since it contains product line data. Still not sure about TAXFACTORY, is it product line or environment level?

richardd

Tax Factory supports defining multiple DATASETS which can equate to a product line. The DATASET environment variable is used to select which DATASET is used by Lawson. Not sure how to use multiple DATASETS on the same box concurrently.

bhillz

Assuming your TAXFACTORY is for BSI, then it can be separate (one for each product line) or combined (one TAXFACTORY for all product lines).

Each way has benefits, depending on how you use BSI. For our installations, we use one BSI for production and one for all non-production, regardless of environment or product line. BYMMV.

Copyright © 2025 Infor. All rights reserved.