Snote + valid releases

hello,
I am facing SAPSQL_ARRAY_INSERT_DUPREC error msg, and I looked in snote and got this no. 632501
I have downloaded this snote, and can anyone lets me know how I can execute this snote ?
seconldly there is valid releases : 46b 46c and 470, I want to know do my system have to have this status inorder to execute this note ?
Regards,

Hi,
First you need to Download the Note from http://service.sap.com, After downloading goto SNOTE transaction code and Implement the same in the SAP System
Regards
Sudheer

Similar Messages

Message no. CZ160 - Select a valid release strategy - IS Retail

while assigning PR release strategy to site thru' "Determination of Release Strategy" under tcode WB02, i am getting following error message.
Select a valid release strategy
Message no. CZ160
Diagnosis
The release strategy 01 is not defined.
Procedure
List the permissible values using F4, and choose a valid release strategy.
FYI, i configured PR release strategy "01" with required config. requirements and checcked the same thru' simulation and it is working fine.

Hi,
Please follow the steps;
1. Create characteristics via tcode CT04
2. Create Class for class type 032. Via tcode CL02
3. Then go to SPRO -> MM -> Pur -> PR -> Release Procedure with Classification -> Set up procedure. create release group, rel obj, class 032.
Next, set up release codes followed by release indicator.
Then the release strategies.
4. go to tcode CL20N to assign the release group and release strategy to the class and class type.
5. SPRO -> MM -> Pur -> PR -> Release Procedure with Classification -> Set up procedure -> Check Release Strategies

Validation of SAP Note correction

