SAP 2000 Tutorial Session Notes – Professor Buyukozturk
1.051 Structural Engineering Design Prof. Oral Buyukozturk Fall 2003 SAP 2000 Tutorial Session Notes This tutorial provides the basic steps of performing a frame analysis using SAP 2000. It is based on the design project example shown below, the complete solution of which is provided as a handout. 16@21′ 26′ 34′ 26′ 20′ 5@13′ 15′ Results of Preliminary Analysis: Slab thickness: 9 in Beam dimensions: 14”x31” Exterior columns: 14”x18” Interior columns: 16”x22” Loads: Exterior beams: LL=0.72 kips/ft DL=1.85 kips/ft Interior beams: LL=0.83 kips/ft DL=2.10 kips/ft Wind and Earthquake loads are specified in the appendix. Only earthquake loads are considered. The frame is solved in the short direction only since this direction is more critical. 1.051 Structural Engineering Design Prof. Oral Buyukozturk Fall 2003 Analysis Steps 1. Generate the frame geometry from analysis templates. Menu: File > New model from template Result Note: make sure that proper units are selected (shown
[Read the rest of this entry...]
Business Objects Enterprise XI 3.1 .NET SDK Runtime Deployment Business Objects Enterprise XI 3.1 .NET SDK Runtime Deployment Copyright ©2008BusinessObjects,anSAPcompany.Allrightsreserved.BusinessObjects owns the following U.S. patents, which may cover products that are offered and licensed by Business Objects: 5,295,243; 5,339,390; 5,555,403; 5,590,250; 5,619,632; 5,632,009; 5,857,205; 5,880,742; 5,883,635; 6,085,202; 6,108,698; 6,247,008; 6,289,352; 6,300,957; 6,377,259; 6,490,593; 6,578,027; 6,581,068; 6,628,312; 6,654,761; 6,768,986; 6,772,409; 6,831,668; 6,882,998; 6,892,189; 6,901,555; 7,089,238; 7,107,266; 7,139,766; 7,178,099; 7,181,435; 7,181,440; 7,194,465;7,222,130;7,299,419;7,320,122and7,356,779.BusinessObjectsand its logos, BusinessObjects, Business Objects Crystal Vision, Business Process On Demand, BusinessQuery, Cartesis, Crystal Analysis, Crystal Applications, Crystal Decisions, Crystal Enterprise, Crystal Insider, Crystal Reports, Crystal Vision, Desktop Intelligence, Inxight and its logos , LinguistX, Star Tree, Table Lens, ThingFinder, Timewall, Let There Be Light, Metify, NSite, Rapid Marts, RapidMarts, the Spectrum Design, Web Intelligence, Workmail and Xcelsius are trademarks or registered trademarks in the United States and/or other countries ofBusinessObjectsand/oraffiliatedcompanies.SAPisthetrademarkorregistered trademark of SAP AG in Germany and in several
SAP Tutor SAP T U T O R Release 1.4 SAP Online Help 09.07.02 SAP Tutor 620 2 Copyright © Copyright 2002 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®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® 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®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE® is a registered trademark of ORACLE Corporation. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks
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
SAS/ACCESS ® 9.1 Interface to SAP BW User’s Guide The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2004. SAS/ACCESS ® 9.1 Interface to SAP BW: User’s Guide. Cary, NC: SAS Institute Inc. SAS/ACCESS ® 9.1 Interface to SAP BW: User’s Guide Copyright © 2004, SAS Institute Inc., Cary, NC, USA ISBN 1-59047-232-2 All rights reserved. Produced in the United States of America. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc. U.S. Government Restricted Rights Notice. Use, duplication, or disclosure of this software and related documentation by the U.S. government is subject to the Agreement with SAS Institute and the restrictions set forth in FAR 52.227–19 Commercial Computer Software-Restricted Rights (June 1987). SAS Institute Inc., SAS
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
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
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
Getting more out of the WebSphere SAP Adapter Use the SCI/Inbound BAPI interface to import BAPI test data into WebSphere Integration Developer Skill Level: Intermediate Samanvitha Kumar (samanvitha.kumar@in.ibm.com) Staff Software Developer IBM 03 Jun 2009 This tutorial provides a series of tasks to import BAPI test data from the SAP GUI into WebSphere® Integration Developer, using the Synchronous Callback Interface provided by the IBM WebSphere Adapter for SAP. Section 1. Before you start This tutorial shows how you can use Synchronous Callback Interface (SCI) to transfer Business Application Programming Interface (BAPI) test data from the SAP® GUI into the WebSphere Integration Developer (hereafter called Integration Developer) environment. Application developers may have used the SCI/Inbound BAPI interface several times in SAP integration projects, but not many have realized its full potential. This tutorial takes a fresh look at SCI and helps developers reduce the time to build and test SAP integration