Transfer Trading Partner to CFP

Project Trading Partner from CD to
CFP
Development Request:
Title: Transfer Trading Partner to CFP from CD for Specific
Accounts
Functional Specification
Request ID: BP060I0050
Table of contents
1 REQUEST OVERVIEW.........................................................................................................................................................................4
1.1 INTRODUCTION .................................................................................................................................................................................4
1.1.1 Purpose ...................................................................................................................................................................................4
1.2 REQUEST OVERVIEW.........................................................................................................................................................................4
2 REVISION HISTORY............................................................................................................................................................................5
3 *FUNCTIONAL SPECIFICATION APPROVAL....................................................................................................................................5
4 TECHNICAL ESTIMATES ...................................................................................................................................................................5
5 TECHNICAL SPECIFICATION APPROVAL........................................................................................................................................5
6 FUNCTIONAL SPECIFICATIONS........................................................................................................................................................6
6.1 FUNCTIONAL REQUIREMENTS ..............................................................................................................................................................6
6.1.1 *Business Driver ......................................................................................................................................................................6
6.1.2 *General Process Description..................................................................................................................................................7
6.1.3 Alternative Solutions................................................................................................................................................................7
6.1.4 Assumptions ............................................................................................................................................................................7
6.1.5 Issues ......................................................................................................................................................................................7
6.1.6 *Related Business Processes: ...............................................................................................................................................8
6.1.7 Security/Authorization Requirements......................................................................................................................................8
6.1.8 Documentation Requirements.................................................................................................................................................8
6.2 FUNCTIONAL DESCRIPTION: REPORT AND FORMS .....................................................................................................................................8
6.2.1 Report/Form Attributes.............................................................................................................................................................8
6.2.2 Type of Development...............................................................................................................................................................8
6.2.3 *Selection Screen (Report Selection Criteria)..........................................................................................................................9
6.2.4 *Data Selection........................................................................................................................................................................9
6.2.5 *Report/Form Layout (if not provided in attachment above)....................................................................................................9
6.2.6 *Exception Handling Rules......................................................................................................................................................9
6.2.7 Special Characteristics.............................................................................................................................................................9
6.2.8 *Printing Requirements............................................................................................................................................................9
6.3 FUNCTIONAL DESCRIPTION: INTERFACE, DATA CONVERSION AND EDI............................................................................................................9
6.3.1 *Dependencies/Prerequisites.................................................................................................................................................10
6.3.2 *Conversion/Interface Information.........................................................................................................................................10
6.3.3 Legacy Systems Involved......................................................................................................................................................10
6.3.4 *Data Requirements .............................................................................................................................................................10
6.3.5 *Processing Requirements (Source-Extraction, Target-Load)..............................................................................................10
6.3.6 *Exception Handling Rules....................................................................................................................................................11
6.3.7 Special Requirements............................................................................................................................................................11
7 FUNCTIONAL TEST ..........................................................................................................................................................................12
7.1 TEST SPECIFICATION.......................................................................................................................................................................12
7.2 *TESTING APPROACH.......................................................................................................................................................................12
7.3 TEST DATA & OTHER NEEDS............................................................................................................................................................12
7.4 TEST SYSTEM & ENVIRONMENT.........................................................................................................................................................12
7.5 *FUNCTIONAL TEST SCENARIOS..........................................................................................................................................................12
8 TECHNICAL SPECIFICATIONS........................................................................................................................................................14
8.1 TECHNICAL REQUIREMENTS...............................................................................................................................................................14
8.1.1 *Business Driver ....................................................................................................................................................................14
8.1.2 *General Process Description................................................................................................................................................14
8.1.3 Alternative Solutions..............................................................................................................................................................14
8.1.4 Assumptions...........................................................................................................................................................................14
8.1.5 Process Flow..........................................................................................................................................................................14
8.1.6 Issues ....................................................................................................................................................................................15
8.1.7 Security Details......................................................................................................................................................................15
8.1.8 Exception handling.................................................................................................................................................................15
8.1.9 Dependencies / Prerequisites................................................................................................................................................15
8.2 DETAILED TECHNICAL DESCRIPTION: REPORT, FORM AND QUERY..............................................................................................................15
8.2.1 *Report, SAPScript Forms or Smartforms.............................................................................................................................15
8.2.2 *Selection Screen (Report Selection Criteria)........................................................................................................................15
8.2.3 Special Requirements Processing.........................................................................................................................................16
Confidential
Page 2
/opt/scribd/conversion/tmp/scratch3635/64025006.doc
7/28/2011
8.2.4 Attributes................................................................................................................................................................................16
8.2.5 Variants Created and Data in Variants..................................................................................................................................16
8.2.6 *Program Flow and Pseudocode...........................................................................................................................................16
8.3 DETAILED TECHNICAL DESCRIPTION: INTERFACE, DATA CONVERSION AND EDI...............................................................................................16
8.3.1 *Attributes...............................................................................................................................................................................16
8.3.2 *Interface/Conversion Steps..................................................................................................................................................16
8.3.3 Data Requirements ..............................................................................................................................................................16
8.3.4 *Scheduling Requirements....................................................................................................................................................17
8.3.5 *Update Process (Required for inbound interfaces)..............................................................................................................17
9 DATA DESCRIPTION.........................................................................................................................................................................18
10 TECHNICAL TEST PLAN ................................................................................................................................................................18
10.1 TESTING APPROACH......................................................................................................................................................................18
10.2 COMPLETION CRITERIA ..................................................................................................................................................................18
10.3 TEST DATA & OTHER NEEDS..........................................................................................................................................................18
10.4 TEST TOOLS & ENVIRONMENT.........................................................................................................................................................18
10.5 TEST DEPENDENCIES/CONSTRAINTS..................................................................................................................................................18
10.6 UNIT TEST CASES AND RESULTS......................................................................................................................................................18
11 APPENDIX A: DATA MAPPING .....................................................................................................................................................19
Confidential
Page 3
7/28/2011
1 Request Overview
1.1
1.1.1
Introduction
Purpose
This document will be used to capture AIGs approved business requirements in a clear, concise
and standardized format from which the technical specifications can then be developed.
Fields marked with an asterisk (*) and highlighted in red are mandatory and therefore must be
completed by the functional analyst in order for the functional specification to be approved and
moved to technical specification development stage. NOTE: Sections not relevant for the
development request may be removed from the document.
Business and Technical signoff (Section 5) is considered AIGs acceptance of this
deliverable (specification).
Modifications and/or additions to this specification
subsequent to approval will be subject to a change order and must be processed via
Change Control.
1.2
*Date:
Request Overview
SAP
Version:
R/3
R/3 Module:
Dev. Request ID:

