APPS.INV_DIAG_GRP_MSN dependencies on FND_FILE

Line 84: -- fnd_file.put_line(fnd_file.log,'@@@ in pipe init : '||to_char(SYSDATE, 'DD-MON-YYYY HH24:MI:SS'));

80: ------------------------------------------------------------
81: PROCEDURE init IS
82: BEGIN
83: -- test writer could insert special setup code here
84: -- fnd_file.put_line(fnd_file.log,'@@@ in pipe init : '||to_char(SYSDATE, 'DD-MON-YYYY HH24:MI:SS'));
85: null;
86: END init;
87:
88: ------------------------------------------------------------

Line 95: fnd_file.put_line(fnd_file.log,'@@@ in pipe cleanup : '||to_char(SYSDATE, 'DD-MON-YYYY HH24:MI:SS'));

91: ------------------------------------------------------------
92: PROCEDURE cleanup IS
93: BEGIN
94: -- test writer could insert special cleanup code here
95: fnd_file.put_line(fnd_file.log,'@@@ in pipe cleanup : '||to_char(SYSDATE, 'DD-MON-YYYY HH24:MI:SS'));
96: END cleanup;
97:
98: ------------------------------------------------------------
99: -- procedure to execute the PLSQL test

Line 121: fnd_file.put_line(fnd_file.log,'@@@ grpmsn 1');

117:
118: -- html formatting
119: JTF_DIAGNOSTIC_ADAPTUTIL.addStringToReport('@html');
120: JTF_DIAGNOSTIC_COREAPI.Show_Header(null, null); -- add html css
121: fnd_file.put_line(fnd_file.log,'@@@ grpmsn 1');
122: INV_DIAG_GRP.g_grp_name :='INV_DIAG_GRP_MSN';
123: -- for dummy testing, simply put status as 'SUCCESS'
124: -- successful test will not show error message and fix info in report
125: statusStr := ''; -- 'SUCCESS';

Line 133: fnd_file.put_line(fnd_file.log,'@@@ grpmsn 2');

129:
130: -- construct report
131: report := JTF_DIAGNOSTIC_ADAPTUTIL.constructReport(statusStr,errStr,fixInfo,isFatal);
132: reportClob := JTF_DIAGNOSTIC_ADAPTUTIL.getReportClob;
133: fnd_file.put_line(fnd_file.log,'@@@ grpmsn 2');
134: END runTest;
135:
136: END;