From: Doni Syamsurianto

Mas Buddy,

Ini gw put nama lu untuk manage resource di ICT, bukan SQL DB development seperti yang di tulis oleh
Usman. Sorry, tadi belum sempat gw update. Nanti untuk development, akan tetap di bawah Afton.

Idenya adalah development SQL dan MS BI akan kita manage sendiri. Sehingga kita bisa manage resource
dan schedule. Mungkin kita perlu kontak IGLO atau other vendor untuk hire satu orang SQL Programmer
agar tidak terlalu membebankan Rofendy. Rofendy nanti akan lebih focus ke design SQL DB nya.

Mas Afton,
Mungkin bisa dibantu untuk kontak vendor kita sekarang, apakah mereka punya SQL DB Developer. Kita
butuh ASAP untuk development.

Mas Rofendy,
Gw rasa approach dan design yang digunakan di TuBiz saat ini bisa digunakan. Hence, kita tidak reinvent
the wheel lagi.

Lets discuss on Monday at 1330 in details.

From: u.hidayat@accenture.com [mailto:u.hidayat@accenture.com]

-------------
Dear Pak Doni,

Please see below minutes of meeting for today meeting, Friday 30 August 2013:
- Interface between SAP CRM and DBS: Database (DBS) -- Staging DB (Ms SQL) -- SAP PI --
SAP CRM
- Server for SQL database will be provided by ICT TU
- Interface for SAP CRM Ms BI: SAP CRM Ms SQL Ms BI
- CRM WEB_UI Performance Test: review the tools (HPQC, Load Runner etc)
- Pak Buddy from ICT TU will be the PIC for the SQL DB (resource, plan, programmer etc)
- Interface should be ready on SIT 1 and SIT 2 date (end of September 2013)
- Ms BI Go Live date will be same as DMS R2A (CRM)

SAP NetWeaver Process Integration (SAP NetWeaver PI) is used as follows:

The architecture of SAP NetWeaver PI 7.1 is based on an established architecture for realizing cross-
system business processes, and is the same as in lower releases (SAP NetWeaver 7.0 usage type Process
Integration and SAP XI 3.0 as part of SAP NetWeaver 2004).

SAP NetWeaver PI 7.1 plays an important role in supporting an enterprise service-oriented architecture
(SOA). The focus is on the service-based integration of applications.

SAP NetWeaver PI is based on general standards so as to enable 3rd-party systems to be integrated. At the
center of SAP NetWeaver PI is an XML-based communication that uses HTTP (Hyper Text Transfer Protocol).
Irrespective of the scenario used, the application-specific contents are transferred in messages in user-
defined XML eXtensible Markup Language) from the sender to the receiver either via the Integration
Server, or directly between the systems involved.

The following figure gives an overview of the key capabilities of SAP NetWeaver Process Integration:
SAP NetWeaver Process Integration 7.1 enables the integration of the applications of the following
communication parties:

B2B Party: Any business partners that want to integrate their application with other applications outside
their own system landscape. Scenarios that require industry standards are supported as well as any
scenarios that are not sufficient for a specific industry standard.

SAP: Applications that run on SAP systems. This includes the processing of events by using the BAM
infrastructure.

3rd-Party Application: Applications from 3rd-party providers within one system landscape, for example
database or file-system-based.

3rd-Party Middleware: Middleware systems from 3rd-party providers that are required for the integration
of applications within a company and across company-boundaries.

SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios. It enables you
to connect systems from different vendors (non-SAP and SAP) in different versions and implemented in
different programming languages (Java, ABAP, and so on) to each other. Like the rest of the SAP NetWeaver
platform, SAP NetWeaver PI is based on an open architecture uses open standards (in particular those from
the XML and Java environments) and offers those services that are essential in a heterogeneous and
complex system landscape.