You are on page 1of 4

Functional Design Document

FUNCTIONAL SPECIFICATION
COPA USER EXIT

Section I: Justification
Spec ID: FICO-
Area (SAP System FICOCOPA Date:
components) (09/13/2010)
Requested by: Dale Tel no:      
Title: COPA User Exit to post SD revenue to different Value Fields based on Invoice type.
Short description: SD revenue condition types is same for either external invoice or Intercompany
invoice, requirement is to distinguish the revenue to different value fields ( Revenue
external customer and Revenue Intercompany) based on invoice type.
Program type: Batch input Online transaction call Direct input
Others
Priority: High/mandatory Medium/recommended Low/optional
Volume of data: frequent Data available from:
1. Quality of legacy data: Good Average Poor
2. Complexity of legacy data: Simple Average Complex Very complex
3. Complexity of manual input: Simple Average Complex
4. Number of screens:       Screens

General information:
Results if no conversions are created: Legal requirements not fulfilled
Lack of essential business information
Lack of functions compared to legacy system
Others:      
Approx. duration of development work:
Is there an alternative in the standard system? Yes No
Description of alternative: Assign SD condition types of both external and Intercompany to
single value field and make the COPA for specific inter company
customer to see the intercompany revenue.
Reasons why alternative is not acceptable: Performance problems Complexity
Others:      
Project cost:       Charge cost to:      
Cost approved by:      
Date of project Date of steering committee
management approval:       approval:      

1
Functional Design Document
Section II: FUNCTIONAL DESIGN
Functional Description: (short description of the required report)

SD condition types are assigned to COPA value fields to pass the revenue and discount
information. The current system is set up in such a way that same condition type is used
irrespective of billing to external customer or Intercompany but the revenue is
recognized in two different GL a/cs. In order to keep in line with financial accounting,
condition value from SD document need to flow to different value fields in COPA
depending on billing type.

Business Benefit / Need: (short description of the why the report is needed, impact if report
is not implemented)
Business will have clear identification of revenue in COPA and reconciling will be easy
between Accounting and COPA.

Input: (Functional description of the input)


Process: (describe the process, what the program should do on functional level)

In COPA Config Condition types are assigned to Value fileds as follows-


SD COPA Value
Condition Desc Field Desc
ZA00 Variant Base Price VV100 Revenue Domestic
YA00 Variant Price VV100 Revenue Domestic
ZVC0 VC prices total VV100 Revenue Domestic
ZLIS List Price VV100 Revenue Domestic
ZPRC Special Price VV100 Revenue Domestic
Capture PriceRndng
ZPRA 1 VV100 Revenue Domestic
Capture PriceRndng
ZPRB 2 VV100 Revenue Domestic
Capture PriceRndng
ZPRD 3 VV100 Revenue Domestic
DIFF Rounding Off VV100 Revenue Domestic
ZDIS Price Code Discount VV100 Revenue Domestic
Z001 Customer + Material VV100 Revenue Domestic
Z011 Customer Discount VV100 Revenue Domestic
Z012 Volume Pricing Disc VV100 Revenue Domestic
ZCTR Contract Price VV100 Revenue Domestic

When the billing type is IV, the assignment to value field should change to following-

SD COPA Value
Condition Desc Field Desc
ZA00 Variant Base Price VV101 Revenue - Inter Company
YA00 Variant Price VV101 Revenue - Inter Company
ZVC0 VC prices total VV101 Revenue - Inter Company

2
Functional Design Document
ZLIS List Price VV101 Revenue - Inter Company
ZPRC Special Price VV101 Revenue - Inter Company
Capture PriceRndng
ZPRA 1 VV101 Revenue - Inter Company
Capture PriceRndng
ZPRB 2 VV101 Revenue - Inter Company
Capture PriceRndng
ZPRD 3 VV101 Revenue - Inter Company
DIFF Rounding Off VV101 Revenue - Inter Company
ZDIS Price Code Discount VV101 Revenue - Inter Company
Z001 Customer + Material VV101 Revenue - Inter Company
Z011 Customer Discount VV101 Revenue - Inter Company
Z012 Volume Pricing Disc VV101 Revenue - Inter Company
ZCTR Contract Price VV101 Revenue - Inter Company

Output: (Functional description of the output)

Additional Comments: (Add any additional information necessary to assist in development as


needed)

Use Exit COPA005 is recommended for this kind of requirements.

Section III: Functional Test


Program: Test date:      
Developer:       Tel no:      

Description of the testing process


1. Create a Billing Document
2. Display Profitability Document to check proper value field assignment.

Team member responsible for testing: Krishna Pasumarthi

1. Test file(s) (optional):      

2. Is the program in line with the functional specification?


Yes No

If “Yes”, sign the form in the appropriate section below. If necessary, add some comments in the ‘General
comments’ section.
If “No”, describe the errors in the program here.
     

3
Functional Design Document
Developer responsible:

3. Describe the solution(s) :

4. New completion date:      

Comments after second test (if the program contained errors after first test):

Date:   /  /    

     

General comments:
     

Names and signatures:

_____________________________________________________________________________
Application consultant
Amit Amin
_____________________________________________________________________________
Developer

You might also like