SAP Business One Integration highlights

SAP B1 has multiple tools to enable integration with your legacy system, eCommerce, etc. In this small article we would like to give you highlights on SAP Business One SDK integrations. These integrations require Microsoft Visual Studio.net C# or VB programming skills. Typical SAP BO integration would move customer orders to SAP B1 Sale Orders

• Staging Table. You need to move your eCommerce transactions to staging table, preferably in MS SQL Server, where SAP BO is hosted. Use stored procedure, if required you can do heterogeneous queries to pull transactions from Oracle, IBM Lotus Notes Domino or another db platform

• SAP BO SDK Loop. You should open connection to SAP BO company via SDK. We will not give you code sample here, we expect intermediate SDK coding experience. When connection is established – you read your staging table and create Sales Orders one by one – or alternatively you create one Sales Order and add items one-by-one

• Flagging Imported Transactions. In staging table you should either delete imported transaction or flag them as being imported, your choice

• AR Invoice. We do not recommend you to add invoice in integration. The reason is simple – invoice is not stored in the batch – it should be posted – and we do not recommend you to review posted invoices – in order to reverse them you will need to enter credit memos, which will create a mess in your data entry

• Other Integrations. SAP Business One SDK allows you to create, modify and manipulate virtually all SAP B1 objects, in this article we showed you Sales Orders, you can also update or add customers, vendors, etc.

Please feel free to call us on SAP Business One integration scenarios: 1-866-528-0577, 1-630-961-5918, help@albaspectrum.com or skype: albaspectrum

Andrew Karasev, Alba Spectrum Group, serving SAP Business One customers in USA nationwide from Chicago and Houston, in Brazil from our call center in Sao Paulo. We also serve Microsoft Dynamics GP US nationwide and support all the types of customization, reporting, software development, integration, data conversion from our Manila software factory.

http://www.albaspectrum.com
http://www.enterlogix.com.br

SAP Data Warehousing Solution

SAP BW is a continuous data warehousing solution that uses former SAP technologies. This SAP BW is built on the Basis of 3-tier architecture and coded in the ABAP (Advanced Business Application Programming) language. This 3-tier architecture and code language uses ALE (Application Link Enabling) and BAPI (Business Application Programming Interface) to link BW with SAP systems and non-SAP systems.

BW Architecture The BW has three layers in it. The top layer is the reporting layer. This top layer may be BW Business Explorer (BEx) or a third-party reporting device. This BEx consists of two components: one is BEx Analyzer and other is BEx Browser.

BW Server is a middle layer that carries out three tasks: it administrates the BW system, stores data and retrieves the data. In The bottom layer it consists of source systems, which may be R/3 systems, BW systems, flat files, and other systems. In the source systems a SAP component called Plug-In must be installed. It contains extractors. An extractor is a set of ABAP programs, database tables, and other objects that BW uses, which helps to extract data from the SAP systems. This BW Server contain Administrator Workbench, Metadata Repository and Metadata Manager, Staging Engine, PSA, ODS and User Roles.

• This Administrator Workbench checks metadata and all BW objects. It has two components: one is BW Scheduler and other is BW Monitor. This component helps to load data and to monitor the data.

• This Metadata Repository contains information relating to data warehouse. Metadata Repository contains two types one is business-related and other is technical. Metadata Manager is used to maintain Metadata Repository.

• PSA (Persistent Staging Area) is also a BW server. This PSA stores data in the original format while being imported from the source system. It ensures quality check of data before they are loaded in their destinations, such as ODS Objects or Info Cubes.

• This ODS (Operational Data Store) Objects helps to build a multilayer structure for operational data reporting. It is used for detail reporting.
• Info Cubes is an actual table and they are the associated dimension tables in a star schema.

• The OLAP Processor is the analytical processing engine. It analyzes and retrieves data as per users' requests.
• Documents are stored in BDS (Business Document Services). The documents can appear in different formats like Microsoft Word, Excel, PowerPoint, PDF, and HTML.

BW Business Content The BW's most powerful selling is Business Content. It contains standard reports and other associated objects. For standard reports, BW use a function called Generic Data Extraction. This function is used to extract R/3 data.

Nowadays, BW is rapidly evolving. It helps to plan BW projects and their scopes.

This sap e-business consists of three components: they are my SAP Technology, my SAP Services and my SAP Hosted Solutions.

• MySAP Technology provides an infrastructure for Web Application Server and for process-centric collaboration. This infrastructure contains a component called mySAP Business Intelligence.
• Another type of services called mySAP Services are the best services which support SAP offers to the customers. They offer for business analysis, technology implementation, and training to system support.

• This mySAP Hosted Solutions are the outsourcing services of SAP. With the help of this solution, customers need not want to maintain physical machines and networks.

Ron Victor is a SEO copywriter for SAP Company . He written many articles in various topics in SAP Articles and SAP Training. For more information about sap information visit SAP Forums .Contact him at ron.seocopywriter@gmail.com