IDOC Type & Message of release 4.5

DOWNLOAD HERE

All Idoc Type & Message release 4.5 for Download.

SAP- Abap Programming for Download

Get e-book for SAP BC - ABAP Programming

DOWNLOAD HERE

How To transport Standard text

1. Go to report RSTXTRAN. (Transfer of SAP script Texts to a Correction).
2. Key-in/ insert object name that you’ve create in standard Text (SO10) at Text key-name
3. Click on Execute button (F8)
4. Click on Continue Button (Enter)
5. Click on Trsfr texts to corr button (F5) . Click YES on pop-up screen.
6. Create transport Request and Save.
   

How to Transport Request Number?

1. Go to transaction SE10.

2. Click on button Display.

3. Set the cursor into Transport Number that will be too transported. After that click on icon lorry .(released directly or press F9)

Upload Excel Data to SAP: 7 Best Practices

By Vikram Chalana
Even with the standardized business processes and centralized data stores provided by SAP, much corporate data still resides in spreadsheets. Taking data in these spreadsheets and putting them into SAP remains one of the thorny challenges facing many corporate IT departments. Many business departments are

wasting resources in manually reentering this data into SAP while introducing errors due to manual data entry. Functional and technical analysts in the IT departments are inundated with requests from business users to automate the upload of Excel data into SAP.
• Are you an SAP business user looking to reduce manual data entry for mass uploads or mass changes to SAP data, particularly when the data already exists in Excel?
• Are you an IT functional or technical analyst looking for ways to service the end-user requests for data uploadd more effectively?
• Are you looking for ways that your company can save time and resources in SAP data management?
If you answered “Yes” to any of the above questions, then this article is for you. This article describes 7 best practices in automating the upload of Excel
data into SAP. Adopting these best practices will alleviate many of the pains that business users and IT analysts face in uploading Excel data to SAP.
1. Avoid Programming. With the several non-programming choices available to connect Excel and SAP, custom programming in ABAP or VB should be the absolute last resort for ad-hoc uploading Excel data to SAP. Not only programming is
expensive and time consuming, a program that will be used only once or even once a year is particularly wasteful. Further, creating robust programs require a fair bit of testing and if a program has not been well-tested, it could be dangerous and cause irreparable data damage.
Use a scripting or a non-programming approach as much as possible. SAP provided tools such as BDC, CATT, LSMW, and third party tools such as Winshuttle’s TxShuttle will allow you to avoid programming to a large extent.

