asset data migration

IMPLEMENTATION PAPER_FUNCTIONAL AND DEVELOPMENT

(IP_FD)

♦

IP DATA MIGRATION ASSETS

IP-NUMBER:<NUMBER>

Document reference <IP Number>_IP_FD_<IP Name>Document type (e.g. GAP IP Functional X) GAP IP Functional DevelopmentOwner (company) AMOS SELast edited by GRP@AGALast edited on <yyyy-mm-dd>

Development Functional and Technical Specification

Table of Content

1 General Information............................................................................................................................. 6

1.1 Document Change History...................................................................................................................6

1.2 Purpose of this document....................................................................................................................6

1.3 Business Needs and Requirements.....................................................................................................7

1.4 Open Issues........................................................................................................................................ 8

2 Functional Description......................................................................................................................... 9

2.1 Solution Overview................................................................................................................................ 9

2.2 Legacy Asset Data Transfer..............................................................................................................10

2.2.1 Set Company Code Status................................................................................................................10

2.2.2 Specify Sequence of depreciation areas...........................................................................................10

2.2.3 Specify Transfer Date / Last Closed Fiscal Year...............................................................................10

2.2.4 Specify Last Period Posted in Previous System (Transf. During FY).................................................11

2.2.5 Transfer Foreign Currency Values...............................................................................................11

2.2.6 Recalculate Depreciation for Previous Years....................................................................................12

2.2.7 Set Reconciliation Accounts (Manually).............................................................................................12

2.3 Impacted business process...............................................................................................................12

2.4 Impacted sub-process....................................................................................................................... 13

2.5 Data Requirements............................................................................................................................ 13

3. Technical Description – Development Types.....................................................................................14

2.1 SAP Enhancement............................................................................................................................ 15

3.1.1 Table Access Diagram....................................................................................................................... 15

3.1.2 Custom Tables / Structure in SAP.....................................................................................................15

3.1.3 Data Validation.................................................................................................................................. 16

3.1.4 Data Flow Diagram............................................................................................................................ 16

3.1.5 Pseudo Code..................................................................................................................................... 17

3.1.6 Technical details................................................................................................................................ 17

3.2 SAP Conversion................................................................................................................................ 22

3.2.1 Data Cleaning Requirements.............................................................................................................22

3.2.2 Extract Logic...................................................................................................................................... 22

3.2.3 Currency and Units of Measure.........................................................................................................22

3.2.4 Language of Texts............................................................................................................................. 22

IP_FD <IP Number> <IP Name> page 2 of 77


3.2.5 File Layout (In Sequence).................................................................................................................. 23

3.2.6 Selection Screen Details (if applicable).............................................................................................23

3.2.7 Starting Condition (Optional).............................................................................................................23

3.2.8 Business Rules (Optional).................................................................................................................23


3.2.10 Selection Criteria............................................................................................................................... 24

3.2.11 Data Conversion & Interface Definition..............................................................................................24

3.2.12 Data Mapping Matrix.......................................................................................................................... 25

3.2.13 BDC Method...................................................................................................................................... 25

3.2.14 LSMW................................................................................................................................................ 26

3.2.15 ALE Configuration (optional)..............................................................................................................28

3.2.16 Custom Dictionary Objects (optional)................................................................................................30

3.2.17 File Layout......................................................................................................................................... 30

3.2.18 Performance Considerations (optional).............................................................................................30

3.2.19 Dependency...................................................................................................................................... 30

3.2.20 Relevant Function Modules...............................................................................................................30

3.2.21 Pseudo Code..................................................................................................................................... 30

3.3 SAP Forms........................................................................................................................................ 32

3.3.1 SAP Script/Forms.............................................................................................................................. 32

3.3.2 Execution Mode Details..................................................................................................................... 32

3.3.3 Technical Details............................................................................................................................... 33



3.4 SAP Interface.................................................................................................................................... 39

3.4.1 Interface Classification....................................................................................................................... 39

3.4.2 Interface Functionalities.....................................................................................................................39

3.4.3 Interface Data Requirements.............................................................................................................40


3.4.5 Selection Criteria............................................................................................................................... 43

3.4.6 SAP Requirements............................................................................................................................ 44

3.4.7 Middleware Solution.......................................................................................................................... 45

3.4.8 Legacy System Requirements...........................................................................................................45

3.4.9 Data Conversion & Interface Definition..............................................................................................47



3.4.10 Data Mapping Matrix.......................................................................................................................... 47

3.4.11 File Layout......................................................................................................................................... 49

3.4.12 Dependency...................................................................................................................................... 49

3.4.13 Relevant Function Modules...............................................................................................................49

3.4.14 Pseudo Code..................................................................................................................................... 49

3.4.15 ALE Configuration (optional)..............................................................................................................50

3.4.16 Custom Data Dictionary Objects (Optional).......................................................................................51

3.4.17 Performance Consideration (Optional)..............................................................................................51

3.4.18 Interface Controls.............................................................................................................................. 52

3.4.19 Compliance........................................................................................................................................ 54

3.4.20 Miscellaneous Data Capture (Optional).............................................................................................55

3.5 SAP ECC Report............................................................................................................................... 56

3.5.1 Technical Solution............................................................................................................................. 56

3.5.2 Selection Screen............................................................................................................................... 56

3.5.3 Starting Condition.............................................................................................................................. 58

3.5.4 Data Mapping Tables......................................................................................................................... 59

3.5.5 Detail Logic Diagrams........................................................................................................................ 60

3.5.6 Interactive Report Flow...................................................................................................................... 65

3.5.7 Sort Criteria Details............................................................................................................................ 65

3.5.8 Calculations and Page Break related information..............................................................................66


3.5.10 Recovery and Restart........................................................................................................................ 67

3.5.11 Language of texts.............................................................................................................................. 67

3.5.12 Currency and Units of Measure.........................................................................................................67

3.6 SAP BW Report................................................................................................................................. 68

3.6.1 Report Description:............................................................................................................................ 68

3.6.2 Report Layout.................................................................................................................................... 68

3.6.3 Report Selections and Navigation.....................................................................................................68

3.7 SAP Workflow.................................................................................................................................... 70

3.7.1 SAP Workflow Diagram..................................................................................................................... 70

3.7.2 Technical description......................................................................................................................... 71

3.7.3 Business Object Information..............................................................................................................72

3.7.4 Workflow Definition............................................................................................................................ 73



3.7.5 Deadline Monitoring Requirements....................................................................................................74

3.7.6 Reporting / Form Requirements........................................................................................................74

3.7.7 Custom screen design....................................................................................................................... 74


3.7.9 User Exit / Enhancement Detailed Description..................................................................................75

3.7.10 Configuration Information.................................................................................................................. 75

3.8 SAS Developments............................................................................................................................ 75

4. Security and Authorization Requirements..........................................................................................76

5. Attachments....................................................................................................................................... 77



1 General Information

This document has been created within the framework of the GRP@AGA project. According to the Global Reporting Program (GRP) running since 2002, several GRP rollout projects have been performed by different operational units (OE) in the past in order to enhance the reporting speed, quality and efficiency. Currently the to-be solution is represented by the GRP kernel solution in order to meet those targets.

The core aim of the GRP@AGA project is to deliver homogeneous system platform (SAP ERP) for all insurance and non-insurance related finance departments at OEs belonging to AGA INTERNATIONAL S.A. (AGA Group). This will align AGA Group with the rest of the Allianz business globally through the implementation of a global template (GRP kernel solution). Realisation of the project will be conducted in several steps. The GoLive of the pilot project – rollout on Mondial Assistance France (MAF) – is planned for the 2012-01-01. It will be followed by rollins on the different OEs, which will have to adhere in general to already accepted GRP solution for MAF based on the GRP kernel solution.

In order to meet the business requirements of asset accounting there is a need to migrate the asset master data records from the feeder systems (e.g. SERVANTISSIMO Document Change History) to SAP CAP.

1.1 Document Change History

Date Changed by Chapters changed Reason for update

08.07.2011 Yagna Reddy All Creation of file

18.07.2011 Michel Schneider

1 and 2 Feedback of internal review

1.2 Purpose of this document

This document describes from a business perspective the purpose of the required migration. It should also provide the developer with a logical overview of what data has to be migrated using BDC/LSMW. Moreover, the document is used to provide him with all relevant details on functional requirements (function and features), information on GAPs, and the technical description for a development in SAP or SAS needed.

