The same InfoSource in multiple SAP systems?

Hello,
In my BW system I have got a mySAP CRM and a mySAP ERP source system delivering data.
But both systems provide the same DataSources. The mySAP CRM system provides sales data and the mySAP ERP system as well. If I put in RSA1 -> Source systems -> DataSource overview, I recognize that both systems have provide the same datasources.
What is the difference between the data each system provides, how could i check this?
Which data from which system should I use for analyzing purposes?
Could I use one InfoSource and connect DataSources from both systems and create an InfoPackage writing the data into the same InfoProvider?
Thanks in advance!!!

Thanks a lot Roberto,
I have got one more question in that context.
If I use one InfoSource, connect two different DataSources, create an InfoPackages for each one and load the data (from both InfoPackages) into the same InfoCube, what will happen?
Does the InfoCube contain redundant data (data from both systems), what data does the InfoCube contain?
I am not familiar with the connection between mySAP ERP and mySAP CRM. Does the mySAP CRM get its data from mySAP ERP? What is the connection?
Does a mySAP ERP system have the same data like a mySAP CRM system regarding DataSources like SD-Delivery (2LIS_01_S261), 2LIS_01_S263, 2LIS_01_S260, etc?
Why do both systems have the same data like the SD ones?
thanks a lot

Similar Messages

How to garantee IDOC types are the same on two communicating sap systems.

Hi all:
    how to garantee IDOC types are the same on two communicating sap systems, including segments and versions, using bd64?
    what's more, what bd64 using for besides generating parter profiles, must we use bd64 for outbound idocs?
    Thank you very much
best regards ?

Hi jingying Sony
You can compare the Idoc type and Version between Sender System and Reciver System.
Use TCode SCMP and Compare the Table EDIMSG in Both System.
This will solve your issue.
Thanks
Ramesh

SLT Replication for the same table from Multiple Source Systems

Hello,
With HANA 1.0 SP03, it is now possible to connect multiple source systems to the same SLT Replication server and from there on to the same schema in SAP HANA - does this mean same table as well? Or will it be different tables?
My doubt:
Consider i am replicating the information from KNA1 from 2 Source Systems - say SourceA and SourceB.
If I have different records in SourceA.KNA1 and SourceB.KNA1, i believe the records will be added during the replication and as a result, the final table has 2 different records.
Now, if the same record appears in the KNA1 tables from both the sources, the final table should hold only 1 record.
Also, if the same Customer's record is posted in both the systems with different values, it should add the records.
How does HANA have a check in this situation?
Please throw some light on this.

Hi Vishal,
i suggest you to take a look to SAP HANA SPS03 Master Guide. There is a comparison table for the three replication technologies available (see page 25).
For Multi-System Support, there are these values:
- Trigger-Based Replication (SLT Replication): Multiple source systems to multiple SAP HANA instances (one source system can be connected to one SAP HANA schema only)
So i think that in your case you should consider BO Data Services (losing real-time analytics capabilities of course).
Regards
Leopoldo Capasso

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

Multiple SAP systems in MSCS with Oracle

Hello,
We are going to install a BI instance in a MSCS cluster in which there is already a SAP system installed and clustered.
The SO is Windows 2008 and Oracle 10.2.0.4.
My problem is about the Oracle sw. In previous SAP releases there was a guide called "Installation of Multiple SAP systems in MSCS: Oracle".
For my release Netweaver 7.0. EHP1 SR1, there is no specific guide. All the references are the installation guide and part related to MSCS installation and a white paper about "new configuration of multiple SAP systems with Windows 2008 Failover Clustering".
In all that documents I haven't found what to do with the database. In the beginning of the installation documents says that Multiple Oracle_home for different database instances are not supported in an MSCS configuration. But in the pages related to the MSCS installation says "if required, set up multiple Oracle Homes".
So, what's the option? Multiple Oracle_homes or MCOD? Be in mind that I already have a SAP system in this cluster, so I already have an Oracle home c:\oracle\<SID>\102
Have you work in this scenario?
Thanks and best regards,
Ana.

