Functional Specification Document (FSD)

Intercompany Output Type - PDF

Functional Specification Document Work stream: Intercompany Process owner: Ankur Chawla

Process name: Output Form Version: 002 Object ID: F_IC_001

Table of contents
1. General 3
1.1 Development Object details <Auto-populated by BOT based on Dev Object> 3
1.2 Cross-functional dependencies & application impacts 4
1.3 Change history 5
2. Functional design requirements 6
2.1 Requirements description 6
2.2 Functional design driver 6
2.3 Functional design process flow 6
2.4 General information 7
3. Functional specification 8
3.1 Interfaces 8
3.2 Enhancements 9
3.3 Conversions 12
3.4 Forms 16
3.5 Workflow 18
3.6 Reports 18
3.6.1 SAP ERP report 18
3.6.2 Analytical Report details ( BW,HANA,BI,3rd Party in-scope reporting tools) 20
4. Error handling 23
5. Security and controls 24
6. Change management and impacts 25
7. Testing 26
7.1 Environment /Configuration 26
7.2 Data requirements 26
7.3 Testing Scenarios & Steps 26
8. Open issues/items for follow up 27
9. Other considerations 27
10. Glossary of terms 29
11. Appendix and attachments 30
11.1 Appendix A: <Title> 30
11.2 Appendix B: <Title> 30
11.3 Appendix C: <Title> 30
1.

2 | Functional Design Document (FSD)

Functional Specification Document Work stream: Intercompany Process owner: Ankur Chawla

Process name: Output Form Version: 002 Object ID: F_IC_001

1. General
1.1 Development Object details
Dev Object ID: F_IC_001

Dev Object Name: Automation of Bill Rate File Prepration

( ) SLC ( ) STP ( ) RTR

Workstream:
(X) Tax ( ) Data ( ) R&A

( ) Report ( ) Interface ( ) Conversion ( ) Enhancement

Type of development
( X ) Form ( ) Workflow ( ) Tech Enablement

Linked Deviation Requirement

Linked Development Object

Attachments: ( ) No ( X ) Yes

Filename (s):

3 | Functional Design Document (FSD)

Functional Specification Document Work stream: Intercompany Process owner: Ankur Chawla

Process name: Output Form Version: 002 Object ID: F_IC_001

1.2 Cross-functional dependencies & application impacts

Functional area Systems impacted Comments
RTR - Record to Report Not Applicable Not Applicable

STP - Source To Pay Not Applicable Not Applicable

SLC - Study Lifecycle Not Applicable Not Applicable

R&A - Reporting & Analytics Not Applicable Not Applicable

TAX Functional Owner Functional Owner

DATA Not Applicable Not Applicable

TECH Development Required Development Required

4 | Functional Design Document (FSD)

Functional Specification Document Work stream: Intercompany Process owner: Ankur Chawla

Process name: Output Form Version: 002 Object ID: F_IC_001

1.3 Created By:

Version Creation Date Created By Description of process Status
V1.0 27/06/24 Ankur Chawla Intercompany Output Form

V2.0 01/08/24 Ankur Chawla VAT Registration Number

V3.0 02/09/24 Ankur Chawla Pending 3 forms

1.4 Change history

Date modified Modified by Description of change
01/08/24 Ankur Chawla VAT Registration Number

02/09/24 Ankur Chawla Pending 3 forms

5 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

2. Functional design requirements

2.1 Requirements description
Requirements description
As per the requirement for the output form addresses, we need to change the address logic for Service provider in the Intercompany
invoice output.

We also need to fix the logic for Service Recipient in the invoice output.

2.2 Functional design driver

Business driver and benefits

 Invoice template - ZMCKSDBIL_CI_PROF_SRV_US_INV

 Output triggers from the Billing document and correction required to fix the address mismatch.
 In case if DE10 is Service provider then system picks up the address from the company code data and when DE10 is
Service Recipient then system picks up the address from Business Partner data.
 In MCKC case there is difference in the BP address and Company code address for the same company and company as a
customer, this creates an issue.

2.3 Functional design process flow

Business process flow
 Sales order creation
 Billing document creation
 Output triggers in the Billing document.