The migration focus is on asset master data. There are two different ways of migrating data from feeder systems.

This document will discuss loading fixed assets using two methods.



1. BDC recording

This is suitable for a very basic upload. If for example you are not creating fixed assets in SAP, but rather updating one field in fixed assets which already exist in the system then this might be the right approach. But it is not flexible enough to be used for the creation of fixed asset data.

2. For a one-time conversion into SAP, we use LSMW tool. It allows you to leverage the full power of ABAP while using standard SAP processing functions, yet it does a lot of the file management and processing work automatically.

A new LSMW for AGA on client 780 will have to be written for the data migration.

Difference between LSMW and BDC are

1. LSMW is used for SAP standard applications whereas BDC is for customized applications.2. Standard Mapping is done in LSMW and data validation is done implicitly by SAP whereas in BDC we have to do it explicitly.3. For any data complexity, LSMW doesn't supports whereas in BDC, we can do it manually.4. LSMW internally might well in using IDOCs, Batch Input, Direct input, Recording.

1.3 Business Needs and Requirements

A fixed asset is an object, a right, or another item owned by an enterprise that is intended for long-term use and can be individually identified in the balance sheet. Maintaining fixed assets involves creating, changing, and displaying asset master records. Please refer to IP 320336_IP_FC_WS1_Customizing_ FIAA_Fully_New for further information on the customizing of FI-AA for AGA.

The different items of information are structured according to area of use and functions in the system to make it easier for users to create, maintain, and evaluate master data. Each asset master record consists of two parts that are described below.

1. General Master Data / Organizational Assignments

This part of the master record contains general information about the fixed asset.

2. Valuation ParametersIn the valuation section of an asset master record is defined, how a fixed asset is valuated for each depreciation area. Example: In the valuation section for a machine, it was specified to be written off in depreciation area 20 (cost-accounting depreciation) within a period of three years. The machine is to be written off using straight-line depreciation.



1.4 Open Issues

1. Asset Master data of Allianz Global Assistance has to be provided.

2. Identifying the tool (whether LSMW or BDS) to migrate the legacy data



2 Functional Description

2.1 Solution Overview

The functionality of the migration is aimed at the synchronisation of the feeder systems (e.g. SERVANTISSIMO) with the respective master data on SAP FI module using data migration. So it will be uploaded into SAP through flat file.

Data migration is slightly different from a normal transaction which happens in Asset accounting module. Normally, in asset accounting the day to day transactions is posted withvalues through FI bookings and at the same time the asset reconciliation is updated online realtime. Whereas in data migration the asset master is updated with values through a transaction code called as AS91. The reconciliation GL account is not automatically updated at this point of time.

The reconciliation accounts are updated manually through another transaction code called OASV.

Creating a Legacy Asset needs following information to be uploaded:

1) Asset Class: Each asset master record must be assigned to one asset class. Asset Class can be determined based on legal or management requirements. Normally, depreciation area and other master data are associated with the Asset Class.

2) Company Code: One Fixed Asset is assigned to one company code.

3) Description: Description of the Fixed Asset

4) Manage Historically: If it is legacy Asset and using transaction AS91, then this check box has to be checked.

5) Capitalization Date: The capitalization date is the value date of an asset. You can also enter this date manually when creating an asset. However, this does not lead to the asset being capitalized, but only to this date being the default for the asset value date when the first acquisition is posted.

6) Cost Center: The SAP system uses the cost center assignment in the asset master record to determine the cost center affected when fixed asset depreciation or Gain/loss from asset sales type of postings are done.

7) Old Fixed Asset Number: You can enter Legacy Asset number in this field to keep a track of the old numbers.

8) Depreciation area: An area showing the valuation of a fixed asset for a particular purpose (for example, for individual financial statements, balance sheets for tax purposes, or management accounting values).



9) Depreciation Key: The depreciation key (valuation key) controls the valuation of the asset in the particular depreciation areas.

10) Take Over values: These are filled depending on the Customization and Depreciation areas.

2.2 Legacy Asset Data Transfer

2.2.1 Set Company Code Status

Test status - We can change values by transferring asset data from a previoussystem, or by posting.

Transfer status - We can enter and change values by transferring asset dataFrom a previous system, but posting is not possible.

Production status - The asset data transfer is complete. You can only changevalues by posting. Before the system goes live, it is essential that you set thesystem status to "production" (not test).

Categories of Status

0 Asset data transfer completed1 Asset data transfer not yet completed2 Test company code with data transfer always allowed3 Company code deactivated - reporting allowed

Company code status is set to Test i.e 2 till asset master data is transferred using Transaction Code AS91and balances are updated in transaction code OASV.After completion of migration company code status must be changed to ‘0’ to avoid inconsistencies in depreciation calculations.Which status will we use when?

2.2.2 Specify Sequence of depreciation areas

In this field we define the order in which you want to update depreciation areas with values during legacy data transfer. You determine this sequence by entering a relative number in this field.

During the transfer of legacy data, the first depreciation area to be transferred is generally the book depreciation area.

In this step, the sequence of the depreciation areas for the data takeover transaction is specified. If there are additional depreciation areas for local /fiscal purposes, the sequence for the depreciation areas may be impacted.



2.2.3 Specify Transfer Date / Last Closed Fiscal Year

Here we specify the transfer date for the Allianz Global Assistance asset data transfer. This date determines the status of posting to be used for the transfer. Posting up to this date will be included in the transfer. This specification also determines whether we want to perform the transfer during the fiscal year (with transfer of posted transactions/depreciation in the current fiscal year) or at the end of the fiscal year (without transactions).

If the transfer date is not the last day of the fiscal year (according to the fiscal year variant in FI), the system interprets this as transfer during the fiscal year. The system cannot transfer any historical transactions. It can only transfer cumulative values from the end of the last fiscal year, and the transactions in the current fiscal year (the second is only possible for transfer during the fiscal year).

Example: Transfer date is last day of the fiscal year

Transfer date – December 31, 2011 Last closed fiscal year 2011 Specify the take over date as 31.12. 2011. The company is going live with SAP on

01.01.2012 To make it simple, the legacy data will be transferred on 31.12.2011. -> Does that

mean it will be technically migrated into SAP CAP only on the 31st December? System will start calculating depreciation from 01.01.2012

2.2.4 Specify Last Period Posted in Previous System (Transf. During FY)

This step is only necessary if you want to perform an old assets data takeover during the fiscal year. In this case, you must specify the period up to which depreciation was posted in the previous system. This period refers to the posted depreciation that is to be transferred during old assets data takeover.

Allianz Global Assistance is going live on 1st January, 2012. In this case we specify that depreciation was posted up to 31st December 2011 in the previous (legacy) system.

2.2.5Transfer Foreign Currency Values

This is important to that carry out this step if you manage depreciation areas in foreignCurrencies.

In this step, determine that foreign currency areas can receive values during old assets data takeover. Then the depreciation areas are not supplied with values from another area by the system, although they are defined as dependent areas by the Customizing settings. This specification can only be made for areas that are managed in foreign currency.

Using this indicator, you specify that you will provide values for the foreign currency area during the legacy data transfer. The system then does not provide values itself for the area (by taking over values from another area, with no changes allowed) as it normally would.

We can only make an entry in this field for an area which is managed in foreign currency.



For any Depreciation area with foreign currency values fixed at the Group Rate as at the takeover date, the takeover values for this depreciation area is calculated manually/automation tool.

Please note that if any change to depreciation area sequence is undertaken, that the manually input flag will change position and will require updating.

Do we need to transfer assets in foreign currencies?

2.2.6 Recalculate Depreciation for Previous Years

If you need system to recalculate depreciation for the previous year up to the date of the transfer there is an option available to calculate depreciation.

Normally this step is not done, since the depreciation calculation by SAP might differ due to some rounding difference, timing difference as compared to the legacy system.

Is that really clear already? Up to now I thought we would load the assets data into SAP CAP at their original value and then depreciate them in SAP using the depreciation run. What are the consequences of using one or the other way?

2.2.7 Set Reconciliation Accounts (Manually)

