Need SAP Note Explanation

Hi Experts,
While up grading company db from SAP 8.8 to 9.0 PL10. I got 4 warning messages. I am having little confusion in two messages (SAP Notes: 1729457 and 1934378).
1) SAP Note 1729457 tells about inventory tracking. Need explanation how it impacts on stock and accounts (if we do/don't reconsile). And what is the role of consultant here in this stage.
2) SAP Note 1934378 tells about Fixed Asset. But there is nothing like fixed asset in company db nor depreciation. Please let me know what is role of consultant in this stage.
With Regards

Hi,
1. SAP Note 1729457
Reason:
The inventory taking process is changed in SAP Business One 9.0, and therefore the in-process inventory tracking records in SAP Business One 8.82 or earlier cannot be upgraded to SAP Business One 9.0 or later. When ongoing inventory tracking is identified, a warning message appears to warn you against potential loss of data and propose to finalize the counting prior to upgrade.
2. SAP Note 1934378
Reason:
If the warning message "Transaction created by the SAP Business One Fixed Asset AddOn for the current fiscal year have been detected” is displayed, it means that in company database, transaction actions are detected which need to be reversed according to the documentation prior to the upgrade.
This is general note for customer. In this case it may not be applicable for your upgrade.
Hope helpful.
Thanks & Regards,
Nagarajan

Similar Messages

Need SAP Note NUmber

Hi,
I need form24Q version 1.28 sap Note number. Anybody knows the SAP note no for that plz let me know
Regards,
Prasad

Dear Prasad,
The last note regarding this form I could find is note 1355062 New Form 17-as per the Income-tax (8th Amendment) rules 2009
Hope this help
Sarah

Need SAP not to clear off the payment in LockBox processing

HI,
In the case of the lockbox processing, we want that the system doews not clear off the invoice in case there is payment difference.
We want to take dicision on those payments manually.
Regards,
MCA

Hi,
You need to define the tolerances in OBA3 and OBXL.
Then the system will not clear off the invoices, instead it will post the ament on account, which you need to then post process.
Regards,
Gaurav

Need SAP notes for - Goods mvt field blank

Hi All,
While doing the cancellation using MIGO screen the field reason for movement (GRUND ) is not automatically copied. Any Notes available ?
Edited by: soyunee on Oct 13, 2009 9:48 AM

Hi,
Please check whether for the reversal movement type,Reason for Movements has been defined or not in OMJJ Tode
TCode OMJJ
Click Movement type
Enter mvt tyoe(say 102)
Click Reason for Movement and maintain if not maintained
Regards

SAP Note 1558066 needed !!

Hello Experts,
I am having a issue with WAD and i need SAP Note 1558066 in order to solve this issue. Can anyone help me for this note ? any sugession, any comments how to get this note ? Many many thanks in advance.. Please help.
Regards,
Sunil Patel

Hello,
This note contains manual instructions. Please follow this instructions (which are very easy). Let me know if you are having problems:
   1. Go to Transaction: SE16
   2. Enter the table name "RSZWMDITEM" and press enter.
   3. Enter the value for MDITEMNAME as "TARTITLE" and execute.
   4. If you find entries for TARTITLE,then please delete all these
   entries from the table.
   After this, please do the following:
   1. Open Web Application Designer.
   2. Go to Tools -> Settings -> Refresh Metadata -> OK
      Now close and restart the web application designer.
Best Regards,
Edward John

Need clarification on SAP notes

Hi,
I need information on SAP notes relation.
Suppose a note X says corrections are delivered in the attached correction instruction, then its enough if we implement that specific note X.
If we go to correction instruction then it may have several other notes, do we need to implement all those notes specified in correction instruction 1st and then implement main note or directly we can apply Main note X.
If we apply main note obvisoulsy all the notes within correction instructions will be implemented
Regards,
Ravi

Hi Ravi
Suppose a note X says corrections are delivered in the attached correction instruction, then its enough if we implement that specific note X.
=>Before implementing those correction verify whether that X note applicable to your system release. Also verify is any manual code correction instructed in that note.
If we go to correction instruction then it may have several other notes, do we need to implement all those notes specified in correction instruction 1st and then implement main note or directly we can apply Main note X.
=> Before implementing those correction verify whether that X note applicable to your system release or its already implemented in your system. All these Prerequisites need to implement before final correction.
If we apply main note obvisoulsy all the notes within correction instructions will be implemented.
=> No we need to implement Prerequisites notes before main notes.
Thank