2.4 General information

Related documents
NA

Assumptions/Constraints
<NA>

6 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

3. Functional specification
3.1 Interfaces: Not Applicable
(*) Marked items are mandatory

General interface information

* Technique :
( ) IDOC ( ) WebService ( ) RFC
( ) ABAP Proxy ( ) Others _____________

* Frequency ( ) Daily ( ) Weekly Other: <Explain>

* Type ( ) Real -Time ( ) Pseudo-real time ( ) Batch

* Direction of interface: ( ) Inbound ( ) Outbound ( ) Both

Interface Details <Source and Target Auto-populated by BOT that will copy from linked Dev Object.>
* Source Application details

* Target Application details

Process execution/initiation methods

* Transaction volume (number and size)

* Security parameters (encryption requirement)

* Execution frequency/schedule

* Error Handling Specifications

Recovery and Resubmission Process

* Critical Dependencies

Source/Target systems and interface diagram

<Describe the source of the information and target systems where the information is going. Include an interface diagram that shows
movement of data.>

Middleware
<Provide information on the middleware requirements(CPI/PI/Mulesoft).>

Dependencies/Prerequisites/Processing considerations
<Describe all dependencies and prerequisites for the interface. Describe all processing and operational considerations for the
interface including reconciliation requirements. Describe if this needs to be scheduled and executed at a certain time.>

7 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

Detailed description Related Documents

Legacy to SAP field requirements

<Identify the legacy system and field name and map it to an SAP field. Describe the interface rules.>

Legacy system/Field SAP S/4HANA Field Interface rules

Data Mapping File

<Use this template for updating the data mapping for interfaces>

A Complete data mapping file is mandatory for the interfaces.

Data Mapping File

3.2 Enhancements/Automation - Not Applicable

(*) Marked items are mandatory

General enhancement information

* Type of Enhancement: ( ) Enhancement ( ) User Exit ( ) Extension

( ) Function Module ( X ) BADI ( ) Other Description:

Transaction Code Automation for Pricing File Preparation in an upload format.

Automation description
NA

Data selection and parameters

NA

8 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

Dependencies/Prerequisites/Processing considerations
NA

Detailed Description Related Documents

Selection Screen

Selection Default values

Field name criteria/Parameters from-to Validation

Output Screen

Field name Description Comments

9 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

3.3 Conversions NA
(*) Marked items are mandatory

Data Input Information

Quality of Legacy Data <Good, Average, Poor>

Complexity of Legacy Data <Simple, Average, Complex, Very Complex>

Complexity of Manual Input <Simple, Average, Complex>

Number of screens <If applicable, input the number of SAP Screens to Input the Data>

* Data Volume

* Program Type
( ) Batch Input ( ) Direct Input ( ) IDOC ( ) LSMW

( ) Data Services ( ) BAPI ( ) Online Transaction

( ) CATT ( ) LTMC (Migration Cockpit)

( ) Other

Data Completeness <Good, Average, Poor>

Conversion Identification

Data Object(s) to Load <Object Details >

<Describe the conversion by stating the source and target systems.
Data Object Definition(s) Supply the SAP functionality required (including SAP field names,
SAP tables, processing logic, error handling logic, etc.). Include a
conversion diagram that shows movement of data including profiling,
cleansing, and staging steps.>

<Define the Data Owner. The Data owner is a role assigned to a

Data Object Business & Data Owners business representative or delegate that has overall responsibility for
the specific data object within the business/system. >

< How will the data be used>

Functional use of Data Objects within SAP

10 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

Additional background / considerations NA

Data conversion method (automatic, semi-automatic, manual)

Manual - All the steps until successful creation of input file is

manual

Semi-automatic - If data is filled into Standard Migration

cockpit template and uploaded to S4

Automatic - If Standard SAP data conversion program like

SAP Data Services is used.

Conversion process

<Describe the scope of data to be loaded. Mention the relevant

Data Scope source tables, columns and filter to be applied for example, list of
Plants, Legal Entities, Sales Org, Change date etc>

<Include historical data requirements, if any>

<Describe the source data. Include the source file format, system
* Data Sources source data resides in, required information to convert, current data
location and describe how the data will it be pulled into SAP.>

