<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: CLIENT SPECIFIED globally in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/client-specified-globally/m-p/6578052#M1433936</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SYST-MANDT (aka sy-mandt) is set globally at log on, and is inserted into the Native SQL generated by your SAP ABAP SELECT..WHERE statements.  Generally, then, we don't use the CLIENT SPECIFIED addition, at least not without including an explicit value for the MANDT/CLIENT table in our where clause. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are you trying to do, actually?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 08 Feb 2010 14:28:36 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2010-02-08T14:28:36Z</dc:date>
    <item>
      <title>CLIENT SPECIFIED globally</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/client-specified-globally/m-p/6578050#M1433934</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   Is there a way to specify a MANDT globally for all SELECT statements in the report?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers, &lt;/P&gt;&lt;P&gt;Bart&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Feb 2010 13:40:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/client-specified-globally/m-p/6578050#M1433934</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-02-08T13:40:41Z</dc:date>
    </item>
    <item>
      <title>Re: CLIENT SPECIFIED globally</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/client-specified-globally/m-p/6578051#M1433935</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Run it in that particular client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Feb 2010 14:28:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/client-specified-globally/m-p/6578051#M1433935</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-02-08T14:28:08Z</dc:date>
    </item>
    <item>
      <title>Re: CLIENT SPECIFIED globally</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/client-specified-globally/m-p/6578052#M1433936</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SYST-MANDT (aka sy-mandt) is set globally at log on, and is inserted into the Native SQL generated by your SAP ABAP SELECT..WHERE statements.  Generally, then, we don't use the CLIENT SPECIFIED addition, at least not without including an explicit value for the MANDT/CLIENT table in our where clause. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are you trying to do, actually?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Feb 2010 14:28:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/client-specified-globally/m-p/6578052#M1433936</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-02-08T14:28:36Z</dc:date>
    </item>
    <item>
      <title>Re: CLIENT SPECIFIED globally</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/client-specified-globally/m-p/6578053#M1433937</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If i understand correctly, you are looking to fetch the data from another clients also with the same select statements. If so you can try below: CLIENT SPECIFIED&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Below code copied from SAP HELP: &lt;A href="http://help.sap.com/saphelp_nw04/helpdata/EN/fc/eb39c4358411d1829f0000e829fbfe/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/EN/fc/eb39c4358411d1829f0000e829fbfe/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;REPORT demo_select_dynamic_database.

DATA wa TYPE scarr.

DATA name(10) TYPE c VALUE 'SCARR'.

SELECT  *
  INTO  wa
  FROM  (name) CLIENT SPECIFIED
  WHERE mandt = '000'.

  WRITE: / wa-carrid, wa-carrname.

ENDSELECT.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Feb 2010 14:33:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/client-specified-globally/m-p/6578053#M1433937</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-02-08T14:33:24Z</dc:date>
    </item>
    <item>
      <title>Re: CLIENT SPECIFIED globally</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/client-specified-globally/m-p/6578054#M1433938</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have test data on client 300 whereas I can write/edit reports only on client 200.&lt;/P&gt;&lt;P&gt;I know 2 things:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- I can use CLIENT SPECIFIED in SELECT to be able to put MANDT in WHERE clause&lt;/P&gt;&lt;P&gt;- I can be logged on two clients simultaneously and switch between windows&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But I'm trying to make my life simpler. Instead of switching windows or adding MANDT=XXX to every SELECT clause I'd like to specify it globally for whole report and it would cause all selects to work on a specified client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Bartosz Bijak on Feb 8, 2010 3:56 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Feb 2010 14:51:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/client-specified-globally/m-p/6578054#M1433938</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-02-08T14:51:04Z</dc:date>
    </item>
    <item>
      <title>Re: CLIENT SPECIFIED globally</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/client-specified-globally/m-p/6578055#M1433939</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It may not possible since you already have MANDT field inthe table from where you are trying to fetch the data.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Feb 2010 15:37:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/client-specified-globally/m-p/6578055#M1433939</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-02-08T15:37:31Z</dc:date>
    </item>
  </channel>
</rss>

