Inbound development steps

What is Inbound ? Is a kind interface method, using this we can import the data from Legacy system to oracle base tables. Mostly we can implement this one using SQL Loader program. Development Process steps : First we will get the MD50[functional Requirement Document] form then we will go through and analysis this document, if we have any issues we can write into open issues part of MD50. And afterwards we are going to design MD70[Technical Design Document]. It is a overall architecture or Skelton part of the component and then send to approval. Once the MD70 is completed approved and approved then we are going to start the actual development of the component. First we need to crate the staging [or Temporary] table based on given flat file. Then we can Move the data from flat file to staging table by using SQL*Loader program. Once data is staging table, we can validate the data and import into the interface tables by using one plsql package, then we can transfer the data from the interface table to base table by submitting the Standard concurrent program.

**************************************************************************** Faqs: 1). While moving the data from flat file to staging table , How can you find out the error Records? A). By checking log file , we can findout the error tables and all other errors. 2). What is diff b/w Discard file and Bad files? A). Bad file contains records which are rejected by Ctl file, due to data format. Discard file contains records , which are rejected by Ctl file, due syntactical errors of CTL files. 3). While moving the data from staging to interface table, how can you tract the error record information? A). We can find by using staging table of process flag[E,S,V means E-error, S-Success, N-New record, Vvalid] and Error message or we can crate the user define error table, we can insert all the errors into that table and we can retrieve the error table and we can see all the errors into that table.

4). How can you tract the Error records information , while moving data from interface table to Base table? A). Normally Every module has to its own predefined error tables , we can see all the errors information in this tables. Ex. For AP module the error table is AP_interface_error. 5). How many files , we have while developing interface and conversion? A). Mainly we have to get 4 types of files , while developing interface and conversions. They are 1). Flat file 2). Log file 3). Discard file 4). Bad file. 1). Flat file: It is a kind of file , it contain the Legacy data , which is provided by client . 2).Log file: It is a kind of file, it will be in SRS Window. It will give the status of the concurrent program. It will give the description of the Bad file, discard file and some of the errors information. 3). Output file: It is also one of the file, it will give the output of the interface or conversion and Report. 4). Bad file: Is a kind of file, it contains records, which are rejected by Ctl file, due to data format. 5). Discard file: it is also a file, it contains records , which are rejected by Ctl file, due syntactical errors of CTL files. ABOUT SQL*LOADER: