Mostrando las entradas con la etiqueta English. Mostrar todas las entradas
// //

FAQ: SAP Query

[1] When is a conversion required?

You must perform a conversion after a release upgrade from 3.1x to Release 4.0x or higher or after a client copy if necessary.
           * After a release upgrade, proceed in accordance with Note 92124.
           * Start report RSAQUM40 after a client copy and set the "release indicator".

[2] Copying between query areas

You can call transaction SQ03 and choose the menu path "Environment" -> "Transports" to copy the query objects between query areas. You can copy queries from the standard area (client-specific) to another standard area using export/import.

[3] Finding quick views

Quick views are user-specific objects. To make a quick view generally available, you must convert it into a query. To do this, go to transaction SQ01 and select a corresponding user group. Choose the menu path "Query"->"Convert QuickView" to copy the quick view to a query that is accessible to all users in the user group. Since quickviews are client-specific objects, this function can be used only within the standard area of the query.

[4] Starting a query via a transaction

Calling a generated query source code (AQ* report) from transaction SE38 or using transaction SE93 can result in errors if the query was not generated after a change or the corresponding program was not found. Calling via the function modules described in Note 393160 avoids these errors or generates the query before the call.

[5] Assigning a query to another InfoSet (extended copy functions)

The standard copy functions of transactions SQ01 and SQ02 were extended by report RSAQCOPY. For example, you can copy an InfoSet including all dependent queries or copy a query into another InfoSet. For more information, see Note 324393.

[6] Report-report interface interface (BBS)

You can use the report-report interface to go directly from the output of the data selected by the query (sender) to the corresponding application transaction (receiver, for example VA03). The system transfers the data from the query to the selection screen that was called if possible. You can also use the query itself as a receiver for other selections. For more information, see Note 50629.

[7] Inconsistency in query objects

Changes in the ABAP Dictionary (change in field length or field type) may result in problems when generating the functional area and/or query. First adjust the InfoSet via transaction SQ02 and the menu path "InfoSet" -> "More functions" -> "Adjust". You can then adjust the query using transaction SQ01 and choosing the menu path "Query" -> "More functions" -> "Adjust".

For more information

[8] For more information about displaying technical fields using the background TECH command in the ok_code, see Note 443727.

[9] For more information about this topic, see Note 451216. 

This note provides you with an exact method of analyzing whether duplicate lines are really issued.

[10] The system has the settings: "Changes to cross-client objects are not allowed".

a) Creating or changing in the global query is not possible with this setting.  Queries and Infosets should be created in the development system or Quality assurance system and should be transported from there to the production system.
b) Infosets and queries can be created in the standard area.

[11] Queries can be called using transactions (see Note 393160). 

Only specific function modules take the role assignment (SAP_QUERY_AD_HOC_ROLE) into account. Transaction PAAH calls the function module SAP_CALL_QUERY_AD_HOC, which does not take the role assignment into account. Instead of using this transaction, you should call the Ad Hoc Query using the SAP Easy Access menu (see Note 761160).

[12] The standard selections are generated dynamically by the ABAP runtime. 

This depends on the segments of the logical database that you use. For this reason, we cannot guarantee that the additional source code is correct for each query that is based on this InfoSet. Therefore, you cannot access standard selections.

Inmortalizado desde h_tp:// pero ya no existe!
Leer más ...
// //

Mobile SAP Portal

In the last years people are talking more and more about mobile access to SAP information. Today, in most cases people mean apps when they talk about mobile access. These apps are created for a device. You can have apps for Android iPhone / iPad or Blackberry, just to name a few. As apps are getting their data out of the internet, you could also use a mobile browser to access that data. Apps offer superior integration for the device, offline access and sync, but they also need maintenance. And they need to get developed, for every device. For online access, you can use the browser installed on the device to consult (or to approve) actual data.

As SAP has a strong position in this market - specially now with Sybase - there is one SAP product that almost never get's mentioned when talking about mobiles: the SAP Portal. WebDynpro Java offers support for some mobile devices, but it doesn't offer portal features like:

  • portal profiles and user management
  • navigation
  • content management
  • central place for maintenance

