The base product provides the form upload staging business object C1-FormUploadStaging that was designed to be generic such that your implementation can use it out of the box.
This BO has a raw XML (CLOB) field that is used to hold the actual form details. Staging the form details as raw XML provides the following benefits:
A uniform way of interfacing form details:
For different types of forms
From various external sources that may upload data for a particular form type using different record structures/layouts.
External sources and Process X (i.e. the process that reads the input files and stores the form data into the form upload tables) do not need to know about the structure of the tax form and registration form business objects in the system.
Form details can be uploaded into the system with minimal validation.
As forms change in structure from year to year or as new form types are added, there is no need to create new form upload staging business objects. Your implementation just needs to configure new form upload staging types (that reference the generic form upload staging BO), and define the mapping logic for the new forms.
The mapping logic configured on the form upload staging types takes care of transforming the data. This BO also has a transformed XML (CLOB) field that holds the transformed data. The value of this field is used when the tax / registration form is added.
Use C1-FormUploadStaging if the structure and lifecycle suits your implementation's form batch headers. As with any base BO, your implementation can extend the BO's processing logic by adding/overriding algorithms and BO options.
If your implementation needs to capture additional information, you can do any of the following:
Inherit from the base BO - if the base BO lifecycle and processing logic works for you.
Copy the base BO or create an entirely new BO - if your form upload staging records have a different lifecycle
Refer to existing help on configuration tools for more details on configuring business objects.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]