*Title
Process Team:
Transfer Trading Partner to CFP from CD
*Short Description
*Request Type:
Systems Impacted:
( ) Form
( ) Report
( ) Interface
( ) Conversion
(X ) R/3 Extension
( ) Workflow
( ) Query
() Other Development
(X)R/3 and/or FSCD
( ) CRM
( ) BW
( ) Other
*Date Required:
*Complexity:
( ) High
(X) Medium
*Business Owner:
Mark Paffmann
( ) Low
Ext.:
*Functional Analyst:
Ext.:
*BE Team QA
Ext.:
Technical Analyst/
Developer:
Ext.:
Confidential
Page 4
7/28/2011
2 Revision History
To track changes to specification after it has been approved
Version #
Date Modified
1.1
08/25/2010
Modified By
Brief Description of Change

Additional information
3 *Functional Specification Approval

Final Sign-off here indicates acceptance of functional specification. (Only upon successful completion of
Functional Specification review.)
Signature
Date
*Business Process Owner

Approval:
*Business Engineering
Process Lead Approval (BE
Team QA):
*Application Lead Approval:
4 Technical Estimates
Plan
Technical Estimate
Revised
Technical Spec.
Development
Unit Test
QC Review
Total
5 Technical Specification Approval

Final Sign-off here indicates acceptance of technical specification.
Signature
Date
*Client Dev. Lead Approval:

*App. Dev. Approval:
Confidential
Page 5
7/28/2011
6 Functional Specifications
6.1
6.1.1
Functional Requirements
*Business Driver
List business requirements for this request.

Currently for transactions posting to accounts listed in set YV_ICACCT only inter-company
transactions are being populated to the trading partner field in CD only and not transferred to
shadow GL (FI) so they can be included in file to CFP GL (program ZCLI_SAPGL_TO_CFP). Need
trading partner to transfer to shadow GL and onto CFP GL, this will require validation in CD as well
as FI (currently have files uploaded in FI that contain postings to GL accounts included in set
YV_ICACCT). In CD Trading Partner field (FKKOP-VBUND) can be entered during clarification,
disbursement, journal entry posting and reversal (Believe event 670 can be used for most of these
transactions. In FI the Trading Partner field will need to be made available for posting on t-code
FB01 and FB02 (did not see any other t-code available for posting entries that users have access
to), this is required due to Treasury settling and reconciling inter-company transaction occuring in
CD.
1. For GL Accounts sitting in the SAP CD set YV_ICACCT add validation to transaction codes in FI
and CD module of SAP under R3P to force users to input trading partner.
2. Include trading partner in any summarization of similar GL postings when transferring items
over from CD to FI (shadow GL) using FPG1.
3. GL accounts not included on the inter-company tables do not populate to the trading partner
field in FI even though users are populating this field in CD. This is required as trading partner
populated from inter-company transactions does populate the field.
4. Same validation being done in CD would be required for postings made to transaction codes
FB01 and FB02 (also any other t-code currently not used that would allow user to make postings).
5. The trading partner should also populate the trading partner field on the file sent to DI Layer.
Currently this field only populated when trading partner account posted to by SAP for intercompany transactions. Layout is attached for file sent to DI-Layer below:
Microsoft Office
Excel Worksheet
Package
Microsoft Office
Excel Worksheet
6. There is also a file being uploaded on a monthly basis for PCG/WINS that post entries to these
accounts through FI, will need to have trading partner field added to layout for upload file to
ensure field is populated. Example of file being uploaded is in the 2 files above, Excel spreadsheet
is file layout.
Confidential
Page 6
7/28/2011
7. Any reversal of documents whether done in FI or CD should capture the trading partner
originally used in the reversal document.
8. Will also need to define trading partners in SAP CD and keep this table in sync with CFP GL
(table T880).
6.1.2
*General Process Description
Describe at a high level the process being requested. Description may include a process flow if
deemed necessary.
Any posting made to GL Accounts in set YV_ICACCT requires trading partner and trading partner
for all non inter-company gl accounts should transfer from CD to FI and also populate file sent to
DI Layer on interface report. Also any reversal of document used for inter-company should also
capture and include trading partner stored in the original document being reversed.
6.1.3
Alternative Solutions
If applicable, list any alternative solutions to the business requirements that were considered and
reasons for their rejection.
6.1.4
Assumptions
List factors that affect the requirements. These factors may not be design constraints, but may be
areas in which future changes might drive change in the requirements.
During the last week of the month Treasury makes request to remove automatic posting only for
inter-company accounts to clear balances for CD transactions. Should continue to ensure that the
trading partner field is validated for these transactions also.
6.1.5
Issues
List any issues affecting completion of the Functional Specification.

#
Issue
Resolution
1
2
3
Confidential
Page 7
7/28/2011
6.1.6
*Related Business Processes:
List the BPP(s) related to the process, sub-process and activities identified in this Request
Process:
Sub-Process:
Activity:
Sub-Process:
Activity:
Sub-Process:
Activity:
BPP1:
Process:
BPP2:
Process:
BPP3:
6.1.7
Security/Authorization Requirements
Provide any special authorization checking or data security provisions required.
6.1.8
Documentation Requirements
Provide documentation expectations such as online documentation, release notes, etc.

None.
6.2
6.2.1
Functional Description: Report and Forms
Report/Form Attributes
*Name of Report/Form/Query:
N/A
*Type:
( ) ABAP report
( ) Form
*Report Layout attached/linked:
( ) No
( ) Yes Filename:
*Run Mode:
( ) Foreground
(Online)
( ) Background (Batch)
*Frequency:
( ) Real-time
( ) On-demand
( ) One-time
( ) Annually
( ) Quarterly
( ) Monthly
( ) Weekly
( ) Daily
( ) Other
Expected Data Volume (Records):
TBD
Date test data will be available:
Immediately
( ) Query
What SAP transactions are

involved?
Menu path for transaction(s)
6.2.2
Type of Development
*Existing vs. Custom:
( ) Modification of Standard Report/Form
*Have you looked at possible standard Reports/Forms?
( ) Yes
( ) Custom Report/Form
( ) No
Name of Standard Report/Form:

Access or path for the Report/Form:
Confidential
Page 8
7/28/2011
6.2.3
*Selection Screen (Report Selection Criteria)
Describe the selection screen of the report. Specify the fields for the selection and what checks need
to be done after the user has entered his or her criteria.
Screen Label
6.2.4
Referenced
Field
Range of
Value
Attributes,
Default
Values
Validations /
Checks
Comments/ Selection
Criteria (options,
parameters, radio
buttons, checkboxes)
*Data Selection
(Describe what data should selected by the report.)
6.2.5
*Report/Form Layout (if not provided in attachment above)
Provide a layout of the form or report here if one has not been provided in a separate attachment.
Note you may use screen captures as required. Layouts should include: Desired report headers and
footers, report columns and field spacing.
None.
6.2.6
*Exception Handling Rules
Describe the exception handling processes to support the rules. Include any error conditions, error
messages, etc.
None.
6.2.7
Special Characteristics
(ex. Sorting, grouping, where total or subtotals should occur, if any, drilldown, etc.) List any special
requirements such as signatures, logos, OCR, bar-coding, function keys, menu bars, special timing,
language translations, etc.
None.
6.2.8
*Printing Requirements
Identify any printing requirements such as Special Paper, Preprinted Forms: (e.g. checks, multiple
copies with impact printer, etc.)
None.
6.3
Functional Description: Interface, Data conversion and EDI
*Name of Interface or Conversion:

*Type:
( ) Interface
*Mapping Attachment:
( ) No
Confidential
Page 9
( ) Conversion
( ) Yes Filename:
7/28/2011
6.3.1
*Dependencies/Prerequisites
List any dependencies or other external requirements that must be met before the
interface/conversion can be completed. Include both legacy and SAP system dependencies (e.g. R/3
upgrade/patch, files from other systems, condition of data, etc.)
Description
6.3.2
Related Document(s)
*Conversion/Interface Information
*Direction of Interface:
( ) Inbound to
SAP
( ) Outbound from
SAP
( ) Bi-Directional
*Frequency:
( ) Real-time
( ) On-demand
( ) One-time
( ) Annually
( ) Quarterly
( ) Monthly
( ) Weekly
( ) Daily
( ) Other
Acknowledgement Required:
( ) No
*Expected Data Volume:
TBD
Date test data is to become available:
TBD
6.3.3
( ) Yes
Legacy Systems Involved
List the existing Legacy systems along with a short description involved in this development effort.
6.3.4
*Data Requirements
Describe the condition of data to be converted/transferred (if known).

Provide a high level data map by identifying source or target fields in SAP.
Data Condition:
Data must match layout described in mapping document (below).
*Data Mapping
6.3.5
*Processing Requirements (Source-Extraction, Target-Load)
NOTE: Do not include field-level details these should be specified in the data mapping
document.
SAP Load/Extraction: For inbound interfaces describe how the inbound data should be processed,
including a Transaction Code that should be executed / simulated, or a BAPI / Program if known.
For outbound interfaces describe how the outbound data should be derived, including source tables,
selection criteria, and list any relevant transactions / BAPIs.
Confidential
Page 10
7/28/2011
6.3.6
*Exception Handling Rules
Specify instructions to be followed when errors occur, or any processing outside the normal process
flow.
6.3.7
Special Requirements
Provide any special requirements related to this development effort such as language translations,
configurability or personalization allowed, etc.
None.
Confidential
Page 11
7/28/2011
7 Functional Test
7.1
Test Specification
This portion of the document is used to plan the unit testing. It includes items such as defining the test
participants, the test environment, the schedule, and scope of the testing event.
Victor Randolph
Functional Test Lead:

Additional Test Team Participant(s):
7.2
*Testing Approach
Provide a brief description of the overall approach and testing needs, including any sequencing
dependencies.
7.3
Test Data & Other Needs
If any, specify test data set-up & refresh needs, volume of data, timeliness of data, etc.
7.4
Test System & Environment
Identify test system and client.

Test System:
R3D
Client:
120
7.5
*Functional Test Scenarios
Document test scenarios to test all of the functional requirements. Include a test scenario for each
different business scenario that may occur.
ID
Test Scenario
Expected
Results
Comments
1. Cash coming in from

Company Code 0108
should get posted to 0165
with Trading Partner in
0407. Canadian currency
to US currency.
Confidential
Page 12
7/28/2011
2. Remove all Company

Codes from all RSP
Trading Partner table and
only leave Company Code
0183. Posting allocation
posting to 0165. All RSOs
Company Codes should be
mapped to 0183.
Confidential
Page 13
7/28/2011
8 Technical Specifications
8.1
8.1.1
Technical Requirements
*Business Driver
List business requirements for this request.
8.1.2
*General Process Description
Describe at a high level the process being requested
8.1.3
Alternative Solutions
If applicable, list any alternative solutions considered and reasons for their rejection.
8.1.4
Assumptions
Describe special issues and assumptions, which might impact the overall design or implementation of
the software. Include any business product line considerations that will impact the manner in which
the software is to be designed, implemented or tested.
8.1.5
Process Flow
Include a Visio diagram of the technical process flow including triggers, inputs, outputs and program
flow.
Confidential
Page 14
7/28/2011
8.1.6
Issues
List any issues affecting completion of the Technical Specification.

#
Issue
Resolution
1
2
8.1.7
Security Details
Describe processing required to address security requirements defined in the functional specification.
None.
8.1.8
Exception handling
Describe the exception handling components used to support the rules specified in the functional
specification. Include any error conditions, error messages, exception classes, return codes, etc.
8.1.9
Dependencies / Prerequisites
List any dependencies or other external requirements that must be met before the development
object can be completed. Include both legacy and SAP system dependencies (e.g. R/3
upgrade/patch, configuration requirements, files from other systems, condition of data, etc.)
Description
Related document(s)
8.2
8.2.1
Detailed Technical Description: Report, Form and Query
*Report, SAPScript Forms or Smartforms
*Report will be created via:
( ) ABAP Program
( ) ALV
( ) Smartform
( ) SAPScript
( ) BW
( ) Report
Writer/Painter
( ) Other
*Name of Report/Form:
( ) Report
Report/Form Layout Attachment:
( ) No
8.2.2
) Form
) Yes - Filename:________________________
*Selection Screen (Report Selection Criteria)
Describe the selection screen of the report. Specify the fields for the selection and what checks need
to be done after the user has entered his or her criteria.
Screen Label
Referenced
Field
Range of
Value
Attributes,
Default
Values
Confidential
Page 15
Validations /
Checks
Comments/ Selection
Criteria (options,
parameters, radio
buttons, checkboxes)
7/28/2011
8.2.3
Special Requirements Processing
Describe the processing required to support any special requirements defined in the functional
specification. (e.g. signatures, logos, OCR, bar coding, function keys, menu bars, special timing, etc.)
None.
8.2.4
Attributes
Logical Database:
None
External Form Calls:
None
Called Transactions:
TBD
Function Group:
None
Function Calls:
8.2.5
Variants Created and Data in Variants
None
8.2.6
*Program Flow and Pseudocode
Briefly explain the program flow and provide pseudo-code.
8.3
8.3.1
Detailed Technical Description: Interface, Data conversion