Hi,
Officially SAP does not support Multiple SAP Systems in One MCSC Cluster. If such installation & configuration has been done by SAP Global Technology Partner then and then only SAP provide support.
what's the option? Multiple Oracle_homes or MCOD?
GO for multiple oracle_home , in which the same drive letter for oracle_home should be used on local disks in both MCSC cluster nodes. And the same oracle_home should be junctioned to the shared location on shared space.
The Chapter 7 High Availability with Microsoft Cluster Service of [Inst. Guide SAP NetWeaver 7.0 incl. EHP1 SR1|http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000659894&_OBJECT=011000358700000353072009E] contains all the required information with detail. Refer it.
Regards,
Bhavik G. Shroff

Multiple SAP Systems In One MSCS Cluster

We have installed a NW 7.0 EHP abap stack in a MSCS Cluster with 2 nodes.
This was installed as a standard Cluster Install.
We have now higlighted a requirement to install a 2nd (Java ) instance in this Cluster Group.
The NW 7.0 EHP1 documentation and Note 1321854 shows that multiple SAP systems in one MSCS cluster is supported.
The documentation, however, is not clear if the 2nd instance can be installed when the 1st instance was installed without the preperations for Multiple Systems.
There are no further documentation or guidelines to help.
Has anyone come across this situation or managed to install 2 SAP instances in one Cluster Group based on Windows 2003, SQL Server 2005.
Regards

