Technical Spec R15

7/30/2019 Technical Spec R15

http://slidepdf.com/reader/full/technical-spec-r15 1/11

Technical Specification

Version: 00

Specification No :

Eg: FS-FI-AP-CHK-001

Business Process No. :

Issue Date(dd/mm/yyyy):

04/10/2012

In Preparation Review

Approved Released

Revision History

Version Date Description of changes

00 04/10/2012 ZMASSUPLOAD

Responsible

For concept – Mass Upload of GLpostings

For Implementation –SAP FI

Section I: Justification

Area (R/3

Module):

FI Date

(dd/mm/yyyy):

10/4/2012

Requested by: R15 Team

Brief description: ZMASSUPLOAD Transaction

Generic question:

1. Impact of not creating the

program:

Legal requirements will not be fulfilled

Lack of information required for the business

Lose functionality compared to the old system

Others:

Is there any alternative in the standard

system:

Yes No

Describe the alternative found: ZMASSUPLOAD trasaction to post GL accounts

Reason why this alternative was not

acceptable:

(Explain in brief)

Performance problems Complexity

Others:

Explanation:

Program type: Report Module Pool Interface

Enhancement Conversion Form

Application Development Others

Priority: High/mandatory Medium/recommended Low/optional



Charateristics Drill Down ALV Others

Frequency: Daily Weekly Monthly

Biweekly Other: Transaction based

Only for Interfaces: Not applicable

Type of interface:

Direction of interface:

Real-Time Batch

Inbound Outbound Both

Sign off – Functional Specification

Prepared By

Date

R15 Team Comments

Team Lead

Date

Nitin GuptaLead Consultant

Date

Approved by Project Management Team

(in case of Application development)

/ /

Received Team Lead/ Lead Consultant

Date

/ /

Sign-Off and Acceptance of developed objectNames and Signatures

_______________________________________________________________________________________

Core Team

_______________________________________________________________________________________

Lead Consultant / Consultant



Section II: (a) Business Needs & Requirement (Please use this section for describing

the business requirement in detail preferably with flow diagram)

Description and Purpose :

For mass upload of Journal entries Z Program is required. Maximum line items will be 999

Business Process Detail :

User will browse the file from desktop and upload in in SAP and SAP will post the entriesautomatically.



Section III: Only For Reports/Forms

Selection Criteria (Input Screen)

Name Table Field/Check box/

Radio button

Comments(Single/Multiple

Selection, Mandatoryetc.)

Default Value

(REQUIRED Y/N)

Table & Field Name

ITEMNO_AC

C y

GL_ACCOUNT Y

COMP_CODE Y

PSTNG_DATE Y

DOC_TYPE Y

AC_DOC_N

O N

FISC_YEAR Y

FIS_PERIOD Y

STAT_CON N

CUSTOMER Y

VENDOR_NO Y

ALLOC_NM

BR YITEM_TEXT N

BUS_AREA y

COSTCENTER Y

ACTTYPE N

ORDERID y

ORIG_GRO

UP NCOST_OBJ N



Name Table Field/

Check box/Radio button

Comments(Single/Multiple

Selection, Mandatory

etc.)

Default Value

(REQUIRED Y/N)

Table & Field Name

PROFIT_CTR y

PART_PRCTR N

WBS_ELEMENT y

NETWORK Y

ROUTING_N

O N

ORDER_ITNO N

ACTIVITY N

PLANT N

SALES_ORD Y

S_ORD_ITEM Y

SEGMENT N

PARTNER_SEGMENT N

ITEMNO_ACC N

CURR_TYPE N

CURRENCY Y

CURRENCY _ISO N

AMT_DOCCUR Y

EXCH_RATE Y

EXCH_RATE _V N

Selection Logic



Process Logic

Transaction F-02

Document Date – dynamic

Posting Date - dynamic

Company Code – dynamic

Currency – dynamic

Document type – dynamic

Posting period – dynamic

Fiscal year - dynamic

Posting keys – 40 for DEBIT and 50 for CREDIT

GL account – dynamic

Cost center – dynamic



Report/Form Layout (Attach format if required)

Sample Sheet

Section III: Only For Interface/ Conversion

Tables

involved:

SAP Input Screen (Data Mapping)

Transaction:

Screennumber

R/3 Screen fieldname

Legacy field Remarks

Process Logic



Section III: Only for module Pool

Screen Layout: (attach details of screen layout)

Screen1

Screen Field Mapping:

Field Field Description SAP Reference Field Mandatory/Optional

Default values

Process Logic

Section III: Only For Enhancements

Name Description

Process Logic



Section IV : Test Case and Test Related

Result specificationFormat No/ Rev: TC-ABAP-001/ 00

Number: FS-FI-AP-CHK-001 (TC-XXX-YYY-

999)

Prepared on :

Test Cases (with expected results)

When user upload the file with all details the document number should be posted in SAP and should bevisible in tcode FB03. Documeny type SA

Checks performed Details about the test

Test sequence and test results Sequence in which the test would be performed.

Expected Result

Section I: Unit Testing

Program name: Test date: / /

Developer name:

Team Members

(Functional)

Responsible functional team member for testing:

1. File(s) used for test (optional):

2. Does the program comply with the functional specification ?

Yes No

Note: If the program is OK just sign the form. If necessary include some comments in the appropriate section.

3. If the answer to question 2 is "No" please describe the problems that were found in the program.

Sign off after testing

Team Lead

Date

/ /

Lead Consultant

Date

/ /

Sign-Off and Acceptance of developed object



Names and Signatures

_______________________________________________________________________________________

Team Lead

_______________________________________________________________________________________

Lead Consultant

Technical Spec R15

Documents

Transcript of Technical Spec R15