Deactivation routine.

Like many people I use 3 machines to do my work.
Workstations at home and office...and a laptop for travel and incidental use.
The two activation limit is starting to cost me time.
I just had to leave my office and drive home to de-activate Muse on one machine so that I could activate it at my office.
I think I exhausted my maximum number of remote deactivations in a month?
While I would love a way to be able to use the products on 3 machines...and would wish for Adobe to grant this privelidge...
I am not holding my breath.
I would even be willing to pony up more money for that concession (something short of another 50 bucks a month hopefully).
It occurred to me to ask the user community what methods they are using to best deal with this limit.
Any suggestions as to how to best work with the Creative Cloud model...on 3 machines?
Should I be de-activating every time I finish a session?
Thanks.
M. Porter

Similar Messages

Routine-Active-deactive

Hi,
Here is a case where a developer has created a routine A,activated it and moved to QA(activated using RV80HGEN) and Production(for some reason business don't need this development so the same was not activated in Prod using RV80HGEN).
After that in Development the same routine was deactivated and deleted from Dev and QA but not in Production.So,now routine A is not available in Dev and QA but available in Prod in deactive state.
Now,a new routine B (for a different scenario) is created and moved to QA and Production.When RV80HGEN is executed it activated even the Previous routines ie Routine A.
If we move the request containing the deletion of routine A to Prod,the problem will be solved.
My question is when we are executing RV80HGEN can't we get an option to show a list of deactivated routines so that we can have an option to choose which one needs to be activated.
Kiran.

Hi Kiran,
sorry, this is not provided. Probably to ensure system consistency you can only activate all.
You should transport the request with the deletion to production as well. If it is already deleted from the input queue, STMS should be able to repeat the transport after appending it to import queue via menu Extras -> Other Requests > ADD.
Regards,
Clemens

Error while scheduling data collector: Error adding routine 'SAPTOOLS.DBH_FWK_CLEANUP' to task scheduler

Error Detail
Exception CX_DBA_ADBC in program RAGS_SISE_ACTIVITY_JOB line 0
Kernel Error ID:
WP ID: 23
WP PID: 28977
SYSID: CR5
SY-SUBRC: 0
SQL statement:
Database: CR5
caused by
Exception CX_SQL_EXCEPTION in class CL_SQL_STATEMENT
Kernel Error ID:
DB Error: Yes
SQL Code: 444-
SQL Message: SQL0444N Routine "*TASK_ADD" (specific name "SQL140704080729140") is implemented with code in library or path "...ib/function/SYSPROC.ADMIN_TASK_ADD", function "*" which cannot be accessed. Reason code: "4". SQLSTATE=42724 row=1
DB Object Exists: No
Duplicated Key: No
Internal Error: 1
Invalid Cursor: No
Unknown Connection: No
Connection Closed: No
System Detail:
Solman 7.1
ST    710    0010    SAPKITL710    SAP Solution Manager Tool
SAP_BASIS    702    0013    SAPKB70213    SAP Basis Component
Managed system:
SAP CRM ABAP 7.0
SAP_BASIS    701    0005    SAPKB70105    SAP Basis Component
SAP_ABA    701    0005    SAPKA70105    Cross-Application Component
PI_BASIS    701    0005    SAPK-70105INPIBASIS    Basis Plug-In
ST-PI    2008_1_700    0008    SAPKITLRD8    SAP Solution Tools Plug-In
CRMLOY    700    0005    SAPK-70005INCRMLOY    CRM Loyalty Management 700
SAP_BS_FND    701    0005    SAPK-70105INSAPBSFND    SAP Business Suite Foundation
SAP_BW    701    0005    SAPKW70105    SAP Business Warehouse
LCAPPS    2005_700    0007    SAPKIBHD07    LC Applications (LCAPPS) 2005_700
Database DB2
db2level
DB21085I Instance "db2cr5" uses "64" bits and DB2 code release "SQL09016" with
level identifier "01070107".
Informational tokens are "DB2 v9.1.0.6", "s081007", "U817474", and Fix Pack
"6".
Activity detail:
We are performing managed system configuration for CRM into Solman by using solman_setup transaction. While performing the Database Extractor Setup in step 8 we have observed above error.
Action take at our end:
1. Clean the LMDB and restart the configuration. - no luck
2. Upgrade the hostagent at CRM - No luck
3. Update the SLD for CRM entry - no luck
4. implemented SAP notes:
875986    Note Assistant: Important notes for SAP_BASIS up to 702
1246964    Note Assistant: Master language of notes incorrect
1262653    SPAU: New object is deleted after note is reset
1309424    DB6: DBA Cockpit Correction Collection SAP Basis 7.01 / 7.11
1335017    DB6:"Remove Redundant Restrictions" can return wrong results
1349277    Note Assistant: Method cannot be implemented
1365677    Note Assistant: Runtime error MOVE_CAST_ERROR during implmtn
1372652    DB6: Short dump when viewing diaglog due to NULL bytes
1373957    DB6: CX_SY_CONVERSION_OVERFLOW in new EXPLAIN
1376543    DB6: OPTIONS parameters for backup jobs in DB13
1378499    DB6: CLI error CLI0112E with "REORGCK_ALL" job
1379260    DB6: Add BW query name as comment to SQL statements
1379346    DB6: Scheduling of data collectors fails
1381179    DB6: Incorrect values for 'number of objects in tablespace'
1382634    DB6: Unable to create view 'SAPTOOLS.DBH_TABCLASS'
1382996    DB6: Update of DPW Back-End in Monitored DBs does not work
1384238    DB6: Defect scheduler on DB2 9.1 FP7/FP8 for LUW on Linux
1387022    DBA Cockpit: Month displayed incorrectly in DB13C
1387297    DB6: SQL-Fehler 901 during RUNSTATS and REORGCHK
1397709    Ignore Dynpro element fields AGLT and ADEZ in SNOTE/CWB
1398258    DB6: Job REORGCK_ALL places load on package cache
1400843    DB6: Incorrect display of key fields in EXPLAIN
1412719    SNOTE: error when implementing enhancement implementations
1413008    DB6: SQL0206N in function module DB6_PM_LOCKSNAP
1414624    DB6: Performance views if database monitors are deactivated
1414626    DB6: Incorrect display of file system sizes of containers
1415680    Note Assistant: Incorrect status in subsequent systems
1421157    DB6: SQL error 204 when accessing table DBSTATC
1425487    SE24: Error regarding READ-ONLY for complex attributes
1426092    DB6: Incorrect DROPPED TABLE clause for tablespaces
1426480    DB2: Incorrect display of registry values for DPF systems
1427030    DB6: Container specifications for tablespaces not changeable
1429082    DB6: No REORG after deactivating compression
1429687    DB6: SQL cache performance
1438168    DB6: REORGCHK recommendations for indexes are missing
1444373    DB6: Loading the package cache with monitor functions
1449482    DB6: Error message 'Command LIST_DB2DUMP failed'
1451958    DBA Cockpit: Incorrect start time for jobs
1452197    DB6: SQL error 100 in job REORGCK_ALL
1452502    DBA Cockpit: Jobs are missing in central planning calendar
1455897    DB6: Display of data classes is not updated
1456379    DB6: No display of indexes in data classes
1460895    DB6: SQL0104N during creation of WLM threshold
1462415    DB6: SQL -444 error messages in system log
1462855    DB6: Incorrect database name in HA environment
1464800    DB6: SQL Commands executes automatically on system change
1464858    DB6: COMPUTE_BCD_OVERFLOW during EXPLAIN Test Execute
1469515    DB6: Runtime error GETWA_NOT_ASSIGNED_RANGE in SAPLSDB6MON
1485313    DBA Cockpit: Incomplete system entries after SLD import
1486972    DB6: Parameters for DB/DBM configuration cannot be changed
1489968    DBA: DBA Cockpit WebDynpro does not care about HTTPURLLOC
1496515    DB6: SQL error 1428N when starting the DBA Cockpit
1501130    DB6: SQL error 802 in DB6_DIAG_COUNT_TABLE_ENTRIES
1508074    RZ20: 'Connection' attribute does not report alerts
1509121    DBA Cockpit: Endless loop occurs when starting DBA Cockpit
1511803    DB6: DB_TABLE_DATA_READ does not return data
1521525    DB6: Table display is not sorted
1522617    DB6: Availability of BW-specific functions in DBA Cockpit
1532114    DB6: Too many locks when collecting table history
1536787    DBA Cockpit: WebDynpro Explain - LOADDATA requires a model
1542311    DB6: Runtime error BCD_OVERFLOW in auto maintenance display
1546866    DB6: Runstats_DBSTATC interprets runtime param. incorrectly
1551729    DB6: Incorrect number of key fields in EXPLAIN
1552812    DB6: Use of db2sap functions
1559699    DB6: Missing data in SQL cache display
1559967    DB6: SQL error 206 when collecting the table history
1563327    DB6: SQL error SQL0551N when accessing SYSSTAT.TABLES
1568800    DB6: Error when deleting alert messages
1569592    DB6: SQL error SQL0433N in EXPLAIN
1569669    DB6: Incomplete history for performance data
1571365    DB6: SQL error SQL0443N in alert monitoring of DPF system
1576094    DB6: Database error SQL1751N in partitioning wizard
1597281    DB6: Incorrect compression displays for tables
1599764    DB6: SQL error 1428 when calling transaction SM50
1602403    DB6: No VOLATILE attribute after RUNSTATS or REORG job
1613270    DB6: Runtime error DYNPRO_FIELD_CONVERSION in DBA cockpit
1615698    DBA Cockpit: Incorrect date selection in DB13C
1619084    DBA Cockpit: Runtime err MESSAGE_TYPE_X when alert displayed
1619636    DBA Cockpit: Daily scheduling is not deleted
1624436    DBA Cockpit: Errors when accessing SHM area CL_DBA_SHM_AREA
1639631    DBA Cockpit: Failed schedulings in DB13
1720495    Invalid deimplementation of obsolete notes by Snote tool
Kindly suggest the correct solution to fix the issue.

Dear Deepak
Thanks for quick response.
Note 1462415 - DB6: SQL -444 error messages in system log ( SAP_BW 701 SP7 suggested)
This is already implemented and updated in my 1st message.
Note 978319 - DB6: Incorrectly cataloged table functions
This note can not be implemented due to version issue.
Kindly suggest some more hints on top of what I already did.
Regards
Bipin

Reg routines(ABAPER)

hi all
FORM routine_9998
TABLES DATA_PACKAGE TYPE tyt_SC_1_full
CHANGING
    ABORT          LIKE sy-subrc
RAISING
    cx_sy_arithmetic_error
    cx_sy_conversion_error.
Perform routine_9998
TABLES
    SOURCE_PACKAGE
CHANGING
    l_abort.
In inventory management , they r doing one transformation.
THEY r getting the following error., plz suuggest ur solution.
E:In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter
"SOURCE_PACKAGE" is incompatible with the formal parameter
"DATA_PACKAGE".
Regards
Karthik

Hi Ben,
My situation was that I had added some 'z' infoobjects to a Business Content DSO. When I activated this it naturally deactivated the transformation that linked this source DSO to a target InfoCube (thanks SAP). When I subsequently tried to reactivate the transformation I got a syntax error in the Start Routine.
To correct this I had to add my 'z' infoobjects to the appropriate definition in the Start Routine, which cured the syntax error and allowed me to activate the Transformation.
This is off the top of my head, but let me know if you need anything more.
Regards,
Andrew

Error in Sales Order Creation - Template material processing is deactivated

HI,
I am getting the following error in all clients in my server while creating the sales order. I am getting this after uploading the Patch 17,probably.
what should i do! All settings given by message below are tried, but not helping.
Template material processing is deactivated
Message no. CB01412
Diagnosis
You attempted to enter a material in an SD document that is set as a template or one-time material. An error occurred that can have the following causes:
Template and one-time material processing is not activated
No determination routine is specified for the SD documents for the permitted combinations
The combination of sales organization, document category, and document type or delivery type for the SD document is not permitted
System response
The system prevents you editing the document any further.
Procedure
Activate template and one-time material processing in the IMG activity Activate Dangerous Goods Checks.
Edit the determination routines in the IMG activity Specify Determination Routines for Sales and Shipping Documents.
Edit the IMG activities Specify Permitted Combinations for Sales Documents and
Specify Permitted Combinations for Shipping Documents.
Thanks in advance.

Hi,
Go to MM03 and check the material (you are creating sales order ) wheather sales views selected or not.
Regards,
Biju K

Requirement Routines & Mandatory Option for condition type

Hi All,
A tax condition type is being setup as mandatory in the pricing proecdure.
It has a requirement routine associated to it. If the requirement routine is not satisfied, sy-subrc is 4 and hence, no tax is calculated for it but mandaotry setting demnds it to have some value. In such situations, will it over-ride the config. setting of mandatory condition type & if not so, how can I over-ride. It is compulsory to have the mandatory option ticked but its ok to over-ride it for some conditions specifed in the requirement routine.
Please advice.
Thank you,
Shiv

Hi Shiv,
Any critial configuration related information is available in internal tables based on which standard SAP does validations. So mandatory property of the condition type as configured in the pricing procedure, would also be available in some internal table of KOMV (KOBLI is the field indicating whether it is mandatory or not)
So in your requirement routine you can code so as to make KOBLI blank whenever the tax condition type is being deactivated by setting SY-SUBRC to 4.
Please reward if helpful.
Regards,
KC

Problem with TFRM table active indicator in pricing routine RV80HGEN

Hi experts,
I have created few custom routines in VOFM tcode, and trasported to Q system.
In DEV in program RV61ANNN and in VOFM tcode, i can see the new includes and new routines.
But when i check in Q system in VOFM tcode the new routines are not available, nor in RV61ANNN program(new includes).
I have run the report RV80HGEN . But its not working.
I checked the table TFRM and the active field is blank for the group number and routine number.
But in DEV TFRM table has an X value in active field for that routine.
I dont know how to do it.
I can retransport the request again, but i dont know what all the objects needs to be created a new request. its risky.
Plz help me out on this.
I have checked OSS notes, even it says the same.nothing else.
Points are rewarded fully.
Thsnks,
KK

Hi,
The problem is with the active field blank in the test system. From OSS note 327220:
(02) Question/problem:
Even though report RV80HGEN was executed, the VOFM object is not registered in the object carrier. Why?
(02) Answer:
During the setup of the object carriers via RV80HGEN the system includes only VOFM objects which have set the 'active indicator' (refer to section 2.3.2). If the active indicator for the corresponding object is not set, the RV80HGEN does not process the VOFM object. Solution: Set the active indicator for the respective object and start the RV80HGEN again.
So I might suggest deactivating the object in development, transporting, then reactivating the object in development, and transporting again.
BR,
Tony.

Activation & Deactivation of Condition type in Sales order

Hi friends,
I have below requirement and need help on the same.
While creating or changing the sales order, if order qty is less than 5, we need to activate condition type 'ZD03' for pricing. if it is more than 5 it should be deactivated.
Kindly suggest on this.
Thanks in advance.
Regards,
Bharat.

Dear Bharat,
Did you try with VOFM ?
Visit the following link:
http://www.sap-img.com/sap-sd/quantity-based-discounts-in-bulk-quantities.htm (Routines and Pricing Procedure)
Hope this will help.
Regards,
Naveen.

Deactivation of Pricing Conditions at header level of Sales Order

Hello there,
We have used a routine in pricing procedure (BaseType Routine) to deactivate condition MWST in the MWST condition line in pricing procedure, transaction V/08.
In the routine, We played with the KINAK (set to K )and KOBLI (set to space) flags of structure KOMT1 and XKOMV and delete the MWST entry in the TOBLI table and succeeded to deactivate the MWST at item level of the sales order. (MWST condition appear in the conditions tab at item level as inactive)
We have created a sales order with only one item that has the MWST condition deactivated at item level.
But in the conditions at header level the MWST condition does not appear. Shouldn't the MWST condition appear at header level but deactivated (with a yellow triangle next to MWST)?
If yes is there a flag that we forgot to set?

Hi,
what is the table name you had mentioned
TOBLI is it correct?
Thanks
mano

Pricing Conditions deactivation at header level of Sales Order

Hello there,
We have used a routine in pricing procedure (BaseType Routine) to deactivate condition MWST in the MWST condition line in pricing procedure, transaction V/08.
In the routine, We played with the KINAK (set to K )and KOBLI (set to space) flags of structure KOMT1 and XKOMV and delete the MWST entry in the TOBLI table and succeeded to deactivate the MWST at item level of the sales order. (MWST condition appear in the conditions tab at item level as inactive)
We have created a sales order with only one item that has the MWST condition deactivated at item level.
But in the conditions at header level the MWST condition does not appear. Shouldn't the MWST condition appear at header level but deactivated (with a yellow triangle next to MWST)?
If yes is there a flag that we forgot to set?

Hi experts,
Has anyone done the above mentioned before, please reply...

Deactivation Impact of ISO Code and Vehicle country key

Hello All,
We have a requirement to use the BSEG-KIDNO in accounting document line item. This field has to do some calculation by using Validation exit. This calculation works fine except for certain countries like Sweden(SE), for which some standard function module is triggering. On further research we have found that by deactivating the country specific checks( Vehicle country key and ISO code) we can deactivate the standard function module and make our validation exit work. This can be acheived by making blank for "Vehicle Country Key" and ''ISO Codeu201D in OY01 (IMG--> General setting --> Set country --> Define country) for Sweden.
Could you please explain what will be the impact in other areas by deactivating ISO code and Vehicle country key in OY01.
Appreciate your reply.
Thanks in advance.
Prasad

Hi Prasad,
You should not remove them since
ISO
The entry is used in countries of the European Community to check the
VAT registration number (VAT reg.no.). You can store the VAT
registration number in the master record of a customer or vendor, or for
the company code.
The ISO code is used as the country key when exchanging information via
EDI. You must therefore specify the ISO code for each country in this
field if you use EDI.
The ISO code also controls which additional specifications are relevant
for a company code. You can always only enter the additional details
which are relevant for the company code country or for all countries.
The assignment to the country takes place via the ISO code.
Vehicle country key
    The vehicle country code is a standard key worldwide. It does not depend
    on the country in which the SAP System is installed.
    The key is therefore used as a basis for accessing country-specific
    check routines. Furthermore, it can also be used as a supplement to the
    postal code.
    This key should be specified for all entries in the country table.
Can you check the OY17 setting under the Further Checks Bank data check box for working Country and Sweden?
Reg
Vishnu

Error at the time of cond. type deactivation in tax code

Hi,
I m facing a problem,when I go through tcode FTXP and try to deactive a one condition types from here.
its showing below error:-
System error: Error in routine
CHANGE_CONDITION_MULTIPLE A003TXGST
anybody have the suggestion regarding this...

Hi,
If youu2019re maintaining tax rate in FTXP, then no need to deactivate the related condition type, just remove the tax rate, keep as blank in FTXP OR if you maintain tax rate in FV11 for condition type, you can delete by with tax combination in FV12.
But check other transaction already done before changing condition record for/ in tax code & not advisable for chnaging condition type with present tax code. If needed do not use the tax code & create a new tax code with your requirement with required condition type.
Regards,
Biju K

Update rules deactivated only has to open the system..

Hello Experts,
-- ODS and update rules are already in Production.
-- I have made changes to the ODS by adding new Infobjects.
-- activated the update rules.
-- When the ODS and update rules are transported. Update rules get deactivated
-- And a message 'Data target changed, suggestion for the update rules generated'
Detailed message:
Data target was changed. Suggestion for update rules generated
Message no. RSAU287
CAUSE&
The data target has been changed (for example, InfoObjects have been added or deleted).
System response
The update rules have been set to inactive.
Procedure
Check the proposal for the update rules: Newly added key figures or characteristics are updated directly using the source-InfoObject from the InfoSource if the InfoSource contains these InfoObjects. Otherwise, the calculation type is set to 'Routine'. Newly added key figures, data fields, or attributes are set to 'No Update'.
The rules for key figures and for characteristics must be checked and adjusted appropriately.
Detailed message end.........
-- Do not get activated by retransporting. or doing a fresh request of the update rules.
-- Currently the only I can see by opening the system and activating them. Wondering if we have any other alternatives to activate these update rules for the ODS
Any solutions:
-- Wondering if I am missing some procedure to transport.
-- Please feel free to post your views / suggestion in case you had a similar situation before.
Many thanks in advance,
BWer
Message was edited by: BWer

BWer,
If you collect your transport in a big lump of a single transport, the tranport connection may not organize it in the order of the proper dependency, so it is best to split it to separate transports as stated above to ensure the proper dependencies.
To fix the issue right now, you can either
1) take another transport through of only the updated / activated update rule or
2) if you know what you are doing and if the client is okay with it, open the system, activate the update rule and when prompted for a transport, create a new one and go to SE10 to clean up that repair transport by deleting the subtasks.
I would probably recommend option 1 for you. I only do option 2 if it is an emergency and there is no transport window for another week or longer or it just simply cannot wait.

