Development Request

Date of
Short Case
LSMW for Purchase Order creation Request
Description
16. June 2008
Name of Require Date
Greg Derick
Requester asap
High
Request
Greg Derick Priority Medium
Owner
Low
Responsible Customizing Yes
Puneeta Singh
Module Expert Required No
Business
Process ID
Authority-
Pre Go-Live Yes
Request Type Enhancement Checks
Post Go-Live No
Problem Req.
Execution Online periodic Transaction
Requirements Batch one time job code
Global
Dialog Interface Scope
Program Type Divisional
Report DataConversion Unit
Local

1. Estimated Effort (in hours or man-days)

Developer ExpertModule

Design and
Specification:

Development:

Testing:

Total time:
Note:

19.09.2017 Page 1 of 5
2. Request Approved
Module Expert

Prepare Functional Spec

Recommen-
Remarks
dation from Dont prepare Functional
Spec

Escalate Approval
Yes Yes
decision to obtained from
Remarks
Project Validation
No
Management Committee
No

Name and
Request Approved Yes No
Signature

19.09.2017 Page 2 of 5
3. Functional Specification

Specification

Introduction
At the LAX unit, the Purchasing activity for the unit is outsourced to Pourshins.
Pourshins will use their own system and send a pre-advisory to the unit. The
pre-advisory file will be used as the input file for PO creation in SAP.

Process

For the LAX unit plant 1023, all purchasing activity will be undertaken by
Pourshins. Pourshins will provide a pre-advisory to the unit which is treated as
the purchase orders.
A PO must be created in SAP for recording goods receipt and invoicing in the
SAP system. The pre-advisory file will be used for PO creation. The file would
be processed by Pourshins employees on the SAP LSMW tool. The file would be
read and the POs created based on the design below.
If there are any fallouts or errors, an error file would be created. Once the errors
are corrected, this file could be run to create Pos for those records.

Assumptions

1. Separate pre-advisory file will be sent by Pourshins for Airline owned

product and Gate group owned product. Only the one containing the Gate
group products will be used to create POs.
2. This interface is for PO create only. PO changes will NOT be supported.
Any changes, fixes will have to be processed manually.
3. Material number, order quantity, order unit, delivery date are the core fields
to be read from the input file. The Purchase order price and order unit to
base unit conversion will be considered from the one stored in SAP. This
serves as a control measure to ensure that valid pricing is used on the
POs.
4. Authorization access will be provided to Pourshins employees into SAP to
conduct this process.
5. Purchasing inforecords will be created by the GG data group for Pourshins
in SAP for all GG products supplied by this vendor.
6. Unit of measures will be mapped offline between Gate group SAP and
Pourshins to ensure that there is no mismatch.

19.09.2017 Page 3 of 5
 7. SAP material numbers must be sent to Pourshins to map SAP material
numbers to Pourshins material numbers.
8. SAP vendor number must be sent to Pourshins.
9. This interface does not cover non-inventory/account assigned PO
creation.

Design details

The metadata file SAP PO create

FIELD NAME DESCRIPTION FORMAT

SUPPLIER GG SAP vendor number Varchar2(10)
ORDERNO Pourshins Sales Order Varchar2(10)
Number
LINE Pourshins order number line Number(10)
DDATE Delivery Date Date suggest standardizing
on YYYYMMDD format
CUSTOMER_REFERENCE Vendor reference number Varchar2(20)

POURSHINS_CODE Pourshins Part code Varchar2(15)

SAP_NUM GG SAP material number Varchar2(18)
DESCRIPTION Product Description Varchar2(25)

SALES_PRICE Sales Price Number (20,4)

UNIT_PRICE Will either be same as Varchar2(4)
order_qty unit (gen CASE) or
weight uom (LBS in the US,
KG outside US) if
catchweight
ORDERS Order Qty Number(20,6)
DELIVERY Expected delivery Qty. Number(20,6)

The input file would be enhanced to include vendor reference number, SAP
material number and SAP vendor number.

For PO creation, certain mandatory and business required fields will be defaulted
in based on a load variant created specifically for 1023, LAX.

The mapping file for PO creation is attached.

PO MAPPING.xls

19.09.2017 Page 4 of 5
 List Layout

normal ALV List Tree

Test Data
System
Data
ID

History of Test data

System
Date User Data
ID

Verification Procedures by Development

checked
Naming conventions are followed
Usage of standard program header
The extended syntax check was performed
Authority-Checks are active and tested
Online User Documentation done (optional)

19.09.2017 Page 5 of 5