Availibility Overview

Dear all ,
What is the Availibilty overview?
What is the exact use of this Report ?
We use T code CO09 to see the availibility overview.
Please guide on it.
Best Regards,
Deepika

Hi
Availability Overview is used to check the material in ATP.
You can check in MD04, how much quantity is available on a particular date. It lists out all the expected receipts/issues date wise. So, for your requirement date, pls check teh availability in MD04.
Availbality Check is worked out based on the checking rule in SPRO. To see what are the checks done by the system, in CO09 click on Scope of Check.
A comprehensive Availability Overview takes into account the following:
Stock can include:
safety stock
stock in transfer
quality inspection
blocked stock
Inward/Outward movement of goods can include:
purchase orders
purchase requisitions
planned orders
production orders
reservations
dependent reservations
dependent requirements
sales requirements
delivery requirements
Revert back if you want more info.
Reg,
Ashok
Rewards Welcome

Similar Messages

  • Availability Overview in ME51N, ME52N, ME53N

    Hi,
    When I go to the menu path Environment -> Availability in transactions ME51N, ME52N or ME53N, nothing happens. The expected behaviour is the display of availability overview as in transactions ME21N, ME22N, ME23N.
    I found the same thing to happen in several SAP systems. What is the reason behind this strange behavior?
    Thank you.
    Helpful answers will be rewarded.

    Availability check only possible for stock transfer items

  • Unit of measure in availability overview

    Hi
    The question is about the possibility to change the unit of measure displayed in the availability overview during a sales order creation as you can do in transaction MD04.
    The problem is that if you set a quantity in the sales order in a alternative unit of measure (for instance Boxes) and if you check the availability, the systems shows the quantities in the base unit of measure (e.g. Pieces), so it is quite complicated to make the conversion, because you do not have the information on the screen.
    Has anybody solved that issue?
    thanks a lot!

    Hi,
           Check in material master.U can go to aditional data and give as box and save the material then it will ask u how many units for a box.Then check this hope it solves ur problem.
    RV

  • CO09 Availibility overview

    Hi all
    I am using CO09 for looking at availibility overview. It shows me the order reservations and material but not show the production order. Is there a way I can see the production order on the CO09 screen
    thanks a lot

    Dear John,
    Step1 :
    Please go to  the availability overview screen using T.code CO09.
    (Enter  the material number, plant, checking rule)
    Step 2:
    You can see that under ATP situation  heading :
    Date , MRP element , MRP element data , Rec/Req qty, confirmed , ***. ATP Qty
    Just double click the MRP element Prd. Ord then you can see the Prod. order Number with date and qty.
    If you want to see the Prod. Order details then copy the Prod. order number and using T.code CO03 to display the Prod. order .
    Hope it is useful for you .
    Thanks and Regards
    srinivas

  • Availability check on schedule lines of contract

    Hi,
    We have maintained 2 line items (L1 and L2) with same material (M1) in contract. Also these two line items have schedule lines maintained.
    e.g.
    L1  :  S1,S2
    L2 :   S3,S4
    Now we create a sales order in reference to line item L1 and do an availability check.  The ATP does not show schedule lines for S1,S2 in availability overview. only S3,S4 quantities is taken into consideration for ATP calculation.
    We have activated availability check at schedule line level.
    Any pointers as to why S1,S2 requirements are not shown in availability overview
    P.S.  If we create a sales order in reference to line item L2 ,then the ATP does not show schedule lines for S3,S4 in availability overview. only S1,S2 quantities is taken into consideration for ATP calculation.
    Any pointers will be highly welcome.
    Thanks.

    Hi,
    Sorry, for Sch. AV check is not activated but TR is activated.
    For material ATP is activated- check in MM03
    Chidambaram

  • Availability  check in Enjoy Purchase Order & Requisition

    Hi Experts,
    The availability check is used in 4.7E also but what is difference in Ecc 6.0 or new functionality added
    Can any one plz let me know
    Regards
    Pratap

    Below is capture from sap release documentation :
    Availability Check in Enjoy Purchase Order and Requisition
    (Changed)
    Use
    As of SAP ECC 6.0, SAP_APPL 600, display and checking of availability are invokable separately in the
    Enjoy purchase order and requisition in line with the system behavior on the Sales side.
    You invoke the display and checking of availability in the Enjoy purchase order (transaction code
    ME21N) and the Enjoy purchase requisition (transaction code ME51N) as follows:
    - To display the availability overview, choose Environment -> Availability
    - To check availability, choose the Check Availability icon.
    13.6.16.3 System Behavior After Availability Check for an Item (Changed)
    Use
    If you carry out the availability check for an item of a stock transport order, hitherto the system adopted
    confirmations as per the desired date/time only.
    SAP AG 30
    ______________________________________________________S_A_P_-S_y_s_te_m_
    As of SAP ECC 6.0, SAP_APPL 600, you can define in Customizing how the system reacts if the desired
    quantity cannot be confirmed for the desired date/time.
    You have a choice of two settings:
    - Confirmation as per desired date/time
    This is the standard setting and corresponds to previous system behavior.
    - Delivery proposal
    - Full confirmation
    Effects on Customizing
    You make the settings in the Rule for Adoption of ATP Results in Purchasing field in Customizing for
    Purchasing under Purchase Order -> Set Up Stock Transport Order -> Assign Delivery Type and
    Checking Rule.

  • Availability check issue in SD

    Hello everyone
    I am currently having some issues during the ATP in Sales Order in SD.
    We are using Check Group 02 - A (Sales Order) with the following settings:
    Stock Overview --- *all are unchecked*
    Relenishment Lead Time -- *"Check without RLT" is checked*
    Storage Location Inspection -- unchecked
    In/Outward Movement --- the following are checked
    Inc. Purchase Orders
    Include Reservations
    Include Sales Order req.
    Include Deliveries
    Rest all is unchecked
    Now on a high level, what this does is that hard allocates the required Order Qty to the Sales Order if stock is available.
    e.g. Material XYZ has 100 EA unrestricted stock
    Order for 10 EA ... is allocated 10EA
    Now if a second order comes in for 100EA .. it will allocate only 90EA
    Now I was able to test this successfully with a newly created material in our development system.
    Later I rejected all the Orders that I had created for this material in ECC.
    Thus now MD04 for that material displayed no requirement.
    Now again when I tried placing an order for this material ... it wouldn't confirm.
    When I check the Availability Overview from the Sales Order, it shows the following details
    Material -- XYZ
    Plant -       WXYZ
    Total Display
    Receipts - 100
    Issues -- 300                        Confirmed Issues - 100
    ATP Situation
    Date, MRP elm., MRP element Data,  Rec./reqd qty , Confirmed , ***. ATP
    02/23/2011 , Stock  , BLANK , 100, BLANK , BLANK
    02/23/2011 , SimReq , Simulated Requirement , (10-) , BLANK , 0
    02/24/2011 , CusOrd , Totals record , (300 -) , 100 , 0
    02/23/2011 , SLocSt ,  LOC1 , 0 , BLANK , 0       
    02/23/2011 , SLocSt ,  LOC2 , 100 , BLANK , 100
    Note:
    I have put the dashes to allign them correctly. Also (10-) means negative 10
    Plant WXYZ has 2 locations viz. LOC1 & LOC2
    Currrently the stock of 100 EA is in LOC2.
    ALso LOC1 is responsible to issue the stock to deliveries.
    Question:
    Why would the ATP confirm 0 qty inspite of the Orders placed for it have been rejected.
    Note this material was never ever used before in Sales Orders.
    Any thoughts
    Thanks
    Vin
    Edited by: vinit parkar on Feb 23, 2011 8:38 PM
    Edited by: vinit parkar on Feb 23, 2011 8:44 PM

    Hey Shiva
    That did not fix the problem.
    I ran the program with Data Transfer checked .. but still the same issue
    Any other thoughts ?

  • Availability check for Make to stock and Make to Order

    Dear All,
    Client is selling   Make to stock and make to Order material.
    How and what settings need to do for Avaialbility check.or we can use standard one.
    I hope in case of Make to Order availability check may not happen.
    Please correct me.
    Thanks in advance.
    Regards,
    Shrikant

    hi,
    yes for make to order we dont have AvChk.  for make to stock items u need to follow the
    below configuration.
    Availability check
    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 u2013 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) u2013 planned issues (outgoing stock). to examine stock on hand (CO09) proceed to logistics u2013 sales & distribution u2013 sales u2013 environment u2013 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 u2013
    Check on basis of ATP quantities.
    Check against product allocation.
    Check against planning.
    Configuring Availability check through Checking Groups u2013
    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 u2013 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 u2013
    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 u2013
    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 u2013
    Checking groups are introduced into the sales order based on the setting in the material master record.
    SAP standard checking groups are 01 u2013 summarized requirements and 02 u2013 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 u2013 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 u2013 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 u2013
    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 u2013 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.
    regards
    anand

  • Availability Check Problem

    Hello Folks
    I have a problem in availability check . When i raise a sale order for material A quantity 1500 and when i have 1000 quantity of material A in stock, there are two schedule lines, and on the order creation date there is 0 quantity confirmed even though 1000 quantity of Material A is available. Instead it creates a another schedule line where it confirms wholly the 1500 quantity.
    I have a necessity where i need to confirm 1000 material stock on the order creation date, and the rest 500should be confirmed on a later date. Have also checked with the config, i don't find anything wrong, Please advise me or guide me through how to handle this now !!
    Thanks in advance
    Cheers
    Vj

    Hi,
    1.If the material is already assigned to existing order, you can not assign it to other order.
    2.At the schedule line level, check item availability which will take u to availability overview screen..
    There selecet System Proposal push butto which will meet ur requirement..
    If u select one time push button, then you'll be getting only one schedule line with the 1000 qty.
    If u select full qty push button, then you'll be getting one schedule line with 1000 qty and remaining 500 qty will be in next schedule line date which can also meet ur req.
    If u select proposal, system will propose a date which will also meet ur req..
    Note that the material should be available at the time of availability check without getting assigned into any order..
    Make sure that the customer is allowing partial delivery..
    Hope it'll helpful..
    Thanks & Regards,
    Venkatesh.S.P.

  • 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

  • Determination of Delivery/Availability dates for a SO

    Hello Gurus,
    .....I am an SAP-PP consultant , my question is..
    .....I have a sales order created by user on Sep 15 for 840pcs .  We do not have any stock of this material
    1. MD04 screen shows availability date as Oct 7 .
    2. I selected the SO in this screen and branced to the schedule line of this Material  . It had 2 line items
    One line item was on Oct 7th, Order qty 840pcs,rounded-840,confirmed qty is ZERO
    second line item was on Nov 11th, order qty and rounde qty is zero, but confirmed qty is 840 .
    ...I want to know why system is proposing 2 line items for the same requiremnst?
    ..I want to know how has sytem arrived at these date .(the inhouse prodn time is only 1day)
    ..i branched into shiiping info for first line item it shows Delivery date,GI date,Loading date,Materila availabality date,Transportation plan date as ...Oct 7th..How did it arrive at this date.
    Appreciate if GURUs can give a detailed reply cos i m not familiar with SD terminology.
    THNX in ADVANCE
    HKR

    The way that I associate this situation is the following:
    10/7 - there is a requirement to ship qty 840 on this date.  Per this requirement, there is 0 confirmed qty to actually ship the goods on this date.  This is also schedule line 1.
    11/11 - the system is proposing this date to ship qty 840 and is confirming for this date based on either an incoming purchase order or the planned delivery time set in the material master.  There is no requirement for this date because the requirement is already set for the 10/7 date.  This is schedule line 2.
    MD04 is known as the stock/requirements list.  As previously stated, you have a requirement to ship qty 840 on 10/7 and it would appear as such within the stock/requirements list.  This isn't the date it will actually ship, it merely lists the requirement to fulfill that qty for the 10/7 date.  MD04 is primarily for the planning side from my understanding.
    CO09 is the availability overview and will show the two dates 10/7 - qty 0 confirmed and 11/11 - qty 840 confirmed.  Lets say you get a shipment on 10/15.  When rescheduling runs, on 10/15, the system will delete schedule line 2 and update schedule line 1 with the following - date 10/15, order qty 840, confirmed qty 840.
    Hope this helps.

  • What is availability check concept  how it is used in SAP

    hi friends,
    i don't know what is availity check,how is it used and how it should be configured,please help me.

    Availability Check in Sales and Distribution Processing 
    There are three types of availability check:
    •     Check on the basis of the ATP quantities
    •     Check against product allocation
    •     Check against planning
    In Customizing, you determine whether an availability check is to be carried out against the ATP quanitity or against planning. The check against product allocations is controlled in the material master and elsewhere in the system.
    Check on the Basis of the ATP Quantities
    The ATP quantity (ATP = Available To Promise) is calculated from the warehouse stock, the planned inward movements of stock (production orders, purchase orders, planned orders) and the planned outward movements of stock (sales orders, deliveries, reservations). This type of check is performed dynamically for each transaction, taking into account the relevant stock and planned goods movements with or without replenishment lead time. Planned independent requirements are not taken into account here.
    Check against Product Allocation
    Product allocation facilitates period-based distribution of products for certain customers or regions. As of Release 3.0F, you can carry out an availability check against product allocation. This ensures, for example, that when production is low, the first customer does not get the full amount, resulting in following sales orders not being confirmed or being confirmed far too late.
    Check against planning
    The check against planning is performed against independent requirements which are usually created for an ‘anonymous’ market rather than being customer-specific (for example, in the strategy ‘Planning without assembly’, when production occurs only up to the stocking level). The planned independent requirements result from demand program planning and are used for planning expected sales quantities independent of orders
    Controlling the Availability Check in Sales and Distribution Processing 
    You control the availability check using general and SD-specific control features.
    General Control Features
    The following control elements need to be maintained in Customizing and in the material master record:
    •     Strategy group
    The allowed planning strategies (main strategy and further possible strategies) are combined in the strategy group. As of Release 3.0, the strategy group is specified in the material master record in the MRP 1 Screen. In Customizing, strategy groups are assigned, dependent on plant, to MRP groups. If the strategy group is missing in the material master record, it is determined on the basis of the MRP group, if it has been maintained.
    Up to Release 3.0, the strategy group is determined on the basis of the MRP group
    •     MRP group
    The MRP group combines materials from the point of view of material requirements planning. This enables you to control planning for these materials in a particular way using, for example, the strategy group, consumption mode and planning period. You enter the MRP group in the material master in the MRP 1 screen. The strategy group is determined from the MRP group.
    •     Planning Strategy
    The planning strategy specifies the requirements type for planning and customer requirements. This represents the decisive control feature for the interaction between Production Planning and Sales and Distribution.
    •     MRP type and item category
    If no requirements type is found using the planning strategy, the system tries to determine a corresponding requirements type on the basis of the MRP type and the item category.
    Until 3.0C, determination of the requirements type via planning strategy has taken priority. This is not always the best option, however, as the following example will show. A requirements type is determined for a material, which causes availability to be checked against planning. In consignment stock processing, however, availability should be checked against stock. Until 3.0C the availability check had to be deactivated in these cases. As of Release 3.0C, you can determine how the requirements type is to be determined for each transaction by maintaining the Source field in Determination of requirement types using transaction in Customizing.
    •     Requirements type
    The various requirements are identified by their requirements type. The requirements type refers to the requirements class and its control features.
    •     Requirements Class
    The requirements class contains all control features for planning such as relevance for planning, requirements planning strategy and requirements consumption strategy. In addition, it is specified at a global level whether an availability check is to take place for the material in the sales and distribution documents on the basis of the ATP quantity (ATP = available to promise) and whether requirements are to be passed on. A finer degree of control can be obtained for sales documents using the schedule line category.
    Control Features Specific to Sales and Distribution
    The following SD-specific control features need to be maintained in Customizing:
    •     Checking group
    The checking group controls whether the system is to create indivdual or collective requirements in sales and shipping processing. In addition, a material block for the availability check with transfer of requirements can be set here. The checking group can also be used to deactivate the availability check. This option was created especially for the assembly order so that when the bill of material is exploded in the assembly order, the individual components, if necessary, can be classified as non-critical parts as far as procurement is concerned.
    The checking group specifies in combination with the checking rule the scope of the availability check. It is proposed in the material master record on the basis of the material type and the plant, and copied into the sales and distribution documents.
    •     Checking Rule
    You use the checking rule to control the scope of the availability check for each transaction in sales and distribution. You also specify whether the check should be carried out including or excluding replenishment lead time. The individual checking rules define by transaction, which stock and inward and outward movement of goods should be taken into account for the availability check.
    •     Schedule line category
    You can control with the schedule line category whether an availability check and transfer of requirements should be carried out in the sales documents. The possible settings for this at schedule line level are dependent on the settings in the requirements class which is determined from the requirements type of the material.
    •     Delivery item category
    The delivery item category can be used to control whether an availability check takes place in deliveries.
    Prerequisites
    An availability check can only be carried out if the following prerequisites have been fulfilled:
    •     The control elements described above for the availability check must be maintained in Customizing for Sales and the relevant assignments made to the sales transactions
    •     The availability check must be switched on at requirements class level and - for the availability check in the sales documents - at schedule line category level
    •     A requirements type must exist by which the requirements class can be found
    •     A plant must be defined. It can either be proposed from the customer or material master record or can be entered manually in the document.
    •     A checking group must be defined in the material master record on the Sales/plant data screen in the Availability check field
    Timing of the Availability Check in Sales and Distribution Processing 
    When you create an order, the system determines the required materail availability date on the basis of the customer’s requested delivery date. On this date, you must begin picking, packing, labeling, and loading the goods. Therefore, this is the date of significance for requirements planning on which the availability should be checked.
    The following data is required for determining this date:
    •     Route from the shipping point to the ship-to party location
    •     Shipping point from which the goods are issued
    •     Loading group from the material master record
    •     Weight group determined from the order using the order quantity
    Scheduling
    This data, which you have already entered in the system, means that scheduling can occur automatically. Since scheduling is carried out backwards from the requested delivery date, it is also called backward scheduling. If backward scheduling determines that the preparation for the shipping activities should have been started already to meet the customer's requested delivery date, the system then starts forward scheduling automatically from the current date.
    Scope of the Availability Check in Sales and Distribution Processing 
    The following elements can be included in the availability check:
    •     Stock
    o     safety stock
    o     stock in transfer
    o     quality inspection
    o     blocked stock
    •     Inward/Outward movement of goods
    o     purchase orders
    o     purchase requisitions
    o     planned orders
    o     production orders
    o     reservations
    o     dependent reservations
    o     dependent requirements
    o     sales requirements
    o     delivery requirements
    Requirements in sales and distribution (sales requirements and delivery requirements) result from all transactions which forward a requirement to Materials Management (MM) or to Production Planning (PP). For example, this could include sales orders or deliveries and quotations as well. Sales and distribution requirements reduce existing stock or inward movements of stock on the material availability date to ensure that other outward movement of stock elements cannot access the quantity reserved in this way.
    Requirements relevant for Sales and distribution are created in Sales and Distribution, whereas other elements in this list are created in Materials Management or in Production Planning.
    Defining the Elements to be Included in Check
    A checking rule is assigned to each transaction. This rule in combination with the checking group controls the scope of the availability check. You can use the checking rules in Customizing for Sales to specify for the various transactions which of the elements listed above should be included in the availability check.
    For trading goods it does not make sense to include planned or production orders, for example, in the availability check. However, for products manufactured by your company these orders should be included in the check.
    For transactions such as make-to-order production, consignment or returnable packaging processing that create special stock, the availability check is performed against special stock.
    If it is defined by the checking rules that both sales and delivery requirements are taken into account in the availability check in sales documents but only delivery requirements are taken into account in the availability check in deliveries, there is a danger that quantities reserved in the sales documents are considered to be available by the availability check in the deliveries. This can lead to sales documents becoming backlogged.
    Reactions to the Availability Check in Sales Documents 
    If the goods ordered by the customer are not available on the requested date, the system branches automatically during sales document processing to a further screen where delivery proposals are offered for selection. The system determines these proposals on the basis of the availability situation. This screen also provides you with information on the scope of the check, the current ATP quantity, and the availability situation across all plants.
    Availability Control
    On the Availability Control screen, you can choose between the following delivery proposals:
    •     One-time delivery on the requested delivery date
    In this section, the system checks whether the requested delivery date can be kept to. If stock of the material is available to make a delivery on the requested delivery date, the stock quantity is confirmed here. If there is no stock available, confirmed quantity zero is displayed.
    To copy this data into the sales document, select Edit One-time delivery.
    •     Complete delivery
    In this section, the system checks whether there will be sufficient stock for complete delivery at a later date:
    o     If there is sufficient stock available at a later date to cover the required quantity in the sales document, the system proposes the date here.
    o     If the system determines that complete delivery cannot be made at a later date, no date is proposed in this section.
    When availability is checked including replenishment lead time, the date which is proposed in this section is the date on which the replenishment lead time period ends if the stock before the end of replenishment lead time does not cover the order quantity.
    When availability is checked excluding replenishment lead time, the system bases its calculations on the stock and the planned inward movements of stock.
    To copy this data into the sales document, select Edit Complete delivery
    •     Delivery proposal
    In this section, the system checks whether and for which dates partial deliveries can be made. Partial deliveries are displayed for different dates. These dates are based on the planned inward and outward movements of stock.
    During an availability check which takes replenishment lead time into account, the date on which replenishment lead time ends is displayed if insufficient stock means that no partial deliveries can be made before replenishment lead time ends.
    During an availability check which does not take replenishment lead time into account, the system displays the dates on which partial deliveries can be made with the available stock.
    To copy this proposal into the sales document, select Edit Delivery proposal
    The dates displayed in the sections complete delivery and delivery proposal are determined from the material availability date using forward scheduling and represent actual delivery dates.
    Availability Across Plants
    You can display the availability situation in the various plants for which a material is maintained. To do this, proceed as follows:
    1.     Select Goto Other plants on the availability control screen.
    The dialog box Plant Selection appears. All plants for which the material is maintained are displayed.
    2.     Mark the plants in which you want to check availability and select Check plants.
    You reach the Availability Check: Overview screen. The requirements quantity and the quantity which could be confirmed as well as some additional information is displayed in a separate line for each plant you selected.
    3.     If you require detailed information on the availability check for a particular line, select the relevant line and select Edit Check availability.
    You reach the Date proposals dialog box where the detailed data is displayed.
    4.     You can select a plant with sufficient quantity for confirmation to be copied automatically into the Overview screen. Select the appropriate line and select Edit Copy plant.
    Using the user exit USEREXIT_PLANT_SELECTION in the Include LV03VFZZ you can make a preselection of the allowed plants. If you use this option, the Plant selection dialog box does not appear and the availability check is performed immediately for the allowed plants. If, on the basis of information resulting from the availability check, you want to deliver from a plant other than the one specified in the item, you must at present enter this plant manually in the item. In a later release, however, you will be able to select the plant directly from the list of plants.
    Displaying the ATP Quantities
    If you want to display the current ATP situation on the availability control screen, select Goto Availability overview.
    Displaying the Scope of the Check
    If you want to display the scope of the check (stock and inward/outward movements of goods taken into account during the availability check) from the availability control screen, select Goto Scope of check.
    Delivery Agreements in the Customer Master Record
    A customer may react in different ways to the fact that a complete delivery can not be provided for the required delivery date. You can define in the customer master record, the way a customer reacts to the inability to meet the requirements represented by the key data.
    •     The customer wants complete delivery of all items by the requested delivery date or at a later date.
    The complete delivery indicator is copied into the sales document from the customer master record. To find it, select Header Business data on an overview screen or a header screen. You find the indicator in the Shipping section.
    If the complete delivery indicator is set in the sales document, the individual items are automatically correlated when the document is saved if the schedule lines exist for various dates (that is, a delivery group is automatically created for the sales document items and the latest delivery date within this group becomes the group delivery date). For further information on delivery groups, see  Combining Sales Document Items for Delivery.
    •     The customer only allows a certain number of partial deliveries for each item.
    The partial delivery indicator and the number of partial deliveries are copied into the sales document item from the customer master record. To find the indicators:
    1.     Go to the Business Data screen for this item.
    2.     Select Edit Shipping details.
    The indicators are found in the Shipping section.
    Performing the Availability Check Again
    Usually, an availability check is only performed when a sales document is created. If quantities or dates are changed in the document and availability needs to be checked again, the check is performed again automatically . However, you can also initiate an availability check manually.
    Automatic Checks
    In the following situations, a new availability check is automatically carried out:
    •     Quantity change
    •     Date change (requested delivery date, material availability date)
    •     Change to the fixed data
    •     After new delivery scheduling (for example, the route or shipping point has been changed)
    •     Change of plant
    •     Change of storage location or batch
    •     Removal of blocks which affect requirements
    •     Removal of reasons for rejection
    Initiating a Check Manually
    In the sales document, you can initiate a new availability check manually. If you want to perform an availability check for all items in a sales document, select Sales document Check availability on the header screen. If you want to check availability for an individual item, select Edit Item availability.
    Fixing Quantities and Dates in Sales Documents 
    If the availability check for an item determines that the item cannot be delivered fully on the requested delivery date, and, as a result one or more schedule lines have to be created for later delivery dates, the customer can decide whether to accept these delivery dates and quantities.
    You can record the customer's decision either by setting an indicator in the Fixed date and qty field or by leaving this field blank. The field is displayed both on the schedule line overview screen and on the availability screen.
    Customer Accepts the Schedule Line Proposal
    If the customer accepts the schedule lines which are proposed by the system, mark the Fixed date and qty field. The system then transfers the requirements for the schedule lines to material requirements planning.
    Customer Requires Goods Earlier
    If the customer requires the goods earlier than the date that the system can confirm after the availability check, leave the Fixed date and qty field blank. The system then only passes on the requirements for the requested delivery date and does not take the quantities and dates confirmed by the system after the availability check into account. In this case, it is assumed that the requested delivery date can be kept to because, for example, additional production capacity may become free. The system only confirms the sales order once the entire order quantity can be delivered on the requested delivery date. In the subsequent delivery processing, the sales order is only considered to be completed when the entire order quantity has been delivered or when all partial delivery agreements have been fulfilled.
    A fixed item is considered to be completed once the entire confirmed quantity (which can be smaller than the originally requested order quantity)has been delivered. Therefore, it does not make sense to fix the confirmed quantity to 0 as the item is considered to be completed from the start.
    During rescheduling, the fixed quantities and dates are no longer taken into account.
    Blocking Confirmation of Quantities in Sales Documents 
    In Customizing, using Block transfer of requirements by delivery block, you can specify that certain delivery blocks in the sales document header also block the confirmation of order quantities.
    If you enter such a delivery block in a sales order header, the system confirms the available quantity to show you the delivery options. If you save the document, however, the confirmed quantities are not saved. Your company could block confirmation for a customer if this customer's credit worthiness was questionable. The sales order in this case is not only classed as unconfirmed, it is also blocked for delivery.
    Thus, no stock is reserved. The stock is still available for other customers. Although the order quantities are not confirmed, the system still transfers the requirements to material requirements planning. It is assumed that the delivery block will be removed at some point. The automatic transfer of requirements means that the order quantity can be confirmed at a later point in time
    Source: SAP Library
    Hope this is of some help.

  • SAP SD  Availability

    1. I have created a Sales Order 15009231 on 02.11.2010 for Material 391115 Quantity Two. Requested delivery date is 08.11.2010. Availability check is working fine and schedule lines confirmed for 08.11.2010.
    2. Created delivery 80106315 on 04.11.2010.
    Picking 06.11.2010
    Trans. Planning 06.11.2010
    Loading 06.11.2010
    Planned GI 06.11.2010
    Delivery Date 08.11.2010
    3. On 04.11.2010 EDI output (LAVA) has processed successfully from delivery 80106315 and updated delivery details (material and quantity) in third party wear house system (Mailway) for picking.
    4. Picking done in Mailway for delivery 80106315.
    5. On 05.11.2010 Mailway has updated the picked material and quantity in their system, which will update delivery through an IDOC.
    6. IDoc has filed in SAP with ERROR MESSAGE '' Only 1 CS from material 391115 are available''.
    Can you help me to understand why IDoc has failed?
    In the sales order 15009231, availability screen I could see Material 391115 and Quantity Two are allocated against the delivery 80106315.
    Any small suggestion even could help me.
    Thanks and Regards,
    Satish

    Dear Satish,
        Just to notify that, MMBE stock overview- doesnt give correct figure of ATP qtty.
    It would be better to check in Availability overview:CO09 or execute function module:BAPI_MATERIAL_AVAILABILITY.
    By using this function Module, system finds ATP qtty in live transactions i.e order / Delivery.
    Can you explain, what for you are using Ztables & whats the purpose using this & how its inter related to availability check?
    Replies given is under the assumption that, availability check in with std system settings, have not considered any developments.
    Regards,
    Reazuddin MD

  • Check availability button in purchase requisition

    Dear All,
    What is the use of the "Check availability" button provided above the item over view sub screen of the ME51N transaction.This button one among the other buttons provided above the Item over view sub screen.
    To enable this we need to do any customisation.
    Please share your ideas for which iam very much thankful.
    Advance thanks,
    Regards,
    Dayanand

    There are two types of availability check:
    _ Availability check for the various stock types in Inventory Management
    _ Check for the available stocks in Materials Planning (MRP)
    Availability check of the stock types is carried out automatically and cannot be manually set in the
    system. Non-availability results in an error message.
    The available stocks check in MRP is activated in the material master record and can be
    configured in Customizing for MRP (refer to Net Requirements Calculation [Ext.]).
    Your system administrator can define:
    _ Whether an availability check is to be carried out
    _ Whether non-availability is to result in a warning message or an error message
    In Customizing for Inventory Management, you can configure the dynamic availability
    check for goods movements. In the step Define Checking Rule, you determine for
    each checking rule which stocks, receipts, and issues should be included in the
    availability overview (transaction code CO09).
    Remember that the system does not update the consumption statistics in the material master
    record if you post goods movements using the special stock types Sales order stock and Project
    stock.
    For every material movement, the system automatically performs an availability check of the
    stock types if this has been defined for a material. The availability check prevents the book
    inventory balance of the various physical stock types (for example, unrestricted-use stock) from
    becoming negative.
    If several withdrawals of material are entered in a single document (for example, for different
    account assignments), the system checks the availability of the material for each item entered. It
    checks whether the desired quantity can be withdrawn. The system takes into account those
    items of the document that have already been entered, but not yet posted.
    If there is not enough stock to cover the withdrawal, the system issues an error message.
    The availability check includes the stock in question at plant, storage-location, and special-stocks
    level, for the current month and, if necessary, for the previous month. Different stocks are
    checked, depending on the movement type:
    _ In the case of a withdrawal for consumption, unrestricted-use stock is checked.
    _ In the case of a release from stock in quality inspection, quality inspection stock is
    checked.
    _ In the case of consumption of consignment material, consignment stock for unrestricted
    use is checked.
    In addition to checking the various types of physical stock, you can also check available stock
    from a Materials Planning perspective. With this type of availability check, you can, for example,
    prevent a quantity already reserved from being used for another purpose.
    There are 100 pieces of a material in unrestricted-use stock. 70 pieces of these 100
    have been reserved for a particular requirement date.
    You want to withdraw 50 pieces for a different purpose. If the availability check is
    active, depending on how the system is set, you will receive:
    _ A warning message
    _ An error message
    _ No message

  • DB12 last successful back up not available

    Hi, i am having problem with backup in our quality system.
    Orcale :10g
    sap ecc6.0
    we are taking online backup  every monday, wednesday, thursday. DB12- last successful backup  not available
    overview of redo log files     not yet backed up  300.
    sapqas:orabqs 3> pwd
    /oracle/BQS/102_64/dbs
    sapqas:orabqs 4> ls
    agent.lic                    initBQS.sap
    dsmerror.log                 initBQS.sap.040107
    hc_BQS.dat                   initBQS.sap.backup040407
    init.ora                     initBQS.utl
    initBQS.000                  initBQS.utl.old
    initBQS.001                  initBQS2703.sap
    initBQS.002                  initdw.ora
    initBQS.1.ora                initoraBQS.bki.old
    initBQS.2.ora                initoraBQS.utl.old
    initBQS.bki                  initorabqs.bki.old
    initBQS.bki.cms              initorabqs.utl.backup030407
    initBQS.bki.old              initorabqs.utl.old
    initBQS.dba                  lkBQS
    initBQS.ora                  orapwBQS
    initBQS.ora.SAPINST-ORIG     spfileBQS.ora
    sapqas:orabqs 5> more initBQS.sap
    @(#) $Id: //bas/700_REL/src/ccm/rsbr/initAIX.sap#5 $ SAP
    SAP backup sample profile.                                           #
    The parameter syntax is the same as for init.ora parameters.         #
    Enclose parameter values which consist of more than one symbol in    #
    double quotes.                                                       #
    After any symbol, parameter definition can be continued on the next  #
    line.                                                                #
    A parameter value list should be enclosed in parentheses, the list   #
    items should be delimited by commas.                                 #
    There can be any number of white spaces (blanks, tabs and new lines) #
    between symbols in parameter definition.                             #
    backup mode [all | all_data | full | incr | sap_dir | ora_dir
    | all_dir | <tablespace_name> | <file_id> | <file_id1>-<file_id2>
    | <generic_path> | (<object_list>)]
    default: all
    backup_mode = all
    restore mode [all | all_data | full | incr | incr_only | incr_full
    | incr_all | <tablespace_name> | <file_id> | <file_id1>-<file_id2>
    | <generic_path> | (<object_list>) | partial | non_db
    redirection with '=' is not supported here - use option '-m' instead
    default: all
    restore_mode = all
    backup type [offline | offline_force | offline_standby | offline_split
    | offline_mirror | offline_stop | online | online_cons | online_split
    | online_mirror
    default: offline
    backup_type = online_cons
    #backup_type = offline_force
    backup device type
    [tape | tape_auto | tape_box | pipe | pipe_auto | pipe_box | disk
    | disk_copy | disk_standby | stage | stage_copy | stage_standby
    | util_file | util_file_online | rman_util | rman_disk | rman_stage
    | rman_prep]
    default: tape
    backup_dev_type = tape
    #backup_dev_type = util_file
    #backup_dev_type = util_file
    backup root directory [<path_name> | (<path_name_list>)]
    default: $SAPDATA_HOME/sapbackup
    backup_root_dir = /oracle/BQS/sapbackup
    stage root directory [<path_name> | (<path_name_list>)]
    default: value of the backup_root_dir parameter
    stage_root_dir = /oracle/BQS/sapbackup
    compression flag [no | yes | hardware | only]
    default: no
    compress = no
    compress command
    first $-character is replaced by the source file name
    second $-character is replaced by the target file name
    <target_file_name> = <source_file_name>.Z
    for compress command the -c option must be set
    recommended setting for brbackup -k only run:
    "compress -b 12 -c $ > $"
    no default
    compress_cmd = "compress -c $ > $"
    uncompress command
    first $-character is replaced by the source file name
    second $-character is replaced by the target file name
    <source_file_name> = <target_file_name>.Z
    for uncompress command the -c option must be set
    no default
    uncompress_cmd = "uncompress -c $ > $"
    directory for compression [<path_name> | (<path_name_list>)]
    default: value of the backup_root_dir parameter
    compress_dir = /oracle/BQS/sapreorg
    brarchive function [save | second_copy | double_save | save_delete
    | second_copy_delete | double_save_delete | copy_save
    | copy_delete_save | delete_saved | delete_copied]
    default: save
    archive_function = save_delete
    directory for archive log copies to disk
    default: first value of the backup_root_dir parameter
    archive_copy_dir = /oracle/BQS/saparch
    directory for archive log copies to stage
    default: first value of the stage_root_dir parameter
    archive_stage_dir = /oracle/BQS/sapbackup
    delete archive logs from duplex destination [only | no | yes | check]
    default: only
    archive_dupl_del = only
    new sapdata home directory for disk_copy | disk_standby
    no default
    new_db_home = /oracle/C11
    stage sapdata home directory for stage_copy | stage_standby
    default: value of the new_db_home parameter
    stage_db_home = /oracle/C11
    original sapdata home directory for split mirror disk backup
    no default
    orig_db_home = /oracle/C11
    remote host name
    no default
    remote_host = <host_name>
    remote user name
    default: current operating system user
    remote_user = <user_name>
    tape copy command [cpio | cpio_gnu | dd | dd_gnu | rman | rman_gnu
    rman_dd | rman_dd_gnu]
    default: cpio
    tape_copy_cmd = dd
    disk copy command [copy | copy_gnu | dd | dd_gnu | rman | rman_gnu]
    default: copy
    disk_copy_cmd = copy
    stage copy command [rcp | scp | ftp]
    default: rcp
    stage_copy_cmd = rcp
    pipe copy command [rsh | ssh]
    default: rsh
    pipe_copy_cmd = rsh
    flags for cpio output command
    default: -ovB
    cpio_flags = -ovB
    flags for cpio input command
    default: -iuvB
    cpio_in_flags = -iuvB
    flags for cpio command for copy of directories to disk
    default: -pdcu
    use flags -pdu for gnu tools
    cpio_disk_flags = -pdcu
    flags for dd output command
    default: "obs=16k"
    recommended setting:
    Unix:    "obs=nk bs=nk", example: "obs=64k bs=64k"
    Windows: "bs=nk",        example: "bs=64k"
    dd_flags = "obs=64k bs=64k"
    flags for dd input command
    default: "ibs=16k"
    recommended setting:
    Unix:    "ibs=nk bs=nk", example: "ibs=64k bs=64k"
    Windows: "bs=nk",        example: "bs=64k"
    dd_in_flags = "ibs=64k bs=64k"
    number of members in RMAN save sets [ 1 | 2 | 3 | 4 | tsp | all ]
    default: 1
    saveset_members = 1
    additional parameters for RMAN
    rman_channels and rman_filesperset are only used when rman_util,
    rman_disk or rman_stage
    rman_channels defines the number of parallel sbt channel allocations
    rman_filesperset = 0 means:
    one file per save set - for non-incremental backups
    all files in one save set - for incremental backups
    the others have the same meaning as for native RMAN
    rman_channels = 1
    rman_filesperset = 0
    rman_maxpiecesize = 0   # in KB - former name rman_kbytes
    rman_rate = 0           # in KB - former name rman_readrate
    rman_maxopenfiles = 0
    rman_maxsetsize = 0     # in KB - former name rman_setsize
    additional parameters for RMAN version 8.1
    the parameters have the same meaning as for native RMAN
    rman_diskratio = 0      # deprecated in Oracle 10g
    rman_pool = 0
    rman_copies = 0 | 1 | 2 | 3 | 4 # former name rman_duplex
    rman_proxy = no | yes | only
    special parameters for an external backup library, example:
    rman_parms = "BLKSIZE=65536 ENV=(BACKUP_SERVER=HOSTNAME)"
    rman_send = "'<command>'"
    rman_send = ("channel sbt_1 '<command1>' parms='<parameters1>'",
                 "channel sbt_2 '<command2>' parms='<parameters2>'")
    remote copy-out command (backup_dev_type = pipe)
    $-character is replaced by current device address
    no default
    in oracle/sid/sapbackup  folder i found one file bdxwbpsz.ant that was created on  May 7th 2008( Wednesday)
    plz check this:
    sapqas:orabqs 21> more bdxwbpsz.ant
    BR0051I BRBACKUP 7.00 (24)
    BR0055I Start of database backup: bdxwbpsz.ant 2008-05-07 01.04.17
    BR0484I BRBACKUP log file: /oracle/BQS/sapbackup/bdxwbpsz.ant
    BR0477I Oracle pfile /oracle/BQS/102_64/dbs/initBQS.ora created from spfile /ora
    cle/BQS/102_64/dbs/spfileBQS.ora
    BR0280I BRBACKUP time stamp: 2008-05-07 01.04.18
    BR0319I Control file copy created: /oracle/BQS/sapbackup/cntrlBQS.dbf 46383104
    BR0101I Parameters
    Name                           Value
    oracle_sid                     BQS
    oracle_home                    /oracle/BQS/102_64
    oracle_profile                 /oracle/BQS/102_64/dbs/initBQS.ora
    sapdata_home                   /oracle/BQS
    sap_profile                    /oracle/BQS/102_64/dbs/initBQS.sap
    backup_mode                    ALL
    backup_type                    online
    backup_dev_type                tape
    compress                       no
    tape_copy_cmd                  dd
    cpio_flags                     -ovB
    cpio_in_flags                  -iuvB
    dd_flags                       obs=64k bs=64k
    dd_in_flags                    ibs=64k bs=64k
    rewind                         tctl -f $ rewind
    rewind_offline                 tctl -f $ offline
    tape_size                      307200.000 MB
    tape_address                   /dev/rmt0.1
    tape_address_rew               /dev/rmt0
    volume_backup                  BQSB29
    expir_period                   0
    tape_use_count                 100
    exec_parallel                  0
    system_info                    bqsadm/orabqs sapqas AIX 3 5 00C0799E4C00
    oracle_info                    BQS 10.2.0.2.0 8192 2370 485914644 sapqas WE8DEC
    UTF8
    sap_info                       700 SAPSR3 0002LK0003BQS0011V18391775040013NetWea
    ver_ORA
    make_info                      rs6000_64 OCI_102 Mar  3 2007
    command_line                   brbackup -u / -jid ALLOG20080507010416 -c force -
    t online -m all -p initBQS.sap -v BQSB29 -a -c force -p initBQS.sap -sd
    BR0116I ARCHIVE LOG LIST before backup for database instance BQS
    Parameter                      Value
    Database log mode              Archive Mode
    Automatic archival             Enabled
    Archive destination            /oracle/BQS/oraarch/BQSarch
    Archive format                 %t_%s_%r.dbf
    Oldest online log sequence     2367
    Next log sequence to archive   2370
    bdxwbpsz.ant (6%)
    plz suggest how can I take online backup and redo log backup.

    Hi Shrinivas,
    Are you taking backup from the local tape device or from 3rd party software.
    I cannot clearly what is the exact problem, Your saying either Db12 the status is mot shown then asking for how to take the backup.
    If a backup device is properly configured in the system, then you can take online and offline backup by scheduling in the DB13 tcode.
    Pls state the exact problems so that it is easy to provide the solution.
    Regards,
    Maheswaran

Maybe you are looking for

  • Problem in lock Sales order create with BAPI BAPI_SALESORDER_CREATEFROMDAT2

    Hi All, i have the z program to create the sales order with reff  quotation in SD With BAPI BAPI_SALESORDER_CREATEFROMDAT2. this program will  excute every 30 mins . Problem: Some times if i excute the program in background it is taking morethan 30mi

  • Mapping of same structure

    Dear Experts, I have querry regarding the mapping of source and target structure.The source and target structure are same. The structure looks like this. <Source> +<Header>   <LineItem>  0:Unbounded     <Value>    1:1     <Text>      1:1   <LineItem>

  • I was wondering, would be able to use my eligible upgrade on 1 phone line to buy a phone for another line?

    Hey, I was wondering if I would be able to use my eligible upgrade on one phone line to buy a phone for another line?. Also, I saw a commercial on TV about getting a plan with 10 gb of data for like 130 a month, that does include the cost of both pho

  • Enable a disabled user on the native oracle resource

    I have to enable a disabled account on the native resource from a form. Field name='view.accounts[$(Resource)].enable' doesnot work whereas Field name='view.accounts[$(Resource)].disable' works properly. I have a custom adapter which has the required

  • Dynamically set transition target

    We are building an application that has multiple steps. As each step is completed, I would like it to move off to the left of the screen with the new screen moving in from the right edge. I am using multiple states and have created a transition that