Ansicht
Dokumentation

ISPSCA_TRM_SCENARIO - Define Forms

Addresses (Business Address Services)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

You can define forms in this IMG activity.

Each form consists of a form scenario that can exist in several versions.

Note:
Only scenarios for application T and object type P are supported in Tax and Revenue Management (TRM).

Transparent Tables for Forms (TTF)
You can save form fields and customer form data in transparent tables in the ABAP environment. This is a high-performance storage alternative to the Business Document Service (BDS) using XML strings. You activate the TTF when you create a new version in the activity Versionby choosing Additional Data for Scenario -> New Entriesand selecting Activate Transparent Table for Forms. For more information, see Activation of Transparent Tables for Forms.

For TTF forms the features form comments and phaseless forms are supported. The features can be activated in the activity Version under Additional Data for Scenario.

SAP delivers various scenarios, such as SP11 to SP13 for different values of income tax. Furthermore, SAP delivers different values for views, such as view A for filed values or view C for calculated values. Check your Customizing system for a list of the delivered values.

1. Create your scenario. To do so, specify an identification (ID) and description for your scenario, select application T and then save your entries.
2. Mark the scenario that you have just created and double-click the Versionentry on the left hand side. Create the required versions and their validity and select one version as the active version. Choose Entry using Adobe PDFfor the entry type on the Web.

Note:
Each version is valid in a period that you define. These versions can overlap. However, this does not apply to versions flagged as active.
If you do not enter a form name, the system automatically generates a form named ISR_FORM_XXXX (XXXX=ID of the scenario) when executing the current Customizing activity.

Caution:
The system automatically assigns different form names if the form exists in different versions. For example, the form in form scenario SPI1 (income tax) is called ISR_FORM_SPI1 in version 0 but ISR_FORM_SPI1_1 in version 1. The different names are prerequisite for the system deriving the scenario version from the form names.

1. For each version you define whether the data of an ISR form is to be extracted to make it available for business warehouse (BW) analysis. To do so, enter the relevant DataSource by clicking the Additional Data for Scenario pushbutton. There you can also trigger a check functionality to check whether ISR form data and extract structure contain consistent data after you have both of them generated.
   

TTF Storage:
By choosing Additional Data for Scenario,you navigate to the TTF-settings for the current scenario and version. For more information, see Activation of Transparent Table for Forms.

1. Check whether you need additional views on top of the ones provided by SAP. You can see which views are provided in your Customizing system.
2. Select a form view and double-click the Form View Fields entry on the left-hand side. Enter all form view fields that you want to see in your Web Dynpro/Adobe PDF form.
   

Caution:
Note that for technical reasons the form view fields are called characteristics in the current Customizing activity. When defining the fields of a view, the field name must start with the technical key of the view as a prefix, for example A_Field1 for field1 in view A and B_Field1 for field1 in view B.
You define field values for each view individually. SAP provides different views for which you can assign authorizations. You can assign an item number to each view. This number controls in which order the views are offered in the Tax ProcessingWeb Dynpro application. In addition to this, the item number determines which values are displayed when one view is selected; all views whose item number is smaller than the one selected are also displayed. The assignment of authorizations enables you to control which users can display which view.

Note:
Best practice has shown that it is most efficient to name the fields as A_FO1_* with A representing view A and F* the sequence in which the field is to appear on the form. To define fields for several views, you can copy existing entries. To do so, you first create the field in one view, select the Copypushbutton and then change the prefix and sequence number (if applicable).

1. To compare values from different versions of a form in your Tax ProcessingWeb Dynpro application, you select the form view field, double-click the TRM Fields Attribute entry on the left-hand side and make the required entries.
2. In the TRM Fields Attribute area you can also define which form fields you want to analysis in BW. If you mark the extraction-relevant field, the system automatically defaults the field name. The derivation of this field name is done via event P343. The system shows this field name in the DataSource as well as in the program that generates the DataSource for an ISR form. For more information, about this program, follow this link.
   If you are using BRFplus as the rules engine for tax returns validation and tax calculation you can enter a table name for form fields. Customizing activity Define BRFplus Objects for Form Bundles generates one BRFplus data object of the type 'table' for all fields assigned to one table name.

Caution:
Be very careful when assigning fields to table names as you can neither undo the assignment nor use this field for any other assignment.

1. To display identical forms with different templates, you can define related scenarios. The physical storage of forms from related scenarios is identical. The only difference ís the way in which they are displayed. For example, you can have a long and a short template version of one identical form. When working in the Web Dynpro application for Tax Processing, the tax officer can choose one of them.
   Furthermore, you can make a form template available for Enterprise Services. To do so, choose the external usage for the related scenario. If you do not define related scenarios, the system displays the (base) scenario as long template version in the Web Dynpro application for Tax Processing and the Enterprise Services.
2. After you have finished all settings for the form, you select the Versions entry on the left-hand side and generate the form. The program writes the form and the interface automatically in the relevant fields once you have generated the form. Then additional functions are available on the interface for processing the form.

Note:
It is also possible to define form types directly using transaction SFP.

General Data in Customer Master   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 8561 Date: 20240523 Time: 171510     sap01-206 ( 173 ms )