2. Do not Upload Directly to SAP tables. While this point is very obvious, it
cannot be overemphasized. Writing directly to SAP tables avoids all the data
validation and checks and balances that happen when creating data through the
normal SAP transactions. So, avoid using any method that writes directly to SAP
tables.
Always upload data via the pre-configured SAP transactions or BAPIs. Again,
using tools such as BDC, CATT, or LSMW, or TxShuttle will allow the upload of
data via SAP transactions instead of writing directly to SAP tables.
3. Choose a Record, Map, and Run strategy. A record, map, and run strategy
generally involves first recording an SAP transaction where data needs to be
uploaded. The recording step is followed by a mapping step where the SAP data
fields captured during the recording are mapped to the Excel fields. Finally,
the transaction is run over and over again with the different rows of data in
the Excel file. A Record, Map, and Run strategy is similar to recording and
running macros for automating routine tasks.
The advantages of choosing a record, map, and run strategy are that (a) it is
very general and can work well for many different upload tasks and many
different SAP transactions, even with custom transactions, (b) it is a very easy
and intuitive approach and saves a lot of time making a mass data update, (c) it
is something that even the business users can do themselves without requiring
much IT support.
A record, map, and run strategy should be used for uploading data from Excel
to SAP. Again, the SAP provided tools, such as BDC, CATT, and LSMW all support
such a strategy and can work for many different upload applications. The
TxShuttle tool simplifies the mapping recording and mapping tasks a lot and
makes it even easier for business users. Also, for applications that require
upload of transactional data containing header and line-items, such as journal
vouchers, invoices, purchase orders, sales orders, etc., the TxShuttle tool has
features that make it really useful.
4. Choose a Secure and SOX Compliant Method: Make sure the method you choose
is secure and preserves SAP’s role-based security. In these days of
Sarbanes-Oxley (SOX) audits, this point cannot be overemphasized. One key aspect
of section 404 is checking that rights and duties are separately assigned to
different individuals so that no individual has the power to divert business or
transactions in a fraudulent manner. One of the most common open SOX audit
issues is that users in the IT departments have very broad access to production
data in SAP. Therefore to ease compliant with SOX, any mass changes or uploads
should ideally be performed by the business users who are already authorized to
make the change.
To allow business users to perform the upload via SAP-provided
transaction-based tools, they would need extra authorizations to use these
tools. If your company is not able to provide such authorizations, the use of
Winshuttle’s TxShuttle product may be more appropriate since it lives outside
the core SAP system and generally does not require extra authorizations.
5. Keep the data in native Excel format. If the data to be uploaded stays in
the native Excel format, rather than being converted to comma-delimited or
tab-delimited text file formats, it makes the upload process much simpler. One
less step for the users to worry about.
The use of Winshuttle’s TxShuttle product allows the users to keep their data
in native Excel format.
6. Select an outside-in approach: The two approaches to bringing outside data
into SAP are: (a) an inside-out approach where the data import tools live inside
SAP are used to bring outside data into SAP, and (b) an outside-in approach
where the tools living outside SAP are used to bring outside data into SAP. An
inside-out approach typically requires all the data import scripts and programs
to live inside SAP and therefore need to be maintained as SAP versions are
upgraded, even when the scripts are one-time-use only. Thus, these one-time use
scripts clutter the SAP system when using the inside-out approach. An outside-in
approach offers a cleaner alternative that can be used with the user’s existing
security profiles.
The announcement of Microsoft and SAP’s joint product, Mendocinno,
recently validates the importance that both companies give to an outside-in
approach. Other add-on products such as TxShuttle also take an outside-in
approach to connect to SAP.
7. Empower business users: On a final note, one of the best practices in
uploading Excel data to SAP is to empower business users to do the upload
themselves. The choice of the right tool for the business users which will
enable them to easily upload data without requiring any programming will go a
long way to freeing up IT resources for more mission-critical applications.
Letting business users take control of their own data also makes SOX compliance
easier.
An easy to use product such as Winshuttle’s TxShuttle which will let business
users upload their own data from Excel to SAP allows the empowering of these
business users.
In summary, the best practices in uploading Excel data to SAP proposed here
involve choosing non-programmatic, easy-to-use approaches, and this will enable
your company to save large amounts of time and resources in day-to-day SAP data
management.

To learn more about SAP tools, BDC, CATT and LSMW, visit
http://www.sap.com.
To learn more about Winshuttle tool, TxShuttle, visit
http://www.winshuttle.com.
At this site, you can download a FREE WHITE PAPER
describing this problem and how the TxShuttle tool works at
uploading Excel data to SAP.

You can also download a FREE 15-day evaluation version of the TxShuttle software for connecting SAP and
Excel.

Vikram Chalana is the SAP product specialist at Winshuttle, Inc. He has helped many clients automate their SAP business processes, in particular processes dealing with the connecting spreadsheets and SAP. He has been in the IT industry as a data minining, business intelligence, business process automation expert for over 10 years.

To learn more about Winshuttle, please visit http://www.winshuttle.com

Article Source: http://EzineArticles.com/?expert=Vikram_Chalana

Performance Trace in SQL For ABAP

To obtain an overview of the behavior of the R/3 System, you can record various processes during the execution of an individual object. To analyze performance problems with database accesses, activate the SQL trace and the buffer trace from transaction ST05.

The SQL trace records SQL statements. There may be considerable differences between the SQL statement formed on the ABAP level and the SQL statement that is received by the database.

A buffer trace lets you trace SQL statements that access buffered tables. SQL statements that access buffered tables can cause buffer reloads, which are indicated in a buffer trace. An SQL statement accessing a buffered table can result in a completely different SQL statement if it cannot be satisfied by the R/3 table buffer.

