MD070 Inv Outbound Interface
MD070 Inv Outbound Interface
MD.070 APPLICATION EXTENSION TECHNICAL DESIGN INV OUTBOUND INTERFACE GE Infrastructure Sensing-China
Oracle Inventory
Author: Creation Date: Last Updated: Document Ref: Version: Bipin July 1, 2006 July 1, 2006 Draft 1.0
Approvals: John, Connor Sabrina, Ng ERP Finance Lead - GE Infrastructure Sensing Finance Controller - GE Infrastructure Sensing Shanghai Project Manager Satyam Computers
Saumil Thakkar
1 Document Control
Change Record
S. No. 1 2 3 4 5 Date None Author Version Change Reference
Reviewed by
S. No. 1 2 3 4 5 , Name Garnette Position Finance Lead Signature Date
Distribution
Copy No. 1 2 3 4 5 Name Location
2 Table of Contents
1 2 3 DOCUMENT CONTROL.....................................................................................................................2 TABLE OF CONTENTS........................................................................................................................3 TOPICAL ESSAY...................................................................................................................................4 3.1 3.2 3.3 4 5 Basic Business Needs.......................................................................................................................4 VAT Issue Report..............................................................................................................................4 VAT Invoice Report..........................................................................................................................6
3 Topical Essay
GE Infrastructure Sensing needs to procure Inventory details from the Inv for payment details which we have done for particular Supplier. Inv Outbound interface program will be developed to transfer the data from oracle INV base tables into the OFM (Legacy) flat file.
3.1
Company has to make all the Transaction in OFM (Legacy), GE needs a data file which is going to store in the legacy database. This Program should bring the data from Inventory which has been entered between the Two Organizations. And Item should be Purchasable item.
3.1.1 Assumptions
This design assumes that the following information will be maintained in Chinese language:
1. 2. 3. 4. 5. 6. 7.
_______________________________________________________________________ _________
3.2
Report output should show the following information in the Output file. No Of Records Transferred into file : No of Records which are transferred to the Flat file. User Name : Name of the User Who has submitted Resonsibility : Name of the Responsibility from which report has submitted Date of submitted : Request submission Date
S q
Paramete r
Descriptio n
Value set
Default Type
Default Value
Requ ired
Dis play ed
Prompt
Token
1 2
Org_ID Org_ID
None None
Profile Profile
Y Y
Y Y
ORG ID ORG ID
P_org_id P_org_id
1.1.1
Configuration
Register Concurrent Program Register Concurrent Executable Responsibilities Request Security Group Data Group
Technical Overview
Use this section to describe the technical approach, high-level algorithms, process flows, etc. Discuss possible solutions to technical challenges. The detailed designs for forms and programs will provide the details for the general overview presented here. Used the following tables to get the Customer and the invoive, item details. MTL_SYSTEM_ITEMS_B ORG_ORGANIZATION_DEFINITIONS MTL_CATEGORIES MTL_ITEM_CATEGORIES
5 Considerations
If any Oracle Applications tables change in future versions of Oracle Purchasing, components of this customization may also require changes to work correctly. Evaluating the impact of such changes on custom programming is the responsibility of the company, although additional consulting services can be contracted to assist prior to upgrading.