Addional lead time for Sales BOM kitting process

When a Sales Order BOM Sales Order is scheduled, we would like to have a lead time added for the Shipping kitting step.  So the pick date will be X number of days before the ship date.
Is there a way to do this is ?
Thanks,
Doug Karien.

Hi DK,
Go to Ent structure > Definition > LE > Define shipping point, choose your shipping point, click on detailsand check there, "Rounding work days" filed may provide you some soln.
Regards
SD

Similar Messages

  • What are the User Exits for Sales Order creation process?

    Hi,
    what are the User Exits for Sales Order creation process? how can I find them?
    thanks in advance,
    will reward,
    Mindaugas

    Please check this info:
    User Exits In Sales Document Processing
    This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
    Involved program components
    System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
    MV45ATZZ
    For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
    MV45AOZZ
    For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
    MV45AIZZ
    For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
    MV45AFZZ and MV45EFZ1
    For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
    User exits in the program MV45AFZZ
    The user exits which you can use for modifications in sales document processing are listed below.
    USEREXIT_DELETE_DOCUMENT
    This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
    For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
    The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
    USEREXIT_FIELD_MODIFICATION
    This user exit can be used to modify the attributes of the screen fields.
    To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
    The usage of the field groups (modification group 1-4) is as follows:
    Modification group 1: Automatic modification with transaction MFAW
    Modification group 2: It contains 'LOO' for step loop fields
    Modification group 3: For modifications which depend on check tables or on other fixed information
    Modification group 4: is not used
    The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
    This FORM routine is called up by the module FELDAUSWAHL.
    See the Screen Painter manual for further information on structuring the interface.
    USEREXIT_MOVE_FIELD_TO_VBAK
    Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBAP
    Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBEP
    Use this user exit to assign values to new fields at the level of the sales document schedule lines.
    The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBKD
    Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
    The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
    USEREXIT_NUMBER_RANGE
    Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
    The user exit is called up in the FORM routine BELEG_SICHERN.
    USEREXIT_PRICING_PREPARE_TKOMK
    Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
    USEREXIT_PRICING_PREPARE_TKOMP
    Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
    USEREXIT_READ_DOCUMENT
    You use this user exit if further additional tables are to be read when importing TA01 or TA02.
    The user exit is called up at the end of the FORM routine BELEG_LESEN.
    USEREXIT_SAVE_DOCUMENT
    Use this user exit to fill user-specific statistics update tables.
    The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
    Note
    If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
    USEREXIT_SAVE_DOCUMENT_PREPARE
    Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
    The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
    User exits in the program MV45AFZA
    USEREXIT_MOVE_FIELD_TO_KOMKD
    Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMPD
    Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMKG
    Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_MOVE_FIELD_TO_KOMPG
    Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_REFRESH_DOCUMENT
    With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
    For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
    The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
    The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
    User-Exits in program MV45AFZB
    USEREXIT_CHECK_XVBAP_FOR_DELET
    In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
    USEREXIT_CHECK_XVBEP_FOR_DELET
    In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
    USEREXIT_CHECK_VBAK
    This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
    USEREXIT_CHECK_VBAP
    This user exit can be used to carry out additional checks (e.g. for completion) at item level.
    USEREXIT_CHECK_VBKD
    The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
    USEREXIT_CHECK_VBEP
    This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
    USEREXIT_CHECK_VBSN
    You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
    USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
    USEREXIT_FILL_VBAP_FROM_HVBAP
    You can use this user exit to fill additional fields in the sub-item with data from the main item.
    USEREXIT_MOVE_FIELD_TO_TVCOM_H
    You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    USEREXIT_MOVE_FIELD_TO_TVCOM_I
    You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    User-Exits for product allocation:
    The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
    USEREXIT_MOVE_FIELD_TO_COBL
    Option to include new fields in structure COBL.
    USEREXIT_COBL_RECEIVE_VBAK
    Option to assign values from the document header to the new fields.
    USEREXIT_COBL_RECEIVE_VBAP
    Option to supply values from the item to the new fields.
    USEREXIT_COBL_SEND_ITEM
    A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
    USEREXIT_COBL_SEND_HEADER
    A changed field can be copied from the structure to the header (see source text MV45AFZB)
    USEREXIT_SOURCE_DETERMINATION
    You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
    USEREXIT_MOVE_FIELD_TO_ME_REQ
    With this user exit you can include additional fields for the following fields:
    EBAN (purchase requisition)
    EBKN (purchase requisition-account assignment)
    USEREXIT_GET_FIELD_FROM_SDCOM
    Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
    USEREXIT_MOVE_WORKAREA_TO_SDWA
    You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
    User-Exits for first data transfer:
    The following user exits can only be used for the first data transfer.
    Note
    Only use the user exits if the names/fields do NOT have the same name.
    USEREXIT_MOVE_FIELD_TO_VBAKKOM
    Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
    USEREXIT_MOVE_FIELD_TO_VBAPKOM
    Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
    USEREXIT_MOVE_FIELD_TO_VBEPKOM
    Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
    USEREXIT_MOVE_FIELD_TO_VBSN
    You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
    USEREXIT_MOVE_FIELD_TO_KOMKH
    You can use this user exit to include new fields for batch determination (document header).
    USEREXIT_MOVE_FIELD_TO_KOMPH
    You can use this user exit to include new fields for batch determination (document item).
    USEREXIT_CUST_MATERIAL_READ
    You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
    USEREXIT_NEW_PRICING_VBAP
    Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
    USEREXIT_NEW_PRICING_VBKD
    Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
    User-Exits in Program MV45AFZD
    USEREXIT_CONFIG_DATE_EXPLOSION
    The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
    User exits in the program FV45EFZ1
    USEREXIT_CHANGE_SALES_ORDER
    In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
    If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
    User-Exits in Program RV45PFZA
    USEREXIT_SET_STATUS_VBUK
    In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
    The following workareas are available for this user exit:
    VBUK (header status)
    FXVBUP (item status)
    FXVBUV (Incompletion)
    USEREXIT_SET_STATUS_VBUP
    In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
    The following workareas are available for this user exit:
    FXVBAP (Item data)
    FXVBAPF (Dynamic part of order item flow)
    FXVBUV (Incompletion)
    USEREXIT_STATUS_VBUK_INVOICE
    You can use this user exit to influence billing status at header level.
    User exits in the screens
    Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
    Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
    For field transports, you do not have to make changes or adjustments.
    Example
    A new field, VBAK-ZZKUN, should be included in table VBAK.
    If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
    User Exits in Program MV45AFZ4
    USEREXIT_MOVE_FIELD_TO_KOMK
    You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
    USEREXIT_MOVE_FIELD_TO_KOMP
    You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
    User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
    EXIT_SAPFV45P_001
    You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
    Regards
    Eswar

  • Lead Time for manufacturing and its corresponding Quantity in Material Mast

    Hi all ,
    Do we have any feilds in SAP Material Master
    which are useful for
    1) Lead Time for manufacturing
    2) Manfactured Lead Time Quantity
    if the mateials are produced inhouse.
    thanks
    ksr

    Dear,
    There are no such a fields in material master, But in MRP 3 view you will get theotal replenishment lead time field.
    Which use for the produced in-house if the replenishment lead time is included in the availability check:
    This is nothing but the  in-house production time and, if available, the goods receipt processing time.
    Also refer this link to calculate the in-house production time correctly,
    Total Manufacturing time for assembly
    Regards,
    R.Brahmankar

  • Lead Time for Purchasing Material & Manufacturing Material

    The query is related to the process of Material Requisition planning.
    I need to know from where exactly the system picks up the lead time for generating Purchase requistions?
    - For purchased material (lead time from placing order to actual recipt of material, time needed for QC checking till its release)
    - For own manufactured material (lead time at each work center in the recipe along with actual time required for a particular process)

    Hi
    for your information for  any material the data for the lead time comes from the material master
    http://help.sap.com/saphelp_46c/helpdata/en/fd/45b7ee9d6411d189b60000e829fbbd/frameset.htm
    if you click on the link you can get the entire process.
    as you can see SAP picks up the deatil from the MRP2 view of the material master.
    hope this  is helpful.
    regards
    Vignesh.

  • Lead time for Purchase items

    I had read that Lead time for Purchased items is calculated per 7 working days / week, by default. However, when I checked this, I found that the MRP planned orders were always considering our mfg calendar that has 5 working days / week.
    Anyone tried this.

    Industries & Product which have stabilsed have the same measuring yard and standards. This is also applicable for calendar working days, otherwise we need to device the 'interface' because the results would be weird, specifically when we speak of 'supply chain'.
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by erik anthonsen ([email protected]):
    this is correct. it is up to individuals to change the amount of days that the company manufactures as their standard. if your facility is running 7 days a week-----use 7 days at setup<HR></BLOCKQUOTE>
    null

  • Lead time for POs

    hello, I am new to this bog, but can anyone help me with a t-code for getting the lead time (planned delivery time) report i.e. how can we identify if a PO has materials with longer lead times for a set of purchasers/vendors ?

    We experienced such a problem ... using only BEx functionalitites means (at the end) using Virtual KF ...
    Considering the complexity calculation to be made this is a time consuming approach that has even an high response time (in terms on minutes ... depending on the amount of data)
    During Data Load create two more technical KFs to store intermediate values of the formula (X^2 and a counter ...): this because of the fact that BEx formulas work AFTER Aggregation.
    Hope it helps
    GFV

  • Business Flows for Sales and Contracts process

    Hi,
    I needs Business Flows for sales and contracts process for my project.
    Does anybody knows where i can find these BFA ?
    Thanks
    Regards
    Mehdi

    Hi mehdi;
    Please check below and see its helpful:
    R12 Responsibilities And Roles Based On Business Flows [ID 406401.1]
    Regard
    Helios

  • Drop Ship processing for Sales BOM

    Hi,
    We have a requirement to have a Sales BOM drop shipped from a Vendor. Only the header material is relevant for pricing and purchase order. However, we have a business requirement to explode the sales BOM in the sales document and billing document to address statistical pricing requirements at the component level.
    Since only the header material is required in the PO, it has a billing relevance of 'F'. However, we have set the components to be relevant for order related billing. Standard SAP opens up the components for billing even though a vendor invoice for the header has not been received.
    Can copy control be used to control the components from being billed unless the header is billed AND the quantity of component materials modified based on the header material being invoiced ? Is it possible to only explode the sales BOM in the billing document using a billing document exit ?
    Would appreciate suggestions from the forum.
    Regards

    Hi
    The billing document creation can be controlled through the copying requirement in Copy Control of Billing documents.
    Transaction VOFM | Billing documents: Create a new requirement which prevents billing unless the parent item has the vendor invoice receipt.
    This requirement has to be then assigned to the respective billing and sales document type in copy control.
    Regards,
    Vinu

  • Delivery lead time in Sales Order--URGENT

    Hi SAP GURUS,
    How the Delivery lead time works in Sales Order  i.e
    "From the time a confirmed Sales order is punched till the time we have delivered the material"
    How to confgure to use effectively

    When you create sales order, system automatically proposes data based on configuration settings.
    1. Check the schedule line proposed by system in sales order. Let's say CP. Go to transaction VOV6 and see if availability check is checked.
    2. Check the requirement type proposed by system in sales order. Let's say 041. Go to transaction OVZH and see what requirement class has been assigned to it. Let' say 041.
    3. Go to transaction OVZG and see if availability check has been checked for this requirement class 041.
    4. Check the shipping point proposed by system in sales order.
    Go to transaction OVLZ and check Loading time & pick pack time maintained there for this shipping point. If there is nothing let's say we have 24 hours and 24 hours respectively.
    5. Check the route proposed by system in sales order. Let's say route selected is 000003. Go to transaction 0VTC and see Transit duration & Transportation lead times maintained there. Let's say timings maintained are  2  days and 1 days respectively.
    Now let's say a customer calls and says he wants a material delivered on Apr 25. Now what the system does is that it does backward scheduling. i.e. it goes backward from delivery date i.e. 25th April. It reduces 3 days for transit time, reduces time taken for loading time, reduces days taken for arranging transport, reduces time taken for pick pack. After calculation it arrives at date Apr 21. Now it checks whether material is available on this date i.e. Apr 21.
    If material is available, it confirms delivery date.
    Otherwise, if material is not available on Apr 21, it determines date on which material is available. Let's say material is available on Apr 23. Now, system immediately carries out forward scheduling. So it starts calculating from Apr 23 and adds time and dates maintained for picking & packing; transportation lead time, loading time and transit time.
    Also note that system takes into account factory holidays, factory timings when it is calculating above. If factory works 24 hours and is closed on Saturday & Sunday, system arrives at date Apr 30. It now confirms delivery date as Apr 30 to customer.
    I have given a simple example. There are many other aspects you can configure on scheduling.

  • Setting for "Exploding BOM in Process order"

    Hello All,
    I have a requirement where I want to create BOM for sales order using CS61 and then I want to explode this BOM automatically in Process order(Production order) and it should happen automatically.Please let me know the settings for the same.
    Regards,
    Rohit

    Hi  Subhro,
    I thought you are talking about the BOM material for the ref technical object say functional location or equipment in the service order. If you have maintained the BOM for the equipment you can pull the all the component list in the component tab.
    In the component tab click on the List button available in the component tab. You will see the list of BOM material.
    DP

  • What is the maeaninf of lead time offset in BOM

    Can anybodye xplain me the maeaning of lead time offset in BOM

    Hi,
    In situations where orders have long lead times, this scheduling procedure can result in components being provided much earlier than they are actually needed in the production process. To avoid this situation, the dependent requirements date of the subordinate component can be rescheduled by the follow-up time. With the follow-up time the dependent requirements date of the components is displaced from the order start date further into the future.
    The lead-time offset (in workdays) for the component in relation to the start date for production of the superior assembly. This value is not included in lead-time scheduling for a task list.
    Displacing the Dependent Requirements Date in the Future
    If you have entered a positive value in the bill of material, the dependent requirements date of the component is displaced in the future, starting from the order start date of the assemblyu2019s planned order.
    Order start date of the assembly: 11.30.1999
    Lead-time offset: 2+
    Dependent requirements date of the component: 12.02.1999
    Bringing Forward the Dependent Requirements Date
    If you have entered a negative value, the dependent requirements date will be brought forward.
    Order start date of the assembly: 11.30.1999
    Lead-time offset: 2-
    Dependent requirements date of the component: 11.28.1999
    Regards,
    Alok Tiwari

  • MOQ and Lead Time in sales order

    Hi: everyone
    I want to limit order MOQ when creating sales order (order type OR). however, sap cannot do that even if I set rounding profile, or rounding value, or mixmum value in MRP view of material master data.
    for lead time, when running ATP check, sap give me a delivery proposal. I want the "delivery proposal" is mandatory. that means user cannot change the delivery date manually.
    thanks
    Henry

    Hi: Everyone
    MOQ store in "sales 1" view not "MRP" view, and change message type v4082 from w to e via t-code OVAH.
    Henry

  • OPR LEAD TIME OFFSET IN BOM

    Hi all ,
    my scenario is like :
    FG contains SFG10 , and SFG10 omtains SFG20
    I am using backward scheduling , Results in MRP run are as :
    FG :          30.03.2008      17:30:00
                     25.03.2008     15:20:00
    (SFG10 frwrd scheduling start time is 09:30:00)
    SFG10:      25.03.2008      12:30:30
                     25.03.2008       09:30:00 (start time of workcenter).
    in BOM of FG for component SFG10 i have mainatined ( 120- min ) opr lead time offset, to start the SFG10 at 11:30:00 , but it is not happening , whr i am missing ?
    Regards,...
    Edited by: venky  shree on Mar 26, 2008 7:32 AM

    Hi,
    pls check with the operation start time and not wth the order start time
    (ie, oprn for which the component you have assigned) in CO02-oprns overview-dates tab.
    you can see that from the start time of the operation,the reqmt time for the component will be 120 min ahead (CO02 -component overview-general tab -dates tab-reqmt date ) .
    Regards,
    sheik

  • Lead Time for Procurement Materials

    Hi Gurus,
    Can you elaborate on hierarchy for procurement lead time materials. If there is lead time given in Material Master as well as Info record and Source List. Then which lead time will be considered by the system for procurement?
    Also clarify what is the significance of Source list for Material Master?
    Regards,
    Pradeep

    Hi
    System takes more priority for lead time mainatained in Info record ahead of material master's planned delivery time. Along with planned delivery time, purchase processing time maintained in OMEW and GR processing time in Material master.
    Source list defines the vendor/list of vendor who supply material for a plant in the given validity period. A vendor can be fixed or blocked. FIxed vendor makes MRP to create source assigned PO. later it can be made as PO automatically.Scheduling agreement with sourcelist and MRP relevency indicator 2 can give automatic schedule line.
    Regards
    Antony

  • Schedule Lines for Sales BoM Material

    Hi All,
    When i trying to maintain the multiples schedule lines for the Sales BoM Material(Both Header and Item), system is not allowing to maintain it.Please guide me how to achieve this?

    Hi,
    "Schedule Line allowed" is enabled at Item category. The Requirement is If we have multiple schedule lines for BoM Line Item, we are not able to maintain. Suppose the Order Quantity is 50 Units and we need schedule line of 10 Quantity each month. We are not able to maintain. System takes the complete 50 quantity and do the availability check and proposes the availablity Date. We are not able to maintain different schedules manually.

