Hi Monika Our organization uses 7 segments Consolidation, Legal Entity, Division, Site(Location), Cost Center, Account and Project. The first six are mandatory. Even though our organization may be more complex than yours, we still probably don't need all of those segments. For instance a division wil occur in one and only one legal entity and a Site will occur in one and only one division. As for FRW row definitions, you don't have to make them as complex as the account structure. If you have redundancies in your strings, ignore all but one segment. For instance, if your "location" codes are uniquely assigned and don't duplicate across company, business, geography, legal entity, you can safely ignore all four of those segments in your row definitions and just define the "location" code. As for reducing the number of string segments, that is a difficult (if not impossible) job once you have started using them. Your best bet is "Don't go there". Gord Royle -----Original Message----- From: Monika_Rossocha@PLANAR.COM [mailto:Monika_Rossocha@PLANAR.COM] Sent: Thursday, February 14, 2002 4:13 PM To: email@example.com Subject: Reflecting complexity of corporate structure in account string Hi, we are currently using five string segments (company, business, geography, legal entity, location), an account and a department number to organize our GL data. This creates some input work and maintenance requirements although we are not a complex conglomerate. I'm seeking information on how other companies use these segments as compared to how complex the company structure is. Do you have redundancies in your string like having a segment for location and one for company although location and company would be unique identifiers. I found that making use of 5+2 segments for GL transactions makes creating and maintaining FRW row definitions quite cumbersome. Has anyone reduced the number of string segments used after finding that you were duplicating information? Thank you, Monika _______________________________________________ This is the SSA's BPCS ERP System (BPCS-L) mailing list To post a message email: BPCS-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l or email: BPCS-Lfirstname.lastname@example.org Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l. Cott - The Leader in Premium Retailer Brand Beverage Innovation.