Additional tools include: the enqueue trace, which records enqueue requests or releases, indicating the enqueue key and the object involved; as well as the RFC trace, which records the RFC calls received or sent.

Initial screen :

To access the SQL Performance Trace, use transaction ST05 or from the R/3 initial screen, choose System ® Utilities ® SQL Trace.

Before activating an SQL Performance Trace for a report or a transaction, you should execute the report one time to prevent the buffer load process for the R/3 table buffer, the R/3 program buffer, and so on, from being included in the subsequent trace.

The trace can be activated in the production system without any risk of creating errors or inconsistencies.

The trace can be activated by any user and for any object. When activating the trace, ensure that you are not using multiple user sessions or running other processes such as background jobs or update processes under the same user ID on this application server. These activities would make the SQL Performance Trace difficult to interpret.

For each application server, there is only one active trace file. Therefore, on a given application server, only one user can activate a trace. The default size of the trace file is 800 KB. SAP recommends increasing the size of the trace file to 16 MB by setting the parameter rstr/max_diskspace to 16 384 000.

Overview of sql trace:

The R/3 database interface receives an SQL statement from the ABAP program and converts it to an SQL statement that can be processed by the database.

For each database operation, the SQL trace measures the time taken from the sending of the request to the database server to the receipt of the results for the request on the application server via the R/3 database interface (including the time spent in the network between the application server and the database server).

The data written to the trace file includes the database response time, a time stamp, the number of transferred data records, the database return code, the text of the SQL statement, and additional administrative information for each database operation.

http://testingcorner.blogspot.com http://abapreports.blogspot.com Article Source: http://EzineArticles.com/?expert=D_V_Suresh

SAP ABAP Performance Tuning Tips & Tricks

Need for performance tuningABAP is the universal language in the World of SAP programming and the focus is also on getting a team of efficient programmers as early as possible in each and every part of the project, both for handing over the technical specifications to them and also for asking them to toss out the ABAP programs within the “given deadlines” as well.

The key focus of assembling an efficient program takes a back seat since this force has a greater pressure of schedules along with deliveries to accomplish successful outcomes. Also an proficient ABAP program is one which brings the wanted output to the user in a finite time according to the complexity involved in the program, rather than hearing the comment “I put the program to run, have my lunch and come back to check the results”.

A performance optimized ABAP program saves the time of the end user, thus increasing the productivity of the user, and in turn keeps the user as well as the management happy leaving aside the hyperbole. SAP ABAP performing tuning tips and tricks are used for making the ABAP programs efficient in doing their work. This tuning tips and tricks also assume that the reader is well versed in each and every concepts and syntax of ABAP programming.

SAP Implementation Benefits SAP solutions embrace an extensive range of business domains, such as Financial Accounting Controlling, Asset Management, Project System, Human Resources, Quality Management, Production Planning and Sales and Distribution. We also help for small and mid-size firms that achieve profits and have significant advantages through SAP investment via our expertise in presenting SAP solutions.

Some SAP implementation benefits include:

• Gradual declination in the total cost of ownership
• Accomplishment of faster return on investment
• Imparting flexibility in business processes
• Inspection of entire business processes
• Integration, collaboration, planning, execution, and coordination of the complete supply chain network
• Achievement of consistent as well as apparent business insights
• Develop employee productivity
• Creation of a quality work environment
• Achievement of operational excellence and growth
• Exploitation of additional solutions with ease

Both SAP Implementation and SAP training are worth investing since it takes into account regarding the benefits it offers. Our partnership with leading application vendors permits us to convey competitive SAP advantages to our enterprising customers. Enterprises get in touch for the processing of SAP Consulting and SAP Upgrade solutions. We also offer its consulting, implementation and training services for the upcoming Microsoft Dynamic Business Solutions.

Ron Victor is a SEO copywriter for http://www.simplysap.com
He written many articles in various topics.For more information visit http://www.simplysap.com
Contact him at ron.seocopywriter@gmail.com

Article Source: http://EzineArticles.com/?expert=Ron_Victor