Archive for June 8th, 2006

XI: Alerts - Step by step by Michal Krawczyk

XI: Alerts - Step by step
Michal Krawczyk
Business Card
Company: BCC
Posted on Sep. 09, 2005 10:57 AM in
SAP Exchange Infrastructure (XI)

Permalink

Print. Print

Using alerts can help us so much with the monitoring of the Exchange Infrastructure.
But why are they so avoided (aren’t they)? It’s true that they can be a little hard to configure at the first place
but if you succeed it can save a lot of your valuable time by telling you only about the events/errors you have to take care of.Alerts within XI give us a simple way to monitor only those errors that we want and send alert messages
to different people depending on the alert category. You can send alert to alert inbox, mail an even on SMS
if your cell phone operator gives you the possibility of sending an sms through a web service.

In this weblog I’ll provide you with a step by step tutorial on how to create and use alerts.

Step 1

At first we have to create an alert category:

- go to TCODE - ALRTCATDEF

- change mode

- define you alert category

image

Step 2

Next we can add some variables to our container which we will later use to compose the text of our alert message.

image

In alerts from XI you can use those variables:

SXMS_MSG_GUID, SXMS_RULE_NAME, SXMS_ERROR_CAT, SXMS_ERROR_CODE,
SXMS_FROM_PARTY, SXMS_FROM_SERVICE, SXMS_FROM_NAMESPACE, SXMS_FROM_INTERFACE,
SXMS_TO_PARTY, SXMS_TO_SERVICE, SXMS_TO_NAMESPACE,SXMS_TO_INTERFACE

for their ABAP dictionary types please go to:

Creating Alert Categories

Step 3

Now we can use our variables from the container to create an alert message.

image

Step 4

In order to receive alerts we have to add ourselfs to the receivers list.

image

Step 5

This is the end of the configuration in sapgui and now we can start working with RWB (Runtime Workbench).

- log on to RWB

- choose Alert configuration

- create a new alert rule

image

In my example I want to see all of the errors but you can restrict it to receive only mapping errors for instance.

Step 6

We’re ready to try our alerts but to check them we first need an error :)
I just gave a wrong XML to one of the processes and as you can see I managed to trigger a mapping error.

image

Step 7

Now you can go to the alertinbox to see if the alert was triggered:

- you can do it from RWB - Alert inbox

- or from sapgui TCODE - ALRTINBOX

image

This weblog shows how you can create a new alert rule in less then five minutes but only if your system is properly configured.
If you have any problems with Alert configuration please take a look at:

XI: Alerts - Troubleshooting guide

Michal Krawczyk is a SAP consultant for BCC (Business Consulting Center) Poland

Add comment June 8th, 2006

Introduction to Mobile Sales Application for Laptops by Santosh V.

Introduction to Mobile Sales Application for Laptops
Santosh V SAP Employee
Business Card
Company: SAP Labs India
Posted on May. 23, 2006 12:57 PM in
Mobile

Permalink

Print. Print

SDN has very limited information about Mobile Sales Application for Laptops. This was one of the main motivations for starting this WebBlog. My plan is to give more information about the application, the features and simple steps to customize the application. I will also be sharing some tips and tricks. To start off, this article deals with the basics of Mobile Sales Application.
A Sales Representative or a Service Representative is always on the move and may not be able to be connected to the server every moment. The representatives also have less time on their hands. These conditions make it necessary for any solution for a Sales / Service Representative to have the following characteristics -

  • Should be a solution for a Mobile device like laptop, PDA etc.
  • Easy to use user interface.
  • Faster to create a transaction.

A solution which satisfies all these characteristics is a SAP Mobile Laptop Application. Mobile Laptop Application is basically a solution which can be used by a Sales / Service Representative when interacting with customers and which works in a disconnected environment (with a provision to synchronise whenever connection is established). It is also easier and quicker to create documents in the laptop solution (this obviously requires a trimming of certain non-critical functionalities when compared to CRM Online).
The various Mobile Applications available for laptop are - Mobile Sales, Mobile Service and Mobile Service R/3 Edition.
Mobile Sales - It provides the functionality which can be used by a Sales Representative. The transactions which are possible are Activities (with provision to synchronise to Microsoft Outlook and Lotus Notes), Opportunities, Sales Transactions (like Sales Order, Sales Quotation etc.) and Marketing Transactions (like Trade Promotion, Campaign etc.).
Mobile Service - It provides the functionality which can be used by a Service Representative. The transactions which are possible are Service Orders, Service Assignments, Service Confirmations and Service Contracts.
Mobile Service R/3 Edition - It also provides the functionality which can be used by a Service Representative. But the difference is that the data is sent to R/3 and not to CRM Server (though CRM Server is required for data exchange). The transactions which are possible are Service Orders, Service Notifications and Confirmations.
It is also possible to generate Reports (the format of which can be customized) in the Mobile Application.
In addition to these applications, Mobile Authorization Management Tool is used to restrict / allow access to certain users to certain transactions in the above applications. The synchronization with the CRM Server is done through an application called Conntrans.
My next blog will be about the general architecture of the framework of Mobile Applications for Laptop.

