FUNCTIONAL DESIGN

ZMD04 Report
PROJECT IDENTIFICATION

Project Name Development ID

<KC1>

Customer Name
<KC1>

Konecranes AMS-Logistic Manager Konecranes Core team- Configuration Owner

< Hiren Ramani> <Anna Lihvoinen >

Approvals

Konecranes AMS- Logistics Konecranes Core Team

Signature: Signature:

Name: Hiren Ramani Name: Anna Lihvoinen

Title: Asst Manager Logistics Title: Configuration Owner Purchasing

Date: 07/09/2016 Date: 07/09/2016

Author Document Location (repository/path/name)

<Shridhar Kumbhar> <H:\Private\IT\SAP_AMS\>
Version Status Date (YYYY-MM-DD) Document Classification
0.1 Initial <2016/09/07> Confidential
DOCUMENT VERSION HISTORY

Version No Version Date Author Summary of Changes

0.1 07/09/2016 Shridhar Kumbhar Report creation(ZMD04) to remove MD04
report anamolies due to EKES table
inconsistencies by using BAPI PO_Change
Routine modification with FM
ME_CONFIRMATION_REDISTR_ITEMS
TABLE OF CONTENT

Article I. Purpose of this document.....................................................................................................4

Article II. General Object Overview.....................................................................................................5

Section 2.01 Process Requirements Reference..................................................................5

Section 2.02 Generic WRICEF Descriptions....................................................................6

Article III. Object Specific Design..........................................................................................................8

Section 3.01 Reporting (operational and analytical).......................................................8

Section 3.02 Interfaces........................................................................................................12

Section 3.03 Data Conversion / Historical Data............................................................14

Section 3.04 Enhancements...............................................................................................16

Section 3.05 Output (e.g. forms).......................................................................................17

Section 3.06 Workflow.......................................................................................................19

Article IV. Test Conditions.....................................................................................................................20

Article I. Purpose of this document

The Specification is the basis for the developments that will be done by Fujitsu. Funai has to verify and approve it
formally. Realization starts only after approval.