I want to share with you some screenshots that demonstrate that it is possible to access the SAP Portal and to interact with backend system. I used the device / browser simulators provided by Blackberry (OS 5) and Opera (Mobile 10). A "normal" user that logs on to the portal get presented with portal content.


It isn't possible to run the same portal content on the mobile, the content administrator has to make sure that the mobile end-user will see only adapted content. Instead of creating a mobile only portal or mobile only users, the portal offers the desktop filter functionality for this. The same user can see different content based on the filter ID of the desktop.

The standard portal logon works also on mobiles, but it is too large for a mobile screen. I developed a simple HTML form that fits the small mobile screen.

Opera Mobile


Leer más ...
// //

ABAP Data Dictionary Overview

ABAP Dictionary centrally describes and manages all the data definitions used in the system and the database. It is completely integrated in the ABAP Development Workbench. ABAP Dictionary supports the definition of user-defined types i.e. data elements, structures and table types. These types are used in the ABAP processors and ABAP programs. It also defines the structure of database objects i.e. tables, views and indexes.

In this document, you will get an overview of ABAP dictionary and predefined data elements.


  1. Unirte a la lista #1 de SAP +1, sumate ahora!
  2. Dale "me gusta" a nuestra página de Consultoria-SAP en Facebook.

    Y no te olvides de seguirnos en las redes sociales para no perderte ninguna novedad:
  3. Copia la URL de éste artículo, e ingresa al foro de Ayuda SAP en español, ve a la parte de Manuales-SAP, y abre un tema nuevo explicando por qué te interesa aprender más sobre SAP, pega ahí la URL que has copiado, para que sepamos que estás cumpliendo estos tres puntos.

    Recuerda que en nuestra comunidad de Ayuda SAP no es solo "pedir" y nada más, lee las normas de solicitudes que tendrás que cumplir para descargar gratis.

    No te pierdas los beneficios de ser VIP en Consultoria-SAP
Leer más ...
// //

Financial Experts: Useful Tips

FI Tips:
  • Why are my invoices not selected in F110 ?
  • How to zero out an account balance in local currency ? (FBB1)
  • How to post to a VAT account ? (FB41)
  • Modifying Header Text in Line Item Reports
  • Drill Down Reporting in SAP FI

Why are my invoices not selected in F110?

Often times users in SAP are puzzled by why a certain vendor's invoices are not selected by the payment run. There may be many reasons for this and I will cover them in a subsequent issue but today, I will touch on one reason that is easy to identify and resolve. When running a payment proposal SAP blocks the
vendors whose invoices have been selected in another proposal. The savvy user will check the payment proposal log where he will be able to see vendors that are blocked by another proposal. In this case I have run a proposal on the 18th but for some reason vendor 1000's invoices are not showing up.
By pressing the proposal log button from within the payment run, Figure 1, the proposal log will be displayed, Figure 2. When examining the log, I will easily see that, that vendor 1000 is contained in a different proposal. At this point I have two options, either complete the other proposal or delete it to release the blocked invoices.

Leer más ...
// //

Introduction to ASAP Methodology

ASAP Methodology
AcceleratedSAP methodology is proven, repeatable and successful approach to implement SAP solutions across industries and customer environments.
It provides content, tools and expertise from thousands of successful implementations.

Phase 1: Project Preparation:
During this phase the team goes through initial planning and preparation for SAP project.
Define project goals and objectives
Clarify the scope of implementation
Define project schedule, budget plan, and implementation sequence
Establish the project organization and relevant committees and assign resources

Phase 2: Business Blueprint:
The purpose of this phase is to achieve a common understanding of how the company intends to run SAP to support their business. Also, to refine the original project goals and objectives and revise the overall project schedule in this phase. The result is the Business Blueprint, a detailed documentation of the results gathered during requirements workshops.

Phase 3: Realization:
The purpose of this phase is to implement all the business process requirements based on the Business Blueprint. The system configuration methodology is provided in two work packages: Baseline (major scope); and Final configuration (remaining scope). Other key focal areas of this phase are conducting integration tests and drawing up end user documentation.

