Ref.Doc.

T-EIM-FS-001
Technical Specification Document
Page # : Page 1 of 11

Technical Specification Document

(Version 1.0)

Schedule Creation of Purchase Order(s) in

Background/Foreground Mode from Legacy Data
File (MM)

Prepared By : Vasshu Manglaa Approved By:

Date : 02-Oct-2018 Date :
 Ref.Doc. T-EIM-FS-001
Technical Specification Document
Page # : Page 2 of 11

Technical Specification Document Control

Document Owner

Function Name Signature

Project Consultant Vasshu Manglaa

Summary of Changes

Version # Version Date Nature of Change Revision Tag Date Approved

1.0 01-10-2018 Draft Of The Document

Document Change Approvers

Function Name Signature

Project Consultant Vasshu Manglaa

Document Approvals
Document approval for this document is maintained by document owner.
Document Review Plans
This document will be reviewed and updated, if necessary as defined below:
 As required to correct or enhance information content
 Following any organizational changes or restructuring
 Following an annual review
How to find the latest level of this document
The latest version of this document may be requested from the document owner.
Document Distribution
This document is automatically distributed to all change approvers and upon request.

Prepared By : Vasshu Manglaa Approved By:

Date : 02-Oct-2018 Date :
 Ref.Doc. T-EIM-FS-001
Technical Specification Document
Page # : Page 3 of 11

Technical Specification Development Requirement Form

Vendor Name EIM Solutions

Consultant Name Vasshu Manglaa

General Information
Call ID / Dev ID A0068
Program Name ZBAPI_CREATE_PO
Development Type (Report/BDC…) Report
T-Code ME21N
Module Material Management
Technical Lead Karthikeyan Venkatachalam

Technical/Business Analyst Parthasarathy N

Technical Developer Vasshu Manglaa
Program Completion Date 22-Sep-2018
Revised Program Completion Date 25-Sep-2018
Complexity (L/M/H) M
Priority (L/M/H) M
Run/Frequency Once A Day
Includes Used ZBAPI_CREATE_PO_F01
ZBAPI_CREATE_PO_TOP

Function Modules Used BAPI_PO_CREATE1

BAPI_TRANSACTION_COMMIT
DEQUEUE_ALL
OOPS Objects Used CL_GUI_FRONTEND_SERVICES
 FILE_OPEN_DIALOG
 GUI_UPLOAD
CL_SALV_TABLE
 FACTORY
 DISPLAY

Prepared By : Vasshu Manglaa Approved By:

Date : 02-Oct-2018 Date :
 Ref.Doc. T-EIM-FS-001
Technical Specification Document
Page # : Page 4 of 11

Table of Contents
TABLE OF CONTENTS…………………………………………………………………………………………………………………………………… 4
1 DEVELOPMENT OVERVIEW .................................................................. ERROR! BOOKMARK NOT DEFINED.
1.1 REQUIREMENTS SUMMARY............................................................................................................................ 5
1.2 OBJECTIVES ............................................................................................................................................... 6
1.3 ERROR HANDLING / MESSAGES ...................................................................................................................... 6

2 DETAILED TECHNICAL SPECIFICATIONS ................................................ ERROR! BOOKMARK NOT DEFINED.

2.1 TECHNICAL FLOW DIAGRAM .......................................................................................................................... 6
2.2 TECHNICAL FLOW DESCRIPTION ...................................................................................................................... 7

3 SAMPLE OUTPUT ..................................................................................................................................... 8

4 SAP TECHNICAL SPECIFICATION DEVELOPMENT REQUIREMENT FORM ................................................. 9

4.1 GENERAL ATTRIBUTES ................................................................................................................................ 9

Prepared By : Vasshu Manglaa Approved By:

Date : 02-Oct-2018 Date :
 Ref.Doc. T-EIM-FS-001
Technical Specification Document
Page # : Page 5 of 11

SAP Technical Specification Form

Call ID # A0068 Module Material Management

Date 02-Oct-2018 SL User N/A
Consultant Vasshu Manglaa Extension N/A

1. Development Overview

1.1 Requirements Summary:

We can create only one Purchase Order at a time using Transaction Code
ME21N, if any organization wants to create multiple Purchase Orders it will be
a troublesome and time consuming task. A more optimal and practical approach
for this requirement can be simplified by using a legacy flat file, populated by
suitable data entries for which the purchase order has to be generated.
Moreover, the creation of purchase order could also be scheduled foreground or
background totally depending upon the requirement of the client. This would
totally eliminate the long time consuming task and also aid users to schedule the
creation of purchase orders according to their choice.

1.2 Objectives:
The requirement mentioned above can simply be achieved by using a Report
Program which can be used to create multiple Purchase Orders using a data
source from legacy flat file typically in (.CSV/.XLS) format. Further user can
directly select and upload data source file from their legacy system directory
and schedule the process in foreground mode or background mode, as such
functionality is embedded for the convenience of the user.

