电信项目实施文件03option1phase(编辑修改稿)

电信项目实施文件03option1phase(编辑修改稿)内容摘要：

s of the invoice by location and processing stage. This information should be accessible to users enquiring of the progress of the System should be able to record the name and location of the action officer who approve the invoice or perform invoice matching to PO. Descriptive Flexfields can be created to store the required information Create a new invoice inquiry function which allow user to enter criteria in the descriptive flexfields Requirements Modification Description invoice. Bank Accounts The system shall be able to automatically assign the appropriate bank account for paying the invoices based on account code, amount and currency. The system should be able to perform the following : 1. based on the account code to determine the type of expenses : CAPEX or OPEX 2. There are specific bank accounts assigned for CAPEX and OPEX expenses respectively. 3. For OPEX expenses, if the amount is less than a predefined amount (. 1M), a particular bank account will be used. Otherwise, another bank account will be used. Program modifications : 1. In bank account maintenance, add fields to specify whether the bank account will be used for OPEX and CAPEX and for what amount range. 2. In invoice, store the information which can be used to determine the type of expenses (note that the account code structure may be changed so that it may be not able to use the account code to determine the type of expenses in future) 3. In payment batch creation, user still need to specify they want to pay OPEX or CAPEX expenses and amount range by specifying the bank account 4. Change the invoice selection program to provide the intelligent to base on the flag stored in the invoice to determine the type of expenses and amount range. It then select only those invoices for payment. Interfaces The plex mix of existing legacy Satellite Systems, 25 systems recognized as internal and another 12 systems recognized as external to the logistics system, make interface development a critical part of the project. Oracle will not develop interfaces to Satellite Systems that are identified being stand alone systems . From information given to Oracle, the following internal satellite systems are standalone:  Warranty Repair System  Phonecard System  Serialized Stock Tracking System  Delivery Order Transmission system  Stores Location System  Equipment registration System  Non code Item Inventory Control System  Petty Cash  MRI  Contract Information System  Powerbase Purchasing System Oracle will develop interfaces to external Satellite Systems as defined explicit in the RFP and as defined in the list below. The Oracle project manager together with the Hongkong Tele project manager will manage the interface development process using Oracle’s interface development procedures. System Interfaces Oracle will develop forty (40) interfaces between internal and external Satellite Systems and the Oracle Applications. All interfaces will be filetofile interfaces, not programtoprogram interfaces. Data will be exchanged via a flat ASCII file. For outbound interfaces from Oracle Applications, Hongkong Tele will specify the format of the file to be produced. The information to be provided must be available to the Oracle Applications. Oracle will create a file on the server where the Oracle Applications exist. These files will exist in a temporary holding area where Hongkong Tele can pick up the file and transfer the data to other external systems if necessary. For interfaces that are inbound to the Oracle Applications, Oracle will specify the format in which the information is to be provided. Hongkong Tele needs to provide the file to the server where the Oracle Applications exist. This format will be consistent with the application program interfaces (API’s) that are available for Oracle Applications. A list of interfaces by Oracle Application Module is provided below, along with an indication of the plexity of each interface. The cost and time to plete the interface work is based on the number of interfaces and the plexities. Interfaces may be added or removed during the Operations Analysis phase without any impact to cost or time to implement, provided the total number of interfaces and the plexity mix does not change. Any changes to the number or plexity mix of interfaces is outside the scope of the Phase I proposal. Interface Point Inbound or Outbound Origin and Destination Systems Complexity Account Code binations from Damp。 B General Ledger Inbound Damp。 B General Ledger to Oracle General Ledger Medium Account Journals from the GL Interface Outbound Oracle General Ledger amp。 B General Ledger. Very High Shipment Details for Invoice creation within Damp。 B Accounts Receivable Outbound Oracle Order Entry to Damp。 B Accounts Receivable High Return Material Authorization information for Credit Memo creation within Damp。 B Accounts receivable Outbound Oracle Order Entry to Damp。 B Accounts Receivable Medium Customer Interface (including Credit Ratings) Inbound Damp。 B Accounts Receivable to Oracle Order Entry High Invoice Information (Types, Terms etc.) Inbound Damp。 B Accounts Receivable to Oracle Order Entry Medium Cable Stock Information In/Outbound CSMS to/from Oracle Inventory Complex Stock。