<?xml version="1.0" encoding="UTF-8" standalone="no"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:gd="http://schemas.google.com/g/2005" xmlns:georss="http://www.georss.org/georss" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-8071344831073090029</atom:id><lastBuildDate>Sat, 21 Mar 2026 19:41:26 +0000</lastBuildDate><category>Allocation</category><category>CO</category><category>CPIC</category><category>GA715</category><category>Help view prior</category><category>LIST_ILLEGAL_PAGE</category><category>ME51</category><category>Master data</category><category>Number Ranges</category><category>RKCORR01</category><category>SAP</category><category>SAPFAX.DLL</category><category>SAPLPD.EXE</category><category>SAPcomm</category><category>Service</category><category>T800</category><category>\</category><category>abap</category><category>account assignment</category><category>authorization</category><category>book</category><category>books</category><category>certification</category><category>controlling areas</category><category>download</category><category>free</category><category>help view</category><category>index series</category><category>javascript:void(0)</category><category>pdf</category><category>rapidshare</category><category>release strategy</category><category>submit</category><category>table</category><category>unknown</category><title>SAP OSS Notes</title><description>SAP OSS Notes are online documents published by SAP which cover modifications, product errors, upgrades, FAQ's and customizing notes.</description><link>http://sapossnotes.blogspot.com/</link><managingEditor>noreply@blogger.com (SAP'er)</managingEditor><generator>Blogger</generator><openSearch:totalResults>3401</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><language>en-us</language><itunes:explicit>no</itunes:explicit><itunes:keywords>OSS,NOTES,OSS,NOTES,SEARCH,OSS,NOTES,LOGIN,OSS,NOTES,IMPLEMENTATION,OSS,NOTES,WEBSITE,OSS,NOTES,LINK,OSS,NOTE,LINK,OSS,NOTES,IN,SAP,SAP,OSS,NOTES,SAP,OSS,NOTES,LINK,SAP,OSS,SAP,OSS,LOGIN,SAP,OSS,LOGIN,PAGE,SAP,OSS,NOTES,SEARCH,SAP,OSS,MESSAGE,SAP,OSS,ID</itunes:keywords><itunes:summary>This SAP OSS Notes site is the only online resource for all the SAP support notes available for SAP system users. These SAP OSS notes are nothing but patches or hotfix provided by SAP for critical problems.</itunes:summary><itunes:subtitle>SAP OSS Notes</itunes:subtitle><itunes:category text="Technology"><itunes:category text="Tech News"/></itunes:category><itunes:owner><itunes:email>sapossnotes@gmail.com</itunes:email></itunes:owner><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-2050633780080420804</guid><pubDate>Thu, 17 Nov 2011 15:42:00 +0000</pubDate><atom:updated>2011-11-17T21:13:10.558+05:30</atom:updated><title>SAP  Note 28869 - Printout of changes although field not print-relevant</title><atom:summary type="text">Symptom:When a field (item or header) is changed in a purchasing document, a   change message is generated although the field is non-print-relevant in  the case of changes. Other termsME90, ME22, ME52,  T166C, ME9F, ME9E, ME9L, ME9K, ME9A, ME22N, ME42,  purchase order,  inquiry, contract, scheduling agreement, outline agreement, schedule  lines, SAPFM06P, MEDRUCK Reason and PrerequisitesWhen  you</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28869-printout-of-changes.html</link><thr:total>5</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-8489121066512954817</guid><pubDate>Thu, 17 Nov 2011 15:42:00 +0000</pubDate><atom:updated>2011-11-17T21:12:54.634+05:30</atom:updated><title>SAP  Note 28866 - Error in logical database VFV</title><atom:summary type="text">Symptom:When entering manual invoice header conditions with GET KONV, no conditions are read for this billing document.   Cause and prerequisitesProgram error SolutionSee source code corrections</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28866-error-in-logical.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-3423568071147856229</guid><pubDate>Thu, 17 Nov 2011 15:42:00 +0000</pubDate><atom:updated>2011-11-17T21:12:39.897+05:30</atom:updated><title>SAP  Note 28865 - SAPF070: Output diffs for multiple currency accts</title><atom:summary type="text">Symptom:For accounts which are managed in several currencies or in foreign   currency, the output may be incomplete when there are differences: If  a difference occurs in the reconciliation currency (for example   company code currency), but not in the update currency, the update of  the update currency is missing. If differences occur  for more than one account, the output of the  account is </atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28865-sapf070-output-diffs-for_17.html</link><thr:total>1</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-6035429443416767124</guid><pubDate>Thu, 17 Nov 2011 15:42:00 +0000</pubDate><atom:updated>2011-11-17T21:12:19.417+05:30</atom:updated><title>SAP  Note 28862 - Cycle Output: too many spool files/ blank pages</title><atom:summary type="text">Symptom:After a cycle has run, you can print the result by means of Cycle  -&amp;gt;  Output -&amp;gt; Print all.  If the 'New spool request' field is  selected with  the subsequently requested print settings, a lot of small  spool files  are created instead of a large one. During print  formatting with 132  columns, a printing termination after the first  page is possible. Cause and prerequisitesProgram</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28862-cycle-output-too-many_17.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-8666406852148975274</guid><pubDate>Thu, 17 Nov 2011 15:41:00 +0000</pubDate><atom:updated>2011-11-17T21:12:02.680+05:30</atom:updated><title>SAP  Note 28860 - Work center hierarchy, graphic, no organization</title><atom:summary type="text">Symptom:The function ´vertical relationship´ does not work in the graphic   display of a work center hierarchy from transaction CR22 (change work  center hierarchy).Procedure: Activate the higher-level node --&amp;gt; Edit --&amp;gt; Allocate --&amp;gt; vertical: no system response. Cause and prerequisitesThe functionality is not linked. SolutionLink the functionality in the program code.Additional key words</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28860-work-center-hierarchy_17.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-2000599751010408008</guid><pubDate>Thu, 17 Nov 2011 15:41:00 +0000</pubDate><atom:updated>2011-11-17T21:11:46.778+05:30</atom:updated><title>SAP  Note 28858 - Message V1384 when creating cust.ind.requirements</title><atom:summary type="text">Symptom:When entering a customer independent requirement with transaction  MD81,  the sales unit is not determined. The stockkeeping unit is also  missing. Message V1384.   Cause and prerequisites SolutionThe following advance correction is possible as of 2.2B</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28858-message-v1384-when_17.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-7445047286238521054</guid><pubDate>Thu, 17 Nov 2011 15:39:00 +0000</pubDate><atom:updated>2011-11-17T21:11:31.883+05:30</atom:updated><title>SAP  Note 28857 - Message V1139 during withdrawal for sales order</title><atom:summary type="text">Symptom:Error message V1139 occurs during a goods movement for a sales document which was assigned to a WBS.   Cause and prerequisites SolutionThe WBS element is proposed from the sales document.Correct programs rvdirekt and lv45mu03.</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28857-message-v1139-during_17.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-1050394625265688469</guid><pubDate>Sat, 05 Nov 2011 15:54:00 +0000</pubDate><atom:updated>2011-11-05T21:25:12.593+05:30</atom:updated><title>SAP  Note 28854 - Deactivate update program in curr.transl.</title><atom:summary type="text">Symptom:This note describes how the update program can be deactivated in the   currency translation of the components FI-LC and FI GLX (FI-SL).This can be useful if DEADLOCK problems occur. Cause and prerequisites SolutionProgram correction.Additional key words  GC29, GWUL, OC91, GWUG, RGCUMR00, RGUUMR00, RGUUMR01SAPLGUWU DBIF_RSQL_SQL_ERROR UPDATE_TT_GLT2 GLT2 LGUWUF10ORA-00060</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28854-deactivate-update.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-5160418667834759467</guid><pubDate>Sat, 05 Nov 2011 15:54:00 +0000</pubDate><atom:updated>2011-11-05T21:24:54.491+05:30</atom:updated><title>SAP  Note 28857 - Message V1139 during withdrawal for sales order</title><atom:summary type="text">Symptom:Error message V1139 occurs during a goods movement for a sales document which was assigned to a WBS.   Cause and prerequisites SolutionThe WBS element is proposed from the sales document.Correct programs rvdirekt and lv45mu03.</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28857-message-v1139-during.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-5629849446780014092</guid><pubDate>Sat, 05 Nov 2011 15:54:00 +0000</pubDate><atom:updated>2011-11-05T21:24:39.734+05:30</atom:updated><title>SAP  Note 28858 - Message V1384 when creating cust.ind.requirements</title><atom:summary type="text">Symptom:When entering a customer independent requirement with transaction  MD81,  the sales unit is not determined. The stockkeeping unit is also  missing. Message V1384.   Cause and prerequisites SolutionThe following advance correction is possible as of 2.2B</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28858-message-v1384-when.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-7397263916087364883</guid><pubDate>Sat, 05 Nov 2011 15:54:00 +0000</pubDate><atom:updated>2011-11-05T21:24:26.291+05:30</atom:updated><title>SAP Note 28860 - Work center hierarchy, graphic, no organization</title><atom:summary type="text">Symptom:The function ´vertical relationship´ does not work in the graphic   display of a work center hierarchy from transaction CR22 (change work  center hierarchy).Procedure: Activate the higher-level node --&amp;gt; Edit --&amp;gt; Allocate --&amp;gt; vertical: no system response. Cause and prerequisitesThe functionality is not linked. SolutionLink the functionality in the program code.Additional key words</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28860-work-center-hierarchy.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-686939145981385605</guid><pubDate>Sat, 05 Nov 2011 15:53:00 +0000</pubDate><atom:updated>2011-11-05T21:24:11.947+05:30</atom:updated><title>SAP  Note 28852 - Services file</title><atom:summary type="text">Symptom:Services file not maintained correctly after installation in the Windows directory. Cause and prerequisitesWith  the installation of the frontend under Windows, a services file is   also generated. It is stored in the Windows directory but is not found   by Windows NT and other network systems under certain conditions.Windows  NT, for example, expects to find it in the WINNT\SYSTEM32\</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28852-services-file.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-7504381471694894997</guid><pubDate>Sat, 05 Nov 2011 15:53:00 +0000</pubDate><atom:updated>2011-11-05T21:23:53.497+05:30</atom:updated><title>SAP  Note 28862 - Cycle Output: too many spool files/ blank pages</title><atom:summary type="text">Symptom:After a cycle has run, you can print the result by means of Cycle  -&amp;gt;  Output -&amp;gt; Print all.  If the 'New spool request' field is  selected with  the subsequently requested print settings, a lot of small  spool files  are created instead of a large one. During print  formatting with 132  columns, a printing termination after the first  page is possible. Cause and prerequisitesProgram</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28862-cycle-output-too-many.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-298793832443778899</guid><pubDate>Sat, 05 Nov 2011 15:53:00 +0000</pubDate><atom:updated>2011-11-05T21:23:36.355+05:30</atom:updated><title>SAP  Note 28865 - SAPF070: Output diffs for multiple currency accts</title><atom:summary type="text">Symptom:For accounts which are managed in several currencies or in foreign   currency, the output may be incomplete when there are differences: If  a difference occurs in the reconciliation currency (for example   company code currency), but not in the update currency, the update of  the update currency is missing. If differences occur  for more than one account, the output of the  account is </atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28865-sapf070-output-diffs-for.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-8745794693882666788</guid><pubDate>Sat, 05 Nov 2011 15:50:00 +0000</pubDate><atom:updated>2011-11-05T21:23:08.028+05:30</atom:updated><title>SAP  Note 28850 - DBIF_RSQL_INVALID_REQUEST for &gt; 250 company codes</title><atom:summary type="text">Symptom:The runtime error DBIF_RSQL_INVALID_REQUEST occurs for reports which use the logical database SDF. Cause and prerequisitesPreconditions:  In the client, there are more than 250 company codes with  the same  chart of accounts that are to be edited by the report.Cause: The  logical database works with a range table, where a line is entered for  all selected company codes for each chart of </atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28850-dbifrsqlinvalidrequest.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-7710637429355872644</guid><pubDate>Thu, 03 Nov 2011 15:01:00 +0000</pubDate><atom:updated>2011-11-03T20:31:52.617+05:30</atom:updated><title>SAP Note 28845 - Sales summary: Incorrect performance measures</title><atom:summary type="text">Symptom:During transaction VC/2 Sales Summary, the value for the 1st customer  is  always output when calling several customers on the 3rd page  (statistics performance measures and last SD documents). Cause and prerequisitesApplication areas were not deleted. SolutionSee source code correctionsGenerate program SAPRV77S again afterwards.Additional key words  Sales support RVKUSTA1</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28845-sales-summary-incorrect.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-4575505979835961675</guid><pubDate>Thu, 03 Nov 2011 15:01:00 +0000</pubDate><atom:updated>2011-11-03T20:31:35.133+05:30</atom:updated><title>SAP Note 28844 - Parameters for sales document types</title><atom:summary type="text">Symptom:In the technical documentation, AAT is always displayed for the sales document type. However, it is not always used.   Cause and prerequisites SolutionThe documentation is being improved. The following is correct:Sales doc. type    ParameterInquiry            AFTQuotation          AGTOrder              AATScheduling agr.    LPTContract           KTTProduct proposal   AMT</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28844-parameters-for-sales.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-5462783747872521330</guid><pubDate>Thu, 03 Nov 2011 15:01:00 +0000</pubDate><atom:updated>2011-11-03T20:31:20.848+05:30</atom:updated><title>SAP  Note 28843 - DEC LPS17 printer definition</title><atom:summary type="text">Symptom:LPS17 setup and definition   Cause and prerequisites SolutionThe network laser printer LPS17 (DEC) is set up in the following way under R/3.1. The server software for DEC UNIX from the DEC Customer Service    must be installed.2. The client must be set up. (check xlpsrc)3. A queue must be set up, which should look like this:   (in the printcap file on the system on which the LPS client is</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28843-dec-lps17-printer.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-2436173356802784933</guid><pubDate>Thu, 03 Nov 2011 15:00:00 +0000</pubDate><atom:updated>2011-11-03T20:31:04.687+05:30</atom:updated><title>SAP  Note 28841 - "Material to be provided" ind. in costing</title><atom:summary type="text">Symptom:In the BOM item, you can specify whether the components are to be   provided by the customer or the vendor using the "material to be  provided" indicator.Consequently, the indicator has effects on MRP.These components will not always be calculated in costing.However, the indicator is not recognized in costing.The  "material to be provided" item is not excluded from costing because   the </atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28841-material-to-be-provided.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-6168206926199485415</guid><pubDate>Thu, 03 Nov 2011 15:00:00 +0000</pubDate><atom:updated>2011-11-03T20:30:47.252+05:30</atom:updated><title>SAP  Note 28838 - Create invoice: Termination message FF723</title><atom:summary type="text">Symptom:When posting an invoice, termination message FF723 occurs 'System  error:  internal error in table SALTAB'. A company code, in which a  second and third local currency is defined, was used. Cause and prerequisitesProgram error. SolutionInstall the following correction.Additional key words  MR01 MRHR MRHG CREATE_BSET_ITEM</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28838-create-invoice.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-1548018557380460071</guid><pubDate>Thu, 03 Nov 2011 15:00:00 +0000</pubDate><atom:updated>2011-11-03T20:30:33.206+05:30</atom:updated><title>SAP  Note 28834 - IP10/IP30(RISTRA20)/IW32 ext. operation on header</title><atom:summary type="text">Symptom:Maintenance calls with external operations do not create any purchase   requisitions. This results in various follow-up problems in order  processing. Cause and prerequisitesProgram error SolutionCorrected in 3.0BAdditional key words  External operation IW32, PM_Order, external processing, PReq</atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28834-ip10ip30ristra20iw32-ext.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-384680047876755515</guid><pubDate>Thu, 03 Nov 2011 14:59:00 +0000</pubDate><atom:updated>2011-11-03T20:30:15.953+05:30</atom:updated><title>SAP  Note 28833 - MR01: FF718 Tax code not mantained for jurisd.code</title><atom:summary type="text">Symptom:Key words: MR01, US,  taxes,  jurisdiction code.Error occurs in a number of cases:Case 11) Entering a vendor invoice.2) Enter tax code on vendor screen   but select tax code TAX-EXEMPT   Do not select "Calculate tax"3) Tax code and jurisdiction code are copied from the purchase   order.4) Simulate or post --&amp;gt; error   FF718 'Tax code is not maintained for jurisdiction code'.If you </atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28833-mr01-ff718-tax-code-not.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-3544157562504803424</guid><pubDate>Thu, 03 Nov 2011 14:59:00 +0000</pubDate><atom:updated>2011-11-03T20:29:52.850+05:30</atom:updated><title>SAP  Note 28827 - 3.0A Project Creation Blocked by TCJ01</title><atom:summary type="text">Symptom:Among the parameters that the user must maintain for project editing isthe length of the structure indicator.As long as there is no project, you can enter any length in the interval1-5 in table TCJ01.Once there is a project you can no longer change the indicator.In previous releases the system did not check whether a project alreadyexisted.   Cause and prerequisitesError in the coding </atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28827-30a-project-creation.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-522195866640097297</guid><pubDate>Thu, 03 Nov 2011 14:59:00 +0000</pubDate><atom:updated>2011-11-03T20:29:38.647+05:30</atom:updated><title>SAP  Note 28826 - MR01 BCD_ZERODIVIDE</title><atom:summary type="text">Symptom:Entry of an invoice for a purchase order (MR01, MRHR). Preconditions:   Goods-receipt-based invoice verification must be active; a new pricing   occurs during goods receipt and a GR reversal occurs. In this  constellation, a zero division occurs when entering the invoice.   Cause and prerequisitesProgram error SolutionCorrected in 3.0B. You can make the following advance correction by </atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28826-mr01-bcdzerodivide.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8071344831073090029.post-293851401239991255</guid><pubDate>Thu, 03 Nov 2011 14:55:00 +0000</pubDate><atom:updated>2011-11-03T20:25:17.911+05:30</atom:updated><title>SAP Note 28823 - SKAT not replaced on client 000 : upgrade from 2.2</title><atom:summary type="text">Symptom:The chart of account CAJP:The language text of CAJP in 'J' is not  replaced by upgrade. The table  SKAT with the key '000JCAJP' contains  still the data of rel.2.2x.The chart of account CAJP is completely changed in the rel. 3.0x and the relevant tables SKAT, SKA1 and SKB1 are inconsistence.The table CSKU with the key '000JCAJP' contains also the data of rel.2.2. Cause and </atom:summary><link>http://sapossnotes.blogspot.com/2011/11/sap-note-28823-skat-not-replaced-on.html</link><thr:total>0</thr:total><author>sapossnotes@gmail.com (Sneha)</author></item></channel></rss>