SAP Standard BAPI (Business Application Programming Interface) named

‘BAPI_PO_CREATE1’ has been implemented which enables users to create
purchase orders. This BAPI uses the technology behind the Enjoy Purchase
Order Transaction (ME21N). A detailed explanation about this BAPI has been
explained later in the document.

Prepared By : Vasshu Manglaa Approved By:

Date : 02-Oct-2018 Date :
 Ref.Doc. T-EIM-FS-001
Technical Specification Document
Page # : Page 6 of 11

1.3 Error Handling / Messages:

A Standard and Sophisticated Error Handling has been implemented to leverage
user experience while creating Purchase Orders. Once a Purchase Order(s) is/are
created successfully user will be able to identify the same as all the messages are
displayed in a tabular format on the screen. However, due to any internal or
external reason if any Purchase Order(s) is/are not created user will also be able
to see and identify whether a purchase order has been created successfully or not
and what is the underlying reason for that. Sample screenshots for the same has
been attached later in the document.

2. Detailed Technical Specification

2.1 Technical Flow Diagram:

Error
Select After
Execute Handling
Foreground / Validating
Background Select Legacy Report Tabular
Input, F4
Mode To Data Source Information
Help Will Be Purchase
Create File Using F4 Is Generated
Enabled To Order(s)
Purchase Help Request Consisting Of
Select The Created
Orders File Status
Messages

Prepared By : Vasshu Manglaa Approved By:

Date : 02-Oct-2018 Date :
 Ref.Doc. T-EIM-FS-001
Technical Specification Document
Page # : Page 7 of 11

2.2 Technical Flow Description:

Before executing the Report Program, User has to schedule whether the
program will be executed in Foreground or Background. Based on the input
received F4 Help for that mode would be activated enabling the user to select
the file from Legacy System. After selecting the file, when user executes the
report program,
The data from legacy file will be uploaded to R3 System and after further
validation data will be passed to BAPI.

SAP Standard BAPI ‘BAPI_PO_CREATE1’ has following mandatory

authorization objects which are checked when a purchase order is created
BSART (Document Type in PO)
EKGRP (Purchasing group in PO)
EKORG (Purchasing Organization in PO)
WERK (Plant in PO)
Further Header Data and Line Item Data is transferred to BAPI Import
Parameters POHEADER and POITEM respectively. After validating the data,
BAPI Exports the Purchase Order Number of BSART Type ‘NB’ and It also
Exports RETURN Parameter containing the status of the process. Moreover,
due to any case if validation of data is failed BAPI Exports Messages about
why the Purchase Order could not be generated in Parameters RETURN, which
is directly shown in a tabular format to inform the user about the status of
Purchase Order(s).An efficient Error Handling has been implemented to
leverage the user experience while creating Purchase Orders.

Prepared By : Vasshu Manglaa Approved By:

Date : 02-Oct-2018 Date :
 Ref.Doc. T-EIM-FS-001
Technical Specification Document
Page # : Page 8 of 11

3. Sample Output
Data Source Flat File (.CSV/.XLS) Format.

Report Program Selection Screen.

Prepared By : Vasshu Manglaa Approved By:

Date : 02-Oct-2018 Date :
 Ref.Doc. T-EIM-FS-001
Technical Specification Document
Page # : Page 9 of 11

Select File From Application Server Directory Using F4 Search Help.

(Can Also Be Scheduled As A Background Job Using SM36.)

Note: Process Is Same For Foreground Mode Also.

After Selecting The Desired File Click On Execute Button.

Prepared By : Vasshu Manglaa Approved By:

Date : 02-Oct-2018 Date :
 Ref.Doc. T-EIM-FS-001
Technical Specification Document
Page # : Page 10 of 11

Displays Purchase Order Creation Status On Screen In A Tabular Format

In Any Case If Purchase Order Could Not Be Generated, A Screen Stating

Possible Error Conditions Will Be Displayed In A Tabular Format.

Prepared By : Vasshu Manglaa Approved By:

Date : 02-Oct-2018 Date :
 Ref.Doc. T-EIM-FS-001
Technical Specification Document
Page # : Page 11 of 11

4. SAP Technical Specification Development Requirement Form

4.1 General Attributes

Description Remarks
Any Modification Of Existing SAP Logic/Name N/A
Of SAP-Provided Layout Set Copied
IMG Path For Customisation N/A
SAP Main Menu Path For Printing Report : N/A
Name Of SAP-Provided Layout (if any) And N/A
Program Where It Belongs :
Print Options Print To Printer N/A
Print Options Print To File N/A
Field Validations Yes
Radio Groups / Check Boxes Yes
Report fields Further Added Report Values N/A
Sort Options N/A
Scheduling Requirements Of The Report N/A
Depending On The Volume Of Data

Technical Consultant : Vasshu Manglaa

Date : 02-Oct-2018

Prepared By : Vasshu Manglaa Approved By:

Date : 02-Oct-2018 Date :