Santosh V is a Development Lead for SAP Labs India. He has been working in the CRM Mobile Applications for Laptop area for close to 3 years. He has a total experience of 6 years in the software industry. He also specialises in developing Web Applications using ASP and ASP.Net.

Add comment June 8th, 2006

What’s new in SAP NetWeaver 2004s? - An introduction to the functionality deltas and major changes by Michael Eacrett

What’s new in SAP NetWeaver 2004s? - An introduction to the functionality deltas and major changes
Michael Eacrett SAP Employee
Business Card
Company: SAP Labs, LLC
Posted on Jun. 07, 2006 05:39 PM in
ABAP, Application Server, Business Intelligence (BI), Business Process Management, Business Process Modeling, Business Solutions, Change Management, Composite Application Framework (CAF), Enterprise Portal (EP), Enterprise Service Architecture, Integration and Certification, Interoperability, Interoperability .NET, Interoperability IBM, Java Programming, Knowledge Management (KM), Master Data Management (MDM), Mobile, SAP Exchange Infrastructure (XI), SAP NetWeaver Platform, SAP xApps, Technologies, Visual Composer, Web Dynpro

Permalink

Print. Print

So SAP NetWeaver 2004s is finally out in the open in unrestricted shipment (as of the 6th of June 2006). After a joint Ramp-up with mySAP ERP 2005, we are finally happy to make the software available to everyone. I can assume that you have a lot of questions about this release, and I hope this weblog will be a good introduction to this latest release. Just remember there are SAP NetWeaver 2004s highlight pages on SDN and the official SAP NetWeaver product homepage on the SAP Service Marketplace (http://service.sap.com/netweaver)

So what is SAP NetWeaver 2004s?

First of the all I have to explain what the little ‘s’ is all about? Well, the primary focus of the new features and deltas delivered in the SAP NetWeaver 2004s release are focused on the specific needs of the mySAP Business Suite applications. Therefore it is not considered a major SAP NetWeaver release but a minor special ‘s’uite release - specific suite features made to the SAP NetWeaver ’04 release. Don’t stop reading here… some of the new features and deltas are quite major when viewed alone and you can definitely leverage nearly all the features in your own SAP NetWeaver implementations.

When is SAP NetWeaver 2004s supported until?
SAP NetWeaver 2004s is supported under the 5-1-2 maintenance model so the end of mainstream maintenance is scheduled for March 31, 2011

How do I get SAP NetWeaver 2004s?
There are a couple of ways to get the SAP NetWeaver 2004s software. First of all it should be clear that it is not automatically shipped to customers, it has to be ordered. You can order SAP NetWeaver 2004s install or upgrade software from your SAP Account Executive or from the SAP Service Marketplace (downloadable from there too if you have such a contract!). In addition all the SAP NetWeaver 2004s software will automatically ship with software kits for the latest mySAP business suite applications (mySAP ERP 2005, mySAP CRM 2005, etc). Finally if you purchase SAP xApps based on SAP NetWeaver 2004s, you will get the software that way too!
All the SAP NetWeaver software shipped in the next months will be based on SR1 so you’ll start with have some reduced patching benefits.
For some SAP Customers, you will end up with many copies of SAP NetWeaver 2004s in the near future! Maybe time to consider using the CD recycling option that the kits offer! :-)