and EDI
*Attributes
*Interface Type:
( ) ALE
( ) EDI
( ) XML
( ) Other
Function Group:
None
Posting Type:
None
Called Transactions:
TBD
BAPI Used:
None
Logical Database:
None
8.3.2
(X) Flat File
( ) BAPI / RFC
*Interface/Conversion Steps
Describe all manual and system steps to process this interface or conversion. This should include all
the restart procedure.
8.3.3
Data Requirements
Data Mapping:
Legacy/SAP Mapping document template provided in Functional Spec
Confidential
Page 16
7/28/2011
8.3.4
*Scheduling Requirements
Specify whether jobs should run during off-peak hours, frequency, manual or automatic start.
None.
8.3.5
*Update Process (Required for inbound interfaces)
Describe the process that will occur to update the proper data requested. A pseudo-code document
may be attached.
Update Program Name(s):
Transfer Mechanism:
( ) BDC
( ) Direct Input
( ) LSMW
( ) Call Transaction
( ) Function Module
( ) BAPI
( ) Other
Update Parameters:
Confidential
Page 17
7/28/2011
9 Data Description
10 Technical Test Plan

This section of the document is used to plan the Technical Unit Test. It includes items such as defining
the test participants, the test environment, the schedule, and scope of the testing event. Unit test cases
and results will be documented in a separate document.
10.1 Testing Approach