Phase 4: Final Preparation:
The purpose of this phase is to complete the final preparation (including testing, end user training, system management and cutover activities) to finalize your readiness to go live. The Final Preparation phase also serves to resolve all critical open issues. On successful completion of this phase, you are ready to run your business in your live SAP System.

Phase 5: Go Live & Support:
The purpose of this phase is to move from a project-oriented, pre-production environment to live production operation. The most important elements include setting up production support, monitoring system transactions, and optimizing overall system performance.

Leer más ...
// //

What is the function of OBYC?

What is the function of OBYC?

Function of the OBYC stand for Configure Automatic Postings.In this step, you enter the system settings for Inventory Management and Invoice Verification transactions for automatic postings to G/L accounts.
Postings are made to G/L accounts automatically in the case of Invoice Verification and Inventory Management
transactions relevant to Financial and Cost Accounting.
For example, Posting lines are created in the Stock account and Consumption account.

Nota de Actualización

Este artículo está publicado está en inglés y archivado.
Si usted necesita más información sobre la información expuesta en el mismo, le ruego use nuestro foro de ayuda SAP para evacuar las dudas que tenga.

Disculpe las molestias.

Otros artículos SAP

Leer más ...
// //

The command &SAP_EDIT

No matter security on table editing. When in transaction SE16N use the command &SAP_EDITin the command field in SAP and off you go: edit table content directly. This works if you have debug with changes access for object S_DEVELOP, but S_TABU_DIS is ignored as well as the system settings regarding changes. If you use this function for transaction, master data or other tables that cannot be changed with SM30, you can cause quiet some damage.  So, use with caution and this is NOT a Best Practice by all means, but to educate you on a little documented feature:
Step 1: Use transaction SE16N or transaction N (yes, there is a transaction called just ‘N’)  and enter a table of your choice, for example SKA1 G/L Account Master (Chart of Accounts)
Leer más ...
// //

Custom transaction for Report Painter

In many organizations, the usage of transaction GR55 has been removed from end users and the usage of custom transaction for Report Painter report is preferred.

These transactions need to be added to roles & also transported via the SAP Transport system and go through change control.

One mistake is to create Variant Transactions that add another layer of objects to maintain and transactions that are not easily accepted by the end user community:


The user will then have to navigate past the selection screen where the report group is selected.


Another common mistake is that users create the transaction code with the SAP-generated program name of the Report Painter report.


The users usually runs the report and via the menu path system status identifies the SAP generated report name, such as GP4D9W908VD93NG59JGEC5C4HE3200 in the development system or in the productive system as GP4D9W908VD93NG59JGEC5C4HE3400. Both program names look identical except for the last 3 digits, which represent the client in which the report was generated.

Because you don’t have control over the SAP-generated program name, you run into problems when the user tries to execute the program and a short dump may occur or the system may tell the user that the program doesn’t exist.

The right approach is to create a Parameter Transaction, map this transaction to the necessary objects in SU24 so that you can make sure that you won’t run into any authorization issues when the user runs the reports.

To create a custom transaction, you need to use transaction SE93 in the development client where your program development & configuration takes place.

Enter a transaction with the naming convention that your organization has issued and select the ‘create’ button:


Enter a short description (according to naming standards of your organization) and select the option ‘Transaction with parameters’:


Enter transaction ‘START_REPORT’ as shown below (1) and select the ‘Skip Initial Screen) (2):


In the lower section, enter Screen Field D_SREPOVARI-REPORTTYPE with the value RW for Report Writer and D_SREPOVARI-REPORT for your report name. If you should have extended a extended report name, you also can add this screen field with the appropriate value D_SREPOVARI-EXTDREPORT to the list of screen fields.


After saving the transaction, the system asks you for a package & transport request. Follow the development standards & instructions from your organization.

Once you have created the transaction, you need to make sure that it will be fully functional from a SAP Security standpoint. Use transaction SU24 to map the object S_Program to the transaction you have just created. The authorization group is the name of the Library with the prefix of RW_. You can find out the library via the report group or by running a trace. (This is helpful if you did not create the report and don’t know what library the developer was using).


If you want to run the authorization analysis via ST01, you can find out easily what the values for S_Program should be:


Once you have identified the objects & values, you can then map the object to the transaction with transaction SU24:


Add all objects needed to run this report (you can find out the objects via your trace analysis):


Switch the indicator to check/maintain:


Enter the values according to your findings


Don’t forget to double-check the values. You may want to make selections regarding on how the user can run the report according to your company guidelines and development standards:


When the SAP Security Administrator maps the newly created transaction to a role, the objects needed for this transaction will be automatically pulled into the role:


Depending on your SAP Security setup, the values of the individual authorizations for Report Writer may be more granular or with access to a broader area.

Reblogged from

Leer más ...
// //

Secure Programming Guidelines

You know the Secure Programming Guidelines but you want to do more? Well, here are my top priority security recommendations for developing secure ABAP applications:

New database tables

  1. Assign table authorization group Usually you create 3 table authorization groups per application:
    a) for customizing tables (C)
    b) for master data and transaction data or other application data (A)
    c) for system data (S)

    You can use the report RDDPRCHK (or RDDTDDAT_BCE) to analyze the settings. Use transaction SM30 for view V_BRG_54 to maintain authorization groups respective view V_DDAT_54 to maintain authorization group assignments. Maintain authorization groups Maintain authorization group assignments
  2. Set the maintenance flag, which controls SE16 am SM30, correctly Data Browser/Table View Maintenance
  3. Activate table logging for customizing table or create a change document object for master data. You can use the report RDDPRCHK (or RDDTDDAT_BCE) to analyze the settings. Check the settings of profile parameter rec/client and the tp parameter RECCLIENT, too. Activate/Deactivate Table Change Logging  Note 1916 Logging table changes in R/3  Note 84052 R3trans: Table logging  
  4. Create specialized SM30 maintenance views instead of offering maintenance using SE16 and add additional authorization checks if required. Create a Maintenance Dialog Event 25: At the Start of the Maintenance Dialog 
Leer más ...
// //

Checking SAP R/3 tablespaces

SAP tcode DB02 is use to check database size, tablespaces size, current statistic, checking freespace statistic, analyze detailed tablespace, checking missing indexes, and space critical objects. Actually, we can do more than that.
Leer más ...
// //

EPM: the story

All about the next release of EPM - what's the story?

With so much happening in the SAP world these days, and so little information necessarily forthcoming, what really is the scoop on EPM?  Here's a little bit of an insider view into that world....
The Enterprise Performance Management (EPM) suite of products has gathered some momentum over the past number of months and is picking up speed as we move towards the launch of the next release.  What's it all about, though?

A little background
The EPM suite has generally included two focus areas.  The first is Financial Performance Management (FPM), which includes the following core products:  SAP BusinessObjects Profitability and Cost Management (PCM), which was originally acquired by BusinessObjects from ALG Software; SAP BusinessObjects Strategy Management (SSM), which was acquired from Pilot Software by SAP; SAP BusinessObjects Financial Consolidation (FC), formerly Cartesis and acquired by BusinessObjects; the corresponding SAP BusinessObjects Intercompany (IC) too; and SAP BusinessObjects Planning and Consolidation (BPC), formerly OutlookSoft, acquired by SAP.  BPC, for those who aren't familiar, is offered on two platforms:  the original MS SQL Server platform leveraging MS Analysis Services and also on the SAP NetWeaver platform, which leverages the BW data warehouse layer.  Additionally, there is an ETL layer tool (for extraction, transformation and loading) named Financial Information Management (FIM).  FIM leverages the BusinessObjects EIM (Enterprise Information Management) tools, specifically Data Services.  FIM provides a finance-friendly layer for data movement and manipulation among EPM tools and into EPM from SAP and non-SAP source systems.
The second area of focus for EPM is Operations Performance Management (OPM), which includes Spend Performance Management (SPM), Supply Chain Performance Management (SCPM), and Sales Planning.  The OPM suite of products is not governed by the EPM 10.0 initiative you may have been hearing about; the direction of OPM products is tracking separately from the FPM products.

Leer más ...
// //