I am not quite sure if I understood your problem completley. But let's see...
Usually you use on on MSCS Cluster Group per SAP instance. So you have your already existing NW 7.0 ABAP stack in a separated Cluster Group, and you create a new Cluster Group for your new Java system.
You can find more information about it in this guide here on SDN:
Link: [High Availability;
More information about High Availability Setups for SAP System can be found here on SDN:
Link: [High Availability]
If you want to use the same database for your clustered ABAP stack and your new Java stack you can do a MCOD installation.
Please see Link: [SAP Note 388866 - Multiple Components on One Database - Installation|https://service.sap.com/sap/support/notes/388866]
Hope this helps.
Best regards,
Mathias

Assignment of One Solution ManagerDiagnostics Agent to Multiple SAP Systems

Dear Experts,
according to the Powerpoint presentation attached to SAP Note 1365123, one single Solution Manager Diagnostics Agent can be used for E2E RCA with multiple SAP systems running on its physical host.
I have installed one Diagnostics Agent on a server where three ABAP systems are running. Each ABAP system on this server has been installed under an alias (i.e. all these SAP systems are reachable under the same IP address. No virtual servers with individual IP addresses have been defined.). I want to configure each ABAP system for E2E RCA. When running the Managed Systems Setup procedure for E2E RCA, I am not able to assign the diagnostics agent to more than one of these ABAP systems - after the first system has been configured for E2E RCA, the entry for the Diagnostics Agent on this particular server is no longer available in the drop-down list of Diagnostics Agents when configuring the next system.
Is my understanding of the presentation mentioned above wrong, or am I missing a trick here? How can I assign the Diagnostics Agent to all three SAP systems that are running on the same physical host?
Details about the environment:
SAP Solution Manager: SAP EHP1 for Solution Manager 7.0 (SP Level 24)
Diagnostics agent version : 7.01.7.0.20100326100205
Thank you for your time,
Rainer Walter

Hello,
Have you followed all the rules?
Rule 1
Consider the diagnostic agent as a standard SAP system
Rule 2
Install one Diagnostic Agent per host (Physical or Virtual) (You mentioned you don't have virtual hosts)
Rule 3
Each Diagnostic Agent gets mapped to the SMSY repository using the server name key
Rule 4
Do not install a Diagnostic agent on a host that only run databases or SAP Central Services
Rule 5
An Agent can only conenct to one single Solution Manager System
If you install multiple Diagnostic Agents on the same host, each one needs to be connecting to a different Soltuion Manager system
Rule 6
Choose the adequate diagnostic agent installer/version
Rule 7
In a switch over scenario diagnostic agent must move with their respective virtual host and managed components
These are the rules attached to SAP Note 1365123. You need to comply to the rules.
If you have multiple agents ont he same host, then they need to conenct to different solution manager systems....according to the rules. One agent per physical host is one of the rules...specifically rule #2. This is my take, and it seems pretty clear here.
Regards,
Paul

Centralised EHS system and users and organisations in multiple SAP systems

Wanted to have your experience/ advice or experience in setting up a centralised EHS system talking to multiple SAP systems and other ERP systems
If the client have sister companies and locations in multiple SAP systems , can we go for a centralised EHS system talking to multiple SAP systems
Is there a concept of application ID in EHS system : If so how EHS system can identify the < to EHS system records to tag the system > , <EHS system Records bound to have different configs for each ERP systems> and < from EHS system records to multiple SAP systems >
Can you list client experiences or roadblocks for this type of design

Hello
the answer to your question is: may be you can use a central EHS system. The reason is: EHS is correlated with MM. A SAP system in which EHS is used without MM makes "not realy" sense. So it is a matter of definition "what is a central EHS system".
EHS it selfs uses SAP standard techniques. That is "ALE" distribution to other SAP systems. The distribution of EHS data top NON SAP systems is possible to via XI (which is the common solution). If you use as the scenario SAP to SAP you must make your that standard EHS customizing is the same on both sides.
Furthermore SAP EHS is a "great" module with several submodules. So regarding each of the potential scenerios you need to check the necessary prerequisites. It ois very common to have EHS PS, DG, HSM in one system and to distribute data via ALE to a different system so that the EHS data can be used "decentral" in the several SAP logistic processes.
In most cases you need to distribute per ALE at least DG master and hazardous substance master.
As a starting point take a look here: http://help.sap.com/erp2005_ehp_05/helpdata/en/c1/eda0f591ec12408b25e7a1b369ca45/frameset.htm
BASIC Data and Tools => Tools => Distribution of specifications, phrases and reports per ALE.
Hope this helps.
With best regards
C.B.

Login to multiple SAP systems using pwd of single SAP system

Hi All,
We have 3 different SAP servers, with sids: ECD, BWD, HRD.
for each user, a user with the same username is created in all three systems.
the user does not want to maintain 3 different passwords, instead only single password to be used in all systems. i.e. when he changes the password in system ECD, the changed password should work in other systems BWD and HRD as well.
if we were using SAP EP, we checked the possiblity of username based SSO and having portal login using only on system ECD.
but we are not using the portal, and all the users will access 3 sap systems using SAPGUI.
is there any way, where one system's password will work to login to other systems.
thanks in advance,
Madhu_1980

Hi Tim,
You're right about the fixed client for the MYSAPSSO2-ticket-issuing system. In the case for Java, the "client" is specified inthe UME parameter login.ticket_client. And the trusting ABAP system will have to add the Java system + "client" into its ACL (in addition to the certificate). This "client" will only play a role in that "trust" relationship.
As for launching the actual transaction via SSO, this is how it works.
SAPGUI transaction will be launched by a thing called Portal transaction iview. That iview will have a parameter called the System Object. The System Object will determine which ABAP system-client it will connect and logon on to. So if you want to logon to multiple clients, then create one System Object for each of the system-client combination, and then create transaction iviews to each of the corresponding system object. The iviews will be presented to the user which then allows the user to launch the transaction iview (specificy SAPGUI link in the iview property)
https://help.sap.com/saphelp_nw74/helpdata/en/4e/1262711e3d2287e10000000a15822b/content.htm
I hope I understood your questions.
Cheers
Donald

Fall back systemwhen multiple SAP systems trying to acheive SSO with BOEXI

Friends,
I need a small clarification on ' SSO between BOE XI 3.1 and SAP BI 7' Scenario,
Say when multiple users log on through their SAP EP Portals or Netwever Portals, they use their tokens generated by their respective EP portals which are passed through the 'Web application server' hosting BOE environment.
1) When its a Single EP portal , we can have have a fall back system. when we register its logical name in the CMC of BOE Environment , a typical SNC.But what's the fall back system for multiple SAP systems?
2) Also Whether there are any pit falls via token method when more than one SAP system communicating to BOE?
3) Do we have any documentation for this?
Thanks ,
Sivakanth.

