Web Dynpro ABAP
WDA Tutorial I: Getting Started with Web Dynpro for ABAP SDN Community Contribution (This is not an official SAP document.) Disclaimer & Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or
[Read the rest of this entry...]
Web Dynpro for ABAP: Tutorial 2 – BAPI Usage SAP NetWeaver 04s 19.12.2005 Copyright © Copyright 2005 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program
Bertram Ganz, Jochen Gürtler, Timo Lakner Maximizing Web Dynpro for Java 077.book Page 3 Wednesday, August 2, 2006 11:29 AM Contents at a Glance 1Introduction…………………………………………………………….. 15 2 Web Dynpro Architecture Concepts ……………………………. 19 3Web Dynpro GameStation………………………………………… 29 4Web Dynpro Gogle Search………………………………………. 115 5 Web Dynpro and SAP NetWeaver Portal …………………….. 151 6 Web Dynpro NavigationTester …………………………………… 197 7 Web Dynpro OBNTester ……………………………………………. 263 8Web Dynpro MusicBox……………………………………………… 289 9 Generic Development Components …………………………….. 343 10 Tips for the Installation, Configuration, and Administration …………………………………………………… 363 A Web Dynpro Componentization …………………………………. 467 B Web Dynpro in the SDN ……………………………………………. 481 CThe Authors……………………………………………………………… 489 Index ………………………………………………………………………. 491 077.book Page 5 Wednesday, August 2, 2006 11:29 AM 7 Contents 1 Introduction …………………………………………………………….. 15 2 Web Dynpro Architecture Concepts ……………………………. 19 2.1 Architecture Concepts ………………………………………………….. 20 2.2 SAP NetWeaver System Landscape …………………………………. 23 2.3 Summary and Perspective ……………………………………………… 26 3 Web Dynpro GameStation …………………………………………. 29 3.1
Sample ABAP Code For BDS for Excel Document. Author : Rachmad Kurniawan ( SAP Consultant ) – Indonesia T-Code OAOR. Assigning new class name to Class Type using t-code SBDSV1. PROCESS BEFORE OUTPUT. MODULE M_STATUS_9000. * PROCESS AFTER INPUT. MODULE M_USER_COMMAND_9000. REPORT zsd8001. TABLES: nast, kna1, likp, lips, mchb, vbfa, vbpa, t001l, t005t, tvstt. INCLUDE zabxixls. TYPES: BEGIN OF ty_pick, vbeln LIKE likp-vbeln, vstel LIKE likp-vstel, vtext LIKE tvstt-vtext, werks LIKE likp-werks, plant LIKE t001w-name1, lfdat LIKE likp-lfdat, lddat LIKE likp-lddat, vbelv LIKE vbfa-vbelv, cname LIKE kna1-name1, stras LIKE kna1-stras, ort01 LIKE kna1-ort01, pstlz LIKE kna1-pstlz, landx LIKE t005t-landx, END OF ty_pick. DATA: BEGIN OF t_mtrl OCCURS 0, werks LIKE likp-werks, matnr LIKE lips-matnr, arktx LIKE lips-arktx, lfimg LIKE lips-lfimg, ntgew LIKE lips-ntgew, lgort LIKE lips-lgort, lgobe LIKE t001l-lgobe, END OF t_mtrl. DATA: x_pick TYPE ty_pick, t_line TYPE STANDARD TABLE OF tline WITH HEADER LINE. DATA: d_adrnr LIKE vbpa-adrnr, d_name1
Tutorial on SMART FORMS © 2005 SAP AG 1 Applies To: SAP R/3 4.6C – ABAP / SMART FORMS. Summary SAP Smart Forms are used to create and maintain forms for mass printing in SAP Systems. As an output medium SAP Smart Forms support a printer, a fax, e-mail. Many a times there is requirement to download output of SAP Smart Forms in a PDF file. This piece of code gives users a demo for creating and downloading Smart forms to their local PC. By: Swaroopa Vishwanath Company and Title: Wipro Technologies, SAP ABAP/XI Consultant Date: 11 Feb 2005 Table of Contents Applies To:……………………………………………………………………………………………………………………….1 Summary …………………………………………………………………………………………………………………………1 Table of Contents ……………………………………………………………………………………………………………..1 Introduction:……………………………………………………………………………………………………………………..2 Creation of SMARTFORM:…………………………………………………………………………………………………2 Global Setting ……………………………………………………………………………………………………………….2 Form attributes …………………………………………………………………………………………………………..2 Form Interface……………………………………………………………………………………………………………2 Pages and windows:………………………………………………………………………………………………………3 Graphics:…………………………………………………………………………………………………………………..3 Date Window……………………………………………………………………………………………………………..4 Main window………………………………………………………………………………………………………………4 Address …………………………………………………………………………………………………………………….4 Generate Function Module for Smart Form ………………………………………………………………………….5 Downloading Smart Form to PDF from Application ……………………………………………………………….5 Sample Code …………………………………………………………………………………………………………….6
Copyright © 2000 ARAsoft GmbH (http://www.arasoft.de). All rights reserved Thomas G. Schuessler, ARAsoft GmbH: “SAP Java Connector” Tutorial Introduction SAP’s new Java middleware, the SAP Java Connector (JCO) allows customers and partners to easily build SAP-enabled components in Java. JCO supports both inbound (Java calls ABAP) and outbound (ABAP calls Java) calls in desktop and server applications. Goal and Scope of This Article Before JCO, there was an interface called “Common RFC Interface for Java” (CRI4J) that had been implemented by HAHT, IBM, and SAP. This article does not assume any experience with CRI4J. If you have built CRI4J-based applications without proxies before, you can learn how to convert them to JCO by reading the article Converting “Common RFC Interface for Java” Applications to the New “SAP Java Connector” after or instead of this one. Future articles will discuss the proxies generated for the JCO middleware and how to convert
SAP Business Connector Developer Tutorial SAP System Release 4.7 SAP AG – Neurottstr. 16 – D69190 Walldorf 2 ! ! ! SAP BC Developer Tutorial 4.7 Copyright ©Copyright 2003 SAP AG.. All rights reserved. No part of this description of functions may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft® , WINDOWS® and EXCEL®, NT® and SQL-Server® are registered trademarks of Microsoft Corporation. IBM®, OS/2®, DB2/6000®, AIX®, OS/400® and AS/400® are registered trademarks of IBM Corporation. OSF/Motif® is a registered trademark of Open Software Foundation. ORACLE®, is a registered trademark of ORACLE Corporation, California, USA. webMethods® is a registered trademark of webMethods Incorporated, Virginia, USA. INFORMIX®-OnLine for SAP is a registered
Reference: 2005/04/26 Adapter Tutorial Tutorial 3 : Invoking SAP BAPI through the Oracle AS Adapter The Oracle AS Adapter for SAP exposes the SAP BAPIs and RFCs as a Service via WSDL with JCA binding. This tutorial describes how to invoke a SAP BAPI interface and query the inverntory given Material ID. The BPEL process is a synchronous request-response service that invokes the SAP BAPI_MATPHYSINV_GETDETAIL API. Tutorial 3 : Invoking SAP BAPI through the Oracle AS Adapter………………………………………………………………………………………………………………..1 Overview…………………………………………………………………………………………………………………. 1 Configuring the Oracle AS Adapter for SAP ……………………………………………………………….. 1 To start Oracle AS Adapter Application Explorer……………………………………………………… 1 Configuring a BPEL process to invoke the SAP Service ……………………………………………….. 4 Deploying & Testing the BPEL Process………………………………………………………………………. 8 Overview The Oracle AS Adapter for SAP is part of the Oracle AS Adapter install. The Oracle as Adapter for SAP can be deployed as both a webservice Servlet as well as JCA 1.5 Resource Adapter.
V H D L – 2 0 0 6 – D 3 . 0 T u t o r i a l A g e n d a : Accellera Standards D ennis Brophy I E E E S t a n d a r d s E d w a r d R a s h b a V H D L T u t o r i a l J i m L e w i s A c c e l l e r a – V H D L – D 3 . 0 Fixed and Floating Point Packages W h a t s N e x t I n V H D L Q u e s t i o n s & A n s w e r s Accellera VHDL-2006-D3.0 By Jim Lewis, SynthWorks VHDL Training jim@synthworks.com S ynth W orks Accellera VHDL-2006-D3.0