Template - Word

OoredooMM & SDTechnical Design IIS005 Interface WMS to SAP

Technical DesignInterface WMS to SAP

General Information

Document Location

Associated Documentation (FD)

Sign Off

TeamNameDateSignature

Revision History

DateAuthorStatusDescription / Reason for Change

20 Feb 2014Rhesa TanotoDraftInitial Draft

19 May 2014Gregorius Raymond DjatnikaVersion 1.1Final

1General Requirements42Related Document43Development Objects44Assumptions45Technical Flow / Program Logic55.1General Program Hierarchy55.2Program Subroutine / Component Inventory55.3Code Reuse55.4Selection-screen Layout55.5Authorization Objects and Checks to be Used55.6Pseudo Codes75.7Output Detail/Layout95.8Interactive Capabilities96Performance Considerations97Set-Up Procedure98Recovery Procedure / Special Considerations99Exceptions910Unit Test1011Design Changes / Issue Documentation10

General Requirements Program DescriptionInterface WMS to SAP

Status (Required)100%

Business Priority

Related Document

DevLog NoDescriptionTransport RequestCHARM Number

Development Objects[List of all objects being used or modified e.g. program, function module, transaction codes, etc. Refer to content of Transport Request submitted for the change]

Object TypeNameDescription

Function moduleZMPU_WMS_GOODSMVT_UPLOADIDOC goods movement via BAPI

Function moduleZ_MPU_WMS_UPLOADERFM to Upload data from WMS to SAP

Assumptions[Assumptions that are being used so that program can be run/used properly]

Technical Flow / Program Logic

General Program Hierarchy [Required - Flowchart of program logic and processing to be included here, not the business or functional flowchart]

Program Subroutine / Component Inventory

Program Subroutine/ComponentDescription

ZMPUI_WMS_TO_SAPF_EXTRACT_DATAExtract data from CSV file

ZMPUI_WMS_TO_SAPF_POSTPreparing data for create Idoc

ZMPUI_WMS_TO_SAPF_SEND_IDOCCreate the Idoc

Code ReuseN/A

Selection-screen LayoutN/A

Input/Output File Layout

File typeCSV

ConceptDelimiter

Field separator, (Coma)

Decimal separator-

Thousand separator-

Date and time formatYYYYMMDD

Header column on 1st lineNo

PositionField NameField DescriptionData TypeLengthSampleRemarks

1PO/SO NumberPurchase Order or Sales order numberCHAR101000000028

2DateTransaction dateCHAR1011.02.2014

3Line itemLine item numberCHAR1010

4Transaction typeWMS transaction codeCHAR10GM_SCT

5Source materialSource material numberCHAR101100000002

6Destination materialDestination material numberCHAR101100000002

7QuantityQuantity to be postedN201

8UoMUnit of materialCHAR3PC

9Source storage locationStorage location numberCHAR42001 retail shop 1Only take the first 4 character to get the storage location number

10Destination storage locationStorage location numberCHAR4WHFX - faultyOnly take the first 4 character to get the storage location number

Data Mapping[Provide the field name, a short description, and any functional notes, translations and calculations. If a transaction was referenced to obtain the table and field names, please list the transaction code.]SAP Table Field NameSAP DescriptionExternal Field NameExternal Field DescriptionFunctional Notes/ Calculations/ Translations

VBAK-VBELNSO NumberPO/SO NumberSales Order Number

EKKO-EBELNPO NumberPurchase Order Number

MSEG-BLDATDateDateTransaction date

VBAP-POSNREKPO-EBELPLine itemLine ItemLine Item PO / SO

MSEG-MATNRMaterial numberSource materialSource material number

MSEG-UMMATReceiving / Issuing MaterialDestination materialDestination material number

MSEG-MENGEQuantityQuantityQuantity to be posted

MSEG-MEINSUnit of MeasureUoMUnit of material

MSEG-LGORTStorage LocationSource storage locationStorage location number

MSEG-UMLGOReceiving Storage LocationDestination storage locationStorage location number

Authorization Objects and Checks to be UsedN/A

Pseudo Codes

1. Get data from application server

Read file to extract the data and mapping the data into table IT_RAW_DATA.

2. Prepare data to be sent via Idoc by append the data into corresponding structure :a. ELBP2017_GM_HEAD_01

b. ELBP2017_GM_CODEIf movement type EQ 101Gm_code EQ 04Else if movement type EQ 551Gm_code EQ 04Else if movement type EQ 541 OR 351Gm_code EQ 04Else if processed data are SO, use GM_CODE EQ 03

c. ELBP2017_GM_ITEM_CREATE

