| Test Case ID | Feature/ Functionality ID | Test Description | Expected Behavior |
| Generalised Test Conditions | |||
| 1 | Running the Loader concurrent program. | Data has been loaded into temp table successfully. | |
| 2 | Don't put the data file in proper directory and run the Loader program. | Loader concurrent program should complete in error and the log file should give the error detail regarding the non existance of Data file in proper directory. | |
| 3 | Don't put the control file in proper directory and run the Loader program. | Loader concurrent program should complete in error and the log file should give the error detail regarding the non existance of control file in proper directory. | |
| 4 | Don't create temp table in APPS OR create temp table in schema other then APPS schema and don't give the GRANT access to APPS. | Loader concurrent program should finish in error and the log file should give the error detail regarding the non existance of temp table. | |
| 5 | Try to load the NULL values in NOT NULL columns of temp table. | SQL*Loader bad file should be created with bad records in respective directory only for those records.. | |
| 6 | Try to load data of a column of more size then specified in temp table for corresponding column. | SQL*Loader bad file should be created with bad records in respective directory only for those records.. | |
| 7 | Try to load data of a column of different data type then specified in temp table for corresponding column. | SQL*Loader bad file should be created with bad records in respective directory only for those records.. | |
| 8 | Running the Validation concurent program. | Data has been validated and loaded into interface tables successfully. | |
| 9 | Don't create stored procedure in APPS OR create stored procedure in schema other than APPS schema and don't give the GRANT access to APPS. | Validation concurrent program should complete in error and the log file should give the error detail regarding the non existance of stored procedure. | |
| 10 | Define incorrect number of parameter in validation concurrent program and run the validation concurrent program. | Concurrent program should complete in error and proper error detail should be captured in error log file related to incorrect number of arguments. | |
| 11 | Define incorrect number of parameters in stored procedure and run the validation program. | Concurrent program should complete in error and proper error detail should be captured in error log file related to incorrect number of arguments. | |
| 12 | Define different data types for parameters in validation concurrent program and stored procedure for corresponding parameter and run the validation program. | Concurrent program should complete in error and proper error detail should be captured in error log file related to datatype mismatch of the parameters. | |
| 13 | Don't Create the error table and run the validation program. | If some of the records failed in validation. Then concurrent program should complete in error and log file should be created which contains the error detail. | |
| 14 | Run the validation concurrent program with error table created. | Error records has been loaded into error table. | |
| 15 | Create the validation stored procedure which is having one or more SQL statements which are not handeled for exception. | If any exception raised then it should give the exception detail in error long file. | |
| 16 | Run the validation concurrent program which is having improper value sets attached to some of its parameters. | Concurrent program should complete in error and proper error detail should be captured in error log file. | |
| 17 | Running the standard interface concurrent program. | Data successfully loaded into Oracle tables. | |
| 18 | Are test cases identified for valid inputs | For valid input ,Program gets sucessfully processed. | |
| 19 | Are test cases identified for invalid inputs | For invalid input ,Program displays Error Exception or Messages. | |
| 20 | Are test cases identified for testing boundary conditions | Program is succefully operating within defined boundry. | |
| 21 | Are performance test condition covered. | Each Query,PL/SQL program should be tuned with performance | |
| 22 | Program cover error guessing. E.g. Division By Zero | Program should not abort abnormaly ,instead give a relevent error message. | |
| 23 | Datatypes handled properly | For datatype mismatch, progarm should give the Data Type missmatch error. | |
| 24 | Check abnormal conditions | Abnormal condition handled by the Exceptions. | |
| Test Cases specific to AutoInvoice | |||
| Setup Related TestCases | |||
| 1 | Transaction sources have not been setup | Records will be transferred to the error table and will not be imported into the standard apps interface table | |
| 2 | Grouping Rules have not been set up | Records will be transferred to the error table and will not be imported into the standard apps interface table | |
| 3 | Accounting Rules have been setup | Records will be transferred to the error table and will not be imported into the standard apps interface table | |
| 4 | Line Ordering Rules have not been set up | Records will be transferred to the error table and will not be imported into the standard apps interface table | |
| 5 | Transaction flexfield has not been appropriately defined. | Records will be transferred to the error table and will not be imported into the standard apps interface table | |
| Other Testcases | |||
| 1 | Customer Code is not provided as a part of the datafile. | Error Message if customer code is Null " Customer Code must be provided" and the record will be transfered to the error table else the data will be transferred to the standard interface table | |
| 2 | Provided Customer is not a valid customer and the details of which are not not not not existing in the database. | Error Message if customer is not a valid customer "This customer information does not exist in the database" and the record will be transferred to the error table else the data will be transferred to the standard interface table. | |
| 3 | Provided Customer does not have a valid Address in the database. | Error Message if customer address is not a valid address in the database. | |
| 4 | Customer address details are not not not present as site information | Error Message if customer address is not provided as a valid site information. | |
| 5 | Customer Site is not a valid Site. | Error Message if customer site is not a valid site. | |
| 6 | Customer Site is not a "BILL TO" site and the Site is not Active. | Error Message if the customer site is not a "Bill To" site and the site is not Active | |
| 7 | Sales Representative is not a valid Sales Representative and the details of which are not present in the database. | Error Message | |
| 8 | Term Name and Term ID are not valid and exist in the database. | Error Message | |
| 9 | Billing Begin Date is Less than Billing End Date, if both are not not not provided. | Error Message | |
| 10 | Item Description is valid and is existing in the database | Error Message | |
| 11 | Memo Line Id is not existing in the Database for the Rev Terms specified by the user. | Error Message | |
| 12 | Invoice No. is not exisiting in the Database. | Error Message | |
| 13 | Invoice From Date is not less than the Invoice To Date | Error Message | |
| 14 | Accounting Rule specified is not valid for the Rev Terms supplied by the user for Type = "A' and Status = 'A' | Error Message | |
February 27, 2016
