You are on page 1of 2

Define Table Form

Use

In this Customizing activity you define templates for table forms that the tax officer can see in his work center
and use to create his own table forms. Table forms are used for tax returns with attached schedules that
contain a large number of line items. To improve performance, SAP recommends that you use table forms for
this type of tax return.

Example:
The tax return for unemployment tax paid by the employer contains aggregated values on the cover
sheet as well as schedules that contain the line items that make up the aggregated values. The
potential volume of the line items within these schedules can reach thousands of lines within each tax
return.

To use table forms you require a cover sheet and at least one schedule. The structure of the cover sheet is
defined based on the Internet Service Request. For the user interface you can either use Web Dynpro for
ABAP or generate and configure an Adobe Interactive Form. The schedules are defined as table forms using
the data dictionary. A table form can have header data (optionally) and line items.

Requirements

 Business Package BP ERP TAX OFFICER 1.51 is applied to your system.

 You have defined the structure of your cover sheet. For more information, see Define Forms.

Activities

Definition of table forms implies the following steps:

1. Create the table


To do so, you use transaction code se11.
First, check whether all of your fields exist as data elements. If this is not the case, you have to create
your own data elements.
Then you create your table. SAP has delivered two structures FMCA_TF_TAB_KEY_H and
FMCA_TF_TAB_KEY_L for the key fields of header table and line item table. SAP recommends that
you first create a structure that holds all of your tax related fields. Then you create a table that includes
SAP's predelivered key structure and your business related structure. For BI reporting purposes you
can add a time stamp field with data element timestamp.
Note
SAP delivers examples for tables, such as DFMCA_TF_UET_L for unemployment tax that you can use
as reference.
2. Create Change Document Objects
Change document objects make sure that changes in your tables are recorded properly. To create a
change document object, enter transaction code SCDO and choose the Create function.
Add the line item table you created in the previous step, and - if available - the header table.
Afterwards choose the Generate update pgm pushbutton.
Note
SAP delivers examples for change document objects, such as FMCA_TF_CDO_UET for
unemployment tax that you can use as reference.
3. Define the table form

o To do so you execute the current Customizing activity.

o Enter a name for the table form, for example UNEMPLOYMENT_TAX.


o Mark this table form as active.

o Choose your intended time frame (valid from/valid to).

o Enter the name of the table you created before.

o Enter the change document object you created before.

o If you want to use a different layout for the header area of your table form than the one
provided by SAP, you have to create your own implementation of the WebDynpro Interface
IF_FMCA_TF_FORM_HEADER and enter its name in the WebDynpro Component for
Table Form Header field.

o If you want to use customer-specific logic for a table form, you can implement class interface
IF_FMCA_TF_DATA_HANDLER, and put your validation logic into method
CHECK_FORM_DATA and your derivation logic into method SUGGEST_FORM_DATA.

4. Execute the current Customizing activity. The program imports all fields that you have defined in
your table(s). Subsequently, you can reorder the column sequence and deactivate or activate a field's
visibility for your line item and - if applicable - header table.

For information on the different options for header and line layout, see the field help in the Customizing
activity.