Hi All,
I have a set of note corrections which are triggered when doing an upgrade of SAP 4.7 to ECC 6.0.
In the Note corrections it gave instructions about the code corrections in the Note.
In this description it gave list of Valid releases . Do we need to check the version of particular module in the source SAP system( SAP 4.7 ( if it exists in the list then we can go a head and apply the note to the upgrade system to get the effect in Target system (ECC 6.0))
Valid Releases
SAP R/3 PlugIn for SAP APO, SAP BBP, SAP BW, SAP CRM
         2003_1_31I
         2003_1_470
         2003_1_46C
         2003_1_46B
         2003_1_45B
         2003_1_40B
         2004_1_470
         2004_1_46C
         2004_1_46B
         2004_1_45B
         2004_1_40B
         2004_1_31I
         2004_1_500
Please let me know wether i can go a head and install all Sap note corrections which are encountered in upgrade or do i need to validate like this.
Please let me know the general pratice.
Cheers,
Reddy

Hi,
When you download a note through SNOTE the system determines whether the note is applicable to your system or not .
If applicable when you implement the note only those corrections that are meant for your system are applied the others are ignored , the system takes care of these.
Regards,
Sowmya.

Deployer Installation: Failed to validate Release Management Server for Team Foundation Server 2013

Attempting to install the deployer on a machine and getting the below error. Not sure what that means, out of turn error or what actually occurs at this step, validating release management server, during the configuration piece. The user,
that we set for the service was validated fine. The user is an service account in the TFS RM Server, is an admin on the local box as well.
I am able to get into the TFS RM Server through the client just fine. I can hit the TFS RM UI just fine as well.
Curious what would not allow the deployer to complete as mentioned below.
Any help is appreciated.
I, 2013/12/16, 14:46:26.521, Validated account to use as identity for Release Management Services.
I, 2013/12/16, 14:46:26.521, Validating Release Management Server for Team Foundation Server 2013...
E, 2013/12/16, 14:46:30.905, Received Exception : Microsoft.TeamFoundation.Release.CommonConfiguration.ConfigurationException: Failed to validate Release Management Server for Team Foundation Server 2013.
at Microsoft.TeamFoundation.Release.CommonConfiguration.DeployerConfigurationManager.ValidateServerUrl()
at Microsoft.TeamFoundation.Release.CommonConfiguration.DeployerConfigurationManager.ValidateAndConfigure(DeployerConfigUpdatePack updatePack, DelegateStatusUpdate statusListener)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
I, 2013/12/16, 14:46:30.905, Work completed for GetConfiguration() call : got out of turn error
E, 2013/12/16, 14:46:30.905, Failed to validate Release Management Server for Team Foundation Server 2013.

Hi Kpdn,
Thanks for your post.
All your participation and support are very important to build such harmonious/ pleasant / learning environment for MSDN community.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Purchase requisition release strategy

I want each purchase requisition should be created with valid release strategy. The problem presently is that if somebody puts wrong parametes (such as purchasing group, currency) the purchase requisition will not be applicable to release and the purchase order can be easily created. So in such cases there is no need to release purchase requisition which is not correct for business point.
Pls advise.

Hi Balaji
Ur need is appreciated but inorder for that to work we have to make sure that all the possible combinations exist in ur characteristics list which may not be possible all times.
So better way would be to check whether the characteristics combinations of ur class and the corresponding data of ur requisitions matches and trigger error msg if differs.
Ex: Plant and doc type be the characteristics used in ur class.
Check whether the PR has only the plants and doc types that is specified in ur release strategy and if no trigger error msg.
Try this using BAPI also. Get help from ur ABAPer.
Thx
Raja

Can't add release key C90

Apologies in advance if this issue has been covered.
Obtained release via email from TAC..uploaded and installed TCNC7.3.0.8cb420c
Diagnostics reports missing release key, click "add valid release key"
...field for adding release key nowhere to be seen...
What have missed?
Thanks in advance smart people.

I noticed you uploaded the non-encrypted version of TC7 software, is that the correct version that was previously installed?
You should be able to enter the release key using the API command below through either the web interface under Configuration > API or using SSH.
xCommand SystemUnit ReleaseKey Add
if that doesn't work, you can perform a software image swap to the other software image you upgraded from under Maintenance > System Recovery. Switching back to the other software image can atleast get you back online in the time being if adding the release key doesn't work.

ValidatorGroupSubscriber fails to refresh so validation is not graphically working

When a ValidatorGroupSubscriber is added to a view its react correctly at first VO instanciation/binding but does not "refresh" when the targetted VO is updated. This cause the validation to fail graphically (eg. there's no more red border shown while a field is erroneous)
You can easily reproduce the bug with the insync modular example :
1- launch insync shell
2- get at least two contacts in the search grid
3- double-click on the first
4- clear the firstname field (for example of a mandatory field) -> the field is "border red" decorated
5- set somehting inside the field -> the red border disapear OK
6- double-click on another contact from the grid
7- repeat operation 4 and see how the application react : -> no red border appears, VO's validation is still enabled and working (save button not enabled) but nothing appear at view level.
Going deeper in debug mode seems to indicate "watcher/linstener" from validator is not correctly affected while you change the VO.
Please confirm the bug and tell if this could be corrected/fixed/correct with workaround
Thx for all
PS:I've already post this in the dev forum... guess it' was not the right place to put it so I apologize if this seems to be "spam-like"

Thx for your reply Nicolas and don't bother you didn't take so much time
There's a small improvement in the validation library when I use it on my project :
1- With the previous validation release (1.12) I was selecting a Person A -> view was updated with Person A information (comming from a VO) based on the relative injected model (code behind style) . Then I was deleting mandatory info from a field -> validation magic opers then red border raises.
I was then selecting Person B (injected model was refering the new reference of VO - there's perhaps where troubles are comming from...) and the red border was still there. I change the field value (clear and fill again) -> nothing happened : red border still there. I should gone back previous selected Person A to fill again value and red border disapears. Switching again on Person B show no red border but clearing the mandatory field does not make the red border appearing anymore...
2- With the new version : Red border still there when I switch from invalid Person A to valid Person B but switching to Person A and filling the mandatory info then swtiching Person B and cleaning mandatory info makes red border appearing !
So it's better but unfortunatly not perfect.
I maybe make a mistake by setting the validation stuff based on a VO which is not IN the view but is IN the model injected in the view ???
But I'm following best practice pattern & code behind and I could not see why this should not work (it works for event/command/injection stuff but not for validation... sadly...)
So I'm sorry Nicolas. I hope I don't bother you and need some more help from you.
Cédric
PS : anyway many thanks for your previous help and it was fast enough to help me.
Still waiting for your news

ME31K release strategy

I've defined several release strategies for contract ageement. When I create a contract, if the system cannot determine a valid release strategy, I can crate a document without release strategy.
How can I make a control when saving the document (tcode ME31K, ME32K) to verify that a strategy release is always defined?
For purchase order (tcode ME21N, ME22N) i've found a badi that works correctly, but it doesn't control in ME31K.
thanks,
Marco

I've definied several release strategy (100) with many parameters (company code, value, plant, etc).
Even if only one of parameters is not satisfied, the document has none release strategy, and I don't have any message about this.
By standard system I must define a phantom release strategy, with all combination not covered by the real strategies.
thanks,
Marco

Release key

Hi
I have a release key for tcnc6.3.1 now i want to upgrade to tc6.3.1.
How to get the release key for tc 6.3.1 and will i get it free?
"This was originaly posted as a blog which was deleted"

What George has posted is slightly wrong. While software versions from TC6.1 onwards no longer require a specific release key, a device still needs to have a valid release key installed (for an one of the releases of software), and that key needs to be from the same software train (ie TC or TCNC) as the software you are installing.
Doing a search in these forums shows this question, or similar, has been asked a number of times before where the answer is:
If you have an active service contract on your device, you should contact Cisco TAC with your Endpoint Serial Number and service contract information and they will be able to assist in converting you from a TCNC to a TC licence/release key (assuming you're in a country that the TC software is allowed in).
Wayne
Please remember to rate responses and to mark your question as answered if appropriate.

Period 000000000 - No valid translation date to specify

Hello,
I set up currency conversion. When I execute the report I receive following warning:
"Period 000000000 - No valid translation date to specify"
That I can suppress the warning is clear.
For me it is not clear what the warning means. Everything what I set up looks fine.
In rrc2 the currency conversion is set up as following:
- Variable time reference: Start of calendar year.
- Object: 0CALYEAR
I have postings on yearly basis (no exact date is specified)
Any idea?

Note 671810 - Period 0000000 - hiding BRAIN 385
Note Language: English Version: 4 Validity: Valid from 20.10.2003
Summary
Symptom
The BRAIN 385 warning Period 0000000 - No valid translation date to specify
(&4) appears when you execute a query. You can use the following correction
to hide/suppress this warning.
To do this, go to transaction /nrsrt, select 'Messages', 'other' as a
query. You can now select the BRAIN 385 message here.
More Terms
Rrms, brain 385, brain385, rrc1, rrc2, rrc3, saplrsw0, saplrsw1, rsw0, rsw1
<b>Cause and Prerequisites</b>
This is caused by a delivery error/program error.
Solution
Import either the Support Package specified in the attachment or the
relevant correction instructions.
Header Data
Release Status: Released for Customer
Released on: 23.10.2003 08:36:16
Priority: Correction with low priority
Category: Program error
Main Component BW-BEX-OT-OLAP-CUR Translation of Currencies or Units
Valid Releases
Software Component Release From
Release
To Release and Following
SAP_BW 30 30B 30B
SAP_BW 310 310 310
Support Packages
Support Packages Release Package Name
SAP_BW 30B SAPKW30B17
SAP_BW 310 SAPKW31011
Related Notes
04.12.2007 Page 2 of 2
Note 671810 - Period 0000000 - hiding BRAIN 385
Number Short Text
1099976 BRAIN385 : Warning Period 0000000
Correction Instructions
Correction
Instructio
ns
Valid
from
Valid
to
Software
Component
Typ
e
Reference
Correction
Last
Changed
600470 30B 310 SAP_BW C J19K011477 21.10.2003 16:41:55
*) C Correction, B Pre-Implementation, A Post-Implementation, M Undetermined

SAP Note Nr. 683745

Hi SD Consultants,
Can someone explain me about SAP Note Nr. 683745. We applied this in 4.7 but now we are upgrading to ECC 6.0. Now we want to analyse if this note is required in ECC 6.0. I'm not sure if this is SD specific or FM specific. If someone can explain what this note does, that would be of great help.
SAP Note Nr. 683745                          03.10.2008           Page 1
     Number                   683745
     Version                  0014
     Processor                BALAJI
     Processing Status        In Process
     Implement. Status        Completely implemented
     Language                 EN
     Short Text               Utility programs for SD-FM integration
     Component                PSM-FM-UP-CM
     Long Text
     Symptom
     You discover that the net value in some sales orders does not agree with
     amounts in Funds Management (FM).
     Other terms
     VA01, VA02, VA03, Sales Distribution (SD)
     Reason and Prerequisites
     Reason: Inconsistency between SD and FM.
     Solution
     1. Create executable programs ZZ_CHECK_SDFM, ZZ_SIMULATE_VA02 and
        ZZ_CORRECT_DEL_SDFM under Financial Accounting (FI) in a customer
        development class beginning with Y or Z, with the titles:
        ZZ_CHECK_SDFM         Check of sales order inconsistencies in FM
        ZZ_SIMULATE_VA02      Update of sales orders in Funds Management
        ZZ_CORRECT_DEL_SDFM   FM correction of deleted sales order lines
        a) After you have saved and activated programs, you can take over
           text symbols in English from the programs as follows:
           - SE38 -> Text elements -> Change (CTRL+F1) -> Utilities ->
              Adjust -> Textsymbols -> Edit -> Insert text symbols.
     Alternatively, you can copy and paste the text from the following lines:
     Text symbols for program ZZ_CHECK_SDFM
     Sym Text                                                dLen mLen
     010 Doc. no.   Line                                       15 15
     011       Amount in SD          Amount in FM              40 40
     020   Line deleted in SD                                  18 18
     030 Net values of selected sales orders in FM are correct 53 53
     040 Missing line in FM                                    18 18
     Text symbols for program ZZ_SIMULATE_VA02
     Sym Text                                                dLen mLen
                                                                       Page 2
     010 SD order was updated.                                 21 30
     Text symbols for program ZZ_CORRECT_DEL_SDFM
     Sym Text                                                 dLen mLen
     010 Doc. no.   Item                                        15 16
     020 Amount in SD          Amount in FM                     34 34
     030 Line deleted in SD                                     18 18
     040 Net values of selected sales orders in FM are correct. 53 53
     050 AccAs AmTp Year FM Date    Period          Amount      49 49
     060 Correction is not possible with selected date.         46 46
     100 Date/period for corrections                            27 27
        b) Then choose the "Selection texts" tab and take all possible
           parameters from the dictionary by checking the "Dictionary ref."
           box.
     2. Now you can run ZZ_CHECK_SDFM to identify inconsistencies in SD-FM
        integration. The billing amounts are not considered by this program
        ZZ_CHECK_SDFM.
     3. To correct any inconsistencies found, you can access the sales order
        using transaction VA02.
        a) In the most cases, if you change and remove a change in VA02 and
           then
        b) save, it will correct FM amount.
        c) For larger numbers of incorrect sales orders, you can use program
           ZZ_SIMULATE_VA02. To run ZZ_SIMULATE_VA02 you will need to
           implement for EA-PS 1.10-2.00 the correction instructions
           0120031469-347128 or 0120031469-347129.
        d) You will need to change 2 methodes: TRANSACTION_INIT and
           SAVE_DOCUMENT using the transaction SE19 and implementation
           IM_BADI_SD_SALES_FM.
     4. Inconsistencies that cannot be corrected using VA02 or
        ZZ_SIMULATE_VA02 will be most likely where a sale order line item was
        deleted and the deletion was not recorded in FM. In such cases, you
        will notice the text: 'Line deleted in SD' in the log of
        ZZ_CHECK_SDFM. Such lines can be corrected with 3 ways:
        a) You need to create the deleted line again, save the sales order,
           and then delete the line again. This will only have the desired
           effect if sales order deletion is working correctly in FM. This
           manual correction has an advantage that Budgetary Ledger documents
           are created as well.
        b) The second way is required for sales order lines which were
           carried forward in FM to the next fiscal year and which are not
           possible to recreate again, because sales order does not exist or
           automatic line item numbering does not allow to type a certain
           number. In such case you will need to run program
           ZZ_CORRECT_DEL_SDFM in order to close the open amount in FM. If
           you use Budgetary Ledger (B/L), then you will need to run
                                                                       Page 3
           budgetary ledger reconciliation program RFFMFG_BL_CORR for
           corrected sales order document in order to create B/L document for
           the FM closing amount.
        c) The third way can be used only for sales orders, which were not
           carried forward yet. It is suitable for sales orders which were
           completely deleted in SD and the deletion was not recorded in FM.
           In such case you can delete FM line items using deletion program
           RFFMDLOI. If you have Period Based Encumbrance Tracking (PBET)
           active, you need to use the modified version, ZFFMDLOI, provided
           in note 577860. If you also use Budgetary Ledger (BL), this third
           way is not suitable for you unless you are experienced with B/L
           reversal program ZRFFMBLREVERSEDOC (provided by note 683707) and
           locating the B/L document based on the relation of fields
           FMIOI-TRANR and BKPF-XBLNR.
     Valid Releases
     IS-Public Sector
         462
     SAP R/3 Enterprise AddOn Public Sector
         110
         200
         500
     ISPSADIN - Merge IS-PS & DI
         10A
