Ptm en 006 Ts Bin to Bin

PROJECT IDENTIFICATION DETAILSProject Name PMIS Code Project Start Date

JAFRA ACE PROJECT PR15_003917 10th May 2015Project End Date SDC Regional Delivery Head SDC Project Manager

29th Jan 2016 Amarnath Jayaraman Michael SturmanSDC QC Member SDC QA Lead SAP Subsidiary

Priya Kota SAP NA

DOCUMENT REVISION, REVIEW, & APPROVAL HISTORY

TECHNICAL SPECIFICATION - PTM_EN_006 – BIN TO BIN TRANSFERV1 / AUGUST 2015

Technical Specification Enhancements Page 2 of 10

VER DATE AUTHOR REVIEWER/APPROVER REMARKS

1.0 Aug 25, 2015 Joel Leon Initial

Table of contents

1. Program Summary.................................................................................................................41.1. Definition..................................................................................................................................61.2. Defined Fields..........................................................................................................................61.3. Procedure................................................................................................................................ 62. Appendix.................................................................................................................................9

Copyright © 2011 SAP AG. All rights reserved 2


1. Program Summary

OBJECT OVERVIEW

Object ID PTM_EN_006Business Process

Object Title PTM_EN_006 - Bin to Bin Transfer

Object Description Bin to Bin Transfer

SAP Release ECC 6 EHP 7 SAP Module WM

Cycle of Testing C1Required Development Completion Date

DDMONYY

Complexity of Object Medium Transaction run Real-time

Type of Enhancement

Custom Dialog Screens Priority High

Similar SAP Transaction

LM00Similar SAP Program

TS CONTROL



TS Author and Phone Number

Leon, Joel

<Customer> Process Owner and Phone Number

Rivera, Ericka

TS Approved By Last Name, First Name TS Approval date DDMONYY

Other Contact and Phone Number

Other Contact and Phone Number

PROGRAM ATTRIBUTES

Enhancement ObjectFunction ExitIncludeScreen ExitMenu ExitBadiNew Transaction ZWM_RFMENU, ZWM_RFSUTSearch HelpArea MenuCustom Dialog ScreensIndexVOFM RoutinesBTE

Transaction CodeMessage Class

SAP Tables Read LTAK, LTAP, LQUA, LAGPCustom Tables N/A

AUTHORIZATION REQUIREMENTS

N/A

TECHNICAL FLOW DIAGRAM



PROCESSING LOGIC

1. Scan or Enter Storage Unit:

The user can type or scan values into the field. If scanning is used then an Enter character may be sent at the end of the barcode string and this should have the same effect as pressing the Enter key.

2. Storage Unit Validation:

Following validations were implemented:

a. If the value entered is neither a valid SU then display an error message “Invalid Storage Unit”.

b.

c.

3. Data Fetching:

Once all validations were made, we get information from the following tables:

LTAK - Transfer Order Header

LTAP - Transfer Order Detail

LQUA - Quants Information

LAGP - Storage Bin information

4. Moving Quantities

5. Moving Total --> Call BAPI: L_TO_CREATE_MOVE_SU (Create new transfer order for full SU move)

Before a transfer order is created the source bin needs to be checked to see if the stock already been allocated to other transfer orders. This is only relevant for storage units and where the source storage type of the storage unit is Block (T331-STEIN = “B”). The table LQUAB needs to be checked to determine the available quantity in a particular bin for the material-batch. If the quantity to be moved > available quantity in LQUAB-MENGE then display an error message ‘Stock in storage bin already allocated (LQUAB)’.

If a storage unit is being moved for the full SU quantity the Function module L_TO_CREATE_MOVE_SU (simulates LT0J transaction) can be used. The following parameters should be passed to the function module:

Name Typing Associated Type

Default value

Description Value



I_LENUM LIKE LEIN-LENUM Storage unit number SU number

I_BWLVS LIKE LTAK-BWLVS Movement type 998bin to bin transaction should use movement type 998

I_LZNUM LIKE LTAK-LZNUM SPACE Additional ref.number

I_NLTYP LIKE LTAP-NLTYP SPACE Destination storage type If manual bin was entered. If crossdocking then use the source storage type

I_NLBER LIKE LTAP-NLBER SPACE Destination storage section If manual bin was entered. If crossdocking then use the source storage section.

