You are on page 1of 15

NORTH AMERICAN AG SAP

DEVELOPMENT SPECIFICATION
FUNCTIONAL / TECHNICAL
Section I: Justification
Request Type:

Program:

( ) Divisonal

( x ) Local

Change Type:
Area (R/3 Module):
Requested by:
Title:
Short description:

( x ) Creation
( ) Change
( ) Break/Fix
MM
Date (03/June/200
Justin Schulz / Saundra Wildes
Contact Name & Phone #:
RF Bin to Bin Transfer
Using an RF device user can transfer material from one Bin Location to another

Program type:

( ) Data Load (Conversion) ( ) Interface ( ) Report
( ) Form (SAPSCRIPT) ( X ) Enhancement/Modification
( ) Others _________________
Program name:
ZLA0
Tran Code/Menu Path:
ZL_BIN2
Priority:
( ) high/mandatory ( X ) medium/recommended ( ) low/optional
Data volume:
_____________ records
Date to be available:
Only for Data Load/Conversion and
Interfaces:
1. Quality of legacy data:
( ) Good ( ) Average ( ) Poor
2. Complexity of legacy data:
( ) Simple ( ) Average ( ) Complex ( ) Extra-complex
3. Complexity of a manual input:
( ) Simple ( ) Average ( ) Complex
( ) Screens
3. Number of SAP Screens:
Only for Interfaces:
4. Type of interface:
5. Direction of interface:
6. Frequency:
Only for Reports:
1. Requested characteristics:
Generic question:
1. Impact of not creating the
program:

(
(
(
(

) Real-Time ( ) Pseudo-real time ( ) Batch
) Inbound
( ) Outbound
( ) Both
) Daily
( ) Weekly
( ) Monthly
) Fortnightly ( ) Other: __________________

(
(

) Drill-down
) Entry files

( ) Pushbuttons ( ) Sort
( ) Others: ________________

( ) legal requirements will not be fulfilled
( ) lack of information required for the business
( ) lose functionality compared to the old system
( ) others: _________________________
Is there any alternative in the standard system:
( ) Yes ( ) No
Describe the alternative found:
Reason why this alternative was not
( ) Performance problems ( ) Complexity
acceptable:
( ) Others: ___________________
Process
Program
Team Lead
Team Lead
Approval on:
Approval on:

.

Once he confirms the transaction then post LT01. This will allow John Deere to move material between different locations within a warehouse easier. This will help with productivity within the warehouses and supermarkets. You can look at transaction LM00 for the different screen resolutions. a current factory on SAP wants this enhancement also. Resolution: 16X20 8X40 The user will be moving Material from one Storage Bin to another. The transaction will be executed on an RF device and not on an SAP screen. I do not see any risks only improvements with implementing this process. For each screen we will need to design two screens to handle two types of resolutions. We will need to develop a multi-screen transaction program to handle this request. The John Deere Supermarkets that are be implemented will use this feature as well. Before posting a confirmation screen to be displayed to the user.Section IIa: Detailed Functional Description This is to enable bin-to-bin movements of loads in the warehouse via an RF scanner. The screens will have to fit accordingly. he will need to enter a source Bin and a destination Bin. Ryder currently has this functionality in their warehouse system and they will need it going forward. . Section IIb: Security Requirements L_LGNUM: Authorization for Warerhouse and Storage type L_TCODE : for Warehouse management Tcodes L_BWLVS : For Movement type in Warehouse management system. Seeding.. The transaction LRFMD has the profile of the user and which resolution of the screen the user will be using.

these are similar to the buttons seen on LM00 transaction. Use the function module L_USER_DATA_GET to retrieve the user settings. validate it. 0401.she has an active status in atleast one of Warehouse Locations. 0402. When user hits Next . This transaction will be linked to the button through customizing Screen 200 /400 : The user will enter Material # Source Storage Bin Quantity Uom The user will then hit Next. If the user has been maintained in the table check that he. 0202. Depending upon the Screen resolutions choose the appropriate screen sequence. 0203 etc If 8X40 then 0400. Once the user confirms the movement Post LT01 Goods movement w movement type ‘999’. 0201. there will be a Button to run the transaction ZL_RFBIN where the xx needs to be decided. Goods Movement between two Storage Bins in the s warehouse. the standard buttons on top will remain throughout all the screens at th top Back. Clr and Next. The screen logic is as follows Screen 101: RF Main menu.END OF FUNCTIONAL SPEC TECHNICAL SPECIFICATION Program Name: Title: Type: Design Considerations: Detailed Technical Description: SAPMZLA0_RFBINMVT ZL_RFBIN ( X ) Creation ( ) Change ( ) Break/Fix Design/Development Complexity Development labor estimate: Technical Specifications Code/Unit Test ( X ) High ( ) Medium ( ) Low _2 days _5 days The overall logic of this transaction is. then obtain the Destina information from the user. 0403 etc The contents of the screen as such will be the same only the screen size will be different. If 16X20 then 0200 . Obtain the source information from the user. In order to get access to LM00 the user will have to be registered via transaction LRFMD.

The user will be entering this info Plant Storage location Storage type Storage Bin: default from previous screen leave ready for input Batch number Stock type Hit Next to go to screen 201/401 Screen: 203/403 Enter Destination Bin . If the user does not enter any value take WM unit of measure or the base unit of measure in the order of priority. If quantity entered is more than available give message and position the Cursor in the quantity field when coming back to this screen. When the user hits Next the program will find out if it has a unique Quan in the table LQUA If Yes Go to screen 203/403 If No Go to screen 202/402 Screen 201/401: Source Info.• Check the quantity entered on the screen is greater than the available quantity in case if on one quant is available in the table LQUA table. • If the user has entered the UOM value then validate whether it is relevant for the material entered. If he hits Next it will mean option 2 is chosen and he will be taken to screen 203/403 If he hits Choose at the bottom of the screen he will be taken to screen 204/404 Screen 202/402 Default as much information as possible from Configuration tables if a unique source Quant not found. This screen will contain all the source information that was found fo that material which includes the following fields Material : default from previous screen Qty : also default from previous screen Storage type Storage bin : default from previous screen Storage Location: Plant Stock type Special stock indicator Stock number Batch number On this screen the user has two options Option 1: Choose the Destination Bin from a list or Option 2: Directly go to the Bin to which he wants to move the material to.

the stock type could also be different. Once the user Hits ‘F1 Save’ Check the source storage bin contains only the material and quantity we are moving to destination bin. Up [^] and Down [↓] buttons will be used by the user to navigate the location he wants to move the material to.User hits Next. if the present record being displayed the first record then disable the Up [^] button. We need to display all the fields similar to source info here. If the source storage bin is of zero stock then call the function module to confirm TO create. Th movement type will be Hard coded to ‘999’. If the material exists in other bins we need to displ the information to the user. If the user enters the destination bin and hits the stock button then show the total stock available in on the screen 207/407. If it was posted successfully a message with the document number will be displayed to the user an . System will find out if this is a unique Bin in that warehouse. Once the user has come to a position where he needs to move the material to he will have to hit the Next Button which will take him to screen 206/406 which is the confirmation screen Screen 205/405: If the Bin is not unique more information is needed as input from the user. since the function module provided by SAP does not retu status whether the posting was successful. LT01 will be posted using this information. Enable/disable the Up [^] and Down [↓] buttons based on the record we are displaying. This info is Storage type Storage Bin will be default from the previous screen and no input possible Storage section User Hits next to go to screen 206/406 Screen 206/406: This is the last confirmation screen to display to the user the Source and the destination Info all in one screen Source Info: Material / From Bin / Storage type / Storage Location / Plant / Stock Type / Sp. The movement type will be Hard coded to ‘999’. Use a BDC to post the LT01 transaction. If the reco being shown is the last record then disable Down [↓] button. The TO created will be immediately confirmed and printed with this movement type. That is the move empties the source storage bin completely or not. If the user does not enter the destination bin but hits the stock button then display the 208/408 scre Screen 204/404: This is where the user can choose a destination. The T created will be immediately confirmed and printed with this movement type. Since function module provided by SAP does not return a status whether the posting was successful. Stock indicator / Batch Destination Info: All the same except the storage bin is different. If it is not unique go screen 205/405 If the Bin is unique go to screen 206/406 which is the confirmation screen On the above screen a button ‘stock’ is provided which shows the available stock in the chosen destination bin.

Screen 207/407 This screen displays the storage bin and the stock in the storage bin. . If user hits back should navigate to 203/403 if the destination storage bin is entered or to 204/ where user can select the destination storage bin. but ch the field t133-sfifo <>’X’. Get entries from lqua and t133 tables use storage type and ware house number for inner join a Destination bin and t133-sfifo <>’X’ as where conditions. To get the stock in the destination storage bin add the stock in the quants of the storage bin. To get the stock in the destination storage bin add the stock in the quant’s of the storage bin. The up and down functionality is provide so that the user can browse through the destination bins.hitting back will take him to screen 200/400. Screen 208/408 This screen displays the storage bins and the stocks in the storage bins. but ch the field t133-sfifo <>’X’. If the posting was in error the error message will be displayed and hitting back will take him to scr 201/401 to start over the process.

Inbound Interfaces (legacy Interface Type: ( ) Legacy SAP ( )S ( ) Batch-Input ( ) Call Transaction ( )Direct Input ( ) IDOC ( ) ALE ( ) RFC Legacy System Information SAP Sy Input Tables/Tran File 01: s Involved: Field Typ Length Description Example Data Table Field OR Tran name e Field Technique: Trans Involved: Position C) Reports Tables / Logical DBs involved: Trans Involved: Report ( ) Report Painter ( ) Report Writer ( ) ABAP Query .B) Interfaces/Data Loads Layout Description Outbound .

