Index value maintenance directly in a Production system

Hi,
Is it possible to control the access to T-code: REAJINDX ( Index value maintenance) by Authorization Management (Profile Generator/Role management) in a closed system (Production) for configuration?
Authorization Object: S_TABU_NAM
Activity: 02
Table: V_REAJINDXCLASS
The requirement is the Index value maintenance directly in a Production system (closed system for the configuration) through the Authorizacion Management.
Thanks and best regards,
Fernando

Hi Franz,
First, thanks for your quick response. I haven´t got to solve the problem with these notes. I would like to explain in further detail the issue and the current system configuration.
The configuration for the Client (T000) is the following:
Client Role: T (Test) or P (Production)
Changes and Transport for Client-Specific objects: No Changes Allowed
Cross-Client Objects changes: 3-No Changes to Repository and Cross-Client Customizing objects
The configuration for the object VC_REAJINDX (SOBJ) is the following:
Category: CUST
Transport: 2-Automatic Transport
Adjustment: Automatically adjustable
Current Settings: Marked
With this configuration at client level and for this object, it is not possible to maintain the Index values in the target client. Then my question (doubt) is if it´s possible to maintain the index values in despite of this configuration by Authorization management (User roles/Profile Generator) for this object (Example: Give authorization to modify this object (in order to maintain the values) to a Key User with a specific role, SU01). Or if it´s not possible, then It´s necessary to change the configuration for the object (VC_REAJINDX) for the fields, Category, or/and Transport,... For this option, it´s necessary to modify the SAP standard using a Developer key and I´m not sure if it is a recommended solution.
But my client wants to maintain the index values directly from PRD system and not from a DEV system and after transport the updates to PRD.
On the other hand, the error message that the system shows it isn´t the message number TK430, It is the message nº SV052, No maintenance authorization for requested data (Diagnosis: You have attempted, in change mode, to access data for which you have no authorization.). This is the reason I think, maybe, it is possible to control it through the Authorization management.
Thanks in advance and best regards,
Fernando

Similar Messages

BCS - master data change in productive system?

Hi group,
We are about to go live with our BCS system, but of course someone got the great idea of changing the company code currency for one of the "non-SAP" companies in the group since the sytem was set up.
When I enter the consolidatin workbench in our production system, everything is considered customizing, so no changes are allowed - even to master data. I''ve searched the "Object changeability" settings of the BW system but couldn't find any settings regarding BCS. I also checked settings in se06 and found a namespace "/FINB/" which I suspect has something to do with BCS (currently set to "Not modifiable")?
What are the correct system settings for the BCS system to function correctly, and what is the normal procedure for maintaining master data in SEM-BCS? - by transport requests or by changing directly in the productive system?
Best regards
Thomas
P.S.: Are there any usefull resources for BCS on the Internet? The help in the system is very limited and I can't find anything on the SAP marketplace.
Message was edited by:
Thomas Ringe Pontoppidan

Hi Dan,
Example: you have a single selection containing a set (not range) of separate values. Then you decided to change the set (adding one more value, for example). Are you saying that this single selection change in DEV will be reflected automatically in PROD?
From my experience I know that while using single selections, the system replaces it by the set/range/node. And when a single selection was changed, nothing yet happened with elimination settings using SS. You have to go into each part of the settings in the method and refresh the SS. You'll see that only after that the set of values was changed. It's obvious for me that if I don't do this refreshing in DEV and then import the request into PROD, I'll have the old, not modified, version of my settings.

Query developement and se16 access on productive system

Hi,
we are setting up an authorization concept on ERP2004s and our users asking for query development rights and se16 on our productive system. I think queries and se16 should be on the test system due to security reasons. Please post some feedback how do you think about it!? I think queries should be developed on the test system and transported.
Thank you in advance!
Best regards
Frank