Thanks,
Rajbans

Hi ,
SAP note 1810084 - SAPBWNews NW BW 7.30 ABAP SP10
This note contains the SAPBWNews for ABAP Support Package 10 for BW release 7.3
It provides a list of all notes describing the corrections or enhancements in Support Package 10.This note will be updated when other notes are added.
To customers who power their BW with SAP HANA, SAP strongly recommends to apply the latest available SAP HANA revision.
AS there is no correction instruction in this note, this cannot be implemented using SNOTE.
You need to refer to all the SAP notes mentioned in this note and apply relevant notes.
Hope this helps.
Regards,
Deepak Kori

NOTE 1474956 Important ( TAX: Arizona Resident Voluntary Withholding)

Hi SAP,
We are HSUP level 23, and this NOTE which is prerequisite of TUB 182 is in HSUP 25. This note doesn't say much but to recomand implement HSUP 25.
Please let us know if this NOTE is mendatory for TUB 182 OR we need to apply HSUP 25
regards,
Saurabh

Hi,
We still need to apply TUB 182 in our system.
The prerequisite for TUB 182 is as mentioned in TUB 182 - 1482468 as below-
o Note 1479549 (TAX: Arizona Resident Tax Withholding Percentage)
o Note 1479550 (CONS: TAX: Arizona Resident Tax Withholding Percentage)
o Note 1474953 (TUB 181: Tax Update Bulletin for TaxFactory 8.0.)
o Note 1474956 (TAX: Arizona Resident Voluntary Withholding)
For the note- 1474956, the following instuction is mentioned-
Steps for Installation in Advance . Please follow the installation steps in the same sequence as described below:
1. Make sure that your system is listed in the Valid release and support package range section of this Note.
2. Install the correction instruction that is attached to this Note using the Note Assistant (SNOTE) transaction.
3. Apply TUB 182 (SAP Note 1482468).
4. Apply, at a minimum, cyclic 8.0.O of TaxFactory, a third-party application distributed by Business Software, Inc. (BSI).
My question is- we are at level HRSP 60423, and this note is released in HRSP level 60425, is this HRSP 60423 a valid release and support package range section for this note?
Saurabh Garg

