<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by SAP PRESS on Medium]]></title>
        <description><![CDATA[Stories by SAP PRESS on Medium]]></description>
        <link>https://medium.com/@sappress?source=rss-5daa0a1d141e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*2jf7GuErKNV2YqRa.jpg</url>
            <title>Stories by SAP PRESS on Medium</title>
            <link>https://medium.com/@sappress?source=rss-5daa0a1d141e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 15:24:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sappress/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Data Preprocessing Techniques for R Script Modeling and Design]]></title>
            <link>https://medium.com/@sappress/data-preprocessing-techniques-for-r-script-modeling-and-design-971c74e970d5?source=rss-5daa0a1d141e------2</link>
            <guid isPermaLink="false">https://medium.com/p/971c74e970d5</guid>
            <category><![CDATA[sap-book]]></category>
            <category><![CDATA[sap-training]]></category>
            <category><![CDATA[sap-hana]]></category>
            <category><![CDATA[sap-press]]></category>
            <category><![CDATA[r]]></category>
            <dc:creator><![CDATA[SAP PRESS]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 19:12:14 GMT</pubDate>
            <atom:updated>2017-09-14T19:12:14.687Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*buTdi15N9ZKT5WMj1EHpzw.jpeg" /></figure><p>Excerpt from the book <a href="https://www.sap-press.com/sap-hana-advanced-data-modeling_3863/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1236"><em>SAP HANA Advanced Data Modeling</em></a> by Anil Babu Ankisettipalli, Hansen Chen, and Pranav Wankawala. Used with permission of SAP PRESS. All rights reserved.</p><p><em>This blog discusses data preprocessing techniques for R script modeling and design within SAP HANA.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/629/0*yNjkfADYPzSE0B4N.jpg" /></figure><p>In the figure above, you’ll notice that both SAP HANA and the R server run on two different machines, and it is important to understand the data transfer between these two entities. The general rule for executing algorithms is that they run in the database closer to the data to avoid data movement and to reduce overhead. Following the same principle by leveraging the native algorithms available in PAL avoids needing to transfer data between the servers.</p><p>However, not all algorithms and statistical techniques are natively available in SAP HANA. Therefore, it is imperative to keep in mind the cost of transferring this data between the servers before deciding to execute a process in R. Unsupervised learning techniques are the most common techniques used that call for large data transfer between the servers.</p><p>We should consider some data preprocessing techniques, such as sampling with random replacement, sampling without random replacement, and stratification sampling, to reduce the amount of data to transfer in these circumstances. In this section, we will focus primarily on data transfer. Of the sampling techniques, stratification sampling poses the least amount of sampling errors, because it maintains the proportions of data distribution and ensures that each subgroup is represented in the sampled data. Let’s look into stratification sampling further in the next section.</p><p><strong>1 Stratified Random Sampling</strong></p><p><em>Stratification</em> is the process of identifying and dividing populations into subgroups based on values chosen categorically. Each of these subgroups are referred to as <em>strata</em>or <em>stratum</em>. Within each stratum, systematic or random samplings are performed to randomly select portions of the data population.</p><p>In SAP HANA, there are two methods for stratification in PAL. The first is through a sampling function, and the second is through a partition function that divides the dataset into training, testing, and validation datasets. For reducing the dataset, consider the sampling function. To start, generate a wrapper function <strong>SAMPLING_TEST_PROC</strong>with the <strong>PAL SAMPLING</strong> function using the Application Function Library (AFL) framework.</p><p>Below shows the required parameters for stratification. The <strong>PERCENTAGE</strong> parameter provides the sampling size. The value of 0.5 as an input is expected to provide half of the population as the sampling output. <strong>STRATA_NUM</strong> is the number of subgroups to be considered by the algorithm, and <strong>COLUMN_CHOOSE</strong> is the categorical column to be used for subgrouping.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/877/0*pDEwOcIIRu4rz1cW.jpg" /></figure><p>The next table shows the distribution of the distinct values for the chosen column for stratification. There are two distinct values and the population size of each value in the X6 column (arbitrary data column).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*9G8V5d3DzS5O7cWj.jpg" /></figure><p>Below shows the distribution of the X6 column after stratification sampling has been performed. Because we have chosen to sample 50% of values, stratification ensures that the proportions of the population are the same; the output in the table below shows half the original population for each value of X6.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/0*ruHY2qfOwxdCkBKJ.jpg" /></figure><p><strong>2 Random Sampling with Replacement</strong></p><p>In this technique, the sampling algorithm with replacement will replace the item selected, and hence the probability of selection for each item remains the same for every item selected for the sampling.</p><p>In order to run this technique, use the same wrapper you generated previously and the same inputs expected for <strong>SAMPLING_METHOD</strong>. Let’s set this value to 4 and rerun the algorithm. Here is the selected sample distribution:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/0*5F5JIlFm1hpSt2gd.jpg" /></figure><p><strong>3 Random Sampling without Replacement</strong></p><p>In this technique, each sampling selection algorithm will not replace the item selected, and hence the probability of each item selected is reduced by an order of 1. Update the <strong>SAMPLING_METHOD</strong> to 5 and run the algorithm. Below depicts the distribution of X6 after sampling without replacement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/0*WUg3R05n8FpA6GwI.jpg" /></figure><p><strong>4 Systemic Sampling</strong></p><p>In this technique, the algorithm selects all elements randomly. The <strong>SAMPLING_METHOD</strong> is 6 and below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/0*T6RnrBgBDRiiSgaB.jpg" /></figure><p>With nearly 1,600 rows, each technique has a similar output, with deviation around 10%. However, stratification sampling is able to precisely sample, keeping the distribution of the stratification column. In addition to these sampling techniques, SAP HANA also supports sampling based on row offsets (First N, Last N, Middle N, and Every Nth), and each of these aforementioned techniques works on a row offset.</p><p>Each of the techniques discussed enables you to reduce the transfer of datasets by maintaining the homogeneity of the data. The recommended approach is to run these techniques in SAP HANA using logical models such as attribute views, analytic views, calculation views, and/or predictive analytics preprocessing algorithms.</p><p>Excerpt from the book <a href="https://www.sap-press.com/sap-hana-advanced-data-modeling_3863/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1236"><em>SAP HANA Advanced Data Modeling</em></a> by Anil Babu Ankisettipalli, Hansen Chen, and Pranav Wankawala. Used with permission of SAP PRESS. All rights reserved.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Sign up for <a href="https://www.sap-press.com/newsletter/subscribe/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=newsletters">SAP PRESS newsletters</a> to get even more SAP tips and tricks delivered to you monthly!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fce6954%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fce6954%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href">https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=971c74e970d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Evaluation Paths in Organizational Management in SAP ERP HCM]]></title>
            <link>https://medium.com/@sappress/evaluation-paths-in-organizational-management-in-sap-erp-hcm-da616ca88eae?source=rss-5daa0a1d141e------2</link>
            <guid isPermaLink="false">https://medium.com/p/da616ca88eae</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[sap-hr]]></category>
            <category><![CDATA[sap-press]]></category>
            <category><![CDATA[sap-training]]></category>
            <category><![CDATA[sap-book]]></category>
            <dc:creator><![CDATA[SAP PRESS]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 19:10:40 GMT</pubDate>
            <atom:updated>2017-09-14T19:10:40.941Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*buTdi15N9ZKT5WMj1EHpzw.jpeg" /></figure><p>Excerpt from the book <a href="https://www.sap-press.com/organizational-management-in-sap-erp-hcm_3996?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1327"><em>Organizational Management in SAP ERP HCM</em></a><em> </em>by Soham Ray. Used with permission of SAP PRESS. All rights reserved.</p><p><em>In this blog, get an overview of evaluation paths in Organizational Management in SAP ERP HCM.</em></p><p><em>Evaluation paths</em> represent a chain of relationships between object types or even between just two object types; for example, an individual is a holder of a Position, and a Position is held by an individual. A chain of relationships might be from one Org. Unit to another to Positions and finally to Persons.</p><p>An evaluation path enables a user to emphasize reports on objects that are affected by certain relationships. The user can either select an evaluation path and subsequently maintain its properties, or create a new evaluation path beginning with Z.</p><p>For example, the evaluation path <strong>PLSTE</strong> (Position Overview Along Organizational Structure) depicts an overview of the Position assignments. It uses an Org. Unit as its initiation point and effectively reads the underlying structure and the relationships between Positions.</p><p>Let’s take a look at the correlation between relationships and evaluation paths. We’ll then discuss the naming principles for evaluation paths. Finally, we’ll look at the functionality available for using evaluation paths.</p><p><strong>1 Relationships and Evaluation Paths</strong></p><p>Evaluation paths and relationships are interrelated. Evaluation paths can have one or more relationships within them. We can conclude, then, that a relationship can be considered a subset of an evaluation path because evaluation paths can’t exist without relationships.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/458/0*KVq9V-GMGouOa2qZ.jpg" /></figure><p>This correlation can be expressed in a deeper sense when we discuss the creation of evaluation paths.</p><p><strong>2 Naming Principles of Evaluation Paths</strong></p><p>Evaluation paths contain a sequence of object relationships. By specifying the several objects and relationships, the evaluation path will effectively analyze the organization structure of an enterprise and retrieve the included objects.</p><p>SAP ERP HCM incorporates a series of evaluation paths and relationships; for example, the relationship between a Person and a Position is known as a <strong>Holder</strong> with the code A or B 008 (see below). All persons along an organizational structure will be evaluated with the standard evaluation path O-S-P (i.e., Org. Unit-Position-Person) in SAP systems. An evaluation path can have a maximum of eight characters in the naming code. The sequence of the relationships included in the evaluation path determines how the results of the evaluation are portrayed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/777/0*0ef-FXuJuQxBnT0j.jpg" /></figure><p>A new evaluation path is necessary if an object type is created that will be reported or a customer relationship needs to be identified due to the company specifics. For example, if a leader of an Org. Unit has been assigned to take responsibility over other units for HR purposes, without being the disciplinal leader, it’s absolutely necessary to create a new relationship that connects the Position with the additional Org. Units. The user creates a new evaluation path by using the customer namespace ‘Y’ or ‘Z’ and then chooses the evaluation path keeping in mind the organizational structure of the enterprise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/0*B7R3rzr8YSnkFKJ9.jpg" /></figure><p>New evaluation paths can be displayed using report <strong>RHSTRU00</strong> (see the following figures).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/0*oD_oH6qFBWbvP1bZ.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*H2tcl2G0CUt1lT29.jpg" /></figure><p><strong>3 Functionalities</strong></p><p>Evaluation paths can be used in a variety of ways not only in Organizational Management, but also in other submodules of SAP ERP HCM. Evaluation paths are used to select the type of structure that needs to be maintained, reported, or accessed. Here’s an overview of these aspects.</p><p><strong>3.1 Pulling Up a Structure</strong></p><p>Users create and maintain objects in Organizational Management. Objects belong to object types, and object types are specific to the type of structure they belong to. To specify a certain structure in the specific system in order to work with it, you have to define the set of object types pertaining to that structure. You must also determine the relationships that objects hold with each other by specifying the evaluation path. This is because an evaluation path can specify multiple relationships in it. Each relationship further defines the object types that it connects. Hence, just by defining the evaluation path, you can specify both criteria to the system.</p><p><strong>3.2 Reporting</strong></p><p>To access object-oriented reports, you need to use the SAP-delivered tools provided to pull up the reports. You then specify the structure and the object types that need to be reported. This again requires using the evaluation path, as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*hrCC1k2tXw2gZ2Nw.jpg" /></figure><p><strong>3.3 Authorization</strong></p><p>When providing authorizations, there are two classifications that can be used: general and structural. <em>General authorization</em> is mandatory and must be provided to any users who access the SAP ERP HCM system. <em>Structural authorizations</em> are optional and object-oriented, as structural authorizations deal with providing access to a certain section of the organizational structure.</p><p>For instance, a payroll administrator may need access to all the infotypes of all the Holders of Positions listed under two different Org. Units. In that case, the authorization is provided by specifying the evaluation path (see below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/0*tHuZO5wd2-7lPeYG.jpg" /></figure><p>Excerpt from the book <a href="https://www.sap-press.com/organizational-management-in-sap-erp-hcm_3996?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1327"><em>Organizational Management in SAP ERP HCM</em></a><em> </em>by Soham Ray. Used with permission of SAP PRESS. All rights reserved.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Sign up for <a href="https://www.sap-press.com/newsletter/subscribe/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=newsletters">SAP PRESS newsletters</a> to get even more SAP tips and tricks delivered to you monthly!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fce6954%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fce6954%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href">https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da616ca88eae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SAP Database Administration — Emergency Scenarios and Response Plans]]></title>
            <link>https://medium.com/@sappress/sap-database-administration-emergency-scenarios-and-response-plans-28700492e790?source=rss-5daa0a1d141e------2</link>
            <guid isPermaLink="false">https://medium.com/p/28700492e790</guid>
            <category><![CDATA[business-continuity]]></category>
            <category><![CDATA[sap-press]]></category>
            <category><![CDATA[database-administration]]></category>
            <category><![CDATA[sap-training]]></category>
            <category><![CDATA[sap-book]]></category>
            <dc:creator><![CDATA[SAP PRESS]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 19:08:58 GMT</pubDate>
            <atom:updated>2017-09-14T19:08:58.415Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*buTdi15N9ZKT5WMj1EHpzw.jpeg" /></figure><p>Excerpt from the book <a href="https://www.sap-press.com/sap-administration-practical-guide_3639?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1024"><em>SAP Administration — Practical Guide</em> by Sebastian Schreckenbach</a>. Used with permission of SAP PRESS. All rights reserved.</p><p><em>Learn how to be prepare for when the unthinkable happens with your data within an SAP database.</em></p><p>Although numerous emergency scenarios are conceivable, it’s impossible to develop plans for all possible scenarios. Therefore, to keep this task manageable, you should limit yourself to approximately three to five probable scenarios. If an emergency occurs, you can adhere to the scenario that best corresponds to the actual emergency. An emergency scenario comprises the following points:</p><ul><li>Description of the emergency</li><li>Planning the main tasks at a high level</li><li>Estimated downtime</li></ul><p>Use the following scenarios as a starting point, and then prepare three to five scenarios that cover the largest possible range of emergencies.</p><ol><li>For each scenario, create a plan for the main tasks at a high level.</li><li>Test the planned scenarios by simulating different emergencies and checking whether your scenarios could be applied to the actual emergency.</li><li>If this isn’t the case, change the scenarios or develop new ones.</li><li>Repeat the process.</li></ol><p>The following three examples are arranged in order of increasing severity. Note that the downtimes cited are merely examples to illustrate the situations you may encounter. Your own downtime will differ from those specified here. You must therefore replace the sample downtime with a downtime that applies to your environment. It will become clear that, depending on the specific emergency, various extensive measures must be taken and that extremely long downtimes may occur even if the damage appears to be minor.</p><p><strong>1 Damaged Database</strong></p><p>A database may be damaged if test data are inadvertently loaded into the production system or if data incorrectly transported into the production system causes a crash. If such an incident occurs, the SAP database and associated operating system files must be restored. The downtime is, for example, four hours.</p><p><strong>2 Hardware Failure</strong></p><p>The following hardware can fail:</p><ul><li>Processors</li><li>Hard disks or their control unit</li><li>RAID controller (known as an array failure)</li></ul><p>If such a failure occurs, the following steps are necessary:</p><ol><li>Replace the failed hardware.</li><li>If required, rebuild the server (operating system and programs).</li><li>Restore the SAP database and associated files.</li></ol><p>The downtime is, for example, three days, broken down as follows:</p><ul><li>Two days to procure replacement hardware</li><li>One day to rebuild the server (by one person), that is, eight working hours in total.</li><li><em>Plan and test the use of your test system (QAS) as a backup server if the production server (PRD) fails.</em></li></ul><p><strong>3 Complete Loss or Destruction of the Server Facility</strong></p><p>The following components may be destroyed if a catastrophe occurs:</p><ul><li>The servers</li><li>The entire supporting infrastructure</li><li>All of the documentation and materials in the building</li><li>The building itself</li></ul><p>Such a complete loss of facilities may be the result of a natural disaster such as a fire, flood, hurricane, or a manmade catastrophe. If such a catastrophe occurs, the following steps are necessary:</p><ol><li>Replace the destroyed facilities.</li><li>Replace the destroyed infrastructure.</li><li>Replaced the destroyed hardware.</li><li>Rebuild the server and the SAP environment (hardware, operating system, database, etc.).</li><li>Restore the SAP database and associated files.</li></ol><p>The downtime is, for example, eight days, broken down as follows:</p><ul><li>At least five days to procure the hardware. If it’s a regional catastrophe, it may take longer to procure the hardware because vendors may also be affected by the catastrophe.</li><li><em>Turn to national vendors that have several regional distribution centers. As an additional backup measure, you should look for alternative vendors in distant regions.</em></li><li>Two days to rebuild the server (by one person), that is, 16 working hours in total.</li><li>While the hardware is being procured and the server is being rebuilt, an alternative facility in which a minimal emergency network can be constructed must work. The integration into the emergency network may take one day, for example.</li></ul><p>A complete loss makes it necessary to perform a recovery in a new facility or in a different building. Depending on the size of the enterprise, how important the SAP system is for the enterprise’s business processes, and the regional risk of a natural disaster, it may make sense to build a redundant data center. If one of your data centers is destroyed, operation of the system landscape can then switch to the other data center. However, both of these data centers must be built at least a few kilometers apart from each other. If housed in the same building, it’s highly likely that both data centers would fail in the event of a disaster.</p><p>If your enterprise doesn’t have or want to use the resources necessary for a redundant data center, you can agree on a contract for a disaster recovery location with an external provider. Then, if a disaster occurs, the provider’s hardware will be available for your emergency use.</p><p><em>Having a contract for a disaster recovery location doesn’t guarantee that this location will be available in the event of an emergency. If a catastrophe that affects an entire region occurs, many other enterprises will want to access the same disaster recovery locations as you. In such a situation, you may have to cope without a recovery location because other enterprises will have booked the location before you.</em></p><p>Sometimes, the equipment in a disaster recovery location or emergency data center isn’t as efficient as your production system. Therefore, when making plans, bear in mind that you’ll be faced with lower performance and limited transactions. For example, reduce background jobs to only the most urgent jobs. Alternatively, only grant recovery system access to those users who need to perform essential business tasks.</p><p>Excerpt from the book <a href="https://www.sap-press.com/sap-administration-practical-guide_3639?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1024"><em>SAP Administration — Practical Guide</em> by Sebastian Schreckenbach</a>. Used with permission of SAP PRESS. All rights reserved.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Sign up for <a href="https://www.sap-press.com/newsletter/subscribe/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=newsletters">SAP PRESS newsletters</a> to get even more SAP tips and tricks delivered to you monthly!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fce6954%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fce6954%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href">https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28700492e790" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Key T-Codes for SAP’s Personnel Development Submodule]]></title>
            <link>https://medium.com/@sappress/key-t-codes-for-saps-personnel-development-submodule-ea64a66b7b3e?source=rss-5daa0a1d141e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea64a66b7b3e</guid>
            <category><![CDATA[sap-book]]></category>
            <category><![CDATA[sap-hr]]></category>
            <category><![CDATA[sap-press]]></category>
            <category><![CDATA[sap-training]]></category>
            <category><![CDATA[sap-t-code]]></category>
            <dc:creator><![CDATA[SAP PRESS]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 19:06:55 GMT</pubDate>
            <atom:updated>2017-09-14T19:06:55.987Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*buTdi15N9ZKT5WMj1EHpzw.jpeg" /></figure><p>Excerpt from the book <a href="https://www.sap-press.com/sap-transaction-codes_4070?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1366"><em>SAP Transaction Codes:</em> <em>Your Quick Reference to Transactions in SAP ERP</em></a> by Venki Krishnamoorthy, Martin Murray, Norman Reynolds, and Peter Teesdale. Used with permission of SAP PRESS. All rights reserved.</p><p><em>Here’s a look at the transaction codes you can use within the Personnel Development submodule of SAP ERP Human Capital Management.</em></p><p><strong>OOEC: </strong><em>Change Development Plan Catalog</em></p><p>You can use this transaction to create and maintain the Development Plan Catalog. Using this transaction, you can create both Development Plan Group (BL) and Development Plan (B) objects. While creating the development plan objects, you need to specify the validity period as well the qualifications and the proficiency required.</p><p><strong>OOQA: </strong><em>Catalog: Change Qualification(s)</em></p><p>You can use this transaction to create and maintain a Qualification Group (QK) or Qualification (Q). The qualification catalog (containing the Qualification Group and Qualification objects) contains all the qualifications that are required for a company. A well-defined qualifications catalog is essential to define the personnel development and talent management processes. The qualification object can be tied to a person (P) or to a position (S) object. If a qualification is tied to a position, it is called a requirement. Requirements, qualifications, and competency all refer to the same Qualification Group (QK) and Qualification (Q) objects.</p><p>The qualifications catalog can be integrated into SAP ERP HCM Performance Management, SAP ERP HCM E-Recruiting, SAP ERP HCM Enterprise Learning Environment, SAP ERP HCM Organizational Management, and SAP ERP HCM Personnel Administration.</p><p><strong>OOSB</strong>:<strong> </strong><em>Assign Authorization Profiles</em></p><p>You can use this transaction to assign users to different authorization profiles. These assignments are time-dependent, and you can specify the validity period during the assignment. If you check the <strong>Exclude</strong> flag, you can exclude the substructures from the structural authorization check. (Excluding small substructures can also potentially improve the performance of structural authorizations.)</p><p><strong>OOSP</strong>: <em>Define Authorization Profiles</em></p><p>You can use this transaction to create and maintain authorization profiles required for authorizations related to Personnel Planning. You can create authorizations related to plan versions, object types, and object IDs. During customization, you are required to specify the validity period of the authorization profile.</p><p><strong>PEPM</strong>: <em>Profile Matchup</em></p><p>You can use this transaction to compare qualifications (or requirements) between two employees, between two positions, or between an employee and a position. You can also have the system generate the qualifications deficits and training proposals. The profile matchup can be performed between two objects. In the <strong>Display Profile Matchup</strong> screen, you can click the dropdown list and see what different objects can be compared with each other.</p><p><strong>PPCP</strong>: <em>Career Planning</em></p><p>For the specified person (employee) and planning criteria, this report will generate a listing of positions that this person is qualified to occupy during the course of his or her career. This report can be used to determine the training requirements that need to be completed to occupy those positions.</p><p><strong>PPCT</strong>: <em>Task Catalog</em></p><p>You can use this transaction to create and maintain a task catalog. In the task catalog selection screen, enter the selection criteria and click the <strong>Execute</strong> button, which will render the <strong>Maintain Tasks</strong> screen. In the <strong>Maintain Tasks</strong> screen, you can create new tasks or display and maintain existing tasks in the catalog.</p><p><strong>PPDPCS</strong>: <em>Display Development Plan Catalog</em></p><p>You can use this transaction to display the development catalog.</p><p><strong>PPLB</strong>: <em>Evaluate Careers</em></p><p>This report displays the careers available in your organization. Careers form the basis for succession planning.</p><p><strong>PPPD</strong>: <em>Display Profile</em></p><p>You can use this transaction to display the profile of the selected object.</p><p><strong>PPPE</strong>: <em>Area Menu: Personnel Development</em></p><p>You can use this transaction to display the SAP ERP HCM Personnel Development (PD) application menu. The SAP Menu tree structure displays the transactions that are related to Personnel Development.</p><p><strong>PPPM</strong>: <em>Change Profile</em></p><p>You can use this transaction to create and maintain profiles for the different objects, such as Person, Position, Job, Organizational Unit, etc. If you are maintaining the profile for an employee, you can include the employee’s current and potential qualifications, preferences, dislikes, individual development plan, and individual plan history. You can also view the appraisal documents of this employee.</p><p><strong>PPQ1</strong>: <em>Find Objects for Qualifications</em></p><p>For the selected qualifications, you can use this report to generate a listing of objects who have been assigned these qualifications. The basic data will display the name of the individual, assigned qualification, and proficiency level of the individual in that qualification. This report is particularly useful while maintaining the qualifications catalog and can help determine which qualifications can be retained and which are obsolete.</p><p><strong>PPQD</strong>: <em>Display Qualifications Catalog</em></p><p>You can use this transaction to display the qualifications catalog.</p><p><strong>PPRP</strong>: <em>Reporting — Personnel Development</em></p><p>When you execute this transaction, the system displays a dynamic menu with a listing of personnel development related reports that can be executed. The menu is categorized into <strong>Organizational Unit</strong>, <strong>Profile</strong>, and <strong>Others</strong>.</p><p>The reports available under <strong>Organizational Unit</strong> are Profile Matchup: Positions/Holders, Profiles, Succession Overview, Expired Qualifications, and Qualifications Overview. The reports available under <strong>Profile</strong> are Objects Without Qualifications or Requirements and Objects with Non-Rated Qualifications or Requirements. The reports available under Others are Listing of Vacant Positions, Prebookings per Attendee, and List of Alternate Qualifications.</p><p><strong>PPUP</strong>: <em>Settings for Personnel Development</em></p><p>You can use this transaction to make system settings specific to SAP ERP HCM Personnel Development application. In the settings dialog box, you can select the plan version and the time period for which these settings need to be applied.</p><p><strong>S_AHR_61003929</strong>: <em>Catalog: Change Qualification(s)</em></p><p>See Transaction OOQA above for details.</p><p><strong>S_AHR_61003942</strong>: <em>Assign Authorization Profiles</em></p><p>See Transaction OOSB above for details.</p><p><strong>S_AHR_61007168</strong>: <em>Change Development Plan Catalog</em></p><p>See Transaction OOEC above for details.</p><p><strong>S_AHR_61007222</strong>: <em>Define Authorization Profiles</em></p><p>See Transaction OOSP above for details.</p><p><strong>S_AHR_61015532</strong>: <em>Profile Matchup: Positions/Holders</em></p><p>You can use this report to compare the requirements of all the positions that exist in an organizational unit with the qualifications of the employees who are currently in those positions.</p><p><strong>S_AHR_61015533</strong>: <em>Profiles</em></p><p>You can use this report to display the subprofiles of all the planning objects in an organizational unit. The report will also display the individual entries, scales used, proficiency levels, and validity periods.</p><p><strong>S_AHR_61015536</strong>: <em>Expired Qualifications</em></p><p>You can use this report to display all planning objects in an organizational unit with qualifications that are going to expire in the specified reporting period.</p><p><strong>S_PH9_46000016</strong>: <em>Qualifications Overview</em></p><p>This report provides an overview of all the qualifications that the employees possess. The report also displays the qualifications group and the proficiency level of the qualifications. In the selection screen, you should specify the organizational unit(s) that you wish to report on.</p><p><strong>S_PH9_46000018</strong>: <em>Objects with Non-Rated Qualifications or Requirements</em></p><p>You can use this report to get a display of all objects of the specified object type whose qualifications (or requirements) status is “Unevaluated.”</p><p><strong>S_PH9_46000019</strong>: <em>Objects without Qualifications or Requirements</em></p><p>You can use this report to get a display of all objects of the specified object type that do not have any qualifications (or requirements) assigned to them.</p><p><strong>S_PH9_46000022</strong>: <em>List of Alternative Qualifications</em></p><p>This report provides a listing of all qualifications that have alternative qualifications assigned to them. The report also displays the validity of the alternative qualifications as well as the replacement percentage.</p><p>Excerpt from the book <a href="https://www.sap-press.com/sap-transaction-codes_4070?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1366"><em>SAP Transaction Codes:</em> <em>Your Quick Reference to Transactions in SAP ERP</em></a> by Venki Krishnamoorthy, Martin Murray, Norman Reynolds, and Peter Teesdale. Used with permission of SAP PRESS. All rights reserved.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Sign up for <a href="https://www.sap-press.com/newsletter/subscribe/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=newsletters">SAP PRESS newsletters</a> to get even more SAP tips and tricks delivered to you monthly!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fce6954%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fce6954%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href">https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea64a66b7b3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using the Custom Code Analyzer to Find ABAP Object Errors Ahead of SAP S/4HANA Migration]]></title>
            <link>https://medium.com/@sappress/using-the-custom-code-analyzer-to-find-abap-object-errors-ahead-of-sap-s-4hana-migration-da97a2ae7399?source=rss-5daa0a1d141e------2</link>
            <guid isPermaLink="false">https://medium.com/p/da97a2ae7399</guid>
            <category><![CDATA[sap-abap-training]]></category>
            <category><![CDATA[sap-press]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[abap]]></category>
            <category><![CDATA[sap-training]]></category>
            <dc:creator><![CDATA[SAP PRESS]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 19:04:08 GMT</pubDate>
            <atom:updated>2017-09-14T19:04:08.965Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*buTdi15N9ZKT5WMj1EHpzw.jpeg" /></figure><p>Excerpt from the book <a href="https://www.sap-press.com/abap-to-the-future_4161/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1410"><em>ABAP to the Future</em></a> by Paul Hardy. Used with permission of SAP PRESS. All rights reserved.</p><p><em>In this blog, follow Paul Hardy’s instructions for testing your objects against a simplification database to see what will need to be fixed before jumping to SAP S/4HANA.</em></p><p>What’s that coming over the hill? It’s SAP S/4HANA!</p><p>SAP Business Suite will only be supported until 2025, and if you want to stick with SAP you’ll have no choice at that point but to move across to SAP S/4HANA, which is officially a new product as opposed to an upgrade (though I still see it as the latter). SAP has taken this opportunity to clear out the deadwood, like logical databases and other obsolete technologies, and in areas in which currently there are fifty-four different solutions for the same problem, SAP has whittled it down to one.</p><p>What this means is that lots of objects will vanish from the SAP ERP system, and if your custom code references these objects, it’ll stop working on the spot. At this point, you may be thinking it really is a monster coming over the hill; even though 2025 may seem a long way away, it’ll be here before you know it, so you had better start making plans.</p><p>How in the world are you supposed to know what will break? SAP has thought of this and come up with a custom code analyzer for this very purpose. The idea is that you run a report in your current system, which downloads a ZIP file of all your custom code. Then, you need to find a 7.5 system (easier said than done, though you can always use the trial 7.5 system in the cloud) and run yet another report, which uploads the file and performs a static analysis of all your Z code to tell you what will break in SAP S/4HANA and how to fix it. In this section, we’ll walk through the steps you need to take before you start and during the analysis, and then we’ll help you sort through the aftermath.</p><p><strong>1 Preparation</strong></p><p>First things first: You need to be on a certain support stack level to run the extractor in your current system — level 33 for 7.00, level 18 for 7.01/7.02, level 17 for 7.31, and level 13 for 7.4. As of July 2016, none of those support stacks have been released yet. The other important thing is that if you’re below a certain level, such as 10 or below for 7.02, you can’t import the custom code analyzer from SAP Note 2185390.</p><p>If your system has a high enough support stack level to be able to import the program from that SAP Note 2185390, but low enough that the extraction program is not there as standard, you can use SAP Note 2185390 to get the extraction program. Sadly it’s quite a painful process, as there are a few manual steps to go through first (creating SAP BASIS packages) and then a tangled web of dozens of dependent notes to be uploaded. SNOTE, used for implementing SAP Notes, will make sure they’re implemented in the correct order, but I’d forgive you if you waited until the support stack level for your system became available.</p><p><strong>2 Usage</strong></p><p>After SNOTE is finished, you end up with a transport with exactly 131 different objects inside it, the most important of which is a new report called <strong>SYCM_DOWNLOAD_REPOSITORY_INFO</strong>, which, amazingly, downloads repository information.</p><p>You execute the repository downloading program twice — the first time in the background because the analysis will take some time. Most likely, when you look at the log in SM37 the job will crash after one second, complaining that the where used list is not up to date. The SAP Note warns you of that, and tells you to run program SAPRSEUB in the background to fix that problem. That job will probably take quite a while to run, but when it’s finished you can run the repository info report again in the background, and this time it won’t be dead on arrival.</p><p>Once you’ve seen in SM37 that the analysis job is finished, execute the program once again, and this time click the magic <strong>Download ZIP</strong> <strong>File</strong> button. This does what it says on the tin, and you have a lovely file on your hard drive, ready to upload into a 7.5 system.</p><p>Now we come to the concept of the <em>simplification database</em>. This lives in the cloud, as everything worth its salt does these days, and is regularly updated by SAP as SAP keeps making changes to SAP S/4HANA. This database stores all the information about what will break and why and what you can do about it. Only a 7.5 system can read this information, though SAP is working on a cloud version so that you don’t have to get an actual 7.5 system.</p><p>If you do have access to a 7.5 system, you can execute report <strong>SYCM_UPLOAD_REPOSITORY_INFO</strong> to upload the ZIP file you just downloaded from your older SAP system. When you run the report from <strong>SE38</strong>, there is one input field with an (F4) dropdown that doesn’t do anything (easily ignored). After you have finished ignoring the dropdown, give your extraction a name like FRED, press the <strong>Execute</strong> icon and select your ZIP file. Then the screen fills up with a list of data about your custom objects — total number of “customer” objects, number of modified objects, and so on — ending with a happy shout of <strong>Upload DONE!</strong> and the fact that the upload data has been stored in various tables, starting with <strong>SYCM_CUST</strong>.</p><p>Next, you need to go to SAP Service Marketplace to download a ZIP file with the latest simplification database content. Go to <a href="https://support.sap.com/swdc">https://support.sap.com/swdc</a> and search for “CCMSIDB”. The screen in the figure below should appear, and you can download a ZIP file — the fourth entry in the screen shot, though by the time you try this, the patch level probably will have increased.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/953/0*pmlH0CS9h2YQ9lHb.jpg" /></figure><p>This ZIP file is uploaded into the 7.5 system using report <strong>SYCM_UPLOAD_SIMPLIFIC_INFO</strong>. If you find that the report times out, as I did, set a breakpoint in the upload program after each note is uploaded to step through the program in that manner.</p><p>The final step is to run report <strong>SYCM_DISPLAY_SIMPLIFICATIONS</strong> to show the results, and this report proudly says in its comments that it works using a CDS view — naturally! As of July 2016, none of the reports referred to in this section have transaction codes, but I bet in a few years they all will, or they’ll be added to the Custom Code Management Cockpit as new buttons.</p><p><strong>3 Aftermath</strong></p><p>When you get the list of all your custom objects and which ones you’ll need to change to get them to work in SAP S/4HANA, you may want to strap dynamite to yourself and jump into a live volcano, because the list is so big (see below, which shows the result from a typical customer installation; note how small the little indicator is in the slider section on the right of the screen). You’ll see that there were over eleven thousand objects that needed to be changed.</p><p>However, before you decide to end it all, bear in mind that this is a computer spewing out a big list of objects that failed an automated test; just like a Java error message, you’re seeing each error described identically a hundred (or a thousand) times in a row.</p><p>Note that one of the columns is the SAP Note number that describes the nature of the problem and what you need to do to fix it. You’ll see that there are a far fewer notes than there are rows in the report, so there are not actually eleven thousand different problems to be solved — just the same few in many places.</p><p>In the ALV report, if you click the SAP Note number, it will tell you that the note does not exist. You can go to SAP Service Marketplace and type in the note number manually to look at it, however. Hopefully, by the time you read this, the drilldown will be fixed. The notes are very helpful indeed (e.g., SAP Note 1976487 explains what you need to do in the future when reading and writing to standard SAP ERP FI/CO tables; of course, you never write to such tables as that would be naughty, but just in case you do, SAP tells you how to proceed going forward, because most of those tables no longer exist in SAP S/4HANA).</p><p>Moreover, a lot of code to read from such tables will work as is, with the database tables that have vanished either being replaced by views with the same name or, more spookily, being magically “redirected” to views with different names without you having to change a line of code.</p><p>Just as with the Code Inspector warning about code that may no longer work under an SAP HANA system, you will find some changes in these notes that you can make right now in your system to ease the pain later on when you have to make the transition.</p><p>Excerpt from the book <a href="https://www.sap-press.com/abap-to-the-future_4161/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1410"><em>ABAP to the Future</em></a> by Paul Hardy. Used with permission of SAP PRESS. All rights reserved.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Sign up for <a href="https://www.sap-press.com/newsletter/subscribe/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=newsletters">SAP PRESS newsletters</a> to get even more SAP tips and tricks delivered to you monthly!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fce6954%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fce6954%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href">https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da97a2ae7399" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Performing the Initial Data Load in SAP MDG, Consolidation]]></title>
            <link>https://medium.com/@sappress/performing-the-initial-data-load-in-sap-mdg-consolidation-a54dd96b9709?source=rss-5daa0a1d141e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a54dd96b9709</guid>
            <category><![CDATA[sap-mdg]]></category>
            <category><![CDATA[loading-data]]></category>
            <category><![CDATA[sap-training]]></category>
            <category><![CDATA[sap-book]]></category>
            <category><![CDATA[sap-press]]></category>
            <dc:creator><![CDATA[SAP PRESS]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 19:01:34 GMT</pubDate>
            <atom:updated>2017-09-14T19:01:34.006Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*buTdi15N9ZKT5WMj1EHpzw.jpeg" /></figure><p>Excerpt from the book <a href="https://www.sap-press.com/sap-master-data-governance_4192/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1433"><em>SAP Master Data Governance: The Comprehensive Guide to SAP MDG</em></a><em> </em>by Homiar Kalwachwala, Sandeep Chahal, Santhosh Cheekoti, Antony Isacc, Rajani Khambhampati, and David Quirk. Used with permission of SAP PRESS. All rights reserved.</p><p><em>In this blog, get an overview of the options available for the initial data load in SAP MDG, consolidation.</em></p><p>To use SAP MDG, consolidation functionalities, master data from the source has to be loaded in the SAP MDG, consolidation application. It’s important to note that data has to be prepared and transformed into the SAP data structures for the successful processing of the initial load.</p><p>Various extract, transform, and load (ETL) tools can be used for loading master data in SAP MDG, consolidation tables from various SAP applications as well as non-SAP applications.</p><p>SAP has provided several options that can be leveraged for performing initial master data loads in SAP MDG, consolidation: SAP Landscape Transformation Replication Server (SLT), SAP HANA Studio, and CSV files.</p><p><strong>1 Source Tables</strong></p><p>Following are some source tables in which data has to be loaded from the business partner data model:</p><ul><li>Table <strong>BUT000_SRC</strong>: BP General Data-I (required in all cases)</li><li>Table <strong>BUT020_SRC</strong>: BP Addresses (required if address relevant data are uploaded)</li><li>Table <strong>BUT_ADRC_SRC</strong>: Addresses (Business Address Services)</li><li>Table <strong>BUT_ADR6_SRC</strong>: Email Addresses (Business Address Services)</li><li>Table <strong>BUT100_SRC</strong>: BP Roles</li><li>Table <strong>KNA1_SRC</strong>: SAP ERP Customer Data (required if a customer data model is used)</li><li>Table <strong>LFA1_SRC</strong>: SAP ERP Vendor Data (required if a vendor data model is used)</li></ul><p>Following are some source tables from the material data model:</p><ul><li>Table <strong>MARA_SRC</strong>: Central Material Data (required in all cases)</li><li>·Table <strong>MARC_SRC</strong>: Plant Data for Material (required while working with plant-level material data)</li><li>Table <strong>MVKE_SRC</strong>: Sales Data for Material (required if distribution chain data of materials are loaded)</li></ul><p>For accessing all SAP MDG, consolidation-specific source tables, you can search for “*SRC” in Transaction <strong>SE16N</strong> to get a list of all relevant tables.</p><p>Report <strong>MDC_BP_TRANSFORM_SOURCE_DATA</strong> can be used for transforming the customer or vendor data to the business partner data model after the source tables are filled.</p><p><strong>Note: </strong>Report <strong>MDC_BP_TRANSFORM_SOURCE_DATA</strong> doesn’t support the transformation of person-related data. Although the SAP MDG, consolidation process supports business partner organizations and business partner persons, it doesn’t support business partner relationships with current versions. Refer to SAP Note 2233142 for more information on how to fill in source tables in SAP MDG, consolidation. In addition, in SAP MDG 8.0, the inbound functionality doesn’t allow you to load the consolidation source tables; however, with SAP MDG 9.0 and based on the SOA service, you can choose whether to load the master data directly to the SAP MDG active area, to the SAP MDG staging area (change request), or to the source tables for SAP MDG, consolidation.</p><p>While loading data in SAP MDG, consolidation, the source ID should be a unique identifier for a specific source system. If data are uploaded using customer or vendor data models, ensure that the IDs remain unique. If there are vendor and customer IDs within the same number range, the IDs can be made unique by adding a prefix.</p><p><strong>2 SAP Landscape Transformation Replication Server</strong></p><p>SAP Landscape Transformation Replication Server (SLT) is a recommended option for initial loads in SAP MDG, consolidation, especially for existing SAP Business Suite models because identical data models are being used. SLT uses a trigger-based replication approach to pass data from source systems to target SAP HANA-based systems. As shown below, with SLT, it’s possible to load as well as replicate data in real time or schedule data to be loaded into an SAP HANA database at a later time.</p><p>SLT has the built-in capability to handle and support conversion between non-Unicode and Unicode data formats. With full integration to SAP HANA Studio, SLT also has table settings and some simple transformation capabilities. For any complex transformation, specialized ETL tools should be considered. With the help of SAP Solution Manager for SAP HANA, SLT also has data monitoring functionalities. To access SLT, use Transaction <strong>LTR</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/0*90dYbPzZwV2kT0s3.jpg" /></figure><p>SLT-based table data provisions provide the following options:</p><ul><li><strong>Load (Full): </strong>This is normally a one-time event used mainly for initial load purposes from a source application.</li><li><strong>Replicate (Full and Delta Load): </strong>With this option, the initial load is triggered along with any delta changes.</li><li><strong>Stop Replication: </strong>This option removes the database trigger and logging table completely while ensuring the replication process is stopped for a given table.</li><li><strong>Suspend: </strong>This option doesn’t remove the database trigger and logging information but just pauses the replication process.</li><li><strong>Resume: </strong>This option resumes the suspended replication process.</li></ul><p>The following are some salient features while establishing a connection between SAP application and an SAP HANA-based system:</p><ul><li>A read engine is created in the SAP source system.</li><li>The connection between SAP SLT and SAP HANA-based systems is established as a database connection.</li><li>The connection between the SAP source applications and SLT is established as an RFC connection.</li><li>While replicating a table, SLT creates logging tables in the source system.</li><li>SLT transforms all metadata table definitions from the ABAP source applications to SAP HANA.</li></ul><p>Here are some salient features while performing a data load connection between a non-SAP system and an SAP HANA-based system:</p><ul><li>A read engine is created in SLT.</li><li>The connection between SLT and the non-SAP legacy system is established as a database connection.</li><li>The connection between SLT and SAP HANA-based systems is established as a database connection.</li><li>While replicating a table, SLT does create logging tables in the source system.</li><li>SLT transforms all metadata table definitions from the legacy source system to SAP HANA.</li></ul><p><strong>3 SAP HANA Studio</strong></p><p>With SAP HANA Studio, it’s recommended that data be imported in an interim table first, and subsequently, in the next steps, this content from the interim tables can be loaded to source tables using custom ABAP reports or SQL.</p><p><strong>4 CSV Files</strong></p><p>SAP MDG, consolidation supports uploading data from a file without ETL tools. SAP HANA-based systems support data loads from file types such as CSV (comma-separated values), XLS, and XLSX.</p><p>Prior to performing initial data loads using these options, a control file (CTL) should be created. To upload data in SAP MDG, consolidation, a table should already exist; otherwise, a new table needs to be created via a SQL script. The generic steps required when using CSV files for initial loads are as follows:</p><ol><li>Select the target system.</li><li>Select the import source.</li><li>Select the file for upload.</li><li>Select the target table.</li><li>Manage the table definition and data mapping.</li><li>Check the target table.</li></ol><p>You should now have a better understanding of the options available for the initial data load in SAP MDG, consolidation.</p><p>Excerpt from the book <a href="https://www.sap-press.com/sap-master-data-governance_4192/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1433"><em>SAP Master Data Governance: The Comprehensive Guide to SAP MDG</em></a><em> </em>by Homiar Kalwachwala, Sandeep Chahal, Santhosh Cheekoti, Antony Isacc, Rajani Khambhampati, and David Quirk. Used with permission of SAP PRESS. All rights reserved.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Sign up for <a href="https://www.sap-press.com/newsletter/subscribe/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=newsletters">SAP PRESS newsletters</a> to get even more SAP tips and tricks delivered to you monthly!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fce6954%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fce6954%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href">https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a54dd96b9709" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Virtualization in SAP HANA Administration]]></title>
            <link>https://medium.com/@sappress/virtualization-in-sap-hana-administration-1121094fe3dd?source=rss-5daa0a1d141e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1121094fe3dd</guid>
            <category><![CDATA[sap-hana]]></category>
            <category><![CDATA[sap-training]]></category>
            <category><![CDATA[sap-press]]></category>
            <category><![CDATA[database-administration]]></category>
            <category><![CDATA[sap-book]]></category>
            <dc:creator><![CDATA[SAP PRESS]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 18:58:34 GMT</pubDate>
            <atom:updated>2017-09-14T18:58:34.183Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*buTdi15N9ZKT5WMj1EHpzw.jpeg" /></figure><p>Excerpt from the book <a href="https://www.sap-press.com/sap-hana_4160?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1407"><em>SAP HANA: An Introduction</em></a><em> </em>by Penny Silvia, Rob Frye, and Bjarne Berg. Used with permission of SAP PRESS. All rights reserved.</p><p><em>Take a look at virtualization in SAP HANA administration, including its benefits and approved vendors.</em></p><p>Beginning with SAP HANA SPS 5, SAP-certified VMware Hypervisor was the first technology capable of virtualizing SAP HANA servers. Virtualization is the process of creating a virtual instance of a resource within a framework that can be used to run multiple logical instances of a resource in a single physical environment. This virtual resource may be an operating system, a storage device, a database, or even a network resource. See the figure below for a comparison of a standard and a virtualized deployment of SAP HANA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/0*dsytTFhrhPyUuKMS.jpg" /></figure><p>Virtualization offers many advantages when compared to the cost, effort, and risk involved in maintaining numerous physical servers. For example, in a virtualized environment, you can quickly reallocate CPUs and memory resources to your SAP HANA servers to meet the changing needs of your business. The figure below provides a closer look at a virtualized SAP HANA landscape.</p><p>You will generally also have a lower total cost of ownership (TCO) in virtualized environments. A lower TCO is possible because many vendors allow on-demand access for your SAP HANA appliances. For example, Amazon Web Services offers on-demand licensing, which only charges for the time that your cloud environment is on and available for use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/572/0*PfLFNpXHMGxO6TAs.jpg" /></figure><p>On-demand licensing also offers a convenient and inexpensive path to creating and maintaining sandbox environments for proofs of concept (POCs). You can create a small SAP HANA instance with very moderate resource requirements and save a copy of this clean environment. When you need to test new ideas, you can simply bring a copy of the clean environment online, complete the POC work, and then delete the copy when you’re finished. The clean copy will still be available for you to use in your next POC effort. Using on-demand licensing for these sandbox environments is both much more convenient and much less expensive than maintaining both the physical hardware and licensing required for a physical sandbox environment.</p><p>Virtualization through a vendor also serves as a convenient and relatively inexpensive gateway to deploy SAP HANA for small companies. As your business grows, and the need for more CPUs and more memory increases, you can scale your licensing and hardware requirements easily within a virtual landscape. As a result, you can select the size of system that you need right now and re-evaluate your needs periodically. If you need to move to a larger environment, adding processors and memory is simple, and you won’t be left with older hardware that is inadequate to meet your needs.</p><p>Some of the benefits of virtualization include:</p><ul><li>Easy hardware replacement, as there is no need to recertify the operating system and SAP software installations</li><li>IT ownership that can be separated into software and hardware layers</li><li>Independent monitoring of the operating system</li><li>Inexpensive high-availability capabilities</li></ul><p>See the table below for a comprehensive list of approved virtualization vendors as well as the required SAP HANA SPS levels. Please be sure to check the SAP Community Network (SCN) for the latest guidance on supported virtualization vendors. As of this writing, SAP Note 1788665 is the most recent guidance about virtualization, but new vendors may be added frequently, and nonproduction vendors may be certified soon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9oy6dRI9Sf7ezrRM.jpg" /></figure><p>Virtualization is a rapidly growing field in the SAP landscape, so you may also want to examine the notes in the following table for more guidance before choosing your virtualization vendor and purchasing any hardware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*svM4rsr60cUB4Fz3.jpg" /></figure><p>Excerpt from the book <a href="https://www.sap-press.com/sap-hana_4160?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1407"><em>SAP HANA: An Introduction</em></a><em> </em>by Penny Silvia, Rob Frye, and Bjarne Berg. Used with permission of SAP PRESS. All rights reserved.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Sign up for <a href="https://www.sap-press.com/newsletter/subscribe/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=newsletters">SAP PRESS newsletters</a> to get even more SAP tips and tricks delivered to you monthly!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fce6954%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fce6954%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href">https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1121094fe3dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Purchase Requisitions in SAP Materials Management]]></title>
            <link>https://medium.com/@sappress/purchase-requisitions-in-sap-materials-management-8e438144143f?source=rss-5daa0a1d141e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e438144143f</guid>
            <category><![CDATA[sap-training]]></category>
            <category><![CDATA[sap-materials-management]]></category>
            <category><![CDATA[sap-press]]></category>
            <category><![CDATA[sap-mm-training]]></category>
            <category><![CDATA[sap-book]]></category>
            <dc:creator><![CDATA[SAP PRESS]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 18:56:38 GMT</pubDate>
            <atom:updated>2017-09-14T18:56:38.370Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*buTdi15N9ZKT5WMj1EHpzw.jpeg" /></figure><p>Excerpt from the book <a href="https://www.sap-press.com/procurement-with-sap-mm-business-user-guide_4355?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1517"><em>Procurement with SAP MM: Business User Guide</em></a><em> </em>by Matt Chudy and Luis Castedo. Used with permission of SAP PRESS. All rights reserved.</p><p><em>In this blog, get an overview of purchase requisitions in SAP MM including a look at creating one manually.</em></p><p>Purchase requisitions are internal documents through which users can request the purchase of a specific item or service. These documents include information about the material to be purchased, the quantity, the person responsible for the purchase, the preferred vendor, and the date the material or service is required at the company as well as internal financial information.</p><p>The MRP system can also create purchase requisitions for materials needed either for production or sales, which are normally not subject to an approval because the company has already gone through the process of production and sales planning.</p><p>Purchase requisitions can be created for different types of purchases:</p><ul><li><strong>Standard</strong>:<strong> </strong>Purchases of stock materials.</li><li><strong>Subcontracting</strong>: Purchases of services that a third party will execute to transform materials that belong to your company and will come back, most of the time with a different material number.</li><li><strong>Consignment</strong>: Purchases of materials that are kept in stock but belong to the vendor until they are actually used.</li><li><strong>Stock transfer</strong>: Requirements to move or purchase materials between plants or companies of the same enterprise group.</li><li><strong>External service</strong>: Purchases of services, one-time services, or services included in the service master.</li><li><strong>Third party</strong>: Purchases of stock materials that will be delivered to either a customer or a vendor, instead of being delivered to your facility. Normally part of a sales process, purchasing-only scenarios can also be addressed with this type of purchase requisition.</li></ul><p>Like other SAP documents, purchase requisitions have a header and Structure item details. Unlike other SAP documents, the header is dedicated only to adding text notes that apply to all of the items in the requisition. SAP designed the requisition document with the final user in mind, who may only care about entering the items that need to be purchased. You can choose between conventional text processing and a continuous text editor, which allows automatic line breaks and text search and replace.</p><p>The requisition items contain all of the necessary information for buying the required materials or services, all in a single screen.</p><p><strong>1 Creating a Purchase Requisition Manually</strong></p><p>To create a purchase requisition manually, use Transaction <strong>ME51N</strong> or follow the menu path: <strong>Materials Management &gt; Purchasing &gt; Purchase Requisition &gt; Create</strong>. The screen has three sections: <strong>Header, Item Overview, and Item</strong> details. Follow these steps:</p><p>1. Enter <strong>Short Texts</strong> in the header section if you need to do so.</p><p>2. In the <strong>Item Overview</strong> section, enter the basic information:</p><ul><li><strong>Account assignment</strong></li><li><strong>Item Category</strong></li><li><strong>Material number</strong></li><li><strong>Quantity</strong></li><li><strong>Unit of measure</strong></li><li><strong>Plant</strong></li></ul><p>With this information, the system can fetch most of the rest of the information, for example, the material description, delivery address, material group, planned delivery time, valuation price, company code, purchasing group, and MRP controller (see the figure below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DeVSpcI5KvRJiQvC.jpg" /></figure><p>If necessary, the user can change the delivery address, which, by default, is the <strong>Plant</strong> or <strong>Stor. Loc.</strong> address.</p><p><strong>2 Assigning Source of Supply</strong></p><p>Purchase requisitions need to be assigned a source of supply, which can be determined automatically if the material has only one info record or several info records and a source list. The vendor can also be entered manually.</p><p>To assign a source of supply, follow these steps:</p><ol><li>Expand the <strong>Item Detail</strong> section of the purchase requisition.</li><li>Select the <strong>Source of Supply</strong> tab.</li><li>If you know which vendor you want to assign, enter the vendor in the <strong>Vendor</strong> field. Otherwise, click on the <strong>Assign Source of Supply</strong> button and select a vendor from the list that is presented.</li><li>If necessary, run a price simulation by selecting a vendor and clicking on the <strong>Price simulation</strong> button. You can also run a price simulation for all vendors by clicking on the <strong>Price simulation all </strong>button.</li></ol><p>Purchase requisitions can be subject to a release strategy, which will require other users to review and approve the purchase requisition. This is beyond the scope of this blog.</p><p>The following table lists some useful transactions for working with purchase requisitions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/0*u5XFrta2M8Svb_ln.jpg" /></figure><p>Excerpt from the book <a href="https://www.sap-press.com/procurement-with-sap-mm-business-user-guide_4355?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1517"><em>Procurement with SAP MM: Business User Guide</em></a><em> </em>by Matt Chudy and Luis Castedo. Used with permission of SAP PRESS. All rights reserved.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Sign up for <a href="https://www.sap-press.com/newsletter/subscribe/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=newsletters">SAP PRESS newsletters</a> to get even more SAP tips and tricks delivered to you monthly!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fce6954%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fce6954%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href">https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e438144143f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data Modeling in SAP Master Data Governance for Financials]]></title>
            <link>https://medium.com/@sappress/data-modeling-in-sap-master-data-governance-for-financials-83977741e30d?source=rss-5daa0a1d141e------2</link>
            <guid isPermaLink="false">https://medium.com/p/83977741e30d</guid>
            <category><![CDATA[sap-financial]]></category>
            <category><![CDATA[sap-press]]></category>
            <category><![CDATA[data-modeling]]></category>
            <category><![CDATA[sap-book]]></category>
            <category><![CDATA[sap-mdg]]></category>
            <dc:creator><![CDATA[SAP PRESS]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 18:52:41 GMT</pubDate>
            <atom:updated>2017-09-14T18:52:41.869Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*buTdi15N9ZKT5WMj1EHpzw.jpeg" /></figure><p>Excerpt from <a href="https://www.sap-press.com/controlling-with-sap-practical-guide_3625/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1012"><em>Controlling with SAP — Practical Guide</em></a> by Janet Salmon. Used with permission of SAP PRESS. All rights reserved.</p><p><em>Learn how to establish a data model so you can load relevant master data from local systems into MDGF.</em></p><p>In terms of data modeling, the master data governance requirements are similar to the requirements for master data reporting in SAP BW. Whereas in SAP BW data models can include different InfoObjects for cost centers, customers, materials, and so on, in SAP MDGF we find a data model that comprises multiple entity types and includes such information as their attributes, whether they can be viewed in a hierarchy, how groups are handled, and so on. It’s important to understand that this model links related data, so the link between cost center and profit center is considered a part of such a model. From SAP MDGF 7.0, you will also find a link between accounts and primary cost elements. The figure below shows the relationships between the various entities in Financials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/0*Np4C1Lg55mgtmeyF.jpg" /></figure><p>SAP delivers several data models for master data governance, which your administrator can activate via the IMG. You’ll find the settings under <strong>Cross Application Components &gt; Processes and Tools for Enterprise Applications &gt; Master DataGovernance &gt; General Settings &gt; Data Modeling &gt; Edit Data Model</strong>. The delivered data models include the following (again, take a look at these options with your administrator):</p><ul><li><strong>Chart of Accounts and Org. Units (0G)</strong>: This model was delivered in EHP 5 for use in combination with the business function Master Data Governance for Financials, Organizational Units (<strong>FIN_MDM_ORG</strong>). The data model includes companies, profit centers, and cost centers, in addition to charts of accounts and cost elements. If you plan to implement in enhancement package 5 or later, use this data model rather than 0F.</li><li><strong>Chart of Accounts (0F)</strong>: This model was delivered in enhancement package 4 for use in combination with the business function Financial Master Data Management: Charts of Accounts (<strong>FIN_MDM_ACC</strong>). The data model supports the central definition of global and local charts of accounts. This model has been superseded by data model 0G.</li><li><strong>Business Partner (BP)</strong>: This covers the master data for the business partner, the supplier, and the customer. Delivery of the supplier model began with EHP 5 and continued over subsequent enhancement packages. Delivery of the vendor model began with EHP 6 and continued over subsequent enhancement packages.</li><li><strong>Material Maintenance (MM)</strong>: This covers the master data for the material master. Delivery of the model began with EHP 5 and continued over subsequent enhancement packages. From a controlling point of view, you will find that the MDG-M model covers both general master data and valuation-specific data, making it compatible with various views of the material master.</li></ul><p>The figure below shows the entity types included in the master data model Chart of Accounts and Org. Units (<strong>0G</strong>). The entity types of most interest to the controller are the cost elements (<strong>CELEM</strong>), cost element groups (<strong>CELEMG</strong>), cost element hierarchies (<strong>CELEMH</strong>), cost centers (<strong>CCTR</strong>), cost center groups (<strong>CCTRG</strong>), and cost center hierarchies (<strong>CCTRH</strong>).</p><p>In the figure below, notice two fundamental aspects of SAP MDGF:</p><ul><li>The controlling entity types are flagged as being changeable via a <em>change request</em>. This means that we’ll find the change request used as both a ticketing mechanism to notify the relevant stakeholders that something is to be done and as a DataStore for the various approvals needed before the change can be executed.</li><li>The entity types are linked with an <em>edition</em>. An <em>edition</em> typically refers to a specific time frame, such as the second quarter of 2014, and groups together all changes to the master data requested within that time frame. Many change requests can be assigned to a single edition, and once all these requests have been processed the data in the edition can be replicated to the local systems.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Bre8uAEQ7fX9w3ru.jpg" /></figure><p>If we compare this data model with the data model for material masters shown in the figure below, we see that these entities are also linked with change requests but that there is no edition. The objects are simply maintained and then replicated to the associated systems via a change request. In Financials, it’s common for headquarters to initiate changes to the account structures, profit center groupings, and cost center groupings and to issue an effective-from date for their usage to the subsidiaries. However, in Logistics, the creation of new materials, suppliers, or customers is rarely tied to a specific time frame but instead needs to be started as the new master data is required. A validity date is still commonly needed, but this might mean that if a supplier is moving to a new address from June 15th onward, then the address change must become effective in all systems on that date.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fS9TiZGOIuac-XCQ.jpg" /></figure><p>Once you have established your model, you can load the relevant master data from your local systems using Transaction <strong>MDMGX</strong>. This is a generic tool for loading entities into your model. Other organizations use SAP Master Data Governance simply to create new clean master data going forward.</p><p>Excerpt from <a href="https://www.sap-press.com/controlling-with-sap-practical-guide_3625/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1012"><em>Controlling with SAP — Practical Guide</em></a> by Janet Salmon. Used with permission of SAP PRESS. All rights reserved.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Sign up for <a href="https://www.sap-press.com/newsletter/subscribe/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=newsletters">SAP PRESS newsletters</a> to get even more SAP tips and tricks delivered to you monthly!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fce6954%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fce6954%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href">https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83977741e30d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating SAP Solutions by T-Codes]]></title>
            <link>https://medium.com/@sappress/navigating-sap-solutions-by-t-codes-5eb25eeef6ec?source=rss-5daa0a1d141e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5eb25eeef6ec</guid>
            <category><![CDATA[sap-training]]></category>
            <category><![CDATA[sap-t-code]]></category>
            <category><![CDATA[sap-press]]></category>
            <category><![CDATA[sap]]></category>
            <category><![CDATA[sap-book]]></category>
            <dc:creator><![CDATA[SAP PRESS]]></dc:creator>
            <pubDate>Tue, 12 Sep 2017 14:18:37 GMT</pubDate>
            <atom:updated>2017-09-14T18:47:48.543Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*buTdi15N9ZKT5WMj1EHpzw.jpeg" /></figure><p>Excerpt from the book <a href="https://www.sap-press.com/using-sap_4155/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1404"><em>Using SAP: An Introduction for Beginners and Business Users</em></a> by Olaf Schulz. Used with permission of SAP PRESS. All rights reserved.</p><p><em>New to SAP? Looking to better maneuver within your solutions? This blog introduces you to transaction codes and how they make your job easier.</em></p><p>Transaction codes help you quickly access the desired application without navigating via the SAP Easy Access menu. Transaction codes are alphanumeric codes assigned to every application in the SAP system. You must know the transaction code of the desired application to navigate to it.</p><p>To use transaction codes in the command field, follow these steps:</p><p>1. Click the command field after logon (see the figure below). The blinking cursor indicates that this field is active and ready for input.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/258/0*GZiWNQjgYJXHe3xI.jpg" /></figure><p>2. Enter a transaction code (see next figure). Confirm your input by clicking the <strong>Next</strong>button or pressing (<strong>Enter</strong>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/255/0*bjcct-PTLBh0AdcE.jpg" /></figure><p>Transaction codes without preceding parameters can only be entered in the initial screen of the SAP Easy Access menu. If you’re already in another transaction, you must enter a parameter in addition to the transaction code.</p><p>You can show or hide the command field by clicking the triangle.</p><p>The following table lists the most important parameters:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/629/0*PVYPRuai0cKQRJIU.jpg" /></figure><p>To describe the navigation via transaction codes in more detail, let’s work through an example in the system. You ultimately want to determine the line items of your customers (debtors) for the current day in company code 1000. Follow these steps:</p><p>1. Log on to the SAP system.</p><p>2. In the SAP Easy Access menu, open the customer line item list via the menu path, <strong>Accounting &gt; Financial Accounting &gt; Accounts Receivable &gt; Account</strong> (see the figure below). Alternatively, you can enter Transaction “<strong>FBL5N</strong>” directly via the command field.</p><p>3. Under <strong>Account</strong>, you can find <strong>FBL5N Display/Change Line Items</strong>. A building block icon displayed in front of the transaction means that it can be executed. Double-click the “box” button, and the initial screen of Transaction FBL5N opens.</p><p>4. Enter the following information:</p><ul><li><strong>Company code</strong>: “1000”</li><li><strong>Open at key date</strong>: Current date (DD.MM.YYYY)</li></ul><p>Click the <strong>Execute</strong> button or press (F8).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/258/0*BjN9bZMuD1rSKiur.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/633/0*yUwzwkBPK39buaCp.jpg" /></figure><p>5. Now the system shows the line item list in which you can view which sales were made to the respective customer (see below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/0*kd9KmWXuKrhnWbcZ.jpg" /></figure><p>6. Click the <strong>Close</strong> button to close the customer line item list. The system takes you back to the SAP Easy Access menu.</p><p>The transaction code is displayed in the SAP Easy Access menu and also in the status bar at the bottom-right of the screen.</p><p>You should now have a better understanding for how to more easily navigate through your SAP system!</p><p>Excerpt from the book <a href="https://www.sap-press.com/using-sap_4155/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=1404"><em>Using SAP: An Introduction for Beginners and Business Users</em></a> by Olaf Schulz. Used with permission of SAP PRESS. All rights reserved.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Sign up for <a href="https://www.sap-press.com/newsletter/subscribe/?utm_source=medium.com&amp;utm_medium=contentmarketing&amp;utm_campaign=Blogs&amp;utm_content=newsletters">SAP PRESS newsletters</a> to get even more SAP tips and tricks delivered to you monthly!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fce6954%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fce6954%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href">https://medium.com/media/bc3f50e35313bac26beca821bee82a2d/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5eb25eeef6ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>