Hi Frank,
I dont think that you can give access to writing a quaery in production system.
writing a query also need access to:
Transaction Code: SE16
Authorization object: S_TABU_DIS
Activity: 02 AND 03
Risk: The risk here is that users who have this access, have the ability to maintain table data directly in the production system. This includes transactional, masterfile, security and configuration data.
Hope it is useful.
Please award points if it is useful.
Thanks & Regards,
Santosh

Will Queries will be created in the Production system?

Hi all,
Is it possible to create queries directly in the Production System. And if there is an issue in the query in production systems can it be fixed in the production system itself nor it should be moved to development and then to qa and then to production???
can anyone guide me on this???
thanxs
haritha

Hi,
I am creating all my queries directly in the production system; it all depends on your strategy.
Of course, when you'll have an issue, you'll have to fix it directly in PROD since your query doesn't exists neither in DEV nor in QA.
Based on our authorization concepts where users are allowed to see only some queries we create new queries in PROD with a certain name so that users cannot see that query. We test it with live data and when it's ready we save it as under another name; the query is now released to authorized users in order to test it. When the query is assessed "valid" for the requester, when save it as again this time "LIVE" which is the final version of it. If they're changes, we go trhough the same cycle.
We also use our DEV (we have chosen not to have a QA) to test special scenarios and variable exits....
hope this helps...
Olivier.

How to Enhance SPRO so that Config can be maintained in Production System

I have a requirement to Enhance the configuration nodes within SPRO so that the Client can directly edit specific configurations that would pose a risk to the business if they have to wait for the production release.
I have to enhance the following Node :
u2022 Advanced Planning & Optimization --> Supply Chain Planning --> Service Parts Planning (SPP) --> Monitoring --> Shortage Analysis -->Make General Settings for Shortage Analysis
u2022 Supply Network Collaboration --> Basic Settings --> Notes --> Define Reason Codes for Notes
The check box for "Current Setting" is input disabled for the above nodes in SPRO.
Please let me know if there is a SAP Note available to Enable "Current Settings" which will allow the Client to maintain settings directly in Production System.
If not , Please suggest any alternative solutions.
Thanks in Advance,
Vinit

Hi,
Your basis team should be able to help you to make changes directly in the production system.
Regards
Datta

Maintain (SMARTFORMS) objects in production system

Hi,
I need to maintain special objects directly on the production system although the system is declared as non-changeable. Is there a chance to customize this without a modification? I need it to be able to maintain smartforms text-modules.
any help is highly appreciated
thanks in advance and regards
Gabriel

Hi Gabriel,
No it is not possible.
Regards.
Ruchit.

Delete COPA value fields in a productive system

Does anyone have practical experience with deleting COPA value fields in a productive system?
The issue is that old, no longer used value fields should be deleted from a productive system to allow creating new ones, as the maximun number of value fields is reached.
An alternative would be to delete the prior transaction data captured on these no longer to be used value fields and rename them for their new use (to avoid that different kind of old and new data is reported on the same value field).
I am refering to the documentation on transaction KEA0 (or OSS note 160892 up to release 4.5), where it is mentioned that deleting value fields should only be done for operating concerns that have not yet been used productively. Did anyone do this already in a productive system?
Cheers, Peter

