ME59N not allowing PO creation- Availability check

Hi
I created  a PR and trying to do Autom PO creation using ME59N, but when I execute ME59N, I am getting a message as NO Items Found in ME59N T Code.
I used to PR number again in ME21N to create PO by manually providing PR number in ME21N line item. But I am getting a warning as " Of material XYX-123, only 0 EA are available on desired date"
Few things I checked are Auto PR is Ticked in Purchasing view of material master and Vendor master.
CAn someone help me how can I make availability of material in the scheduled date. Here we using  APO also.
MD04- From APO Product availablity overview- CUmulative QTY- 17, Confirm Quantity- 0. My PR Qty is 1.
Can some one guide me what might be the problem, in which I am not able to create PO from ME59N. as it is showing No items.
Also when I try to cretae manuall, its saying available qty is zero.
Thanks
Vineeth Varghese

Hi There
I hope you trying to convert the STR(PR) to STO(PO),,  And in the supplying plant avilability on the delivery date is ZERO,,
Raise the stock in Supplying plant( through 561- if you are only doing testing) and make sure that availability is more than the required,, and try to create the STO(PO) in ME59n the PO will create,,,
Seems you have configured as Dynamil Safety Stock, sytem will look not only Current Stock, but also a MRP point of view,, If there is any reservations, cutomer requirement and order requirement, system will block the current stock for that usage,,
Guessing thats the reason you are facing this issue,,
Thanks
Senthil