CHANGE OVER FROM TAXINJ TO TAXINN

HI ALL ,
TAXINJ and TAXINN cannot co exist in the same system.
If you are talking about technical Upgrade, then I don't think this would be feasible since old Txn would have got posted with TAXINJ procedure with rates as defined in Tax codes and now after migration to TAXINN in same box, the system would pick value from Condition records.
Just check this basic point of feasibility before we go ahead and look for changes.
In SuN the change is for existing implementation, here at present they have R/3 4.7, and are now in the process of technical upgrade to ECC 6.00; TAXINN is required to be implemented in the upgraded version.
At present they are using around 129 pricing procedures, 25 sales org,220 tax codes in TAXINJ. Suzlon has 21 company codes, 219 plants and 1300 end users the whole nature of group activities results in use of all possible types of indirect taxes in India like VAT, CST, Excise, Service Tax etc...
i have tried to search on sap help, service market place and others but could not come across any document for the change over. However i will try again.
what are the things i need to take care before any implications busisneww point of view, what will be the status of open sales order and purchase orders, and splitting delivery docs. which are under process, what will be the cutoverstrategy.
need ur help and guidance, thanks in advance.
We are migrating from 4.7 to ECC 6.00 ( technical upgrade only), at the same time we will shift from TAXINJ to TAXINN,please let us know the steps requred to do this activity.
RELEASE NOTES OR OSSNOTES, ANY DOCUMENT STEP BY STEP IS REQUIRED asap.
CHEERS
SRI_CNU