* Data volume

Key Enrichment Requirements

Major Transformation Requirements

11 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

Data Formatting / Naming Standards / Conventions

<Describe any known deficiencies in the legacy data that should be

Data Quality / Cleansing quantified as part of profiling (reference any data profiling documents
if necessary and their file location).>

<Describe all requirements for post-conversion deliverables (Data

Reconciliation reconciliation, validation, special data quality monitoring,
management requirements and assumptions).>

<Describe all dependencies and prerequisites for the conversion.

Dependencies Describe if this needs to be scheduled and executed at a certain
time. Describe all cutover assumptions.>

Conversion Data Flow Diagram

< Add data flow diagram for the conversion process, if any>

Input File

* Input File Name <Conversion File Name>

* Input File Type <File Type, XLS, TXT, etc>

* File Path <File Path if in Network>

* File Location <File Location if in Network>

Relevant SAP Tables

<Mention all the SAP tables required for the conversion>

Data Mapping
<Attach field mapping between legacy SAP fields & tables to S4 tables and fields. Mention data filter criteria,
transformations, substitutions etc as applicable >

Program Information
Program Name <Mention migration cockpit template, IDoc, BAPI or program name relevant for the conversion>

12 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

Transaction < Mention relevant t-code>

Field Mapping and Translation Requirements

<Insert any specifics around field mapping, such as mapping multiple fields into one field or splitting one field into
multiple fields. Include any field translation rules/details>

13 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

3.4 Forms – Applicable

(*) Marked items are mandatory

General form information

Type of the form Adobe

Development type
( ) Modification of Standard SAP Form

Name of Standard Form:

Driver Program (applicable in case of standard form)

( ) Custom Form Have you looked at possible standard Forms?

( X ) Yes ( ) No

Form path
VF03 – Display Output Requests

Data selection and validation

Take a document number belong to Customer (ICC**)

Special characteristics

Layout set

ZMCKSDBIL_CI_PROF_SRV_US_INV

Audience and distribution

<Describe if there are any distribution requirements. Who is the audience? Is the Form being distributed to a group via SharePoint or
Email? Describe requirements if any.>

Printing requirements

Modifications required in the existing form ZMCKSDBIL_CI_PROF_SRV_US_INV

Technical Logic: we have 2 requirements for form change, which are as follows:

14 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

1. First Requirement: Address change for Service Provider

Input parameter for the Output type is VBRK-VBELN.

We have 2 conditions for the address printout of Service Provider.
Condition 1 is where the “Plant” mentioned in the sales order has a “Business Place” assigned to it. If condition 1
meets the criteria then system will pick the address of the plant and will not enter in the logic of Condition 2.
Condition 2 is where “Plant” assigned to the sales order doesn’t have “Business Place” assigned to it, in that case
system will skip the logic for condition 1 and will pick the address data from condition 2.

Condition 1: We need to pick the address of plant where Business place is activated for the plant.
In this case, Pick VBRK-VBELN and Pass it in VBRP-VBELN and Pick VBRP-WERKS.
Use FM “VIEW_GET_DATA” in SE37 where View = J_1BT001WV.
Compare VBRP-WERKS in the FM and if system founds an entry in the FM for this VBRP-WERKS then use the
address logic as follows:
Pass VBRP-WERKS in T001W-WERKS and Pick T001W-ADRNR and Pass it in ADRC-ADRNR.
Pick all the fields as on date we are printing on the invoice.
In case if VBRP-WERKS is not available in the “VIEW_GET_DATA” then skip this logic and Pick the logic from
Condition 2 for the printing.

Condition 2:

Pick VBRK-BUKRS from VBRK-VBELN and Pass it in TVKO-VKORG and Pick TVKO-KUNNR.
Pass TVKO-KUNNR in KNA1-KUNNR and Pick KNA1-ADRNR and Pass KNA1-ADRNR in ADRC-ADRNR and Pick
the fields which we are printing as on date on the invoice.

