【正文】 t 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 Requirements Modification Description than a predefined amount (. 1M), a particular bank account will be used. Otherwise, another bank account will be used. 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. Internal Satellite Systems Functionality Based upon the information Oracle has on the Internal Satellite systems functionality Oracle has identified minor extensions and or workarounds to be applied for replacing the following two Satellite Systems by using Oracle Standard Products, the Mobile Sales and Administration SystemMSAS and the Deliver Order Transmission System. During the Definition phase of the implementation Project the detailed requirements will be defined and agreed upon. 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 , new custom systems, and nonOracle systems make interface development a critical part of the project. However through the replacement of 20 internal satellite systems by Oracle Applications standard function and features, the effort of developing interfaces has bee less critical for the project implementation and gives HKT an important benefit in embedding some of the standalone systems as integrated parts of the Logistics system. Thus avoiding redundant data capture and maintenance effort of the Satellite System The Oracle project manager together with the Hongkong Tele project manager will manage the remaining interface development process using Oracle?s interface development procedures. System Interfaces Oracle will develop twentysix (26) interfaces between 2 internal and 12 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 this proposal. Interface Point Inbound or Outbound Origin and Destination Systems Complexity Account Code binations from Damp。B Accounts Receivable Outbound Oracle Order Entry to Damp。B Accounts Receivable to Oracle Order Entry High Invoice Information (Types, Terms etc.) Inbound Damp。B General Ledger. This has been classified as one very plex interface. ? All invoicing data from Order Entry will not include account code information. Instead all information requested by the Damp。 Critical Path Project Teams (Oracle and HKT) Resource Estimate The project resources should be provided from both the user and the IT side. From the user side, we normally suggest to have a full time team leader for each major module (. Inventory). If resources are a constraint and the processes of the module is relatively simple, a parttime team leader could be adequate. We need to evaluate the situation during the project planning phase. The team leader should have indepth business knowledge of the current business process and have the delegated authority to make business decision about any future business processes, including the running of the Oracle Financial module. In addition to the team leader, key business representatives will be required to be involved on a part time basis. These key business representatives will be required to provide input to the decision process as required. To formalise new policies and procedures, to be involved with testing and acceptance of module functionality, customisations and interfaces, reconciliation of converted data. The business representatives will be required to provide a map from the codes and accounts used in the existing system and any third party interfaced system to the Oracle Financials System. On the technical side, ideally the DBA should have Oracle technical skills and experience. If not, practical experience of RDBMS is remended. It is preferred to have general experience in package implementation and support. Further technical resources should be provided to assist with developing interfaces from existing system to the Oracle Applications. It is important to have inhouse knowledge of the current business