I_NLPLA LIKE LTAP-NLPLA SPACE Destination storage bin If manual bin was entered. If crossdocking then use the source storage bin.

I_NPPOS LIKE LTAP-NPPOS SPACE Position in destionation storage bin

I_SQUIT LIKE RL03T-SQUIT SPACE Immed.confirmat.

I_LETYP LIKE LTAP-LETYP SPACE Storage unit type Defect 349 – take the SUT from the material master record MLGN-LETY1

I_NIDRU LIKE RL03A-NIDRU SPACE Do not print X

I_DRUKZ LIKE T329F-DRUKZ

SPACE Print code

I_LDEST LIKE LTAP-LDEST SPACE Printer

I_UPDATE_TASK LIKE RL03A-VERBU

SPACE Indicator: update via update task

I_COMMIT_WORK

LIKE RL03B-COMIT

'X' Indicator whether COMMIT WORK in function module

I_BNAME LIKE LTAK-BNAME SY-UNAME

User who is generating the TO

I_SOLEX LIKE LTAK-SOLEX 0 Sollaufwand aus Fremdsystem

I_PERNR LIKE LTAK-PERNR 0 Personalnummer

I_BETYP LIKE LTAK-BETYP SPACE Bedarfstyp

I_BENUM LIKE LTAK-BENUM SPACE Bedarfsnummer

If there are errors then these should be displayed using screen 13. Pressing F3 after displaying the error should return to the previous screen.

If the transfer order is successfully created then the TO number and destination bin will be returned.

.

6. Moving Partial --> Call BAPI: L_TO_CREATE_SINGLE

For a partial SU move, the function module L_TO_CREATE_SINGLE should be used. The following values should be passed to the function module.

Name Typing Associated Type

Default value

Description Value



I_LGNUM LIKE LTAK-LGNUM Warehouse number WH code the user is signed into

I_BWLVS LIKE LTAK-BWLVS Movement type bin to bin transaction should use movement type 998 999

I_BETYP LIKE LTAK-BETYP SPACE Requirement type

I_BENUM LIKE LTAK-BENUM SPACE Requirement number

I_MATNR LIKE LTAP-MATNR Material no. Material

I_WERKS LIKE LTAP-WERKS

Plant Plant

I_LGORT LIKE LTAP-LGORT SPACE Lagerort SLoc

I_CHARG LIKE LTAP-CHARG SPACE Batch Batch

I_BESTQ LIKE LTAP-BESTQ SPACE Stock category Stock Category

I_SOBKZ LIKE LTAP-SOBKZ SPACE Special stock indicator Special stock indicator – this will allow vendor consignment stock to be moved

I_SONUM LIKE LTAP-SONUM

SPACE Special stock number Special stock indicator – this will allow vendor consignment stock to be moved

I_LETYP LIKE LTAP-LETYP SPACE Storage unit type Defect 349 – take the SUT from the material master record MLGN-LETY1

I_ANFME LIKE RL03T-ANFME

Requested qty. Quantity in alternate UOM

I_ALTME LIKE LTAP-ALTME Unit of measure WM UOM

I_WDATU LIKE LTAP-WDATU

INIT_DATUM

Goods receipt date

I_VFDAT LIKE LTAP-VFDAT INIT_DATUM

Expiration date

I_ZEUGN LIKE LTAP-ZEUGN SPACE Certificate number

I_LZNUM LIKE LTAK-LZNUM SPACE Additional ref.number

I_SQUIT LIKE RL03T-SQUIT SPACE Immed.confirmat.

I_NIDRU LIKE RL03A-NIDRU

SPACE Do not print If the SU label was scanned in step 16 then set to X. No print is required if there is an existing label.

I_DRUKZ LIKE T329F-DRUKZ

SPACE Print code

I_LDEST LIKE LTAP-LDEST SPACE Printer

I_WEMPF LIKE LTAP-WEMPF

SPACE Consignee

I_ABLAD LIKE LTAP-ABLAD SPACE Unload.point

I_VLTYP LIKE LTAP-VLTYP SPACE Source storage type Source storage type

I_VLBER LIKE LTAP-VLBER SPACE Source storage section Source storage section

I_VLPLA LIKE LTAP-VLPLA SPACE Source storage bin Source storage bin

