<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SAP Archive - Pixelfriedhof</title>
	<atom:link href="https://pixelfriedhof.com/en/tag/sap-en/feed/" rel="self" type="application/rss+xml" />
	<link>https://pixelfriedhof.com/en/tag/sap-en/</link>
	<description>IT-Blog, Fotoblog, Travelblog, Nerdstuff</description>
	<lastBuildDate>Tue, 04 Feb 2020 13:18:43 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.3</generator>

<image>
	<url>https://pixelfriedhof.com/wp-content/uploads/2022/02/cropped-My-project-3-32x32.png</url>
	<title>SAP Archive - Pixelfriedhof</title>
	<link>https://pixelfriedhof.com/en/tag/sap-en/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Activate HRFORMS after Patch (if no authorization exists, activate by report)</title>
		<link>https://pixelfriedhof.com/en/activate-hrforms-after-patch-if-no-authorization-exists-activate-by-report/</link>
					<comments>https://pixelfriedhof.com/en/activate-hrforms-after-patch-if-no-authorization-exists-activate-by-report/#respond</comments>
		
		<dc:creator><![CDATA[megaadmin]]></dc:creator>
		<pubDate>Wed, 20 Mar 2019 18:18:15 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[HRFORMS]]></category>
		<category><![CDATA[SAP]]></category>
		<category><![CDATA[SAP HCM]]></category>
		<guid isPermaLink="false">http://pixelfriedhof.com/?p=209</guid>

					<description><![CDATA[<p>If you want to start HRFORMS in payroll accounting after a patch or release upgrade, you may experience the following error as soon as you call up the print output of the remuneration statement.</p>
<p>Runtime error OBJECTS_OBJREF_NOT_ASSIGNED<br />Exception CX_SY_REF_IS_INITIAL</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/activate-hrforms-after-patch-if-no-authorization-exists-activate-by-report/">Activate HRFORMS after Patch (if no authorization exists, activate by report)</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>If you want to start HRFORMS in payroll accounting after a patch or release upgrade, you may experience the following error as soon as you call up the print output of the remuneration statement.</p>
<p>Runtime error OBJECTS_OBJREF_NOT_ASSIGNED<br />
Exception CX_SY_REF_IS_INITIAL</p>
<p>ABAP Programm CL_INFOSTAR_HRF02=============CP<br />
Exception CX_SY_REF_IS_INITIAL</p>
<p>The reason for this is that the HRFORMS used are probably not yet activated, even if they are already activated in the system according to the display.</p>
<p>To activate HRFORMS, we use transaction HRFORMS.</p>
<p>If the form is already active in the list, we choose the menu path &#8220;Utilities / Activate forms&#8221;.<br />
If the form is still inactive in the list, we select the required form and choose the menu path &#8220;Form / Activate&#8221;.</p>
<p>Bypass missing authorization to activate HRFORMS<br />
If you do not have authorization to activate HRFORMS using the transaction of the same name, you can also activate it using TX SA38 -&gt; HR99HRF_GENERATE.</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/activate-hrforms-after-patch-if-no-authorization-exists-activate-by-report/">Activate HRFORMS after Patch (if no authorization exists, activate by report)</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://pixelfriedhof.com/en/activate-hrforms-after-patch-if-no-authorization-exists-activate-by-report/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>SAP: Determining the Host Name and IP Address of an SAP Server Using a Transaction</title>
		<link>https://pixelfriedhof.com/en/sap-determining-the-host-name-and-ip-address-of-an-sap-server-using-a-transaction/</link>
					<comments>https://pixelfriedhof.com/en/sap-determining-the-host-name-and-ip-address-of-an-sap-server-using-a-transaction/#comments</comments>
		
		<dc:creator><![CDATA[megaadmin]]></dc:creator>
		<pubDate>Sat, 08 Sep 2018 11:50:05 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[SAP]]></category>
		<category><![CDATA[SAP CRM]]></category>
		<category><![CDATA[SAP HCM]]></category>
		<guid isPermaLink="false">http://pixelfriedhof.com/?p=169</guid>

					<description><![CDATA[<p>How can we quickly and reliably find out the host name and IP address of an SAP server via the SAPGUI?</p>
<p>&#160;</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/sap-determining-the-host-name-and-ip-address-of-an-sap-server-using-a-transaction/">SAP: Determining the Host Name and IP Address of an SAP Server Using a Transaction</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>How can we quickly and reliably find out the host name and IP address of an SAP server via the SAPGUI?</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Open the transaction &#8220;os01&#8221;.</p>
<p>Click on &#8220;Application server&#8221;.</p>
<p>The host name is now displayed. If the IP address is not yet displayed, also click on &#8220;Change View&#8221;. The IP address of the server should now be displayed behind the hostname.</p>
<p>&nbsp;</p>
<p><img fetchpriority="high" decoding="async" class=" size-full wp-image-707" src="http://pixelfriedhof.com/wp-content/uploads/2018/09/servernameandipaddress.PNG" alt="" width="515" height="257" srcset="https://pixelfriedhof.com/wp-content/uploads/2018/09/servernameandipaddress.PNG 515w, https://pixelfriedhof.com/wp-content/uploads/2018/09/servernameandipaddress-300x150.png 300w" sizes="(max-width: 515px) 100vw, 515px" /></p>
<p>&nbsp;</p>

<div class="aawp">

            
            
<div class="aawp-product aawp-product--horizontal"  data-aawp-product-asin="B01BJ0I18M" data-aawp-product-id="10648" data-aawp-tracking-id="daniel-net-21" data-aawp-product-title="[ SAP Administration - Practical Guide ] [By  author  Sebastian Schreckenbach] published on  April 2011">

    
    <div class="aawp-product__thumb">
        <a class="aawp-product__image-link"
           href="https://www.amazon.de/dp/B01BJ0I18M?tag=daniel-net-21&linkCode=ogi&th=1&psc=1" title="[(SAP Administration - Practical Guide)] [By (author) Sebastian Schreckenbach] published on (April, 2011)" rel="nofollow noopener sponsored" target="_blank">
            <img decoding="async" class="aawp-product__image" src="https://pixelfriedhof.com/wp-content/plugins/aawp/public/image.php?url=YUhSMGNITTZMeTl0TG0xbFpHbGhMV0Z0WVhwdmJpNWpiMjB2YVcxaFoyVnpMMGt2TkRGUVNXbGxhM0IwV1V3dVgxTk1NVFl3WHk1cWNHYz18MTc2Mzc4NzQxMA=" alt="[(SAP Administration - Practical Guide)] [By (author) Sebastian Schreckenbach] published on (April, 2011)"  />
        </a>

            </div>

    <div class="aawp-product__content">
        <a class="aawp-product__title" href="https://www.amazon.de/dp/B01BJ0I18M?tag=daniel-net-21&linkCode=ogi&th=1&psc=1" title="[(SAP Administration - Practical Guide)] [By (author) Sebastian Schreckenbach] published on (April, 2011)" rel="nofollow noopener sponsored" target="_blank">
            [(SAP Administration - Practical Guide)] [By (author) Sebastian Schreckenbach] published on (April, 2011)*        </a>
        <div class="aawp-product__description">
            <ul><li>Sebastian Schreckenbach (Author)</li></ul>        </div>
    </div>

    <div class="aawp-product__footer">

        <div class="aawp-product__pricing">
            
                            <span class="aawp-product__price aawp-product__price--current">90,22 EUR</span>
            
                    </div>

                <a class="aawp-button aawp-button--buy aawp-button aawp-button--amazon aawp-button--icon aawp-button--icon-black" href="https://www.amazon.de/dp/B01BJ0I18M?tag=daniel-net-21&#038;linkCode=ogi&#038;th=1&#038;psc=1" title="Amazon" target="_blank" rel="nofollow noopener sponsored">Amazon</a>
            </div>

</div>

    
</div>

<p>&nbsp;</p>
<p>&nbsp;</p>
<p><span style="font-size: 8pt;">All the links in this text are Amazon Affiliate Links, and by clicking on an affiliate link I will earn a percentage of your subsequent Amazon purchases. However, this circumstance does not influence the background of my product recommendation. This product recommendation is independent, honest and sincere.&nbsp;</span></p>
<p><span style="font-size: 8pt;">Bei allen genannten Links handelt es sich um Amazon-Affiliate-Links. Durch einen Klick auf einen Affiliate-Link werde ich prozentual an Euren darauf folgenden Amazon-Einkäufen beteiligt. Dieser Umstand beeinflusst aber nicht die Hintergründe meiner Produktempfehlung. Diese Produktempfehlung erfolgt unabhängig, ehrlich und aufrichtig.</span></p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/sap-determining-the-host-name-and-ip-address-of-an-sap-server-using-a-transaction/">SAP: Determining the Host Name and IP Address of an SAP Server Using a Transaction</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://pixelfriedhof.com/en/sap-determining-the-host-name-and-ip-address-of-an-sap-server-using-a-transaction/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>SAP HCM: Error accessing holiday calendar  P2518</title>
		<link>https://pixelfriedhof.com/en/sap-hcm-error-accessing-holiday-calendar-p2518/</link>
					<comments>https://pixelfriedhof.com/en/sap-hcm-error-accessing-holiday-calendar-p2518/#respond</comments>
		
		<dc:creator><![CDATA[megaadmin]]></dc:creator>
		<pubDate>Sat, 25 Aug 2018 11:50:05 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[Holiday Calendar]]></category>
		<category><![CDATA[P2518]]></category>
		<category><![CDATA[SAP]]></category>
		<category><![CDATA[SAP HCM]]></category>
		<guid isPermaLink="false">http://pixelfriedhof.com/?p=165</guid>

					<description><![CDATA[<p>Solving "Error accessing holiday calendar on 20180901<br />Message number P2518<br />The function module HOLIDAY_CHECK_AND_GET_INFO returned an error"</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/sap-hcm-error-accessing-holiday-calendar-p2518/">SAP HCM: Error accessing holiday calendar  P2518</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Solving &#8220;Error accessing holiday calendar on 20180901<br />
Message number P2518<br />
The function module HOLIDAY_CHECK_AND_GET_INFO returned an error&#8221;</p>
<p><img decoding="async" class=" size-full wp-image-704" style="display: block; margin-left: auto; margin-right: auto;" src="http://pixelfriedhof.com/wp-content/uploads/2018/08/holiday_calender_p2518_1.png" alt="holiday calender p2518 1" width="580" height="185" srcset="https://pixelfriedhof.com/wp-content/uploads/2018/08/holiday_calender_p2518_1.png 810w, https://pixelfriedhof.com/wp-content/uploads/2018/08/holiday_calender_p2518_1-300x96.png 300w, https://pixelfriedhof.com/wp-content/uploads/2018/08/holiday_calender_p2518_1-768x246.png 768w" sizes="(max-width: 580px) 100vw, 580px" /></p>
<p>If you receive the above error when revaluating absences after changing or recreating and reassigning a holiday calendar, this may be due to the calendar buffer not being updated.</p>
<p>To do this, switch to TX SCAL.</p>
<p><img decoding="async" class=" size-full wp-image-705" style="display: block; margin-left: auto; margin-right: auto;" src="http://pixelfriedhof.com/wp-content/uploads/2018/08/holiday_calender_p2518_2.png" alt="holiday calender p2518 2" width="395" height="342" srcset="https://pixelfriedhof.com/wp-content/uploads/2018/08/holiday_calender_p2518_2.png 395w, https://pixelfriedhof.com/wp-content/uploads/2018/08/holiday_calender_p2518_2-300x260.png 300w" sizes="(max-width: 395px) 100vw, 395px" /></p>
<p>Select the relevant holiday calendar and click on &#8220;Update calendar buffer&#8221; in the &#8220;Extras&#8221; menu.</p>
<p><img loading="lazy" decoding="async" class=" size-full wp-image-706" style="display: block; margin-left: auto; margin-right: auto;" src="http://pixelfriedhof.com/wp-content/uploads/2018/08/holiday_calender_p2518_3.png" alt="holiday calender p2518 3" width="580" height="215" srcset="https://pixelfriedhof.com/wp-content/uploads/2018/08/holiday_calender_p2518_3.png 810w, https://pixelfriedhof.com/wp-content/uploads/2018/08/holiday_calender_p2518_3-300x111.png 300w, https://pixelfriedhof.com/wp-content/uploads/2018/08/holiday_calender_p2518_3-768x284.png 768w" sizes="auto, (max-width: 580px) 100vw, 580px" /></p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/sap-hcm-error-accessing-holiday-calendar-p2518/">SAP HCM: Error accessing holiday calendar  P2518</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://pixelfriedhof.com/en/sap-hcm-error-accessing-holiday-calendar-p2518/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Where to find the Tax Jurisdiction Code in SAP ERP BDoc in Structure Editor</title>
		<link>https://pixelfriedhof.com/en/where-to-find-the-tax-jurisdiction-code-in-sap-erp-bdoc-in-structure-editor/</link>
					<comments>https://pixelfriedhof.com/en/where-to-find-the-tax-jurisdiction-code-in-sap-erp-bdoc-in-structure-editor/#respond</comments>
		
		<dc:creator><![CDATA[megaadmin]]></dc:creator>
		<pubDate>Fri, 16 Feb 2018 16:56:12 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[BDoc]]></category>
		<category><![CDATA[BUPA_MAIN]]></category>
		<category><![CDATA[SAP]]></category>
		<category><![CDATA[SAP CRM]]></category>
		<category><![CDATA[SAP ERP]]></category>
		<category><![CDATA[SMW01]]></category>
		<guid isPermaLink="false">http://pixelfriedhof.com/?p=160</guid>

					<description><![CDATA[<p>If you want to check if SAP ERP is sending correct information about a customers tax jurisdiction, you can do so by looking at the single BDoc in TX SMW01.</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/where-to-find-the-tax-jurisdiction-code-in-sap-erp-bdoc-in-structure-editor/">Where to find the Tax Jurisdiction Code in SAP ERP BDoc in Structure Editor</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>If you want to check if SAP ERP is sending correct information about a customers tax jurisdiction, you can do so by looking at the single BDoc in TX SMW01.</p>
<p>&nbsp;</p>
<p>Open TX SMW01<br />View related BUPA_MAINs within the Queue &#8216;R3AR_CUST_MAIN*&#8217; by hitting the button &#8216;Show BDoc Message Ext. Data&#8217; (it&#8217;s the blue icon near the &#8216;show errors&#8217;-button).</p>
<p>Now select the list of PARTNER entries.</p>
<p>From the following list select the partners entry you want to check and click on &#8216;Single Entry&#8217; (Shift + F7).</p>
<p>Now open the following structure:</p>
<p>PARTNERS / CENTRAL_DATA / ADDRESS / ADDRESSES -&gt; Click on Entry-View</p>
<p>You will find the following segments relevant for determination of the customers tax jurisdiction codes:</p>
<p>COU, CO, REG and TAXJURCODE.</p>
<p>Following you see an example for the affected segments regarding a canadian customer based in the region &#8216;Alberta&#8217;:</p>
<p>COU: CA<br />CO: CA<br />REG: AB<br />TAXJURCODE: CAAB</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/where-to-find-the-tax-jurisdiction-code-in-sap-erp-bdoc-in-structure-editor/">Where to find the Tax Jurisdiction Code in SAP ERP BDoc in Structure Editor</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://pixelfriedhof.com/en/where-to-find-the-tax-jurisdiction-code-in-sap-erp-bdoc-in-structure-editor/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Most common SAP HCM transactions</title>
		<link>https://pixelfriedhof.com/en/most-common-sap-hcm-transactions/</link>
					<comments>https://pixelfriedhof.com/en/most-common-sap-hcm-transactions/#respond</comments>
		
		<dc:creator><![CDATA[megaadmin]]></dc:creator>
		<pubDate>Sun, 04 Feb 2018 10:52:32 +0000</pubDate>
				<category><![CDATA[IT relevant topics]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[SAP]]></category>
		<category><![CDATA[SAP HCM]]></category>
		<guid isPermaLink="false">http://pixelfriedhof.com/?p=1992</guid>

					<description><![CDATA[<p>The following table contains the most used and most important transactions for SAP HCM.</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/most-common-sap-hcm-transactions/">Most common SAP HCM transactions</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>The following table contains the most used and most important transactions for SAP HCM.</p>
<table style="border-collapse: collapse; width: 855px;" border="0" cellspacing="0" cellpadding="0">
<colgroup>
<col style="width: 130pt;" width="173">
<col style="width: 256pt;" span="2" width="341"> </colgroup>
<tbody>
<tr style="background-color: #d2cbcb;">
<td class="xl65" style="height: 16.5pt; width: 130pt;" width="173" height="22"><strong>TCODE</strong></td>
<td class="xl65" style="border-left: none; width: 256pt;" width="341"><strong>Description</strong></td>
<td class="xl65" style="border-left: none; width: 256pt;" width="341"><strong>Beschreibung</strong></td>
</tr>
<tr style="height: 15.75pt; background-color: #97b9ed;">
<td class="xl67" style="border-right: 0.5pt solid #3f3f3f; height: 15.75pt;" colspan="3" height="21"><strong>Administration</strong></td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; width: 130pt;" width="173" height="19"><strong>PA20</strong></td>
<td class="xl66" style="border-left: none; width: 256pt;" width="341">Display master data</td>
<td class="xl66" style="border-left: none; width: 256pt;" width="341">Personalstammdaten anzeigen</td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PA30</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Master data maintenance</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Personalstammdaten pflegen</td>
</tr>
<tr style="height: 14pt;">
<td class="xl66" style="height: 14pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PA40</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Personnel Actions</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Personalmaßnahmen durchführen</td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PM01</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Infotyope creations and Enhancements</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Infotypen und Erweiterungen anlegen</td>
</tr>
<tr style="height: 15pt; background-color: #97b9ed;">
<td class="xl70" style="border-right: 0.5pt solid #3f3f3f; height: 15pt; width: 642pt;" colspan="3" width="855" height="20"><strong>Zeitwirtschaft / Time management</strong></td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; width: 130pt;" width="173" height="19"><strong>PA51</strong></td>
<td class="xl66" style="border-left: none; width: 256pt;" width="341">Display time data</td>
<td class="xl66" style="border-left: none; width: 256pt;" width="341">Zeitdaten anzeigen</td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PA61</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Maintain time data</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Zeitdaten pflegen</td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PA71</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Fast Entry of Time Data</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Schnellerfassung Zeitdaten</td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PT40</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Time Management worklist</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Arbeitsvorrat Zeitwirtschaft</td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PT61</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Time statement</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Zeitnachweis</td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PT60</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Time accounting</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Zeitabrechnung</td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PTMW</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Time Manager&#8217;s Workplace</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Arbeitsplatz Personalzeitmanagement</td>
</tr>
<tr style="height: 15pt; background-color: #97b9ed;">
<td class="xl73" style="border-right: 0.5pt solid #3f3f3f; height: 15pt; width: 642pt;" colspan="3" width="855" height="20"><strong>Entgeltabrechnung / Payroll</strong></td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; width: 130pt;" width="173" height="19"><strong>PA03</strong></td>
<td class="xl66" style="border-left: none; width: 256pt;" width="341">Maintain payroll control record</td>
<td class="xl66" style="border-left: none; width: 256pt;" width="341">Abrechnungsverwaltungssatz pflegen</td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PU03</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Employee&#8217;s payroll status</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Abrechnungsstatus eines Mitarbeiters</td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PC00_M01_CEDT</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">salary statement</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Entgeltnachweis</td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PC00_M01_CALC_SIMU</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Simulation of payroll calculation</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Abrechnungssimulation</td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PC00_M01_CALC</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Start payroll calculation</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Abrechnung starten</td>
</tr>
<tr style="height: 15pt; background-color: #97b9ed;">
<td class="xl73" style="border-right: 0.5pt solid #3f3f3f; height: 15pt; width: 642pt;" colspan="3" width="855" height="20"><strong>Organisationsmanagement / Organisation management</strong></td>
</tr>
<tr style="height: 14.25pt;">
<td class="xl66" style="height: 14.25pt; width: 130pt;" width="173" height="19"><strong>PP01</strong></td>
<td class="xl66" style="border-left: none; width: 256pt;" width="341">Maintain object</td>
<td class="xl66" style="border-left: none; width: 256pt;" width="341">Organisationsobjekte pflegen</td>
</tr>
<tr style="height: 14pt;">
<td class="xl66" style="height: 14pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PP02</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Maintain plan data</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Plandaten pflegen</td>
</tr>
<tr style="height: 14pt;">
<td class="xl66" style="height: 14pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PO13</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Position maintenance &#8211; Expert mode</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Planstelle pflegen</td>
</tr>
<tr style="height: 14pt;">
<td class="xl66" style="height: 14pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PO10</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Org Unit maintenance &#8211; Expert Mode</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Organisationseinheit pflegen</td>
</tr>
<tr style="height: 14pt;">
<td class="xl66" style="height: 14pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PPOM</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Maintain organisation plan with graphical editor</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Organisationsstruktur im grafischen Editor pflegen</td>
</tr>
<tr style="height: 14pt;">
<td class="xl66" style="height: 14pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PPOSE</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Display organisation plan</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Organisation und Besetzung anzeigen</td>
</tr>
<tr style="height: 14pt;">
<td class="xl66" style="height: 14pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PPOME</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Maintain oranisation plan</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Organisation und Besetzung ändern</td>
</tr>
<tr style="height: 14pt;">
<td class="xl66" style="height: 14pt; border-top: none; width: 130pt;" width="173" height="19"><strong>PPCI</strong></td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">HRP Infotype Creation and Enhancement</td>
<td class="xl66" style="border-top: none; border-left: none; width: 256pt;" width="341">Infotypen und Erweiterungen anlegen</td>
</tr>
</tbody>
</table>
<p class="alert-message">Tipp: Für Anfänger im Bereich SAP HRM empfehle ich dieses Fachbuch:&nbsp;<a href="https://amzn.to/2BiKOKb">https://amzn.to/2BiKOKb</a></p>
<p class="alert-message">Tip: For beginners in SAP HRM I recommend this book:&nbsp;<a href="https://amzn.to/2BiKOKb">https://amzn.to/2BiKOKb</a></p>
<p><span style="font-size: 8pt;">All the links in this text are Amazon Affiliate Links, and by clicking on an affiliate link I will earn a percentage of your subsequent Amazon purchases. However, this circumstance does not influence the background of my product recommendation. This product recommendation is independent, honest and sincere.&nbsp;</span></p>
<p><span style="font-size: 8pt;">Bei allen genannten Links handelt es sich um Amazon-Affiliate-Links. Durch einen Klick auf einen Affiliate-Link werde ich prozentual an Euren darauf folgenden Amazon-Einkäufen beteiligt. Dieser Umstand beeinflusst aber nicht die Hintergründe meiner Produktempfehlung. Diese Produktempfehlung erfolgt unabhängig, ehrlich und aufrichtig.</span></p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/most-common-sap-hcm-transactions/">Most common SAP HCM transactions</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://pixelfriedhof.com/en/most-common-sap-hcm-transactions/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Name of the component for alternative Delivery address</title>
		<link>https://pixelfriedhof.com/en/name-of-the-component-for-alternative-delivery-address/</link>
					<comments>https://pixelfriedhof.com/en/name-of-the-component-for-alternative-delivery-address/#respond</comments>
		
		<dc:creator><![CDATA[megaadmin]]></dc:creator>
		<pubDate>Wed, 22 Mar 2017 15:35:19 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[CRM]]></category>
		<category><![CDATA[SAP]]></category>
		<category><![CDATA[SAP CRM]]></category>
		<category><![CDATA[WebUI]]></category>
		<guid isPermaLink="false">http://pixelfriedhof.com/?p=140</guid>

					<description><![CDATA[<p><span lang="EN-US">The WebUI dialog-window for choosing an alternate delivery address doesn&#8217;t allow us to have a look at the technical details. So it is hard to find out which component is responsible for the configuration of that dialog.</span></p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/name-of-the-component-for-alternative-delivery-address/">Name of the component for alternative Delivery address</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><span lang="EN-US">The WebUI dialog-window for choosing an alternate delivery address doesn’t allow us to have a look at the technical details. So it is hard to find out which component is responsible for the configuration of that dialog.</span></p>
<p>&nbsp;</p>
<p><img loading="lazy" decoding="async" class=" size-full wp-image-576" src="http://pixelfriedhof.com/wp-content/uploads/2017/03/image001.png" alt="image001" width="600" height="293"></p>
<p style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">The component „GS_SIMPLE_ADDR“ is responsible for the configuration of that dialog window with its views like “POSTALVIEW”.</p>
<p style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Besides being used for the alternative shipping address, the component is also used in the view for involved companies within the opportunity-management.</p>
<p style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Before customizing the component it should be copied to avoid interference with other system functions.</p>
<p>&nbsp;</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/name-of-the-component-for-alternative-delivery-address/">Name of the component for alternative Delivery address</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://pixelfriedhof.com/en/name-of-the-component-for-alternative-delivery-address/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>SAP CRM: Message &#8216;- CONTENT GENERATED AT RENDERING TIME -&#8216; when creating notes and invoking the editor</title>
		<link>https://pixelfriedhof.com/en/sap-crm-message-content-generated-at-rendering-time-when-creating-notes-and-invoking-the-editor/</link>
					<comments>https://pixelfriedhof.com/en/sap-crm-message-content-generated-at-rendering-time-when-creating-notes-and-invoking-the-editor/#respond</comments>
		
		<dc:creator><![CDATA[megaadmin]]></dc:creator>
		<pubDate>Wed, 22 Mar 2017 15:35:19 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[CRM]]></category>
		<category><![CDATA[Interaction Center]]></category>
		<category><![CDATA[SAP]]></category>
		<category><![CDATA[SAP CRM]]></category>
		<category><![CDATA[WebUI]]></category>
		<guid isPermaLink="false">http://pixelfriedhof.com/?p=150</guid>

					<description><![CDATA[<p>If the message '- CONTENT GENERATED AT RENDERING TIME -' appears instead of the usual editor input field when creating texts, for example as a note underneath a support ticket, check the following facts.</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/sap-crm-message-content-generated-at-rendering-time-when-creating-notes-and-invoking-the-editor/">SAP CRM: Message &#8216;- CONTENT GENERATED AT RENDERING TIME -&#8216; when creating notes and invoking the editor</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>If the message &#8216;- CONTENT GENERATED AT RENDERING TIME -&#8216; appears instead of the usual editor input field when creating texts, for example as a note underneath a support ticket, check the following facts.</p>
<p>&nbsp;</p>
<ul>
<li>Transaction SU01 &#8211; Has the user defined a language? If not, enter language.</li>
<li>Reset personalization of the Assignment Block in the WebUI, in which the notes or texts are displayed in tabular form.</li>
<li>Subsequently, log off the user system-wide and then log on again.</li>
</ul>
<p>The problem should now be fixed in new cases. Old cases (e. g. support tickets which were created or edited before the above mentioned correction) may continue to suffer from the problem.</p>
<p>&nbsp;</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/sap-crm-message-content-generated-at-rendering-time-when-creating-notes-and-invoking-the-editor/">SAP CRM: Message &#8216;- CONTENT GENERATED AT RENDERING TIME -&#8216; when creating notes and invoking the editor</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://pixelfriedhof.com/en/sap-crm-message-content-generated-at-rendering-time-when-creating-notes-and-invoking-the-editor/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to find out affected Component name of a transport  via GUID</title>
		<link>https://pixelfriedhof.com/en/how-to-find-out-affected-component-name-of-a-transport-via-guid/</link>
					<comments>https://pixelfriedhof.com/en/how-to-find-out-affected-component-name-of-a-transport-via-guid/#respond</comments>
		
		<dc:creator><![CDATA[megaadmin]]></dc:creator>
		<pubDate>Wed, 22 Mar 2017 15:19:06 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[CRM]]></category>
		<category><![CDATA[SAP]]></category>
		<category><![CDATA[SAP CRM]]></category>
		<category><![CDATA[WebUI]]></category>
		<guid isPermaLink="false">http://pixelfriedhof.com/?p=138</guid>

					<description><![CDATA[<p>Sometimes there are situations when you know that there was a change on a special Component, but you do not quite know which component specifically was affected.&#160;Such a situation can happen especially when a dialog window in WebUI doesn&#8217;t show technical information about itself. We can find out the affected component when using the transport GUIDs.</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/how-to-find-out-affected-component-name-of-a-transport-via-guid/">How to find out affected Component name of a transport  via GUID</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Sometimes there are situations when you know that there was a change on a special Component, but you do not quite know which component specifically was affected.&nbsp;Such a situation can happen especially when a dialog window in WebUI doesn’t show technical information about itself. We can find out the affected component when using the transport GUIDs.</p>
<p>&nbsp;</p>
<p>First we have a look in our Transport-Organization (Transaction SE10) and we open all nodes of our Customizing-Transport to which we want to find out the affected components.</p>
<p>On the bottom-most level of our tree we find the linked GUIDs. We copy them for later research:</p>
<p>&nbsp;</p>
<p><img loading="lazy" decoding="async" class=" size-full wp-image-576" src="http://pixelfriedhof.com/wp-content/uploads/2017/03/image001.png" alt="image001" width="600" height="139" srcset="https://pixelfriedhof.com/wp-content/uploads/2017/03/image001.png 734w, https://pixelfriedhof.com/wp-content/uploads/2017/03/image001-300x69.png 300w" sizes="auto, (max-width: 600px) 100vw, 600px" /></p>
<p>&nbsp;</p>
<p>Now we change to Table-View (Transaction SE16) of the table „BSPC_DL_XMLSTRX2“ an enter one of our GUIDs in field “CONTEXT_ID” and start the query:</p>
<p><img loading="lazy" decoding="async" class=" size-full wp-image-577" src="http://pixelfriedhof.com/wp-content/uploads/2017/03/image002.png" alt="image002" width="433" height="323" srcset="https://pixelfriedhof.com/wp-content/uploads/2017/03/image002.png 577w, https://pixelfriedhof.com/wp-content/uploads/2017/03/image002-300x224.png 300w" sizes="auto, (max-width: 433px) 100vw, 433px" /></p>
<p>&nbsp;</p>
<p>The following view shows information about all the affected components of that GUID:</p>
<p><img loading="lazy" decoding="async" class=" size-full wp-image-578" src="http://pixelfriedhof.com/wp-content/uploads/2017/03/image003.png" alt="image003" width="545" height="169" srcset="https://pixelfriedhof.com/wp-content/uploads/2017/03/image003.png 663w, https://pixelfriedhof.com/wp-content/uploads/2017/03/image003-300x93.png 300w" sizes="auto, (max-width: 545px) 100vw, 545px" /></p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/how-to-find-out-affected-component-name-of-a-transport-via-guid/">How to find out affected Component name of a transport  via GUID</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://pixelfriedhof.com/en/how-to-find-out-affected-component-name-of-a-transport-via-guid/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