To delete characteristics or value fields, you should perform the following
activities:
1. Delete the corresponding characteristics and value fields from
Customizing in all clients (this includes forms, reports, planning
layouts, and so forth). To locate characteristics and value fields, use
the appropriate where-used list in the Customizing Monitor. You can
access it by choosing Tools -> Analysis -> Check Customizing Settings
(TA KECM).
You can jump directly from the where-used list to the relevant
Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an
operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the
operating concern before making any deletions, effect those changes and
save the data structure.
4. In order to be able to select the fields of the data structure,
choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove
them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking
whether the operating concern contains any data and whether the fields
to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the
re-activation. If the operating concern does not contain any data or
does not require the database system to be converted, the tables are
activated. You are then able to activate the environment for the
operating concern. In this case, the following activities no longer
apply.
If the operating concern already contains data, a system message tells
you that the database needs to be converted. If you proceed, an
activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages
telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can
be converted. In this case, you should answer "No" to the next prompt,
which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the
tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted
is shown for this. If the tables only contain a small amount of data
(less than 10 000 records), then all the tables can be converted in one
job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs.
However, you should ensure that table CE4xxxx (where xxxx = operating
concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during
the conversion.
A copy of the table is generated during the conversion. The database
system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function.
You can display the current status of the conversion by selecting the
"Refresh" icon. Tables disappear from the list once they have been
converted sucessfully. If a conversion is taking a while, it is also
possible to leave the transaction. You can then continue the conversion
using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services ->
Jobs.
Using the database utility transaction. You access this by choosing
Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating
concern during operating concern maintenance. You need to activate all
tables after conversion.
11. To analyze errors that have occurred during the conversion, you can
use the database utility transaction by choosing Extras -> Logs. The log
has the same name as the conversion job: TBATG-date. You can also
restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application
help while still in the above transaction.
12. Once you have activated all the tables in the operating concern,
generate the operating concern environment from within operating concern
maintenance.
You can then use the operating concern again.
Please, refer to the IMG documentation under Controlling ->
Profitability Analysis -> Structures -> Define operating concern
-> Maintain operating concern, for further details.
Hope it helps

Update Purchasing group directly in production system

Hi,
We keep getting purchasing group changes requests and we follow conventional approach, configure in development - move to Quality and then to Production.
Since we have high number of requests, we are exploring the direct maintenance in Production system. Please advise on the best approach to this.
thanks
Mahesh

there is an alternative missing.
you can change a customizing activity to be a master data activity, and you do not need to have the PRODuction system open for customizing..
this is explained in OSS Note 135028 - Transfer IMG activity to current setting
However, I have made my experience in the past as I joined my current employer. In this system the purchasing groups were maintained in production system, which I did not know, and some key user did not know too, as they asked me to add a new purchasing group. I did this in the development system and transported to prouction.
And it happened, that I added a purchasing group in developement that was already accopied in production, so the entry in production got overwritten with my transport. so for a couple of days 2 buyers worked with the same purchasing group, they did not even realize it, as nobody is really looking at a PO form if a system is live for many years. This caused some trouble with statistics and as well with communications between vendors and us.
a second experience was made by the fact that people had deleted purchasing groups, after buyers had left the company. But SAP validates the existing of purchasing groups when archiving purchase orders. So I had to recreate all deleted purchasing groups before I could continue with archving.
I think that this experience is reason enough to not give this customizing activity into user hands.

Wrong value in message header on target system | "test" -- "production"

Hi all,
need some help with this.
When sending a message with RNIF Adapter to target system there's something wrong with the Message Header.
GlobalUsageCode has the value "test" but should say "production".
Any ideas where i can change that value on PI side ?
Cheers
Lars

may be u can change it in the mapping . it should be definitely possible using abap mapping

Create a Support Message in Production system showing up in Solution Manage

Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
Paul

Hi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role.

How to edit customizing view in production system?

Hi,
I wonder if it is possible to edit customizing view (ex: tcode OAV8) directly in production system. I need a method that doesn't require repair.
Any help will be appreciated..

Hey
You can copy view V_T087G to ZV_T087G. After you have to create a new table maintenance for this view. The new table mainteance will have a Z function module so you can select in the "Dialog Data Transport Details" the flag "no user recording routine" instead of "Standard, recording routine".
After you have to call this table maintenance from Sm30 or from a transaction.
Regards

How do I use the Index Values property node with a multidimensional array.

I am using a 2D array to store operator inputs on my front panel. I only want to display one element to the operator at a time. I am trying to use the Index Values property node to change the displayed element. However, I can only get the Rows index to work. How do I direct the Columns index as well? The help says to use one per dimension. I need clarification on what this is talking about. I've tried adding a second element to the property node, 2 seperate property nodes, and diferent wiring techniques. (series, parallel)

If you only wire up one of the inputs (col or row) what you get out is a 1D array of either the column or row. If you wire controls to both, then you will get one element out of the array. Getting a single element in a 2D array requires you to specify both a row and column.
Message Edited by Dennis Knutson on 02-08-2007 08:34 AM
Attachments:
Index 2D Array.PNG ‏2 KB

Replicate data from one client to another in a production system

Hello,
I have two client in production system. Whenever a equipment is created in one client it should be replicated in another client and whenever a equipment is changed in one client the changes should be replicated to another client.
Data should be immediatly replicated to the another client.
Can basis do some setting so that the two client will always have the same data for equipments.
or i have to get the data from one system and send it to another system through idoc and update that data in another system. This will take a lot of time.
or is there any easy way

Hi Sachin,
You need custom program to achieve this requirement. Either you can use ALE+IDoc or direct BAPI function module call.
This should happen within seconds if designed properly.
Regards,
Avinash

Transformation pointing to Quality Client in Production System Repeatedly

Hi,
I need to understand one issue which is explained in detail below step by step.
1. I created one Customized Data Source(Full Load) and replicated in BW.
2. Also created Info Objects, DSO, Info Package, Transformation, DTP.
3. While transporting this modelling to Production(first time), i unknowingly/mistakenly missed capturing the datasource in Transport Request.Sequence of transport was -
Data Source
Info Area
Info Object Catalogue
Info Object
DSO
Cube & MP
Data Source
Transformation
Info Package & DTP
Now, the moment TR for transformation was transported it threw an error - "Data Source does not exist in Quality client". Then I transported the Data Source TR and after that re-transported the transformation TR production and this error was removed.
But, there were 2 transformations in production - 1) Pointing to Production, 2) Pointing to quality.
4. I request the basis team to delete the second transformation(pointing to quality) from BW production system.
5. After that we captured Data Source and transformation in same TR and transport was successful.
6. Now, after few days we transported a change to production for same object and the system again threw the same error mentioned in point no.3 above and created two transformations again.
How to resolve this issue permanently and I also want to know the reason of this type of system behavior.