Hi Sivakanth,
the normal scenario for SSO is the following:
When you said ''back end system ', i did not get it.
Enterprise Portal -
(iView)-------> BOE -
> SAP BI <- This is your backend system
Well Could I define more than one logical name there in SNC tab of CMC.?
I assume you have the following situation:
(EP1, EP2, EP3) -
> BOE -
> (SAP BI 1, SAP BI 2, SAP BI n)
You can define more than one entitlement systems in the BOE CMC and also configure for each one of them for SNC. Please note that we are talking about server trust and NOT client trust here. It is all about letting your sap system and the boe system trust each other. If you have your portal with client SNC configured (ie. the user logs using a certificate and an SAP logon ticket is created) it is NOT necessary to configure SNC in the CMC (Please refer to the section "Configuring SAP Server-Side Trust" in the installation guide for the integration kit for SAP) side.
Back to the SSO scenario now: When a user connects from an enterprise portal on the BOE system the logon ticket, generated from the portal, is forwarded to the back-end system, which is defined in the portal iView the user is currently navigating through. If it is a Crystal Enterprise iView then you just have to select the appropriate system alias of your back-end system in the System drop down menu when creating the iView. For URL iViews you must utilize the relevant openDocument parameters. If you do not define anything at all when creating the iView then BOE tries to authenticate the logon ticket against the SAP BI system you selected to be the default one in the "Authentication->SAP->Options" tab of the CMC.
If what you want is just to distribute the load between your SAP back-end systems then you should consider utilizing an SAP cluster for your pursposes. As explained before BOE will not distribute the requests evenly on the back-end systems. It will try to contact either the system defined in the request (iView) or the default system. To be honest I am not sure what happens if the explicitely defined system is not available but I think that an error message is what you should expect then. I do not think that in this case the BOE system tries to use the system defined as default.
Another part is what kind of security is defined in BEX querys..as i read from SAP IK guide, we can import all the roles which are defined at ABAB level.
Will there be any security threats to SAP data via this method.
It is true that you can import all roles in your BOE system. But keep the following four things in mind:
1) You can restrict on the BOE side the users which are authorized to logon in the CMC and import the roles (normally only the BOE administrator is authorized to do this)
2) Importing a role means that an SAP user can try to logon the BOE. Still the logon process can only be succesfull only if the SAP user has special authorization on the SAP side (Please check the Appendix "Authorizations" in the installation guide of the integration Kit for SAP.
3) You can restrict the access to data by assigning authorizations only for specific infoareas/infoproviders. In order to partially restrict data access in a given infoprovider (e.g infocube or multiprovider) you can utilize authorization variables in your BW query.
4) You can further restrict access on specific reports either on the BOE side or on the portal side (by rstricting access to the defined iViews).
For sure you must invest some time to define and implement your security concept.
More over could you please answer other 2 questions in my original question.
2) Also Whether there are any pit falls via token method when more than one SAP system communicating to BOE?
3) Do we have any documentation for this?
2) As long as your portals, the back-end systems and your BOE system are configured correctly for SSO this should not be a problem. Well just a tip based on my experience: be sure to use full qualified domain names for your systems in the iView definitions. And do not forget SSO works only if all systems are in the same domain.
3) As said in my previous posting the netweaver documentation regadring SSO setup maybe interesting for you. As far as I know the multiple systems scenario is not contained explicitely in any official BOBJ documentation. I assume that you already went through the installation guide for the integration kit for SAP.
Please tell me if you have a completely different scenario in mind
Regards,
Stratos
Edited by: Efstratios Karaivazoglou on Mar 22, 2009 12:27 AM

Installing data quality management for sap for multiple sap system

Hello folks,
I have an Requirement where i need to install data quality management for sap in multiple sap system.
I have installed it successfully for one system .
here my data services is installed in one server with rfc server as windows services in same server.
i have done the required configuration in ecc side.
my question is how do i use same data services jobs which are configured as real time services for both my sap connection?
in simple terms how do i installed dqm for multiple sap system having single data services server.
thanks,
Shubhangi.