WA_ITEM-PO_NUMBER = WA_RAW_DATA-DOCNO.WA_ITEM-PO_ITEM = WA_RAW_DATA-POSNR.WA_ITEM-MATERIAL = WA_RAW_DATA-MATNRWA_ITEM-MOVE_MAT = WA_RAW_DATA-UMMATWA_ITEM-STGE_LOC = WA_RAW_DATA-LGORTWA_ITEM-MOVE_STLOC = WA_RAW_DATA-UMLGOWA_ITEM-ENTRY_QNT = WA_RAW_DATA-MENGEWA_ITEM-ENTRY_UOM = WA_RAW_DATA-MEINS

If transaction type EQ GI_SCWA_ITEM-MOVE_TYPE = 551Append WA_ITEM.If transaction type EQ QI_OKWA_ITEM-MOVE_TYPE = 101WA_ITEM-STGE_LOC = WA_RAW_DATA-UMLGOWA_ITEM-MOVE_STLOC = blankAppend WA_ITEM.If transaction type EQ GI_STIf WA_RAW_DATA-UMLGO EQ WHFX OR WHQXWA_ITEM-MOVE_TYPE = 351Append WA_ITEMWA_ITEM-MOVE_TYPE = 101WA_ITEM-STGE_LOC = WA_RAW_DATA-UMLGOWA_ITEM-MOVE_STLOC = blankAppend WA_ITEMElseWA_ITEM-MOVE_TYPE = 351Append WA_ITEMIf transaction type EQ GM_SCTSELECT table EKET WHERE EBELN EQ WA_RAW_DATA-EBELNAND EBELP EQ WA_RAW_DATA-EBELPLoop at table RESB WHERE RSNUM EQ EKET_RSNUMWA_ITEM-material = RESB-MATNRWA_ITEM-ENTRY_QNT = RESB-MENGEWA_ITEM-ENTRY_UOM = RESB-MEINSWA_ITEM-VENDOR = RESB-LIFNRIF WA_RAW_DATA-LGORT IS BLANKWA_ITEM-STGE_LOC = WA_RAW_DATA-UMLGOELSEWA_ITEM-STGE_LOC = WA_RAW_DATA-LGORTENDIFAppend WA_ITEMENDLOOPWA_ITEM-PO_NUMBER = WA_RAW_DATA-DOCNO.WA_ITEM-PO_ITEM = WA_RAW_DATA-POSNR.WA_ITEM-MATERIAL = WA_RAW_DATA-MATNRWA_ITEM-MOVE_MAT = WA_RAW_DATA-UMMATWA_ITEM-MOVE_TYPE = 101WA_ITEM-STGE_LOC = WA_RAW_DATA-LGORTWA_ITEM-MOVE_STLOC = WA_RAW_DATA-UMLGOWA_ITEM-ENTRY_QNT = WA_RAW_DATA-MENGEWA_ITEM-ENTRY_UOM = WA_RAW_DATA-MEINSAPPEND WA_ITEMIf transaction type EQ GR_STWA_ITEM-MOVE_TYPE = 101WA_ITEM-STGE_LOC = WA_RAW_DATA-LGORTWA_ITEM-MOVE_STLOC = blankAPPEND WA_ITEM

3. Send idoc to be processedSend the idoc using function module IDOC_INBOUND_WRITE_TO_DB

And start the data processing by call function module IDOC_START_INBOUND

IDOC will call function module ZMPU_WMS_GOODSMVT_UPLOAD

This function module will processed data based on the data type (PO OR SO)

If the data are PO, the function module BAPI_GOODSMVT_CREATE will be called,Else, for SO data, function module BAPI_OUTB_DELIVERY_CREATE_SLS will be crated.

Output Detail/Layout(the data result are material documents for PO data and delivery order for SO data)

Interactive CapabilitiesN/APerformance ConsiderationsN/ASet-Up ProcedureN/ARecovery Procedure / Special ConsiderationsN/AExceptionsN/AUnit Test[The following table is used for unit test procedure by ABAPer refer to test script provided in Functional Design document. Provide screen-capture to show result when necessary]

Test Condition Expected ResultTest Result

Normal Processing

1.

2.

3.

4.

Error Processing

1.

2.

3.

Design Changes / Issue Documentation[Describe any change to the original design in this section Use this section to record issues or items that need to be resolved as part of the Functional Design. The following Issues were defined during Functional Design/Preparation.]

Raised byIssueDate NeededResolution/AnswerDate CompletedResolved by

File Name: AP450 IIS005 Interface WMS to SAP v1.1.docxPage 3 of 10Status: Draft

Copyright 2014 Ooredoo-Accenture. All Rights Reserved