Using MANDT in tables.

[Piersol, J Mark]

Rick,
 
You are right, this is a trick question.
 
As a general rule, I try to use MANDT, since this is the style I see
most common in SAP.  Making your "Z" table data Client Dependent allows
for data diversity across clients within a system. This data segregation
allows for more flexibility and control in development/testing,
training, and production.  For master data (ie customizing) that is
truly system wide (and essential), you may consider Client Independent
tables.  This will ensure data consistency system wide and will
eliminate the need to populate data in all clients.   =20
 
For workflow related settings, I plan to stick with MANDT. =20
 
Mark       =20
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Rick Sample
Sent: Wednesday, August 18, 2004 11:17 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Using MANDT in tables.
 
 
We are creating tables for a new application. While some of it=20
should have gone directly to ABAP like creating the DB (tables)=20
and programs.
 
We created some tables with MANDT and was asked why we decided to use=20
MANDT in our tables.=20
 
Not sure if this was a trick question so I need to ask why wouldn't we=20
want to use MANDT?=20
When I created a new Business Object it checks for Mandt by default.=20
 
Pros / cons?
 
Rick Sample
WorkFlow Developer
Graybar, Inc.=20