Need the note for 632429 in sap basis

my friend working in sap bw server got an error where to see the sap note this number please reply

Hi,
You need to look in service.sap.com.
You'll need to have userid & pwd for this. Check with your basis consultant to provide one for you.
Check the note details for now.
Summary
Symptom
This note concerns additions to the system switch or component upgrade, and an ADD-ON component that existed before the upgrade.
It also refers to errors in the guide or problems during the upgrade that only occurred after the guide was created.
Other terms
Add-On, ADD_ON, ADDON, ADDON_INFO, PREPARE
R/3 Enterprise
Reason and Prerequisites
You want to perform a system switch or component upgrade and have already installed an add-on component in your system.
The ADDON_INFO PREPARE phase (in the 'initialization' PREPARE module) recognized this prerequisite and this composite SAP note was created as a result.
Use the list below to check if one or more of the add-ons in the list are installed in your system.
The attached note contains other important information you require for the system switch or component upgrade.
If your system contains an add-on of an SAP software partner, the upgrade will always refer you to this note. Contact the vendor of the partner add-ons to receive additional information about the upgrade, if necessary.
Solution
This note is updated on a regular basis;
obtain the latest version before you start the upgrade.
History (LIFO) 24.04.2007 AOFTOOLS 400_710
08.12.2006 AUTOID_INT
03.11.2006 DBM 600, DBMC 100
10.10.2006 RCX 600, FCX 600, DDS 600
27.09.2006 DMIS
04.08.2006 IS-M/AMC 200
14.07.2006 NRX 306_600, 305_500
12.07.2006 OSEM 500, RCXEM 500
05.07.2006 REBK01 250, REBKXL 100, REBKXL 470
30.06.2006 FINBASIS, SEM-BW
12.04.2006 AOFTOOLS 351, 400
13.03.2006 BANK-ALYZE
06.03.2006 EA-IPPE
02.03.2006 KJCHM 601
24.02.2006 BI_CONT 353, 702, 703
06.02.2006 OSEM 410, RCXEM 410
24.11.2005 IS-PS-XT 600
04.10.2005 ISREA 510
12.01.2005 SLL_PI, ST-PI 003C, ST-PI 2005_1
15.12.2004 ECC-DIMP 500, P3A V500
20.10.2004 C-CEE, HR-CEE
28.09.2004 SLL-LEG
24.06.2004 WP-PI, PI_BASIS
04.06.2004 LSOFE, ERECRUIT, WFMCORE
03.03.2004 ECC 500
16.07.2003 CSC-ABPL, HR-KR+CN
16.06.2003 BANK/CFM 463_20
16.06.2003 Release note
SAP ERP Central Component 600 (ECC 600) ADD-ON RELEASE NOTE
NRX 306_600 954621
IS-PS-XT 600 890090
KJCHM 601 921295
EA-IPPE 400 914554
REBK01 250 960415
RCX 600 973274
FCX 600 973273
DDS 600 973272
DBM 600 983872
DBMC 100 983872
SAP ERP Central Component 500 (ECC 500)
Note 700778 contains a constantly updated list of all add-ons that are integrated in ECC 500 - this note contains references to the add-on specific information for the upgrade.
ADD-ON RELEASE NOTE
NRX 305_500 924462
ISREA 510 882097
SCM_BASIS 410 753272, Section I
WP-PI 723189, 789554
C-CEE 105_500 574102
HR-CEE 105_500 776578
ECC-DIMP 500 717818
P3A V500 778122
SLL_PI 700779
ST-PI 003C 606041
ST-PI 2005_1 769519
MRSS 500 889961
EA-IPPE 300 914554
AUTOID_INT 884658, 738424
You use SCM 5.0.
ADD-ON RELEASE NOTE
OSEM 500 952165
RCXEM 500 952166
You use SCM 4.1.
ADD-ON RELEASE NOTE
OSEM 410 919794
RCXEM 410 922117
EA-IPPE 300 914554
Solution Manager 4.0
ADD-ON RELEASE NOTE
ST 310 892412
ST 320 892412
ST-SUP 310 892412
ST-SUP 320 892412
ST-SER 892412
TMWFLOW 320 892412
CPROJECTS 310_620 892412
ST-ICO 892412
Web Application Server 620
ADD-ON RELEASE NOTE
DMIS 2006_1_620 970534
DMIS_CNT 2006_1_620 970539
NetWeaver 2004
ADD-ON RELEASE NOTE
AOFTOOLS 351 736572
BI_CONT 353 774933
ERECRUIT 300 717803
DMIS 2006_1_640 970534
DMIS_CNT 2006_1_640 970539
LSOFE 300 718625
WFMCORE 110_640 718627
WP-PI 723189, 789554
SLL-LEG 300_640 754698
ST-PI 003C 606041
ST-PI 2005_1 769519
FINBASIS 300 718455
SEM-BW 400 718455
NetWeaver 2004s
ADD-ON RELEASE NOTE
AOFTOOLS 400 921103
BI_CONT 702 847019
BI_CONT 703 916834
BANK-ALYZE 50 920370
DMIS 2006_1_700 970534
DMIS_CNT 2006_1_700 970539
FINBASIS 600 852448
MDM_TECH 555_700 1024362
SEM-BW 600 852448
SLL-LEG 700 853060
SLL-LEG 710 970465
IS-M/AMC 200 965483
SAP NetWeaver 7.1 (AS ABAP)
ADD-ON RELEASE NOTE
AOFTOOLS 400 921103
R/3 Enterprise Extension Set 2.0 (R/3 47x200)
Note 625318 contains a constantly updated list of all add-ons contained in R/3 Enterprise 47x200 - this note contains references to the add-on-specific information for the upgrade.
ADD-ON RELEASE NOTE
BANK/CFM 463_20 352072, section II(8)
CSC-ABPL 606860, 159979, 640520
HR-KR+CN 159979, 549368, 535649, 351062
RBD see Note 625318
ST-PI 003C 606041
ST-PI 2005_1 769519
EA-IPPE 200 914554
Regards, Siva