Within the SAP Custom Development Methodology, the Specification is the link between the business requirements
(normally given in the solution proposal) and the technical design (a separate document). It has the following goals:
Reference to the business requirements (customer requirements) given in the solution proposal.
Show the mapping into standard SAP products.
Describe the solution from an external (user or customer) point of view.
Implementation details (database model, report names, and so on) are generally NOT part of the Specification.
[Customers shall be enabled to recognize that all their requirements are taken into consideration. For approval of the
Specification they have to understand the solution.
Article II. General Object Overview

Object Overview

INC0566563 Business MD04 report

Incident ID
Process

ECC 6.0 SAP SAP MM, ABAP

SAP Release
Module
( X) Report
( ) Interface
( ) Conversion
Object Type ( ) Enhancement
( ) Form
( ) Workflow

Object Title ZMD04

Object Description ZMD04 Report

Mock Up ID / Name Not Applicable

Required
Cycle of Testing / C2 Development
Sprint Cycle
Completion Date

Complexity of Object Medium Priority Medium

Not calling interface Frequency of Not Applicable

Type of interface
Interface
BAPI PO_CHANGE
SAP Transaction SAP Program FM
MD04
Name Name ME_CONFIRMATION_REDI
STR_ITEMS
Similar SAP Not Applicable Similar SAP Not Applicable
Transaction Program

FS CONTROL

Functional Consultant Mr. Shridhar Kumbhar

Author and Phone
Number +91-9881000918

Planned Date of FS 07/09/2016 Actual Date of FS DDMONYY

Completion Completion

FS Approved By FS Approval date DDMONYY

Other Contact
Other Contact and
and Phone
Phone Number
Number
Section II.1 Process Requirements Reference
Process Reference
Incident ID INC0566563
Requirement Report creation (ZMD04) to remove MD04 report anamolies due to EKES
Description table inconsistencies by using BAPI PO_Change Routine modification with
FM ME_CONFIRMATION_REDISTR_ITEMS.
Gap to be addressed Standard SAP does not have this functionality
Alternative SAP Not available
Standard Solution

Section II.2 Generic WRICEF Descriptions

Justification

1. Business requirement to remove inconsistencies from MD04 Report due to EKES faulty entries by
creating ZMD04 Report.

FUNCTIONAL DESCRIPTION / DESIGN

Scenario :-
Purchase order creation updating MD04 report with POitem after getting delivery date
confirmation MD04 report changing this to ShpngNtfn but due to EKES table getting updated with
faulty entries currently user getting POitem & ShpngNtfn for same purchase order in MD04
report which is creting ambiguity to user while reading this report.

T RANSACTION VOLUME
10 to 15 purchase order per week

FREQUENCY & T IMING

Daily Activity

DEPENDENCIES
If this type of situation arises then Material requirement planning will face issue as requirement is not correct by
all means while watching MD04 report

AUTHORIZATION REQUIREMENTS

RELATED DOCUMENTATION (ATTACH OSS NOTES, EMAILS, DOWNLOAD OF EXISTING

REPORT, ETC)
Not Applicable
Article III. Object Specific Design

Section III.1 Reporting (operational and analytical)

Reporting
WRICEF Description Report Type Data Elements Relevant KPI Owner
-ID (ABAP, BI,
BOBJ)

Selection Criteria
Input Plant - EK

Functional Design, Validation and Variants

Function module "ME_CONFIRMATION_UPDATE" work well, The problem is in the table XEKES, this need to fill
the data XEKES-KZDIS with 'X'.

If data XEKES-KZDIS = 'X', The system will be update the transacion MD04.

Report Output

Output Method
Not Applicable

Main Heading
Not Applicable

Sub Heading
Not Applicable

DRILLDOWN REQUIREMENTS
Not Applicable

TOTALING
Not Applicable

SORTING
Not Applicable

PAGE BREAK
Not Applicable

ERROR HANDLING
Not Applicable
Section III.2 Interfaces

Interface
WRIC Description Interface Applications Data Elements Frequency / Owner
EF-ID Method Volumes

Interface Process Flow Diagram, incl.Transfer Method/ Network Integration

Not Applicable

File Specifics
Not Applicable

MAPPING SAP FIELDS TO SOURCE / TARGET

Not Applicable

RECONCILIATION PROCEDURES & AUDIT REQUIREMENTS

(a) Reporting

(b) Approach

(c) Metrics

(d) Error Handling

Section III.3 Data Conversion / Historical Data

Conversions
WWRIC Conversion Source Conversion Conversion # of Objects Owner
EF-ID Object Activities Method to be
(e.g. (manual / converted
cleansing) automated)

1MAPPING SAP FIELDS TO SOURCE / TARGET

Not Applicable

RECONCILIATION PROCEDURES & AUDIT REQUIREMENTS

(a) Reporting

(b) Approach

(c) Metrics

(d) Error Handling

Section III.4 Enhancements

enhancements
WRIC Description Data Object Functional Alternative SAP Reason Owner
EF-ID (Sales Order) Gap Standard
NLP Sales order Not Not Applicable Automatic Fujitsu
automatic Applicable functionality
functionality

Functional Design / Flow, Validation and Variants

(a) Flow

Creation of Sales Create Outbound Create Billing

order (T.code Delivery (T.code Document (T.code
VA01) VL01N) VF01)

(b) Design
Scenario1:
If the user enters ZNLP condition manually in conditions tab at sales order(ZOR) item level then
ZPRO condition amount should get derived automatically based on the below mentioned formula

FORMULA: ZPRO = ZNLP condition value (KWERT)*100/[100+ {[TAX (VAT or CST amount)]} ]

Eg: ZNLP amount =10000/EA

Order Quantity =5
ZVAT (TAX) =12.5%

Then Condition value of ZNLP (KWERT)= 50000

As per the formula ZPRO =50000*100/12.5+100= 44444.44 (Condition value (KWERT) for total
quantity)

Total value (KWERT) of ZPRO = 44444.44

The ZPRO/EA value (KBETR) = 44444.44(KWERT of ZPRO)/5(order quantity)

ZPRO/EA=8888.88(KBETR)

Need to use the following structures to get the values

KOMV ZNLP and ZPRO
KONP-ZVAT and ZCST [TAX conditions]

Scenario2:
If the ZNLP value is deriving through condition record (VK11)
The formula will be the same scenario1 as mentioned above to get the ZPRO condition amount.
Also need to redetermine the pricing as Gusing the below mentioned exit.

USEREXIT_NEW_PRICING_VBKD CHANGING NEW_PRICING.

Rounding off of TAX amount will be taken care through configuration only.
Functional changes:
Set rounding rule asA (Rounding Up) for ZVAT & ZCST condition types.
Assigning formula(601) to calculation type field against ZPRO condition type in pricing procedure
ZVA001
Please find attachment

NLP_Pricicng
Conditions.docx
Section III.5 Output (e.g. forms)

Output
WRIC Description Data Object Output Type Frequency Volumes Owner
EF-ID (Sales (Form, EDI, etc.)
Order)

Selection Criteria
Not Applicable

Process Flow Diagram

Not Applicable

Form Layout

LAYOUT
SL # Table/Structure Field Format Defaul Column Translation Rule
Name Name (ie decimal t Value Name
places)

Desired output is as below:

Printer Requirements
Not Applicable
Legal Requirements
Not Applicable

Existing Sample Forms

Not Applicable

Section III.6 Workflow

Workflow
WRIC Description Business / Data Object (Sales Engaged Parties Owner
EF-ID Order)
XX-xx-
W001

Process Flow Diagram

Not Applicable

Trigger Events
(a) Transactions and Batch Programs that trigger the workflow

(b) Start Conditions

Rules and Determination

(c) Standard Rules

(d) Latest End, Latest Start

Article IV. Test Conditions
BUSINESS TEST CONDITIONS (TO BE FURNISHED BY THE FUNCTIONAL CONSULTANT)

Scenario# Test scenario

1 Order to Cash with 1 line item (VAT) by entering ZNLP condition
manually

2 Order to Cash with 1 line item (CST) by enteringZNLP condition

manually

3 Order to Cash with multiple line items(VAT) by enteringZNLP

condition manually

4 Order to Cash with multiple line items(CST) by enteringZNLP

condition manually

5 Order to Cash with multiple lie items(VAT different ratios) by

enteringZNLP condition manually

6
Order to Cash with 1 line item (VAT) (with automatic ZNLP price)

7
Order to Cash with 1 line item (CST) (with automatic ZNLP price)

8 Order to Cash with multiple line items(VAT) (with automatic ZNLP

price)

9 Order to Cash with multiple line items(CST) (with automatic ZNLP

price)

10 Order to Cash with multiple line items(VAT different ratios)(with

automatic ZNLP price)

Order to Cash with 1 line item (VAT) (first entering the ZNLP
11
condition manually bat bottom then prcie entering at bottom
against the same condition)

Order to Cash with 1 line item (CST) (first entering the ZNLP
12 condition manually bat bottom then prcie entering at bottom
against the same condition) by enteringZNLP condition then price
at top

Order to Cash with multiple lie items(VAT) (first entering the ZNLP
13
condition manually bat bottom then prcie entering at bottom
against the same condition) by enteringZNLP condition manually

Order to Cash with multiple lie items(CST) (first entering the ZNLP
14 condition manually bat bottom then prcie entering at bottom
against the same condition) by enteringZNLP condition manually
Order to Cash with multiple lie items(VAT different ratios)(first
15 entering the ZNLP condition manually bat bottom then prcie
entering at bottom against the same condition) by enteringZNLP
condition manually