Hi
Vasu Sri,
I got this document from some body might help u a bit.
Condition-Based Excise Determination in MM (New)
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the system can calculate excise duties
and sales tax in Materials Management (MM) using the standard condition technique.
SAP has enhanced the existing tax procedure, TAXINJ, so that it now supports formula-based
and condition-based excise determination. The R/3 System also comes with a new tax procedure,
TAXINN, which only handles condition-based excise determination.
Which Tax Procedure Must I Use?
Existing customers must continue to work using the same tax procedure.
If you switch to a new tax procedure, you cannot display any documents that you have already
posted using the old tax procedure.
If you have worked with formula-based excise determination in previous releases and wish to
continue, you do not have to do anything. However, if you wish to start using the
condition-based excise determination method, proceed as specified below.
We recommend that new customers use the condition-based excise determination and tax
procedure TAXINN.
<b>How Do the New Functions Work?</b>
First, customize the system in the activities listed below. Then, for each material, create one
condition record for each form of excise duty and sales tax that applies, and enter the tax code
for purchasing documents (see below) in every condition record.
When you come to create a purchase order, enter the tax code in each line item. The tax code
tells the system whether to look in the condition types for formula-based or condition-based
excise determination
To set up the new excise determination method, carry out the following activities:
IMG activity
What to do
Check Calculation Procedure
Existing customers: Adjust your tax procedure to
match the changes to TAXINJ. Steps 560-583 are new, as are 593-598.
New customers: Create a copy of TAXINN.
Select Tax Calculation Procedure
New customers only: Assign the copy of
TAXINN to India.
Maintain Excise Defaults
New customers only: Enter the condition type
that you use for countervailing duty.
Define Tax Code for Purchasing Documents
Define a tax code.
Assign Tax Code to Company Codes
Assign the tax code to the company codes that it
is relevant for.
Classify Condition Types
Specify which condition types you want to use
for condition-based excise determination.
Define Tax Accounts
Check which G/L accounts the various taxes will
be posted to. Define G/L accounts for the account keys used in the tax procedure
6 MM
Materialwirtschaft
16.1 Country Version India in Standard R/3 System
Verwendung
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), Country Version India is no longer
delivered as an add-on but as part of the standard R/3 System.
Integration of functions in the SAP Easy Access menu
The functions for withholding tax have been integrated into the SAP Easy Access menu, under
Accounting -> Financial Accounting -> Accounts Payable -> Withholding Tax ->
India and Accounting -> Financial Accounting -> Accounts Receivable -> Withholding
Tax -> India.
You can access all other functions using the area menu J1ILN, which you can call from the
SAP Easy Access screen using the transaction code J1ILN.
Country Version India Implementation Guide
The Country Version India Implementation Guide (IMG) has been integrated into the standard
Reference IMG (see Changes to Structures for Country Version India).
Release Notes
You can access release notes from previous add-on releases using the links below.
SAP Library Documentation
The SAP Library documentation for Country Version India is also delivered on the standard
SAP Library documentation CD (see below).
New and Changed Functions
For information about new and changed functions for Country Version India, see the other
release notes for this release.
Auswirkungen auf den Datenbestand
You do not need to change any data.
Auswirkungen auf das Customizing
IMG activity
What to do
Activate Country Version India for Specific Fiscal Years
Delete the entry ZIND and
create a new entry for IND.
Siehe auch
SAP Library -> Financials or Logistics -> Country Versions -> Asia-Pacific -> India.
Release Notes from Country Version India Add-On (FI)
Release Notes from Country Version India Add-On (SD)
SAP AG
1
SAP-System
Page 9
Release Notes from Country Version India Add-On (MM)
16.2 Condition-Based Tax Calculation (New)
Verwendung
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), a new method for calculating taxes
in Brazil is available, which makes use of the standard condition technique. Tax rates, tax laws,
and special indicators that influence whether tax line items are included in the nota fiscal are all
stored in the system as condition records. An additional tax calculation procedure, TAXBRC, is
delivered for this new method, in addition to the existing one for Brazil, TAXBRJ.
Auswirkungen auf den Datenbestand
You can continue to calculate taxes using the former method: when the system processes the tax
procedure assigned to the country (TAXBRJ), it calculates the taxes externally by calling
function module J_1BCALCULATE_TAXES. We do, however, recommend that you assign the
new procedure TAXBRC and use the condition-based tax calculation functions, as it enables you
to flexibly adapt the tax calculation logic to cover new legal requirements or special customer
needs.
You will need to migrate your existing tax rate table entries to condition records, which you
can do directly from the Tax Manager's Workplace described below. You can check all tables
and subsequently convert the entries, whereby the system generates condition records. After the
initial migration, each time you create or change a tax rate table entry, the system automatically
generates a condition record as needed.
Auswirkungen auf das Customizing
If you want to employ the new condition-based tax calculation, you need to activate it and
carry out all related Customizing activities, under Financial Accounting -> Financial
Accounting Global Settings -> Tax on Sales/Purchases -> Basic Settings -> Brazil
-> Condition-Based Tax Calculation, all of which are new:
o
Activate Condition-Based Tax Calculation
o
Map MM Tax Values to Nota Fiscal Fields
o
Map SD Tax Values to Nota Fiscal Fields
o
Map MM Tax Laws to Nota Fiscal Fields
o
Define Internal Codes for Tax Conditions
o
Assign Internal Codes for Tax Conditions to Condtion Types
o
Assign Tax Rate Tables to Condition Tables
In addition, you need to assign the new tax calculation procedure TAXBRC to the country in
Customizing, under Financial Accounting -> Financial Accounting Global Settings ->
Tax on Sales/Purchases -> Basic Settings -> Assign Country to Calculation Procedure.
A new Customizing tool called the Tax Manager's Workplace is available that enables you to
SAP AG
2
SAP-System
Page 10
make all tax-related settings for Brazil. You access it under the same path as above through
Tax on Sales/Purchases, then Calculation -> Settings for Tax Calculation in Brazil ->
Access Tax Manager's Workplace, or alternatively by entering transaction J1BTAX. You can
use the Tax Manager's Workplace regardless if you use condition-based tax calculation; it
simply brings all tax activities to a single transaction (only the Migration, Nota-Fiscal Mapping,
and Condition Mapping options under the Condition Setup pulldown menu are relevant only for
condition-based tax calculation).
16.3 Changes to Structures for Country Version India
Verwendung
As of SAP R/3 4.7, Country Version India is no longer delivered as an add-on, but forms part
of the standard system.
SAP has discontinued the Country Version India Implementation Guide (IMG) and has added its
activities have been added to the standard Reference IMG as follows:
Activities relating to withholding tax are now located in Customizing for Financial
Accounting (FI), under Financial Accounting Global Settings -> Withholding Tax.
Activities relating to excise duty and excise invoices are in Customizing for Logistics -
General, under Tax on Goods Movements -> India.
As far as the activities under Preparatory Activities are concerned, two of them (Activate
Country Version India for Accounting Interface and Activate Processes) are no longer
relevant and have been removed from the IMG entirely. The activity Execute Country
Installation Program is already included in the standard IMG under the name Localize Sample
Organizational Units. And the other two activities (Activate Country Version India for Specific
Fiscal Years and Activate Business Transaction Events) have been added to the standard IMG.
For information about other changes to the IMG relating to changes in the functions in Country
Version India, see the other release notes.
16.4 Release Notes from Country Version India Add-On (MM)
Verwendung
The Release Notes from Releases 3.0A and 4.0A of Country Version India for Materials
Managment (MM) are listed below. For more Release Notes, see the alias globalization in
SAPNet, and choose Media Center -> Country-Specific Documentation -> Country Version
India - Release Notes.
Release 3.0A
o
CENVAT Credit on Capital Goods After Budget 2000 (Changed)
o
Multiple Goods Receipts for Single Excise Invoices
SAP AG
3
SAP-System
Page 11
o
Enhancements to CVD Solution
o
Pricing Date Control in Excise
o
Order Price Unit in Excise
o
Alternate Assets MODVAT Capitalization
o
Enhancements for 57 F4
o
User Exits for Customer Validations
Release 4.0A
o
Procurement Transactions for Excise Invoices
o
New Transactions Based on User Roles for Incominng Excise Invoices
o
Capture Excise Invoices with Reference to Multiple POs for the Same Vendor
o
Capture Excise Invoice and Post CENVAT in a Single Step
o
Open Schedule Quantity Defaulted in Excise Capture for Scheduling Agreement
o
Accounting Document Simulation for CENVAT Postings
o
Rejection Codes for Excise Invoices
o
Single-Screen Transaction for All Excise-Related Entries
o
Stock Transfer Orders Through MM Route
o
Excise Invoices for Multiple Import Purchases
o
Customs Invoices Can Be Captured Using Logistics Invoice Verification and Conventional
Invoice Verification
o
Material Type at Line Item Level
o
Excise Invoice Capture Without PO
o
Excise Invoice Without PO - Capture and Post in a Single Step
o
Recalculation of Duty and Excise Defaults Restore Feature Available
o
Split of Nondeductible Taxes During Excise Invoice Capture
o
Error or Warning Messages Displayed at the Time of Saving
o
Reversal of Excise Duty
o
MIGO Solution Available as a Note 0408158 (Featuring All Functionalities as in MB01)
o
Excise Invoice Defaults in Excise Popup at Goods Receipt
o
Split Accounting Lines for CENVAT Posting
o
Authorization for Incoming Excise Invoices Extended
o
Authorization Available for Part I Entry at GR
o
Authorization Available for Register Update Transaction
o
User Exit Available for Incoming Excise Invoice Transaction for Defaulting Values
SAP AG
4
SAP-System
Page 12
o
User Exit Available for Incoming Excise Invoice Transaction Before Database Update
o
User Exit Available for Register Update for Validations on Fetched Records Based on
Selection Criteria
o
User Exit Available for Register Update of RGSUM Register
o
User Exit Available for Excise Invoice Create for Other Movements to Default the Excise
Details
o
Register Update Separately Handled for Receipts and Issues Based on Classification Code
o
Ship-From Vendor Can Be Defaulted and Captured in Incoming Excise Invoices for Other
Movements
o
Removal Time Can Be Captured in Excise Invoices for Other Movements
o
Field Selection of Incoming Excise Invoices
o
Transaction Code Customizing for Incoming Excise Invoices
o
Excise Group Setting for Part I Indicator for Blocked Stock, Stock Transfer Order, and
Consumption Stock
o
Multiple Goods Receipts and Multiple/Single Credit Settings Available at Excise Group
Level
o
Rejection Code Master Setting for Posting on Hold Is Available
o
Stock Transport Orders