Basically there is no real difference. It is just about marketing name of same products. SAP PI or XI is SAP NetWeaver based technology for Enterprise Application Integration (EAI). EAI software enables different systems to communicate each other. This cover systems within same organization or systems of external parties. That type of software is so called Integration Brokers as they are mediates between entities with varying requirements in terms of connectivity, format, and protocols. It provides common repository for all interfaces. Central component of XI/PI is the SAP Integration Server, which facilitates interaction between diverse operating systems and applications across internal and external networked computer systems.

When was SAP XI/PI introduced into the market and how it all began? There was always a demand for integration software within SAP’s costumers and always lack of it on SAP side. Since SAP had no strong experience within integration software they teamed up with WebMethods Company (in 2009 acquired by Software AG) and introduced SAP Business Connector (known as SAP BC). This happened around year 2000. SAP BC was branded version of webMethods Integration Server as a middleware solution for SAP R/3. In 2002 joined team were split and both companies continues to develop their product lines independently. SAP released SAP BC version 4.7. Approximately at same time SAP as having experience learned with SAP BC started with own integration / middleware product called Message Broker. This was renamed later to SAP Exchange Infrastructure (XI). Later (around year 2006) within SAP NetWeaver the name was changed from XI 3.0 to SAP Process Infrastructure (PI 7.0).

What is future of PI? Actually it is been little bit cloudy. Gartner and other analysts are saying that SAP’s statements about PI are clumsy and therefore they do not advise costumers to use it for strategic projects. This was strengthening even more by SAP’s acquisition of SOALogix. Therefore for sure there will be changes in PI as integration of BPM software is never easy. But SAP says that they are strongly committed to SAP PI.

Something about SAP: SAP PI vs. XI
Leer más ...
// //

Certification Exam

Taking the Certification Exam
The SAP certification exam is designed to be challenging; take my word for it! Most are offered as a 3-hour exam (breaks are optional), with 80 questions and typically a 55% pass-rate... Think about it, that's about 2 minutes per question (excluding breaks), and each question is a complex multiple choice (e.g. a question can have one or more answers out of many, and most questions are scenario-driven). Given that amount of time, and necessity of thinking through questions methodically and carefully, you will need to be very prepared.

Worst case, you can take the exam up to three times per year, with an elapsed interval between each retake (rules might have changed already, so don't quote me on that). In any case, below are some tips on how to prepare for the exam and use techniques during the exam to succeed.

> BREAKS Given the short amount of time, it is very hard to take a break. Inevitably, your body will need it, so try to plan for one break every hour; usually 2-3 minutes for a quick stretch and bathroom break works best.
> COUNT Keeping count of your answers is a handy method to gauge your possible pass-rate. If you feel 100% confident about at least 60% of the questions, then you are in a fairly good shape to get to the 60+% you need when doing the final review at the very end.
> FLAG Use the flagging functionality for questions you are not sure of. It is VERY helpful when revisiting questions at the end that your uncertain of.
> NOTES Use your note sheet to create diagrams of the scenarios presented in the questions. Also use it to keep count of confident/non-confident questions you answered.
> READ Read the questions very carefully; they are often scenario-based and you have to understand it very well before answering or considering the multiple choice answers.
> RELATIONSHIPS Believe it or not some questions have relationships to others, so it is good to keep a tab in your mind or note sheet of some of the more complex questions as others might be related and answers could be "deduced" if you are clever enough ;-)
> SCENARIOS Since most questions are scenario oriented, requiring some effort of thinking, try to play them out in your mind as if you were doing them in real life. This can often help confirm your answers.
> TIMING Keep time; watch the clock on the screen, and time yourself with your own watch. Remember to keep it short, quick and efficient per question; 1 to 1.5 minutes per question is usually a good strategy, this way you gather enough buffer time for breaks and doing a final review at the very end.
> TITLES The titles of every question often provide a good context for what to expect, so make sure you read the title/topic before reading the question.

Last, but not least... Prepare, Prepare, Prepare. Before taking the test review your notes and training material. It is often very helpful to review the summary sections of each unit; you will find most of the complex concepts documented there that are often used in the exams.

Keep studying, and best of luck!

Smile! =)
Leer más ...
// //

