03.0 Terp24 605 Form-Based Processes

EDUCATION – PUBLIC SECTOR
TAX AND REVENUE MANAGEMENT

IPS520 – TAX PROCESSING
UNIT 3 – FORM-BASED PROCESSES

CONTENT
Introduction
Business Intelligence Overview Tax Processing

Providing Taxpayer
Form-Based Processes
Online Services
Invoicing
Taxes and Revenues Registering Taxpayers
Processing Managing Taxpayer

Property Tax Inquiries
Processing Tax Processing Tax

Objects Submissions
Managing Tax Work Items Amending Tax Submissions
Managing Correspondence Processing Refunds
© SAP – IPS520 – Form-Based Processes / Page 2

FORM-BASED PROCESSES
Content Overview
Form processing within the TRM package
Define scenarios
Define forms
Exercise
Maintain form layout
Exercise
Form bundle type / Revenue type
Exercise
Use table forms
Upload forms
Mass transaction for processing
forms
Tax officer work center
Appendix

Characteristics of form-based processes
FORM-BASED Processes
 Registration activities or tax assessment and calculation are based on incoming
declaration.
 Declarations are validated, exceptions are handled in the work center by a tax
officer.
 In SAP the declaration is represented by the ISR (Internal Service Request)
 The user interface can be designed as Adobe Interactive Form using the Adobe
Designer as part of NetWeaver or as Web Dynpro (ABAP).
 The processing object for the declaration is the form bundle.
Forms Processing – Business Rule Engine

General overview
In the standard, SAP is covering three main form processes: Registration, Tax
Returns and Refund Requests. The available framework is able to process any other
custom form-based process.
As examples of outcomes we can highlight billing documents, master data records,
accounting documents, workflow items, ……
UNIVERSAL WORKLIST
TRM: Processing of tax forms

WORKFLOW INBOX
External
Data stream

Content Overview
Define scenarios
Define forms
Exercise
Exercise
Exercise
Use table forms
Upload forms
forms
Appendix

Define scenarios
Which fields are necessary in

general and how are they
related in each revenue type?
For a complete
understanding of all
What is master data and
?
dependent processes who
can help you in your unit or what is transactional data?
organization ?
Do you have already a clear

idea how the design of the What are the relevant Form
form should look like (e.g. Views for each form bundle?
Corporate Identity)?
Which data types from the Which fields have to be

ABAP dictionary can be calculated for further
used from a technical processing? What are the
perspective? formulas?
Define forms
Version
Customer form dependent views:
 As filed
 As amended
 As calculated
Time View
 As corrected
dependent dependent
 As audited
versions fields
Version Views Fields
Returns Registration
Adobe Livecycle Web Dynpro
Designer
Refunds
..
..
Form processes
Define form - Basic data configuration
Define Forms
 The scenario is used to define the Internal Service Request (ISR).
 In the scenario, you define the fields for the tax form.

Define form – Version configuration
 Only one version of a scenario can ever be valid at a time. Consequently, the
validity periods of different versions must not overlap.
 At this point in time you should not generate the ISR – Form since the form
fields are still not defined.

Define form – Views configuration
This attribute groups the form fields to form views (phases)

Define form - View fields configuration
Define all your fields depending on the form view assigning a field name to a
character type, reference and index number

Define form - Fields attributes configuration
 If you want to compare form field values using form versions, you have to
define the field name in the predecessor form if it is different to the name in the
current form.
 This Configuration will be needed when the tax officer compares values
between periods within the tax officer work center.

Content Overview
Define scenarios
Define forms
Exercise
Exercise
Exercise
Use table forms
Upload forms
forms
Appendix

Exercise – Define Form
3.1 : Form Based Processes

Topic: Define Form
© SAP AG 2009. All rights reserved. / Page 15

Content Overview
Define scenarios
Define forms
Exercise
Exercise
Exercise
Use table forms
Upload forms
forms
Appendix

Maintain Form Layout – Adobe versus Web Dynpro
The layout can be created as Adobe Interactive Form or as Web Dynpro based
on the form scenario previously defined
As Adobe Forms
As WebDynpro