Need alternative solution for SAP Note, kindly do needful

Dear Consultants,
Our client is not able to apply SAP NOTE (SAP NOTE :- 1850965) for the issue (http://scn.sap.com/thread/3517341)due to some technical problem, kindly suggest if any other way is there to solve this issue, please do needful.
Thanks & Regards,
Navesh

Dear Consultants,
Please do needful, I need your help.
Thanks & Regards,
Navesh

Can anyone give the details of SAP note 325525 .

Hai
Can anyone give the details of SAP note 325525 .
Thanks
Kumar

What exactly do you want. Is that just the explanation in the note: If so, here it is.
Summary
Symptom
WARNING: THIS NOTE HAS BEEN REPLACED. FOR MORE CURRENT AND MORE COMPREHENSIVE INFORMATION SEE NEW NOTE 886102.
You want to copy and or rename one or more systems (database or client copy). One or more of the systems is a BW system or is connected to a BW system.
Caution: This note only deals with problems that occur in the BW source system connections. Other problems that occur in the BW environment (indexes) are NOT dealt with. See URL http://www.service.sap.com/bw --> Services & Implementation --> System copy & Migration.
Other terms
BW, source system, OLTP, database copy, client copy, system infrastructure, transport system, connections, RFC connection, trfc, transfer structure, IDoc, ALE customizing, logical system name, system changeability, renaming systems, system copy
Solution
Several scenarios are possible in this environment. Find the scenario relevant to your situation below and execute the steps listed or read the note(s) specified:
Scenario 1) You do not want to copy a system but only want to rename one (changing a logical system name).
           Solution scenario 1): Execute Transaction BDLS both in the client to be renamed and in the connected BWs or BW source systems. To do this, see Notes 121163 and 369758.
           Check the RFC destinations in all connected BWs/BW source systems as described in Note 524554.
           Reactivate all partner agreements that carry the new logical system name after renaming.
Scenario 2) You want to copy the entire system infrastructure connected by the BW source system connections (that means the entire system group) by a database copy. SAP recommends this procedure for copying systems.
           Solution scenario 2):