This step is required for conversion purposes. Carried out directly in client during cutover. By default the relevant GL accounts will have been created as reconciliation accounts. As part of the conversion, the flag is removed from the GL accounts per asset class per company code. After the balances have been loaded, the reconciliation flag is reset. OAMK allows this to be carried out manually. Once they are set as reconciliation accounts, the system will only post to them via Asset Accounting from this point onwards. This ismaintainable in each client except production where this step is managed by the cutover strategy.



2.3 Impacted business process

TEXT TO BE REMOVED. GUIDANCE ONLY:

< Please provide the high level description of the impacted business process > END OF GUIDANCE TEXT

Text

2.4 Impacted sub-process


< Provide the high level description of the impacted sub - business process at transaction level. > END OF GUIDANCE TEXT

Impacted Sub-process 1

Text

Impacted Sub-process 2

Text

2.5 Data Requirements

Require flat file for migrating the data from legacy system to SAP.

The format of this file needs to be described.



3.Technical Description – Development Types

TEXT TO BE REMOVED. GUIDANCE ONLY< This chapter is used to describe all relevant technical details for SAS or SAP developments implemented.Fill in all sub chapters of the relevant development type, besides the chapters marked as optional.In some chapters are provided examples and guidance on what content is expected.> END OF GUIDANCE TEXT

In the following chapters are described the following (mark the line in the middle with an “x”) – the text in the 3rd column is a link to the chapter within the document

SAP Enhancement 3.1 SAP EnhancementSAP Conversion 3.2 SAP ConversionSAP Forms 3.3 SAP FormsSAP Interface 3.4 SAP Interface SAP ECC Reports 3.5 3.5SAP ECC ReportSAP BW Reports 3.6 SAP BW ReportSAP Workflow 3.7 SAP Workflow SAS Developments 3.8 SAS Developments



3.1 SAP Enhancement

3.1.1 Table Access Diagram

3.1.2 Custom Tables / Structure in SAP


< This section should detail the attributes of any custom table used, and the properties of its fields.

NB: Existing SAP Data Elements and/or Domains should be used whenever possible when creating custom table fields, in order to avoid unnecessary typos. In this instance, the data table row for that field should not be completed beyond ‘Domain’, as the remaining attributes will be default values for the selected Domain.

>END OF GUIDANCE TEXT

Table Name

Short text

Size category

Table maintenance


DE117727, 04/05/11,

Please provide your table access Diagram


allowed

Data class

Buffering

Table maintenance generation

Authorization Group

Field Name

Data Element

Domain Type Length Check Table-Field

Key Field

Foreign Key

Description

Comments

3.1.3 Data Validation

TEXT TO BE REMOVED. GUIDANCE ONLY < Provide the data validation rules> END OF GUIDANCE TEXT

Table Field Name Validation Rule

3.1.4 Data Flow Diagram



3.1.5 Pseudo Code

TEXT TO BE REMOVED GUIDANCE ONLY <

Pseudo-code should describe the main steps that will be performed in a program with easy to follow logic and select statements.

Logic should be detailed enough so that any developer can be able to code the object without significant effort on logic redesign.

Data declarations should not be included in pseudo-code, unless the data declaration will impact the logic.

Format the pseudo-code into logical processing units.

Begin each section of pseudo-code with a heading that clearly describes the logic to follow. (i.e. Validate user input, gather the inventories)

Each main step needs to start with description of the process, in functional language.

All major checking should be specified, such as whether the internal table is empty, or if SY-SUBRC is equal to zero.

> END OF GUIDANCE TEXT

3.1.6 Technical details

TEXT TO BE REMOVED GUIDANCE ONLY <



All chapters are optional, only those ones which are needed needs to be filled in. For all chapters below also separate Excel sheets can be attached per chapter


3.1.6.1 SAP User-Exits

Enhancement Main Program Includes Form Routines

3.1.6.2 Function Exits

Project Enhancement ComponentMain Program Logical trigger

Point

Function Module Name

Includes

3.1.6.3 Field Exits

EnhancementMain

Program Name

Function Module Name

Field Exit IdScreen Number

Screen Field Name

Conditions for execution

3.1.6.4 Menu Exits

Enhancement Menu/Path Function/Transaction Code

3.1.6.5 Screen Exits

Enhancement Main Program NameScreen Number

Program Name & Sub-Screen Number

3.1.6.6 Search Help Exits

Field Name

Field Description Import / Export

Key Field

Data Type (CHAR,

Length Default



(I/E) (Y/N) Element NUMC) Value

3.1.6.7 Search Help Assignment

Standard Search Help Collective Search Help Elementary Search Help

3.1.6.8 BADI

BADI Definition Implementation name Methods Comments

3.1.6.9 Custom Transaction

TEXT TO BE REMOVED. GUIDANCE ONLY < Functional details of custom transaction can be incorporated here: Number of screens required and flow diagram can be included and provide the selection screen screen shot along with the table name and field name and screen shot for the required output.> END OF GUIDANCE TEXT

3.1.6.10 Requirement routine

Menu/Submenu

Routine number

Business logic required

3.1.6.11 Business Transaction event

TEXT TO BE REMOVED. GUIDANCE ONLY < Provide the details of the Business transaction Event if some specific config required that can be mentioned here > END OF GUIDANCE TEXT

3.1.6.12 Substitution

TEXT TO BE REMOVED. GUIDANCE ONLY <For FI related transaction specifically




Validation Description

Fields required for validation

Point of Validation

Table used in validation

Business Rules

Substituted Field

Derived from Field Table used in Substitution Business Rules

3.1.6.13 Screen Details

Screen Number:

Screen Layout: (type or attach details of screen layout)

Screen Field Mapping:

Field #*

Field Descrip

tion

Field

Type

SAP Refere

nce Field

Screen Fiel

d Length

Input/ Output Fiel

d

Mandatory/ Optio

nal

Default

values

Get Value (G)

Set Value (S)

Or Both (B))

Match codes used

(if any)

Other field formatting

requirements **

* Number the fields sequentially for referencing.** Other formatting requirements – left or right justification, padding requirements, invisible / visible, bright,

etc.

Necessary field validations and sorting logic, (if any)

Processing Functionality



Pre-screen display processing:

Screen Processing Pseudo code:

Screen Flow Diagram


DE117727, 04/05/11,

Please provide your screen flow diagram


3.2 SAP Conversion

3.2.1 Data Cleaning Requirements

TEXT TO BE REMOVED. GUIDANCE ONLY

< Specify how data cleansing will be handled. Identify the key contacts responsible for this process.


3.2.2 Extract Logic


< Describe the extract logic: filtering (e.g. active vendors only, last two fiscal years), summarizing (e.g. monthly balances, size of the documents)


3.2.3 Currency and Units of Measure


< Are all the units of measure and currency details in the data mapping tables correct? Will the report work for different currencies? What about the EURO? What happens to the report if the common measure of weight used on client’s sites is changed to tones instead of kilograms? Or to stones and pounds?


3.2.4 Language of Texts


< The texts of the report may be different in different countries. What language should be used to derive these texts? The login language or another?




3.2.5 File Layout (In Sequence)

3.2.6 Selection Screen Details (if applicable)


< Detail exactly what is needed at the selection screen by using this table. The programmer will be able to construct the screen directly from the details in this table. Some SAP technical knowledge will be needed for the complete production of this table.


Name Table-Field / Check Box /

Radio Button – with group

Parameter (P) / Select-option (S)

Comments (Range, Single/Multiple

selection, Patterns, Mandatory etc.)

Default Value

Desired screen design (selection possibilities):

(use attachment if possible):

3.2.7 Starting Condition (Optional)


< When should the conversion be run? Does another conversion need to be run before this one is triggered? Should it be a batch only program (with added security) or is it needed on-line as well? Will the program automatically start a batch session or should someone be in place to trigger these?


3.2.8 Business Rules (Optional)


< Provide any business rules that are applicable for the transformation. You can also add a separate spreadsheet






<Table Access Diagram with primary key relationships between tables. Not necessary if calling transaction(s) to update SAP tables

(Table access diagram to be attached)

Insert Image Here - To insert TAD (or other OLE object):1. Open your previously created Excel TAD spreadsheet from disk and select the area covered

by the TAD.2. Press Ctrl-C to copy TAD to clipboard.3. Without closing Excel, switch back to this word document and position cursor where you'd like

to insert the TAD.4. From the menu, select TDS Insert TAD (do not use standard paste)5. Resize the diagram.6. Delete these instructions, example, and extra lines in this section to avoid printing an extra

page.7. You're done!

