The following batch jobs must be scheduled as per your implementation's business rules:
C1–CREFC (Create Controls For Uploaded Forms). This batch process creates form controls for batch-uploaded forms. To create form controls using this process, the batch job must be run after all the forms upload processes have run. This background process selects Ready for Posting tax forms that reference a Form Batch Header ID and that are not yet linked (as Active) to an existing form control. The selected tax forms are grouped by form batch header so that a Pending form control can be created for each unique form batch header. All forms related to the form batch header are linked (as Active) to the form control.
C1-FCMD (Form Control Monitor (Deferred)). This batch job selects form control records that are Pending and validates that the tax forms in the list are valid and in an appropriate state. Once this batch job completes, the processed form controls are ready for approval. Implementations should schedule this based on the business practice of the users that are creating the form controls and the users that are expected to approve the form controls. The assumption is that the approval should be done in a timely manner. So one option is to schedule this job on a frequent schedule, such as every 15 minutes. That way the approvals are processed quickly throughout the day.
C1-FCPTF (Process Form Control Tax forms). This batch job selects form controls that are stamped with this batch code and the current run number and posts the "active" tax forms. This batch job is creating financial transactions among other objects created by posting a tax form and the assumption is that implementations will run this in their nightly batch run.
Refer to Batch Process Dependencies for more information.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]