What are the major issues to consider in code review? Or performance analys

What are the major issues to consider in code review? Or performance analysis?

I would not recommend you to try to optimize performance by checking the coding.
There is the code inspector which can do all which makes sense automatically.
The above mentioned points are not the real issues.
Instead of code review you should execute test cases and measure the exection time.
1. With STAD if you want to get good time measurement
2. With SE30 and ST05, if you want to have data for further anaylsis.
Check total time (SE30), check whether DB part is large, then go to SQL trace. Do the check mentioned here
/people/siegfried.boes/blog/2007/09/05/the-sql-trace-st05-150-quick-and-easy
to find the SQL bottlenecks.
The major point about SQL problems is index support, if there is no proper index support then the performance will be poor. Be aware, that problems are only visible, if you tables are filled.
In a test system where you have very little data, you will never encounter performance problems.
Check also the Top10 of the SQ30 hit list.
Be aware that a proper performance analysis is not a 5 minutes job.
Siegfried

Similar Messages

Dear All,what are the major issues in implementation in sap hcm

what are the major issues in implementation in SAP HCM project scope is PA ,OM,TIME, INDIA PAYROLL

Hi Ramjan,
Try to have a clear understanding of requirements and find the best solution in SAP. Keep as much as possible everything standard and based on SAP best practices.
In PA look for a comprehensive enterprise structure. It's base for everything.
DON"T do anything through development(ABAP code) as much as possible specially in PT and PY. Try to do claculation by PCRs and Schema.
Regards,
Omid

What are the major issues in implementation SAP CRM sales and CIC.

Hi
We are newly implanting the project to the mobile Manfaturing Company. Our Clint is going for are looking to implement the CIC interaction center win Clint and the Sales modules of CRM .
We have some 3rd parry raw data with us with that raw data we are calling to the customers and we want create the opportunity in the CIC after that we will convert the opportunity as a sales with our other sales people. After that they will sale that product to that customers.
We have the back end of the R/3 SD, MM modules implemented for Clint.
Now 1) I want to know after implementation what are the major issues will come in the project normally for the conman Sales and CIC Win Clint projects kindly give the some issues normally come and solutions for the problems also.
My motto is that if I know the issues I can make preparation for that conman issues and I will make my project with good effective and smooth running ..
with Regards,
prakesh
Edited by: prakesh on Dec 9, 2009 6:04 AM

hi prakesh,
firstly, cic winclient is an older version and obsolete so its better to implement the new crm version.
secondly, in any case if you want to implement, then your 3rd party raw data has to be mapped with the SAP system which could be a problem. Middleware could be a lot of effort. Rest all depends on how much customization you need for your business requirement in cic and sales. In case you are implementing standard functionality mostly then no major complications are expected otherwise lot of development effort may be required.
regards
shikha

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

What are the major components in class?

1)     What is the purpose of load-of-program? When it will be trigger?
2)     Write the code for displaying the three parameters in single line with the first parameter as mandatory in the selection screen?
3)     Which event triggered whenever the user call the function BACK, EXIT, CANCEL?
4)     What are the major components in class?
5)     What is the functional module is used to get popup screen for ALV reports?
6)     Which type of pool is used to get drop-down list?
7)     What is the tcode for creating the variant truncations?
8)     Is it possible to call LDBs number of times in same report?
9)     What are the conditions to use control break statements in our report program?
10)     What is the use of range statement?
11)     What is the difference between normal reports and alv reports? With comparing to normal report are there any disadvantages in alv reports?
12)     What are the components used to suppress the fields in the selection-screen?
13)     What is the standard program to transport selection screen variants?
14)     What is the event keyword for defining event block for reporting events?
15)     What is the specific statement use when writing a drill down report?
16)     What are the different tools to report data in sap?
17)     Write the menu path to create a selection text in reports?
18)     How do we omit the leading zero s while formatting outputs in reports?
19)     What are the report truncations?
20)     How do we align selection input in single row?
21)     How do we suppress the display of input fields on selection screen?