Note: If you create your TAD in an embedded excel spreadsheet and then copy and paste from the embedded object and not from an excel spreadsheet on disk, Word may insert the spreadsheet as a protected object. You will not be able to edit or delete it. You should create your TAD excel files on disk and not as embedded icon files.

To insert graphics within the document (non-OLE objects):1. Copy the bitmap image to the clipboard 2. From the menu, select TDS Insert Graphic (do not use standard paste)3. Resize the image.4. Delete these instructions and extra lines in the section.5. You're done!> END OF GUIDANCE TEXT

3.2.10 Selection Criteria

Name Table Field/ Check box/ Radio button

Select-option (S) or Parameter (P)

Comments (Range, Single/Multiple Selection, Patterns, Mandatory, etc.)

Default Value

S or P

Variants:

Attach selection screen shot here

3.2.11 Data Conversion & Interface Definition

TEXT TO BE REMOVED GUIDANCE ONLY



< For inbound interfaces, indicate any relevant transaction codes and a description of the dynamic transaction call (i.e. for materials, if the material exists, MM02 is called, whereas for materials not already established in SAP, MM01 is called).> END OF GUIDANCE TEXT

File

Name

Inbound /

Outbound

I/O

File Type

(ASCII,

EBCDIC, Excel

file, etc.)

Location Description Logical

File

Name

File

Delimiter

Comments

Source System:

Target System:

System Diagram:

3.2.12 Data Mapping Matrix

3.2.13 BDC Method

Batch Data Communication or BDC is a batch interfacing technique that SAP developed. It is a common data transportation method and is especially useful in large data communication scenario. There are two methods to run BDC program. One is using statement ‘Call Transaction’ directly. In this method, the screen is simulated directly but difficult for error processing. The other method is to create a BDC session. Actual data transportation is executed when running this BDC session.

The migration consists of seven steps in BDC

1. Creation of flat file

2. Mapping fields of the flat file to SAP asset master record fields

3. Call the transaction of Asset master AS91

4. Trap all the errors in the program

5. Rectify the errors if found and same process will follow.



3.2.13.1 For BDC/Call Transaction

This file is not filled.

3.2.14 LSMW

The migration of data using LSMW consists of following steps

SAP provides Standard LSMW to upload legacy Fixed Assets as a whole or its parts (Sub - Numbers). This program copies the Asset master data and asset transaction in FI Asset Accounting systems.

The steps

1) Maintain Object attributes

Object - 0160

Method - 0001 (Batch Input)

2) Create a flat structure for input data in step 2.

3) Maintain fields in step 3 for the input structure.

Most of the fields are available in header structure provided by SAP.

While running the transaction online, SAP automatically fills the Depreciation areas based on the Asset Class. But with this program, Depreciation Area and Depreciation Keys MUST be provided.

In addition to this, if you want to change the Useful life in Years/Periods, please include them in the source fields as well.

The field for Depreciation Key is AFASLXX. 'XX' depends on how many depreciation areas. For e.g. AFASL01 for Book Depreciation, AFASL02 for Group Depreciation etc. Similarly, field for Depreciation Area is AFABEXX.Take Over values are also present in the header structure and should be mapped with Depreciation areas.

E.g. of source structure is as shown below:



4) Maintain structure relations: Since we have a flat structure, relate only header level to input structure.

5) Maintain Field mapping and conversion rules: create the source fields for all target fields and give transaction as constant 'AS01'.

6) Specify Files: provide the path of the file in this step.

7) Assign files to the target structure

8) Read file

9) Convert File

10) Create Batch Input session: Normally, this step creates a batch input session which can run using SM35. But, this is the case with this LSMW program.



3.2.15 ALE Configuration (optional)

TEXT TO BE REMOVED GUIDANCE ONLY< The following tables should be used to document all ALE/EDI configurations. If Configuration exists in more than one SAP system, then the information in the following section should be repeated in multiple tables.


3.2.15.1 For ALE/IDOC/BAPI/Direct Input

Source System & Client or Logical System name

Partner ProfileTarget System & Client or Logical System NameMessage TypeBasic IDoc TypeIDoc ExtensionBusiness Object / MethodsProcess Code / Function Module

1. IDoc Type Structure

TEXT TO BE REMOVED GUIDANCE ONLY



< This table documents the exact IDoc type structure of a customized IDoc


SAP IDoc Type:IDoc Extension:Parent Segment:

New Child Segment:

IDoc Field

Field Name

Data Element/Type

Format/Length Comments

2. Assignment of FM to Logical message and IDoc type

Function Module FctTyp BasicTyp Log message type

Obj type Directn Extension MsgCode MsgFunct

3. Characteristics of inbound function modules

Function Module Input type Dialog allowed

4. Inbound process codes

Process Code Process Code description

5. Link type and serialisation type of message type

Message type Serialisation object type Object type link

6. Workflow event linkages to be activated

Object type Event Receiver type



3.2.16 Custom Dictionary Objects (optional)

TEXT TO BE REMOVED GUIDANCE ONL< Use an appropriate attachment. Table-View Structure and Search Help to be attached> END OF GUIDANCE TEXT

3.2.17 File Layout

Input / Output File NameRef. Field Name Field

TypeStarting Position / Delimiter

Length Decimal Format Mandatory (M) / Optional (O)

1.

2.

3.

Volume of data:

3.2.18 Performance Considerations (optional)

TEXT TO BE REMOVED. GUIDANCE ONLY <Performance considerations (if any), else write N/A>END OF GUIDANCE TEXT

3.2.19 Dependency

TEXT TO BE REMOVED. GUIDANCE ONLY <Dependency on other programs / external applications (if any)>END OF GUIDANCE TEXT

3.2.20 Relevant Function Modules

TEXT TO BE REMOVED. GUIDANCE ONLY <List the function modules used in the program>END OF GUIDANCE TEXT

3.2.21 Pseudo Code

TEXT TO BE REMOVED GUIDANCE ONLY<









All major checking should be specified such as whether the internal table is empty, or if SY-SUBRC is equal to zero.

All parameters of a function call should be specified




3.3 SAP Forms

3.3.1 SAP Script/Forms

Customizing requirements for the form have to be added to the customizing chapter of this template.

3.3.1.1 Printing Existing Solution

Menu Path for transaction:Values to be used and output type:Actions to be taken:

3.3.1.2 Desired functionality

Output type(s):

Form Types:

Transmission medium:Legal requirements:Type of printer:Paper Size:Orientation: Portrait/Landscape:Special stationary to be used:

3.3.2 Execution Mode Details

TEXT TO BE REMOVED GUIDANCE ONLY< Specify the execution mode details whether the execution mode is transactional or stand alone mode > END OF GUIDANCE TEXT

Transactional:

Output Determination:

Output Type Print Program Layout Set

Navigation Path:



Batch Job Name:

Stand Alone:

Select-Options:




Default Value

S or P

Selection Screen Layout: (insert attachment if applicable):

3.3.3 Technical Details

TEXT TO BE REMOVED. GUIDANCE ONLY< Mention the technical details of the development. Fill the appropriate section> END OF GUIDANCE TEXT

3.3.3.1 Flow Diagrams

TEXT TO BE REMOVED GUIDANCE ONLY< Logical flow of the execution of the form > END OF GUIDANCE TEXT

3.3.3.2 Pseudo Code

TEXT TO BE REMOVED GUIDANCE ONLY< Pseudo-code should describe the main steps that will be performed in a program with easy to follow logic and select statements.






All major checking should be specified, such as whether the internal table is empty, or if SY-SUBRC is equal to zero.




3.3.3.3 Form Layout

TEXT TO BE REMOVED. GUIDANCE ONLY < Attachment giving the look of the layout of the form to be developed> END OF GUIDANCE TEXT

3.3.3.4 Print Program

TEXT TO BE REMOVED. GUIDANCE ONLY < Details of custom print program can be incorporated here. If it is a SAP print program add the information what the print program does > END OF GUIDANCE TEXT

3.3.3.5 SAP script

TEXT TO BE REMOVED. GUIDANCE ONLY < Details of SAP script can be incorporated here. > END OF GUIDANCE TEXT

3.3.3.6 Smart form

TEXT TO BE REMOVED. GUIDANCE ONLY < Details of Smart form can be incorporated here.> END OF GUIDANCE TEXT

3.3.3.7 Windows

