<?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>Question Re: Customer data in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/customer-data/qaa-p/3843694#M1497930</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="4972656"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="4929064"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="3654040"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="4591664"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;/message/3168994#3168994 &lt;B&gt;[original link is broken]&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="4566710"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 19 May 2008 05:15:58 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-05-19T05:15:58Z</dc:date>
    <item>
      <title>Customer data</title>
      <link>https://community.sap.com/t5/technology-q-a/customer-data/qaq-p/3843691</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.What is master data?&lt;/P&gt;&lt;P&gt;2.What is customer  data?&lt;/P&gt;&lt;P&gt;3.What is customer master data?&lt;/P&gt;&lt;P&gt;4.What is master data management (MDM)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With Regards&lt;/P&gt;&lt;P&gt;Vijay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 May 2008 05:06:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/customer-data/qaq-p/3843691</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-19T05:06:12Z</dc:date>
    </item>
    <item>
      <title>Re: Customer data</title>
      <link>https://community.sap.com/t5/technology-q-a/customer-data/qaa-p/3843692#M1497928</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;&lt;STRONG&gt;master data,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Master data is the central information source for your company. All SAP components access this data. By integrating master data in central database objects, you can avoid data redundancy. SAP components use data from the individual master data records for most transactions. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;customer data&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customer data is the data woned by the customer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;customer master data&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customer master data are master data for customer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;master data management (MDM)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP Master Data Management (SAP MDM) is a component of SAP's NetWeaver product group and is used as a platform to consolidate, cleanse and synchronise a single version of the truth for master data within a heterogeneous application landscape. It has the ability to distribute internally and externally to SAP and non-SAP applications. SAP MDM is a key enabler of SAP Enterprise Service-Oriented Architecture. Standard system architecture would consist of a single central MDM server connected to client systems through SAP Exchange Infrastructure using XML documents, although connectivity without SAP XI can also be achieved. There are five standard implementation scenarios:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Content Consolidation - centralised cleansing, de-duplication and consolidation, enabling key mapping and consolidated group reporting in SAP BI. No re-distribution of cleansed data. &lt;/P&gt;&lt;P&gt;Master Data Harmonisation - as for Content Consolidation, plus re-distribution of cleansed, consolidated master data. &lt;/P&gt;&lt;P&gt;Central Master Data Management - as for Master Data Harmonisation, but all master data is maintained in the central MDM system. No maintenance of master data occurs in the connected client systems. &lt;/P&gt;&lt;P&gt;Rich Product Content Management - Catalogue management and publishing. Uses elements of Content Consolidation to centrally store rich content (images, PDF files, video, sound etc.) together with standard content in order to produce product catalogues (web or print). Has standard adapters to export content to Desktop Publishing packages. &lt;/P&gt;&lt;P&gt;Global Data Synchronization - provides consistent trade item information exchange with retailers through data hubs (e.g. 1SYNC) &lt;/P&gt;&lt;P&gt;Some features (for example, workflow) require custom development out of the box to provide screens for end users to use.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 May 2008 05:07:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/customer-data/qaa-p/3843692#M1497928</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-19T05:07:34Z</dc:date>
    </item>
    <item>
      <title>Re: Customer data</title>
      <link>https://community.sap.com/t5/technology-q-a/customer-data/qaa-p/3843693#M1497929</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;Master data are data that you create once only, for example material master data, customer master data, vendor master data,...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customer master data are master data for customer. Master data management is a new tool for managing master data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;...Reward if useful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 May 2008 05:10:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/customer-data/qaa-p/3843693#M1497929</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-19T05:10:46Z</dc:date>
    </item>
    <item>
      <title>Re: Customer data</title>
      <link>https://community.sap.com/t5/technology-q-a/customer-data/qaa-p/3843694#M1497930</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="4972656"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="4929064"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="3654040"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="4591664"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;/message/3168994#3168994 &lt;B&gt;[original link is broken]&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="4566710"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 May 2008 05:15:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/customer-data/qaa-p/3843694#M1497930</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-19T05:15:58Z</dc:date>
    </item>
    <item>
      <title>Re: Customer data</title>
      <link>https://community.sap.com/t5/technology-q-a/customer-data/qaa-p/3843695#M1497931</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vijay,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Master Data&lt;/STRONG&gt; are data, which are created by users based on requirement, such as:&lt;/P&gt;&lt;P&gt;Customer Master Data&lt;/P&gt;&lt;P&gt;Material master Data&lt;/P&gt;&lt;P&gt;Customer Material Info Record&lt;/P&gt;&lt;P&gt;Pricing Condition Record &lt;/P&gt;&lt;P&gt;Vendor Master&lt;/P&gt;&lt;P&gt;&amp;amp; so on ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In SAP determination of any functionality, following are needed:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Input ---&amp;gt; Logic -&lt;/P&gt;&lt;HR originaltext="---" /&gt;&lt;P&gt;&amp;gt; Output&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now to support the logic to give desired o/p when input is there, we need some reference data against which logic can be developed. This data is called Master Data. Now we have different types of master data like Customer, Material, Vendor etc. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will also define Pricing condition records, o/p records, text records also as master data as they also help to determine the logic for converting i/p to o/p&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;master data is modified infrequently.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data records that remain in the database for a long period of time are called master data. Master data&lt;/P&gt;&lt;P&gt;includes creditors, vendors, materials, accounts, and so on.&lt;/P&gt;&lt;P&gt;n Master data is created centrally and can be used in all applications.&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;&amp;#159; A customer is master data that can be used in customer requests, deliveries, invoices, and&lt;/P&gt;&lt;P&gt;payments.&lt;/P&gt;&lt;P&gt;n Master data also has an organizational aspect as it is assigned to organizational units.&lt;/P&gt;&lt;P&gt;n Master data has cross-component usage&lt;/P&gt;&lt;P&gt;Examples:&lt;/P&gt;&lt;P&gt;&amp;#159; Customer master data uses the same data for financial accounting and sales&lt;/P&gt;&lt;P&gt;&amp;#159; Customer master records can be assigned to the following organizational units:&lt;/P&gt;&lt;P&gt;company&lt;/P&gt;&lt;P&gt;code&lt;/P&gt;&lt;P&gt;sales&lt;/P&gt;&lt;P&gt;organization&lt;/P&gt;&lt;P&gt;distribution&lt;/P&gt;&lt;P&gt;channel&lt;/P&gt;&lt;P&gt;division&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When creating a customer master record, you enter:&lt;/P&gt;&lt;P&gt;&amp;#159; Shared data on the client level&lt;/P&gt;&lt;P&gt;&amp;#159; Company code-specific data for each company code&lt;/P&gt;&lt;P&gt;n Data on the client level can be used by all company codes. The customer account number is assigned&lt;/P&gt;&lt;P&gt;on this level. That means, the same customer has an explicit accounts receivable number in all&lt;/P&gt;&lt;P&gt;company codes from a financial view.&lt;/P&gt;&lt;P&gt;If you also have SAP Sales and Distribution implemented, there are additional fields you can&lt;/P&gt;&lt;P&gt;maintain. These fields contain information and control data that are necessary for processing the&lt;/P&gt;&lt;P&gt;business activ ities in the Sales area.&lt;/P&gt;&lt;P&gt;n Fields for customer master data are divided into Accounting and Sales areas. Address data is used&lt;/P&gt;&lt;P&gt;from both areas. In the Sales area, information recorded can be accessed by Financial Accounting&lt;/P&gt;&lt;P&gt;and vice versa.&lt;/P&gt;&lt;P&gt;Note:&lt;/P&gt;&lt;P&gt;The structural logic for customer master records/accounts receivable is also valid for vendor&lt;/P&gt;&lt;P&gt;master records/accounts payable&lt;/P&gt;&lt;P&gt;The material master represents the central source for releasing material-specific data. It is used by all&lt;/P&gt;&lt;P&gt;of the SAP Logistics components in the R/3 System.&lt;/P&gt;&lt;P&gt;n Integrating all of the material data in one single database object means that the problem of data&lt;/P&gt;&lt;P&gt;redundancy is not an issue. The stored data can be used by all areas, such as purchasing, inventory&lt;/P&gt;&lt;P&gt;management, materials planning, invoice verification, and so on.&lt;/P&gt;&lt;P&gt;n The data contained in the material master is required, for example, by the following functions in the&lt;/P&gt;&lt;P&gt;SAP Logistics component:&lt;/P&gt;&lt;P&gt;&amp;#159; Ordering in Purchasing&lt;/P&gt;&lt;P&gt;&amp;#159; Updating movement of goods and managing the physical inventory in Inventory Management&lt;/P&gt;&lt;P&gt;&amp;#159; Posting invoices in Invoice Verification&lt;/P&gt;&lt;P&gt;&amp;#159; Processing sales orders in Sales&lt;/P&gt;&lt;P&gt;&amp;#159; Planning requirements, scheduling work in Production Planning and Control&lt;/P&gt;&lt;P&gt;n The structural logic that applies to vendors and customers is also valid for material master records.&lt;/P&gt;&lt;P&gt;When creating an order for a customer, you must take transport agreements, delivery and payment&lt;/P&gt;&lt;P&gt;conditions, and so on, with business partners into consideration. To avoid re-entering this&lt;/P&gt;&lt;P&gt;information each time for every activity related to these business partners, relevant data for the&lt;/P&gt;&lt;P&gt;activity from the master record of the business partner is simply copied.&lt;/P&gt;&lt;P&gt;n In the same way, the material master record stores information, such as the price per unit of quantity,&lt;/P&gt;&lt;P&gt;and stock per storage location that is processed during order entry. This concept is valid for&lt;/P&gt;&lt;P&gt;processing data for each master record included in the activity.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rewards points if helpful.&lt;/P&gt;&lt;P&gt;Ganesh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 May 2008 05:22:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/customer-data/qaa-p/3843695#M1497931</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-19T05:22:47Z</dc:date>
    </item>
  </channel>
</rss>

