Sie sind auf Seite 1von 2

AP / CE miscellaneous tasks requiring Technical support Quarterly Datafix Just before each quarter end we must run a data

fix. The Oracle bugs that contribute to the bad data are fixed in 11.5.10. Until then the only way to fix the payments is the quarterly data fix. The tasks are run by the DBA. See attached document for the instructions and justification for the CR. Run the Bai bank statement import for Wells Fargo We created this job to handle the BAI bank statements. The volume of wires is small and it is currently faster for the CE reps to get the hard copy and clear the payments manually. Currently I run the job myself to move the statements from the staging table into the Oracle interface table. There probably is no need to do this, because they are not processed any further. They just stay in the interface table. Responsibility CE Rep or CE Support Request Set Bank Get and Load BAI Statements (SBUX) (no parameters are required) Beginning November of each year Check for Oracle updates to 1099 processing for current Tax year. Beginning November each year check Oracle note 209913.1 Oracle Payable Plans for 1099 Reporting. If the IRS has made changes, Oracle will provide a patch for the 1099s. The user will bring the supplier tax information up-to-date and run the Oracle job Update Income Tax Details Utility. Important note: Be sure to confirm the job was run with the parameters Update, not just Report. When corrections have been made the user will run 1099 Electronic Media The changes must be in place and the 1099s set to our vendors each year by the end of January. Check with Treasury to get Bank Holiday schedules Provide the Bank holiday schedules for the coming year to production control so the Control-M banking jobs can be scheduled correctly

Quarterly data fix The FA will create the MR as the quarter end approaches. No packages will be created. The TA will create a copy of the following set of instructions for the DBA. ------------------------------------------------------DBA instructions for MR <mercury number> Run once for EMEA and once for NA Step 1 - DBA Login to appropriate server As apps run $AP_TOP/patch/115/sql/b4749619s.sql When complete, the script will provide the name and location of the log file. Send a copy of the log file to Marcy Reed and the <technical analyst>. Step 2 - FA Marcy will review the log file. If any of the events need to be excluded from the next step, Marcy will provide the event_id. Step 3 (optional) - DBA If an event needs to be excluded: As apps run $APPFIN_TOP/adhoc/b4749619_flag_event.sql When prompted enter the event_id provided by Marcy Commit if successful Step 4 - DBA If there are events that need to be corrected: Marcy will give the ok to go forward with the next step As apps run $AP_TOP/patch/115/sql/b4749619x.sql Enter Y when prompted for backup table Events_4749619 Enter value for backup: Y When complete, the script will provide the name and location of the log file. Send a copy of the log file to Marcy Reed and <technical analyst>.

Das könnte Ihnen auch gefallen