Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Technical Specification - Data Conversion/Interface: Ricefw Name

Download as pdf or txt
Download as pdf or txt
You are on page 1of 11

Technical Specification - Data Conversion/Interface

RICEFW Name
Date Created :

Page 1 of 11
Document Information
Business Area

GAP/CR ID

Type of development

FS Definition Form ID

SAP R/3 Version

Global / Local

Approval

Approved by Name Role Signature Date


Process Team
Lead
Development
Team Lead

Document History

Version Author Reason for change Date


1.0

Related Documents

<Page 2 of 11>
Table of Contents

1 GENERAL INFORMATION .................................................................................................................. 4


2. DESCRIPTION AND PURPOSE .......................................................................................................... 5
3. NOTES .................................................................................................................................................. 5
4. ASSUMPTIONS .................................................................................................................................... 5
5. ISSUES ................................................................................................................................................. 5
6. SELECTION CRITERIA ........................................................................................................................ 6
7. DATA CONVERSION & INTERFACE DEFINITION............................................................................. 6
8. FILE LAYOUT ....................................................................................................................................... 7
9. DATA MAPPING MATRIX .................................................................................................................... 7
10 ALE CONFIGURATION ........................................................................................................................ 7
11 CUSTOM DATA DICTIONARY OBJECTS (IF ANY) ........................................................................... 8
12 ERROR HANDLING ........................................................................................................................... 10
13 PERFORMANCE CONSIDERATIONS............................................................................................... 10
14 AUTHORIZATION DETAILS .............................................................................................................. 10
15 DEPENDENCY ................................................................................................................................... 10
16 RELEVANT FUNCTION MODULES ....................................... ERROR! BOOKMARK NOT DEFINED.
17 PSEUDO CODE .................................................................................................................................. 10
18 UNIT TEST PLAN ............................................................................................................................... 11

<Page 3 of 11>
1 General Information

WRICEF ID
Description
Transaction(s) (if applicable)
Package
Message Class (if applicable)
Develop. Class
Module
Data Conversion/Interface
User/User Group
Execution Mode
Run Frequency Language

Transport Information

Change Object Identifier Object Type


Request # Task # (Program ID, Layout Set ID, etc) (Program,
Transaction, Layout
Set)

<Page 4 of 11>
2. Description and Purpose

3. Notes
NA

4. Assumptions
1

5. Issues
NA

<Page 5 of 11>
Issue Date Raised to/Resolved By Issue Description Issue Resolution
# Raised

6. Selection Criteria

Name Table Field/ Select-option Comments (Range, Single/Multiple Default Value


Check box/ (S) or Selection, Patterns, Mandatory, etc.)
Radio button Parameter (P)
P

7. Data Conversion & Interface Definition


NA

File Name Inbound / File Type Location Description Logical File Comments
Outbound (ASCII, File Name Delimiter
I/O EBCDIC,
Excel file,
etc.)

System Diagram:

<Page 6 of 11>
8. File Layout

9. Data Mapping Matrix

9.1 For BDC/Call Transaction


NA

9.2 For ALE/IDOC/BAPI/Direct Input


NA

9.3 For LSMW

10 ALE Configuration
NA
Source System & Client or Logical System
name

Partner Profile
Target System & Client or Logical System
Name
Message Type
Basic IDoc Type
IDoc Extension
Business Object / Methods
Process Code / Function Module

IDoc Type Structure

<Page 7 of 11>
SAP IDoc Type:
IDoc Extension:
Parent Segment:
New Child Segment:
IDoc Field

Field Data Format/Length Comments


Name Element/Type

Assignment of FM to Logical message and IDoc type


Function Module FctTyp BasicTyp Log mess type
Obj type Directn Extension MsgCode MsgFunct

Characteristics of inbound function modules

Function Module Input type Dialog allowed

Inbound process codes


Process Code Process Code description

Link type and serialisation type of message type


Message type Serialisation object type Object type link

Workflow event linkages to be activated


Object type Event Receiver type

11 Custom Data Dictionary Objects (if any)


NA
Table Name
Type [ ] Transparent Table [ ] Structure
Short text
Size category
Table maintenance
allowed
Data class
Buffering
Table maintenance
generation
<Page 8 of 11>
Authorization Group
Function Group
Event Name(s)
Field Data Domain Type Length Check Key Foreign Description
Name Element Table- Field Key
Field

Comments

<Page 9 of 11>
12 Error Handling

12.1 Error and process log

1 Reconciliation Report

2 Severe Error Conditions

3 Post execution notification details

4 Restart/Recovery

• Error Messages: NA
Error HOW ERROR MESSAGE SHOULD Error Messages Corrective action
BE REPORTED

10. Performance Considerations

11. Authorization Details

12. Dependency

13. Pseudo Code

<Page 10 of 11>
14. Unit Test Plan
Normal Functionality -

Exception - special logic or exceptions (e.g., do not process Government Markets customers, only process pre-packs)
NA

Test Step Step Description Test Data Expected Result Actual Result Executed By/Date Remarks
Condition

Error Handling - functionality in case of errors (e.g., Vendor not found, Record already exists)
NA

Test Step Step Description Test Data Expected Result Actual Result Executed By/Date Remarks
Condition

Page 11 of 11

You might also like