Provide a brief description of the overall approach and testing needs
10.2 Completion Criteria

How will you determine test completeness?
10.3 Test Data & Other Needs

If any, specify test data set-up & refresh needs, volume of data, timeliness of data, etc.
10.4 Test Tools & Environment

Identify test tools required for the technical test
Test System
R3D
Client
120
Tool
N/A
Test Programs
N/A
10.5 Test Dependencies/Constraints

Indicate if there are any dependencies or constraints related to this object.
No.
10.6 Unit Test Cases and Results

Unit test cases and results will be documented in a separate document. Link completed Unit test results
document below.
Confidential
Page 18
7/28/2011
11 Appendix A: Data Mapping
Confidential
Page 19
7/28/2011

Transfer Trading Partner to CFP

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Transfer Trading Partner to CFP

Uploaded by

Copyright:

Available Formats

Project Trading Partner from CD to

Request ID: BP060I0050

Request ID: BP060I0050

Request ID: BP060I0050

Dev. Request ID:

(X)R/3 and/or FSCD

Request ID: BP060I0050

Brief Description of Change

3 *Functional Specification Approval

*Business Process Owner

5 Technical Specification Approval

*Client Dev. Lead Approval:

Request ID: BP060I0050

List business requirements for this request.

Request ID: BP060I0050

