SAP_ALL in non-productive systems

Hello SAP Security Administrators,
I have been searching (without success) for documentation or posts for a SAP security best practice for who should or should not have the profile SAP_ALL in a non-productive system. Is this typically left up to the individual company security policies? Is it a given that Basis will have SAP_ALL for administrative support? Are Security Admins allowed to have elevated privs in a non-productive system for research and troubleshooting?
We are trying to establish a standard for non-productive systems, so any input would be greatly appreciated!
Regards,
Janice

I do not think there are real standards. Personally I consider using SAP_ALL a sign of utter lazyness because there is never a person who needs to access all functionallity in an ERP system.
The only valid occasions I know to use SAP_ALL is during upgrades but even then it's not a guarantee against surprises.
You are talking about non productive systems but that does not exclude systems with production data, something to consider.
Some thoughts:
Do you want people to influence developments and/or transports if that is not their task?
Do you want pepole to see sensitive testdata just copied from production?
Do you really think your system/landscape configuration will be safe if you have to rely on agreements? Transport routes for instance?
SAP_ALL is something I only allow in sandbox systems and only if they're being backupped at least weekly. That is to avoid heavy discussions when people destroy each others work by curiously hitting buttons and 'trying' transactions.
I am sure some others will have a few suggestions to add

Similar Messages

Setting client role in non-production systems

In our QA test systems of R/3 and BW, the client role in SCC4 was set to 'Production'. The reason I was given is that by setting the client role to 'Production', will enable some settings in FI such as period closing,and customizing settings remain open without transportable requests. I totally disagree with this. I worked on numerous projects, but this is first time I am hearing this. I always set client role to Test in non-production systems, without any problems. Do any one have any idea about this?
Thanks
Santosh

SAP have a concept of "current settings". These include things like exchange rates and other items which really appear to be configuration settings. In a non-modifiable system these cannot be changed because the transport management system tries to get involved. If the client is set to productive, this restriction is overridden.
I would always suggest that the QA system should be set to productive and non-modifiable to ensure that the behaviour of the transactions affecting such objects can be tested in a production-like environment. If you need to have your QA system open for any sort of changes you are exposed to having changes introduced in QA to leading to the impression that new/modified functionality or config works but when the transport takes the unmodified version to production you'll be in trouble.

Technical Monitoring one template used for production and non-production system.

Dear All,
Is there a way to have one template in Solman Technical Monitoring for production system and non-production system with different alerts ? For example if it exceeds a threshold for production system it will trigger red alert or set automatically an incident and if it's non prod system it will go to yellow warning alert ?
Regards
Lukasz Goral

Hi Likasz,
You first create and customize the template, and then assign to a system.
If it was selecting a system and then customizing a template, then may be such functionality makes sense.
So, I don't think that is possible.
Better would be copy the template used for production to non-production and make the adjustment to it.
Regards,
Divyanshu

EWA for non-productive Systems

Hi all,
is there a possibility to get Early Watch Alerts for Systems in a Solution, which are not marked as productive.
I don't want to create many solutions.
The same problem i have with the monitoring, I only see the productive in the monitoring overview.
Regards
Tobias

>
Schlosser Tobias wrote:
> I have added Systems to the Solution XY. The Leading Role of this solution is "productive Systems"
>
> I have add System PR1 (Productive) and System DE1 (Development). But I can only see the EWA for the Productive.
> If I want to see the EWA for the Development I have to delete the log. components and switch the leading role to "Development Systems".
>
> That's very inconvenient.
>
> I wan't one Solution with all my Systems, and EWAs for every System in it. Is this possible?
Yes, it's possible to have all systems (Prod, Dev, QA, ...) within one solution and to have EWA activated.
You need to choose "Put in Solution" from the context menu. See screen shots attached.
Regards,
Ruediger

Source system deletion before copy or refresh of Non productive system