TEXT TO BE REMOVED. GUIDANCE ONLY <Details of the windows used in the layout > END OF GUIDANCE TEXT

Reference Print on page Label PositionW1 All Pages X

Y ......WN

3.3.3.8 Standards Texts / Text Modules

Reference Text / Field Name

Print on page

Label Position

Font Output Format

Font Format



If a logo is to be printed, specify the standard text ID in the Standard/Application Text(s) table above.

Logo: Yes/No

Barcodes Yes / NoBarcode Field Name: Verification of Barcode Printing Capability:

3.3.3.9 Field Mapping

Field FieldDescription

Functionality Logic Print on page

Font Font Format

Window

3.3.3.10 Translation

Reference Description of use (in Language1)

Description of use (in Language2)

Description of use (in Language3)

Text module Name

Notes

3.3.3.11 Layout Details

Position of Left Margin (Specify Unit)

Position of Right Margin(Specify Unit)

Position of Logo(Specify Unit)

Logo(Specify Logo)

Position of Main Window(Specify Unit)

3.3.3.12 Styles

TEXT TO BE REMOVED. GUIDANCE ONLY < Provide styles used > END OF GUIDANCE TEXT



3.3.3.13 Paragraph formats

TEXT TO BE REMOVED. GUIDANCE ONLY < Provide Paragraph formats used > END OF GUIDANCE TEXT

Paragraph Format

Description Indents and spacing

Font Tabs Numbering and outline

3.3.3.14 Character formats

TEXT TO BE REMOVED. GUIDANCE ONLY < Provide Character formats used > END OF GUIDANCE TEXT

Character format

Description Standard settings Font





TEXT TO BE REMOVED. GUIDANCE ONLY:< This section should detail the attributes of any custom table used, and the properties of its fields.

NB: Existing SAP Data Elements and/or Domains should be used whenever possible when creating custom table fields, in order to avoid unnecessary typos. In this instance, the data table row for that field should not be completed beyond ‘Domain’, as the remaining attributes will be default values for the selected Domain.

>END OF GUIDANCE TEXT

Table Name

Short text

Size category

Table maintenance allowed

Data class

Buffering



Table maintenance generation

Authorization Group

Field Name

Data Element


Key Field

Foreign Key

Description

Comments



3.4 SAP Interface

3.4.1 Interface Classification


< Enter the requested information and type one “X” in each checkbox group.


Interface Number

<Interface Number>

Interface Name

<Interface Name>

Direction(with respectto SAP R/3)

Inbound Interface data flows inbound to SAP R/3Outbound Interface data flows outbound from SAP R/3Other Specify:

InterfaceType

Batch One-way transfer of “accumulated” data set; Usually done by scheduled file transfer.Near Real-Time One-way message-based transfer of data; Usually triggered by event.Real-Time Immediate transfer of small data set; Usually triggered by event.Excel Upload Manually invoked from SAP session; Local spreadsheet file uploaded from PC.Other Specify:

InterfaceFrequency

Hourly Details:Daily Details:Weekly Details:Monthly Details:Quarterly Details:Yearly Details:On-Demand How often:Other Specify:

Type ofRecords

Sent

Full record load Send all records every time interface is executedDelta full records Only send records where one or more fields have changed since previous executionDelta records Only send fields (and keys) that changed since previous interface executionOther Specify:

Volume(per singleexecution)

Average Volume: <Volume> records per interface executionPeak Volume: <Lower Volume – Upper Volume>

3.4.2 Interface Functionalities



3.4.2.1 Data Filter Rules


< Describe any filtering rules that may apply for this Interface


3.4.2.2 Other Business Rules


< Provide any business rules that are applicable for the transformation between the source and the target. You can also attach a separate spreadsheet.


3.4.2.3 Process Flow / Data Flow


< Capture the interface process flow and/or data flow. Include not only interface steps, but also the steps immediately before and/or after the interface to establish context. Include diagram(s) if it will help the explanation, and clearly indicate scope of the interface within the flow. For the steps that occur within the interface scope indicate who does what, when, how, and all related error conditions.


3.4.3 Interface Data Requirements

3.4.3.1 Source Interface Data Layout


< List the data elements that will be provided by the source system for this interface. Do not make any assumptions about how the data will be accessed, and instead provide all methods that are available to access the data. For example, your data may be available from both a database and a file.


Source data is available as (Type “X” for all that apply):

Database Table Name(s): < Provide Table Name>File Type: <e.g. “Comma Delimited”, “Fixed Position”, “Excel”> XML file Procedure Name: <List function, transaction, or other procedure call that can provide this data set>Other Method:



If indicated “Database” above, provide the table columns necessary for this interface:

Table Column Element Description Data Type Length

If indicated “File” above, provide the fields here (preserve order):

Field # Field Description Data Type Length

If indicated “Procedure” above, provide the fields of the result set here:

Field Name Field Description Data Type Length

If indicated “Other” above, list field detail here:

If you have preferences or concerns on the information in this section, mention them here:

3.4.3.2 Target Interface Data Layout


< List the data elements that are required by the target system for this interface. Do not make any assumptions about how the data will be delivered, and instead provide all methods that are available to accommodate the data. For example, your data may be deliverable as both a file and a transaction call.


Target data can be delivered as (Type “X” for all that apply):

Database Table Name(s): <e.g. “ABC0001”, “VENDOR Number”>File Type:Procedure Name: <List function, transaction, or other procedure call that can provide this data set>Other Method: Development team will decide

If indicated “Database” above, provide the table columns necessary for this interface:

Table Column Element Description Data Type Length

If indicated “File” above, provide the fields here (preserve order):



Field # Field Description Data Type Length

If indicated “Procedure” above, provide the fields of the result set here:

Field Name Field Description Data Type Length

If indicated “Other” above, list field detail here:

If you have preferences or concerns on the information in this section, mention them here:

3.4.3.3 Source / Target Data Mapping


< Complete the list. Other mapping documents can be attached in this section as supporting documentation, but this MUST be populated with all of the data elements used in this interface.


SourceElement

TransformationTarget

ElementComments

3.4.3.4 Sample Data


< Provide two attachments of sample source data with the expected target data after this interface is executed. Supply the sample data in the native format or .csv, and preferably zipped.


3.4.3.5 Data Retention


< In file based interfaces a “backup” copy of interface data can be retained in the middleware for each execution. This can be useful for reconciliation purposes. Indicate the retention period for this interface. If not file based, then the source or target system must fill any data retention requirements.




None Data retention is not necessary for this interface7 days15 days (default)30 daysOther Specify:

3.4.3.6 Special Case: Bi-Directional Real Time Interface


< If you know this interface will be a bi-directional real-time interface (i.e. the “Source” system sends and receives data in the same execution), then a second data mapping is required. If applicable, duplicate the table from section (insert source link) and capture the “return data” mapping rules for the “Source” system.



TEXT TO BE REMOVED. GUIDANCE ONLY<Table Access Diagram with primary key relationships between tables. Not necessary if calling transaction(s) to update SAP tables> END OF GUIDANCE TEXT

3.4.5 Selection Criteria




Default Value

S or P

Variants:

Attach selection screen shot here

3.4.6 SAP Requirements

3.4.6.1 Interface Trigger in SAP and/or Middleware

TEXT TO BE REMOVED. GUIDANCE ONLY: < Describe what initiates the execution of this interface. >




3.4.6.2 SAP Transaction

If the interface uses an SAP transaction to extract or insert data, capture the details here.Custom SAP Transaction (New) Name:Custom SAP Transaction (Existing) Name:Standard SAP Transaction Name:None

3.4.6.3 ALE and IDOC specific information ( if any )

Field/Parameter ValuesSource System & Client or Logical System Name

Target System & Client or Logical System Name

Sender Partner Number

Sender Partner Type

Receiver Partner Number

Receiver Partner Type

Message Type

IDoc Type

Extension Name

Business Object

3.4.6.4 SAP Scheduling / Performance Requirements / Service Level Agreement


< Describe any requirements around the timing of this interface.


3.4.6.5 SAP Special Requirements


< Provide any system requirements that are applicable for SAP. Information like data retrieval logic, detail functionality, data retrieval logic diagram can be mentioned here. > END OF GUIDANCE TEXT



3.4.7 Middleware Solution

3.4.7.1 Solution Description


<This section should contain an outline of the chosen middleware solution and the processes involved.> END OF GUIDANCE TEXT

