De Centralized Warehouse - Contigency Plan

Hello, We are implementing DWM solution for a warhouse and seek help for contigency scenario. The scenario is as described below
a) Create a purchase order in the ERP system
b) Create inbound delivery in ERP system
c) Use a BAPI to distribute the delivery to DWM
d) Put away goods in DWM - post goods receipt
e) Confirm to ERP thru BAPI - were stock is posted at IM
the help required is
a) When the ERP system is not available (system is down) , what is the best practise to receive stock into DWM
b) Can we create inbound delivery in DWM system w/o refering to a purchase order
c) How can the stock be blanced when the ERP system is Up
We are looking for a contigency solution for both inbound & outbound delivery when the main ERP system link is broken
Regards
Prakash Govindarajan

Hi Prakash,
Using a DWM scenario gives you the functionality to process deliveries which are already in the DWM system after the ERP system connection is broken. From past business experience you will need to do some coding to keep everything "in one basket" to keep the 2 systems in sync when you want to start your main processing from the DWm system. remember that the DWM system is pure a stock system.
We use our best business practices as follow: 1st Make sure that the ERP system and connection to DWM is 100% configured and DRP processes are in place. If the ERP system goes down, then the WH can continue with the work load (deliveries already distributed) it's got. NO NEW documents will be created from the DWM side.
Because we are a manufacturing (yes, with lots of sales as well) company, we did a custom development to start a production intake from DWM side, but then use std ERP transactions to counter the transactions and thus keep evrything tidy and in sync.
Having to systems you will need to keep number ranges, auth's, config, etc in place...all double work.
See the following recent thread:
[Decentralised WM some clarifications;
See also this online document (if you've got auth):
[http://www.scmexpertonline.com/article.cfm?id=3594]
I hope I could help,
Hein
Edited by: Hein Botha on Mar 23, 2011 10:25 PM

Similar Messages

  • Best practice for centralized material planning in distributed environment

    Hi All- Hope everybody is doing fine. Things are going fine,at my end.
    We are debating on the organization hierarchy decision at our current utilities client. We are proposing that:
    1)     We will have central warehouse as plant/storage location/warehouse.
    2)     Create one plant (it will be virtual only) and 65 storage locations. Plant maintenance orders will be created at the storage location and it will generate the reservation at the plant level. This reservation will be converted into STO during MRP run. Central warehouse plant will use this STO to create the outbound delivery and then the shipping documents. APO will be ok with arrangement as all the requirements are centralized. Now my problem is, the reservation doesn’t have any delivery address to copy it in the STO. To populate the delivery address automatically, I believe we will need the modification / enhancement. Am I right? If this is right then what type of modification we will require? I mean effort wise (hours etc.) & time wise.
    ANy help is highly appreciated.
    best regards,
    KHAN

    Hi,
    If all 65 storage locations are going to be just different areas within the same physical site (address) then that should be OK, but if any of those storage locations have a different site address to the others then I would suggest that they should be Plants and NOT storage locations.
    The reason you are having problems with addresses is that in a Plant to Plant reservation the plants have different addresses.
    PLEASE don't use storag locations for different sites, if you DO then this will only be the first of MANY modifications that you will have to do.
    Yes there will be more master data if they are all set as plants, but how many times does master data change compared to how many receipts, issues and transfers etc. will occur. I would rather compromise on the master data maintenance than have to compromise on EVERY movement.
    I can't stress this strongly enough, if you use storage locations when you should be using plants you WILL lose major functionality and the SAP implementation will be seen as a poor one.
    I have seen many implementations at first hand where this has been the one influencing factor that has resulted in a poor implementation instead of a good one.
    Steve B

  • In wms difference between lean warehouse and central warehous

    hi
    this is very important that could any body tell me
    what is lean warehouse
    what is centeral warehouse
    what is the differe

    Hi
    Lean ware house can also said as clean warehouse
    here the basic difference between central WH is the material is always stored in  or inventory is maintained in FIXED storage bins
    Always the material is kept in FIXED storage bins
    That is Picking area is fixed
    This will have the organizational structures mainly Warehouse no,storage type,Picking area(fixed storage bins),doors and staging area
    But a Central warehouse has random storage bins
    Apart from all the organizational structures mentioned in lean it will also have storage sections ,reserve storage bins,strategies for picking like LIFO and FIFO,replinishment and inventory at storage bin level
    WH is big concept in SAP and there is a separate forum SCM LOGISTICS EXECUTION here
    Pls post it there
    You will get more inputs
    Regards
    Raja

  • About Warehouse?

    Hi frds
    what is mean by warehouse and give table and field name of warehouse ?
    thanks,
    Pari Vendhan.R

    SAP WMS - Decentralized Warehouse Management System Integration Setup
    You can operate the SAP Warehouse Management System (WMS) as a stand-alone decentralized system that is independent of a central Enterprise Resource Planning (ERP) System.
    You make the necessary settings for the ERP (Enterprise Resource Planning) system within the WMS component (Warehouse Management System).
    The steps are set up as a checklist and guide you through the process of configuring the system parameters.
    Checklist (For those with the Table Views used transaction code SM30).
    1. Customizing for "Enterprise Structure"
    Create storage location in OX09 (if necessary).
    Define warehouse number in Views V_T3001.
    (you should not copy the warehouse number in the ERP system)
    Activities within a warehouse, like goods movements and physical inventory, are assigned to a specific
    warehouse number.
    The physical warehouse where these activities take place is identified by the warehouse number.
    Assign plant/storage location to warehouse number in Views V_T320.
    (Valid if the component MM-IM (Inventory Management) is implemented.)
    Fields : Plant + Sloc + WhN
    2. Customizing for "Decentralized WMS integration", section "Central processing" -> Application
    Activate decentralized WMS in Views V_T340DM.
    Define interface to Inventory Management in Views :-
    V_156S_WM - Assign WM movement type references to IM movement types
    V_T3211 - Delivery-Relevant Parameters for Reference Movement Type
    V_T340DL - Delivery-Relevant Data for Warehouse Number
    Exclude stock in decentralized WMS in Views V_T321B
    (if the decentralized WMS is not an SAP R/3 system)
    Finally do a consistency check for decentralised WMS in transaction OL20.
    3. Customizing for "Application Link Enabling (ALE)", section "Basis Components"
    Maintaining Logical Systems in Views V_TBDLS.
    Assign logical system to client in Views T000.
    4. Make basic settings for RFC in transaction BD97.(if necessary)
    5. Customizing for "Application Link Enabling (ALE)", section "Maintain Distribution Model"
    You can define the Reduce message types and Activate message types in transaction BD53.
    SAP recommends that you use message types :
    "MATMAS" (material master tables) and
    "DEBMAS" (customer master) as a template.
    Be aware that only those fields that are absolutely necessary are transferred from the master data tables in
    the ERP system to the decentralized WMS.
    6. Customizing for "Decentralized WMS integration", section "Central processing" -> Distribution
    Use transaction OL19 to generate distribution model. As far as the application is concerned, when the model
    is generated, application-specific Customizing parameters are modified or set (for example, activate
    decentralized WMS).
    Display or check distribution model
    Generate partner profile in transaction BD82.
    (you can also perform this activity using ALE Customizing)
    Distribute distribution model in transaction BD64 (model view) using menu item "Edit"
    If both the ERP system and the decentralized WMS are SAP R/3 systems, the distribution model should be
    distributed on a central basis only, that is, via the ERP system.
    7. Customizing for "Application Link Enabling (ALE)", section "Maintain Distribution Model" (transaction BD64)
    Activate the change pointers for master data distribution using transactin BD61.
    If necessary, reduce the message types concerned with transaction BD53.
    8. Customizing for
    "Logistics - General" - "Material Master" - "Tools" - "Data Transfer : Material Master" -
    -> "Define required-field check for ALE/Direct Input" (Views V_T130S)
    Define whether an error message should be generated in the receiving system for required fields
    from the material master.
    <REMOVED BY MODERATOR>
    Edited by: Alvaro Tejada Galindo on Feb 14, 2008 2:32 PM

  • T-codes for warehouse management

    hi.
    can anybody gives the mostly used t-codes for warehouse management

    SAP WMS - Decentralized Warehouse Management System Integration Setup
    You can operate the SAP Warehouse Management System (WMS) as a stand-alone decentralized system that is independent of a central Enterprise Resource Planning (ERP) System.
    You make the necessary settings for the ERP (Enterprise Resource Planning) system within the WMS component (Warehouse Management System).
    The steps are set up as a checklist and guide you through the process of configuring the system parameters.
    Checklist (For those with the Table Views used transaction code SM30).
    1. Customizing for "Enterprise Structure"
    - Create storage location in OX09 (if necessary).
    - Define warehouse number in Views V_T3001.
    (you should not copy the warehouse number in the ERP system)
    Activities within a warehouse, like goods movements and physical inventory, are assigned to a specific
    warehouse number.
    The physical warehouse where these activities take place is identified by the warehouse number.
    - Assign plant/storage location to warehouse number in Views V_T320.
    (Valid if the component MM-IM (Inventory Management) is implemented.)
    Fields : Plant + Sloc + WhN
    2. Customizing for "Decentralized WMS integration", section "Central processing" -> Application
    - Activate decentralized WMS in Views V_T340DM.
    - Define interface to Inventory Management in Views :-
    V_156S_WM - Assign WM movement type references to IM movement types
    V_T3211 - Delivery-Relevant Parameters for Reference Movement Type
    V_T340DL - Delivery-Relevant Data for Warehouse Number
    - Exclude stock in decentralized WMS in Views V_T321B
    (if the decentralized WMS is not an SAP R/3 system)
    - Finally do a consistency check for decentralised WMS in transaction OL20.
    3. Customizing for "Application Link Enabling (ALE)", section "Basis Components"
    Maintaining Logical Systems in Views V_TBDLS.
    Assign logical system to client in Views T000.
    4. Make basic settings for RFC in transaction BD97.(if necessary)
    5. Customizing for "Application Link Enabling (ALE)", section "Maintain Distribution Model"
    You can define the Reduce message types and Activate message types in transaction BD53.
    SAP recommends that you use message types :
    "MATMAS" (material master tables) and
    "DEBMAS" (customer master) as a template.
    Be aware that only those fields that are absolutely necessary are transferred from the master data tables in
    the ERP system to the decentralized WMS.
    6. Customizing for "Decentralized WMS integration", section "Central processing" -> Distribution
    Use transaction OL19 to generate distribution model. As far as the application is concerned, when the model
    is generated, application-specific Customizing parameters are modified or set (for example, activate
    decentralized WMS).
    Display or check distribution model
    Generate partner profile in transaction BD82.
    (you can also perform this activity using ALE Customizing)
    Distribute distribution model in transaction BD64 (model view) using menu item "Edit"
    If both the ERP system and the decentralized WMS are SAP R/3 systems, the distribution model should be
    distributed on a central basis only, that is, via the ERP system.
    7. Customizing for "Application Link Enabling (ALE)", section "Maintain Distribution Model" (transaction BD64)
    Activate the change pointers for master data distribution using transactin BD61.
    If necessary, reduce the message types concerned with transaction BD53.
    8. Customizing for
    "Logistics - General" - "Material Master" - "Tools" - "Data Transfer : Material Master" -
    -> "Define required-field check for ALE/Direct Input" (Views V_T130S)
    Define whether an error message should be generated in the receiving system for required fields
    from the material master.
    Reward points if useful.

  • Define Warhouse number or Copy standard warehouse number?

    Hi
    I am in situation where we are in a client replication project ( two different clients move in to one already existing client ).
    Client 1 - has no WM settings ( 3 different plants for different company codes ) - US
    Client 2 - has WM settings ( plant 221 for  company code 221 ) - US
    I am reconfiguring the whole setup in the Client 1 for plant 221 for WM settings.
    I am planning to define  the warehouse number and assigning the plant/storage location (221/009) for the same.
    If i copy from standard warehouse number 001 ( Germany ) it will copy the region.
    I dont see any option of removing region Germany for my ware house if i do so...
    I know this is very trivial question but i donot want to proceed with out procedure.....
    ( Usually in case of Plant copy in MM we remove all standard settings of DE for the created one, but in case of ware house no i do not see any thing )
    Since 001 Central warehouse is not connected to any plant i can copy that so that all tables get copied but how to remove the region?
    Please suggest
    Regards
    Rudresh K
    Edited by: Ravi Rudresh on Aug 18, 2009 10:06 PM
    Edited by: Ravi Rudresh on Aug 18, 2009 10:08 PM
    Edited by: Ravi Rudresh on Aug 18, 2009 10:09 PM

    Hi Anna Durai
    It works and it removes the Region Code. Thanks for your suggestion on this...
    I have one more  question ,
    Do you copy 001Central warehouse  or we can define our own ware house number?
    We have two options in Enterprise structure - LE-Define, copy, delete, check warehouse number
    Define warehouse number
    Copy/delete/check warehouse number
    Is the Region code required only hazardous materials or it has any impact on structure ....
    As my understanding the Central Warehouse 001 is not assigned to any plant.
    Regards
    Rudresh K

  • Error while running ETL Execution plan in DAC(BI Financial Analytics)

    Hi All,
    I have Installed and configured BI Analytics and everything gone well but when I run ETL in DAC to to load the data from source to Analytics Warehouse Execution plan Failed with the following error message - Error while creating Server connections Unable to ping repository server.can anyone please help me on resolving the error.and here is the error error description.
    Error message description:
    ETL Process Id : 4
    ETL Name : New_Tessco_Financials_Oracle R12
    Run Name : New_Tessco_Financials_Oracle R12: ETL Run - 2009-02-06 16:08:48.169
    DAC Server : oratestbi(oratestbi.tessco.com)
    DAC Port : 3141
    Status: Failed
    Log File Name: New_Tessco_Financials_Oracle_R12.4.log
    Database Connection(s) Used :
         DataWarehouse jdbc:oracle:thin:@oratestbi:1521:DEVBI
         ORA_R12 jdbc:oracle:thin:@oratestr12:1531:DEV
    Informatica Server(s) Used :
    Start Time: 2009-02-06 16:08:48.177
    Message: Error while creating Server connections Unable to ping repository server.
    Actual Start Time: 2009-02-06 16:08:48.177
    End Time: 2009-02-06 16:08:51.785
    Total Time Taken: 0 Minutes
    Thanks in Advance,
    Prashanth
    Edited by: user10719430 on Feb 6, 2009 2:08 PM

    I am facing a similar error.. can you pls help me in fixing it.
    Following is the log from DAC server:
    31 SEVERE Fri Oct 16 17:22:18 EAT 2009
    START OF ETL
    32 SEVERE Fri Oct 16 17:22:21 EAT 2009 MESSAGE:::Unable to ping :'ebsczc9282brj', because '
    =====================================
    STD OUTPUT
    =====================================
    Informatica(r) PMCMD, version [8.1.1 SP5], build [135.0129], Windows 32-bit
    Copyright (c) Informatica Corporation 1994 - 2008
    All Rights Reserved.
    Invoked at Fri Oct 16 17:22:20 2009
    The command: [pingserver] is deprecated. Please use the command [pingservice] in the future.
    ERROR: Cannot connect to Integration Service [ebsczc9282brj:6006].
    Completed at Fri Oct 16 17:22:21 2009
    =====================================
    ERROR OUTPUT
    =====================================
    ' Make sure that the server is up and running.
    EXCEPTION CLASS::: com.siebel.etl.gui.core.MetaDataIllegalStateException
    com.siebel.etl.engine.bore.ServerTokenPool.populate(ServerTokenPool.java:231)
    com.siebel.etl.engine.core.ETL.thisETLProcess(ETL.java:225)
    com.siebel.etl.engine.core.ETL.run(ETL.java:604)
    com.siebel.etl.engine.core.ETL.execute(ETL.java:840)
    com.siebel.etl.etlmanager.EtlExecutionManager$1.executeEtlProcess(EtlExecutionManager.java:211)
    com.siebel.etl.etlmanager.EtlExecutionManager$1.run(EtlExecutionManager.java:165)
    java.lang.Thread.run(Thread.java:619)
    33 SEVERE Fri Oct 16 17:22:21 EAT 2009
    *     CLOSING THE CONNECTION POOL DataWarehouse
    34 SEVERE Fri Oct 16 17:22:21 EAT 2009
    *     CLOSING THE CONNECTION POOL SEBL_80
    35 SEVERE Fri Oct 16 17:22:21 EAT 2009
    END OF ETL
    --------------------------------------------

  • Same warehouse for different company codes

    Hello Guru's
                     is there a possibility in WM , considering decentralized WMS to create a warehouse which can be managed by two different company codes.
    thanks a lot for ur suggestions

    yeah i do understand that warehouse is connected to plant and we can also have one warehouse to two plants and manage the inventory but in my company case, we manage the inventory of two different company codes in one warehouse by their legacy systems, so i was wondering how to map that in SAP.
    In the centralized warehouse as far as i know i dont think we can assign the warehouse to 2 different company codes but i was wondering can we do that in decentralized warehouse.
    thanks for the reply

  • Set Availability Check to Exclude Planned Order

    Hi All,
    anyone know how to set the availability check so it will not include the planned order in the calculation ?
    I find one setting in SPRO, the path is :
    Sales & distribution ==>  Basic functions ==> availability check and Transfer of Requirements ==> Availability Check  ==> Availability Check with ATP Logic or Against Planning ==> Carry Out Control for Availability Check
    select one of the record, and update filed "Incl. Planned Orders".
    I've uncheck that field, but I can't get the appropriate result. When I create a new sales order, the availability check still take the planned order I created before into account.
    The problem is, my user want to prevent creating delivery before the goods are already put in the stock. So the planned order should not be considered in the availblity check.
    Thank you in advance
    Rudy

    Hi Rudy,
    Concept of availability check is to verify if the stock is available at the time of creation of sales order. If available, when it can be ready for delivery (as Packing, arranging for transportation, etc may have lead time) & if not available, when it would be available considering Packing, arranging for transportation, etc lead time.
    Availability check whether material is available on required delivery date (backward scheduling) or not. If not available on required delivery date, system will propose next available date (forward scheduling)
    1.     Define Checking Groups
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Checking Groups
    You define checking groups with which you specify the type of requirements records the system is to create when processing sales orders or deliveries
    2. Define Material Block for Other Users
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Material Block for Other Users.
    3 .Define Checking Groups Default Value
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Checking Groups Default Value.
    4. Carry out Control for Availability Check
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Carry Out Control for Availability Check.
    5. Define Procedure by Requirements Class
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Procedure by Requirements Class.
    6. Define Procedure for Each Schedule Line Category
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Procedure for Each Schedule Line Category.
    7. Determine Procedure for Each Delivery Item Category
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Determine Procedure for Each Delivery Item Category.
    8. Checking Rule for Updating Backorders
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Checking Rule for Updating Backorders.
    9. Define Default Settings
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Default Settings.
    Availability checks
    1. Availability check is an integral part of the business process that determines if the required delivery quantity can be met on a required delivery date. For this purpose the system takes into account pre-delivery activities such as scheduling for picking or packing times and the time taken to produce or obtain the material. It also performs several background functions such as Backorder processing, rescheduling and ATP quantities.
    2. Backorder processing: processing of a sales order that has not been fully confirmed or not confirmed at a certain delivery date.
    3. Rescheduling: is a proposal of how – confirmed quantities already assigned to a sales order can be reassigned to other sales orders that have a higher priority.
    4. Available to promise (ATP): is a process of checking the available quantities of a material. The ATP quantity consists of warehouse stock + planned receipts (incoming stock) – planned issues (outgoing stock). to examine stock on hand (CO09) proceed to logistics – sales & distribution – sales – environment – availability overview.
    5. Replenishment lead time (RLT): is the time taken for the material to become available either internally (in house production) or externally (from a vendor). The most important things to consider during an external procurement are purchasing and MRP 2 (procurement) views of MMR where the processing time for purchasing, planned delivery time and goods receipt processing time are taken into account. On the other hand internal procurement is based on in house production time (MRP 2 view) goods receipt processing time or alternatively RLT time, which is found on MRP 3 view.
    6. RLT (Replenishment Lead Time) is the time taken for the material to become available. RLT is only used when doing an ATP check (Available To Promise). The value of RLT for a material is specified on material master record.
    7. There are three types of availability checks –
    Check on basis of ATP quantities.
    Check against product allocation.
    Check against planning.
    Configuring Availability check through Checking Groups –
    1. The checking group + checking rule determine how the availability check is to be performed.
    2. The checking group determines whether and how the system checks the stock availability and generates requirements for material planning. The checking group defines what type of requirements will be passed on i.e. summarized requirements (daily/weekly) or individual requirements for each sales order.
    3. The checking rule applies to how the availability check is to be carried out at the transaction level. Note that you must define checking rules for each individual application such as for production orders for example. In Sales and Distribution, the checking rule is specified internally within the system and cannot be changed.
    4. The checking rule, in conjunction with the checking group, determines the scope of the availability check for every business operation; that is, which stocks, receipts and issues are to be included in the availability check and whether the check is to be carried out with or without the replenishment lead time.
    5. Briefly explaining the above – checking group determines which type of requirement to be passed on to MRP whether it be individual or summarized and checking rule which is at the transaction level and can be configured independently for each application module, determines which stocks, receipts and issues to be taken into account. For performing an availability check checking group has to work in conjunction with checking rule.
    6. Advantages of individual processing over summarized processing –
    Backorder processing is possible.
    You can access (MD04) order, line and schedule line individually which gives a greater control on available stock and requirements placed on stock.
    The system automatically uses individual requirements in case of special stock items.
    7. Required data for the Availability check to be carried out –
    The Availability check must be switched on at the requirement class level.
    The Availability check must be set at the schedule line level.
    A requirements type must exist by which the requirements class can be found.
    A plant must be defined in the sales order for each schedule line item (in other words plant must be defined for every material in MMR).
    A checking group must be defined in the material master record in the MRP3 screen in the availability check field.
    8. Configuring Availability check and defining Checking Groups –
    Checking groups are introduced into the sales order based on the setting in the material master record.
    SAP standard checking groups are 01 – summarized requirements and 02 – individual requirements or you can create your own by copying the standard ones.
    Total sales and total deliveries columns are there to configure a checking rule to sum up requirements to post to MRP either individually or by day or week.
    Block quantity required can be set if you want several users to be able to process the material simultaneously in different transactions without blocking each other.
    The no check indicator is CHECKED when you DO NOT want the system to carry out ATP check.
    9. Defining material block for other users – the block check box is an indicator that enables you to block material master records of a particular material during the availability check and restrict other users from accessing same master record and reserve the material. If the block is not set, two users can confirm the same material at the same time for two different orders, not knowing if the stock is available or not. If you select this field, the material is blocked during the availability check and other users cannot: a) Make changes in the material master record. b) Create purchase orders for the material. C) Create orders for the material.
    10. Defining default values for checking groups - Checking groups are introduced into the sales order based on the setting in the material master record.
    However if there is no entry present in the material master record for the checking group, a default value can be set here, depending on material type and plant.
    This default value will be used by the system depending on the material type mentioned in MMR and plant in sales order.
    If an entry exists, this default value is over written by MMR.
    11. Controlling Availability Check – in this section, you tell the system what stock on hand and what inward and outward movements of stock it must take into account when performing the availability check in addition to whether or not to consider the replenishment lead time.
    12. These settings are based on the checking group that is assigned to the material master record and the checking rule that is predefined and assigned to the sales and distribution transaction.
    13. These settings carry out control both for sales order and delivery as well. This is due to the fact that you may want to include specific stock or incoming stock for the sales order, yet at the time of the delivery only include physical stock on hand waiting to be shipped.
    14. It is possible to indicate to the system that you would like the availability check NOT TO CHECK the stock at the storage location level. This indicator is used to set the scope of the availability check.
    15. It is used to switch off the check at storage location level. You create a reservation for a particular storage location. However, the scope of the availability check is set in such a way as to exclude the storage location. In this case, the system carries out the check at plant level only and does not take the storage location into account that is specified in the reservation.
    16. Should you not want the system to automatically check RLT, you may indicate so here. RLT is the time taken for a material to become available. It is only used when doing an ATP check and is taken from MMR.
    17. Defining the elements in the availability check entirely depends on the business needs, but a few tips are given under –
    When controlling the Availability check at the time of the sales order, a purchase requisition does not necessarily indicate by it is going to come into the plant.
    A shipping notification on the other hand - a confirmed purchase order – is a good indicator of receiving stock on a specified date.
    It is always recommended not to select the shipping notifications for the delivery requirements type as you may not actually receive the stock into plant or warehouse for which you are creating a delivery.
    Please Reward If Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • Federated warehouse

    Hi Experts,
    I have been able to build a warehouse with data from operational system so we can report on. We are just using ROLAP (all tables - no MOLAP yet - but I would like to use AW at some point. I am using Microstrategy as reporting tool.
    Now I have requirements to build federated warehouse. I need to aggregate data from operational systems in U.K office with operational system from the US. The customer dim is completely different between the two countries but for corporate analytics, I would like to have one giant customer dim (50 mill to start with).
    I am thinking about doing rollups to certain level in the U.K (warehouse there) and then bring down top few levels over to US warehouse. But this is not federated warehouse, this is central warehouse. Perhaps I could enforce same ETL processes in the UK to reduce the effort.
    Any suggestions on build federated warehouse ?. I am thinking distributed queries is bad. So I am leaning toward duplicating top few levels in both warehouses. I am not sure how microstrategy will deal with the metadata. Any suggestions
    Ofcourse: platform is 10g R2.
    Thanks a lot
    Vissu

    Hi,
    Only the OWB 2.1.x version is certified with Apps 11i. This means that if you want to extend the intelligence modules which are shipped with 11i, then you have create an OWB repository which understands 11i - this is done using the OWB 2.1.x BIS Repository assistant as against the normal OWB 2.1.x Warehouse Repository assistant.
    But, having said this, you can always install OWB 3i or OWB 9i independantly on the 11i 8.1.7 database (OWB 9i installs in a new home) and use it to connect to Apps tables, or any other tables elsewhere and do some OWB work !
    Cheers
    Deepak

  • Diff in functionality betwen centralised and decentralised Warehouse magmt

    Hi Gurus,
      Could anybody clarify the difference in functionality between centralized and decentralized warehouse management linked with inventory management in SAP System.
      mail me related doc or pdf to mai ID: [email protected]
    fFull points for answer
    regards,
    Venkatesh

    Hello Venkatesh,
    Functionality are same in centralized warehouse management and decentralized management, but is all about the volume of transactions, system performance and independency.
    The following document will give you very good idea about the decentralized warehouse management.
    http://www.catalystinternational.com/Content/Knowledge_Center/Downloads/whitepapers/dWM_Whitepaper.pdf
    Hope this helps.
    Regards
    Arif Mansuri

  • Copy a Warehouse number

    Hi,
    in SAP there is a standard Warehouse Number 001 Central Warehouse full, if I want to create a new one
    as copy of the above it is correct to copy al the entries related to 001 warehouse number ?
    My purpose is to avoid that some mvts won't work. I don't know if that is a good idea or not.
    Best regards

    Hi,
    It is always good to copy warehouse Number 001. The storage type search table for warehouse 001 also gets copied directly to the new warehouse. You need to change the search startegy to meet your requirements.
    Regards,
    Ramakrishna

  • Satellite warehouse for projects

    Dear All,
    i have an scenario for construction business, how we can manage satellite warehouses in MM for PS scenario like the client have central wahouse which is a storage location but its delivering the material to yard and then site and then from there they consume it on the project.
    kindly help me
    regards,
    qsm sap

    they are not issuing from the central warehouse but they are transferring from central to satellite warehouse and from satellite warehouse they issue to project, so how can i manage the satellite warehouse in MM because every time of new project its creating new satellite warehouses.
    regards,
    qsm sap

  • Which movement type to show Directly Procured material in stock?

    Hi All
    Is there another movement type that I can use to reverse from a network, Directly Procured material in to stock?
    Our issue is that we plan and have delivered directly procured material to out production plant (Plant A) and the PO has an account assignment of 'N'. The production team then decide (due to unforseen issues) that they do not need it anymore for that network/WBS and want to send it to our central warehouse (Plant B)
    In order to recover the cost from the network, we process MB1A mvt 222 with reference to the WBS in Plant A and then stock transfer to our central warehouse, Plant B
    My question is....can we use another movement type to remove the cost from the project/network/WBS and return the material in to stock?
    I don't want to reverse the PO but can i use that as a reference?
    Your help is appreciated
    Regards
    Darren

    MB1A transaction is a goods issue
    goods issues are valuated with the material master valuation price.
    in goods issues you cannot reference purchase orders (this is only possible in receipts)
    there is no goods receipt transaction for material which was already received against a PO.
    You credit the network with the leading price from material master, there is no value flow in the opposite direction. But you can control the valuation if you allow external value entry in the movement, which is usually not liked by auditors, especially as such movements are executed by warehouse personnel

  • Multiple shedule lines

    Multipul Schedule line in 1-line item-SO
    Dear Sir,
    I had created Sales Order 7063100174--8 line item and each line item
    having 10 schedule line for deifferent date.
    But if i will go for check item Availability all scheduled date will
    come to one date 05.09.2007(or current date if stock is not there) why
    system is removed my all 10 scheduled date.
    Regards
    vinod sunkari

    dear vinod,
    To confirm the quantities for a particular line item in the sales order on particular day system carried out transfer of requirements (TOR) & AVAILABILITY check, so has to confirm the quantity on particular day as system should know what are there requirement of the sale order and delivery with MRP then system carries out availability check function, to confirm the quantity on particular day. Depending upon the IMG setting system carries out availability check function based on 3 methods:
    A) Availability check with ATP logic or against planning:
    In ATP logic systems ATP Qty while carrying out availability check function for
    Particular line item (ATP qty=warehouse stock +planned receipts planned issues)
    Planned Receipts: EX: - purchase requisitions, purchase orders, stock in transfer stock at inspection etc.
    Planned Issues: - EX: - open sales order & open delivers
    B) Availability check against product allocation:
    Availability check can be carried out against product allocations in which system automatically restrict the user to confirm the quantity beyond reserved quantities per particular customer. EX:- Availability qty =100, existing orders=10,then system automatically distributes to items evenly to the sales order.
    C) Rule based Availability check:
    Rule based availability check can be carried out based on the business transaction.
    EX: - For normal sales order system has to carry out availability check for special sales order ex: - cash sales and rush order systems need not to be carry out availability check,
    In rule based availability check system in which system carried out Global availability to promise in all plants. In this check system transfers the requirements to APO system where GATP takes place and the result of the availability check transferred to R/3 system. This process takes place with the transaction code CIF(central inter face) inR/3.After carrying out availability check function system proposes(by using ATP logic) default values of ATP check  result to the user in a dialog box, in which system gives the  choice to the user to take the decision in contest of insufficient stock.
    i hope u understood..
    rewards pls
    siva

Maybe you are looking for