this forum is not for answering your interview questions...if you stucked with any realtime problem then post...please try to respect forum terms and conditions.
Thank you.

What are the major differences b/w R/3 4.7 and ECC 6.0 with SAP BW/BI

Hi,
Any one can give an idea about the conversions from SAP R/3 to ECC 6.0 with respective of SAP BI/BW.
what are the major differences loading the data,delta methods,enhancements,lo's,FI-SL,CO-PA etc.....
if any one have documents and links please can you share it is very usefull for my client.
with out knowing i don't want to go forward,i don't misguide my client.
actually i am working as sap bw/bi consultant,my client is going to upgrade the R/3 4.7 to ECC6.0 and BW 3.5 to BI 7.0.can you help me or guide me .
Thanks in advance.
SAP Member......

Check
http://service.sap.com/releasenotes
http://erp.fmpmedia.com/
Markus

What are the major risks buying used lenses ?

i just bought my first dslr, and i was wondering what are the major risks buying used lenses ?

You need to be able to inspect and test the lens.
Look for obvious signs of physical damage, drops, etc. (cracks, dents, etc.) A lens normally will get some signs of wear but as it's a used lens, you expect *some* wear... you're really looking for signs of damage.
Remove both front and rear caps. Look through the lens into a bright no-contrast background (a white wall, a blue sky, etc.) and check the optics. You're looking for signs of mold growth or damage to coatings. Minor dust on internal optics wont impact the lens performance... so while you wouldn't want major amounts of dirt... don't worry too much about minor bits of dust (I've actually helped prove this to someone by clipping a 3M PostIt note down to a tiny 1/4" x 1/4" size and sticking it on the front glass. Take a photo... nothing shows in the photo (even a piece of "dirt" that big wont show because the camera cannot focus on anything that close to the lens.)
Rotate the focus ring from end to end. You should feel a smooth and consistent amount of friction as you rotate the focus ring. There should be no rough spots. Listen to the lens as you do this... there should be no grinding noises.
Do the same with the zoom ring but in addition to checking for smooth consistent performance (no sticky or rough spots) you're also checking to make sure nothing seems excessively worn (nothing wobbles loose... very heavily used lenses can do that after enough wear.)
Connect the lens to the camera and make sure the camera can completely operate the auto-focus motors without a problem and/or if it's an image stabilized lens that the IS components are working.
Set the camera to max aperture (e.g. f/22, f/32.. depending on the lens) and press your camera's "depth of field preview" button (if you don't know which button is your DOF preview, check your manual. Canon tends to move that one around a bit but it's almost always on the front side of the camera near the lens mount.) You want to press and release it a few times. This will cause the lens aperture blades to stop down to the aperture you set. Release... do this while watching the lens. You should see the aperture blades move in and out (well... they snap in and out very quickly). You want to make sure it works ok, the camera gets no error codes, and there's no signs that anything is sticking.
And then there is the focus test...
Focus the camera preferably at a FLAT surface that has lots of detail.... such as the brick wall of a building. Make sure the camera is level and that the camera's focal plane is parallel to the plane of the wall. Take a test photo at low f-stop and inspect. You're checking to verify that the focus works and that the focus is reasonable across the image. As you inspect from left ot right and top to bottom you are looking to make sure the focus is more or less equal (if the right side of the image is focused... but the left side of the image is soft... it would indicate that lens elements are skewed (lens isn't collimated). It's difficult for a lens to get into this situation unless it was dropped and you'd probably see signs of damage.
Tim Campbell
5D II, 5D III, 60Da

What are the major differences between hana 2013 and 2014 release

Hi Guys,
I am planning to learn sap hana and write certification exam. As sap release new platform 2014, may I know what are the major deference between 2013 and 2014 release or its just enhancement pack on top of 2013.
Please help me....thank you in advance.
Regards,
Tapas

Hi,
Good morning and greetings,
Please use the following link
http://solutionbrowser.erp.sap.fmpmedia.com
Please reward points if found useful
Thanking you
With kindest regards
Ramesh Padmanabhan

What are the major differences between the 4.7 and ECC5 or 6   ?

Hi Abapers,
                        Can anyb one answer this question ....
what are the major differences between the 4.7 and ECC5 or 6    ?
Thank's,
Siri

Tan,
we have solution for this question on previous pages.

What are the major differences b/w live copy blueprint and Language copy of CQ ?

We are in process of creating a different Language Versions of a Website and trying to figure out the best/recommended approach.
what are the major differences b/w live copy blueprint and Language copy of CQ ? which one is recommended in which ? any pointers on this would be appreciated.

The language copy tool is a one-shot tool to create pages under a certain structure. It has a nice UI for it. But that's it.
The MSM blueprint/livecopy concept is much more powerfull, because it has live connections between the blueprint and the livecopy. It does not only allow you to easily create livecopies, but supports you also in maintaining the relationshop between these. So you can easily detect, that the blueprint page has been updated and needs to be rolled out again. Or that there are conflicts, because both blueprint and livecopy have been updated independently. And so on.
From my perspective the language copy tool should not be used, because with creation of language pages the "fun" has just started and the real work is just ahead.
Jörg

What are the major differences between BODS and Talend ?

Hi Friends,
We had a client meeting 2 days back regarding BODS project, But our client is showing more interest on Talend. We have explained/demo him on BODS. Could any one please tell me, What are the major differences between BODS and Talend ? What are the features of BODS which are not there in TELEND ?
Thanks,
Bheem.

Hi,
If you talk difference than Talend is an open source. SAP DS as huge advantage when it comes to loading data into SAP and it is more flexible with lots of inbuilt features and easy to load data into SAP using DS directly and extracting data from various legacy systems.

What are the major logic steps of WL Portal Server process a portal request

Hi,
I comes from IBM and we provided a product to monitor most types of J2EE App Server about transactions and performance.
we will monitor WebLogic Portal Server in next release.
So would you please tell me:
How Weblogic Portal handles a page request from browser, what are the major logic steps that a page requests are fulfilled, which areas in Weblogic Portal are most likely to cause response time problem. For example, We monitor WebSphere Portal Server as the following major steps:
Portal Page loading, Model building, Page rendering, portlet action, etc....
we look forward to get your developer helps since we cann't find related documents over your website.
Thank you very much
Edited by wutingbin at 12/28/2006 12:35 AM

WebLogic Portal, if Desktop enabled, it will render from Desktop->Portal->Books->Pages-->Portlets. You can get these information from WebLogic E-Docs.

What are the major differences between oracle 10g and oracle express 10g

Hi
Can anyone tell, What are the major differences between[b] oracle 10g and oracle express 10g.
Or if you know any URL, then please do let me know.
Advance Thanks
JC

Dear sir,
here it is.
http://www.oracle.com/database/product_editions.html

What are the major differences b/w DTP & Infopackage

HI Experts,
what are the major benifits of DTP over Infopackages???? also what are the major differences b/w them ????
Cheers
Swaps

Since you are talking of DTP's, I assume you are working on BI 7
In BI 7:
Infopackage- is used to pull data from the source system to the PSA. PSA is compulsory in BI 7. Beyond this infopackage doesn't play any role.
DTP: DTP's are used to transfer data from one data provider to another.
it can be
PSA - DSO/Cube
Cube - CUbe
DSO - Cube
DSO - DSO and so on
Hope this helps
Godhuli

What are the major differences between 4.7 and ecc5.0

hi all
What are the major differences between 4.7 and ecc5.0
regards
JK Rao

Hi,
Good morning and greetings,
Please use the following link
http://solutionbrowser.erp.sap.fmpmedia.com
Please reward points if found useful
Thanking you
With kindest regards
Ramesh Padmanabhan

What are the major issues to consider in code review? Or performance analys

Similar Messages

Maybe you are looking for