*General Process Description

List any issues affecting completion of the Functional Specification.

Request ID: BP060I0050

*Related Business Processes:

Provide any special authorization checking or data security provisions required.

Provide documentation expectations such as online documentation, release notes, etc.

Functional Description: Report and Forms

*Report Layout attached/linked:

Expected Data Volume (Records):

Date test data will be available:

What SAP transactions are

*Existing vs. Custom:

( ) Modification of Standard Report/Form

*Have you looked at possible standard Reports/Forms?

Name of Standard Report/Form:

Request ID: BP060I0050

*Selection Screen (Report Selection Criteria)

(Describe what data should selected by the report.)

*Report/Form Layout (if not provided in attachment above)

*Exception Handling Rules

Functional Description: Interface, Data conversion and EDI

*Name of Interface or Conversion:

Request ID: BP060I0050

*Expected Data Volume:

Date test data is to become available:

Legacy Systems Involved

Describe the condition of data to be converted/transferred (if known).

Data must match layout described in mapping document (below).

*Processing Requirements (Source-Extraction, Target-Load)

Request ID: BP060I0050

*Exception Handling Rules

Request ID: BP060I0050

Functional Test Lead:

Test Data & Other Needs

Test System & Environment

Identify test system and client.

*Functional Test Scenarios

1. Cash coming in from

Request ID: BP060I0050

2. Remove all Company

Request ID: BP060I0050

List business requirements for this request.

*General Process Description

Describe at a high level the process being requested

Request ID: BP060I0050

List any issues affecting completion of the Technical Specification.

Detailed Technical Description: Report, Form and Query

*Report, SAPScript Forms or Smartforms