Entity Name
Street
Street 2
Street 3
VAT Reg No: - From the above logic, check if the address is being picked based on Business Place or customer.
If the plant has a business place assigned to it then use CDS view PBUSINESSPLACE and Pass VBRK-BUKRS in
PBUSINESSPLACE-BUKRS and VBRP-WERKS – PBUSINESSPLACE-WERKS and Pick PBUSINESSPLACE-
GSTIN

If its from customer, then the logic will be

From KNA1 check fields KNA1-STCD1, KNA1-STCD2, KNA1-STCEG, KNA1-STCD3, KNA1-STCD4, KNA1-STCD5,
KNA1-STCD6
Value will be available only in one of these fields, Pick the value and show it in VAT number field.

2. Second Requirement: Address logic for Service Recipient

15 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

VBRK-VBELN Pick VBRK-KUNAG and Pass VBRK-KUNAG in KNA1-KUNAG and Pick KNA1-ADRNR and Pass
ADRC-ADRNR and Pick the same as provider.
Entity Name
Street
Street 2
Street 3
VAT Reg No:

Form 2: ZMCKSDBIL_INTERCOM_GPS_FORM
Screen shot and sample data available from the Dev 200 system.
Please ensure that it has the same logic of fields provided above in the ZMCKSDBIL_CI_PROF_SRV_US_INV for
service recipient.

Form 3: ZMCKSDBIL_CI_IC_BALNC_TRANSFER
Payee: use the logic of Service Recipient from the 1st Invoice

16 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

Payer: use the logic of Service Provider

Sample Data in SD1-200 – Invoice – 850100086

Form 4: ZMCKSDBILL_IC_GPS_CIG_FORM
Use logic from ZMCKSDBIL_CI_PROF_SRV_US_INV Form of Service Recipient
Sample Data: 850330052

17 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

3.5 Workflow NA
(*) Marked items are mandatory

General workflow information

<Insert the workflow diagram below. Describe the access method or path for the Workflow. >

Dependencies/Prerequisites/Processing considerations
<Describe all dependencies and prerequisites for the workflow. Describe if this needs to be scheduled and executed at a certain time.>

Detailed description Related documents

3.6 Reports NA
(*) Marked items are mandatory

3.6.1 SAP ERP report

Development type
( ) Modification of Standard SAP Report Name of Standard Report:

( ) Custom Report: No Standard available. Have you looked at possible standard Reports?

( ) Yes ( ) No

Report framework
<Provide the following key information as part of the reporting framework.>

Category Description Report details

Report Type High level purpose (Financial, Management, &
Regulatory)

Report Category High level business function (Capital Planning, Cost

Analysis, Planning & Forecasting, Variance Analysis, etc.)

Report Area/Line of Business Business Services TO/Corp, CEHE, CES, Financial

Planning, Gas, etc.

Business Process Defined activity to accomplish a task or goal for the

organization

18 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

Report Owner Point of escalation for a given report

Report Preparer Responsible for creating a given report

Business User Group Organizations or departments that use the report

(Business Services, Budget Coordinators, Board
Members, CES Billing, Gas Finance, etc.)

Priority Importance of a report to the business (Critical and

Required, High, Medium, Low, and Not Required but
Available)

Complexity What steps are involved and how much time does it take
to create (High, Medium, and Low)

* Frequency How often is a report created (Daily, Weekly, Quarterly,

Monthly, Annually, and Ad-Hoc)

Data Acquisition Method How required data is obtained (via email, GR55, monthly
report, etc.)

* Source System(s) What systems are used to access data (SAP, BW,
SharePoint, Excel, etc.)

* Key Data Elements Data required for a specific report (cost center, WBS
grouping, Internal Orders, Profit Centers, YTD Actuals,
etc.)

Report path
<Describe the access method or path for the report.>

Selection Screen
<Describe the selection screen for the report. Specify fields for selection and what checks are needed after the user had entered the
criteria.>

Selection Default values

Field name criteria/Parameters from-to Validation

Output Screen
<Describe the selection screen for the report. Specify fields for selection and what checks are needed after the user had entered the
criteria.>

Selection Default values

Field name criteria/Parameters from-to Validation

19 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

Data selection
<Describe the data selection for the report.>

Special characteristics
<Describe all special characteristics (totals, subtotals, etc.) for the report.>

