Remediation Schedule - Date Specific

In my organization, we are only allowed to patch computers from 10:00 pm until 6:00 am the next morning. I want to use the Remediation Schedule - Date Specific function for deploying patches and stay within my narrow window of time, and I thought I could use the "Start at a random time between Start and End Times" feature.
For example, I wanted to start patching on 02/25/09 starting at 10:00 pm, ending at 6:00 am, and I wanted the same schedule for 02/26/09. I added 02/26/09 and 02/27/09 as Start Dates, checked the "Process immediately if device unable to execute on schedule" option, selected the "Start at a random time between Start and End Times" feature, and set the Start Time for 10:00 pm and the End Time for 6:00 am. Unfortunately, I have computers patching at 11:00 am on 02/26/09, which is not at all what I intended.
Do the Start and End Times have to fall on the same date? Based on how I did it above, what logic is ZENworks using to determine that it's ok to patch at 11:00 am? I was trying to mimic the old-style blackout schedule we used to have with PatchLink. Is it even possible to do it without having to specify a content blackout schedule, which would effect not only patch bundles, but my bundles, settings, and policies?

mdstewar,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Similar Messages

  • Infotype 41 (Date Specification)

    Hi,
    Can anybody explain clearly what is the difference between Date Type 01 (Technical Date of Entry) and Date Type 07 (Hire Date) in infotype 41 (Date Specifications).
    Thanks in advance.
    Regards
    Sudarsan

    Hi,
    Hope this explanation helps
    Day Type is an indicator that a certain calendar day is payment-relevant, that is, an employee is paid for working that day.
    An employee's scheduled attendance can differ from the employee's daily work schedule.
    Example
    Two day types are defined in the standard SAP System. Day type "0" or "blank" indicates a paid workday and day type "1" indicates days that are paid but no work is performed. Therefore, public holidays are assigned the day type "1."
    If a calendar day is assigned the day type "1," than the day is considered "off" and is paid, although the employee usually works on that day according to the employee's daily work schedule. This is the case, for example, when a public holiday is a Thursday.

  • URGENT:Schedule date restricted to a date in SO

    Hi All,
    I was trying to schedule a sales order, but it restricted to date like (31-dec-2008), I can't change this date. Is there any setup for ,why schedule date is restricted to a specific date? Please help.
    Thanks,
    Shishir

    I tried after logout, that date restriction was gone, but now it' showing message "Unable to find calendar date". I changed the calender date by Inventory->setup->organization->calender and rebuild it , rebuild program is throwing error. Is these are right steps or I have to do anything else.
    regards,
    Shishir

  • MRP SCHEDULING DATES IN R3

    Hi guys,
    I need to understand How MRP scheduling dates are calculated for <b>external procurement</b>
    I understand scheduling date is calculated from the following...
    Purchasing processing timePlanned delivery timeGR processing time...
    1. What is the default scheduling either backward scheduling or farward scheduling??
    2. Where we can set as per our requirement??
    3. Delivery date is calculated from individual requirement date?? or It is calculated from MRP running date for all the requirements??
    For example the scenario is as follows:
    The requirement is for continuourly for 3 days from today i.e.21.09.2007,22.09.2007 and 23.09.07...
    Supposing purchasing processing time is 0, Planned delivery time is 10days and GR processing time is 0..
    What will be the delivery date of each above requirement???
    Can any one throw some idea on this...
    sundar...

    Hi
    Please refer the link explaining the MRP configurations.Please go thru the file and reply if you have any specific doubts.
    http://www.sap-topjobs.com/SpecialPP/overviewdoc.pdf
    Regards
    RamakrishnA

  • Schedule Date

    Hi All,
    Got a requirement to fetch Job Scheduled Date from Tidal. I am new to this Tidal, Please give me hint to achive this.
    Thanks!!
    Prasad G

    Could you elaborate?
    Config
    Tidal can use offsets, etc so an admin you can set that the "day" looks like in the configuration
    Job Activity
    Jobs typically use a calendar so you can also look at the job definitions (although you can have jobs that are ad-hoc/triggered other ways)
    Project Schedule
    You can forecast ahead if you need to look at a specific day to see if a job would be in schedule or not
    Marc

  • Patch Policies not applying when set to Date Specific

    I have been trying to use patch policies for a while but can't seem to get
    them working very well. In 'Patch Policy Enforcement Settings' I have set
    a schedule using 'Date Specific' and 'Process immediately'. If I check the
    patch status policy I see 100 targeted/ 12 Effective/ 0 Not Effective/ 88
    Pending. The 88 never move from pending even though almost all of them need
    the required patches. If I set the schedule to Recurring and 'When a device
    is refreshed' it basically tries to install the patches on every refresh
    cycle even though the device no longer requires the patches. This happens
    on every device targeted by the policy.
    Digging into the actually bundle that gets created I can see in the install
    actions the Install Frequency is set to 'Install always' which may explain
    why it runs through each patch every refresh when it is set to install on
    refresh.
    The documentation on this new feature doesn't go into much detail on how
    everything actually works. I would guess the correct functionality would be
    once a policy is enforced on a machine it would no longer try to keep
    installing the same patches from the policy since they are not needed.
    Using the Enforcement by 'Date Specific' seems to be broke also.
    Jim Koerner
    Server - ZCM 11.3.1FTF1 and Internal Database on Win2008R2x64
    Clients - ZCM 11.3.1FTF1 on Win7SP1x64

    Originally Posted by Jim Koerner
    Sounds just like it. Missed when I was browsing the knowledge base. doing
    some more detailed searching I fount this in readme for 11.3.1 "Defects
    addressed 848442 Process immediately if device unable to execute on
    schedule" option doesn't work of Patch Policy Enforcement Settings. In my
    case this is not fixed and I am at 11.3.1FTF1
    I will have to put in a SR and see if anything has been done with it since.
    Jim
    "thsundel" wrote in message news:[email protected]...
    Jim Koerner;2337983 Wrote:
    > I have been trying to use patch policies for a while but can't seem to
    > get
    > them working very well. In 'Patch Policy Enforcement Settings' I have
    > set
    > a schedule using 'Date Specific' and 'Process immediately'. If I check
    > the
    > patch status policy I see 100 targeted/ 12 Effective/ 0 Not Effective/
    > 88
    > Pending. The 88 never move from pending even though almost all of them
    > need
    > the required patches. If I set the schedule to Recurring and 'When a
    > device
    > is refreshed' it basically tries to install the patches on every refresh
    > cycle even though the device no longer requires the patches. This
    > happens
    > on every device targeted by the policy.
    >
    > Digging into the actually bundle that gets created I can see in the
    > install
    > actions the Install Frequency is set to 'Install always' which may
    > explain
    > why it runs through each patch every refresh when it is set to install
    > on
    > refresh.
    >
    > The documentation on this new feature doesn't go into much detail on how
    > everything actually works. I would guess the correct functionality
    > would be
    > once a policy is enforced on a machine it would no longer try to keep
    > installing the same patches from the policy since they are not needed.
    > Using the Enforcement by 'Date Specific' seems to be broke also.
    >
    > Jim Koerner
    > Server - ZCM 11.3.1FTF1 and Internal Database on Win2008R2x64
    > Clients - ZCM 11.3.1FTF1 on Win7SP1x64
    Could be this: http://www.novell.com/support/kb/doc.php?id=7015217
    Thomas
    thsundel
    thsundel's Profile: https://forums.novell.com/member.php?userid=128
    View this thread: https://forums.novell.com/showthread.php?t=480214
    Yes, please do open a SR if you can..
    Thomas

  • Trap syntax error in trap-schedule.dat alert; possibly SMC related

    Receiving many ID xxxxxx daemon.alert events every hour. The message is:
    [ID xxxxxx daemon.alert] syslog Nov 10 14:00:10 trap syntax error in trap-schedule.dat(200) at token '???'
    followed immediately (same timestamp) with:
    [ID yyyyyy daemon.alert] syslog Nov 10 14:00:10 trap *** aborting execution ***
    I coudn't find anything on the web specifically for this message but several hits that looked similar seemed to indicate that this might be a problem in SMC. If it is not I apologize in advance.
    System is an ldom:
    Solaris 10;
    SunOS clsol8 5.10 Generic_127127-11 sun4v sparc SUNW,T5140
    Current situation is:
    # /opt/SUNWsymon/sbin/es-validate
    This script will help you in validation of Sun (TM) Management Center.
    Validation Tool Version : 4.0
    Host name : clsol8
    Number of CPUs : 24
    Platform : SUNW,T5140
    Operating System : SunOS 5.10
    Memory size : 2048 Megabytes
    Swap space : 595480k used, 3727296k available
    JAVA VERSION : "1.5.0_14"
    Sun Management Center Production Environment Installation.
    Following layers are installed : SERVER, AGENT, CONSOLE
    Installation location : /opt/SUNWsymon
    Sun Management Center installation status:
    PRODUCT : Production Environment
    INSTALLATION STATUS : Setup.
    DATABASE SETUP : Setup.
    COMPLETELY INSTALLED PACKAGES : SUNWescom,SUNWesbui,SUNWesbuh,SUNWenesi,
    : SUNWesdb,SUNWesagt,SUNWessrv,SUNWessa,
    : SUNWesjp,SUNWesaxp,SUNWesse,SUNWesclt,
    : SUNWesjrm,SUNWmeta,SUNWenesf,SUNWesmdr,
    : SUNWesgui,SUNWesweb,SUNWessvc,SUNWesasc,
    : SUNWescix,SUNWsuagt,SUNWsusrv,SUNWesval,
    : SUNWesmc,SUNWessms,SUNWessdv,SUNWescdv,
    : SUNWlgsmc,SUNWeslac,SUNWesodbc,SUNWesmib,
    : SUNWesken,SUNWesmod,SUNWesae,SUNWesaem,
    : SUNWesmcp,SUNWesafm,SUNWescon,SUNWsucon,
    : SUNWescli,SUNWesclb
    <NOTE: I had to cut out a bunch of installed components to hit character limit>
    Sun Management Center Add-Ons and Versions:
    PRODUCT VERSION
    Production Environment 4.0
    Advanced System Monitoring 4.0_Build15
    Sun Fire Entry-Level Midrange S 3.5-v6
    Service Availability Manager 4.0_Build15
    Performance Reporting Manager 4.0_Build15
    Solaris Container Manager 4.0_Build15
    Sun Fire Midrange Systems Platf 3.5-v6
    System Reliability Manager 4.0_Build15
    Sun Management Center Integrati 4.0_Build15
    Workgroup Server 3.6
    Generic X86/X64 Config Reader 4.0_Build15
    Sun Management Center Patch installation details:
    No Sun Management Center patch is installed.
    Sun Management Center disk-space consumption:
    PRODUCT APPROXIMATE DISK SPACE CONSUMED
    Production Environment : 54452 kB
    Advanced System Monitoring : 2391 kB
    Sun Fire Entry-Level Midrange S : 1738 kB
    Service Availability Manager : 1838 kB
    Performance Reporting Manager : 3371 kB
    Solaris Container Manager : 3688 kB
    Sun Fire Midrange Systems Platf : 3270 kB
    System Reliability Manager : 970 kB
    Sun Management Center Integrati : 540 kB
    Workgroup Server : 3707 kB
    Generic X86/X64 Config Reader : 608 kB
    TOTAL : 76573 kB
    Database is located at : /var/opt/SUNWsymon/db/data/SunMC
    Free space available on this partition is : 6493142 kB
    Following locales are installed :
    Information about upgrade from old versions is not available.
    Sun Management Center Ports:
    SUNMC COMPONENT PORT_ID
    agent service 1161
    trap service 162
    event service 163
    topology service 164
    cfgserver service 165
    cstservice service 167
    metadata service 168
    platform service 166
    grouping service 5600
    rmi service 2099
    webserver_HTTP service 8080
    webserver_HTTPS service 8443
    You are currently running SNMPDX.
    Sun Management Center Server Hosts definitions in domain-config.x:
    SUNMC COMPONENT SERVER_HOST
    agent service clsol8
    trap service clsol8
    event service clsol8
    topology service clsol8
    cfgserver service clsol8
    cstservice service clsol8
    metadata service clsol8
    platform service clsol8
    Sun Management Center Processes:
    SUNMC SERVICE STATUS
    Java Server Running.
    Database services Not Running.
    Grouping service Running.
    Event-handler service Running.
    Topology service Not Running.
    Trap-handler service Not Running.
    Configuration service Running.
    CST service Not Running.
    Metadata Services Running.
    Hardware service Not Running.
    Web server Running.
    Sun Management Center Agent Running.
    Platform Agent Not Running.
    Privilege level for Sun Management Center users :
    CATEGORY USERS
    esadm : smcadmin
    esdomadm : smcadmin
    esops :
    ALL USERS : smcadmin
    server is local host
    Web server package is installed correctly.
    Web Server is up and responding.
    Web Server servlet engine is up and responding.
    I have also read that patching SMC has caused problems for some people so I don't really want to try that until I get some feedback.

    Hi Mike,
    Tried your suggestion to rename the .dat and let SMC recreate it but I can't get the SMC database service to launch. So it looks like I am having trouble with the database. Any suggestions?
    To back up, you nailed it with the loss of power - we lost both power supplies on a Sunday night with no warning and nothing in /var/adm/messages (since we send them to a loghost.) It was determined that chips within each power supply in the T5140 failed. So we replaced both power supplies and fired the server up. That is when we started getting the trap errors and only those two errors on clsol8.
    I did check http://sun.com/msg/SMF-8000-KS but am not sure how that helps.
    What I tried:
    On clsol8 as root:
    # cd /opt/SUNWsymon/sbin
    # ls
    {db-memconfig.sh   es-details        es-imagetool      es-setup
    db-start          es-device         es-inst           es-start
    db-stop           es-dt             es-keys.sh        es-stop
    es-apps           es-gui-imagetool  es-lic            es-tool
    es-backup         es-guiinst        es-load-default   es-trapdest
    es-chelp          es-guisetup       es-makeagent      es-uninst
    es-cli            es-guistart       es-platform       es-validate
    es-common.sh      es-guistop        es-restore        esmultiip
    es-config         es-guiuninst      es-run            ports.config}
    # ./es-stop -A
    {Stopping metadata component
    Stopping cfgserver component
    Stopping topology component
    Stopping event component
    Stopping grouping service
    Stopping trap component
    Stopping java server
    Stopping webserver
    Stopping agent component
    Stopping platform component}
    <attempting Mike's solution suggestion>
    # cd /var/opt/SUNWsymon/cfg
    # ls
    trap-schedule.dat
    # mv trap-schedule.dat trap-schedule.dat.maybeCorrupted
    # /opt/SUNWsymon/sbin/es-start -Ac
    {Some of the SunMC services are in maintenace state.
    Please check the corresponding SMF service log in /var/svc/log directory.
    Please disable the services in maintenance state and re-start the services again.}
    # svcs -vx
    svc:/application/management/sunmcdatabase:default (SunMC database service)
    State: maintenance since November 6, 2009 3:50:51 PM CST
    Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
    See: http://sun.com/msg/SMF-8000-KS
    See: /var/svc/log/application-management-sunmcdatabase:default.log
    Impact: This service is not running.
    svc:/application/management/sunmcwebserver:default (SunMC webserver service)
    State: maintenance since November 12, 2009 2:45:50 PM CST
    Reason: Start method failed repeatedly, last exited with status 103.
    See: http://sun.com/msg/SMF-8000-KS
    See: /var/svc/log/application-management-sunmcwebserver:default.log
    Impact: This service is not running.}
    # svcadm disable sunmcdatabase
    # svcadm disable sunmcwebserver
    # svcs -vx
    # svcadm enable sunmcdatabase
    # svcadm enable sunmcwebserver
    # /opt/SUNWsymon/sbin/es-start -Ac
    {Failed to successfully perform Database Startup.}
    # svcs -vx
    svc:/application/management/sunmcdatabase:default (SunMC database service)
    State: maintenance since November 12, 2009 2:49:50 PM CST
    Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
    See: http://sun.com/msg/SMF-8000-KS
    See: /var/svc/log/application-management-sunmcdatabase:default.log
    Impact: This service is not running.}
    # cd /
    # svcadm disable sunmcdatabase
    # shutdown -y -g0 -i6
    (after reboot, I logged into clsol8 and su'd to root)
    # svcs -xv
    svc:/application/management/sunmcdatabase:default (SunMC database service)
    State: disabled since November 12, 2009 3:02:11 PM CST
    Reason: Disabled by an administrator.
    See: http://sun.com/msg/SMF-8000-05
    Impact: 1 dependent service is not running:
    svc:/application/management/sunmctopology:default}
    # svcadm enable sunmcdatabase
    # svcadm disable sunmcdatabase
    # svcadm clear sunmcdatabase
    svcadm: Instance "svc:/application/management/sunmcdatabase:default" is not in a maintenance or degraded state.
    # svcadm refresh sunmcdatabase
    # svcadm enable sunmcdatabase
    # svcs -xv
    svc:/application/management/sunmcdatabase:default (SunMC database service)
    State: offline since November 12, 2009 3:09:25 PM CST
    Reason: Start method is running.
    See: http://sun.com/msg/SMF-8000-C4
    See: /var/svc/log/application-management-sunmcdatabase:default.log
    Impact: 1 dependent service is not running:
    svc:/application/management/sunmctopology:default
    # svcs -xv
    svc:/application/management/sunmcdatabase:default (SunMC database service)
    State: maintenance since November 12, 2009 3:10:30 PM CST
    Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
    See: http://sun.com/msg/SMF-8000-KS
    See: /var/svc/log/application-management-sunmcdatabase:default.log
    Impact: 1 dependent service is not running:
    svc:/application/management/sunmctopology:default
    [ Nov 12 15:08:37 Leaving maintenance because disable requested. ]
    [ Nov 12 15:08:37 Disabled. ]
    [ Nov 12 15:09:07 Rereading configuration. ]
    [ Nov 12 15:09:25 Enabled. ]
    [ Nov 12 15:09:25 Executing start method ("/lib/svc/method/es-svc.sh start datab
    ase") ]
    execution of verifyDatabaseUp failed
    exiting........................
    [ Nov 12 15:10:30 Method "start" exited with status 95 ]

  • Delivery schedule dates are coming in Past dates

    Hi Friends,
    In the Scheduling Agreements the delivery schedule dates are coming in the past dates even tough the scheduling agreements are having new schedules. There is also open quantities there for the scheduling agreements.
    please kindly explain me what is the delivery schedule date in Scheduling Agreement.
    Thanks in advance.
    Regards,
    Kannan M

    Hi Khan,
    Just check this thease might be the reasons to get correct the delivery schedule.
    To access a delivery schedule, mark a scheduling agreement item and choose Goto ® Item ® .
    The following data is displayed in the delivery schedule tabstrip:
    ·        Delivery schedule number and date
    ·        A wide range of standard cumulative quantities
    ·        Delivery information
    To display deliveries for the delivery schedule, choose Deliveries on the delivery schedule tabstrip.
    In scheduling agreements involving external agents, the system displays deliveries made to the customer by external agents as consignment issues.
    ·        Correction delivery information
    To display or create correction deliveries, choose Corr. delivery on the delivery schedule tabstrip.
    ·        An analysis function
    ·        Information at a glance
    To display a summary of delivery schedule data, choose Short disp. on the delivery schedule tabstrip.
    ·        Schedule lines
    Choose DlvSch.Hdr on the delivery schedule tabstrip to access the delivery schedule header. The following data is displayed here:
    ·        Information on quantities received by the customer
    ·        Information on the customer fiscal year and cumulative quantities reset due to a year change
    ·        A wide range of cumulative go-ahead quantities
    ·        Notes on the delivery schedule
    Correcting Cumulative Delivered Quantities
    Prerequisites
    You correct cumulative quantities in scheduling agreements:
    ·        In case of returns
    ·        When there has been a processing error
    ·        When there has been a year change
    ·        When you are transferring initial quantities from a legacy system into the SAP System
    To do this, you create a correction delivery within the delivery schedule itself. This delivery is not relevant for requirements planning, shipping, goods issue, or billing.
    Correct cumulative quantities only when the customer has not posted goods receipt.
    Procedure
    To create a correction delivery (document type LFKO):
           1.      Choose Corr. delivery on the delivery scheduletabstrip.
    The system displays a dialog box in which you enter a:
    -         Correction delivery date
    For help on deciding where you want to position the correction delivery, choose Display. The system lists delivery dates in chronological order.
    -         Correction quantity
    Enter a negative correction quantity by placing a minus sign after the quantity.
           2.      Choose Enter and save the scheduling agreement.
    Result
    When you save the correction delivery, the system updates the cumulative quantities in the delivery schedule.
    To display correction deliveries, choose Deliveries on the delivery schedule tabstrip, or  Environment ®  Display document flow.
    Example
    Your customer returns 200 pieces of material from a delivery made on 7/10 because of damage during transport. Several other deliveries have been made before you prepare the correction delivery, so you view a list and choose an appropriate date. In this case you decide on 7/14 because it occurs after the delivery on 7/10 and before the delivery on 7/15.
    Regards,
    Murthy V.N

  • Sales order item data & sales order schedule data

    Hello,
    I have a Sales Orders cube which is pulling data from two DSOs (one for sales order item data and the other for sales order schedule data). The common fields between these two DSOs is the Sales Order number but in my cube I have dual entries for each Sales Order document (item and schedule info).
    Example of how the data looks now:
    Sales Order . . Item Cat. . . Article . . . Net Price . . . Delivery . . . Act GI Date
    1. . . . . . . . . ...TAN. . . . . ABC123. . . .10
    1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 . . . . . . . . 01/01/2000
    2. . . . . . . . . ...TAN. . . . . CBA321. . . .15
    2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 . . . . . . . . 01/02/2000
    How do I merge the data on the Sales Order number in the cube so it looks like below?
    Sales Order . . Item Cat. . . Article . . . Net Price . . . Delivery . . . Act GI Date
    1. . . . . . . . . ...TAN. . . . . ABC123. . . .10 . . . . . . . . . .1 . . . . . . . . 01/01/2000
    2. . . . . . . . . ...TAN. . . . . CBA321. . . .15 . . . . . . . . . .2 . . . . . . . . 01/02/2000
    Many thanks,
    Matt

    > Hello,
    >
    > I have a Sales Orders cube which is pulling data from
    > two DSOs (one for sales order item data and the other
    > for sales order schedule data). The common fields
    > between these two DSOs is the Sales Order number but
    > in my cube I have dual entries for each Sales Order
    > document (item and schedule info).
    >
    Two previous remarks:
    1) If you need to report on very detailed data consider doing an info-set joining both datastores. 2 reasons why:
    - not a good idea to report on very detailed information (sales order, GI dates) on cube level, if you have a scenario with lots of data. You end up with big dimension tables a poor report times;
    - there are better alternatives, like drill-through from cube query to DS query with report to report interface or Datastore-based reporting...so...
    With this solution you do not need to change the data model, I think, but test to be sure. See if the reporting times are acceptable. If not...
    2) First confirm your requirements, because what you show in your example as "to-be" have details that do not make sense, probably..
    - if you have more that one schedule line for each item then you would have many times the item information like material/price;
    - if not or if you could cope with that, then you can consider:
    2.1) create a new DS that agregattes from the previous on, with the same key of sales order item; do you have schedule line kf's? if so you these KF's should be additive in DS update; But if you may have more one scheduled line for 1 item then you have to decide what to do with the GI data (keep the last one posted, use code..) and other characteristics.
    2.2) update the shedule line datasource to the sales order item DS; same comments apply.
    2.3) maintain the missing data in the cube update rules from sheduled lines DS. Using code, refer to the respective item in the order item ODS. You would have to make sure that DS's data are correctly activated before updating the infocube.
    What solutions to choose?
    2.1 is better in terms of flexibility and architecture...because you could re-arrange the new DS to answer future needs, without loosing the 1st line DS's data;
    2.2 choose if data volumes and disk space are a concern...
    or
    2.3 it's OK, but i do not like it because of what explained in point 1...
    Message was edited by:
            Miguel Costa

  • Sales order schedule dates

    Hai,
         I have created a sales order, whenever we created a SO it displays possible delivery dates, we enter that possible delivery date in delivery creation, I want to know where those schedule dates are getting stored when we save a sales order. I have seen for those in VBAK and VBAP tables but i havent found those schedule lines can anybody say where these dates are getting saved
                                                                                    Thank you in advance
                                                        Srinivas

    When the order quantity is available as on the delivery date and confirmed then there will be only one schedule line created. If stock is not available then as delivery date the confirmed quantity will be 0 and another schedule line will be created as on material availability date where the order quantity will be confirmed.
    Its not necessary that there are only one or two schedule lines...but there can be more than two also.
    Regards,
    GSL.

  • Sales order schedule date is a (working) day before Scheduled ship date

    In MRP/MPS planning, the forecast consumption is occuring for all sales orders at a date (sales order schedule date) which is always a working day before the Scheduled Ship Date (SSD). What is the logic?
    Time fences are not used.
    E.g. Sales order is scheduled to ship (SSD) on 30th Nov, in forecast set > Forecast items > Consumptiion > Detail, the sales order schedule date is a day before SSD.

    Hi,
    This is a complex issue; best solution is by using APO/GATP.
    If not, then in ERP only, the second best is:
    1) Work with assembly processing in SO, meaning that a production/planned order is automatically created in the customer order during order creation.
    2) Then, after the order is created it is scheduled, and the delivery date proposal is based on that.
    3) Now you can check in the order that there are no capacity overloads, and all capacity required to produce on the proposed date is available. If yes, you're done. If not, it gets a bit complex, since you actualy need to switch to capacity planning, do capacity leveling and dispatch (PP), and the you get a new feasible schedule proposal based on that.
    APO/GATP could do all that automatically!
    Regards,
    Mario

  • Basic date is not same with schedule dates

    Hi,
    I have a problem in MD04 stock requirement list.
    Planned order basic date and schedule date is not the same.
    The schedule date finish at year 2010 but basic date still end ad 2009
    in MD04, the date display is basic date.
    Why the basic date is not adjusted?
    in configuration i had choosen adjust basic date in scheduling planned order.
    In material master in house production time is not updated because we use lead time scheduling
    Please kindly help
    Best regards,
    Freddy Ha

    Hi,
    i omit the scheduling maergin key in material master,
    the result of MRP is
    BASIC DATES
    Finish 15.10.2009
    Start 14.10.2009
    PRODUCTION DATES
    15.02.2010 14:33:25
    14.10.2009 07:00:00
    scheduling type i planned order is still "backwards"
    so in MD04 it is say that the goods is available at 15.10.2009 same with requirement dates.
    this seem not right.
    it seems that order finish date is not adjusted by lead time scheduling on "today scheduling".
    Is there a way so order finish date is adjusted by lead time scheduling on "today scheduling" ????
    Best regards,
    Freddy Ha
    Edited by: Freddy Halim on Oct 14, 2009 10:01 AM

  • Error while scheduling data in QA

    Hi Experts,
                I am having this problem while Scheduling data in QA. I tried activating Infosource in se38 with program rs_transtru_activate_all but still i am getting the below error, can anyone let me know why is this happening....
    Diagnosis
    DataSource ZFAB_BILLINGCALC does not have the same status as the source
    system in the Business Information Warehouse.
    The time stamp in the source system is 10/06/2006 09:33:40 .
    The time stamp in the BW system is 08/09/2006 15:52:25 .
    System response
    The load process has been terminated.
    Procedure
    Copy the DataSource again and then activate the transfer rules that
    belong to it. You have to activate the transfer rules in every case,
    even if they are still active after the DataSource has been copied.

    Kris,
    I also got the similar error (time stamp)
    Try this.
    Replicate data source
    Activate transfer structure in source system. For this
    you navigate from source system tab---> your data source --> context menu --> display data source in source and then come back. It will activate the transfer structure in source. ( I dont know exact procedure but this worked for me many times)
    I  think this is sufficient.
    If this not works include this step also Use the program for activating transfer structure in BW.
    Hope this helps.
    Vijay

  • Scheduling Date issue in Assemble to Order Scenario

    Hi Friends,
    I am facing a Weird issue with Production order Scheduled dates created automatically after creation of Sales Order for configurable material.
    Our availability check is set to check  open Purchase orders, for one component the delivery date in the PO is 20.12.2011, currently at the time of creation of SO the availability check shows this component as a missing part and committed date as 20.12.2011.
    Now the issue is that for one type of customers when the SO is saved, the production order gets created with basic start and finish date of 20.12.2011 with a status CRTD PRC MACM SETC.
    But with another customer group it creates the Production order with today's date basic start and finish date, with a status CRTD MSPT PRC  SETC.
    Now since in both the cases the Material is same and also the components are exactly the same, the only difference is the customer, I am unable to make out why it is happening.
    I am basically a MM  Consultant so am unaware if there is any standard setting relating to customer or something relating to that which is causing such  a issue in scheduling date of the Production Order.
    Regards
    Chandra Shekhar

    Hi Vivek,
    Yes, the availability check is working in both the cases, when I create the sales order, I key in the Configurable material code, then do the configuration, after that system does availability check, in both the cases the result of availability check is same with one component marked as a missing part, available date as 20.12.2011.
    One more thing if I try to view the Production order at the time of SO creation before saving it, the Production order shows today's date, but when I save the SO, and do Credit release, the actual Production order gives different scheduling date based on customer. Just wondering what could be affecting based on Customer, is there any other field present in Customer master which could alter the date.
    I also saw today's scheduling note in some of the cases, but its not coming up in all of the orders created with today's date and moreover the same components are getting scheduled for 20.12.2011 also for diff customer.
    I am afraid I can't provide any screenshots for this as am not permitted to publish any screenshots of the client.
    Regards
    Chandra Shekhar

  • Calculation of basic dates and schedule dates

    I update material master from routing with CA97 to material master
    work scheduling data with base quantity 1000
    When MRP running, planned order for 54000 PCS is schedule with work scheduling data.
    when i schedule planned order (change)
    the calculation basic date & schedule date differs for 19 days
    cause basic start shift
    why is this happend?
    is this cause by rounding when transforming minute from routing to days in material master?
    is this because i used shift sequence and scheduling with breaks?
    some strage case again is
    for base qty 1000 processing time is 0.97
    for base qty 10000 processing time is 6.93
    is there any solution for this case?
    please help.
    Best regards,
    Freddy Ha

    i forgot i used overlapping
    sorry

Maybe you are looking for