Log Analysis Tool for SAP NetWeaver

Log Analysis is an SAP tool for analyzing list formatted logs and traces in Application Server Java (AS Java). Initially, it was developed for the Logging Cleanup process but it can also be used for analyzing system logs from different scenarios. You can analyze several groups of logs (from several periods of the server operation) at the same time.
The tool is applicable for all SAP NetWeaver versions (from 6.40 to 7.20 and higher).

More info: SAP Community Network Wiki - Java Development - Log Analysis Tool for SAP NetWeaver AS Java
Leer más ...
// // 1 comentario

Don't Wait to Archive

Top 7 Excuses for Delaying SAP Archiving Projects and Why You Shouldn't Accept Them

Only one third of SAP customers currently archive data. Review the seven most common reasons for delaying archiving projects and learn how changing your archiving practices can improve performance.

Download this whitepaper from the Macro 4 SAP EcoHub storefront.

Leer más ...
// //

Reference to ABAP Basics

The following ebook is for the ABAP beginners giving an overview of basic topics in ABAP.

This reference guide focuses on following topics:
  • Role of ABAPer
  • Reports
  • Menu Painter
  • LSMW ( Legacy System Migration Workbench)


Nota de actualización

Este artículo se mantiene publicado a fines informativos, si usted necesita más ayuda sobre el mismo por favor use nuestro foro de ayuda.

Disculpe las molestias.

Leer más ...
// //

F110: Error in payment method

F110: Error in payment method selection without job log

The SAP system displays an additional log only for selected customers and vendors. If there is no specified any vendors or customers, the additional log is not displayed.
However, the payment method selection may fail due to various reasons. Since only one reason can be entered as an error indicator REGUP-POKEN, the SAP system can provide more detailed information about the last reason for error only.

The items receive the item indicator 006 with the text "No valid payment method found" in the proposal display or payment display or in the proposal list or payment list. This text is defined in message FZ 506. If the SAP system does not display the additional log, the reason for the error cannot be determined.
Leer más ...
// //

SM02 Message Problem

If SAP system messages which be created by SM02 transaction, are not display even the SAP system message still valid.

New users cannot display the current SAP system messages. The SAP system only displays system messages that were created after the first login of the user.

Next time logon by this user, the SAP system messages are not displayed to this user. This problem is caused by a SAP program error.

Leer más ...
// //

Tcodes for FI GL AR AP Asset

Financial Accounting   
SPRO    Enter IMG
OX02    Company Code - Create, Check, Delete
OX03    Create Business Area
OKBD    Functional Areas
OB45    Create Credit Control Area
OB29    Maintain Fiscal Year Variant
OB37    Assign Co. Code to Fiscal Year Variant
OB13    Creation of Chart of Account (CoA)
OBY7    Copy Chart of Account (CoA)
OBY9    Transport Chart of Account
OBD4    Define Account Group
OBY2    Copy GL Accounts from the Chart to Co. Code
OB53    Define Retained Earnings

Leer más ...
// //

SAP FI CO Reports

FI/CO Frequently Used Reports


S_ALR_87013611 Cost Centers: Actual/Plan/Variance
S_ALR_87013612 Range: Cost Centers
S_ALR_87013613 Range: Cost Elements
S_ALR_87013614 Cost Centers: Current Period/Cumulative
S_ALR_87013616 Cost Centers: Breakdown by Business Transaction
S_ALR_87013617 Range: Activity Types
S_ALR_87013618 Range: Statistical Key Figures
S_ALR_87013619 Range: Assigned Orders/WBS Elements
S_ALR_87013620 Cost Centers: Actual/Plan/Commitments
S_ALR_87013621 Range: Actual/Plan/Commitments
S_ALR_87013623 Cost Centers: Quarterly Comparison
S_ALR_87013624 Cost Centers: Fiscal Year Comparison
S_ALR_87013625 Cost Centers: Actual/Target/Variance
S_ALR_87013626 Range: Cost Elements
KSBL Cost Centers: Planning Overview
S_ALR_87013630 Activity Types: Plan Receivers
KSBT Cost Centers: Activity Prices

Leer más ...