Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction

EMIGALL)

Applies to:
Tax and Revenue Managements.

Summary
With Enhancement Package 5 Tax and Revenue Management includes new functionality (e.g. Table Forms) to supports all kind of tax types that require tracking of information based on multiple line items e.g. to be declared by an employer. This cookbook describes all the necessary steps to upload tax return header data, form data and table form data using the Migration Workbench (transaction EMIGALL). Author: Diego Gaudenzi

Company: SAP America Created on: 1 May 2011

Author Bio
Diego Gaudenzi has worked at SAP since January 2001. He joined the IBU Public Sector and worked as a software developer for 8 years and started his current position as Solution manager for Tax and Revenue Management in 2009.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 1

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

Table of Contents
Introduction ......................................................................................................................................................... 3 EMIGALL ............................................................................................................................................................ 3 PS_RETURN Migration Object ....................................................................................................................... 3
Prerequisite .................................................................................................................................................................. 3

BAPI Migration Object ..................................................................................................................................... 9

Table Form Data .......................................................................................................................................................... 9

Related Content ................................................................................................................................................ 17 Copyright........................................................................................................................................................... 18

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 2

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

Introduction
In Tax and Revenue Management, the data import of forms provided by any of the form-based processes is performed using the Migration Workbench (transaction EMIGALL). This tool allows an upload of forms on a periodicity to be defined by the customer. The following example describes how to import data to Table Forms (cover sheet and at least one schedule) which are defined In the IMG activity Define Table Forms. The functionality of table forms supports all kind of tax types that require tracking of information based on multiple line items e.g. to be declared by an employer. An example is the tax return for unemployment tax paid by the employer that 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 (ISR). The schedules are defined as table forms using the data dictionary. A table form can have header data (optionally) and line items.

EMIGALL
You use the migration workbench (transaction EMIGALL) to upload the data. You have to use migration object PS_RETURN for the upload of tax return header data, form header data and the data that is stored in the form itself (ISR form data only). To upload table form data, you have to use separate BAPI Migration Objects. PS_RETURN Migration Object Prerequisite Structure TAX_FORMS within Migration Object PS_RETURN should have field FORM_CLASS available to be used:

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 3

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

If field FORM_CLASS is not visible in Auto. Structure TAX_FORMS you can add it up executing the following steps:

After the field is displayed, double click on it to change processing type from 1 to 3, save and go back to the initial screen:

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 4

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

The new field should now be displayed:

If you added up the field FORM_CLASS, you will need to regenerate the Report (Migration Object Generate Report) To upload the coversheet data, use Migration Object PS_RETURN and manually enter the data for the required data types (e.g. RETURNS, FORMS and FIELDS). For this example the coversheet data will be loaded for ISR Form ISR_FORM_SUET.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 5

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

Enter a File name and click Create pushbutton:

Enter data for the required data types as shown on this screen shot:

Notes: The two lines of Data type FORMS highlighted in yellow above are needed; the first entry indicates the Adobe or Webdynpro form which is represented by the Internet Service Request ISR structure and the second entry indicates the Table Form. On this example just three fields are used with Data Type FIELDS located in to ISR_FORM_SUET structure. Any other ISR structure can be used in the same way and any number of FIELDS entries can also be used. You can generate the unique key for the tax return (e.g. RETURN_ID and CASE_GUID) in transaction SE37 using function module GUID_CREATE. CASE_GUID used for Rec. data type FORMS with FORM_CLASS empty and FORM_CLASS = TL is different.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 6

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

Here the RETURN entry:

Here the ISR Form entry (FORM_CLASS = space):

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 7

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

Here the Table Form entry (FORM_CLASS = TL):

After all the data is entered the Data Import can be executed (Migration Object Data Import):

Finally check if your data was uploaded correctly looking at the Statistics report or looking into table DFMCA_RETURN and searching for the new entry using the master data entered above on the Rec. Data Type RETURN entry.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 8

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

BAPI Migration Object Table Form Data To Load the Table forms a new Migration Object has to be created using migration class BAPI and as a Service Module point out to the Function Module that will create the entries in the Table. In this example, I am using function module FMCA_TF_MIGRATE_UET delivered in Function Group FMCA_TF_SAMPLES within Package FMCA_TRM_SAMPLES and can be used as a reference to create a new Function Module to upload any other Table Form. To create the new Migration Object go to the menu Migration Object Create, enter Migration object (e.g. UET_TABLE), enter Migration Class BAPI and click :

Enter Mig. Obj. abbr., Service module and press enter:

Click YES to the question on the popup window:

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 9

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

Go back using the green arrow:

New Migration Object is created

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 10

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

Double click on the new Mig. Object and double click on the Auto. Struct. FORM_KEY:

Click on Menu Automatic structure Change and change the Rec. data Type from DAT001 to KEY and click on Save

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 11

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

Double click on Auto. Struct. LINE_ITEMS:

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 12

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

Now click again on Menu Automatic structure Change and change Rec. data type from TAB001 to LINE_ITEMS and finally click on Save and the green arrow to go back to the initial screen:

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 13

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

Select your Migration Object and click on Migration Object Generate Report:

Now Select Migration Object Data Import, enter a File name and click

Notes: When entering the data for the Mig. Data Type KEY It is important to pay attention to the FORM_GUID and to the RETURN_ID: The RETURN_GUID should be the same as the RETURN_ID used in Mig. Object PS_RETURN The FORM_GUID should match to the CASE_GUID used in Mig. Object PS_RETURN used to upload the coversheet (for entry with FORM_CLASS = TF)

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 14

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

Enter data for Rec. Data Type KEY:

Enter data for Rec. Data type LINES. This data will be uploaded into the Table Form:

Notes: Enter as many Rec. Data type LINES as you wish.

Example of the Mig. Object with two lines on the Table Form:

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 15

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

Go back to the initial screen. After all the data is entered the Data Import can be executed (Migration Object Data Import):

Finally check if your data was uploaded correctly (e.g. Statistics). At this point the upload is finished and all the Form data (header and table form data) should be written in the following tables: DFMCA_RETURN

DFMCA_FORMS

DFMCA_TF_UET_L (Transparent table created to hold the Table Form Data):

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 16

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

Related Content
Uploading Tax Forms Using Table Forms

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 17

Step by Step How to Upload a Tax Return that Contains Table forms using the Migration Workbench (Transaction EMIGALL)

Copyright
Copyright 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 18