Routine doesnt get copied

Hi
we have a cube on which there are update rules. Now created a new cube same as the old one and copied update rules from the old cube update rules. After copying the update rules, i deleted few keyfigures from the new cube and activated. So update rules gets deactivated. When i try to activate the update rule, it says there is error in the routine.
Here my question is when i copied the update rules to the new cube, the routine which is under
$$ begin of routine - insert your code only below this line -*
fill the internal table "MONITOR", to make monitor entries*
Doesnt get copied to the new update rule..Why is it?
REgards
Annie

Hi Annie,
Every update rules are exclusive used by the infoprovider to where it attached. Now, you can do copying the structure of a particular cube or infoprovider. Then, in update rules you can also copy the same code manually and once you'd like to remove infoobjects with it, you need to make it sure that it was not included in your routine or no mapping has been defined on your update rules.
You could find lot of materials here in SDN to understand more.
Godbless,
nips

How to transport routines?

Hi,
I wrote a Start Routine in the update rule, of a cube and tried to transport the complete update rule to the Quality system. After the transport request was released from Developement BW system, it had ended up with an error 8 and in turn also the update rule got deactived in the Quality system. After manually activating the update rule in the Quality system, I created a new Transport Request in the Developement BW and this time transported only the start routine to quality and it was sucessfully transported this time...My query is, during the time I will be releasing the TR from Quality to UAT, will I face a similar problem in the UAT? That is, update rule of the Cube getting deactivated?

Hi,
You have actually done the right thing, even when a single routine is changed, it is a good practice to transport the entire update rule. I am not sure why it ended in errors, I think the reason must be order of the elements in the request. You need to check the transport log and determine the reason for the failure.
It cannot be stated, but it is quite likely that if the transport failed in Quality, it might fail in the next environment also. You could try one think, instead of manually activating the rules, collect the update rules again in transport request and retransport them or Just ask the Basis team to reapply the failed transport. If the failure is due to order of elements in request, reapplying the transport might solve the problem.
Please let me know if you need any more information.
Regards,
Pankaj

Deactivation routine.

Similar Messages

Maybe you are looking for