Transport BW warehouse management objects

hi
can soem one explain which is the best practise for transporting AWB objects in BW
1. create Single packages to transport AWB objects
or
2.create multiple packages to transport AWB objects
what are the pros and cons
can some one explain?

Hi,
You can search for threads on this topic. You'll find out that such transports are neither recommended nor supported by SAP. I have gone through such (system upgradation) cycles in projects - I think the best practice would be to plan the project deliverables in such a way so that tranport freeze can be achieved during the period the systems are getting upgraded.
Edited by: Mayank Gupta on Jul 30, 2008

Similar Messages

  • Reading material on shipping,transportation and warehouse management

    hi
       if anybody has material on above topics please send me at my mail [email protected]

    hi,
    please follow this link
    <a href="http://172.27.44.7/PlainHTML/helpdata/EN/c6/f85c504afa11d182b90000e829fbfe/frameset.htm">Warehouse mgmt</a>
    <a href="http://172.27.44.7/PlainHTML/helpdata/EN/38/c1853488601e33e10000009b38f83b/frameset.htm">Shipping</a>
    <a href="http://172.27.44.7/PlainHTML/helpdata/EN/d5/2285347860ea35e10000009b38f83b/frameset.htm">Transportation</a>
    Check ur mail for warehouse intergration document
    regards,
    Arun prasad

  • Reg : Material warehouse management view 1 & 2

    Hello All,
    Using a Z-programI am extending the warehouse managemnt view for a single Plant, the view gets created successfully. But some how an Inactive version of Warehouse management view gets created for other plant also. How we can prevent the creation of this inactive view creation.
    Please let me know your suggestion.
    Regards,
    Ravi Kasale.

    from Note 545626 - FAQ: Data transfer problems:
    Read the explanations in OSS Note 67616.
    Bear in mind that, in the structure/table HEADDATA, the for BAPI methods StandardMaterial.SaveData (BAPI_MATERIAL_SAVEDATA) and StandardMaterial.SaveReplica (BAPI_MATERIAL_SAVEREPLICA) of the business object BUS1001006, you can select the required views and these correspond to the respective maintenance status.
    In the segment E1MARAM of the MATMAS IDocs, you can assign the overall maintenance status in the field VPSTA.
    Edited by: Jürgen L. on Jun 6, 2011 4:01 PM

  • Transport an Appraisal and Objective Setting Template

    Note the following advice pertaining to transporting an appraisals and objective setting template (I have not found documentation about this anywhere else, so hopefully some of you find this useful):
    Scenario:
    You have maintained your templates in PHAP_CATALOG_PA in the main config client, and you have transported all other configurations (basic settings, etc.) to your unit test/integration test environment.
    However, although you have right-clicked the category groups and templates to be transported and included them in a transport request, you find that only some of your configuration (or perhaps none at all!) is arriving in the target client when the transport is performed.
    You may initially be able to work around this by downloading/uploading your config, but once your templates contain more complex configuration (such as using dynamic element references, etc.) you will find that this is no longer a feasible approach.
    Cause & Resolution:
    The problem is caused by outdated information in the workflow definition environment (transaction SWU3), and specifically the section labeled "Check Entries from HR Control Tables".
    Run transaction SWU3, expand tree node "Maintain Definition Environment" (which should be marked with a red cross at this stage) and click on "Check Entries from HR Control Tables". The information presented in the right-hand pane indicates that:
    If there are errors regarding the transport objects PDST or PDWS, the relevant entries are not maintained in table SOBJ. You can use the report RHSOBJCH to rectify this later.
    Proceed as suggested and run report RHSOBJCH (through SE38 or SA38) in the config client (i.e. where the templates are to be transported from). This has no side-effects I am aware of other than updating the reference information required.
    If you now run SWU3 again you should find that the "Check Entries from HR Control Tables" node is marked with a green tick.
    Simply go back to the catalog, include your cat.groups & templates in a transport again, and Voila! Our work here is done.
    Happy transporting...
    Side-note: You may ask (as I did) what transporting of appraisal templates has to do with workflow, but it just so happens that the PD objects and infotypes associated with appraisals (VA, VB, VC, etc.) are transported through the same mechanism as workflow templates (which are also PD objects). if you peek inside the transport you will note that everything to do with the template and category group configuration is bundled inside PDWS and PDST transport objects...
    Edited by: Francois Van Lille on Jun 29, 2009 9:58 AM

    >
    A. Jimenez wrote:
    > Hi Francois,
    >
    > I have successfully transported Categories and Templates, but I have customized "appraisals process", which seems to create VH Objects, and this objects or customizations are not added in the transport order.
    >
    > You or anyone know how to transport this customization?
    >
    > Thanks in advance
    Hi Abe,
    what is the appraisal process you are talking about?  The new stuff in ep4 where you define the process and steps which create the roadmap at the top of the document?  if so SAP does not have a great straightforward solution, but they did provide us some options.
    you can check out this thread and if you want I can send you the full document that is referred to in the post. 
    EP4: Performance Management-Flexible-Transporting the Tab & Process config

  • Lean warehouse Management

    Hi!
    I want to use lean warehouse management for creating TO. kinldly help me out to  know the settings of lean warehouse management with fixed storage bin and also for
    2. Wave pick settings
    With Regards
    Bhikshapathi

    dear vonnala
    Lean Warehouse Management: Configuration Guide
    Purpose
    The purpose of this document is to describe the general configuration steps required to manually set up the configuration within the system landscape that has already been installed using the corresponding installation or configuration guides for installation.
    The Configuration Guide describes how to set up the configuration of a Building Block manually, without the support of automated configuration tools.
    Preparation
    1.1 Prerequisites
    The following building blocks form the basis for all my SAP All-in-One Automotive, High Tech and Industrial Machinery and Components solutions. You only have to install these building blocks once.
    Building Blocks Comment
    Baseline Building Blocks (Layer 0)
    J00 - Essential Information
    J02 - Organizational Structure
    J03 - Financial Accounting
    J08 - Controlling
    J05 - Materials Management
    J04 - Sales and Distribution
    Baseline Building Blocks (Layer 1)
    J06 - Production Planning and Controlling
    J07 – Quality Management
    J18 - Product Cost Controlling
    J19 – Batch Management
    J20 - Cost Object Controlling – Make-to-Order
    J21 - Cost Object Controlling – Make-to-Stock
    J17 - Profitability Analysis
    J14 - Human Capital Management
    J09 - Travel Management
    Industry generic Building Blocks
    E04 - Supplement Settings
    E05 - Master Data HT / IM&C
    Configuration
    1.2 Lean WM Basic Settings
    1.2.1 Defining Defining Control&#61664;Control Parameters and Number Ranges for the Warehouse Number  Parameters for the Warehouse Number
    Use
    A warehouse number is an organizational unit in Logistics, which organizes the company from the perspective of Warehouse Management.
    In the Warehouse Management System, you can define a variety of control parameters at warehouse number level.
    Procedure
    1. Access the activity using one of the following navigation options:
    &#61664; Picking &#61664; Shipping &#61664; Logistic Execution &#61664;IMG Menu IMG   Define control parameters and number ranges for the warehouse number&#61507;Lean WM  Define control parameters and number ranges for warehouse no.(double&#61664; click)
    Transaction Code SM30
    2. Find the Field Name and input the relative value into the field.
    Table V_T3002
    Field name Value R/O/C Description
    Whse number L01 R
    Warehouse no. description Lean WM BP01 R
    Weight unit KG R
    Volume unit
    Default UoM K R
    Time unit/performance data
    Lean WM active X R
    Link to subsystem active
    Performance data
    Transfer order 01 R
    Group number 01 R
    1.2.2 Defining Storage Type
    Use
    A warehouse number is subdivided into a variety of storage types. A storage type is defined by its physical or organizational features (for example, high rack storage area, bulk storage, and goods receipt areas).
    A storage type has a short description rather than an address.
    Before you can implement Lean WM, you must configure the following settings:
    1. Assign a (newly defined) storage location to a warehouse number.(This step is defined by step 3.12 Control Plant / Storage Location / Warehouse Number Assignment
    2. You should set up at least three storage types:
    a storage type (that will be used as a source storage type) with one&#61692; or several fixed storage bins
    a goods issue area (as destination storage&#61692; type) for deliveries
    an interim storage area for differences&#61692;
    Procedure
    1. Access the activity using one of the following navigation options:
    IMG  Define Storage&#61664; Lean WM &#61664; Picking &#61664; Shipping &#61664; Logistic Execution &#61664;Menu IMG  type
    Transaction Code SM30
    2. Find the Field Name and input the relative value into the field
    Table V_T3012
    Data record 1:
    Field name Value Sub-screen
    Whse number L01
    Warehouse no. description Lean WM BP01
    Storage type 001
    Storage type name Fixed bin storage
    Stock plcmt requires confirmation for putaway control
    Unit of measure type srch
    Stock rmvl requires confirmation for picking control
    Unit of measure type srch
    Data record 2:
    Field name Value Sub-screen
    Whse number L01
    Warehouse no. description Lean WM BP01
    Storage type 916
    Storage type name Shipping area deliveries
    Stock plcmt requires confirmation for putaway control
    Unit of measure type srch
    Stock rmvl requires confirmation for picking control
    Unit of measure type srch
    Data record 3:
    Field name Value Sub-screen
    Whse number L01
    Warehouse no. description Lean WM BP01
    Storage type 999
    Storage type name Differences
    Stock plcmt requires confirmation for putaway control
    Unit of measure type srch
    Stock rmvl requires confirmation for picking control
    Unit of measure type srch
    Data record 4:
    Field name Value Sub-screen
    Whse number L01
    Warehouse no. description Lean WM BP01
    Storage type 902
    Storage type name IN-ZONE
    Stock plcmt requires confirmation for putaway control
    Unit of measure type srch
    Stock rmvl requires confirmation for picking control
    Unit of measure type srch
    1.2.3 Defining Doors
    Use
    In a WM-managed warehouse, you can define dock doors (also known as doors or gates). A door is a location where the goods either arrive in the warehouse or leave it.
    You can assign different functions to a dock door, for example:
    Goods receipt
    Goods issue
    Other transactions such as cross-docking and flow-through
    Procedure
    1. Access the activity using one of the following navigation options:
    &#61664; Picking &#61664; Shipping &#61664; Logistic Execution &#61664;IMG Menu IMG  Define Doors&#61472;&#61664;Lean WM
    Transaction Code SM30
    2. Find the Field Name and input the relative value into the field
    Table V_T30B
    Field name Value R/O/C Description
    Whse no. L01 R Warehouse number
    Door A01 R Door for warehouse number
    Text for door Door A01 R Text for door
    Staging area
    Matl stag. area txt
    GI indic. X R Goods issue indicator
    GR ind X R Goods receipt indicator
    CD ind Cross-docking indicator
    FT ind Flow-through indicator
    1.2.4 Defining Material Staging Areas
    Use
    A staging area is an interim storage area for goods that have been received from goods receipt and afterwards need to be transferred into the warehouse.
    It is also an interim storage area for goods that were picked in a warehouse and are to be loaded for goods issue through loading ramps or doors.
    You can assign different functions to a staging area:
    • Goods issue
    • Goods receipt
    Procedure
    1. Access the activity using one of the following navigation options:
    &#61664; Lean WM &#61664; Picking &#61664; Shipping &#61664; Logistic Execution &#61664;IMG Menu IMG  Define Material Staging Area
    Transaction Code SM30
    2. Find the Field Name and input the relative value into the field
    Table V_T30C
    Field name Value R/O/C Description
    Whse no. L01 R
    Staging area A01-01 R
    Matl stag. area txt Zone 1 R
    Door A01 R Door for warehouse number
    Text for door Door A01 R
    GI ind X R Goods issue indicator
    GR ind X R Goods receipt indicator
    CD ind Cross-docking indicator
    FT ind Flow-through indicator
    HU ind Handling unit indicator
    1.2.5 Defining Picking Area
    Use
    A picking area is an object within a storage type that groups together storage bins for purposes of stock removal.
    Procedure
    1. Access the activity using one of the following navigation options:
    &#61664;IMG Menu IMG  Define Picking&#61472;&#61664; Lean WM &#61664; Picking &#61664; Shipping &#61664;Logistic Execution  Area
    Transaction Code SM30
    2. Find the Field Name and input the relative value into the field
    Table V_T30A2
    Data record 1:
    Field name Value R/O/C Description
    WhN L01 R Warehouse number
    STy (storage type) 001 R
    PAr (Picking area) 001 R
    Picking area name Picking area 1 R
    Data record 2:
    Field name Value R/O/C Description
    WhN L01 R Warehouse number
    STy (storage type) 001 R
    PAr (Picking area) 002 R
    Picking area name Picking area 2 R
    1.2.6 Defining Transfer Type
    Use
    In Lean WM, the transfer type "A" (stock removal) is required for movement type control.
    Procedure
    1. Access the activity using one of the following navigation options:
    &#61664; Picking &#61664; Shipping &#61664; Logistic Execution &#61664;IMG Menu IMG   Define Transfer Type&#61664;Lean WM
    Transaction Code SM30
    2. Find the Field Name and input the relative value into the field
    Table V_T333A2
    Field name Value R/O/C Description
    WhN L01 R Warehouse number
    Transfer type A R
    Text f. shipment type Pick R
    1.2.7 Defining Movement Types
    Use
    The SAP R/3 System uses movement type to process movements in Inventory Management (for example, goods receipt for a purchase order or goods issue to a cost center). When the system recognizes a movement as being relevant for Warehouse Management, it assigns this movement to a WM movement type by means of a table.
    The movement type for the Warehouse Management System provides the information required for stock removals or picking:
    Interim&#61692; storage bin
    Fixed bin coordinate&#61692;
    Control indicator for processing,&#61692; confirming, and printing transfer orders
    Confirmation info&#61692;
    Procedure
    1. Access the activity using one of the following navigation options:
    &#61664; Lean WM &#61664; Picking &#61664; Shipping &#61664; Logistic Execution &#61664;IMG Menu IMG  Define Movement Type
    Transaction Code SM30
    2. Find the Field Name and input the relative value into the field
    Table V_T3332
    Data record 1:
    Field name Value R/O/C Description
    Warehouse number L01 R
    Warehouse no. description Lean WM R
    Movement type 255 R
    Movement type description Goods Issue general R
    Src 001 R
    Src Stor. Bin
    Dest 916 R
    Dest Stor. Bin
    Transfer type A R
    Text for transfer type TRATX Pick R
    TO creation screen 2 R
    Scr. TO confirmation 2 R
    Manual TO creation not allowed
    Transfer priority
    Print code
    TO item can be confirmed immed.
    Propose confirmation
    Data record 2:
    Field name Value R/O/C Description
    Warehouse number L01 R
    Warehouse no. description Lean WM R
    Movement type 601 R
    Movement type description Picking by delivery note R
    Src 001 R
    Src Stor. bin
    Dest 916 R
    Dest Stor. bin
    Transfer type A R
    Text for transfer type TRATX Pick R
    TO creation screen 2 R
    Scr. TO confirmation 2 R
    Manual TO creation not allowed X R
    Transfer priority
    Print code 02 R
    TO item can be confirmed immed. X R
    Propose confirmation
    1.2.8 Defining Difference Indicator
    Use
    Using the difference indicator, you can classify your differences. This indicator is used in Lean WM for evaluation purposes only.
    Procedure
    1. Access the activity using one of the following navigation options:
    Logistic&#61664;IMG Menu IMG   Define Difference&#61664; Lean WM &#61664; Picking &#61664; Shipping &#61664;Execution  Indicator
    Transaction Code SM30
    2. Find the Field Name and input the relative value into the field
    Table V_T3362
    Field name Value R/O/C Description
    WhN L01 R Warehouse number
    DiffInd (difference indicator) X R
    Description of difference indicator Stock difference R
    Stor.ty.differences 999 R
    Diff.bin
    TO X R
    Source bin
    1.2.9 Control Plant / Storage Location / Warehouse Number Assignment
    1.2.9.1 Assigning Warehouse No. to Plant-Storage Locations
    Use
    By doing so, system can recognize which storage locations in Materials Management are controlled by the Warehouse Management system (LE-WM); you must assign the plants and the storage location to the warehouse number.
    Procedure
    1. Access the activity using one of the following navigation options:
    &#61664;Assignment &#61472;&#61664;Enterprise Structure &#61472;&#61664;IMG Menu IMG  Assign warehouse No. To plant/storage&#61664;Logistic Execution  &#61664;Location
    Transaction Code SM30
    2. Find the Field Name and input the relative value into the field
    Table V_T320
    Field name Value R/O/C Description
    Plant BP01 R
    SLoc 0005 R
    WhN L01 R
    1.2.9.2 Control Plant / Storage Location / Warehouse Number Assignment
    Use
    You can control for each combination of plant, storage location, and warehouse number whether Lean WM or standard management of bin inventory is to be selected.
    If you are using Lean WM, you can also specify a picking storage type that is used for creating transfer orders.
    Procedure
    1. Access the activity using one of the following navigation options:
    &#61664; Logistic Execution &#61664;IMG Menu IMG   Control Plant / Storage Location / Warehouse&#61664; Lean WM &#61664; Picking &#61664;Shipping  Number Assignment
    Transaction Code SM30
    2. Find the Field Name and input the relative value into the field
    Table V_T3202
    Field name Value R/O/C Description
    Plnt BP01 R
    Stor. loc. 0005 R
    WhNo (Whse number) L01 R
    Degree of activation Warehouse Mgmt 1 R
    Stor.type for picking in Lean WM 001 R
    1.2.10
    1.2.11 Assigning Picking Location
    Use
    Assign the picking locations to the combinations of shipping point and storage condition for every plant.
    Procedure
    1. Access the activity using one of the following navigation options:
    &#61664; Shipping &#61664; Logistic Execution &#61664;IMG Menu IMG   Assign Picking Location&#61664; Determine Picking Location &#61664;Picking
    Transaction Code SM30
    2. Find the Field Name and input the relative value into the field
    Table V_TVKOL
    Field name Value Description
    ShPt BP01 Plant
    Plnt BP01 Shipping point/receiving pt
    SC K1 Storage conditions
    SLoc 0005 Storage location
    1.3 Print Control for Warehouse
    Use
    Print control defines the following:
    • Which slips are to be printed for the movements (that is, for the transfer orders) within the Warehouse Management System
    • How these slips are to be printed (that is, which forms are to be used, how many copies are to be printed)
    • On which printer a slip is to be printed automatically
    And print control manages the print operations of the warehouse. This flexibility involves a certain degree of complexity with regard to the parameterization.
    Procedure
    1. Access the activity using one of the following navigation options:
    &#61664;IMG Menu IMG   Define Print&#61664; Lean WM &#61664; Picking &#61664; Shipping &#61664;Logistic Execution  control
    Transaction Code OMLV
    2. Choose the following button and check the contents
    (Here only the contents of the warehouse no. L01 are listed):
    2.1 Spool code
    Data Record 1
    Field name Value R/O/C Description
    WhN L01 R Warehouse number
    Spool 01 R Spool request name
    Copies 1 R Number of copies
    Title LVS1 R Spool control data
    Print_immed. X R Print immediately
    Delete_after_print X R Release after output
    NewSplReq__ New spool request
    Data Record 2
    Field name Value R/O/C Description
    WhN L01 R Warehouse number
    Spool 02 R Spool request name
    Copies 1 R Number of copies
    Title LVS2 R Spool control data
    Print_immed. Print immediately
    Delete_after_print X R Release after output
    NewSplReq__ New spool request
    2.2 sort profile/collective process
    Field name Rec1 Rec2 Rec3 Rec4 Rec5 Rec6 Rec7 Rec8 Rec9
    WhNo_(Whse_number) L01 L01 L01 L01 L01 L01 L01 L01 L01
    Sort_profile 1 2 3 4 5 6 7 8 9
    1st_sort_criterion SPOOI SPOOI SPOOI SPOOI SPOOI SPOOI SPOOI SPOOI SPOOI
    Sort_descending_order (1st_sort_criter.)
    Control_break_1st_sort_criterion
    2nd_sort_criterion LDESI LDESI LDESI LDESI LDESI LDESI LDESI LDESI LDESI
    Sortdescending_order (2nd_sort_crit.)
    Control_break_2nd_sort_criterion X
    3rd_sort_criterion REFNR REFNR REFNR REFNR FORMI FORMI FORMI FORMI REFNR
    Sortdescending_order (3rd_sort_crit.)
    Control_break_3rd_sort_criterion X X X X
    4th_sort_criterion FORMI FORMI FORMI FORMI LGNUM LGNUM LGNUM LGNUM FORMI
    Sortdescending_order (4th_sort_crit.)
    Control_break_4th_sort_criterion X X X X
    5th_sort_criterion LGNUM LGNUM LGNUM LGNUM VLTYP VLTYP VLTYP VLTYP LGNUM
    Sortdescending_order (5th_sort_crit.)
    Control_break_5th_sort_criterion
    6th_sort_criterion VLTYP NLTYP VLTYP TANUM VLPLA NLPLA WERKS TAPOS NLTYP
    Sortdescending_order (6th_sort_crit.)
    Control_break_6th_sort_criterion X X X X
    7th_sort_criterion VLPLA NLPLA WERKS TAPOS
    TANUM TANUM LGORT KOBER
    Sortdescending_order_ (7th_sort_crit.)
    Control_break_7th_sort_criterion X
    8th_sort_criterion TANUM TANUM LGORT TAPOS TAPOS MATNR VLPLA
    Sortdescending_order (8th_sort_crit.)
    Control_break_8th_sort_criterion
    9th_sort_criterion TAPOS TAPOS MATNR CHARG TANUM
    Sortdescending_order (9th_sort_crit.)
    Control_break_9th_sort_criterion
    10th_sort_criterion CHARG BESTQ
    TAPOS
    Sortdescending_order_ (10th_sort_crit.)
    Control_break_10th_sort_criterion
    11th_sort_criterion BESTQ SOBKZ
    Sortdescending_order_ (11th_sort_crit.)
    Control_break_11th_sort_criterion
    12th_sort_criterion SOBKZ LSONR
    Sortdescending_order_ (12th_sort_crit.)
    Control_break_12th_sort_criterion
    13th_sort_criterion LSONR VLTYP
    Sortdescending_order_ (13th_sort_crit.)
    Control_break_13th_sort_criterion
    14th_sort_criterion VLTYP
    Sortdescending_order_ (14th_sort_crit.)
    Control_break_14th_sort_criterion
    15th_sort_criterion
    Sortdescending_order_ (15th_sort_crit.)
    Control_break_15th_sort_criterion
    2.3 print code
    Field name Rec1 Rec2 Rec3 Rec4 Rec5 Rec6 Rec7
    WNo___(Warehouse_number) L01 L01 L01 L01 L01 L01 L01
    PrCd__(Print_code) 01 02 03 11 12 21 22
    Print_code_description
    Find_shipping_data____
    Determine_production_data_
    Form_ LVSTAEINZEL LVSTALISTE LVSTOSOLO LVSTAEINZEL LVSTALISTE LVSKOMMIL1
    LVSKOMMIL2
    PTm_(Time_of_printing)________
    Sort_profile 1 1 1 4 1 1
    Combined_print x x x x
    Spool_data 02 02 01 02 02 02 02
    Label_form LVSLABELS
    Label_spool_code 01
    Quantity_of_labels_(Indicator) 2
    2.4 assign printer to storage type (LP01 to 001 only)
    Field name Rec1 Rec2 Rec3
    WhNo_(Whse_number) L01 L01 L01
    STy__(storage_type) 001 916 999
    Storage_type_description Fixed bin storage Shipping area deliveries Differences
    Printer
    2.5 assign print code to movement type
    Field name Rec1 Rec2 Rec3
    WhNo_(Whse_number) L01 L01 L01
    MvT__(WM_movement_type) 101 255 601
    Movement_type_description Goods receipt for pur.or.
    Picking by delivery note
    PrCd__(Print_code) 01 02
    2.6 assign print report to warehouse No.
    Field name Rec1
    WhNo_(Whse_number) L01
    Warehouse_number_descrip. Lean WM Plant BP01
    Print_report RLVSDR40
    2.7 print control multi-processing
    Field name Rec1
    WhN L01
    Ref.ty. L
    Status 2
    Print_prog. RLKOMM40
    PrCd 21
    Printer LP01
    1.4 Manual Activity
    1.4.1 Maintaining Number Range Intervals for Transfer Order
    Use
    Maintain number range intervals for transfer order
    Procedure
    In this step, you define that, the Number range for Transfer order as 01 and Group number as 01, now you should tell the system how the number range would like for 01 as transfer order and 01 for the group number, for both number range, you may define you own number range, the following information just for reference:
    Access the activity using one of the following navigation options:
    &#61664; Logistic Execution &#61664;IMG Menu IMG   Define control parameters and number ranges for&#61664; Lean WM &#61664; Picking &#61664;Shipping   Maintain number range intervals for transfer orders&#61664;the warehouse number  (double click)
    Transaction Code LN02
    Check if the internal number range 01 (0000000001-1000000000) has been defined
    Once you have defined your number ranges, it is extremely difficult to change them afterwards when the objects concerned are filled with data.
    Bear in mind that you will be entering data on a long-term basis. Create your number range intervals accordingly.
    1.4.2 Maintaining Number Range Intervals for Reference Numbers
    Use
    Reference number range has the following meanings:
    This number identifies a number range to be used for the assignment of sequential numbers for WM reference numbers. Reference numbers are used to create or print a group of transfer orders at one time.
    A sequential number generated by the system for the purpose of multiple processing of transfer requirements and delivery notes.
    The reference number can also be used to print the resulting transfer orders at a later time.
    Procedure
    In this step, you define that, the Number range for Transfer order as 01 and Group number as 01, now you should tell the system how the number range would like for 01 as transfer order and 01 for the group number, for both number range, you may define you own number range, the following information just for reference:
    Access the activity using one of the following navigation options:
    &#61664;IMG Menu IMG  Define control parameters&#61472;&#61664; Lean WM &#61664; Picking &#61664; Shipping &#61664;Logistic Execution   Maintain number range intervals for&#61664;and number ranges for the warehouse number  Reference Numbers( double click)
    Transaction Code LN06
    Check if the internal number range 01 (5000000000 - 5999999999) has been defined
    Once you have defined your number ranges, it is extremely difficult to change them afterwards when the objects concerned are filled with data.
    Bear in mind that you will be entering data on a long-term basis. Create your number range intervals accordingly.
    rewards if it helps
    siva

  • Configuration of warehouse management

    Dear All,
         Can anybody tell me step by step detail configurations of Warehouse management in SAP R/3 system ??
                                                                                    with regards,
                                                                                    RANA

    Hi,
    It's very tough to explain you step to step config process of WM. Following are the main configuration steps that are required for any new ware house implementation.
    Please explore all the following steps, that will help you in configuring the ware house.
         Configuration     
    1     Define, copy, delete, check warehouse number (SPRO)
    2     Assign warehouse number to plant/storage location (SPRO)
    3     Define Control Parameters for Warehouse Number (SPRO)
    4     Define Number Ranges  (OMLW)     
    5     Define Storage Type (Trans : SPRO)     
    6     Define Storage Sections (SPRO)     
    7     Define Storage Bin Types (SPRO)     
    8     Define Blocking Reasons (SPRO)     
    9     Define Storage Bin Structure (LS10)     
    10     Define Storage Type Indicators (SPRO)     
    11     Define Storage Unit Types (SPRO)     
    12     Define Storage Section Indicators:     
    13     Activate Storage Type Search (OMLY)     
    14     Activate Storage Section Search  (OMLZ)     
    15     Activate Storage Bin Type Search (OMM1)     
    16     Define Sort Sequence for Putaways (Cross-line Stock Putaway) (OMLM)     
    17     Define Sort Sequence for Stock Removal (Picking) (SPRO)     27
    18     Define Requirement Types (OMNF)     
    19     Define Shipment Types (SPRO)     
    20     Define Movement Types (SPRO)     
    21     Confirmation (OMLX)     34
    22     Define Print Control (OMLV)     
    23     Define Default Values (SPRO)     
    24     Define Types per Storage Type (OMNK)     
    25     Define Differences and Document Limits (SPRO)     
    26     Clear Differences (Interface to Inventory Management) (SPRO)     
    27     Maintain Number Ranges   (OMMB)     
    28     Activate Storage Unit Management per Warehouse Number (SPRO)     
    29     Activate Warehouse Activity Monitor Objects (SPRO)     
    30     Define Critical Parameters (SPRO)     
    31     Define Variant for "Object Overview" Program (OML1)     
    32     Define Variants for Selection Programs (OML2 & OML7)     
    33     Define Movement Types (Interfaces) (OMLR)     
    34     <SAP OSS Notes and User Exits>     
    Thanks & Regards,
    Krish

  • Materia master warehouse management view

    Hi Experts
    In OMS2 I have enabled the Warehouse Management view for ROH & HALB.
    But In MM01 appears both warehouse management view 1 & 2. 
    How do i restrict it to appear view 1 only and not . Also how to control in the field reference for a specific plant only. I have assigned a new field reference #0009.
    thanks
    Edited by: SAP-MM1 on Aug 25, 2011 4:40 PM

    Hello ,
    For Field Reference please make sure you have maintained the following:
    Txn OMSR
    Eg Field MBEW - MTORG  -> Selection group 128
    in Txn OMS9
    Field Selection group 128 Field reference 0009 -> Optional Entry
    Txn OMSA
    Plant 1000 -> Field reference 0009..
    As for Views , you cant restrict by authorisation for just one view . You can restrict the wholw view by using Authorisatio Object M_MATE_STA. OR you can customise screens. Please look at note 44410
    Regards
    Amber

  • Experiences with ES Bundle "Integration of external Warehouse Management" ?

    Hi PI Experts,
    anybody who can share experiences with the ES Bundle Integration of [External Warehouse Management System |https://www.sdn.sap.com/irj/scn/wiki?path=/display/espackages/integrationofExternalWarehouseManagement+System] and the usage of its Enterprise Services "Confirm Goods Movement_V1" or "Confirm Goods Movement" ?
    As far as I understood these ES can be used for goods movements out of the ERP System.
    Is it really possible to use these ES while creating an goods movement with Transaction MIGO ??
    As far as I know it is only possible to send Transport Orders with WMTORD IDOCS out of SAP to externa Systems (!!) without any custom coding (!!) . Using instead an WMBXY message type (IDOC WMBIDO02) is only for inbound IDOC processing. If using this Standard IDOC for outbound IDOC processing the only way is implementing the BADI called while perfoming the TA MIGO. Correct?
    Any experiences either with the ES Bundle or the IDOC goods movement out of SAP ERP are welcome.
    Kind regards,
    Dries

    you can use ES for creating goods movement in SAP ( see the esoa sample apps on sdn) or you can make your won service published using BAPI .
    I am not catching you in the use of BADI , elaborate more about that.

  • Transport user error: invalid object name while starting CMS in CCM

    Hi Experts,
            I'm not able to start the CMS in CCM.It was working fine. Suddenly it went down due to some data base access failure. After that Iu2019m not able to start the CMS.
    Kindly find the event viewer error and information.
    Error: The root server reported an error Initialization Failure.
    Error: Failed to register object..   Reason: Transport user error: invalid object name..
    Information: Central Management Server stopped
          Could you please tell me how to start the CMS in CCM? Since I can able to setup CMS Database and audit database successfully.
    Regards,
    Sridharan

    Hi ,
            Thanks for the response.I have trace the CMS.I found some error in log file.any idea on the following errors,
    trace message: CNSClientManager::VerifyConnection() : search fails(37) - Transport user error: object with the specified name not found.
    trace message: CNSClientManager::VerifyConnection() : Failed to query for APSs.  Empty cluster list returned.
    trace message: TheAPSServer::RegisterApsInNameServer: Fail to register the current APS(Transport user error: invalid object name.)
    trace message: CNSClientManager::ClusterInfo::InvalidateAPS: Removing APS  from m_ActiveMembers and adding to m_InactiveMembers
    trace message: SIServerController:run: Fail to initialize or uninitialize.  Reason is The root server reported an error Initialization Failure.:
    Regards,
    Sridharan

  • User Exit for warehouse management - transfer order sorting

    Hi,
    I want to sort transfer order of warehouse management by user exit, which user exit I can use?
    Kindly please advise.
    Regards

    Hi,
    I worked on the same object.
    For sorting you have to place a button in the standard transaction,
    I found some screen exits but they are not working.
    Finally I developed the total customized transaction for that standard LM45.
    If you have any doubts let me know.

  • Deactivating Warehouse management

    Hi friends
    I need to deactivate warehouse management for one of the plant (which is basically third party plant). Objective is to stop using WM for the particular plant / storage location combination. WM activities will be taken care separately by third party.
    Please provide me information like what are the ways of doing the same. Whether removal of WH assignment will do ?/ what are the precautions to be taken.
    Thanks
    Pramod Raul

    Hello Pramod,
    Just delink WH assignment will not work, but you need to carry out some other process as well. The following thread will help.
    Re: Convert WM storage location to IM storage location
    Regards
    Arif Mansuri

  • IPhone core data - fetched managed objects not being autoreleased on device (fine on simulator)

    I'm currently struggling with a core data issue with my app that defies (my) logic. I'm sure I'm doing something wrong but can't see what. I am doing a basic executeFetchRequest on my core data entity, but the array of managed objects returned never seems to be released ONLY when I run it on the iPhone, under the simulator it works exactly as expected. This is despite using an NSAutoreleasePool to ensure the memory footprint is minimised. I have also checked with Instruments and there are no leaks, just ever increasing allocations of memory (by '[NSManagedObject(_PFDynamicAccessorsAndPropertySupport) allocWithEntity:]'). In my actual app this eventually leads to a didReceiveMemoryWarning call. I have produced a minimal program that reproduces the problem below. I have tried various things such as faulting all the objects before draining the pool, but with no joy. If I provide an NSError pointer to the fetch no error is returned. There are no background threads running.
    +(natural_t) get_free_memory {
        mach_port_t host_port;
        mach_msg_type_number_t host_size;
        vm_size_t pagesize;
        host_port = mach_host_self();
        host_size = sizeof(vm_statistics_data_t) / sizeof(integer_t);
        host_page_size(host_port, &pagesize);
        vm_statistics_data_t vm_stat;
        if (host_statistics(host_port, HOST_VM_INFO, (host_info_t)&vm_stat, &host_size) != KERN_SUCCESS) {
            NSLog(@"Failed to fetch vm statistics");
            return 0;
        /* Stats in bytes */
        natural_t mem_free = vm_stat.free_count * pagesize;
        return mem_free;
    - (void)viewDidLoad
        [super viewDidLoad];
        // Set up the edit and add buttons.
        self.navigationItem.leftBarButtonItem = self.editButtonItem;
        UIBarButtonItem *addButton = [[UIBarButtonItem alloc] initWithBarButtonSystemItem:UIBarButtonSystemItemAdd target:self action:@selector(insertNewObject)];
        self.navigationItem.rightBarButtonItem = addButton;
        [addButton release];
        // Obtain the Managed Object Context
        NSManagedObjectContext *context = [(id)[[UIApplication sharedApplication] delegate] managedObjectContext];
        // Check the free memory before we start
        NSLog(@"INITIAL FREEMEM: %d", [RootViewController get_free_memory]);
        // Loop around a few times
        for(int i=0; i<20; i++) {
            // Create an autorelease pool just for this loop
            NSAutoreleasePool *looppool = [[NSAutoreleasePool alloc] init];
            // Check the free memory each time around the loop
            NSLog(@"FREEMEM: %d", [RootViewController get_free_memory]);
            // Create a minimal request
            NSEntityDescription *entityDescription = [NSEntityDescription                                                 
                                                  entityForName:@"TestEntity" inManagedObjectContext:context];
            // 'request' released after fetch to minimise use of autorelease pool       
            NSFetchRequest *request = [[NSFetchRequest alloc] init];
            [request setEntity:entityDescription];
            // Perform the fetch
            NSArray *array = [context executeFetchRequest:request error:nil];       
            [request release];
            // Drain the pool - should release the fetched managed objects?
            [looppool drain];
        // Check the free menory at the end
        NSLog(@"FINAL FREEMEM: %d", [RootViewController get_free_memory]);
    When I run the above on the simulator I get the following output (which looks reasonable to me):
    2011-06-06 09:50:28.123 renniksoft[937:207] INITIAL FREEMEM: 14782464
    2011-06-06 09:50:28.128 renniksoft[937:207] FREEMEM: 14807040
    2011-06-06 09:50:28.135 renniksoft[937:207] FREEMEM: 14831616
    2011-06-06 09:50:28.139 renniksoft[937:207] FREEMEM: 14852096
    2011-06-06 09:50:28.142 renniksoft[937:207] FREEMEM: 14872576
    2011-06-06 09:50:28.146 renniksoft[937:207] FREEMEM: 14897152
    2011-06-06 09:50:28.149 renniksoft[937:207] FREEMEM: 14917632
    2011-06-06 09:50:28.153 renniksoft[937:207] FREEMEM: 14938112
    2011-06-06 09:50:28.158 renniksoft[937:207] FREEMEM: 14962688
    2011-06-06 09:50:28.161 renniksoft[937:207] FREEMEM: 14983168
    2011-06-06 09:50:28.165 renniksoft[937:207] FREEMEM: 14741504
    2011-06-06 09:50:28.168 renniksoft[937:207] FREEMEM: 14770176
    2011-06-06 09:50:28.174 renniksoft[937:207] FREEMEM: 14790656
    2011-06-06 09:50:28.177 renniksoft[937:207] FREEMEM: 14811136
    2011-06-06 09:50:28.182 renniksoft[937:207] FREEMEM: 14831616
    2011-06-06 09:50:28.186 renniksoft[937:207] FREEMEM: 14589952
    2011-06-06 09:50:28.189 renniksoft[937:207] FREEMEM: 14610432
    2011-06-06 09:50:28.192 renniksoft[937:207] FREEMEM: 14630912
    2011-06-06 09:50:28.194 renniksoft[937:207] FREEMEM: 14651392
    2011-06-06 09:50:28.197 renniksoft[937:207] FREEMEM: 14671872
    2011-06-06 09:50:28.200 renniksoft[937:207] FREEMEM: 14692352
    2011-06-06 09:50:28.203 renniksoft[937:207] FINAL FREEMEM: 14716928
    However, when I run it on an actual iPhone 4 (4.3.3) I get the following result:
    2011-06-06 09:55:54.341 renniksoft[4727:707] INITIAL FREEMEM: 267927552
    2011-06-06 09:55:54.348 renniksoft[4727:707] FREEMEM: 267952128
    2011-06-06 09:55:54.702 renniksoft[4727:707] FREEMEM: 265818112
    2011-06-06 09:55:55.214 renniksoft[4727:707] FREEMEM: 265355264
    2011-06-06 09:55:55.714 renniksoft[4727:707] FREEMEM: 264892416
    2011-06-06 09:55:56.215 renniksoft[4727:707] FREEMEM: 264441856
    2011-06-06 09:55:56.713 renniksoft[4727:707] FREEMEM: 263979008
    2011-06-06 09:55:57.226 renniksoft[4727:707] FREEMEM: 264089600
    2011-06-06 09:55:57.721 renniksoft[4727:707] FREEMEM: 263630848
    2011-06-06 09:55:58.226 renniksoft[4727:707] FREEMEM: 263168000
    2011-06-06 09:55:58.726 renniksoft[4727:707] FREEMEM: 262705152
    2011-06-06 09:55:59.242 renniksoft[4727:707] FREEMEM: 262852608
    2011-06-06 09:55:59.737 renniksoft[4727:707] FREEMEM: 262389760
    2011-06-06 09:56:00.243 renniksoft[4727:707] FREEMEM: 261931008
    2011-06-06 09:56:00.751 renniksoft[4727:707] FREEMEM: 261992448
    2011-06-06 09:56:01.280 renniksoft[4727:707] FREEMEM: 261574656
    2011-06-06 09:56:01.774 renniksoft[4727:707] FREEMEM: 261148672
    2011-06-06 09:56:02.290 renniksoft[4727:707] FREEMEM: 260755456
    2011-06-06 09:56:02.820 renniksoft[4727:707] FREEMEM: 260837376
    2011-06-06 09:56:03.334 renniksoft[4727:707] FREEMEM: 260395008
    2011-06-06 09:56:03.825 renniksoft[4727:707] FREEMEM: 259932160
    2011-06-06 09:56:04.346 renniksoft[4727:707] FINAL FREEMEM: 259555328
    The amount of free memory reduces each time round the loop in proportion to the managed objects I fetch e.g. if I fetch twice as many objects then the free memory reduces twice as quickly - so I'm pretty confident it is the managed objects that are not being released. Note that the entities that are being fetched are very basic, just two attributes, a string and a 16 bit integer. There are 1000 of them being fetched in the examples above. The code I used to generate them is as follows:
    // Create test entities
    for(int i=0; i<1000; i++) {
        id entity = [NSEntityDescription insertNewObjectForEntityForName:@"TestEntity" inManagedObjectContext:context];
        [entity setValue:[NSString stringWithFormat:@"%d",i] forKey:@"name"];
        [entity setValue:[NSNumber numberWithInt:i] forKey:@"value"];
    if (![context save:nil]) {
        NSLog(@"Couldn't save");
    If anyone can explain to me what is going on I'd be very grateful! This issue is the only only one holding up the release of my app. It works beautifully on the simulator!!
    Please let me know if there's any more info I can supply.

    Update: I modified the above code so that the fetch (and looppool etc.) take place when a timer fires. This means that the fetches aren't blocked in viewDidLoad.
    The result of this is that the issue happens exactly as before, but the applicationDidReceiveMemoryWarning is fired as expected:
    2011-06-08 09:54:21.024 renniksoft[5993:707] FREEMEM: 6131712
    2011-06-08 09:54:22.922 renniksoft[5993:707] Received memory warning. Level=2
    2011-06-08 09:54:22.926 renniksoft[5993:707] applicationDidReceiveMemoryWarning
    2011-06-08 09:54:22.929 renniksoft[5993:707] FREEMEM: 5615616
    2011-06-08 09:54:22.932 renniksoft[5993:707] didReceiveMemoryWarning
    2011-06-08 09:54:22.935 renniksoft[5993:707] FREEMEM: 5656576

  • Can not see warehouse management data screens for material while extending.

    I want to extend material for warehouse managment views.I can not see these views for the material in MM01.Looks like this is some thing to do with material type configuration.Can some one assist me how to do this?

    1)Check whether the material exist for that plant and storage location which is assigned to warehouse number .
    spro->enterprise structure->assignment->logistic execution->assign warehouse number to plant/sloc.
    2) Check in OMS2 tcode in the material type setting WM view is selected.

  • Report for List of Transfer orders in warehouse management

    hi,
    i want generate a report for list of transfer order orders in warehouse management
    is there any report with you guys kindly help me,
    or any standard report is there to display list of transfer orders in warehouse management
    Thanks,
    Rajesh
    Edited by: rajesh kumar kandagatla on Feb 11, 2009 9:27 PM

    Hi,
    If it is one time requirement, you can run the report LT23 and download the data to excel sheet and donwload material details in another sheet and you can match the temperature column in excel file.
    If it is permanent requirement, create a query and attach transaction code to that or write a seperate report for this requirement.
    Please let me know.
    Thanks
    Nagarajan

  • Q&A db for warehouse management and inventory management

    Hello Everybody,
    i read on the help.sap website that standard as well as industry specific versions of Q&A db are available. but the website doesnt say where. i searched a lot but the links dont lead to the actual Q&A db.
    i would like to request you to kindly share the Q&A db for inventory management and warehouse management with me as i need it for preparing the AS IS documentation.(preferably automotive industry but if not then even standard Q&A db is fine).
    thanks a lot.
    sapman.

    Now QADB will not help to map the clinets requirement. Instead of QADB get AS IS information form Coreusers... thats best practice now....
    Go through www.sap-img.com for further details...
    Edited by: Ganti on Jul 26, 2008 7:26 AM

Maybe you are looking for