The impairment is not recognised in the year of impairment!!!!

Hello Forum,
I make a impairment posting in yera 2007.
But the imaprments posted are accounted in year 2008 only.
Why is the imapirments posted in the year 2007, not recognized in the same year?
How can i configure such scenario?
Please guide me .......
Thanks
GS

Hi,
I think this is not a regular issue,
I think still Sap do not have any solution for it.We need to implement SORP to do the impairment
I am sending some OSS notes regarding SORP solution,
Note 1142467 - SORP - Statement of Recommended Practice
Legal Change in UK
The guidelines of the recommended practices have been published by CIPFA
(The accounting body for public sector). The SORP sets out the proper
accounting practices required for Statements of Accounts, by section 21(2)
of the Local Government Act.
More Terms
SORP - Statement of Recommended Practice
MHCA - Modified Historic Cost Accounting
Cause and Prerequisites
Legal change affecting local authorities. The SORP has guidelines on how
the councils are to value various items on the balance sheet. This request
deals specifically with fixed assets and includes all the relevant
scenarios for revaluing assets upwards and downwards.
Solution
The solution will describe the major tasks and the customizing steps needed
to be compliant with SORP.
Timelines are as follow:
Note release of necessary customizing activities for
ERP2004 for pilot customers: 22 of February
Note release of additional changes in the
system for ERP2004: 29 of February
Release for other versions: 14th of March
Header Data
Release Status: Released for Customer
Released on: 20.02.2008 09:37:45
Priority: Correction with high priority
Category: Legal change
Main Component FI-AA-AA-H Revaluation
Additional Components:
XX-CSC-GB Great Britain
Valid Releases
09.01.2009 Page 2 of 2
Note 1142467 - SORP - Statement of Recommended Practice
Software Component Release From
Release
To Release and Following
SAP_APPL 46C 46C 46C
SAP_APPL 470 470 470
SAP_APPL 500 500 500
SAP_APPL 600 600 600 X
09.01.2009 Page 1 of 3
Note 1156819 - SORP - Statement of Recommended Practice 2006/2007,UK,
FIAA
Note Language: English Version: 8 Validity: Valid from 22.05.2008
this is the second OSS NOTE 156819
Dear Customers,
Please DO NOT implement this note for SORP solution.
Please refer the OSS note 1144500 to implement the SORP solution.
For internal use:
More Terms
To release the CR for UK solution
Cause and Prerequisites
not intended for customer implementation.
Solution
For SORP solution, please refer the note 1144500
Released only for internal purpose.
Purpose: For testing in the 462, release.
Apply this Note and create the following system objects.
Create and activate the following objects:
1. Package
For releases ERP2004(ECC 5.00) and ERP2005(ECC 6.00):
Transaction code: SE80
Package Name : ID-FIAA-UK
Short Description : Asset Accounting localization - UK
Application Component : FI-LOC
Surrounding Package : ID-FI
Software Component : SAP_APPL
For releases 4.6C and 4.7 :
Transaction code: SE80
Package Name : ID-FIAA-UK
Short Description : Asset Accounting localization - UK
Application Component : FI
Surrounding Package : ID-FI
Software Component : SAP_APPL
2. Function Group
Transaction code: SE80
Page 6
Function Group Name : ID_FIAA_UK
09.01.2009 Page 2 of 3
Note 1156819 - SORP - Statement of Recommended Practice 2006/2007,UK,
FIAA
Package : ID-FIAA-UK
3. Data Element
Transaction code: SE11
Data Element : FLG_SORP_MHCA
Short Text : Activate SORP/MCHA Functions
Domain : XFELD
Package Name : ID-FIAA-UK
Field Label Length Field label
Short 10 SORP/MHCA
Medium 18 Activate SORP/MHCA
Long 20 Activate SORP/MHCA
4. Table
Transaction code: SE11
Table Name : IDFIAA_UK_SORP
Short Text : Activate SORP/MCHA Functions
Package : ID-FIAA-UK
Delivery Class : C
Table View Maintenance: Display/Maintenance Allowed
Field Key InitialValues DataElement
MANDT Y Y MANDT
BUKRS Y Y BUKRS
SORP_MHCA - - FLG_SORP_MHCA
Technical Settings
Data Class : APPL2
Size : 0
Buffering : ON (Fully Buffered)
5. Table Maintenance Generator
Transaction code: SE11
1. Open the table IDFIAA_UK_SORP in change mode.
2. Go to Utilities -> Table Maintenance Generator.
3. Create the table maintenance using the "Create" button:
Function group : ID_FIAA_UK
Package : ID-FIAA-UK
Maintenance Type : one step
Note: IMG changes will not be reflected until the Support Pack is
implemented. However, SM30 transaction can be used to maintain this
table, if the SP is not implemented.
6. Install the following correction instruction of this note:
Correction instruction number: 1001810, 1010333 only for 462 release.
Header Data
Release Status: Released for Customer
Released on: 05.06.2008 12:10:20
09.01.2009 Page 3 of 3
Note 1156819 - SORP - Statement of Recommended Practice 2006/2007,UK,
FIAA
Priority: Correction with medium priority
Category: Correction of Legal Function
Main Component XX-CSC-GB Great Britain
Additional Components:
FI-AA Asset Accounting
Valid Releases
Software Component Release From
Release
To Release and Following
SAP_APPL 46C 46C 46C
SAP_APPL 470 470 470
Support Packages
Support Packages Release Package Name
EA-APPL 110 SAPKGPAA28
EA-APPL 200 SAPKGPAB17
SAP_APPL 46C SAPKH46C57
SAP_APPL 46C SAPKH46C58
SAP_APPL 470 SAPKH47031
SAP_APPL 470 SAPKH47032
SAP_APPL 500 SAPKH50020
SAP_APPL 500 SAPKH50021
SAP_APPL 600 SAPKH60015
SAP_APPL 602 SAPKH60205
SAP_APPL 603 SAPKH60304
SAP_APPL 604 SAPKH60401
Correction Instructions
Correction
Instructio
ns
Valid
from
Valid
to
Software
Component
Typ
e
Reference
Correction
Last
Changed
1001810 46C 46C SAP_APPL C P9CK496292 06.05.2008 11:23:51
1018076 46C 46C SAP_APPL C P9CK497712 05.06.2008 13:06:54
*) C Correction, B Pre-Implementation, A Post-Implementation, M Undetermined
To solve this issue we need OSS note 1144500 but still SAP is working on it I think
If I get any solution I will contact you
Thank you
Ravinder