Layout set
<Describe the layout set, header, footers, fonts, colors, theme, output type and print program for the report.>

Audience and distribution

<Describe if there are any distribution requirements. Who is the audience? Is the Report being distributed to a group via SharePoint
or Email? Describe requirements if any.>

Printing requirements
<Describe the printing requirements (paper type, etc.) for the Report.>

3.6.2 Analytical Report details ( BW,HANA,BI,3rd Party in-scope reporting tools)

General report information
Report Type <Describe Report Type such as Dashboard, Workbook, Analytical etc.>

Description <Report Description>

Brand Specific Requirements <Insert requirements specific to any Brand such as Lane>

Frequency of Update <Daily, Weekly, Monthly, etc>

Periods Reported <Daily, Weekly, Monthly, etc>

Reporting Dimensions <Insert Reporting Dimensions>

History Needed <Yes or No> If yes, how much?

Distribution and Output Type <Distribution Requirements>

Volume < Volume Requirements>

Special Printing/Media Requirements <Special Printing Needs, such as a specific printer or special printer size>

Special Font Requirements

Special Precision Requirements

20 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

Sort Criteria <Selection Options>

Mode of Execution <On Demand, Batch Job etc>

Paper size <Paper Size>

Page Orientation <Orientation>

Total <Totals, i.e Totals for Year>

KPIs <Insert Key Performance Indicators>

BW report user info

<Specify the user community who will be using this report>

User Community <Describe User Community>

Role/Function Est. # users Site/Location Key users Security needs

Report layout
<Describe the layout set, header, footers, fonts, colors, theme, output type and print program for the report.>

Formula Mapping
Formula name Description Formula Logic/Algorithm Source fields Additional comments

Field Mapping
Report field name Description Source object Source object field Additional comments

21 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

22 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

4. Error handling
Error handling


23 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

5. Security and controls TBD

Security, authorization, and controls
<Describe any security and authorization checks required. Also provide list of relevant controls.>

Will a separate transaction code be required? Yes – Separate program required.

Will access be restricted by organizational units? No

Will access be restricted by activity types? No

Will access be restricted by data items? Yes

List Roles Affected or New Roles Required: Existing Role

Is there a financial/SOX impact? No

Is there any impact to regulatory compliance? No

24 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

6. Change management and impacts

TBD
Change management and impacts
<Describe all change management considerations associated with implementing this object.>

Comment 1 –>

Comment 2 –>

Comment 3 –>

Comment 4 –>

25 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

7. Testing
7.1 Environment /Configuration
Environment/Configuration
Initial testing will be conducted in SD1 200 in S4 followed up by the UAT in SQ1-600

7.2 Data requirements

Data requirements
Material Master created under the first Sales Org and Plant

7.3 Testing Scenarios & Steps

Testing requirements
No Scenarios Name Scenario description Expected Outcome
1 Mckinsey Intercompany processes PDF output as per the logic

Test scenario : <Scenario Name>

Expected result : <Final Outcome>

26 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

Steps no Step Description

8. Open issues/items for follow up

Open issues/Items for follow up
<List any open issue or follow up actions required.>

Id Open issue/item description Assigned to Status

9. Other considerations
Software impact
<Indicate which software will be impacted by this development.>

Software impacted Software package

Legacy impacts

<Add any relevant legacy impacts here.>

<Comment 1 – >

<Comment 2 – >

<Comment 3 –>

<Comment 4 –>

Cutover items
<Add any items relevant to the cutover process here.>

<Comment 1 –>

<Comment 2 – >

<Comment 3 - >

27 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

<Comment 4 – >

28 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

10. Glossary of terms

Terms Definition
AR Accounts Receivable

29 | Functional Design Document (FSD)

Functional Specification Document Work stream: Data Process owner: Ankur Chawla

Process name: Bill Rate file Automation Version: 001 Object ID: A_DATA_001

11. Appendix and attachments

<List any necessary Appendix or Attachment materials.>

11.1 Appendix A: Company Code and Name file

11.2 Appendix B: <Title>

11.3 Appendix C: <Title>

30 | Functional Design Document (FSD)