Created via: ( ) ABAP Program Input Data: (Format of the data as its input into the report (ex. Data Dictionary format)) Field name Output Data Display: Position Type ( ) Info System Lengt h Decimal s Description Format of the data as its output to the end user Field name Type Lengt h Design of desired screen (select-options): Design of desired report: Decimal s Description .

D) Online Tables involved: Field Type Length Description Screen Label Design of desired screen(s): Consistency checks that must be done: Ite m Screen Field Description Flow Logic: Example: Screen 100 200 if selected pushbutton 1 go to screen 210. otherwise go to screen 220. .

IMG Tran: Print Program: Perform Program: Design of desired form: SAP Standard Form Layout: PS. Include also the name of the standard form and path/transaction where it is in R/3.E) Forms (SAPSCRIPT) Tables involved: SAP Standard Form: Config. . please include the copy here.: If this form is a copy of a standard form or if there is a model in the legacy system.

.

Process team member signature: _____________________________ Date: __/__/____ Developer/Tech Analyst signature: _____________________________ Date: __/__/____ .F) Other developments 1. 7. customizing path and details about what must be done.). Enhancement: Specify the available enhancement name. Matchcode ID or Search-Help: Specify the new ID that must be inserted or changed and what fields must be selected and the customizing path where it is possible to find it in R/3. You can copy the models from previous sections. 3. Modification: Give details about what must be done (program name. etc. transaction in which the program is used. Note: The section "Other developments" contains all other development types that were not put in previous sections. Caution: If you want to create a new screen. you must attach the desired screen model to this document. You can use the previous sections if applicable. for example.

___________________________________________________________________ _____________ ___________________________________________________________________ _____________ ___________________________________________________________________ _____________ ___________________________________________________________________ _____________ Responsible developer/TA: 11. New delivery date: 99/99/9999 Comments after new revision: (if the program contained errors before): Date: __/__/____ ___________________________________________________________________ _____________ ___________________________________________________________________ _____________ ___________________________________________________________________ . File(s) used for test (optional): ________________________________________________________________ 9. Describe the solution given to the errors.Section III: Unit Test Program name: Dev name: TA name: Test date: _______________________________________ Extensio ___ n: _______________________________________ ___ Responsible Process team member for testing: 8. If necessary include some comments in the appropriate section. 10. Is the program according the functional specification ? ( ) Yes ( ) No Note: If the program is OK just sign the form. ___________________________________________________________________ _____________ ___________________________________________________________________ _____________ ___________________________________________________________________ _____________ ___________________________________________________________________ _____________ 12. If the answer to question 2 is "No" please describe what problems were found in the program.

_____________ ___________________________________________________________________ _____________ Generic comments: ___________________________________________________________________ _____________ ___________________________________________________________________ _____________ ___________________________________________________________________ _____________ ___________________________________________________________________ _____________ Names and Signatures: _____________________________________________________________________________________ Process Team Lead _____________________________________________________________________________________ Developer/TA .