If you want to rename one or more of the copied systems, then execute Transaction BDLS both in the client you wish to rename and in all the connected BW and BW source systems. See Note 121163.
                    Make sure that an RFC destination exists with the new logical name in every connected BW or BW source system.
                    Reactivate all partner agreements that carry the new logical system name after renaming.
Change the hosts in the appropriate RFC destinations so that they refer to the correct computer. For this, see Note 524554.
Scenario 3) You want to copy a single BW system of the group by database copy.
Scenario 3)a) You only want to exchange the hardware of your system but do not want to rename the system.
                     Solution scenario 3)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
Scenario 3)b) You want to keep the original system of the copy so that you have two systems after copying.
                     Solution scenario 3)b): See Note 184754.
Scenario 4) You want to copy a single source system of the group by database copy.
Scenario 4)a) You only want to exchange the hardware of your system but do not want to rename the system.
                     Solution scenario 4)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
Scenario 4)b) You want to keep the original system of the copy so that you have two systems after copying.
           Solution scenario 4)b): See Note 184322.
Scenario 5) You want to import a client copy in a source system.
           Solution scenario 5): See Note 325470.

Can you please explain sap note 817499

Hi All,
        Can anyone explain me the SAP note: 817499.
I'm getting a short dump when i'm using this part of code in the program RCNRW007 as per sap note.
start of note 817499: use memory only if needed
G_WORK_WO_MEMORY = 'X'.
EXPORT G_WORK_WO_MEMORY TO MEMORY ID 'G_WORK_WO_MEMORY'.
end of note 817499: use memory only if needed
                                                                                Information on where termination occurred :
                                                                                The termination occurred in the ABAP/4 program "RCNRW007 " in
"%_GET_ACT01".
The main program was "RCNRW007 ".
The termination occurred in line 135
of the source code of program "RCNRW007 " (when calling the editor 1350).
Source code extract
001050     T_PSMASTDATA1-SUBPR      = PRPS_R-SUBPR.
001060     APPEND T_PSMASTDATA1.
001070
001080   *      collect prps for conversion exit CJPN
001090     MOVE-CORRESPONDING PRPS_R TO T_PRPS.
001100     APPEND T_PRPS.
001110
001120   GET     AUFK.
001130     IF GD_PSMASTDATA-SEL_NW_MIN IS INITIAL OR
001140        GD_PSMASTDATA-SEL_NW_MIN > AUFK-AUFNR.
001150       GD_PSMASTDATA-SEL_NW_MIN = AUFK-AUFNR.
001160     ENDIF.
001170     IF GD_PSMASTDATA-SEL_NW_MAX < AUFK-AUFNR.
001180       GD_PSMASTDATA-SEL_NW_MAX = AUFK-AUFNR.
001190     ENDIF.
001200     MOVE-CORRESPONDING AUFK TO T_PSMASTDATA1.
001210     T_PSMASTDATA1-VERNA      = AUFK-USER2.
001220     T_PSMASTDATA1-OWAER      = AUFK-WAERS.
001230     T_PSMASTDATA1-AKOKR      = AUFK-KOKRS.
001240     T_PSMASTDATA1-AKSTL      = AUFK-AKSTL.
001250     T_PSMASTDATA1-FKOKR      = AUFK-KOKRS.
001260     T_PSMASTDATA1-FKSTL      = AUFK-KOSTV.
001270     APPEND T_PSMASTDATA1.
001280
001290   GET     ACT01.
001300     MOVE-CORRESPONDING ACT01 TO T_PSMASTDATA1.
001310     T_PSMASTDATA1-KTEXT      = ACT01-LTXA1.
001320     T_PSMASTDATA1-OWAER      = ACT01-WAERS.
001330     T_PSMASTDATA1-AKOKR      = ACT01-ANFKOKRS.
001340     T_PSMASTDATA1-AKSTL      = ACT01-ANFKO.
>     APPEND T_PSMASTDATA1.
Regards,
Nikhil.