3.4.7.2 Mapping Rules & Conversion Criteria


< This section should contain a high level outline of the mapping rules and conversion criteria. > END OF GUIDANCE TEXT

3.4.8 Legacy System Requirements

3.4.8.1 Legacy System Details


< Provide the following information on the Legacy System.


Application Name <Application Name>

Name Abbreviation

Primary Contact

LegacyApplicationConversion

Strategy

SAP Values All historical data will be converted to or is already compatible with SAP valuesLegacy Values Application will not be converted and requires ongoing translation to SAP valuesMixture Specify: <e.g. “SAP Cost Centers, Legacy Employee Numbers”>

Other Specify: Conversion of customer number from Legacy to SAP. Business Team will be responsible for one time update. <Project > team is responsible for providing full file of all partner types and the SAP customer with reference to legacy customer number.

LegacyApplication

Decommission

None There are currently no plans to decommission this application<Project> This application will be decommissioned after go-live <Project >: <N>Date This application will be decommissioned in <e.g. Q4 2006, Fall 2007, …>Other Specify:

What system will replace the legacy functionality after it is decommissioned?

Application’sRelationshipTo Interface

Source Interface data originates from this applicationTarget Interface data is delivered to this application from elsewhereBoth Interface data is communicated both to and from this applicationOther Specify:


Development Functional and Technical SpecificationT

est

Server / IP <Provide the server /IP details>

Directory Same as above

Database Same as above

PasswordCapture

Test environment passwords have been emailed to “<mail Id>” mailboxTest environment is N/A Reason:

Pro

d

Server / IP <Provide the server /IP details>

Directory Same as above

Database Same as above

PasswordCapture

Prod environment passwords have been emailed to “<mail Id>” mailboxProd environment is N/A Reason:

3.4.8.2 Interface Trigger on Legacy System


< Describe what initiates the execution of this interface. If time-based, capture the day and time requirements.


3.4.8.3 Legacy Scheduling / Performance Requirements / Service Level Agreement


< Describe any requirements around the timing of this interface.


3.4.8.4 Legacy Special Requirements


< Provide any system requirements that are applicable for the legacy system.


3.4.8.5 Legacy Initial Processing


< Describe any pre-processing the legacy system must perform on interface data before loading.




3.4.9 Data Conversion & Interface Definition

TEXT TO BE REMOVED GUIDANCE ONLY<For inbound interfaces, indicate any relevant transaction codes and a description of the dynamic transaction call (i.e. for materials, if the material exists, MM02 is called, whereas for materials not already established in SAP, MM01 is called).> END OF GUIDANCE TEXT

File

Name

Inbound /

Outbound

I/O

File Type

(ASCII,

EBCDIC,

Excel etc.)

Location Description Logical

File

Name

File

Delimiter

Comment

s

Source System:

Target System:

System Diagram:

3.4.10 Data Mapping Matrix

3.4.10.1 For BDC/Call Transaction

3.4.10.2 For ALE/IDOC/BAPI/Direct Input

3.4.10.3 For LSMW




< This section needs to be filled if the development is of type LSMW. Write the Objects Attributes, Source Structures, Source Fields, Structure Relations here

STEP1: Initial Screen Give the project name/description, subproject/description and object name/description of the LSMW object.

STEP 2: Maintain Object Attributes Give an overview of the object type and import technique set up in order to upload the data.

STEP 3: Maintain Source Structures Give an overview of the source structures defined within LSMW.

STEP 4: Maintain Source Fields Give an overview of the source fields.

STEP 5: Maintain Structure Relations

SAP structures Source structure

STEP 6: Maintain field mappings and conversion rules Describe the conversion rules required.

STEP 7: Specify Files Give a list of the files needed, together with their properties for: file contents, delimiter, file structure, file type and code page.

STEP 8: Assign Files Assign the respective files defined in Step 7 to the source structures

Input files Source structure

STEP 9: Read Data

STEP 10: Display read data

STEP 11: Convert Data

STEP 12: Display converted data etc.> END OF GUIDANCE TEXT



3.4.11 File Layout

Input / Output File NameRef. Field Name Field

TypeStarting Position / Delimiter

Length Decimal Format Mandatory (M) / Optional (O)

1.

2.

3.

Volume of data:

3.4.12 Dependency

TEXT TO BE REMOVED. GUIDANCE ONLY <Dependency on other programs / external applications (if any)> END OF GUIDANCE TEXT

3.4.13 Relevant Function Modules

TEXT TO BE REMOVED. GUIDANCE ONLY <List the function modules used in the program> END OF GUIDANCE TEXT

3.4.14 Pseudo Code

TEXT TO BE REMOVED GUIDANCE ONLY<







All major checking should be specified such as whether the internal table is empty, or if SY-SUBRC is equal to zero.



All parameters of a function call should be specified


3.4.15 ALE Configuration (optional)

TEXT TO BE REMOVED GUIDANCE ONLY< The following tables should be used to document all ALE/EDI configurations. If Configuration exists in more than one SAP system, then the information in the following section should be repeated in multiple tables.


Source System & Client or Logical System name

Partner ProfileTarget System & Client or Logical System NameMessage TypeBasic IDoc TypeIDoc ExtensionBusiness Object / MethodsProcess Code / Function Module

1. IDoc Type Structure

TEXT TO BE REMOVED GUIDANCE ONLY< This table documents the exact IDoc type structure of a Customized IDoc


SAP IDoc Type:

IDoc Extension:

Parent Segment:

New Child Segment:

IDoc Field

Field Name

Data Element/Type

Format/Length Comments

2. Assignment of FM to Logical message and IDoc type

Function Module FctTyp BasicTyp Log message type

Obj type Directn Extension MsgCode MsgFunct



3. Characteristics of inbound function modules

Function Module Input type Dialog allowed

4. Inbound process codes

Process Code Process Code description

5. Link type and serialization type of message type

Message type Serialisation object type Object type link

6. Workflow event linkages to be activated

Object type Event Receiver type

3.4.16 Custom Data Dictionary Objects (Optional)

TEXT TO BE REMOVED GUIDANCE ONLY< Use an appropriate attachment > END OF GUIDANCE TEXT

3.4.17 Performance Consideration (Optional)

TEXT TO BE REMOVED. GUIDANCE ONLY <Performance considerations (if any), else write N/A> END OF GUIDANCE TEXT



3.4.18 Interface Controls

3.4.18.1 Completeness Control


< Interface functionality includes automated processes or manually captured results that will occur for each execution that verify all the data transmitted by the source system has been uploaded to the receiving system. Example controls:

How will the receiving system ensure that they have received all the data intended for their application?

Is a trailer record expected? If yes, what values are expected in the trailer record? Are interface hash totals expected? How will completeness be verified and validated?


Control Control Addressed

3.4.18.2 Accuracy Control


< Interface functionality includes automated processes or manually captured results that will occur for each execution that verify the data uploaded to the receiving system is the same data that was transmitted by the source system. Example controls:

How will the receiving system ensure they have the complete data values? How will the receiving system ensure that source records were accurately converted or

transformed?



3.4.18.3 Duplicate Records Control


< Interface functionality includes processes to handle duplicate records.

If the receiving system cannot “handle” duplicate records, this interface includes a process to insure that duplicate records are not transmitted to the receiving system.