Hi
regarding the refresh of non prod BI system. . As part of refresh, we were asked to follow note 886102.
In this Scenario B3 matches to us. While doing the scond step. I have to delete source systems from RSA1 except my self system.
It is taking long time to delete source systems as each object of source system is prompting for request and consuming long time to complete thsi activity.
Please help me with a smarter method to delete the sourcesystems.
Thanks,
Haaris
Edited by: Hari Prasad Bolla on Jul 14, 2010 8:50 PM

Hi:
The primary source of information is the how to paper on this topic:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
YOu are correct, you can refreh the BI system without deleting the source system.
Thanks for any points you assign (after all, I wrote the paper!).
Best Regards -
Ron Silberstein
SAP

Chart of account conversion SLO tool,method for a Production system

Hi All
We have a requirement like we want to use Chart of account conversion tool for a production system where transactional data are present.
We have used this COA conversion tool for best practice solution not in a production system.
we want to know the difference between these two methods like production and non production system.
Provide me some process document on the SLO service tool for the same
Mrinal dey
9836265158

Hi Mrinal
I'm wondering the same? How to go on in productive system after to use the conversion toll?
How did you manage?
Regards
Angels

Monitoring availability - Different action for Production/Non-production

Hi there,
We've configured availability monitoring on our central monitoring system using CCMSPING agent. Everything is configured correctly and working nicely. However, I have a problem how to take a different action depending on whether alert was raised for production or non-production system.
I've configured an autoreaction method for MTE class Availability_SysPercent_ABAP. This class is not dependent on the remote system. It is the same for all monitored systems, which is the reason for my problems.
If I assign an autoreaction method to the MTE class, the same method will be called if there is an alert for any of the monitored systems. The autoreaction method automatically logs a new ticket in our call handling system. Unfortunately the call handling system can't parse the email to find out which system was the alert generated for. It can only raise a ticket based on some keywords in the content of the email.
The way we configure CCMS for everything (apart from availability) is that we assign different autoreaction methods to different MTE classes. It can't be done in this case as there is only one MTE class. We can't assign different autoreaction method to individual MT elements as this is lost (see note 660126). One of the options could be to change CCMSPING to generate a different MTE class for production and non-production systems, but I haven't found a way of doing it. Another option was to have 2 CCMSPINGs, but they both use the same MTE class.
Has anyone got any experience with this or can suggest anything we can try?
Thanks,
Rob

Hi,
Its still available.
You can still assign different method to nodes.
Its working fine , we are using.
You can assign different method to different systems in RZ20 itself.
Regards,

Procedure to make a system Non-Productive

Hello All,
I want to execute the program ZZ_DELETE_CRMPRLS in the R/3 system to delete the entry in the table CRMPRLS since the LOGSYS and LSGUID are wrong in this table and my material replication is failing. Making the system non-productive is pre-requisite for executing this program.
Can you let me know what the procedure to make a system non-productive? I want to execute this program in my quality system. Tried locking out all the dialog users but it is not working.
With Regards
Sathya

I think you have the setting in Scc4 to make client role as production or non production like test,development.
Run Scc4 select the perticular client and then goto change mode and then change the client role.
Thanks
Rishi Abrol

Can PPDS be linked to non sap system which records production

Hi, We are currently planning with SNP and PPDS but for part of our business, the manufacturing execution occurs in a non sap black screen archaic system. Is there any way to consume PPDS planned orders with the data from an external Production recording system? Or is the only way to consume PPDS planned orders via using SAP R3/ECC?
I have dug through the MES PDF and the BAPIs and cant find a way to "consume" the PPDS planned orders without using SAP R3.
Thanks
j

Hi Lokesh,
There is no limitation to connect two non SAP Systems,PI will support to connect two differt non SAP Systems.
The reuirement you mentiioned bit not clear,what i understood is use JDBC Adapter at sender side and SOAP adapter at receiver side.How to use these adapters search in sdn you will find tons of documents.
Regards,
Raj

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.

Unable to delete Role from User ID in SAP SOLMAN production system but able to from DEV with the same authorization, pls suggest

unable to delete Role from User ID in SAP SOLMAN production system but able to from DEV with the same authorization, pls suggest