Maintain Form Layout: Adobe LiveCycle Designer
Design Forms
The form design specifies the layout, data capture and final presentation rules for
a specific form handling.
 Adobe LiveCycle Designer integrated in SAPGui

Is a point-and-click graphical form design tool that simplifies the creation of XML
form designs for distribution as Adobe PDF.
 Supporting Features
Form authors can drag-and-drop images and other objects, such as list boxes,
drop-down lists and command buttons, onto their forms. They can design a form,
define its logic, modify it to match paper counterparts or meet strict legislative
requirements, and then preview the form before distributing it.
 Integration of Business Rule Framework (BRFplus)

Form authors can create simple electronic data capture solutions to consolidate
the data they receive from the people filling in the form or from electronic filing. In
addition, form developers are enabled to maintain data capture solutions that read
from, validate against and add to corporate data sources via BRFplus.

Maintain Form Layout – Configuration
 You can arrange the palettes in the workspace to suit your work style, hiding or
docking the frequently used.
 This allows starting the form layout creation making usage of available fields
created before in the form definition.

Maintain Form Layout based on Web Dynpro
Configuration
Tax Officer
Work Center

Using Web Dynpro

Content Overview
Define scenarios
Define forms
Exercise
Exercise
Exercise
Use table forms
Upload forms
forms
Appendix

Exercise – Define / Design Form
3.2 : Form-Based Processes

Topic: Maintain Form Layout with Adobe LiveCycle Designer

Topic: Maintain Form Layout using Web Dynpro

Content Overview
Define scenarios
Define forms
Exercise
Exercise
Exercise
Use table forms
Upload forms
forms
Appendix

Form Bundle type versus Revenue type
 Revenue types correspond to tax types within the tax authority identifying the
source of revenue expected from the taxpayer on submission of the tax returns.
 The form bundle type combines all the forms needed for a specific process
together with the set of rules and assessments required, e.g. Sales and Use
Tax Return or Registration for Corporation Taxes
Revenue type Form bundle type
Form-Based
Rules
Process
Form Revenue
Tax Periods Rules
Types Type(s)
Form
Revenue Revenue
Bundle
Type Type
Type
Transaction Reason Other Form
Types … Codes Configuration Types
Posting Posting
Document Document
Type Type

Form-based process - Configuration
Form-based process
 Each form bundle type is linked to one form-based process
 Classification of real business process: SAP delivers TRM_REGISTRATION,
TRM_RETURN, TRM_REFUND as standard
 Form-based process determines own status profile, correspondence Type for
Confirmation Letter and the configuration variant of the floorplan manager
 Derive different posting control during re-assessment

Revenue type – Configuration I
Revenue type
 Contract account category
 Main and Sub Transaction: If no main/sub transaction is entered in the billing
document then a specific main/sub transaction is used
 Billing document type: Once a tax return is billed a billing document is created.
You can enter here a billing document type for simulated and real billing
documents

Revenue type – Configuration II
Revenue type
 The ID Type defines what alternative business partner number is used in the
tax officer cockpit (e.g. Social Security Number, SSN)
 A revenue type maybe form-based or object-based.
 Joint Filer: Certain tax types such as Personal Income Tax allow for joint filing.
If this flag is set, then a joint assessment of two taxpayers is possible for this
revenue type
 A revenue type is assigned to a contract object type. Several revenue types
may be assigned to a contract object type. The assignment is time-dependent
based on the period key.
 Assignment of workflow definition

