Organizational structure in WM (Warehouse management)

Hi,
could You please explain me what is the organizational structure in WM?
Best regards

hi
plz follow the link , this will clear you about WM
http://help.sap.com/erp2005_ehp_03/helpdata/EN/c6/f838d24afa11d182b90000e829fbfe/frameset.htm
Reward points if helpful
Thanks and regards
Ravikant Dewangan

Similar Messages

  • Organization structure for Inventory management

    Hi All,
    I am looking for organization structure specific to inventory management and also data flow architecture.
    If there is any standard org structure is available please share with me.
    Regards
    Vijay

    I am looking for organization structure specific to inventory management and also data flow architecture.
    > If there is any standard org structure is available please share with me.
    Hi Vijay,
    Standard Org Structure for IM starts with Plants and ends with Storage Locations. You can create required no of storage locations under your plants, where plants are assigned to company codes. Its always better to copy from master plant 1000/0001 while creating the plants where you can make changes during creation where required (factory calendar etc).
    All the material movements within the plant happen between storage locations, material-material, special stocks-unrestricted stocks with no accounting effect.
    Movements between the plants can be planned wrt your needs such as STO with no financial postings unless you have plant wise PCA
    You can follow the standard avaiable structure for your IM org structure.
    Regards
    Shiva

  • Organizational structure iview

    good night.
    is posible that a manager can display an organizational structure iview and other manager can display others organizational structure iview in the page of general information??
    I enclosed in the box the field that i want use.
    [image|http://www.freeimagehosting.net/uploads/e31f2d26f2.jpg]
    regards

    Hi Juan,
    the view show is the employee selection - what the manager can see is restricted by their authorisations and depending on how you have configured the OADP selections used - on the root objects resolved for the manager and the selections that are used.
    There are many posts on the use of OADP (Object and Data Provider) - have a search and you should find something useful.
    Cheers,
    Chris

  • Bare minimum configuration for warehouse management

    Hello,
    For one of our Projects, there is a requirement of Warehouse Management merely just to enable the tracking of Material received to the Storage Bin level, as they manage the Inventory in Storage Bins in the existing Warehouses.
    Other no major requirement is expected from WM like, automation of Putaway, etc.
    Few of the Inventory scenarios are like Goods receipt, Goods Issue, Warehouse to Warehouse transfer, Bin to Bin transfer, Physical Inventory,  Subcontracting for repairs, Vendor Consignment, also they will handle Project Special stock.
    Now the configurations for Inventory Management are enabled for all the above processes. I now need to know, what are the bare mimimum configurations required so as to enable the WM related process, following each of the IM processes, like Putaway after Goods Receipt, Stock removal before Goods Issue, etc.
    The Configuration for the Enterprise Structure to support Warehouse Management have been completed by creating the Warehouses & assigning the Storage locations to these Warehouses.
    A detailed step by step process would be very helpful for me at this stage.
    And i surely will assign points for all the useful answers.
    Regards,
    Zafar.

    Hi,
    If you want to define new storage types other than the standard ones, please define them. Otherwise, you can assign
    the existing storage types to the newly defined warehouse.
    Also you have to define storage bin types and storage bin structures.
    All this you can find under the IMG path:
    SPRO->Logistics Execution->Warehouse Management->Master Data.
    Regards,
    Pavani.

  • TIME MANAGEMENT AND ORGANIZATIONAL STRUCTURE

    Good afternoon,
    We are going to customize the Time Management (PT) and the Organizational structure (OM) modules in SAP version ECC 6. At the moment we have installed an configured a lot of SAP modules: Personal Administration (PA), Payroll (PY), besides other modules not related directly with HR like PM, MM, IS-U, etc.
    We need::
    - To be able to define the organizational structure of the company with every work unit, inside every work unit locate the employees with their functions and positions, etc.
    - To know the number of employees that are avalaible for a service requirement (PM module)
    - To manage with SAP all the absences when the employees don't go to work.
    We have had training of some official courses but I think that they are not enough to achieve the goal, I think we need some kind of guide.
    Do you know if exists any consult SAP note or other kind of document where it's explained the steps or the good practices for the customization of these SAP modules (OM, PT).
    Thanks in advance,
    Julian Olmo

    Hi,
    SAP customers and partners can download SAP Best Practices from the SAP Software Distribution Center on the SAP Service Marketplace (http://service.sap.com/swdc) or order via their contracts department. SAP Best Practices are provided  free of charge.
    For downloading SAP Best Practices, customers and partners require a valid S-User ID. For more information about obtaining an S-User ID, see SAP Note 1037574
    You can check whether PT and OM best practice materials are available for your industry type and download.
    Regards
    Chandrashekar

  • Organizational structure Management by BAPI

    Hello,
    We want to maintain (Create/Change/Delete) the Organizational structure
    by BAPI.
    Make all the Staff assignments in the Organization Unit and its Positions.
    In other words we want to use all the PPOME transaction actions, by BAPI
    or something else.
    Can any one help us with suggestions ?
    Thanks in advance.
    Gilad.

    Hello Suresh,
    Thanks, it works!
    Gilad.

  • Organization structure for Case study .... need yr advice

    Hi …I am in process of preparing an org structure for one of the company.
    The company operations is like ….
    The company has four factories in different locations and have 3 Regional distribution centers (RDC) across india. Each distribution center has 5 branches (Sales Offices), in this way they 15 Sales offices across India.
    Most of the materials are procured by factories independently while some materials are centrally procured. Factories produce Finish goods and they are either sale to customer directly ( big regular customers) , or transferred to RDC to cater the requirements of other MID size customers and the other possibility to transfer it to Branches for Retail customers. RDCs also transfer FG to Branches.
    All factories , RDC and branches have warehouse facility , however branches have limited warehouse facility as the customers supported by them are very few and generally deliveries are made directly from RDC / Factory.
    They also have one R&D department in another location to develop new products and material is generally transferred from factories to R&D department.They also have one project division at the same (R&D) location which handles commissioning of new plants and procurement of capital goods.
    Raw Material , Semi finish and FG are transferred between factories and FG material is also transferred between RDCs.
    The group also has another Company which produces another line of products. RDCs and Branches of first company also work for second company (which means same RDC can store FG produced by both companies) and also Branches can also have FG material of both companies. Second company doesn’t have any specific R&D or capital division and R&D and capital of first company also work for second company.
    Inter company transfer between both companies is a regular practice.
    > Proposed Org structure
    Company – Group Company
    Company Code – First company and Second company
    Factory Configurations
    For first company
    4 Factories will be 4 plants
    Factories Structure (Storage locations / warehouses and storage type)
    Since factories have different type of material ( like FG , Raw material , WIP ) therefore I am confused what option I should select 
    1) 3 storage location ( for each plant) and one warehouse, 1 storage type
    2) 1 storage  location and three warehouses (I think this is not possible in SAP , not sure ?? )
    3) 1 storage location , 1 warehouse and 3 storage types
    RDC structure
    RDCs have full fledged warehouse facility and therefore thinking of making them also as Plant. Every RDC will have 6 Storage locations , 1 for First company RDC itself, 5 for associated branches and I feel each “RDC storage locations” should be a associated to a separate warehouse also.
    ( Since both companies produce different set of products therefore they will have different material and hence thinking of handling products of both companies in same plant and same storage location and warehouse , may be two storage type/area can be defined to differentiate material of both companies.)
    Branches: Will be storage locations under RDC …..
    While making branches as Storage location …. I have another question about valuation , since material from Plant and RDC is being transferred to Branches and  from there it is distributed to customers therefore the valuation of FG at BRANCH and RDC should be different as transportation cost , packing , unpacking etc cost should get added at Branch level.
    Therefore in case I make branch as Storage location , I will miss the valuation part while if I make them as Plant then there will be lot of documents get generated for each movement. Hence not sure for what option I should go.
    R&D:
    Since R& D department is involved in testing in New Product development and generally material is required to be scrapped after testing therefore thinking of making it as Plant with one storage location and may be here I don’t need any warehouse (WM) here.
    Project Division
    Project division may also be a separate plant with one storage location and NO WAREHOUSE is required to linked with it.
    Purchase Organizations
    4 purchase organizations for each plant respectively and 1 centralized purchase Org for central procurement.
    Your all valuable inputs are welcome .... looking foward to have a best possible configuration for above mentioned case study.
    Regards

    Phew... long long question
    The rule I generally follow is that the org structure should map reality.
    Company code - where Balance Sheet and Profit and Loss are prepared at the end of the year. If an entity does not do this, it is not a company code.
    Plant
    1) Each manufacturing facility is a plant (could be in 1 location or separate).
    2) Each separate location is a plant (even if it only stores goods). May be an overkill, but helps when legal requirements change or the location is upgraded.
    So in your case, RDC will be a plant (may be more than 1 if necessary). R&D should be a separate plant without warehouse management
    Storage location
    The only rule I follow is that there should not be any overlap of storage locations. So physically, any area of say 1 square foot should belong to one and only one storage location. Otherwise there is a lot of confusion during physical inventory. So logical locations are a no-no.
    I usually use a lot of storage locations.
    Don't have a warehouse spanning multiple plants (even though it is allowed).
    Purchasing organizations
    Have one for each location of purchase. If there is a team sitting in each plant procuring for only that plant, have it as a separate purchasing org (not strictly necessary, but makes authorization simple). For central purchasing, a central purchasing org should do nicely...
    Hope this helps,
    Lakshman

  • 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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:
     Picking  Shipping  Logistic Execution IMG Menu IMG   Define control parameters and number ranges for the warehouse numberLean WM  Define control parameters and number ranges for warehouse no.(double 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 or several fixed storage bins
    a goods issue area (as destination storage type) for deliveries
    an interim storage area for differences
    Procedure
    1. Access the activity using one of the following navigation options:
    IMG  Define Storage Lean WM  Picking  Shipping  Logistic Execution 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:
     Picking  Shipping  Logistic Execution IMG Menu IMG  Define Doors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:
     Lean WM  Picking  Shipping  Logistic Execution 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:
    IMG Menu IMG  Define Picking Lean WM  Picking  Shipping 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:
     Picking  Shipping  Logistic Execution IMG Menu IMG   Define Transfer Type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 storage bin
    Fixed bin coordinate
    Control indicator for processing, confirming, and printing transfer orders
    Confirmation info
    Procedure
    1. Access the activity using one of the following navigation options:
     Lean WM  Picking  Shipping  Logistic Execution 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IMG Menu IMG   Define Difference Lean WM  Picking  Shipping 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:
    Assignment Enterprise Structure IMG Menu IMG  Assign warehouse No. To plant/storageLogistic Execution  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:
     Logistic Execution IMG Menu IMG   Control Plant / Storage Location / Warehouse Lean WM  Picking 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:
     Shipping  Logistic Execution IMG Menu IMG   Assign Picking Location Determine Picking Location 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:
    IMG Menu IMG   Define Print Lean WM  Picking  Shipping 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:
     Logistic Execution IMG Menu IMG   Define control parameters and number ranges for Lean WM  Picking Shipping   Maintain number range intervals for transfer orders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:
    IMG Menu IMG  Define control parameters Lean WM  Picking  Shipping Logistic Execution   Maintain number range intervals for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

  • 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.

  • Problems assigning BP to a position in the organizational structure

    I tried to assign a bp to a position in the organizational structure,
    but I receive this message "Object cannot be assigned to object CliC
    Agent in the period 21.12.2006 - 31.12.9999".
    Also, I notice that in the screen, the checkbox where i can select for
    the business partner is missing.
    However, I can assign a user to the org structure.
    Before upgrading, it was working. This is the support packages that it was in.
    SAP_ABAP: Level 9
    SAP_BASIS: Level 9
    PI_BASIS: Level 9
    SAP_AP: Level 6
    BBPCRM: Level 6
    After the upgrade to the following,
    SAP_ABAP: Level 10
    SAP_BASIS: Level 10
    PI_BASIS: Level 10
    SAP_AP: Level 7
    BBPCRM: Level 7
    The assigning of business partner to a position no longer works.

    Hi,
    we're facing exactly the same problem, it was all going well until we went on production.... we applied note 997009 which results in a different error... did you manage to find a solution yet ?
    Regards,
    Jacob.

  • Organization structure in CRM 7.0 from ECC and HR

    Hi,
    We are trying to download Org structures from ECC and HR. (CRM 7.0, HR & R/3 ECC 6.0)
    From HR
    The ALE distribution is set across the systems CRM and HR and I did the PFAL run as per the best practices BB C05. There are about 100,000 Idocs inbound to CRM system and out of which about 15K are in 51 status and the rest are in 53 status.
    Observations:
    The Organization structure from HR is not totally mapped in CRM but only a part of it is displayed in PPOMA_CRM.
    The remaining Org units are found in 'non-related objects' selection.
    All the Idocs in failure are in error "Error in subroutine read_namtb for structure  of infotype  ". When I go to the long text
    Message no. 5-109
    Diagnosis
    An error has occurred in subroutine read_namtb for structure  of infotype .
    Procedure
    Check the entry for infotype  in table T777D (structure, IDoc segment, expanded structure) and the corresponding structures.
    I am not sure which infotype needs to be checked in T777D.
    From ECC
    The CRM - ECC connectivity is set. Downloaded all the required customizing objects successfully. Switched the org model to "enhanced backend integration version " and then followed on to SPRO->CRM->Master Data->Organizational Management->Data transfer->Copy SAP ECC structure and selected all the available R/3 Organization assignments available and then selected the "generate selected lines".
    Observations:
    All the generated org units are in GREEN in SPRO but there are no assignments found in PPOMA_CRM not even in the unrelated objects
    Checked tables HRP1000 and HRP1001 from the CRM Sales org unit IDs (ex: O 5000012) created here and they are not found but the generation is in GREEN.
    I will appreciate any assistance I get here.
    << Moderator message - Everyone's problem is important >>
    Regards,
    DT
    Edited by: Rob Burbank on Oct 20, 2010 4:25 PM

    Hello DT,
    Could you please let me know the process how the problem is solved..
    even we are having the same issue like, we have downloaded the Org Model form HR to CRM system, till here it was fine.
    when we are trying to download the ECC sales structure(CRMC_R3_ORG_GENERATE) to CRM system, i have selected all the items and triggered the Gerenerated Selectd Lines, but after all the items are generating in a error with RED.
    Could you please share you knowledge, so that it will help me in figuring out the issue.
    Thanks in Advance DT. Hope you reply back.
    Regards,
    Ven

  • 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

  • Set up the Organizational structure for MSS scenario

    Hi!
    I would like to set up the Organizational structure for MSS scenario within SAP Portal.
    Question:
    1) How to set up/map real user from SU01 to Manager? (tcode, report)
    2) How to mark them as 'Chief' (tcode, report)
    3) How to be sure that PA & OM are configured correctly and the integration switch is on?
    Which SAP course or SDN blog describes this?
    Thank you very much!
    regards
    Jürgen

    How to be sure that PA & OM are configured correctly and the integration switch is on?
    Check It000 and IT0001 here u will get objects from OM and PA  (position ID , Job Key, organisational Key)
    and integration switch
    check plogi orga , plogi plogi , plogi perli  in V_T77s0
    Edited by: Sikindar on Feb 10, 2009 6:53 PM

  • Warehouse Management User Manuals

    Dear Friends,
    Can you please forward me some user manuals for Warehouse management.. urgently needed for training purposes ?
    I will be very grateful.
    thnks
    nandu

    Hi Nandu
    Please refer this link attached and all the branches under this tree structure. This should give you almost everything in Warehouse Management "
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/c6/f8386f4afa11d182b90000e829fbfe/frameset.htm
    Hope you find this worthful
    Regards
    Vinayak.M.G.

  • Organization Structure level

    Hi All,
    I know this is a fundamental question, so guide me if this is not the right place.
    I am new to HCM and am trying to get my fundamentals right. I have been reading a lot about organization structure and organization plan. In real life scenarios when we create an organization structure, is it created at a company code level or enterprise (client) level. Bottom line, is there only one organization structure created per client or multiple?
    Thank you!
    Sudhir

    Hi Sudhir,
    Vishru and Vikrant have given you an excellent start.  I believe you are confusing some terms here - Company Code is determined by the Financial organization and refers to a group having their own set of books - general ledger.  There will be at least one Company Code per country but there may be more than one in a country if you have subsidiaries or divisions that keep their own general ledgers. 
    In HR the Organizational Structure shows who reports to whom.  This may cut across several Company Codes as the CEO may manage the heads of several subsidiaries each of which has their own P&L responsibility.  The structure then continues down in each subsidiary again showing who reports to whom.
    The Personnel Area and Personnel Subarea (Enterprise Structure) usually look at location and function - where a person works and their function in the company.  For example, all persons working at the Corporate Headquarters may be in the same Personnel Area if they are all at the same location.  But they may work in Fianance, HR, Purchasing, etc. which may be separate Subareas.  But each Personnel Area may be assigned to only one Company Code.
    The Employee Group and Subgroup (Personnel Structure)determine the type of pay and benefits the employee may receive.  Example, Salaried Employee, Hourly, Union Worker, Part TIme, Full Time, etc.  These will cross Company Code lines if they have the same benefits, work schedules, pay structure, etc. 
    What you must remember is that every employee has an assignment in the Enterprise Structure, Personnel Structure and Organizational Structure and these are all assigned in IT0001-Organizational Assignment. 
    Paul

Maybe you are looking for