Hi,
For SU01 role removal, you do not need S_USER_AGR with 02, and as you mentioned both authorizations available in production, if so trace should not show you the S_USER_AGR with 02 with RC=04.
I would recommend to do role comparison for the user performing the activity. and then check if you have the S_USER_AGR with 02 in user buffer SU56.
But ideally it should not ask you S_USER_AGR for 02 through SU01, so please take help of abaper to debug it.
Also put trace in non-prd to see if S_USER_AGR is getting checked with 02 for removal through SU01.
BR,
Mangesh

External requirement from non SAP system created in SRM 7.0 Extended Classi

Hello SRM Gurus:
Has anyone created an external requirement using XI ExternalRequirement_Create_In (http://sap.com/xi/EBP). We are getting a E001 "No company code could be determined for backend for product##". I traced the error to FM 'BAPI_SCEC_CREATE' in class "CL_BBPX_EXTERNAL_REQUIREMENT". What I found is that it check the attributes for BUK and updates a table with the backend EEC system. Then it checks if any of the entries match our external non SAP system in our external requirement and since it is a non SAP system none do. Then it sets a return error code.
I configured our non SAP system in the SLD and in SPRO under "Define System Landscape" as a non SAP system.
We are running external classic scenario. We just want to created a shopping cart from an external non SAP system. Source the shopping cart in SRM and create the PO in SRM/ECC. We are not using a product master but creating "describe requirement" in our external system. Our product categories are replicated from ECC and the same codes used in our external non SAP planning system.
If I change the external planning system to the ECC backend system, the external requirement is created in SRM but when I source it and convert it to a PO, it returns a backend error that the external requirement number does not exist in ECC. Therefore it appears all of our data from our external system is correct with the exception of how to deternine the backend company code
According to SAP this should be possible using XI.
Has anyone been successful doing this or can you please advise any OSS notes or documentation explaining how to do this. Please advise if you need additikonal info.
Thanks in advance.
Bert

Dear Poster,
As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
Best Regards,
SDN SRM Moderation Team

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

ORA-28500: connection from ORACLE to a non-Oracle system returned this message: ORA-02063: preceding line from OWB_75

ORA-28500: connection from ORACLE to a non-Oracle system returned this message: ORA-02063: preceding line from OWB_75
Scenario:
I am having difficulty getting ODBC connection between Oracle OWB app with an 11gR2 DB (running on a VirtualBox Linux) and SQL Server 2008 running directly on the host. (Windows 8)
I am trying to take a SQL Server 2008 feed into Oracle Ware house Builder, and think(!) I have read everything and configured it in accordance (but I presume not given 3 days of failed attempts to fix it). I have also read several blogs, hence there might be a few more settings in the configuration files than the formal documentation says, but these have come from blogs that have “Solved” problems for other similar situations.
The environments:
HOST:
Name: RESOLVEIT-PC
IP: 192.168.1.80
Windows 8 (64bit) , with system DSN ODBC connection ACME_POS created with 32 bit ODBC set up (This setting still shows up fine in the 64 bit ODBC).
GUEST VM:
Name: OraDBSvr.com
GUES fixed IP Address: 192.1.200
Oracle VirtualBox (4.2.16)
Oracle Redhat Linux 6 (x86)
Oracle 11gR2 Enterprise Edition (11.2.0.1.0)
ODBC: Freetds driver
Configuration files:
initacmepos.ora
HS_FDS_CONNECT_INFO = 192.168.1.80/SQLEXPRESS/ACME_POS
HS_FDS_TRACE_LEVEL = 0
HS_FDS_SUPPORT_STATISTICS=FALSE
HS_RPC_FETCH_REBLOCKING= OFF
HS_FDS_FETCH_ROWS = 1
HS_FDS_SHAREABLE_NAME = /usr/local/lib/libtdsodbc.so
set ODBCINI=/opt/odbc/odbc.ini
# set <envvar>=<value>
odbc.ini
[ACME_POS]
Driver     = FreeTDS
Description = ODBC Connection via FreeTDS
Trace       = 1
Servername = 192.168.1.80
Database    = dbo
odbcinst.ini
[PostgreSQL]
Description                        = ODBC for PostgreSQL
Driver                   = /usr/lib/psqlodbc.so
Setup                    = /usr/lib/libodbcpsqlS.so
Driver64                              = /usr/lib64/psqlodbc.so
Setup64                              = /usr/lib64/libodbcpsqlS.so
FileUsage                           = 1
[MySQL]
Description                        = ODBC for MySQL
Driver                   = /usr/lib/libmyodbc5.so
Setup                    = /usr/lib/libodbcmyS.so
Driver64                              = /usr/lib64/libmyodbc5.so
Setup64                              = /usr/lib64/libodbcmyS.so
FileUsage                           = 1
[FreeTDS]
Discription             = TDS driver (Sybase / MS SQL)
Driver                           = /usr/local/lib/libtdsodbc.so
# Setup                         = /usr/local/lib/libtdsS.so
FileUsage                           = 1
CPTimeout               =
CPReuse                 =
[oracle@oraDBsvr etc]$
freetds.conf
#   $Id: freetds.conf,v 1.12 2007-12-25 06:02:36 jklowden Exp $
# This file is installed by FreeTDS if no file by the same
# name is found in the installation directory.
# For information about the layout of this file and its settings,
# see the freetds.conf manpage "man freetds.conf".
# Global settings are overridden by those in a database
# server specific section
[global]
        # TDS protocol version
;              tds version = 4.2
               # Whether to write a TDSDUMP file for diagnostic purposes
               # (setting this to /tmp is insecure on a multi-user system)
;              dump file = /tmp/freetds.log
;              debug flags = 0xffff
               # Command and connection timeouts
;              timeout = 10
;              connect timeout = 10
               # If you get out-of-memory errors, it may mean that your client
               # is trying to allocate a huge buffer for a TEXT field.
               # Try setting 'text size' to a more reasonable limit
               text size = 64512
# A typical Sybase server
[egServer50]
               host = symachine.domain.com
               port = 5000
               tds version = 5.0
# A typical Microsoft server
[ACME_POS]
host = 192.168.1.80
port = 60801                                # also tried 1433
instance = SQLEXPRESS
tds version = 8.0
client charset = UTF-8
tsql -LH 192.168.1.80
     ServerName RESOLVEIT-PC
   InstanceName SQLEXPRESS
    IsClustered No
        Version 10.50.4000.0
            tcp 60801
             np \\RESOLVEIT-PC\pipe\MSSQL$SQLEXPRESS\sql\query
            via RESOLVEIT-PC,0:1433
Oracle listener:
[oracle@oraDBsvr log]$ cat /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
# listener.ora Network Configuration File: /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = acmepos)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(PROGRAM = dg4odbc)
(HS = OK)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = oraDBsvr)(PORT = 1521))
ADR_BASE_LISTENER = /u01/app/oracle
[oracle@oraDBsvr log]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 16-SEP-2013 13:57:41
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oraDBsvr)(PORT=1521)))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date                16-SEP-2013 13:50:34
Uptime                    0 days 0 hr. 7 min. 7 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/oraDBsvr/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraDBsvr)(PORT=1521)))
Services Summary...
Service "acmepos" has 1 instance(s).
Instance "acmepos", status UNKNOWN, has 1 handler(s) for this service...
Service "dw" has 1 instance(s).
Instance "dw", status READY, has 1 handler(s) for this service...
Service "dwXDB" has 1 instance(s).
Instance "dw", status READY, has 1 handler(s) for this service...
The command completed successfully
Oracle tnsnames.ora
[oracle@oraDBsvr admin]$ cat tnsnames.ora
# tnsnames.ora Network Configuration File: /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
dw =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = dw)
acmepos =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521))
(CONNECT_DATA=(SID=acmepos)
(HS=OK)
Oracle sqlnet.ora
[oracle@oraDBsvr admin]$ cat sqlnet.ora
# sqlnet.ora Network Configuration File: /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
# Generated by Oracle configuration tools.
NAMES.DIRECTORY_PATH= (EZCONNECT, TNSNAMES)
ADR_BASE = /u01/app/oracle
I can connect from the linux server to SQL Server, and query the database:
[oracle@oraDBsvr etc]$ tsql -S acme_pos -U acme_dw_user -P acme1234
locale is "en_US.utf8"
locale charset is "UTF-8"
using default charset "UTF-8"
1> select last_name from dbo.employees;
2> go
last_name
Davolio
Fuller
Leverling
Peacock
Buchanan
Suyama
King
Callahan
Dodsworth
(9 rows affected)
1>
However, I can’t get a response through Oracle OWB , and I get:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message: ORA-02063: preceding line from OWB_75
In the hs log file I get:
[oracle@oraDBsvr log]$ cat acmepos_agt_3821.trc
Oracle Corporation --- MONDAY    SEP 16 2013 13:51:22.170
Heterogeneous Agent Release
11.2.0.1.0
HS Gateway: NULL connection context at exit
[oracle@oraDBsvr log]$
I am really stuck now and going round in circles and can’t see the wood for trees! Can anyone please help?!!
Many Thanks.
Rafe.

Let us rewrite your ODBC DSN a little bit... Your current odbc.ini looks like:
[ACME_POS]
Driver     = FreeTDS
Description = ODBC Connection via FreeTDS
Trace       = 1
Servername = 192.168.1.80
Database    = dbo
Let us change it a little bit so that we only need one config file - no odbcinst.ini nor freetds.conf file anymore:
[ACME_POS]
Driver =/usr/local/lib/libtdsodbc.so
Server = 192.168.1.80
Database
= dbo     #### I have some doubts that you have a SQL Server database called dbo - one database that always exists is master - so as a test use master here or get the real database name of the SQL Server database you want to connect
Port = 60801 ## make sure it really is the correct port - best would be to check on the SQL server and then try telnet <ip> <port> if you can connect to the SQL server
TDS_Version = 8.0
QuotedId=YES
Especially the last 2 parameters are mandatory. TDS_Version specifies the TDS Version you have to use to connect to the SQL Server and QuotedID is required for DG4ODBC as it surrounds objevt names by double quotes.
What happens now when you try to connect with for example isql - the ODBC test utility shipped with the ODBC Driver manager?
In addition, could you please do me another favour and check the word size of DG4ODBC and the ODBC Driver Manager as well as the ODBC Driver - just execute:
file /u01/app/oracle/product/11.2.0/dbhome_1/bin/dg4odbc
file /usr/local/lib/libtdsodbc.so
file < the patch to your libodbc.so library>/libodbc.so
and post the output.

Query created in production system and object changeability

Hi,
The production BW has the object changeability for query elements set to 'Changeable original'. Some queries which have been created in this system can be changed, others, which have also been created in the system, can not.
All queries are assigned to the development packate $TMP. None of them have been transported anywhere, nor have they been created somewhere else and transported into the system.
The system is BW 3.5, SP 17.
Has anyone got any idea what the problem could be?
Best regards,
Rita

Hi,
The object changeability in the system is set to 'Changeable Original' and I know where to switch from 'not changeable' to 'changeable original' to 'everything changeable'.
The normal development cycle sees reports being created in the development system and then being transported through to the production system. Here, they should not be changeable. However, users with the relevant authorisation should be able to either -
- create new copies of these reports and change them or
- create new ad-hoc reports and also change these
We have several of these reports on the production system. The object changeability is set to 'changeable original', as I mentioned. I would expect that all queries which have been created on this system and never transported (either in or out of the system) should be changeable, based on this setting. However, some are, some ar not. The error message when trying to change the 'non-changeable' ones is 'Operation falied! No error message available from the server'. If I make a copy of one of these queries, hoping to save is as an ad-hoc query and change it, the error message is 'query could not be saved due to a problem in transport'.
How come some can be changed, others can't? Is there anywhere I can check what the difference is between the changeable and non-changeable reports which have been created on the system?
Best regards,
Rita

SAP_ALL in non-productive systems

Similar Messages

Maybe you are looking for