Mais conteúdo relacionado
Semelhante a SUSE Technical Webinar: Build B1 apps in the Framework of the SAP and SUSE Campaign (20)
Mais de SAP PartnerEdge program for Application Development (20)
SUSE Technical Webinar: Build B1 apps in the Framework of the SAP and SUSE Campaign
- 1. SAP Business One and SAP HANA Integration
Eddy Neveux – Solution Architect – North America
2014
- 2. © 2013 SAP AG. All rights reserved. 2Public
Topic 3: User Interface API
Topic 4: SAP Business One Development Tools
Topic 1: Introducing SAP Business One SDK
Topic 2: Data Interface API
Topic 5: Add-Ons Packaging & Deployment
Topic 6: SAP Business One Integration Framework
Topic 7: SAP Business One on SAP HANA
Introducing SAP Business One Integration
- 3. © 2013 SAP AG. All rights reserved. 3Internal
A Complete Business ERP Solution Platform
The purpose of ERP is to facilitate the flow of information between all business functions inside the boundaries
of the organization and manage the connections to outside stakeholders
Enhance solution
enablement
for partners
Cover standard business
processes end-to-end
Orchestrate integration
and collaboration
Run completely in-
memory technology
Manage TCO
Extend the
solution scope
Full flexibility
on deployment
Aerospace – Automotive – Chemical - Consumer Products - EC&O - Food and Beverage – Healthcare – IMC - Life
Sciences – Manufacturing - Mill Products – Oil and Gas - Professional Services – Retail/AFS - Wholesale Distribution
- 4. © 2013 SAP AG. All rights reserved. 5Public
SAP Business One - Technology and Interfacing
SAP® Business One
Server
RDBMS
Integration
Services
Client
Interfaces
Continuous and integrated solution
Windows look & feel (SAP style)
Simple navigation
Ability to drill down to details
“Drag and relate” feature
Two-tier client-server architecture (fat client)
Microsoft Windows 32 based, 64 Bit supp.
Microsoft SQL Server / SAP HANA Server
Ease of Use
Product
Architecture
Customizing
Form Settings
Queries / Reports
User-Defined Tables and Fields
Linkage of input fields to queries
User-Defined Objects (UDOs)
Microsoft Excel, Word (out)
Microsoft Outlook (in / out)
Adaptations
MS Office
Integration
File-based (built-in)
XS Engine, Service Layer
APIs (COM, web services)
User-Defined objects (UDOs)
Integration (not only) to SAP systems
Interfaces
SDK (COM)
GUI
Email
Backup
Microsoft
SQL Server
/SAP HANA
SDK (COM)
SDK (DI Server)
License
- 5. © 2013 SAP AG. All rights reserved. 6Public
SAP Business One SDK - Motivation
Customization
capabilities are
powerful!
Customization
capabilities cannot
solve every
requirement.
Source code not
accessible!
Use SDK!
SAP
Add-Ons
Software
Development Kit
Partner
Add-Ons
SAP
Business One
- 6. © 2013 SAP AG. All rights reserved. 7Public
SAP Business One SDK – Terminology and Packaging
The SDK consists of 2 major packages:
The Runtimes (i.e. the APIs)
The runtimes (DI API + UI API) are installed together with the SAP Business One client
application
DI API can be installed stand-alone (separate installer package available)
The documentation (samples, helpfiles, utilities) named „SDK Installation“
- 7. © 2013 SAP AG. All rights reserved. 8Public
Topic 3: User Interface API
Topic 4: SAP Business One Development Tools
Topic 1: Introducing SAP Business One SDK
Topic 2: Data Interface API
Topic 5: Add-Ons Packaging & Deployment
Topic 6: SAP Business One Integration Framework
Topic 7: SAP Business One on SAP HANA
Introducing SAP Business One SDK
- 8. © 2013 SAP AG. All rights reserved. 9Public
SAP Business One SDK – Data Interface API
Provides objects and methods (add, update etc.) to work on data level – installing the SAP
Business One client application is not required
Provides access to business objects (e.g. master data and transactional data) and cross
functionalities (services)
Performs the same checks as the SAP Business One client application
Links existing third-party solutions “as-is”
Use COM capable development tools (e.g. Microsoft Visual Studio)
SAP Business One
Company
Database
DI API
(or JCo
or
DI Server)
UDO
3rd Party
Application
SAP
Business One
- 9. © 2013 SAP AG. All rights reserved. 10Public
DI API – Object Categories
Business Objects
Master Data Objects
BusinessPartners
Items
…
Transactional Data Objects
Journal Entries
Documents: Order, Invoice,…
…
Infrastructure Objects
Company object
Extended Functionality Objects
RecordSet
DataBrowser
SBObob
Meta Data Objects
UserTablesMD
UserKeysMD
UserFieldsMD
UserObjectsMD
Special Objects
Service Type Objects
CompanyService
AccountsService
BusinessPartnersService
FormPreferencesService
MessagesService
ReportLayoutsService
SeriesService
Definition Objects related to SAP
Business One GUI
ChooseFromList
DynamicSystemStrings
Formatted Searches
MultiLanguageTranslations
UserQueries
- 10. © 2013 SAP AG. All rights reserved. 11Public
Data Interface API – Use cases
There are a couple of scenarios where Data Interface API is engaged:
Data level integration of existing applications:
Easily read or write data from / to SAP Business One – when needed
Data Import / Export scenarios – which are not covered through SAP tools – and where the
capabilities of the SAP Business One application are not sufficient.
Depending on the architecture of the overall solution you might consider to use DI Server
though.
Handling data in an Add-On that uses UI API (see next unit) beyond UI API‘s capabilities.
Essentially writing data to the SAP Business One database by default requires usage of DI
API
Even though other techniques may be faster when it comes to reading data from the
database – usage of DI API is often a good choice regarding usability (no need to request
additional credentials etc) and data coherence (imagine that the required data might be
stored in various tables).
- 11. © 2013 SAP AG. All rights reserved. 12Public
The User Defined Object offers partners the ability to:
Add own Business Objects to the application’s object collection.
Use the set of services that the application offers, such as:
Connect a Form to the Object; use Find, Add, and Update modes and other predefined
services.
Optionally the predefined behavior of the services can be modified and extended
through implementing a class that inherits (C++) from a business object base class in a
DLL and overriding virtual methods.
SAP Business One supports two types of main Objects:
Master Data Object
Document Object
SAP Business One SDK – User Defined Object (UDO)
Object Collection
Add
Find
Remove
…..
New partner
object
Register the
object for
services
UDO
- 12. © 2013 SAP AG. All rights reserved. 13Public
Topic 3: User Interface API
Topic 4: SAP Business One Development Tools
Topic 1: Introducing SAP Business One SDK
Topic 2: Data Interface API
Topic 5: Add-Ons Packaging & Deployment
Topic 6: SAP Business One Integration Framework
Topic 7: SAP Business One on SAP HANA
Introducing SAP Business One SDK
- 13. © 2013 SAP AG. All rights reserved. 14Public
SAP Business One SDK – User Interface API
Provides objects and methods to access screen objects of the User Interface
Provides access to internal system events of the user interface
Provides ability to modify or add menus, windows, or fields
Provides one integrated user interface
Use COM capable development tools (Microsoft Visual …)
SAP Business One
Company
Database
Data
Interface
API
UserInterfaceAPI
UDO
3rd Party
Application
SAP
Business One
- 14. © 2013 SAP AG. All rights reserved. 15Public
User Interface API – Use Cases
User Interface API is usually used to:
Reach a „seamless“ integration of additional functionality with SAP Business One
(usually requested by customers)
…including hooking on SAP Business One standard processes
…including adding own GUI elements into SAP Business One standard forms
…including adding own forms and plugging the corresponding data behind
Manipulate SAP Business One standard functionality (when standard options do not
apply to the customer‘s processes (or the branch the customer works in))
…including hiding SAP Business One GUI elements
…including blocking SAP Business One events
- 15. © 2013 SAP AG. All rights reserved. 16Public
Inquiry
Vendor
Name
Contact Employee
Phone
Vendor Ref. No.
Inquiry No.
Inquiry Date
Item Number Item Description Quantity Price
Document Type
# Tax
Total Sum
Add Cancel
Inquiry Ref. No.
User Interface API
Control flow of applications
Change existing screen layout:
Add/Remove Controls
Change Control Properties
Add new screens
Add/Modify/Remove menus
Summary: UI API provides the capability for seamless integration maintaining the
uniform “look and feel” of SAP Business One
- 16. © 2013 SAP AG. All rights reserved. 17Public
UI API – Object Overview
Menus
Forms
Controls (“Items”) on
Forms
Connection Objects
SboGuiAPI
Application
Desktop
Menu
Form
Items
ComboBox
EditText
Matrix
Grid
ActiveX
…
DataSources
DBDataSource
DataTable
UserDataSource
Collection Obj.
- 18. © 2013 SAP AG. All rights reserved. 19Public
Topic 3: User Interface API
Topic 4: SAP Business One Development Tools
Topic 1: Introducing SAP Business One SDK
Topic 2: Data Interface API
Topic 5: Add-Ons Packaging & Deployment
Topic 6: SAP Business One Integration Framework
Topic 7: SAP Business One on SAP HANA
Introducing SAP Business One SDK
- 19. © 2013 SAP AG. All rights reserved. 20Public
SAP Business One Studio Suite
Developer Consultant Customer IT
SAP Business One Studio for Microsoft Visual
Studio
SAP Business One StudioSuite
UX Designer
• SAP Business One Studio
• SAP Business One Studio for Microsoft Visual Studio
Target Users
- 20. © 2013 SAP AG. All rights reserved. 21Public
SAP Business One Studio - Highlights
Reduce development effort
Offer better user experience by drag & drop
Cover user/UDO/system forms (compatible screen painter file format)
Open platform for functions like SAP Business One Workflow
- 21. © 2013 SAP AG. All rights reserved. 22Public
SAP Business One Studio for Microsoft Visual Studio -
Highlights
Leverage Visual Studio (SAP Business One 9.0 supports C# only.)
Design and develop user/UDO/system forms and event handling by drag & drop
Add-On code generation based on SDK UI Object Level Event
Shared input and output between Studio and Studio for VS
- 22. © 2013 SAP AG. All rights reserved. 23Public
Typical Use Cases
Case1: consultant designs a Add-On form in Studio, a developer programs this
form in Studio for VS.
Case2: customer IT designs and implement a UDO in Studio for VS.
Case3: developer implements a Add-On from scratch in Studio for VS.
Case4: consultant/UI designer draw a form in Studio; a developer loads it by raw
API.
Case5: continue developing old SRF generated from ScreenPainter in Studio for
VS.
- 23. © 2013 SAP AG. All rights reserved. 24Public
Topic 3: User Interface API
Topic 4: SAP Business One Development Tools
Topic 1: Introducing SAP Business One SDK
Topic 2: Data Interface API
Topic 5: Add-Ons Packaging, Deployment
Topic 6: SAP Business One Integration Framework
Topic 7: SAP Business One on SAP HANA
Introducing SAP Business One SDK
- 24. © 2013 SAP AG. All rights reserved. 25Public
Add-On Packaging
Pack Add-On components (including registration data file, setup etc.)
Create Add-On Installer, that must be 1 (one!) executable file
Provide Documentation
Describe User-defined fields and tables
Describe the User-defined objects you define in your Add-On (if applicable)
List where you modify SAP Business One standard functionality (if appropriate):
List where you interfere in the control flow of SAP Business One standard functionality (if
appropriate)
- 25. © 2013 SAP AG. All rights reserved. 26Public
Add-On Deployment
Register / Install / Administrate
Develop / Create Package
Register (and install) the Add-On
Create registration data file
Create installation program
Set User Preferences
Set Company Preferences
Run-time
Compile the Add-On program
Run or Stop the Add-On
Assign Add-On Licenses to Users (if appropriate)
- 26. © 2013 SAP AG. All rights reserved. 27Public
Add-On Administration
The Add-On Administration tool is designed to help administrators deploy and manage add-
on applications on end-users workstations.
Add-Ons on the server NOT
assigned to current company.
Add-Ons assigned to
current company.
- 27. © 2013 SAP AG. All rights reserved. 28Public
Topic 3: User Interface API
Topic 4: SAP Business One Development Tools
Topic 1: Introducing SAP Business One SDK
Topic 2: Data Interface API
Topic 5: Add-Ons Packaging & Deployment
Topic 6: SAP Business One Integration Framework
Topic 7: SAP Business One on SAP HANA
Introducing SAP Business One SDK
- 28. © 2013 SAP AG. All rights reserved. 29Public
SAP Business One Integration – B1if
Network of Solutions Supporting Network of Business and People
B1i as the platform for integration & collaboration
Integrates business partners, employees across system environments
Unifies business processes, and automates operations across the ecosystem
- 29. © 2013 SAP AG. All rights reserved. 30Public
B1if Components
- 30. © 2013 SAP AG. All rights reserved. 31Internal
B1i – Integration Framework of SAP Business One
B1i
The main task for B1if is to enable SAP B1
to publish/send data to external systems
and to allow SAP B1 to consume/access
data from external data provider.
ConnectivityTypes
DI API
File
JDBC
SMTP, IMAP, POP3
RFC
HTTP
Web Service, SOAP
REST
FTP
Get you up and running faster with a lower TCO
Lightweight architecture to address especially Small
Businesses (Apache Tomcat comes with B1if and installed)
Scalable due to parallel processing (by programming
model)
Multiplatform support (OS, DB … allows for connectivity
to multiple OS’s and database types)
Tailored deployment (S, M, L, – local, centralized, cloud)
Based on established integration standards (XML, XSLT,
HTTP … common technologies in the marketplace …
nothing new to learn)
Robustness due to pluggable apps/scenarios (Isolation
concept … each business scenario can run independent of
others)
Browser based administration (Remote administration)
SW logistics (Packaging, Hot Deployment, Incremental)
- 31. © 2013 SAP AG. All rights reserved. 32Public
B1BC: Intercompany Solution
• Enables businesses running SAP Business One to manage intercompany transactions for
more than one company.
• Automatically replicates corresponding transactions across multiple company databases.
Automating the replication of such transactions significantly reduces the amount of end-
user effort and manual rekeying of data to maintain intercompany trading financial
statements.
- 32. © 2013 SAP AG. All rights reserved. 33Public
Market Need Solution Features Globality Technology
Data sharing
Master Data Replication
Supported SAP Business One
localizations
Australia, Austria, Belgium, Brazil, Canada,
Chile, China, Costa Rica, Cyprus (EN), Czech
Republic, France, Germany, Guatemala,
Hungary, Ireland, Israel, Italy, Mexico,
Netherlands, New Zealand, Panama, Poland,
Russia, Singapore, Slovakia, South Africa,
Spain, Switzerland, UK, USA
Multi-Currency
Transactions in foreign as well as local
currencies are supported
Cross Localization
Integration and consolidation of subsidiaries
which use different country localizations is
possible.
Bi-directional Text Support for
Israel localization
Integration
Framework
of SAP Business
One
&
add-on
components
Service Contract and Customer Equipment
Replication
UDFs and UDTs Replication
Standardized
business
processes
across
companies
Intercompany Trade
G/L Allocations
A/P Service Invoice Allocations
Centralized Payments
Overview over
operations
across the
group
Multi-Level Financial Consolidation
Intercompany Reports:
Branch Inventory in Warehouse Report
Consolidated Balances by Business Partner
Report
Consolidated Sales Analysis Report
Branch Balances Report
Un-posted Transaction Report
Remote Query Execution
Improve
control &
collaboration
beyond
company
borders
Consolidated Credit Limit Check
Intercompany Message Log
Business Transaction Notifications (Alerts)
Intercompany Workflow
How Intercompany Integration Solution tackles the
needs
- 33. © 2013 SAP AG. All rights reserved. 34Public
B1iSN: Subsidiary & Intercompany integration
- 34. © 2013 SAP AG. All rights reserved. 35Public
Topic 3: User Interface API
Topic 4: SAP Business One Development Tools
Topic 1: Introducing SAP Business One SDK
Topic 2: Data Interface API
Topic 5: Add-Ons Packaging & Deployment
Topic 6: SAP Business One Integration Framework
Topic 7: SAP Business One on SAP HANA
Introducing SAP Business One SDK
- 35. © 2013 SAP AG. All rights reserved. 36Public
Why SAP Business One on SAP HANA
SAP HANA technology relies on main memory for computer data storage, providing faster
and more predictable performance than database management systems that employ a
disk storage mechanism.
The analytical features powered by SAP HANA:
Perform enterprise searches based on the SAP HANA database.
Access dashboards based on the SAP HANA database.
Generate pre-defined and customized Crystal reports based on SAP HANA.
Perform Microsoft Excel interactive analysis.
Import and deploy customized SAP HANA models.
- 36. © 2013 SAP AG. All rights reserved. 37Public
What is SAP Business One 9.0, version for HANA
- 37. © 2013 SAP AG. All rights reserved. 38Public
SAP Business One 9.0, version for HANA: Architecture
- 38. © 2013 SAP AG. All rights reserved. 39
What we have today … … the future
DI API for SAP HANA Service Layer for HANA
Use the full power of SAP HANA on the server side without COM mediation
Reuse the standard SAP Business One business logic and localizations
Proprietary UI API Standard off-the-shelf HTML5
Standard tools and technology to develop your presentation layer
Develop beautiful user experiences
Microsoft COM OData web-
services
Standard state-of-the-art OData protocol
Develop web applications that are natively mobile
- 39. © 2013 SAP AG. All rights reserved. 40
What we have today … … the future
Visual Studio .NET HANA
Studio
Leverage the full SAP HANA development environment
Use all its advanced capabilities such as: XS, OData, XMLA, BFL and PAL, R integration, etc.
Client based integration Server side
integration
Stay closer to your data
Leverage the multithreading capability of Service Layer: scalability and performance
Add-ons HANA extreme
applications
Go native with SAP HANA
Bring your innovation closer to your data
Easily consume it in SAP Business One, in a browser or on your mobile
- 40. © 2013 SAP AG. All rights reserved. 41
SAP Business One Service Layer - APIs format
The URI and content of HTTP request and response follow OData protocol
The payload follows JSON format.
Operation URI Request Content Response Content
on success
Login POST
http://localhost/b1s/Login.js
Object JSON Object JSON
Logout GET/POST
http://localhost/b1s/Logout.js
(Empty) (Empty)
Add POST
http://localhost/b1s/Items
Object JSON Object JSON
Get GET http://localhost/b1s/Items(‘I101') (Empty) Object JSON
Update POST http://localhost/b1s/Items(‘I101') Object JSON {}
Delete DELETE http://localhost/b1s/Items('I101') (Empty) {}
- 41. © 2013 SAP AG. All rights reserved. 42
Some theory - OData
http://www.odata.org
Web protocol for querying and updating data.
Based on Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON.
Any OData client can access
data provided by any OData
data source.
• Largely follows the conventions defined
by REST, which define how HTTP
verbs are used.
• Data can be serialized using
Atom/AtomPub or JSON.
• Allows access to an entire application-
defined data model.
• Clients are free to query this
model in any way they find
useful.
• The application's creator still has
control over what's exposed by
designing the data model.
- 42. © 2013 SAP AG. All rights reserved. 43
SAP Business One Extreme App Framework
A jump start development methodology and framework to enable partner
of SAP Business One ecosystem to build lightweight web application
(Extreme App, or X-App) based on SAP HANA’s XS engine(Extended
Application Services).
- 43. © 2013 SAP AG. All rights reserved. 44
SAP Business One Extreme App Framework
Scope:
• Empower SAP Business One ecosystem to build easy to extend,
lightweight, high performance, web-based, analytical
applications providing business insights to actions with superb
user experiences
Value Proposition for Customers:
• Optimize the efficiency of business processes
• Run directly on SAP HANA appliance with minimized TCO and
excellent performance
Value Proposition for Partners:
• Enrich traditional add-ons by web-based analytical applications
on the new lightweight framework & embed them into add-ons;
• Leverage the built-in strengths of SAP HANA and XS with
integrated SAP Business One services to develop apps in a low
cost of development on a lean stack with big data processing;
explorer new businesses
9.0, version for HANA 2014
Build essential
services and
integration with XS
and access to
semantic layer
Service Layer – 9.1
Extreme app life cycle
management enhancement
Delivery Plan from SAP Business One:
Physical Table
Client
HANA SERVER
Crystal Report Pervasive Analysis Interactive Analysis
BOBJ Extreme Apps …
Query View
Semantic
Layer Reuse View SQLScript
Control flow (JavaScript)
Control Flow (JavaScript)
XSEngine
HTTP(S) / oDATA, XMLA, SQL, MDX
Cont
rol
flow
(Jav
aScri
pt)
B
O
DIServer+**/Service
- 44. © 2013 SAP AG. All rights reserved. 45
SAP HANA XS Engine: Architecture
Consumption
model
Persistence
model
Java
Script
Enable application development/deployment:
• http-based UI
• Run on SAP HANA
• No external app. server
• Best possible performance
Broaden implementation base:
• Small Web-based apps
in lightweight environments
• Complex, high-speed business apps
in robust environments
- 45. © 2013 SAP AG. All rights reserved. 46
SAP HANA XS Engine: Built in Services
• Odata(Version 2.0)
• Standardized data exchange
• Drastic code reduction
• Restful HTTP commands: Atom/AtomPub
or JSON
• XMLA(XML for Analytics)
• Standard analytical data access
• SAP UI5
• SAP UI development toolkit for HTML5
• extensible UI component mode
• Server-side scripting in JavaScript
• Easy Language
• Built-in extensibility
• Inbound channel: http(s)
• Outbound connectivity: http, smtp
- 46. © 2013 SAP AG. All rights reserved. 47
SAP Business One Extreme App Framework – Login
Service
RESTful web service that provides authentication
verification.
It logs in the business user.
- 47. © 2013 SAP AG. All rights reserved. 48
SAP Business One Extreme App Framework – Login
Service Sample
<!DOCTYPE html>
<html>
<head>
<script src="jquery.js"></script>
<script>
$(function () {
/*Login service sample code*/
$("#login").click(function () {
var button = $(this);
$.ajax({
type: "POST",
url: "../../../platform/login",
data: {
"company": $("#company").val(),
"username": $("#b1user").val(),
"password": $("#b1pwd").val(),
"language": $("#b1language").val()
},
error: function (xhr, status, error) {
window.alert("login failed: " + xhr.responseText);
},
success: function () {
window.alert("login successfully.");
}
});
});
});
</script>
</head>
<body>
<div id="container">
<!--Login Service-->
<h1>Login Service</h1>
<p>
<label for="company" style="display: block">B1 Company: </label>
<input type="text" id="company" value="SBODEMOUS" />
<br />
<label for="b1user" style="display: block">B1 User: </label>
<input type="text" id="b1user" value="manager" />
<br />
<label for="b1pwd" style="display: block">B1 Password: </label>
<input type="password" id="b1pwd" value="manager" />
<br />
<label for="language" style="display: block">B1 Language:
</label>
<input type="text" id="b1language" value="en-US" />
<br />
<input type="button" value="Login" id="login" />
</p>
</div>
</body>
</html>
- 48. © 2013 SAP AG. All rights reserved. 49
SAP Business One Extreme App Framework – Query
Service
RESTful web service that executes predefined
user-defined queries (UDQ) and user-defined
stored procedures (UDSP).
- 49. © 2013 SAP AG. All rights reserved. 50
SAP Business One Extreme App Framework – Lifecycle
management
• Package your extreme app.
Export the package, containing the design-time artifacts and the
master data definition, from a development system.
• Deploy your extreme app.
Import the package into a productive/development system, and
run it in SAP Business One.
- 50. © 2013 SAP AG. All rights reserved. 51
SAP Business One Extreme App Framework – Lifecycle
management
Packaging Extreme Apps
• Section 5.2 of SAP HANA Developer Guide to set up a delivery unit.
• Section 14.3 of SAP HANA Developer Guide to assign your extreme app artifacts into a delivery unit (for
example, HTML, JavaScript, CSS, OData definition files and so on).
• Package Master Data of User-Defined Queries and Stored Procedures - Develop an add-on through
SAP Business One DI API to package the master data using the UserQueries object.
• Create Extension Registration File - run ExtensionRegDataGen.exe from SAP Business One SDK tools.
- 51. © 2013 SAP AG. All rights reserved. 52
SAP Business One Extreme App Framework – Lifecycle
management - Deploying Extreme Apps
• Deploy the extreme app artifacts into SAP HANA.
See Section 14.4 of SAP HANA Developer Guide.
• Register the extreme app to SAP Business One.
SAP Business One client Tools Extreme App Center.
• Deploy the extreme app to companies.
• Authorize users in the companies for the extreme app.
• Run the extreme app in SAP Business One, for example from a browser widget.
- 52. © 2013 SAP AG. All rights reserved. 53
SAP Business One Extreme App Framework – Lifecycle
management - Deploying Extreme Apps
- 53. © 2013 SAP AG. All rights reserved. 54Public
Topic 3: User Interface API
Topic 4: SAP Business One Development Tools
Topic 1: Introducing SAP Business One SDK
Topic 2: Data Interface API
Topic 5: Add-Ons Packaging & Deployment
Topic 6: SAP Business One Integration Framework
Topic 7: SAP Business One on SAP HANA
Introducing SAP Business One SDK
- 54. © 2013 SAP AG. All rights reserved. 55Public
Useful Links
SAP Business One 9.0 Central Information
http://sappartneredge.com/B1/90
B1 Innovations
https://service.sap.com/smb/sbo/innovations
SAP Business One Integration Capabilities
http://sappartneredge.com/B1/b1i
SDN B1if key topic page
http://scn.sap.com/community/business-one-integration-technology
SAP Business One on SAP HANA Products
http://sappartneredge.com/B1/hana
- 55. © 2013 SAP AG. All rights reserved. 56Public
Q & A