Hi Raja,
detailed explanation is already available over help.sap.com.
For your ready reference check below links
http://help.sap.com/saphelp_spm21_bw/helpdata/en/57/898009a859493a8bce56caaf0f8e13/frameset.htm
http://help.sap.com/saphelp_webas610/helpdata/en/da/11df3a9b10355ae10000000a11405a/frameset.htm
http://help.sap.com/saphelp_snc70/helpdata/en/3f/7ffb40ef74f923e10000000a155106/frameset.htm
Regards
Jitender

SAP System inconsistency for Inbound delivery / MIGO and a "sap note"

Hello Friends ,
After following SAP instruction on how to remove the inconsistency between posting GR through MIGO (Inv. mang.) and the reflection of the goods movement status in the inbound delivery document - done that using sap note 570991
the problem is that the system start behaving in a weird way throwing unjustified Error messages for any suggested goods receipt using MIGO with reference to inbound
for example after creating an inbound delivery document and trying to post it via migo , an error will pop up
- Inbound delivery storage location cannot be changed to here Message no. VLA316
the thing is i didn't even maintain any storage location entry up to that point and yet i cannot post any stock !!
also another error like
- Inbound delivery batch cannot be changed to *** here
which doesn't make any sense because there is not batches in the inbound document !!
i think this behavior is coming from the "Document Flow Update for Stock Postings" inbound indicator at the shipping parameter at client level customization
i need help on how to overcome this annoying SAP Bug/Problem specially i am in a post go live critical situation

Hi,
The messages you mentioned were introduced to avoid inconsistency between inbound delivery and IM, through the note: 1050944 - GR for inbound delivery using inventory mgmt as of ECC 6.00
If the messages are issued incorrectly, then you may check for SAP notes (I couldnt find anything relevant) or raise an OSS ticket to SAP.
Regards,
AKPT

What is the new sap note for Ptax slabs of FY 2011-12.

Dear Experts,
we are currently using ECC 6.0, release 604, patch level 0035 and support package SAPKE60435. professional tax slabs not updated in table V_T7INP4.
what is the new sap note for Ptax slabs of FY 2011-12.

Hi,
The Profession Tax tables T7INP3 & T7INP4 are customizing tables in which the entries are to be modified. SAP provides the initial entries and, if there is any change in slab rates, then you would need to update these slabs manually.
Please delimit the slab code in table T7INP3 and then create a new slab code entry from the date of delimition for the new rates in table T7INP4.
Regards,
Nishtha

Is it possible to force the implementation of a SAP note?

Hi guys,
I am installing SAP CPM, software components CPD 1.0 and PICM 1.0. During the SAINT installation, I hit an error for both components in the ABAP Generation Phase. I have found two notes with automatic corrections (1843317 and 2040519) to fix the errors.
However, when attempting to implement both notes through SNOTE, it shows them as "Cannot be implemented". I am assuming this is because the software components are not fully installed yet.
I know that I can get the correction instructions from each note and manually put them in, but one of the notes has 15+ corrections. Not exactly how I want to spend my day.
Is there a way to force SNOTE to implement a note that is listed as "cannot be implemented"? If not, does anyone have a better way to get the corrections applied besides doing each one manually?
Thanks!
-Jayson

Hi,
Here i would recommend to go for correction instruction instead of searching force implementation of SAP Notes as notes are used to fix bugs under some specific SAP standard codes and affects specific programs even and only recommended if support package still to be provided by SAP.
Also need to check for the supported releases under SAP notes for performing corrections (strictly based or relevant for mentioned releases.)
Hope you will understand and will try to avoid any issues by opting any force methods to implement the SAP Notes.
Regards,
Gaurav

Performance credit master data (FD32)--SAP Note 705317