Error while creating document in cv01n

In cv01n while attaching excel,word etc.file,at the time of saving error massege given is document can not change.Please provide me solution

I have checked the img setting ,img setting is ok,still it gives program error as below,can you suggest me whether reccomndations can implemented or not.
Note 964021 -Update Task Fails When New Version Created
Note Language: English Version: 2 Validity: Valid from 07.11.2006
Summary
Symptom
Update task fails when a new version of an old document info record is
created using CV02n transaction.The system throws an update terminate
error.
More Terms
UPDATE TERMINATE, MESSAGE 26 178, CV200_DB_DOC_UPDATE, CV02N
Cause and Prerequisites
Program Error
Solution
Implement the note
Header Data
Release Status: Released for Customer
Released on: 07.11.2006 12:13:26
Priority: Correction with medium priority
Category: Program error
Main Component CA-DMS Document management
Valid Releases
Software Component Release From
Release
To Release and Following
SAP_APPL 500 500 500
SAP_APPL 600 600 600
Support Packages
Support Packages Release Package Name
SAP_APPL 500 SAPKH50016
SAP_APPL 600 SAPKH60008
Attributes
Attribute Value
SAP objects CV200_DB_DOC_UPDATE
Transaction codes CV02N,CV03N
Transaktionscodes - manuell CV02N,CV03N
SAP-Objekte - manuell CV200_DB_DOC_UPDATE
DownPort/UpPort-WF UpPort check done, symptom
repaired
Correction Instructions
19.06.2008 Page 1 of 2
Note 964021 -Update Task Fails When New Version Created
Correction
Instructio
ns
Valid
from
Valid
to
Software
Component
Typ
e
Reference
Correction
Last
Changed
518092 500 500 SAP_APPL C P6DK093226 07.11.2006 17:30:29
807328 600 600 SAP_APPL C P7DK042952 13.07.2006 14:50:41
*) C Correction, B Pre-Implementation, A Post-Implementation, M Undetermined
19.06.2008 Page 2 of 2

Snote + valid releases

Similar Messages

Maybe you are looking for