Form types - Configuration
Form type
Form Types define what types of forms are used (e.g. Adobe Interactive Forms,
Web Dynpro forms or table forms.
In addition you assign inbound correspondence categories to a form type.

Assign form to form type - Configuration
Form type
In Configuration you have to assign a defined form and its scenario to a form type
in order to control form processing

Form bundle type – Configuration

Form processing activities - Configuration
Form Processing Activities

 Used to categorize different functional actions, e.g. check, simulate, create tax
assessment, suggest form data
 Activities may vary depending on different form bundle types
 Every activity can link to a group of rules
 Result of the activities can be billing, invoicing and PDF document(s)
 Amendment check can be triggered based on activities
 The allowed activities during mass activity processing can be status dependent

Status management overview
Corrected In Processing
Created Processed Processable
In Review
Corrected
UNIVERSAL WORKLIST
WORKFLOW INBOX
External
Data stream

Status management
System Status
 A status the SAP System sets internally as a part of general status management.
 This status tells the user that a certain business transaction was performed
for an object.
User Status
 A status set by the user to complement the system status for a given status object.
 You can use only a user status belonging to a status profile (defined in
Configuration) and assigned to the relevant status object.

System status - Configuration
List of System Status for Tax

1
and Revenue Management
List of Business Transactions for

2
Tax and Revenue Management
Assign system status to

3
business transaction

User Status - Configuration
You can use this activity to create status profiles for your own status (application
status)

Content Overview
Define scenarios
Define forms
Exercise
Exercise
Exercise
Use table forms
Upload forms
forms
Appendix

Exercise – Form Type and Form Bundle Type

Topic: Define Form Type and Form Bundle Type

Content Overview
Define scenarios
Define forms
Exercise
Exercise
Exercise
Use table forms
Upload forms
Exercise
forms
Appendix

Tax return – Multiple line items – Cover form (summary)
Cover Form
The cover form contains the summary of all filed item lines, checks the
consistency of the individual item lines and calculates the filed and amended
sums and triggers messages in case of missing or wrong data

Tax return – Multiple line items – Table form
Table Form
The table form contains the individual line item information as defined in
configuration. It contains the mass data to be summarized and checked in the
cover form and diverse functionalities are available e.g. to copy or to transfer
data to new or other form bundles

Define table forms - Configuration
For the usage of table forms a cover sheet and at least one schedule is
required. The cover sheet is created as an ISR scenario. The schedule is defined
as table form using the data dictionary.

Content Overview
Define scenarios
Define forms
Exercise
Exercise
Exercise
Use table forms
Upload forms
forms
Appendix

Upload forms: Data model
Header (DFMCA_RETURN)
Form bundle data model
Return Attributes (DFMCA_RETURN)
 Revenue Type
 Taxpayer
 Joint Filer
 Taxpayer ID Tax Form (DFMCA_FORMS)
 Joint Filer ID
Form Attributes (DFMCA_FORMS)
 Account
 Form ID
 Registration ID Form Data
 Receipt Date DFMCA_FORM_VERS
 Joint Account 1:n 1:n
 Amendment
 Joint Registration Link to Document
 Archive Link
 Applied from/to
 Period Key
 Authorization Group
 Consolidated by
 Duplicate to
 Form Process
 Consolidated Return
 Dates (Postmark etc.)
 Attributes (Transaction Code etc.)

Change upload forms – Configuration
The TRM application allows you to log changes to the tax return and form data.
The changes are stored in change header table CDHDR and items table CDPOS.
Changes of the tax return header are stored with object ID FMCA_RETURN,
changes of form data are stored for object ID FMCA_FORMDATA.
In Configuration for the form views you can flag what views shall be logged for
changes.

Upload forms: Migration Workbench
UNIVERSAL WORKLIST
WORKFLOW INBOX
External
Data stream

Upload forms: Technical overview - Data load
Mainframe or
Migration
Client/Server Client/Server Dictionary Objects
Configuration
Program Module
Generation Migration Configuration
<INCLUDE RS3Nobj >

Import
FORM RS3Nobj.
LOOP AT R2_r2tab.
Program
PERFORM RS3Iobj_LOOP_ST .
CHECK LCODE EQ ‘X’.
CLEAR r3tabs. “zu r2tab
LOOP AT R2_r2tab.
F ...
ENDLOOP.
I PERFORM RS3Iobj_IC_r3tab USING RCODE.

IF RCODE EQ ‘X’.
“Regelverarbeitung r3tab entspr. TUMRE
L IF MG_TESTL NE ‘X’.
INSERT r3tab.
ENDIF.
E PERFORM RC_CHECK USING ‘r3tab’ .
PSCD/
ENDIF.
- “Langtexte zur r2tab

ENDLOOP.
T ENDFORM.
R
A
TRM
N
S
F PSCD file
E system Direct Input
R
Interface
Structure
Legacy
Key and status
System Restart Management
Company code 0199 not found.
legacy system key ABC1234
entry A123 not found in table Txyz
Customer project ...
Error File Error Log

Upload forms: Functions available on data import screen
Start import
Start batch runs in dialog Schedule
import runs import runs in
immediately batch
Display
migration Create / delete
statistics migration files
Display Error Edit/display

log migration files
Display KSM Overview over

entries migration files
File splitting and Performance

conversion Mass job monitors
scheduling
Upload forms: Field rules - Complex rule
$C$ source field (cusotmer)

$S$ target field (SAP)
ABAP code
The transferred value from the
legacy system is available in
variable $C$.
The field in the SAP structure
is denoted by $S$.

Content Overview
Define scenarios
Define forms
Exercise
Exercise
Exercise
Use table forms
Upload forms
forms
Appendix

Mass Transaction for Processing Forms
UNIVERSAL WORKLIST
WORKFLOW INBOX
External
Data stream

Mass Transaction for Processing Forms
Mass Transaction
FMCAPFPF
 Mass transaction for

processing forms
 Calls BRFplus
 Started per (or)
 Process (return, registration,
refund)
 Form Bundle Type
 Form Processing Activity
(mandatory)
 Period Keys
 Simulation mode available
 BRFplus trace displayed in

Content Overview
Define scenarios
Define forms
Exercise
Exercise
Exercise
Use table forms
Upload forms
forms
Appendix

UNIVERSAL WORKLIST
WORKFLOW INBOX
External
Data stream

Tax officer work center – Universal work list (UWL)
Tax Officer Work Center…

 Is based on NetWeaver Portal technology
 Is also known as the „Cockpit“
 Contains the Tax Return Worklist
 Includes all tax related functionalities based on portal roles
 Provides additional cross-application functionalities to execute e.g. PSCD master data
maintenance or Financial Customer Care processes within one portal platform

Tax officer work center using the NetWeaver Business Client
SAP NetWeaver Business Client

(NWBC), offers a unified
environment for and a single point
of entry to SAP business
applications and technologies.

Configuration of NetWeaver Business Client Workflow Inbox
 By default the following two TRM tasks are automatically displayed in the
NWBC inbox: TS22600008, TS22600061 in case the user is included in the list
of possible workflow agents.
 In case of customer created tasks, these tasks have to be added to the

following views (transaction sm30)*
 IBO_C_WF_CAC
 IBO_C_WF_TAC
 IBO_C_WF_TTAC

Tax return work item
Identification Area
Application Toolbar Related Services

Navigation Panel
Content Area
Application Toolbar Related Services

Form-based tax return
Tax return processing:

 A filed tax return is processed via BRFplus
 Warnings/ Errors are displayed in the message area triggered by BRFplus
 The tax officer works through the messages and can enter comments if
necessary
 Filed, supplemented, calculated, corrected and checked values are displayed
according the form design

Floorplan manager (FPM)
Floorplan Manager (FPM)

The Tax Officer Work Center is based on the Floorplan Manager (FPM).
Floorplan Manager (FPM) is a Web Dynpro ABAP application that provides a framework for
developing new Web Dynpro ABAP application interfaces consistent with SAP UI guidelines.
Application FPM Dynamic Floorplan

Windows Configuration Adaptations Application
+ + ==
ABAP
APIs
Applications provide the application specific UI FPM ensures consistency and guideline compliance
Appendix
Content Overview
Define scenarios
Define forms
Exercise
Exercise
Exercise
Use table forms
Upload forms
forms
Appendix

APPENDIX – FORM-BASED PROCESSES
Form Builder: Data view palette
General function
The data view contains all objects you
defined and some standard objects like
general header data, control parameters
or user information. You can create the
content of a form design to correspond to a
full or partial data source. The available
data sources include XML schemas,
sample XML data files, and WSDL files.
Object binding
Once you connect to a data source, you
can bind an object in the form design to a
node in the data view palette. After
connection your field is enriched with an
icon and interacts with the data source.

Form Builder: Hierarchy palette
General function
This palette is a graphical representation of
the contents in the body pages and master
pages tabs.
Defining page structures
All forms contain a root (parent) subform,
and every body page is created with a
default subform that covers the whole page.
When you add objects to a body page,
including another subform, the objects are
wrapped in the default subform for the page
automatically.
Clear overview
In addition, whatever you select in the
hierarchy palette is also selected in the
master page or body page it is associated
with.

Form Builder: Layout, font & paragraph palette
Layout palette
This palette displays the following
information about the selected object:
 The size and position of the object in
the page
 The position of the anchor point
 The margins
 The caption position and width
 Object depending properties
Font palette
Use this palette to change the font family,
size, and style of text in the selected object.
Paragraph palette
This palette lets you change the alignment,
indents, and line spacing of the selected
text. You can also set the radix alignment
for a numeric field object.

Form Builder: Object & border palette
Object palette
Use the object palette to modify properties

that are specific to the selected object. The
object that is selected in the layout editor
determines which tabs are available in this
palette.
Border palette
Use the border palette to edit the border

properties for objects in the form design.
You can edit the borders individually (left,
right, top, and bottom) or together. You can
also specify the type of border corner and
background colours.

Form Builder: Drawing aid palette
Drawing aid palette

 Use the drawing aids palette to specify the
layout editor grid and ruler settings and
drawing units. You can also show or hide
object boundaries.
 The horizontal and vertical rulers, the grid,
and the long crosshairs help you position
objects precisely across the width or length
of a body or master page.
 When visible, rulers appear along the top
and left side of the active body or master
page. Markers in the ruler display the
pointer's position when you move it.
Changing the ruler origin lets you measure
from a specific point on the image. The
ruler origin also determines the grid's point
of origin.

Form Builder: Script editor
Script editor
Using the script editor, you can write scripts to
increase the form design's interacting
capabilities. As part of the form design
process, a form developer can create own
functions tailored towards own custom form
processing needs.
JavaScript and FormCalc are supported.

Form Builder: Library palette
General functions
This palette contains all the objects that you
can add to a form design. Objects are
organized into groups. Each group is
contained in a tab labelled with the group's
name.
Available objects
 The standard tab contains the core
drawing objects. The barcodes tab
contains a list of standard barcode objects,
and the custom tab contains individual
objects included with the designer and
your own defined ones.
 It is possible to enrich your library with
further individual tabs to meet your needs.

Form Builder: Report palette
Report palette
 The report palette provides information
about the form design. You can view one or
more of the following reports:
 A list of all fields that have normal data
binding
 A list of all fields that have binding by
reference
 A list of all fields that have global data
binding
 A list of all fields with no data binding
 A list of unbound data connection
nodes
 The warnings tab lists errors and
messages that are reported as you
work in the form design

Form Builder: Layout editor (design area)
Layout editor
 You create the body and master pages for
the form design in the layout editor using the
surrounding palettes.
 You can also view and edit the form design's
XML source and preview the editable form
as PDF.
 The PDF preview tab only appears when
Acrobat or Adobe Reader is installed.

Upload forms: Data migration design - Implementation (I)
The data import of forms provided by any of the form-based processes is

performed using the Migration Workbench. This tool allows an upload of forms on
a periodicity to be defined by the customer.
 Open, documented interface structures
 Independent of the source system or its data model

 Transfer in object-oriented form (business objects)
 Transfer structures can be adjusted as required
 Reduction of data stream from source system
 Transfer controlled by Configuration (IMG)
 Conversion rules for each field can easily be created and changed
 Data saved by means of PSCD Service Modules
 Optimum consistency checks

 Fast direct input instead of batch input
Upload forms: Data migration design - Implementation (II)
 Key and Status management in PSCD

 Transferred legacy system keys are mapped to PSCD keys
 Interface description
 Display of the structures, their layout, their fields
 Display of sample import files
 Migration-specific documentation
 Test data generation / file editing

 Manual creation of test data
 Editing of import files
 Functions for creating, changing and deleting import files
 Statistic and logging functions

 Information about running and finished imports
 Error description and error files
 Massively parallel import of data possible

 To achieve high throughput
Upload forms: Concept of the ‘Migration company’
 The concept of the “Migration Company”
 All parts of the migration configuration is client-independent

 Introduction of the ‘(Migration) Company’ to distinguish between
different settings. Each Migration Company represents a Migration Project
 Necessary for different migration projects in the same system
 The company ‘SAP’ is included in the shipment and can be used as
reference. The settings in this company will be overwritten with each
upgrade.
 Starting the Migration Configuration
 Maintain the migration users and authorization for the migration

 Define an own company. This is done in the Migration Workbench
 Copy the necessary migration object PS_RETURN from company ‘SAP’ to
your own company
 Collect information about the migration objects from the migration
documentation.

Upload forms: Main screen of the migration workbench
Auto data fields

• Fields of automation
data structure
• Carry the conversion
rules
• Can be (de-)activated
Migration object Automation data structure
Business object / logical Structure used by the

unit equals input data of service module for direct
an PSCD transaction input processing of the
represented by an PSCD corresponding transaction
service module (DI) (data container)

Upload forms: Automation data structures - Configuration
Automation data of migration objects represent the maximum input for one direct
input module
 Fields of the Automation Data Structures can be switched off
 Mandatory fields cannot be switched off
 The remaining fields form the so-called ‘Customer Structure’, which is a

customized Automation Data Structure, reduced by a number of fields
 Result is a set of Customer Structures for one Migration Object. This set of
structures can be displayed and downloaded
 The import program reads the data in the layout of the customer structure
 Using a set of customized automation data structures generates an import

process for the necessary fields only!

Upload forms: Data import

Upload forms: Data import screen
Runtime information
Name of server and file
directory, work process
type and char. set.
File name
Name of the sequencial
file that contains the
data to be imported.
Maintenance buttons
File information Here you can create,
Information from the file change, display, delete
header. the import files

Upload forms: File details
Header information
Name of the migration
object and the file
PSCD_MIGRATION
creation data
Record information Data

Upload / Download
Record length, legacy Presentation of data
Import / Export record
system key and data record from
From / To text file
type of the record corresponding data set

Upload forms: Import file maintenance screen I
PSCD_MIGRATION
Help / Information F1 and F4

help available for each field
Data
Field-by-field presentation of
data; change possible

Upload forms: Import file maintenance screen II
PSCD_MIGRATION

Upload forms: Data import screen - Import control data
Test and Restart

These options allow a
dialogue-like behavior or
a restart of an import
Commit interval
Cancellation Some migration objects

allow lower commit
Defines error margins of
frequencies
the import process
(performance)

Upload forms: Upload strategies
When uploading tax returns the data structure provided by the taxpayer is to be
mapped to the corresponding TRM structures.
By maintaining rules for the fields of your migration object you can derive the
corresponding values.
 Taxpayer files with Identification Number (e.g. Social

Security Number)
 Business partner may be derived from identification number
 Contract account may be derived based on revenue type provided in tax
return and business partner derived before
 Contract object is derived based on the period key and revenue type and
the business partner derived before
 Taxpayer provides business partner and contract object

ID on tax return
 Contract account may be derived based on revenue type and business
partner provided in tax return

Upload forms: Assigning field rules
Initial value (no action necessary)
Choose/define a fixed value for

Fixed value the assigning to this field
Assign (Move) (no action necessary)
Field Define ABAP code that has to be

Business Partner Complex rule executed during processing of the
value of this field
Choose a top-object (migration

From KSM object whose key represents the
value of the field)
Choose/define a conversion
Translation object for assigning output values
to this field
DFMCA_RETURN (Tax Return)

Field Business Partner
How to enhance cockpit to build custom and interactive features
Basics:
 The cockpit is wrapped by FPM (Floorplan Manager) and button actions by FPM
events
 A BRFplus round-trip call is an FPM event triggered by a button action
 Standard actions hardly have any user interactions
Steps to make enhancements:

 Enhance cockpit user interface through component configuration by FPM
 Design the user interface for the custom logics in Web Dynpro
 Implement a dedicated interface for the Web Dynpro
 Link the Web Dynpro to the cockpit in Configuration
 Enhance BADI implementation for the relevant form-based process

Start component configuration for the cockpit
FMCA_WDY_FPF is the application configuration for the tax return cockpit

Start component configuration for the cockpit - Continued

Add a new triggering pushbutton in the identification area
FPM Event ID is used

technically to map the UI
button to the backend logic

Design the user interface for the new action
A new Web Dynpro has to be built to serve as the action presenter and carrier.
The interface IF_FMCA_WDY_FPM_EVENT_POP has to be implemented to enable the data
swap. GET/SET function can handle all return header / form data as well as user defined
interaction parameters.

Link the Web Dynpro and the FPM event ID

BADI implementation
CL_FMCA_FPF_FORMPROC_REG,
CL_FMCA_FPF_FORMPROC_TAXRETURN,
CL_FMCA_FPF_FORMPROC_REFUND are BADI implementations for all events
in the cockpit for all kinds of standard form-based processes.
If the user popup is expected

according to the configuration,
make sure the
abap_undefined is returned by
var er_result to the caller
function. Otherwise, the Web
Dynpro dialog will be
disregarded

03.0 Terp24 605 Form-Based Processes

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

03.0 Terp24 605 Form-Based Processes

Uploaded by

Copyright:

Available Formats

EDUCATION – PUBLIC SECTOR

TAX AND REVENUE MANAGEMENT

UNIT 3 – FORM-BASED PROCESSES

Business Intelligence Overview Tax Processing

Processing Managing Taxpayer

Processing Tax Processing Tax

Managing Tax Work Items Amending Tax Submissions

Managing Correspondence Processing Refunds

© SAP – IPS520 – Form-Based Processes / Page 2

Form processing within the TRM package

© SAP – IPS520 – Form-Based Processes / Page 3

 In SAP the declaration is represented by the ISR (Internal Service Request)

 The processing object for the declaration is the form bundle.

Forms Processing – Business Rule Engine

TRM: Processing of tax forms

© SAP – IPS520 – Form-Based Processes / Page 5

Form processing within the TRM package

© SAP – IPS520 – Form-Based Processes / Page 6

Which fields are necessary in

Do you have already a clear

Which data types from the Which fields have to be

Version Views Fields

© SAP – IPS520 – Form-Based Processes / Page 9

© SAP – IPS520 – Form-Based Processes / Page 10

This attribute groups the form fields to form views (phases)

© SAP – IPS520 – Form-Based Processes / Page 11

© SAP – IPS520 – Form-Based Processes / Page 12

© SAP – IPS520 – Form-Based Processes / Page 13

Form processing within the TRM package

© SAP – IPS520 – Form-Based Processes / Page 14

3.1 : Form Based Processes

© SAP AG 2009. All rights reserved. / Page 15

Form processing within the TRM package

© SAP – IPS520 – Form-Based Processes / Page 16

© SAP – IPS520 – Form-Based Processes / Page 17

 Adobe LiveCycle Designer integrated in SAPGui

 Integration of Business Rule Framework (BRFplus)

© SAP – IPS520 – Form-Based Processes / Page 18

© SAP – IPS520 – Form-Based Processes / Page 19

© SAP – IPS520 – Form-Based Processes / Page 20

© SAP – IPS520 – Form-Based Processes / Page 21

Form processing within the TRM package

© SAP – IPS520 – Form-Based Processes / Page 22

3.2 : Form-Based Processes

3.3 : Form-Based Processes

© SAP AG 2009. All rights reserved. / Page 23

Form processing within the TRM package

© SAP – IPS520 – Form-Based Processes / Page 24

Revenue type Form bundle type

© SAP – IPS520 – Form-Based Processes / Page 25

© SAP – IPS520 – Form-Based Processes / Page 26

© SAP – IPS520 – Form-Based Processes / Page 27

© SAP – IPS520 – Form-Based Processes / Page 28

© SAP – IPS520 – Form-Based Processes / Page 29

© SAP – IPS520 – Form-Based Processes / Page 30

© SAP – IPS520 – Form-Based Processes / Page 31

Form Processing Activities

© SAP – IPS520 – Form-Based Processes / Page 32

Created Processed Processable

TRM: Processing of tax forms

© SAP – IPS520 – Form-Based Processes / Page 33

© SAP – IPS520 – Form-Based Processes / Page 34

List of System Status for Tax