If the receiving system can “handle” duplicate records, the logic exists to process duplicate records appropriately (i.e. Initiating an update, discard process etc.

Are corresponding key values available in the source system and the receiving system to insure that duplicates do not occur?

Does the receiving system have logic in place to avoid duplicate records from being processed? If no, are duplicate records possible from the sending system? If yes, does this interface require the logic to process duplicate records according to receiving system business rules?



3.4.18.4 Error Detection and Communication Control

3.4.18.5 Integrity of Data Transformation Control


< Automated processes or manual result procedures that will execute for each interface execution will be used to verify that the data that is summarized, translated, reformatted, or converted remains accurate and complete during processing. Example controls:

What source values are transformed by Middleware? How will the validation between the source and receiving system values occur to insure

success? Are cross reference tables used in this interface? How will this transformation be validated?



3.4.18.6 Standard File Format Control


< Automated processes or manual result procedures that will be executed for each interface execution to verify that the data being transmitted by the source system and uploaded to the receiving system is accomplished by using a defined file layout that is not intended to be changed each time the interface is run. Example controls:

What is the format of the data that is sent from the sending system to the receiving system? How is this format insured?





3.4.18.7 Interface Data Security


< Automated processes or manual result procedures that will be executed for each interface execution to verify that the path used to transmit data from the source system to the receiving system either cannot be accessed other than by certain electronic means (i.e. programs, transactions, etc.) or that access path is limited to a few appropriate people. Example controls:

What controls the data security? How is the security defined? What enforces this security? > END OF GUIDANCE TEXT


3.4.19 Compliance

3.4.19.1 Compliance Team Classification


< Indicate which Compliance Team member has determined the relevance of this interface. > END OF GUIDANCE TEXT

Determined by:Not yet determined

3.4.19.2 Relevant Regulations


< Indicate any regulations that govern the design and execution of this interface.


SOX Why?:HIPAA Why?:



Other Specify:

3.4.19.3 Other Regulatory Requirements


< Describe any additional regulatory requirements (e.g. non-HIPAA, non-SOX). Also include original text from requirement. This ensures that everyone will read the same version of the requirement, even if the official requirement changes over time. > END OF GUIDANCE TEXT

3.4.20 Miscellaneous Data Capture (Optional)

3.4.20.1 Interface referring Report Definition Document(s)


< List the report specification numbers that define the “non-interactive” reports used for monitoring, reconciliation, or logging purposes. Reports necessary to support this interface for monitoring, reconciliation, or logging will require a report specification to be populated. NOTE: The same report can satisfy the requirements for more than one interface specification.


Report Specification Number Description

3.4.20.2 Other Pertinent Details


< If you feel that there is something that needs to be communicated or documented that you are unable to find the proper location in the above template, document it here.


Item Description Reported By Date



3.5 SAP ECC Report

3.5.1 Technical Solution


< This section highlights the key design issues. A series of bullet points summarizes the logic chosen for the program and the main technical difficulties.

For Example:

What assumptions are made in the technical specification and what they entail in technical terms.

Key process steps.

Why a particular function module was chosen.

Why use multiple selects than just one.

Why use a particular kind of logic for the main processing.

What were the major technical problems with the design of the program.

Etc.


3.5.2 Selection Screen

3.5.2.1 Extract Data Relationship Diagram




< The purpose of the diagram is to show the database tables that contain the relevant data for the report and the relationships between them. Drawing the diagram removes out many of the main design issues of the program at both the business and the technical levels.

Diagram Guidelines

The diagram should show all the SAP tables that the program will extract data from.

The relationships between tables should also be illustrated in the form of crows feet (one to one, one to many etc.) This is useful as it will show the developer whether they are expected to have multiple or single records for a chosen related record.

Database tables – using keys F1 and F9.) Note when structures are included in the diagram, the notes section will become much more complicated.


3.5.2.2 Selection Prototype


< A screen dump of a prototype of the selection screen should be included, showing the way the fields are ordered, frames, titles, etc. This will allow QA review at an early stage.


For Example:



3.5.2.3 Details


< In this section, all the error messages (ID and Classes) prompted by the validations executed at the selection screen will be detailed

For Example:

If an invalid Company Code is entered on the selection screen the message E001(ZF) ‘Company Code & is not valid’ should appear and the field is left open for input.

Etc.


3.5.3 Starting Condition


< When should the report be run? Does an interface need to be run before the report is valid, and (more commonly), should it be a batch only program (with added security) or is it needed on-line as well?

Eg ‘This program will be run after month-end billing.’Eg ‘This program will be run each time a sales order is saved> END OF GUIDANCE TEXT



3.5.4 Data Mapping Tables


< List of all the fields along with their details are to be mentioned here. Look and feel wise, a desired report design can also be specified here.> END OF GUIDANCE TEXT

Field Name Field Desc Output Length

Output Type

Format

Position

SAP screen No./ field name

3.5.4.1 Desired Report Design/Layout

Use screen shot if possible

3.5.4.2 Report Example

Use screen shot if possible



3.5.5 Detail Logic Diagrams


< The diagrams, along with the notes associated to them should be the main structure of the program. They should include critical decision logic, the database selects, complex conversions, calculations, and formatting and output.

High Level Overview



<Program name>

SELECTI0ONSCREEN

PROCESSING

MAINPROCESSING

FINALPROCESSING

1 2 3


3.5.5.1 Selection Screen


< The diagram should show the processing triggered by the selection screen.

Example:


3.5.5.2 Main Processing

TEXT TO BE REMOVED. GUIDANCE ONLY: <

Detail logic diagrams will amalgamate the data relationship diagram and the report (or file) layout diagram from the functional specification to illustrate the flow of the program. They should link the input and output format to the data.

Each database table will roughly equate to each subroutine.

The file layout diagram will roughly equate to the final output internal table to be created in the code.

The diagram should not be a simple copy and paste of the diagrams from the function specification. The programmer should investigate efficient ways of coding the program. For example, often it is more efficient to perform selects on a database table from the data relationship diagram in the final part of the processing where the output is formatted. Eg you are to produce a customer report for all the customers that have outstanding invoices for over 30 days. Through program validations and calculations the number of valid customers is greatly reduced. Only at this point would you retrieve the customer details from the database to be displayed.

The data relationship should be considered in two ways in this diagram. If a ’many to one’ relationship exists between two tables because of the program flow (but does not appear in the functional specification as the database relationship is only ‘one to one’ or ‘one to many’). This should be illustrated, as it will have an impact on where the selects in the code


1 Selection Screen Processing

P_COMP

Is companycode valid?

Yes

No

Accept companycode

Issue errormessage to

screen. Leave fieldopen for input

RB_TEST

Is TestRadiobutton

selected

Yes

No

Set program modeto test

Set program modeto live


appear. For example, the functional specification may state that document headers are selected first and then the subsequent item lines are then selected afterwards. However it may prove to be more efficient to select the item lines first and then get the corresponding header lines due to the information that the program has already accumulated.

Direction arrows should be included in the diagram, but it should not be a full on logic-flow diagram to avoid over complication. There should be no decision logic included in the diagram unless this impacts upon where the data is taken from or what the overall output is.

Example:


3.5.5.3 Final Processing


< The final processing section will differ depending on the type of program being designed. A report/outbound program should illustrate the final output of the program (example 1) while an


2 MAIN PROCESSING

Is RB_OPENselected?

Yes

No

KNA1

BSID BSADNote 1 Note 2

Note 3

Note 4Report table


inbound program should show the screens that are processed and the function codes that navigate between them (example 2).

Example 1:


3 FINAL PROCESSING

Report to besent to the

spool?

Set printparameters

Yes

I_OUTPUT

Header Detail Lines Summaries

Company

AccountingClerk

Customer

DocumentNumber

Amount

DaysOverdue

AccountingClerk

Company


Example 2:




3.5.5.4 Detail Logic Notes


< The notes should complement the detail logic diagrams.

They should include all the error messages (ID and Class), as well as the complete SQL statements (all fields and selection criteria) and the function modules used. Details of calculations or particular formatting should also be included here.

Example:

Note 1

Retrieve the following fields from BSID (Customer open documents table)

BUKRS (Company Code)

BELNR (Document Number)

KUNNR (Customer Number)

DMBTR (Amount in local curreny)

BLDAT (Document Date)

By the following key

BUKRS (Company Code) = P_COMP

If no records are found issue an error message to the screen: E012(ZF) ‘No records found for company code P_COMP’ and return to the selection screen.

Note 2

Etc…


3.5.6 Interactive Report Flow

TEXT TO BE REMOVED. GUIDANCE ONLY < If the report is an interactive report, mention the flow of the navigation in details > END OF GUIDANCE TEXT

3.5.7 Sort Criteria Details

TEXT TO BE REMOVED. GUIDANCE ONLY < Mention the sorting criteria of the Report Output. Specify the field name at different level of sorting.> END OF GUIDANCE TEXT



3.5.8 Calculations and Page Break related information

TEXT TO BE REMOVED. GUIDANCE ONLY < Mention the calculation logic in detail and the Page break information

Example:Calc 1 – Expected Production CasesThis field is calculated by converting the number of Lals in the “Actual Syrup Used Lals” field to cases based on the alternative unit of measure that has been set up for the material. The CF_UT_UNIT_CONVERSION function module can be used to calculate this value.