What are the major changes in SAP NetWeaver 2004s?
There are three main groupings of what’s new:

  • New concepts
  • Platform for first shipments of Enterprise services
  • New features and deltas to existing functionality1. New Concepts:
    For a minor release the concept changes in SAP NetWeaver 2004s are quite radical and will take some thought, head scratching, and in all honesty, some time to get your head around. There is more information the concepts uploaded to the SAP NetWeaver 2004s page on SDN.

    ‘No More Components’
    Yes! The component view of SAP NetWeaver has gone as of the SAP NetWeaver 2004s release. SAP will no longer use components to segregate SAP NetWeaver functionality, or use it for Sales licensing view, the installation view, or the implementation view. The removing of the components completes the roadmap of delivering a single SAP NetWeaver platform at SAP.
    This has been a little controversial when covered in a prior weblog. I have seen the classic 5 phases of grief (Denial, Anger, Bargaining, Depression, and Acceptance) expressed directly or indirectly but unfortunately they are gone and there’s not much we can do about it … Change is always a challenge for everyone (SAP included) and it is good, in my opinion, that SAP introduces such radical changes in a minor release but I digress.
    So this leads to the what has replaced them topic:

    Functionality and Implementation view: The introduction of the IT Practice and IT Scenario concept. This is a very easy to understand concept for assigning the features and functions with the tasks that IT actually do. You will see that SDN is already changing in this direction with their IT Practice and IT Scenario pages: https://www.sdn.sap.com/irj/sdn/developerareas/itpractices
    IT Scenarios are further broken down into manageable and implementation units call IT Scenario variants.
    You can see a holistic view of all delivered IT Scenarios from the SAP NetWeaver technology map

    Installation view: With SAP NetWeaver 2004s we install and deploy parts or all of SAP NetWeaver based on installable units. There are 3 installable units used in SAP NetWeaver or applications based on SAP NetWeaver 2004s onwards – they are technical ‘Usage types’, ‘Standalone Engines’ and ‘clients’. You can probably guess that ‘Usage types’ are the largest units you can install and represent large building blocks that can then be used to implement IT Scenario variants. For more information on the installable units, please consult the SAP NetWeaver 2004s Master guide
    located in the SAP Service Marketplace (https://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000626763&_SCENARIO=01100035870000000202&)

    Sales licensing view: You will see SAP NetWeaver platform licensing, engine licensing, and user licensing. I’m not a expert in this area so I would suggest you contact your SAP NetWeaver Account Executive or SAP VAR for more information.

    2. Platform for first shipments of Enterprise services
    SAP NetWeaver 2004s is the platform powering the first Enterprise Services that SAP is shipping in Q3 2006. This basically means that SAP NetWeaver 2004s provides the core technology for delivery, enablement, and consumption of Enterprise Services. Enterprise Services(ES) are the key building blocks for implementation of SAP’s vision of Enterprise SOA. I will not dive into this topic further as there is ample knowledge on SDN already on ES and even hosted systems to preview and play with the services (if you can’t wait for the SAP Discovery System for Enterprise SOA)

    3. New features and deltas to existing functionality
    Now we get to the most interesting part of the new release. What does it do? In this section I will give an outline of the major changes and links to other weblogs from other colleagues on their specific IT Scenarios. Remember there is more detailed information in PDF on the SAP NetWeaver 2004s page on SDN. Further very detailed information is available in the online help for SAP NetWeaver 2004s – just remember that there are no more components and therefore the release notes are organized by IT Scenario! Don’t say you were not warned! :-)

    Major changes:
    Even though SAP NetWeaver 2004s is billed as a minor release, there are a number of areas where there are significant new features and deltas. Please note that some (not all!) of the features are back-ported to SAP NetWeaver ’04 (these are highlighted in the documents on the SDN page above):

    BI Capabilities:

  • Enhanced query, analysis, and reporting with integration of the BEx frontend into Portal capabilities. Exciting additional new features include the BI Kit for SAP Visual Composer and the new Excel features such as drag and drop. This is definitely not your old BEx from the 3.x days!
  • A new integrated business planning feature has been delivered. This new feature is seamlessly integrated with exist data warehouse objects and query tools.
  • Enhanced Enterprise Data Warehousing features include new objects for modeling and implementing EDW layers, the new administration cockpit for managing the data flows in your EDW, and lastly the new BI Accelerator feature enables ridiculously fast and high performance analytics
    Portal capabilities:
  • A new feature called Federated portal networks enables you to manage distributed portals as a single local unit. This feature is a godsend for those who will have multiple installations of the Portal capabilities of SAP NetWeaver and most likely on differing releases.
  • External facing portals enable you to reuse your existing SAP NetWeaver based portal investments for delivering extranets and servicing occasional low touch users.
    Development capabilities:
  • Web Dynpro for ABAP. Yes, by popular request the previously available WebDynpro for Java feature has been delivered on the ABAP stack. So if you have major ABAP investments, you can now deliver WebDynpro applications with minimal investments in J2EE.
  • There is a new “Switch Framework” feature delivered that helps to deliver support for multiple industry solutions in a system faster – nearly all the IS solutions are available for mySAP ERP 2005 from the day it was released. In addition this gives the developer access to more business functions via the ‘Enhancement Framework’.
    image
    As I mentioned previously, my colleagues have written weblogs on the new features and deltas in their respective IT Scenarios. You can find them as follows (if one is missing – it is coming soon!)IT Practice: User Productivity Enablement
    Running an Enterprise Portal: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3697
    Enabling User Collaboration: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3568
    Business Task Management: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3698
    Enterprise Knowledge Management: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3677

    IT Practice: Data Unification
    Enterprise Data Warehousing: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3730

    IT Practice: Business Information Management
    Business Planning and Analytical Services: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3737
    Enterprise Data Warehousing: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3730
    Enterprise Knowledge Management: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3677

    IT Practice: Business Event Management
    Business Task Management: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3698

    IT Practice: End to End Process Integration
    Enabling Application to Application Processes: https://weblogs.sdn.sap.com/cs/junior/view/wlg/3738
    Business Task Management: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3698

    IT Practice: Custom Development
    Developing, Configuring, and Adapting Applications: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3720

    IT Practice: Unified Life Cycle Management
    Software Lifecycle Management: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3663
    SAP NetWeaver Operations: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3711

    IT Practice: Consolidation
    SAP NetWeaver Operations: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3711
    Enterprise Data Warehousing: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3730
    Enterprise Knowledge Management: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3677

    And so there you have it, a somewhat brief introduction to what’s new with SAP NetWeaver 2004s.
    I hope this weblog was worthwhile and enjoy the new release.

  • Michael Eacrett is a SAP NetWeaver Product Manager.

    Add comment June 8th, 2006

    What is the IT Scenario ‘Enterprise Data Warehousing’ about? by Alexander Peter

    What is the IT Scenario ‘Enterprise Data Warehousing’ about?
    Alexander Peter SAP Employee
    Business Card
    Company: SAP AG
    Posted on May. 31, 2006 11:58 AM in
    Business Intelligence (BI)

    Permalink

    Print. Print

    One of the major challenges Business Intelligence (BI) customers face today is the integration of different source systems in one Enterprise Data Warehouse landscape. Not only different heterogeneous technical platforms must be interfaced, but also different master and transaction data semantics must be consolidated. In addition, an Enterprise Data Warehouse must provide flexible structures and layers in order to adapt quickly to new business challenges (such as changed objectives, mergers, acquisitions, etc.) Beyond these designtime aspects, Enterprise Data Warehousing should facilitate the administration and monitoring of all processes (such as load processes, distribution of data etc.) and proactively help coping possible performance issues – especially regarding increasingly sophisticated data volume requirements.The IT scenario Enterprise data warehousing (EDW) enables customers to create and operate a data warehouse in an enterprise-wide environment. It combines strategic analyses and operational reporting, enables the business to report real-time, integrates heterogeneous systems and facilitates designtime as well as runtime of BI models and processes.
    EDW covers all steps an administrator requires to set up a highly flexible, reliable, robust and scalable BI solution and easily administrate it.

    Scenario Variants:

    • Modeling the enterprise data warehouse
      Describes processes like data modeling, data acquisition, data cleansing/transformation, data distribution and meta data & document management.
    • Running the enterprise data warehouse
      Describes processes like controlling the data flow, administration and monitoring, performance optimization (including BI accelerator), information lifecycle management and user management (authorizations).

    Here is a list of the most important new capabilities; for further information, please refer to the IT scenario overview:

    • BI accelerator
      Boosts query performance by orders of magnitude and cuts off administration costs
    • Admin Cockpit
      Provides overview on BI processes (data load and queries) at one glance
    • New data flow
      New data flow design capabilities such as transformation and DTP supply additional flexibility and performance
    • New analysis authorization concept
      The new authorizations concept provides additional flexibility and improves transparency
    • Real-time data acquisition
      Enables operational reporting by providing information in real-time

    Alexander Peter has been with SAP since 1997. Current position: product manager SAP NetWeaver BI with focus on EDW and performance.

    Add comment June 8th, 2006


    Calendar

    June 2006
    M T W T F S S
    « May   Jul »
     1234
    567891011
    12131415161718
    19202122232425
    2627282930  

    Posts by Month

    Posts by Category