Hi Vishal,
Regarding DQM Please refer the below Link.
Links:
http://scn.sap.com/community/data-services/blog/2013/07/18/i-installed-dqm-for-sap-you-can-too
or you can also refer below SNotes given by SAP:
1732816 - How to manually import DQM ATL files correctly after failed install
Note 1732816 - DQM Adapter Dataflow installer fails on Data Services 4.1
Links:
https://service.sap.com/sap/support/notes/1732816
Thanks,
Daya

Can I view the same pdf on multiple iPads at the same time with 1 iPad operating as the master (controlling page turns etc)?

Would like to use 4nr iPads as an autocue system. Can I view the same pdf on multiple iPads at the same time with 1 iPad operating as the master (controlling page turns etc) and the others operating as slaves? Can this be done without the use of 3G or a remote Wifi hub? I would appreciate your input.................

Open the document in Acrobat Reader and use the menu Window > New Window.

Can i use the same advertisement to multiple collections?

Can i use the same advertisement to multiple collections?
Advertisment A1 currently linked to collection C1.
Can i use the same advertisement A1 to a collection C2? Because my collection C1 is query based and the C2 would be a static one.
If i use the same A1 advert, will it affect the earlier linked C1 collection i any ways?
System Security analyst at CapG

Well, in 2007 you actually kind of can. You can used linked collections to make C2 a linked sub-collection under C1 and ensure that the advert applies to sub-collections.
Jason | http://blog.configmgrftw.com | @jasonsandys

Two ODSs share the same InfoSource but with different updata mode load?

We've got two different ODSs (ODS1 and ODS2) for two respective clients (client 1 and client 2). Client 1 has already going alive and in the InfoPackage, we only pick up ODS1 (Client 1) as feeding target and we have conducted initial load and several times of Delta loads for ODS1 (data load daily). But now we are going to start to load data to ODS2 (Client 2) and at the same time we will have to continue our delta load to ODS1.
It could not be possible that the two ODSs will be feeded data with different pace (ODS1: continue delta load, ODS2: initial load) if they share the same InfoSource. Then what's the best way to resolve this issue?
Thanks

hi Pradip,
Tell you a bad news that the solution doesn't work on two of the EBP (a source system which is similar to R3, we've got 4 EBP ODS/InfoSources, but two of the four don't work with the last step listed below) ODSs/InfoSources. The steps I took on production are:
1. Conduct Full Repair data load to ODS2;
2. Delete init option of ODS1 from Scheduler menu;
3. Run Init without data transfer to set delta pointer for both ODS1 and ODS2.
But the last step to run Init without data transfer has taken 1 whole day and eventually becomes red since it takes so long time to set delta pointer.
When I said our solution worked is that I conducted the test on our GL ODS and the Init without data transfer took about 1 hour to finish.
Also when we conduct the last step to do the Init without data transfer to click Start button to set pointer, a msg box titled "Activate ODS Data" pops up saying that "No requests have been selected for activation. Do you want to make a selection, or activate all the requests?" with buttons "Activate all requests", "Select requests" and "Cancel". If clicking the button "Select requests", another msg box pops up to prompt to input a Date range, we didn't input any date range, just click continue, then the Init without data transfer will run forever!
Thank
Message was edited by: Kevin Smith

Multiple SAP systems in MSCS

Hello,
We would like to install an ECC 6.0 and a CE in a cluster MSCS of two nodes.
I've found the SAP documentation "Installation of Multiple SAP Systems in MSCS: Oracle" but the doc version is 03/30/2007. Could you please tell me wether there is a new version of this document? or where can I find more documentation about this?
Is it recommended to create a domain between the cluster nodes? We're going to have 3 MSCS clusters with two systems in each cluster, should I create a domain for the three clusters, one domain per cluster or no domain at all?
Thanks and regards,
Ana.
Edited by: systems2111 on Feb 3, 2010 9:46 AM

Hello Shailesh,
The scenario is the following:
- MSCS between ECC and CE.
- MSCS between Solution Manager and nothing.
- MSCS between Websphere and SAP Business Objects
Every MSCS has two machines. for example, ECC will run on one machine, CE oon the other machine and in case of problems the cluster will run the ECC in the CE node.
I don't know if I have explain myself, but, anycase, please ask me with your doubts.
Regards,
Ana.

The same InfoSource in multiple SAP systems?

Similar Messages

Maybe you are looking for