Sekolah Tinggi Penerbangan Indonesia (STPI) Established in Jakarta, precisely in the area, Kemayoran Gempol in 1952, this educational institution was originally named Akademi Penerbangan Indonesia (API). In 1954 API was moved from Jakarta to the new campus, in the district Legok, Tangerang (better known by the aviation community with the campus Curug).
In 1969, Akademi Penerbangan Indonesia (API) changed its name to the Lembaga Perhubungan Udara (LPPU). In 1978, the institution changed its name to the Pendidikan dan Latihan Penerbangan (PLP) which is the Technical Unit of the Training Agency of Transportation.
In 2000 the PLP changed its name to Sekolah Tinggi Penerbangan Indonesia (STPI), to the present. The presence of STPI is based on Presidential Decree and the Minister of Transport as follows:
- Presidential Decree number 43 of 2000 dated March 10, 2000 on Sekolah Tinggi Penerbangan Indonesia.
- Decree of the Minister of Transport number 64 of 2000 dated August 21, 2000 about the work of organization and procedure of Sekolah Tinggi Penerbangan Indonesia.
- Decree of the Minister of Transportation number. 29/DL.003/Diklat-2001 dated January 29, 2001 on the Statute of Sekolah Tinggi Penerbangan Indonesia.
Oracle Application implementation for Distribution Modules
Procure to Pay (Purchasing)
Oracle Purchasing supports four types of purchase orders: standard, blanket, contract and planned. There are several methods that can be used to create purchase orders. You can manually create purchase orders or search approved requisitions and add them to purchase orders. Standard purchase orders can be imported through the Purchasing Documents Open Interface in a status of Incomplete or Approved. You can automate purchase document creation using the PO Create Documents workflow to automatically create a blanket purchase agreement release or a standard purchase order upon approval of a requisition.
Once purchase orders are created, they may be submitted for approval. The approval process checks to see if the submitter has sufficient authority to approve the purchase order. Once the document is approved, it may be sent to your supplier using a variety of methods including: printed document, EDI, fax, e-mail, Oracle iSupplier Portal and XML. Once the purchase order or release is sent to your supplier, they are authorized to ship goods at the times and to the locations that have been agreed upon.
Oracle Inventory treats many different types of things as inventory. Inventory can be:
- Finished goods that you sell to customers
- Services that you sell to customers
- Spare parts for maintenance
- Raw materials for manufacturing processes
- Inventory you purchase from a supplier on consignment
Warehouse Management System
Warehouse Management provides the following features in addition to the features available in MSCA:
- Task management
- Material tracking with License Plate Numbers (LPNs)
- A configurable rules engine that enables you to create custom picking rules, put away rules, and compliance labeling rules.
- Advanced inventory and materials management including material status, lot, and serial support.
Warehouse Management also is heavily integrated with, and extends some of the current functionality in Oracle manufacturing applications.
Oracle Application implementation for Business Intelligance Standard Edition One
Oracle Business Intelligence Foundation Suite (OBIEE+ and Essbase) is a complete, open, and architecturally unified business intelligence system for the enterprise that delivers abilities for reporting, ad hoc query and analysis, online analytical processing (OLAP), dashboards, and scorecards. All enterprise data sources, as well as metrics, calculations, definitions, and hierarchies are managed in a Common Enterprise Information Model, providing users with accurate and consistent insight, regardless of where the information is consumed. Users can access and interact with information in multiple ways, including web-based interactive dashboards, collaboration workspaces, search bars, enterprise resource planning (ERP) and customer relationship management (CRM) applications, mobile devices, and Microsoft Office applications.
Implemetation Time Frame
Aug 2010 – Mei 2011