I_VPPOS LIKE LTAP-VPPOS SPACE Item in source storage bin

I_VLENR LIKE LTAP-VLENR SPACE Source storage unit Source storage unit, if in SUM storage type

I_VLQNR LIKE LTAP-VLQNR SPACE Src.quant

I_NLTYP LIKE LTAP-NLTYP SPACE Destination storage type If manual bin was entered. If crossdocking then use the source storage type



I_NLBER LIKE LTAP-NLBER SPACE Destination storage section If manual bin was entered. If crossdocking then use the source storage section

I_NLPLA LIKE LTAP-NLPLA SPACE Destination storage bin If manual bin was entered. If crossdocking then use the source storage bin

I_NPPOS LIKE LTAP-NPPOS SPACE Position in destionation storage bin

I_NLENR LIKE LTAP-NLENR SPACE Dest.storage unit If the SU label was scanned in step 16 then populate this field. Otherwise leave blank and the system will generate a new SU number.

I_NLQNR LIKE LTAP-NLQNR SPACE Dest.quant

I_RLTYP LIKE LTAP-RLTYP SPACE Return storage type

I_RLBER LIKE LTAP-RLBER SPACE Return storage area

I_RLPLA LIKE LTAP-RLPLA SPACE Return storage bin

I_RLQNR LIKE LTAP-RLQNR SPACE Return quant

I_UPDATE_TASK LIKE RL03A-VERBU

SPACE Indicator: update via update task

I_COMMIT_WORK LIKE RL03B-COMIT

'X' Indicator whether COMMIT WORK in function module

I_BNAME LIKE LTAK-BNAME SY-UNAME User who is generating the TO

I_KOMPL LIKE RL03B-KOMPL

'X' Only generate TO if requested amount supplied

I_SOLEX LIKE LTAK-SOLEX 0 Sollaufwand aus Fremdsystem

I_PERNR LIKE LTAK-PERNR 0 Personalnummer

I_AUSFB LIKE LTAK-AUSFB SPACE Bemerkung zur Ausführung

If there are errors then these should be displayed. After displaying the error should return to the previous screen.

If the transfer order is successfully created then the TO number and destination bin will be returned.

7. Display Success Message

Display a Transfer order success message: “Transfer order “ &TOnumber “confirmed into bin “ &bin.

REUSABLE CODE

N/A

INTERNAL TABLES

Name Description



MESSAGES

Message Class

Message ID

Message Text

ZMM 001 Report Selection fetched no data

TEXT ELEMENTS

Name Text Description000 List Contains no text

SUBROUTINES

Name DescriptionLAYOUT_BUILD Logic for building the output

ASSUMPTIONS IN TECHNICAL DESIGN

OPEN ISSUES IN TECHNICAL DESIGN

UNIT TEST PLAN

[Please copy the Business test Conditions and Control scenarios from the FS]

[Add relevant Technical scenarios associated with this development. Examples would include 1) testing an error-free run; 2) testing the exception processes; 3) testing the error handling.]

Scenario # Input Selection Criteria Expected Result1 Scan SU, full quantity, allow system to

determine bin and confirm transfer Transfer Order created and confirmed automatically.



order – with verification2 Scan SU, part quantity, allow system to

determine bin, system generated SU number, print label, and confirm transfer order – with verification

Transfer Order created and confirmed automatically.

3 Scan SU, part quantity, allow system to determine bin, system generated SU number, print label and confirm transfer order – without verification

Transfer Order created and confirmed automatically.

4 Scan bin, confirm material, one material/batch/SLoc/stock category in bin, allow system to determine bin and confirm transfer order – with verification

5 Scan bin, confirm material, multiple material/batch/SLoc/stock category in bin, allow system to determine bin and confirm transfer order – with verification

6 Scan bin, confirm material, multiple material/batch/SLoc/stock category in bin, allow system to determine bin and confirm transfer order – destination is SUM, system generated SU number, print label - with verification

7 Scan bin, confirm material, multiple material/batch/SLoc/stock category in bin, allow system to determine bin and confirm transfer order – destination is SUM, scan destination SU number - with verification

RELATED DOCUMENTATION (ATTACH OSS NOTES, EMAILS, DOWNLOAD OF EXISTING REPORT, ETC)

2. Appendix


Documents

Ptm en 006 Ts Bin to Bin