TEXT TO BE REMOVED. GUIDANCE ONLY< This section should detail the attributes of any custom table used, and the properties of its fields.NB: Existing SAP Data Elements and/or Domains should be used whenever possible when creating custom table fields, in order to avoid unnecessary typos. In this instance, the data table row for that field should not be completed beyond ‘Domain’, as the remaining attributes will be default values for the selected Domain > END OF GUIDANCE TEXT

Table Name

Short text

Size category

Table maintenance allowed

Data class

Buffering

Table maintenance generator

Authorization Group

Field Name

Data Element


Key Field

Foreign Key

Description

Comments



3.5.10 Recovery and Restart

TEXT TO BE REMOVED. GUIDANCE ONLY< If the program fails half way through will this have an impact on any programs to be run after its completion? Who will re-run the report if it does not function properly? Should anyone be alerted if certain validations fail?> END OF GUIDANCE TEXT

3.5.11 Language of texts


< The texts of the report may be different in different countries. What language should be used to derive these texts? The login language or another?


3.5.12 Currency and Units of Measure

TEXT TO BE REMOVED. GUIDANCE ONLY: < Are all the units of measure and currency details in the data mapping tables correct? Will the report work for different currencies? What about the EURO? What happens to the report if the common measure of weight used on client’s sites is changed to tonnes instead of kilograms? Or to stones and pounds? > END OF GUIDANCE TEXT



3.6 SAP BW Report

3.6.1 Report Description:

WhoWhyWhatWhen

3.6.2 Report Layout

Original Layout

(Original File to be attached)

Data model to retrieve the above spreadsheets follows:

Row Description/Formula Characteristic Characteristic Value

Key figure

Column Description/Formula Characteristic Characteristic value

Key figure

Notes (if any):

3.6.3 Report Selections and Navigation

3.6.3.1 Report Selections (Filters)

Field Name Other Selection Information



3.6.3.2 Report Navigation (Free Characteristics)

Field Name Other Navigation Information



3.7 SAP Workflow

3.7.1 SAP Workflow Diagram


< Show the technical workflow diagram(One can use Visio or can even paste the diagram from the downloaded file from the workflow builder – Menu options: Workflow Print Graphic)

SAP Workflow Process Steps:

Business Process Trigger:

The process steps should describe the technical implementation done in the workflow template. There should be a one to one match between the process step & the workflow diagram. Thus if the workflow diagram had 12 boxes and each numbered from 1 to 12 – then there should be 12 process steps describing each step in the diagram.

See below for sample pseudo-code:1. Workflow is started via transaction XYZ.2. Condition Step: Describe the condition.3. Container Operation: Describe the operation taking place in the container.

3A.Background Step: Describe the step; for example: the date after eight business days is calculated. This date will be used to send a notification to the supervisor of Approver#1 is no action was taken by Approver#1 for three business days.

4. Background Step: Approver#1 is determined.5. Activity (Dialog) Step: The work item is presented to the approver for necessary action

(Approve/ Reject).

Approve Path6. Container Operation: The status container is set to “A”.7. Container Operation: The name of approver is added to a multi line container.

Reject Path8. Activity (Dialog) Step: A window is presented to approver to enter the rejection comments.9. Background Step: The document is reverted back to the original status.10. Background Step: A mail is sent to the initiator informing him/her about the rejection.11. Process Control Step: The workflow instance is terminated.12. The workflow ends.

Exception Handling13. Background Step: A mail is sent to the workflow administrator.14. Background Step: A mail is sent to the approver stating that the work item will be presented

again for approval.

Escalation Handling



14A. Background Step: Supervisor of Approver#1 is determined.14B. Background Step: A mail is sent to the Supervisor of Approver#1 informing

that no action was taken by Approver#1.

15. Loop: If the status container is not equal to “A” (Approved); the work item is routed back to the approver; else the workflow continues to the next approver.


3.7.2 Technical description

Enter the requested information and type one “X” in each checkbox group

Trigger mechanism (Mention the start condition for the workflow, e.g. on creation of a purchase document, batch program etc)

Start ConditionExample – The workflow should start only for certain document type , work flow should start only if credit amount is greater than 250000 etc

SAP business Object (Mention the SAP business object, if possible. Otherwise indicate the object in general terms (e.g., Purchase Requisition)

SAP Standard Workflow Task/Template

In case of enhancement required for SAP delivery workflow is required

Level of approval required

Agent determination technique

Role Security Role Org Unit HR org structure.Custom Table Agents maintained in custom tableDistribution lists

Unspecified To be decided in technical design; Will provide detailed requirements in this doc.

Other Specify:

If the agent determination technique is different for each foreground step then repeat this section.

Mention logic for agent determination (if any)

Notification destinationInternal SAP user SAP Inbox External E-mail Id Example Lotus notes

Workflow notifications text If any specific work item text/work item subject to be used

Escalation handling (if any) If any deadline monitoring is to be done. Example: If approver does not approve for 3 business days notify his supervisor

Integration with portal

Configuration dependencies

(Example setting up a new organization structure)

Error handling (if any)

An exception situation could occur if workflow routes to a one position is vacant/not available (i.e. no user is assigned to that position.) If a specific report or additional information is required. Add attachment if necessary.



Substitution

3.7.3 Business Object Information

Object Type: Description: Short Description: Program: SuperType: Application

Key Fields

Element Description Dictionary Field

Attributes (only mention those used in the workflow template)

Element Description Source Attribute Property Dictionary Field Pseudo logic Ref

VirtualDatabase

MultilineMandatory

Instance-independent

A1

VirtualDatabaseObj Status

MultilineMandatory

Instance-independent

A2

Pseudo logic : Mention Logic for custom attributes only.

A1:

A2:

Method (only mention those used in the workflow template)

Name Description Source Result Type ABAP Pseudo logic RefDialogSynchronous

Result parameter

Instanceindependent

Function Module

APITransactionDialog

ModuleReportsOthers

M1



DialogSynchronous

Result parameter

Instanceindependent

Function Module

APITransactionDialog

ModuleReportsOthers

M2

Pseudo logic: Mention Logic for custom methods only.

M1 Pseudo logic:

Parameter List

Imp EXP Parameter List Mutiline

Exception

M2 Pseudo logic:

Parameter List

Imp EXP Parameter List Mutiline

Exception

Event (only mention those used in the workflow template)

Name Description Parameter List Import Export

3.7.4 Workflow Definition

Abbreviation: Number: Name: Triggering Events: Object Type: Event:

Workflow Container:

Element Description Import(Y/N)

Export(Y/N)

Multiple Values(Y/N)

Mandatory(Y/N)

Dictionary Field

Object Type

Binding Workflow Container/Event Container: (Indicate in the middle column below as to the direction of the parameters - or )



Workflow Container Element Event Container Element

Responsibility Agents:

Task Name Agent Deadline Notification

3.7.5 Deadline Monitoring Requirements

Task Name Deadline Time Agent Type

3.7.6 Reporting / Form Requirements

Description SAP Tool Report Name Custom Requirements

3.7.7 Custom screen design

TEXT TO BE REMOVED. GUIDANCE ONLY < Technical details of custom screen can be incorporated here. Number of screens required and flow diagram can be included and provide the selection screen screen shot along with the table name and field name and screen shot for the required output. > END OF GUIDANCE TEXT


Table NameShort textSize categoryTable maintenance allowedData classBufferingTable maintenance generatorAuthorization Group



Field Name

Data Element

Domain Type

Length Check Table-Field

Key Field

Foreign Key

Description

Comments

3.7.9 User Exit / Enhancement Detailed Description

TEXT TO BE REMOVED. GUIDANCE ONLY < If workflow to be triggered from user exit or if any modification required using user exit. > END OF GUIDANCE TEXT

3.7.10 Configuration Information

TEXT TO BE REMOVED. GUIDANCE ONLY < List the configuration/custom objects that need to be maintained for this workflow to function. Some commonly used examples are listed below > END OF GUIDANCE TEXT

Server: Client:Activity T-Code Screen shot

3.8 SAS Developments

Text



4.Security and Authorization Requirements


< Define the role matrix related with the objects and processes for the authorization objects. List Segregation of duty requirements. > END OF GUIDANCE TEXT



5.Attachments


asset data migration

Documents

development ip

data requirements

aga development functional

functional description

data validation

data cleaning requirements

data flow diagram

legacy asset data transfer