Defining Schedules on MDS9500

If I do not want to use CLI, is there an option using DM or FMS to define schedules & jobs on MDS9500?
If there is how do I navigate?

The chart B1 in the Fabric Manager Configuration Guide located at:
http://cisco.com/en/US/docs/switches/datacenter/mds9000/sw/4_1/configuration/guides/fm_4_1/fmguide.html
states that schedule configuration is not supported via Fabric or Device Manager.
So unfortunately the answer to your question is no, it is not supported via FM or DM, only CLI.
-Mike

Similar Messages

  • Forecast delivery schedule lines consumption

    Hi,
    I cannot fully understand what is the logic behind the consumption of the forecast delivery schedule lines. This is how the problem can be exactly defined:
    - scheduling agreement with delivery orders (LZM)
    - JIT delivery schedules are not used and no delivery schedule is maintained... just a forecast delivery schedule
    - the whole process is manual, there is no EDI implied
    - the cumulative received quantity is updated by an ABAP development that is triggered at delivery goods issue
    The rest, happens normal - forecast schedule lines are updated weekly, the customer send pick-up sheets, a TAM delivery order is created, then delivery, GI...
    The problem: not always the MRP requirements generated by the forecast delivery schedule lines are consumed by the delivery order/GI. If the delivery orders / deliveries are made on the exact quantity of the schedule lines everything works fine. It is also ok when there are two successive delivery orders with a cumulative quantity that matches exactly the forecast line. As soon as a over-delivery is made, everything turns upside-down: older delivered schedule lines appear again in planning as if nothing was delivered until now...
    I suspect that the problem is related to the fact that the whole process is manual and updating the cumulative received quantity is not the only parameter that is counting... is it so? Or the forecast delivery schedule has to be respected 100% in terms of quantities and timing?
    I would really appreciate your help.
    Regards,
    H.

    Also please clarify whether delivery schedule lines in ME38 (even it is created automatically), in Planning time fence, will get affected by MRP run.

  • Schedule Line Block

    Dear All,
    Pls go through my requirement.
    I want to block the requirement for particular Materials in the sales order.
    So I had created New Item Category Group, Item Category & Schedule Line Category.
    Done all the necessary assignments also.
    Delivery block assigned to newly created schedule line via VOV6.
    Now I have created one quotation with one material.
    When I created a sales order by copying the quotation, delivery block is not coming by default w.r.t newly created schedule line.
    if I enter the same material in next line item in the same sales order, delivery block is coming by default against that schedule line.
    Issue: While copying from Quotation to Sales order, defined schedule line is coming in the sales order but not the Delivery block which is assigned in the settings of schedule line catergory.
    Pls Suggest.
    Rgds,
    Senni.B

    Hi,
    Please check the copy control settings in VTAA tcode:
    Go to VTAA
    Enter your Source and Target Order type:
    Then in the Schedule Line Section -- >> for your Schedule Line Category ... following settings has to be maintained:
    Copying Requirements: 501
    DataT: 201

  • [SD] table for Schedule line date

    If we display a sales order through Va03 and Go to tab Item overview. There is a excel sheet kind of display showing
    all items. The 12th col is 'First Date' and the f1 help says its 'Schedule line date'.
    I need to display this date in my report.
    <i>F1 Help Says :</i>
    <b>Schedule line date</b>
    The delivery date for the schedule line. The delivery date can be the
    Date requested by the customer, or (if the requested date cannot be met)
    Earliest date proposed by the system after automatic availability checks and delivery scheduling
    <b>Use</b>
    The system uses the delivery date for each schedule line together with predefined time estimates for delivery activities (such as picking and packing) to determine the
    Material availability date
    Loading date
    Goods issue date
    Transportation planning date
    <b>Dependencies</b>
    If you want the system to automatically determine the above dates, the Delivery scheduling and Transportation scheduling fields must be active in the sales document definition ( Tools --> Customizing, Sales and Distribution --> Basic Functions --> Delivery scheduling and transportation scheduling --> Define scheduling by sales document type).
    <b>Note</b>
    If there is more than one schedule line for the item, the system displays the earliest delivery date in the item and overview screens.

    Hi flora
    You can get he details of the schedule line data in the VBEP table.
    EDATU is the schedule line date
    regards
    kishore

  • Scheduling Agreement - Priority for GR Processing Time

    Dear Forum Members,
    While defining Scheduling agreement for a material we can define the GR processing time and Planned Delivery time,likewise we
    define in the material master also.
    1.While running MRP which one has the higher priority?
    2.After running MRP for the schedule line we are able to see only the delivery date,is there any setting to display the release date
    or the start date based on the planned delivery time of the scheduling agreement?
    Please suggest.
    Regards
    S Mangalraj

    Hi Mangalraj,
    For your question:
    1.While running MRP which one has the higher priority?
    -->GR processing time MRP-run will take it from material master data
    -->Planned delivery time, you can use t-code OMI8 to define the higher priority of SA or material master data
    2.After running MRP for the schedule line we are able to see only the delivery date,is there any setting to display the release date or the start date based on the planned delivery time of the scheduling agreement?
    -->Yes, in standard SAP system, you only can see the delivery date after MRP-run! As to the release date or the starte date which take planned delivery time of SA into account, it's only used to inform the buyer with purchasing transaction.
    Hope my answers can help you!
    Good luck
    Tao

  • Error in scheduling parameters for production orders

    Hi Guys,
    Greeting for the day u2026u2026u2026.
    I am trying to create production orders creation for own order  type ex MM01, but I am getting error message as u201C scheduling parameters are not defined for the order type u201C even though I have maintained following parameters as below,
    Production scheduler      -
    xxxxx,
    Detailed scheduling -
    check box of scheduling ticked,
    Rough cut scheduling    --- scheduling id u201301, scheduling and generate capa requi,, boxes     ticked,
    Adjust scheduling  -- requi to operation  date,
    Scheduling control for detailed scheduling ---backwards and check box of auto scheduling ticked
    Operation segment ---setup,
    All operation in order will be reduce
    Do not reduce,
    Could any one light on this issue,
    Thanks in advance,
    Mohan

    Hi,
      This error will come if you have not maintained Define scheduling parameters for production orders.
    Check this order type whether linked with respective plant in OPU3.*And give production scheduler * mark ie, all.*
    And in Define production scheduling profile - OPKP, link your order type in the page below.
    In material master work scheduling view, input production sch profile or prod scheduler.
    Regards,
    Dharma

  • Error in scheduling aggr for GIT

    Hello All,
    We have a requirement wherein we need to uncheck the IR and give net price as 0 for scheduling agreement.We are doing a dummy GR(for Goods in Transition).For this the user wants to unchekc the IR indicator and give net price as 0 but the system is giving error
    'No delivery costs allowed without invoice receipt'.This is more of CIN releated.please help me find a solution.
    Thanks,
    Rakesh.

    Hi,
      This error will come if you have not maintained Define scheduling parameters for production orders.
    Check this order type whether linked with respective plant in OPU3.*And give production scheduler * mark ie, all.*
    And in Define production scheduling profile - OPKP, link your order type in the page below.
    In material master work scheduling view, input production sch profile or prod scheduler.
    Regards,
    Dharma

  • Scheduling Agreement- ANY IDEAS FROM GURUS?

    Hai ALL,
                I have a req-
    Customer will place order with pre-defined schedule for the next month ( including schedule dates & Qtty).
    When User creating Sch.Agreement-VA31,
    Enters Material in line item & Total Qtty ( total req for the next month), then this qtty has to be divided equally into next month working days(will get from Factory Calender) into schedule lines.
    Is there any BDC, so that whenever user enter material & qtty, schedule lines can be divided into day wise in schedule lines tab?
    I have tried this from std, but i couldnt find.So thought of use BDC to split monthly req into day wise.
    Any Thoughts
    Edited by: SAP Consultant- on Dec 30, 2008 10:52 AM

    THanks for your reply,
    I have created my own rule by copying from SAP1.
    assigned this rule to instructions.
    created sch.agreement with Doc type:BL/LZ
    assigned instructions in control parameter tab.
    still sch.lines not splitting.
    can you explain, how splitting works while doing transaction?
    Have read SAP Help & customized according to that, But it is not splitting, checked SAP Notes, but nothing solves my problem

  • Scheduling in Real-Time Java

    Hello,
    I have some questions concerning how scheduling in fact is intended to be performed in a RTSJ based Real-Time Java System.
    As far as I understood, RTSJ requires pre-emptive priority-based dispatching of Schedulable objects.
    This means that the execution eligibility of a schedulable entity is mainly its priority.
    That causality is reflected within the specification with the (one-and-only specified) PriorityScheduler, which is the base scheduler for actual Real-Time Java applications.
    Furthermore, there is a notion of extensibility of that PriorityScheduler described by RTSJ,
    in order to provide further scheduling mechanims and feasibility analysis algorithms (please correct me if there are any wrong assumptions).
    This is the point, where everything becomes really weird to me ...
    As far as I could investigate, in most RTSJ implementations based on a POSIX compliant system underneath (like Java RTS does on RTLinux or Solaris)
    each (Realtime)JavaThread is mapped 1-to-1 to a light-weight process on the operating system level (e.g. a pthread).
    So far, we have no "green threads" within the JVM, but real LWPs scheduled by the OS.
    The difference between "normal" and "real-time" threads lies in the scheduling policy used for that mapping.
    While normal Java threads probably map to SCHED_RR or SCHED_OTHER, real-time threads are scheduled by the OS via the SCHED_FIFO policy in order to achieve a better real-time predictability.
    However, the OS's scheduling mechanisms automatically make decisions about the right positioning of a LWP within an appropriate run-queue, due to thread's preemption, blocking or release (even dynamic priority changes) activities and its scheduling policy.
    That's exactly why I ask myself, what is the need of a Scheduler representation within a JVM?
    Furthermore, how a Scheduler extension is able to incorporate with the threading model and the underlying scheduling mechanisms of the OS?
    One point could be a situation where a real-time JVM runs directly on top of the bare hardware and has to perform scheduling decisions on its own.
    The Scheduler API could then be understood as an extension mechanism of a kind of JVM-intern scheduler (e.g. the PriorityScheduler), thereby allowing scheduling decisions to be made even in user defined Scheduler implementations.
    A similar use case for an OS-based scenario could be if a JVM is intended to pass scheduling/threading routines of the underlying OS (eg. a part of the POSIX API)
    up to the Java application level in order to provide the opportunity for a kind of application defined scheduling (like e.g. in the MaRTE OS).
    Unfortunatelly, after introspecting the RTSJ API, both conclusions seem to me to be wrong.
    So far, Java RTS seems not to provide any mechanism for reaction on scheduling events/decisions, neither intra-JVM nor from an underlying OS outside of the JVM.
    Furthermore, there is no notion for incorporation with the base PriorityScheduler for making extended scheduling decisions.
    I hope this post could bring me more light into the scheduling idea behind Real-Time Java systems as intnded by the RTSJ.
    Sincerely,
    Vladimir

    Vladimir.Nikolov wrote:
    That means, that a scheduling policy different to PriorityScheduler can only be assigned to a Schedulable object if it is supported by the OS and the JVM?Well it has to be supported by that implementation of the RTSJ. Howe that is done - ie whether it requires OS support - depends on that VM, the OS and the actual scheduling policy.
    It also seems that at the current state of the art the PriorityScheduler representative within the JVM is intended only for manipulating a feasibility set of Schedulable objects (supporting online feasibility analysis)?
    However, since user-defined scheduling is not intended by the specification, applications have to rely on the feasibility analysis based on the underlying/supported scheduling mechanisms.
    Thus, in the current Java RTS implementation this would be the "default" feasibility mechanism based on the PriorityScheduler.
    Unfortunatelly I can not figure out the need of maintaining a feasibility set, since feasibility, as specified for the PriorityScheduler, is a simple asumption that we have "an adequatly fast machine to handle the periodic and sporadic load"?
    I actually assumed that feasibility analysis performs real cost budgeting taking into account deadlines and so on, but it seems to be specified simply to make a negative statement always when aperiodic tasks are involved ?The RTSJ scheduling framework provides support for feasibility analysis by defining the admission control methods eg setXXXIfFeasible. However the RTSJ does not, and can not, mandate any non-trivial feasibility algorithm because in simple terms no such general algorithms exist. There are some static feasibility tests in the literature and you could apply those offline to your application (assuming you can find the values of all the "magic" numbers in such formulae - which is generally not the case). At present the RTSJ doesn't support even these simple feasibility tests because blocking-time is not recorded in the release parameters - something being addressed in RTSJ 1.1. In any case unless there is a pluggable framework for feasibility tests it would be a waste of time for VMs to implement them given they can (more) easily be done offline using other tools.
    Only dynamic admission control is really of interest and as far as I am aware no such general dynamic admission control policies exist (anything you find in the literature is very context specific). So it is left up to an implementation as to whether they try and define dynamic admission control algorithms - and so far none have because they don't have one.
    In "Getting More Flexible Scheduling in the RTSJ" Wellings and Zerzelidis propose some (more or less) "minor" extensions to the RTSJ API in order to enable hierarchical scheduling within the fixed priority framework.
    Since Andy Wellings is a member of the RTSJ Technical Interpretation Committee, is there any attempt to evolve the specification in a similar direction as described above, in order to support more flexible scheduling mechanisms and feasibility analysis?If there is ever a RTSJ 2.0 then more sophisticated scheduling support is one of the items on the wishlist. But there's no guarantee there ever will be a RTSJ 2.0
    David Holmes

  • Scheduled start and Finish date .

    Hi Everyone,
    I am facing a problem in dates in creating a process order in Production .
    In the tcode COR1, when input the BASIC START DATE manually, the BASIC FINISH DATE ,scheduled start date and finished dates should get calculated automatically  as per standard SAP.
    The problem that I am facing is that , if I input the BASIC START DATE in future , the scheduled start date and finished dates are always coming as  the system date.
    whatever date I input in the BASIC START DATE  the scheduled start date and finished dates are always coming as  the system date.
    But this is not happening in quality and development server .
    Please help me if you have any solution
    Thanks
    Bijay

    Dear ,
    1.Scheduling parameter for new process order type and plant combination, to be defined at OPUZ . U can copy the settings at standard order type PI01.Here you should keep Backward Scheduling as Scheduling Type  and Keep the adjustment  Scheduling as Adjust to Basic Date , depenent requirement Date .
    Now  Order Basic finish date = Order Basic start date + float before prod + Lead Time of Operations (operation time from routing )+ float after prod.
    These floats are predefined in SMK  and assinged to material master .It comes through Planned Order after MRP run andcoped to Production Order .
    .2.Check and Define Scheduling Margine key in MRP -Carry All over all palnt paremtres (OPPQ)
    If you are MTS process , then Keep the Scheudling Type as Forward .Enter the Basic Start date and Scheduling Margine Days ( Opening periods , FBP, FAP) and then hit the Scheduling Indicator .It will calcuate all the dates based on the SMK and operation setup and propose you Basic Finish Date .
    So adjust the Flaots in SMK tab in process order , enter Basic Finish Date , Choose Bacward Scheduling to arraive Basic Start  or Go in reverse direction by choosing Forward scheduling .
    Hope its clear
    Regards
    JH

  • Process order scheduling based on in-house production time.

    Hello!
    I have following problem. My SAP system is configured in that way that process oedrs are schedulled based on times saved in master recipies. When I input data to in-house production time in master data for materials and make new process order, this time is not
    taken into account.
    Where I have to change configuration to use in-house production time from material master data to make scheduling process orders.
    Regards
    Bogdan

    Dear
    Process Order /Production Order scheduling ( Lead Time Scheduling )  based on the Operation timings in the routing not based on the Material Master In house Production Time in Work Scheduling View .
    If you are loking for Basic Date Scheduling then it will happend based on material master , scheduling margin key  at material master level .
    It depends the selection of Schedueling indicator while excetion of MRP in MD02 .
    In case of Process order specifically , you need  to schedule the Master Recipe and check whether operations are getting scheduled, if it is not then you need to first the problem, which may be because of wrong "Forumla" or paramater assigned in resource or the resource is not maintained for Finite scheduling (capacity header).
    Master reciepe can be schedule in the change transaction C202, and from menu you would find the option to schedule the recipe .
    Also  check the OPU3/OPU5-Define scheduling parametres wether scheuling , adjust scheduling , scheuling type , logs all are in place .
    Check and revert
    Regards
    JH

  • OWB: Not Able to Deploy Schedule, Says 'No dates could be generated'

    Logging in as repository owner.
    I have defined schedule and tagged with the process.
    But there is no 'Deploy' option available against the schedule in control center.
    Then tried to Edit the schedule where in 'Schedule Preview', its showing error message as 'No dates could be generated because the design repository is not installed on Oracle 10g or later. This does not prevent you from deploying the schedule to a 10g schedule location.'
    Please help me for this.

    Logging in as repository owner.
    I have defined schedule and tagged with the process.
    But there is no 'Deploy' option available against the schedule in control center.
    Then tried to Edit the schedule where in 'Schedule Preview', its showing error message as 'No dates could be generated because the design repository is not installed on Oracle 10g or later. This does not prevent you from deploying the schedule to a 10g schedule location.'
    Please help me for this.

  • About schedule report by broadcaster

    Hello:
       Now I send query to user by E-mail immediately,the status is successful. I define schedule job also send query by E-mail.I can not find the request in T-CODE 'SOST' on default time.
    Hope this clear.Hope anyone can give me advice to solve the problem.
    Regards&Thanks
    zagory

    Check in SCOT and see is there a job which is scheduled for sending emails or  whether there is any errors in sending the email?
    If there is no job scheduled you can send emails manually by selecting the execute icon from SCOT.
    Thanks.

  • Define sd organisational structure?

    define sd organisational structure?

    SD Configuration:
    Enterprise Structure:
    1. Maintaining Sales Organization
    Sales Organization is an organizational unit responsible for the sale of certain products or services.
    IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization
    2. Assigning Sales Organization to Company Code
    This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code
    3. Maintaining Distribution Channel
    Distribution Channel is the way, in which Products or Services reach Customers.
    IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel
    4. Assigning Distribution Channel to Sales Organization
    This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization
    5. Maintaining Division
    Division is a way of grouping materials, products, or services.
    IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division
    6. Assigning Division to Sales Organization
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
    7. Setting up Sales Area
    All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.
    IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area
    8. Assigning Sales Organization- Distribution Channel- Plant
    Plant is created ny MM Consultant.
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant
    9. Define Shipping Points
    Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
    IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point
    10 Assigning Shipping Point to Plant
    This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
    IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant
    Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
    11. Defining Common Distribution Channels for Master Data
    Use
    The purpose of this activity is to define distribution channels which have common master data..
    Procedure
    Access the activity using one of the following navigation options:
    IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
    Transaction Code: VOR1
    12. Defining Common Divisions for Master DataUse
    The purpose of this activity is to define distribution channels which have common master data..
    Procedure
    Access the activity using one of the following navigation options:
    IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
    Transaction Code: VOR2
    Pricing Procedure
    In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
    In SD, the steps to configure Pricing procedure are as under:
    Step 1:
    Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
    Step 2:
    Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
    Step 3:
    Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
    Step 4:
    a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
    b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
    5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
    Normal Sales Order Cycle:-
    Step 1: Sales Document Type
    IMG > Sales and Distribution > Sales > Sales Documents >
    Sales Document Header:
    1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
    2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
    3. Assign Sales Area To Sales Document Types:
    A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
    B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
    Sales Document Item:
    1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
    2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
    Schedule Line:
    1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.
    2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.
    Step 2:
    IMG > Logistic Execution > Shipping > Deliveries >
    1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.
    2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.
    3. Define Number Ranges for Deliveries: Ensure to maintain number range.
    Step 3:
    IMG > Sales and Distribution > Billing >
    1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
    2. Define Number Range For Billing Documents: Ensure to maintain number range.
    3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.
    The configuration differs from scenario to scenario & requirement of the client.
    Regards,
    Rajesh Banka
    Reward point if useful.

  • Doubts in Delivery scheduling

    Hi all,
    I am unable to understand the delivery scheduling concept.
    For ex  I am creating a sales order for the material xxx today.Requested delivery date is todays date.there is no stock available for the material xxx today. But there is a purchase order in which the delivery date is 30th dec.
    So obviously the system checks the avaialbility and asks whether the delivery(schedule line date) can be confimed on 30th dec.When I click continue the material avai date in the sales order is changed to 30th dec.
    At the same time loading date, trans plann date, goods issue date and the schedule line date is changed to 30th dec.But I dont want this
    I want the loading date to be 1st Jan.Trans planning date on 2st jan, goods issue date is 4rd jan.and the delivery(schedule line date) to be on 6 th jan.How to perform this.
    I have given determine load time and pick pack time as C and have given 1 day for loading and pick/pack.
    But the loading date is not changed to 1 st Jan.
    Please correct me where I am wrong.What setting I have to do to perform the above
    Regards
    Mano

    Dear Mano,
    First you have to maitain the working hours of your plant/shipping point :
    how many hours per day? from whent to when
    How many days per week?  which days.
    Customizing : Logistics execution>>Shipping>>Basics function>>Scheduling>>delivery scheduling and transportation scheduling>> Maintain working hours.
    Then, you define for the shipping point the loading time and the pick/pack time "Duration"
    you have mention how many hours/minutes requested by each operation. "hhhhhh:mm"
    example : if you are working in your plant 8 hours/day. and the pick/pack take 3 days. so you mention in the duration Pick/pack w-hours 24:00.
    to set these go to
    Customizing : Logistics execution>>Shipping>>Basics function>>Scheduling>>delivery scheduling and transportation scheduling>>Define Scheduling By Shipping Point.
    In the fields  :
    Determine load. time ---> set the indicator C
    Loading time - w.hrs---> hhhhhh:mm  for example 9 days equivalent to 72:00 if you work 8 hours per day
    Det.pick/pack time---> set indicator C
    Pick/pack time-wk hrs----> hhhhhh:mm
    ps : I have tested thes information before posting.
    regards

Maybe you are looking for