Maybe you are looking for

  • JDBC Receiver doesn't work (and doesn't show any error msg)

    Hi all, I'm now trying to test a file to JDBC scenario. After many msgs sent, I'm checking at sxmb_moni and the file sender is ok, the msg mapping is ok, and the JDBC receiver is ok - the status is "processed successfully". But... in my database (Ora

  • IBooks Author TrueType font problem

    I'm working on an iBook and I'm attempting to use a truetype font for a page heading, but when I preview it on my iPad, the font shows up correctly for a brief moment, then is replaced by something generic. I have confirmed in the Font Book applicati

  • How to use CWGPIB API

    Hello, I want to use CWGPIB component to control a GPIB device such as power supply or spectrum. First thing is to search the what GPIB device is on the bus, but I don't know which given API can be used to scan the device by feeding back parameters s

  • HandShakeStatus

    I write a NIO Server program with SSL(JSSE).I encount some problem in here. SSLEngineResult res = sslEngine.wrap(////); HandshakeStatus hs = res.getHandshakeStatus(); HandshakeStatus hs2 = engine.getHandshakeStatus(); in my program ,hs = FINISH but h

  • Problems using the letterbox filter

    Hello, I am having a problem compressing from Final Cut via Compressor into an Mpeg-1 file. I shot (and edited) in 16:9 but the Mpeg-1 files turn out squeezed up in 4:3. I was advised that the letterbox filter would be a way round it but when I go in