Similar Messages

  • When trying to send E-mail via AOL i get the message "rejected by the server because it does not allow relaying" I have checked settings as per answers to similar question

    When trying to send E-mail via AOL i get the message "rejected by the server because it does not allow relaying" I have checked settings as per answers to similar question

    From which account does the email not send?  When sending from an account, the iPad will first try to use the aoutgoing server for that account.  If it can't it will try the other accounts listed.in the setting on the iPad for that account.  It soulds like the server for the account is not working and that the alternate server is resjecting the messag since it did not originate ffrom the account associated with that server,  That is to prevent sending spam.

  • Delivery from projects not included in dynamic availability check

    Problem:
    In our client, we use deliveries for project (delivery type LP, delivery item type DLP) triggered from network reservations.
    During delivery creation, we are finding that the existing deliveries are not being considered/cumulated into the ATP calculation. For example, for a given a material with an on hand balance of 22 units, individual deliveries for 4 units are created every day. The individual delivery passes the availability check test as it is always backed by the 22 units of stock.  However, as a whole now the individual deliveries are totaling 80 units, exceeding the quantity on hand.
    Is there any way to fine tune the availability check through customizing such that these  deliveries for project created are included in CO09 and the delivery for project creation?
    Or this should be an enhancement?. Client is in SAP R/3 version 4.7
    Thanks,
    Marco

    Query posted in the PP Forum and hence this is closed.

  • Nfs mount point does not allow file creations via java.io.File

    Folks,
    I have mounted an nfs drive to iFS on a Solaris server:
    mount -F nfs nfs://server:port/ifsfolder /unixfolder
    I can mkdir and touch files no problem. They appear in iFS as I'd expect. However if I write to the nfs mount via a JVM using java.io.File encounter the following problems:
    Only directories are created ? unless I include the user that started the JVM in the oinstall unix group with the oracle user because it's the oracle user that writes to iFS not the user that creating the files!
    I'm trying to create several files in a single directory via java.io.File BUT only the first file is created. I've tried putting waits in the code to see if it a timing issue but this doesn't appear to be. Writing via java.io.File to either a native directory of a native nfs mountpoint works OK. ie. Junit test against native file system works but not against an iFS mount point. Curiously the same unit tests running on PC with a windows driving mapping to iFS work OK !! so why not via a unix NFS mapping ?
    many thanks in advance.
    C

    Hi Diep,
    have done as requested via Oracle TAR #3308936.995. As it happens the problem is resolved. The resolution has been not to create the file via java.io.File.createNewFile(); before adding content via an outputStream. if the File creation is left until the content is added as shown below the problem is resolved.
    Another quick question is link creation via 'ln -fs' and 'ln -f' supported against and nfs mount point to iFS ? (at Operating System level, rather than adding a folder path relationship via the Java API).
    many thanks in advance.
    public void createFile(String p_absolutePath, InputStream p_inputStream) throws Exception
    File file = null;
    file = new File(p_absolutePath);
    // Oracle TAR Number: 3308936.995
    // Uncomment line below to cause failure java.io.IOException: Operation not supported on transport endpoint
    // at java.io.UnixFileSystem.createFileExclusively(Native Method)
    // at java.io.File.createNewFile(File.java:828)
    // at com.unisys.ors.filesystemdata.OracleTARTest.createFile(OracleTARTest.java:43)
    // at com.unisys.ors.filesystemdata.OracleTARTest.main(OracleTARTest.java:79)
    //file.createNewFile();
    FileOutputStream fos = new FileOutputStream(file);
    byte[] buffer = new byte[1024];
    int noOfBytesRead = 0;
    while ((noOfBytesRead = p_inputStream.read(buffer, 0, buffer.length)) != -1)
    fos.write(buffer, 0, noOfBytesRead);
    p_inputStream.close();
    fos.flush();
    fos.close();
    }

  • Why does the Grid Installer not allow the creation of multiple disk groups?

    Ok I finally managed to get the ASM disks to be visible for the Installer. But now I want to create three disk groups (OCRVOTE,FRA and DATA), but the installer only allows me to create one disk group. Do I have to create other disk groups manually later?

    Hi,
    as Igoroshka said during the GI installation you create one diskgroup.
    Your screenshot show me that you create 3 disks OCRVOTE01-03. In 12c the the OCR and Voting is placed inside the default diskgroup which is normally DATA.
    You can check this via "query votedisk".
    May be you create these disks while you would like to move ocr and vote in a separate diskgroup you can do this after the installation is finished.
    kind regards
    SPA09

  • STO Creation - Availability check

    When you create an STO & if there is not enough stock in supplying plant, you got a WARNING message saying something like u201C of Material XXXXXX, only 49 EA are available on desired dateu201D.  The STO is saved but the system put a date of 12/31/9999 into the COMMITTED DELIVERY DATE for that material/line item. Even when additional materials are available, since the COMMITTED DELIVERY DATE is 12/31/9999, SAP will not try to deliver them.  Now the business is asking to change this warning message to  error message (06 450 Message number). If I change this warning message to error message, I believe it will impact all other type of STO's, PO's & SO's also. We want this warning message to be changed to Error message only for a particular STO type. What are the options available to us.
    Edited by: Csaba Szommer on Feb 2, 2012 8:33 AM

    You can control document type by putting some logic in some user exit.Suppose If PO first line item has no stock available and other line items confirmed in this case if you make it error that message then you can not save the STO?.For smooth flow STO keep the message to warning and tell the Business to follow the process.If Business really insisted to stop creating the PO if any line item is not confirmed then you can try for user exit.

  • 8i client not allowing database creation

    I think I've worked around the P4 issue on the 8i personal install, but now I can't get it to create a database. I keep getting a "end-of-file on communication channel" error. I've tried using a known good CD as well as re-downloading. Is it another P4 issue?

    I think you need a good dba or try to do the dba courses. That helps you a lot.

  • Availability check - sales order

    Hi experts,                              
    I've gone through the relevant info, but still hit the issue below. Pls help. Thx.                                                       
    Issue: How to include the created order (not delivered ) when running availability check?                                                       
    Example:                              
    Stock (storage location C) - 1pc                              
    sales order A - 1pc (confirmed in schedule line)                         
    sales order B - 2pcs (1pc confirmed, 1pc unconfirmed)                                                       
    Those two orders are created agaisnt storage location C. No other stocks against storage location C are available, such as on-order stock.                              
    In my understanding, order B cannot be confirmed as order A has been created firstly.                                    
    Background: As the customer just sells the purchased product, he places PO firstly, then sales order following. Thus, he requests new sales order creation to be based on the stock qty, created sales order qty, PO qty to be received & delivered sales order qty.                                                       
    For this sales scenario, availability check with ATP is activated, but not against product allocation. And the check boxes "incl.purchase orders", "include sales reqmts", "include deliveries" are checked in OVZ9 only.                              
    ps. "Check sales requirements" has been checked in Availability check control while "No storage location inspection" has not been checked.

    Dear Cathy
    Can you please reconfirm that the combination of availability check and checking rule in OVZ9 in which, you have selected the box "Include sales reqmts"  is the same value what you have maintained in material master MRP3 view for availability check ??
    If the availability check is same in both the cases, then try to create a fresh order and post the outcome.
    thanks
    G. Lakshmipathi

  • Availability Check authorization per plant

    Hi
    How can we set in VA01/VA02, such that user is only allowed to have availability check on certain plants.. and not allowed to check other plants..

    One option is through Object assignment in PFCG, this can be achieved.  The other method is dont maintain that storage location in MMSC.  In fact, you can also consider sale order user exit. 
    But of these options, I would prefer creating separate roles in PFCG where I assign only those plants for which availability check should happen and assign this role to that user id.  The object for this is C_AFKO_AWK
    thanks
    G. Lakshmipathi

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

  • Disable Availability Check on Sales Order  But Activate on Outbound Delv

    Greetings all experts !
    Currently, there's a new request to create a new processes whereby during the sales order creation, no availability check will be in place but material will still be posted to production planning ( TOR ).
    Availability check instead should be activated  during the creation of outbound delivery.
    I have already configured in such a way that the relevant sch line item ( VOV6 ) - availability check is unchecked and TOR is checked.
    But during creation of sales order, availability check is still in place for material specified.
    I have check on the necessary requirement class and requirement type settings. Fyi, requirement class used - availability check is ticked. Could this be the reason even though i have disabled availability check on sch line ?
    I have tried to untick the availability check setting in requirement class  ( OVZG ), and while this can disable the availability check in Sales order, but that configuration will also disable availability check in outbound delivery.
    My queries :
    1 ) What are the configurations that I need to look into to cater to the above request. To disable availabilty in sales order but instead, run availability in outbound delivery ?
    2 ) Is there any way I can disable the availability check on based on sales order type using userexit or function module ?
    3 ) Is there any additional function module/bapi/userexit that i can implement to force outbound delivery to run availability check ?
    My apologies for such lenghty message here but really really need some valuable feedback here as I'm totally at lost with the new requirement for now.
    Many thanks in advance.
    Warmest Regards,
    Edie O

    In SPRO
    goto SD>Schedule line>Define schedule line categories
    here check if the schedule line category associated with your mentioned order has a flag ticked for Availability.
    Availability check for sales
    You must carry out an availability check for the following transaction.
    The indicator is determined as a proposal in conjunction with the respective requirements type. It can be changed in individual shipping transactions. However, only one restriction is effective.
    Example
    You do not set an indicator for maintaining the requirements type. In this case, no availability check is carried out. This is independent of the selection in the respective transaction.
    You set an indicator for maintaining the requirements type. In this case you can decide whether or not you require an availability check for the relevant transaction.
    reward points if it helps
    regards
    Biju

  • Firefox did not allow ghostery download. Why? Should I allow it, anyway?

    I read in the paper today that ghostery browser extension is available within Firefox. I couldn't find any reference to it, so I tried to download it. Firefox said it was not allowed, but I could check on allow to let it go forward. Why is it not allowed and should I check allow?

    The Ghostery add-on is available for your version of Firefox, you can get it from https://addons.mozilla.org/firefox/addon/ghostery/
    If you are having problems installing it see https://support.mozilla.com/kb/Unable+to+install+add-ons
    On a side note, you should upgrade to the current version of Firefox (Firefox 3.6.13)

  • Availability check & TOR

    hi
    can anyone   tell me whether availability check is first or TOR.  Explain in one scenario.
    please urgent
    regards
    murali

    hi,
    Availability Check & TOR configuration is done hand in hand..
    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.
    a) One time delivery:
    If the user chooses one time delivery and the order Quantity is 100 units system confirms 50 units then systems automatically confirms as a zero. If the user saves the document with the zero confirm qty then system trace the sales order as aback order (V_RA), which can be confirmed later by RESCHEDULLING (V_V2).
    b) Complete Delivery:
    If order Qty=100, Availability stock = 50, system says that remaining can be given after one week. Then if the user selects this option then system push up existing confirmed qty to after one week and the total qty can be confirmed after one week only.
    c) Delivery Proposal:
    If order qty=100, system confirms 50, and remaining 50 can be confirmed after one week. If the user chooses this option then system confirms 50 Qty today allows the user to delivery 50 quantities today remaining 50 can be delivered after one week.
    CONFIGURATION SETTINGS FOR TOR:
    Define Requirement Class:
    Path:  SImg & Availability Check Basic functions D  & Transfer of  Define Requirement classes Transfer of requirements requirements
    Requirement classes control MRP, Requirement consumption, strategy, relevance for planned. It specifics whether the availability check & TOR to be Called out for transactions. Ex: Sales Order
    It determines whether requirements relevant for MRP or not, the allocation indicator from the sales view which controls the settlement of customers requirements with planned independent requirements. It determines the item b to be settled as an availability heck. Assignment, the settlement profiles the results analysis key. The TOR and Availability check functions are globally controlled using the requirement class for all the Sales documents. The values from the Requirements class are transferred to scheduled the of the sales documents class are transferred to scheduled the of the sales document default values and can be over written there.
    Define Requirements Classes:
    Requirement class defines whether the system has to carry out availability check based on the STP Qty. Ex:
    Define Requirement Types:
    Here we define requirement type, Ex: and Assign to Requirement class that we defined in the promote step.
    Determination of Requirement types using Transaction:
    Requirement type is going to be determined for sales document by following a search strategy. .
    First System checks strategy group in MRP3 view if it trend requirement type then system takes from it, otherwise.
    It will go to MRP group in MRP1 view, otherwise
    It will check to Material type, otherwise
    It will go to item Category + MRP type, otherwise
    It will go to Item category only, otherwise
    Finally system determines the transaction b not relevant for TOR & Availability check.
    Choose Item category TAN+MRP type PD=Requirement type =0
    Define Procedure for each schedule the category:
    Here we define respective schedule the category of the sales documents, whether an availability check and TOR should be carried out. This setting is relevant for sales documents only. It is fine tuning of availability check for sales documents TOR & Availability check function can be activated at sales order level those are proposed in to schedule line category level. If u wants to deactivate TOR availability check function at schedule the category level and want to deactivate at requirement class level it b impossible.
    Ex: If u wants to check availability w/o transferring the requirement we can use it.
    Choose schedule line category CP & Activate Availability check, requirement & Product Allocation
    Block Quantity confirmation in delivery Blocks:-
    When we transfer requirements to MRP then confirmed quantities is also reserved for confirmed sales documents, if transaction is blocked for delivery the reserved quantities are also blocked so that the conformed quantities cannot be used by any other purpose. So has to avoid this situation we can block the transfer of requirements(TOR) for delivery blocks, in this case requirements transferred to MRP but will not be reserved, that will be cleared once we save the documents then system shows confirmed qty as zero.
    When we remove the delivery block then system automatically carries out availability check & confirms the qty.
    A) Deliveries: Blocking region for sales Area:
    Here we define blocking regions for TOR ex:-credit limits
    B) Reasons for scope of delivery blocks: TOR. Block:
    Ex: - 01 credit limits-check confirmation block.
    Maintain Requirements for TOR:-
    Here we can define our own requirement with the help of ABAPer for TOR
    Ex: - a) 102- prevent reservation in the event of credit block
    b) 102-purchase requisitions.
    System doesn’t create purchase requisitions for sales order line items if it has a credit limit.
    Availability check:
    Configuration setting:-
    Availability check with ATP logic or against planning:-
    Define checking group:
    Checking group define what kind of requirement record system use to create when sales order & deliveries are processed for this material. We can create 2 kinds of requirements records
    Individual requirement records: that means system creates requirement record for each S&D document.
    Summarized requirement Records: That means system creates requirement records under certain condition in the material master record. There are 2 type of summarized requirement record:
    Summarized requirement records for each day.
    Summarized requirement records for each week
    Define checking Action;
    Here we define 01- daily requirement -B 02- Individual requirements -A
    Where b-total record per day
    A-single record per day
    B) Define material Block for other users:
    When 2 users tries to confirm the quantities for the sales order for same material at a time system will be confused to confirm the quantities both sales orders. So has to avoid this kind of situation we can block the materials from confirming the quantities for 2 users at a check, check block
    C) Define checking group default values:
    Checking group is going to be determined depending upon the material type & plant.
    -Go to new entries, specify material type, ex;-FERT
    & plant = checking group of availability check: 02
    D) Carry out for Availability check:
    Here we define checking rule for the Availability check & allocate them to the checking group. The checking rules specify the scope of the availability check. For a respective transaction, means which planned receipts & planned issues systems has to taken into consideration and also it determines whether system has to take RLT into consideration.
    Action:
    *Select checking group of availability check-02, checking rule=01
    *Go to details icon, & check which planned receipts & planned issues system has taken into consideration for availability check
    *save it, exit.
    E) Define procedure by Requirement class:
    Here we define requirement class whether on availability check & TOR should be carried out the setting that we carries out at requirement class level they are at global level. There settings automatically copied into define from of requirement class and vice versa.
    Action:
    *Choose requirement class: 041 & check availability check & TOR (requirement)
    F) Define procedure for each schedule line category:
    Here we carry out fine tuning setting for availability check at schedule line category level. Here we define whether system has to carry out Availability check for particular transaction.
    Ex:- if we want to implement a availability check w/o TOR for a particular transaction. According to settings at requirement class level TOR & availability check function activate & those setting will be copied into the schedule time category by default, so that at schedule line category level we deactivated TOR
    G) Determine procedure for each Delivery Item category:
    H) Checking group for updating back orders:
    CHAN

  • Availability check Problem in sales order according MRP sterategy

    hi,
    We are using strategy 56 for configurable final product and strategy 65
    for its variants.Requirement type is "ELV V". According this requirement type,
    it is not possible to confirm availability check and then deliver the
    sales order. We tried to mark availability check for requirement type ELV V in OVZG Tcode, but the
    following error came up: "Check against plan material can only be carried
    out w/o avail.check". Is there any setting to handle this problem to work
    with strategies 56 and 65? Is it some configuration that we forgot?
    Thanks,

    Yes, We have maintained planned del. time. and other fields also,
    My problem is that, To make assembly of material A we have two component material B and C.
    in the sales order of material A, system should check availability of component material B and C.
    please help
    vikas

  • ORA-00976: Specified pseudocolumn or operator not allowed here

    Hi,
    After 11gR2 upgrade we got error in insert statement.
    INSERT INTO SDE_TBL_FLEXTRIMSITROUT
    (BRANCHCD,
    SOURCECD,
    CURRENTNO,
    BATCHNO,
    DEPTCD,
    CCY,
    INITIATIONDATE,
    AMOUNT,
    ACCOUNT,
    ACCOUNTBRANCH,
    TXNCD,
    DEBITCREDIT,
    LCYEQUIVALENT,
    EXCHRATE,
    VALUEDATE,
    INSTRUMENTNO,
    RELCUST,
    ADDLTEXT,
    TXNMIS1,
    TXNMIS2,
    TXNMIS3,
    TXNMIS4,
    TXNMIS5,
    TXNMIS6,
    TXNMIS7,
    TXNMIS8,
    TXNMIS9,
    TXNMIS10,
    COMPMIS1,
    COMPMIS2,
    COMPMIS3,
    COMPMIS4,
    COMPMIS5,
    COMPMIS6,
    COMPMIS7,
    COMPMIS8,
    COMPMIS9,
    COMPMIS10,
    COSTCODE1,
    COSTCODE2,
    COSTCODE3,
    COSTCODE4,
    COSTCODE5,
    RELATEDACCOUNT,
    RELATEDREF,
    USERREFERENCE,
    ACCTPOSTOVERWRITE,
    EXCHRATEOVERWRITE,
    VALUEDATEOVERWRITE,
    ACCTBALOVERWRITE,
    ITRREFER,
    RefinanceAmount,
    PROCESSID)
    VALUES
    (vBranchCode,
    cCreateNewTrimsITR_rec.APPLSYS,
    ROWNUM,
    nBatchNo,
    cCreateNewTrimsITR_rec.DEPT,
    vCcy,
    TO_DATE(cCreateNewTrimsITR_rec.TRANSDATE, 'YYYYMMDD'),
    nAmount,
    vAccount,
    vAccountBranch, --added by subhashish
    vTxnCd,
    cDebitCredit,
    nLcyEquivalent,
    nExchRate,
    TO_DATE(cCreateNewTrimsITR_rec.VALUEDATE, 'YYYYMMDD'),
    vInstrumentNo,
    --'      ' || SUBSTR(cCreateNewTrimsITR_rec.ITRREFER,2,11),
    vFlxCntry || cCreateNewTrimsITR_rec.APNO,
    vDesc,
    cCreateNewTrimsITR_rec.TRANSOUC,
    RPAD(' ', 9),
    vExpenseMIS,
    vProductMIS,
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 9),
    RPAD(' ', 20),
    cCreateNewTrimsITR_rec.THEIRREF,
    RPAD(' ', 16),
    cActPostOverwrite,
    cExchRateOverWrite,
    cValueDateOverWrite,
    cAcctBalOverWrite,
    cCreateNewTrimsITR_rec.ITRREFER,
    cCreateNewTrimsITR_rec.REFIAMOUNT,
    nFlexOutProcessId);
    Error : ORA-00976: Specified pseudocolumn or operator not allowed here
    As per checking, found there is an issue in 11gR2 with insert query using rownum in values.
    Do anyone know how to solve this issue ?

    If there is a bug here, then it is in 10g, not 11.  Although it does insert a row, I don't think it does anything useful.
    SQL> create table t (id number, descr varchar2(10));
    Table created.
    SQL> insert into t values (rownum, 'One');
    1 row created.
    SQL> select * from t;
              ID DESCR
               0 One
    SQL> insert into t values (rownum, 'Two');
    1 row created.
    SQL> select * from t;
              ID DESCR
               0 One
    SQL> commit;
    Commit complete.
    SQL> insert into t values (rownum, 'Three');
    1 row created.
    SQL> select * from t;
              ID DESCR
               0 One
               0 Two
               0 Three
    John

Maybe you are looking for