Hi,
When running the FD32 tranasaction,I am changing the credit account and saving the transaction...it is taking quite a long time and going for dump....TIME_OUT error.
The appropriate notes for this problem are 705317 and 9937.
I shall give the details details of the note.
SymptomLong runtimes occur for the reorganization of credit data in SD documents.
This reorganization can occur in two situation:
- You start report RFDKLI20.
- You create or change credit master data in Transaction FD32.
Reason and PrerequisitesIn the credit management, you change assignments in Customizing or create or change
credit master data. The transfer of the changed settings into existing SD documents
requires a reorganization of these documents.
The reorganization is triggered from Transaction FD32 or using report RFDKLI20. Since
the relevant partner function in the credit management is the payer, all open sales
documents for a payer are selectedfor the reorganization.
The selection is performed within function module SD_CREDIT_RECREATE, which is called
from both Transaction FD32 and report RFDKLI20.
The documents are selected according to one of the two following options:1. Partner index VAKPA
The relevant documents are selected via partner index VAKPA. In index table VAKPA,
the system updates all SD documents for a customer number in dependency on the
partner function. All documents for a payer can be determined using index table
VAKPA.
CAUTION: Partner index VAKPA is only updated if the corresponding partner
functions and transactions are activated in Customizing table TINPA. Table TINPA
does not provide any update for the payer partnerfunction in the standard system!
2. Document table VBPA
If the update for the payer is not active in table TINPA, the relevant documents
are selected via application table VBPA. Table VBPA contains the used partners
(customer numbers) for SD documents.
The access to table VBPA with the customer number of the payer requires a long
SAP Note Nr. 705317 07.02.2008 Page 1
runtime because the customer number is not a key field in table VBPA. It might
result in a TIME_OUT.
Solution
Due to the technical conditions described above, there are two possible solutions for
runtime problems in Transaction FD32 or with report RFDKLI20:
1. Activate the update of index table VAKPA for the payer partner function:
Activate the update of index table VAKPA for the payer partner function by
creating an entry with transaction = 0, partner function = RG in table TINPA. You
can use Transaction SM31 for that.
Subsequently, a reorganization of index table VAKPA is absolutely required!! You
can execute the reorganization with report RVV05IVB. Note that all existing SD
documents thus also those ones already closed are indexed again by this report.
Depending on the number of your documents in the system, this can result in a
runtime which is correspondingly long. Therefore test this beforehand in a copy of
your production system!
2. Create a database secondary index for table VBPA:
If a reorganization of index table VAKPA is not possible or not wanted, you can
optimize the access via document table VBPA. For that, create a database secondary
index for table VBPA.
We cannot provide a general recommendation on how you have to define the secondary
index in detail. This basically depends on your dataset.
Use the SQL trace with Transaction ST05 in order to analyze the access onto table
VBPA within function module SD_CREDIT_RECREATE. Then define a suitable database
secondary index for table VBPA according to your analysis results.
For example, you could create the secondary index for VBPA fields KUNNR and PARVW.
Test the new secondary index by creating an SQL trace with Transaction ST05 again
in order to check the effectiveness of the database access and the runtime.
Also take the related notes into account.
Use Note 99937 to avoid the automatic reorganization - and thus runtime problems - in
Transaction FD32. Note that this does not solve the runtime problem during the
reorganization in general, but shifts it to RFDKLI20 which you can schedule as a job.
Thus, you are not disturbed by the runtime problem.
Please can anyone help me as to in which table and what fields i need to take to create secondary index.Thank you,
madhu.

Hi
Instead of creating Indexxes u contact basis to increase the the time limit for the execution
Regards
Shiva

ABAP dump in ECC 6.0 - Need OSS notes

ABAP dump is coming when retriving data between select-endselect.
Runtime Errors DBIF_RSQL_INVALID_CURSOR
Except. CX_SY_OPEN_SQL_DB
The problem cannot be resolved without correcting the application
program.
The statements MESSAGE, COMMIT WORK, ROLLBACK WORK, CALL SCREEN,
BREAK-POINT, WAIT, CALL FUNCTION ... DESTINATION, CALL FUNCTION ...
STARTING NEW TASK, RECEIVE RESULTS, CALL SELECTION-SCREEN, CALL
DIALOG, CALL TRANSACTION cannot be used within a database
loop.
You can collect the data needed for these statements together in an
internal table and process them
in a loop.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_RSQL_INVALID_CURSOR" "CX_SY_OPEN_SQL_DB"
Can you please give the OSS notes no. if anything is available.

Hi Sreedevi..
In the dump report, the piece of code where the dump occured will be shown
something with >>>>>> sign in the line...
Please copy and paste this peice of code..
Thanks and Best Regards,
Vikas Bittera.
**Reward if useful**

Need SAP Note Explanation

Similar Messages

Maybe you are looking for