Mohammed,
I did that also - please read my step no.4.
We are able to delete the transformation which was referring to quality client and then captured D.S & transformation in a single TR and transport as successful.
Now, after few days I did one change in the same transformation and transported to production.
System Behavior:
Error - " No source exist (i.e.,system referred to quality in production)".
Also again transformation was visible in production which was referring to quality client(which we already deleted with the help of BASIS).
Now since again the transformation needs to be deleted from production, our basis team is telling us to they cannot delete objects every time in production.Thus,
1. Is there any option to solve this issue permanently?
2. Also is it necessary to transport data source along with the transformation which is directly linked to data source?
Please Note: We have Dev+Quality as one client and Production.

Support message and change requests only for production system

Hi guys,
I would like to connect the solman helpesk with CHARM ( CHARM is still running ).
In CHARM I have to create a CR only for production system. ( don't know why - but works as designed).
In SAP helpdesk I can create support messages for every kind of system type but if I want to connect both (HD and CR) , the source system (ibase component) of the issue will copied to the CR and runs in error because of the rule (only p-system) of CHARM.
Of course I can change the ibase to production system manually in SDCR but it seems a very error-prone method.
Now my question: is it possible to change the ibase component due to the creation of CR by copy rule or something like this?
Kind regards
Rayko

Hi Rayko,
We do not have this option.
Once in ChaRM, we assume that the changes will always correct an issue in the PROD system.
I would recommend to open the tickets directly with the PROD system IBase, once the issue is also happening there.
Best Regards,
Fernando

Index value maintenance directly in a Production system

Similar Messages

Maybe you are looking for