ATC Functional & Technical Specification

Work Center in componenets

Version: 1.0 Date: 24.01.2012

Ticket No:

7000000052

1.0

Basic Information0

Priority Date Needed Development Labor Estimate SAP Module Resources (if applicable) Developer(s) Document Contact Voice Mail e-Mail Address

Very High ASAP 3 days CS modules Subhash,Kalyan.

2.0

Table of Contents 3.0 Functional Specification Details (Functional Team) 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 4.0 4.1 4.2 4.3 4.4 4.5 4.6 Business Requirement Process Area SAP Module (if applicable) Data Requirements Additional Features Assumptions Alternatives Dependencies Training Requirements Technical Overview New Tables/Structures/EDI Segments New Data Elements New Domains Development Objects, etc. New Screens
Last Changed By: Sitaraman Page 1 of 8

Technical Specification Details (Technical Team)

Last Changed On: 2/13/2012

ATC Functional & Technical Specification

Work Center in componenets
Version: 1.0 Date: 24.01.2012

Ticket No: 5.0

7000000052 Technical Specification Details (Systems Engineering) 5.1 5.2 5.3 Technical Overview Component/Static Structure Diagrams Sequence Diagrams Unit Test Procedures Installation Procedures Integration Test Procedures

6.0

Testing Procedures 6.1 6.2 6.3

7.0 3.0

Issues or Concerns (Function & Technical Team)

Functional Specification Details (Functional Team)0

Customer Requirement as mentioned in the Ticket No. 7000000115 : During cash sales, there should be option to update mode of payment i.e.manually enters Credit card number,type i,e KNET payment card.

3.1

Business Requirement0

Customer Requirement as mentioned in the Ticket No. 7000000115 : The addition of Knet card type is a manual entry which is required by end user at the time of creating rush order.

There is no need to check the authenticity of the card.

3.2

Process Area SAP Module 0 SD/ LE

3.3

Data Requirements0
TVCIN- CCINS VCNUM -CCINS,CNUMS

Last Changed On: 2/13/2012

Last Changed By: Sitaraman

Page 2 of 8

ATC Functional & Technical Specification

Work Center in componenets
Version: 1.0 Date: 24.01.2012

Ticket No: 3.4

7000000052

Additional Features0

3.5

Assumptions0 NA

3.6 3.7

Alternatives0 Dependencies0 NA

3.8

Training Requirements0 NA

4.0

Technical Specification Details (Technical Team) Program: SAPMM07R Transaction: MB21

4.2

New Tables/Structures/EDI Segments0

Table Name:Nil Key Field Name Data Element Description Check Table Type Length

4.3

New Data Elements0 Description Domain

Data Element

Last Changed On: 2/13/2012

Last Changed By: Sitaraman

Page 3 of 8

ATC Functional & Technical Specification

Work Center in componenets
Version: 1.0 Date: 24.01.2012

Ticket No:

7000000052

4.4

New Domains Description Type Length Fixed Values

Domain

4.5

Development Objectives, etc.0

Z_GOODSRECIPIENT_MB21
data:wempf. import wempf from MEMORY ID 'WEMPF'. if wempf IS NOT INITIAL. CLEAR RKPF-WEMPF. endif. Data : fields type table of DYNPREAD with header line, v_wempf type wempf, wempf type char1, flag type c. case sy-ucomm. when 'BU'. fields-fieldname = 'RKPF-WEMPF'. append fields. *To fetch the screen field values to validate CALL FUNCTION 'DYNP_VALUES_READ' EXPORTING dyname = sy-repid dynumb = sy-dynnr tables dynpfields = fields EXCEPTIONS INVALID_ABAPWORKAREA =1 INVALID_DYNPROFIELD =2 INVALID_DYNPRONAME =3 INVALID_DYNPRONUMMER =4 INVALID_REQUEST =5 NO_FIELDDESCRIPTION =6
Last Changed On: 2/13/2012 Last Changed By: Sitaraman Page 4 of 8

ATC Functional & Technical Specification

Work Center in componenets
Version: 1.0 Date: 24.01.2012

Ticket No:

7000000052

INVALID_PARAMETER =7 UNDEFIND_ERROR =8 DOUBLE_CONVERSION =9 STEPL_NOT_FOUND = 10 OTHERS = 11 . IF sy-subrc <> 0. * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. ENDIF. *Based upon the screen value, validating the field value with the entry in the table ZWEMPF select single wempf into v_wempf from zwempf where wempf = fields-FIELDVALUE. if sy-subrc ne 0. flag = 'X'. ENDIF. *To display the error message if the entry not found in the table ZWEMPF if flag eq 'X'. message E017(ZCS_MSG). ENDIF. endcase. *** data: o_value type RKPF-WEMPF, i_value type DYNPREAD-FIELDVALUE. clear o_value. CALL FUNCTION 'GET_DYNP_VALUE' EXPORTING i_field = 'RKPF-WEMPF' i_repid = sy-repid i_dynnr = sy-dynnr changing o_value = o_value. if o_value is NOT INITIAL . clear flag. *Based upon the screen value, validating the field value with the entry in the table ZWEMPF select single wempf into v_wempf from zwempf where wempf = o_value. if sy-subrc ne 0. clear:RKPF-WEMPF,o_value. set CURSOR FIELD RKPF-WEMPF. MESSAGE I017(zcs_msg) DISPLAY LIKE 'E'. wempf = 'X'. export wempf to memory id 'WEMPF'. else. clear wempf . export wempf to memory id 'WEMPF'. ENDIF. endif.

Last Changed On: 2/13/2012

Last Changed By: Sitaraman

Page 5 of 8

ATC Functional & Technical Specification

Work Center in componenets
Version: 1.0 Date: 24.01.2012

Ticket No: 4.6

7000000052

New Screens0

Detail new screen design here: No new Screen Transaction: Program: Screen: Program Screen Field OK Code Description Required OK Code: Next Screen:

5.0

Technical Specification Details (Systems Engineering)0

5.1

Technical Overview0 Briefly describe the breadth of the development project (systems and technologies involved and why). The project should be divided into subsystems and explained here (as well as shown in the Package Diagram). This section should include a Package Diagram and Use Case/Activity Diagrams (if necessary).

5.2

Component/Static Structure Diagrams0 This section should include Component Diagrams with a brief explanation of purpose and any key points.

5.3

Sequence Diagrams This section should include Sequence Diagrams with a brief explanation of purpose/process and any key points.

6.0

Testing Procedures (Technical Team)

Last Changed On: 2/13/2012

Last Changed By: Sitaraman

Page 6 of 8

ATC Functional & Technical Specification

Work Center in componenets
Version: 1.0 Date: 24.01.2012

Ticket No: 6.1

7000000052

Unit Test Procedures

6.2

Installation Procedures0 Describe how to install the application.

6.3

Integration Test Procedures Describe how to integration test this program.

7.0 7.1

Issues or Concerns (Functional & Technical Team)0 Unit Test Procedures0 This section should contain a matrix which will track all issues and resolution related to this development.

# 1 2

Date Created/Resolved

People

Issue/Resolution

Last Changed On: 2/13/2012

Last Changed By: Sitaraman

Page 7 of 8

ATC Functional & Technical Specification

Work Center in componenets
Version: 1.0 Date: 24.01.2012

Ticket No:

7000000052

Section No.
All

Describe Change

Date

Revision History

Author Department

REQUIRED APPROVAL
Chairman of the Board President CFO Legal

Approval Date

ADDITIONAL APPROVAL

Approval Date

Last Changed On: 2/13/2012

Last Changed By: Sitaraman

Page 8 of 8