Set background job - create dn automatically

hi
Pls advice how to set background job to create DN automatically
thanks

How you are saying that no Deliveries were created ?
First of all make sure that they are sales orders due for delivery data on the day you are creating.
-> Run VF04 in foreground with the variant that you used in Background and check whether there is any orders due for delivery or not?
Make sure you have proper data.
Hope you should get it.
Regards,
Ajai.

Similar Messages

  • How to set a job to import automatically transport requests

    I wander how to set a job to import automatically transport requests

    Hi jan Bo,
    http://help.sap.com/saphelp_erp2004/helpdata/EN/44/b4a3c57acc11d1899e0000e829fbbd/frameset.htm
    Usung above link you can schedule a transport, if you schedule this job a back ground job will be defined copy this job and create a new varient with your transport request. Make this job run after the back ground job you want.
    Regards,
    S.Manu.

  • Background job- getting printed automatically

    In my BDC Program i have submitted  Session for Background Processing using
    Submit RSBDCSUB..........
    my code is also given below..The problem is after the user executes the program, background job is automatically going to his Local printer and getting printed. HOw to avoid this?
    CALL FUNCTION 'JOB_OPEN'
           EXPORTING
                jobname          = gf_jobname
           IMPORTING
                jobcount         = gf_jobcount
           EXCEPTIONS
                cant_create_job  = 1
                invalid_job_data = 2
                jobname_missing  = 3
                OTHERS           = 4.
    *-Submit the selected sales orders for changes.
      SUBMIT rsbdcsub AND RETURN
             WITH mappe = v_sess
             WITH von = sy-datum
             WITH bis = sy-datum
             WITH z_verarb = 'X'
             WITH fehler = space
             WITH batchsys = space
             WITH logall = space
             USER sy-uname VIA JOB gf_jobname NUMBER gf_jobcount.
      IF sy-subrc NE 0.
        MESSAGE i999 WITH text-013.
        EXIT.
      ENDIF.
    *-Close job and start immediately.
      CALL FUNCTION 'JOB_CLOSE'
           EXPORTING
                jobcount             = gf_jobcount
                jobname              = gf_jobname
                strtimmed            = 'X'
           IMPORTING
                job_was_released     = gf_release
           EXCEPTIONS
                cant_start_immediate = 1
                invalid_startdate    = 2
                jobname_missing      = 3
                job_close_failed     = 4
                job_nosteps          = 5
                job_notex            = 6
                lock_failed          = 7
                OTHERS               = 8.

    On SUBMIT use
    SUBMIT zxxxxxx TO SAP-SPOOL
                        WITHOUT SPOOL DYNPRO
                        IMMEDIATELY  ' '
                        KEEP IN SPOOL 'X'
                        DESTINATION printer
                         NUMBER  number
                        AND RETURN

  • A background job creating/instantiating another background job

    Hi,
    Is there any possibility in SAP, that, a background job can create/instantiate another background job ?
    I have one suce requirement, and not sure if this is possible. Any inputs..
    -DK

    yes you can
    when you create a job using SM36,there is a option for start condition
    in that there is an option for After Job
    just give the job name and when that job completes,this job will trigger off
    http://help.sap.com/saphelp_nw04/helpdata/EN/c4/3a7fae505211d189550000e829fbbd/frameset.htm
    Rohit

  • Setting Background job for BDC

    Dear Frds,
             I created upload program(i.e through call transcation) for Material Master.I  sheduled background job through SM36/SM37 .But it is giving error as "code page error"
                if any body has idea on this topic.please send me the details.

    have you used any GUI_UPLOAD or WS_UPLOAD or UPLOAD function modules ?
    I mean how your uploading legacy data to the internal table? if you used uploading from presentation server,then you can NOT use the program to run in background. either you have to place the file on application server or use the program in foreground mode.
    Regards
    Srikanth

  • Automatic Mail not getting generated through background job

    Hi Experts,
    We have set up a job variant with spool recipients. We are getting the automatic mail if the job is getting finished successfully. But we are not getting the automatic mail if the job is in cancelled status. Earlier we used to get the mail even if the job is in cancelled status. We are not sure if there is any setting which would restrict the automatic mail based on the job status.
    Appreciate your help in this regard.
    Thanks and Regards,
    Ranjani.

    Hi,
    Just for a work around, try checking the SAP user inbox for the user who has scheduled the background job.
    I don't there  is any seperate configuration in Spool List Recipient for the canceled jobs. We need to confirm that the email ids provided in the Spool List recipient are correct and the background job creates a spool request even if it is canceled.
    Also if possible try deleting the existing background job and create a new background job with the same parameters and valid email id's maintained in the Spool List recipient.
    OR
    Without deleting the existing background job, parallely create a new background job with the same parameters and valid email id's maintained in the Spool List recipient. If it works then delete the old background job.
    Thanks
    Harish

  • SAP  Back ground Jobs getting cancel automatically

    Hi All,
    All schedule Background jobs getting cancel  automatically in ECC 5 server. Also not getting any job log in respective schedule job. please help me out with expert suggestions.
    Regards
    Gyan

    1)Are the bgd workprocess free in the system currently?Check if there are any long running jobs holding them.
    Bgd Work process are free but with error code 373,223,007 etc for all 5 bg wp
    error reports from work directory as per work process:---
    wp 22 :Fri Sep 25 15:07:04 2009
    A 
    A  ABAP/4 Program SAPLSYDB                                .
    A  Source LSYDBU27                                 Line 7.
    A  Error Code DBIF_DSQL2_DEFAULT_CR_ERROR.
    A  Module  $Id: //bas/640_REL/src/krn/runt/abexsql.c#5 $ SAP.
    A  Function DsqlErrorHandler Line 1986.
    A  COMMIT/ROLLBACK error on "DEFAULT" database connection..
    A 
    M  ***LOG R68=> ThIRollBack, roll back () [thxxhead.c   12289]
    C  Rollback Work (0)
    M  *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c  252]
    B  ComRolHook(BEFORE_COMMIT, free_all) failed
    B  db_con_commit received an error return code in before-commit action
    M  ***LOG R38=> ThICommit3, db_commit98 ( 001024) [thxxhead.c   12036]
    WP23: Fri Sep 25 15:06:05 2009
    B  dbtran INFO (init_connection '<DEFAULT>' [MSSQL:640.00]):
    B   max_blocking_factor =  50,  max_in_blocking_factor      = 255,
    B   min_blocking_factor =   5,  min_in_blocking_factor      =  10,
    B   prefer_union_all    =   1,  prefer_union_for_select_all =   0,
    B   prefer_fix_blocking =   0,  prefer_in_itab_opt          =   0,
    B   convert AVG         =   1,  alias table FUPD            =   0,
    B   escape_as_literal   =   0,  opt GE LE to BETWEEN        =   0,
    B   select *            =0x00,  character encoding          = STD / []:X,
    B   use_hints           = abap->1, dbif->0x1, upto->0, rule_in->0,
    B                         rule_fae->0, concat_fae->0, concat_fae_or->0
    M  ***LOG R68=> ThIRollBack, roll back () [thxxhead.c   12289]
    C  Rollback Work (0)
    M  *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c  252]
    B  ComRolHook(BEFORE_COMMIT, free_all) failed
    B  db_con_commit received an error return code in before-commit action
    M  ***LOG R38=> ThICommit3, db_commit98 ( 001024) [thxxhead.c   12036]
    wp 24:Fri Sep 25 14:33:10 2009
    M  *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c  252]
    B  ComRolHook(BEFORE_COMMIT, free_all) failed
    B  db_con_commit received an error return code in before-commit action
    B  ***LOG BZY=> unexpected return code 32768      calling DBACDS     [dbacds#2 @ 1225] [dbacds  1225 ]
    B 
    *WP25: *** ERROR => BtcCleanUp: BtcLgAp-call failed (rc = 4) [btcjcntl.c   1308]*
    M  ThCallHooks: call hook >ITSP: EndOfSession< for event BEFORE_SESSION_CANCEL
    M  ThCallHooks: call hook >RtmClearSession< for event BEFORE_SESSION_CANCEL
    M  ThCallHooks: call hook >HttpClearSession< for event BEFORE_SESSION_CANCEL
    M  ThCallHooks: call hook >SpoolHandleHook< for event BEFORE_SESSION_CANCEL
    M  ***LOG R47=> ThResFree, delete (001009) [thxxmode.c   1284]
    M  ThCallHooks: call hook >ASTAT-collect commit handling< for event BEFORE_COMMIT
    M  ThCallHooks: call hook >rsts_before_commit< for event BEFORE_COMMIT
    M  ThCallHooks: call hook >rsts_after_commit< for event AFTER_COMMIT
    M  ThCallHooks: call hook >ThNoClearPrevErr< for event AFTER_COMMIT
    M  ThCallHooks: call hook >SpoolHandleHook< for event AFTER_COMMIT
    M  ThCallHooks: call hook >SAP-Trace buffer write< for event BEFORE_TASK_SWITCH
    M  ThCallHooks: call hook >ImcResetPtr< for event BEFORE_TASK_SWITCH
    M  ThCallHooks: call hook >DbgBeforeTaskSwitch< for event BEFORE_TASK_SWITCH
    M  ThCallHooks: call hook >HttpResetPtr< for event BEFORE_TASK_SWITCH
    B 
    B Fri Sep 25 14:47:04 2009
    B  Disconnected from connection con_da={R/3*WORKFLOWTRACE,26000006,1}
    please let me know where i can send log file if req.
    2)Check for the sm21/sm50 bgd wp traces.
    Getting so may Tem se management errors.
    Some TemSe objects are stored in files. To do this, a path name is set up from the TemSe object name. To be able to use this path, TemSe management requires a directory. It attempted to create it itself. However, this did not succeed.
    3)Check if the filesystem is full as you suggest no logs are being written.
    File system having free space
    4)Check if the user who has scheduled the job is locked ?
    user unlocked
    please help me to resolv this issue.
    thanks
    Gyan
    Edited by: Gyan Prakash on Oct 9, 2009 10:02 AM

  • Triggering a background job of class 'A' from within the ABAP program

    Dear All,
    We are implementing SAP ECC 6.0 on IBM System i, i5/OS V5R4,  SAP kernel 7.00, kernel patch level 173.
    Is there a way to control that when a background job is triggered from within an ABAP program using the : CALL FUNCTION 'JOB_OPEN' statement, the background job is of class A ?
    I know that through transaction SM37, the job class for a background job can be changed manually, but the situation is an outsource company did for us some changes in the native SAP ABAP programs related to some SAP native transactions, and those programs trigger at their end some background jobs, each job running with the name of user running the transaction.
    Through SM37, I can't find a template background job, to be changed to have class 'A'
    The following is an excerpt from the ABAP code, bearing the CALL FUNCTION 'JOB_OPEN' statement :
    FUNCTION z_cs_technical_completion.
    ""Local Interface:
    *"  IMPORTING
    *"     VALUE(AUFNR) TYPE  VBRP-AUFNR
      DATA jobcount TYPE tbtcjob-jobcount.
      CALL FUNCTION 'JOB_OPEN'
        EXPORTING
          jobname                = 'CS_TECH_COMPLETE'
      SDLSTRTDT              = NO_DATE
      SDLSTRTTM              = NO_TIME
      JOBCLASS               =
       IMPORTING
         jobcount               = jobcount
    CHANGING
      RET                    =
       EXCEPTIONS
         cant_create_job        = 1
         invalid_job_data       = 2
         jobname_missing        = 3
         OTHERS                 = 4
      SUBMIT zcs_technical_completion
              WITH p_aufnr EQ aufnr
                AND RETURN
              VIA JOB 'CS_TECH_COMPLETE'
              NUMBER jobcount.
      CALL FUNCTION 'JOB_CLOSE'
        EXPORTING
          jobcount             = jobcount
          jobname              = 'CS_TECH_COMPLETE'
          strtimmed            = 'X'
        EXCEPTIONS
          cant_start_immediate = 1
          invalid_startdate    = 2
          jobname_missing      = 3
          job_close_failed     = 4
          job_nosteps          = 5
          job_notex            = 6
          lock_failed          = 7
          invalid_target       = 8
          OTHERS               = 9.
    ENDFUNCTION.
    Thank you in advance for your cooperation.
    Best regards.
    Reda Khalifa

    Dear Darren,
    Thank you very much for your cooperation and for your prompt reply.
    Could you please explain to me how to find out the template background job that was first used, or in other words, how things were set up in the first place, i.e. when first the ABAP program was written and executed, there had to be at least one background job created through transaction SM36 ?
    Thank you in advance for your cooperation.
    Best regards.
    Reda Khalifa

  • Sending output to a printer in a background job

    I did a quick search on this issue and found a few suggestions.  One suggestion was to use something like this:
    SUBMIT RSFLFIND ... TO SAP-SPOOL DESTINATION 'LT50'.
    I looked at the SAP help for SUBMIT and it was quite helpful however it raised a few questions.  The program that am writing will be run in the background.  I want to create a simple report that will print at several different printers when it is done.  Looking at the help section (specifically this part):
    "The SUBMIT statement accesses an executable program rep. The executable program is executed as described under Calling Executable Reports.
    The program name rep can either be specified directly or as the content of a character-like data object name. The data object name must contain the name of the program to be accessed in block capitals. If the program specified in name is not found, an irretrievable exception is generated.
    The selscreen_options additions can be used to determine the selection screen for the program accessed and to supply it with values.
    The list_options additions allow you to influence the output medium and the page size in the basic list for the program accessed.
    You can schedule the program for background processing by specifying job_options. "
    It seems like I would create a simple program like this:
    DATA: number TYPE tbtcjob-jobcount,
          name TYPE tbtcjob-jobname VALUE 'JOB_TEST',
          print_parameters TYPE pri_params.
    CALL FUNCTION 'JOB_OPEN'
      EXPORTING
        jobname          = name
      IMPORTING
        jobcount         = number
      EXCEPTIONS
        cant_create_job  = 1
        invalid_job_data = 2
        jobname_missing  = 3
        OTHERS           = 4.
    IF sy-subrc = 0.
      SUBMIT submitable TO SAP-SPOOL
                        SPOOL DESTINATION 'LT50'.
                        VIA JOB name NUMBER number
                        AND RETURN.
      IF sy-subrc = 0.
        CALL FUNCTION 'JOB_CLOSE'
          EXPORTING
            jobcount             = number
            jobname              = name
            strtimmed            = 'X'
          EXCEPTIONS
            cant_start_immediate = 1
            invalid_startdate    = 2
            jobname_missing      = 3
            job_close_failed     = 4
            job_nosteps          = 5
            job_notex            = 6
            lock_failed          = 7
            OTHERS               = 8.
        IF sy-subrc <> 0.
        ENDIF.
      ENDIF.
    ENDIF.
    That will then call the background job and the output will go to the print spool.  I have a few reservations about this.  The print spool will not be determined until the background job.  The background job creates sales orders and the material group, in the sales order, determines the printer that the final report will go to.  Also, if this is the way to do it, do I just do simple write statements in the background job?

    Hi,
    Please try this ... perhaps it may help.
    SUBMIT submitable TO SAP-SPOOL
                      SPOOL DESTINATION 'LT50'.
                      IMMEDIATELY 'X'           "Add here
                      VIA JOB name NUMBER number
                      AND RETURN.
    OR
    SUBMIT submitable TO SAP-SPOOL
                      SPOOL DESTINATION 'LT50'.
                      IMMEDIATELY 'X'           "Add here
                      WITHOUT SPOOL DYNPRO      "Add here
                      VIA JOB name NUMBER number
                      AND RETURN.
    Regards,
    Ferry Lianto

  • Pass lock to background job

    Hi,
    I'm looking for ideas.
    We have an inbound process for special messages transfered from XI system via asynchrounous call. Messages are identified by a GUID.
    The inbound process will save the messages in a database table and create background jobs for processing big messages while small messages are processed directly.
    To avoid any interference, we want to lock messages as long as they are processed. For this we have a lock object and the Enqueue/dequeue modules.
    Now my question is: How can I pass a lock to the background job (created by SUBMIT VIA JOB) and have it released there after processing is done. The Job will run in a new LUW.
    And then, if any error in background (or online) processing occurs, how to make sure all existing locks are released?
    Thanks for some good ideas on how to proceed.
    Regards,
    Clemens

    resolved - we won't do it. We'll create some kind of queue: A fully-buffered database table where we put the lock entries and remoce them when it's time to do so. This way we can integrate an activity monitor watching the objects being processed.
    Thanks for reading
    Clemens

  • How we can done background job in web dynpro abap

    Hi expert,
    my requriment is how i can set background job in web dynpro .
    regard's
    vikash

    The same way you do it in normal ABAP. There is nothing Web Dynpro ABAP specific about starting a background job.
    There are API Function modules that begin with the name JOB_*.  Have a look at the online help for samples:
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/fa/096d40543b11d1898e0000e8322d00/frameset.htm
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/fa/096d4d543b11d1898e0000e8322d00/frameset.htm
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/fa/096d67543b11d1898e0000e8322d00/frameset.htm
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/fa/096d74543b11d1898e0000e8322d00/frameset.htm
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/fa/096d8e543b11d1898e0000e8322d00/frameset.htm
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/fa/096ce5543b11d1898e0000e8322d00/frameset.htm

  • Error in MRP Run- Background Job.

    Hi PP Gurus,
    I defined scope of planning for two plants and defined counter too. And set background job through Transaction code MDBT taking 24Hrs as Schedule selection parameter.
    When I'm accessing MDBT after 24Hrs system is throwing following messages in Scheduling log:
    1. Please check the destination for Parallel MRP (message no. MD251)
    Diagnosis of Message:
    No destination have been entered in Customizing or none of the destinations (application server) entered are active. In Customizing for MRP, you define the logical destinations (servers) to be used for parallel processing.
    2. Job cancelled after system exception ERROR_MESSAGE (Message no. 00564)
    Though I tried to enter to Customization through Message no. 1 but system is not allowing for it.
    What could be the problem. No help is available through any OSS note also.
    Please suggest the required solution in terms of Configuration or any other changes?
    Thanks & Regards,
    Abu Arbab

    Hi,
    Two more queries:
    1. If I don't want to go for Parallel Processing MRP, I don't have to select 'Parallel Processing' in Transaction code MDBT variant. But when I'm trying to change it system is not allowing me. It's not allowing me to go further without selection of it. What could be the reason behind it? Either Customization problem or any other?
    2. If set 'Parallel Processing destination' through Customization, system is giving only Development server as available destination and also Customization Request is getting generated. But the request is going to be transported to Production server. Since Parallel Processing destination was selected 'Development server' earlier and now MRP will run on 'Production server', it has to be changed to 'Production server'. But as already mentioned Customization Request will be getting generated and further it is freeze for Customization. How could get rid of these issues?
    Please come back with prompt comments.
    Thanks & Regards,
    Abu Arbab

  • Setting up Background job

    Hello Guys,
    I gone thru the forum and tried to set up the background job for an requirement but could not able to proceed further as I was not sure how to move on..
    Requirement
    We would like setup to call our PM's automatically when they are due or at least 3 days before.This would save time to plan well in advance.
    In this case where should I mention the 3 day period ? I just started getting into SM36 and clikc the start condition and set the time to run and then flagged the periodic job and clicked the periodic values as daily and save it. Then I hit steps button and maintain ristra20 as prog name and keep the variant as blank and save it .(Is variant is neccessary ?) Then I get into sm37 where I could see some * on job name .I dont know how to proceed from here and wht would be the job name and other steps Also I tested job wizard and not sure what is the purpose of this ?
    Could anyone walk me through for the above mentioned requirement
    Mahee

    Mahee,
      Creating the work order ahead of the actual due date is actually accomplished by the "call Horizon" parameter on the Maintenance Plan. A 100% Value on this field indicates that the Call object be created on the date its due. Please enter a appropriate value here based on the plan to get the order created 3 days ahead.
    You actually schedule the PM in background using IP30 transaction.First create and save a variant for the plan that you would liek to schedule.Then call up the variant In here enter the plan details and then choose Program > execute in background.Enter a valid SAP printer and then choose "DATE AND TIME" push button to enter the start date and time of the job.After this, Choose the "Periodic job" check box and then choose "period values" at the bottom of the screen to indicate the frequency at which you would like to run the program and then choose the "SAVE" button.
    This should complete teh job creation for you.
    Regards
    Narasimhan

  • DYNPRO_SEND_IN_BACKGROUND when submitting a background job, when creating a

    Hi.
    We create sales orders via EDI.   When certain sales orders are created, we execute user exists on the Sales Order save.  During the User Exit, we submit/create (job_open_adk function, the submit command, and the job_close_adk function) a background job. 
    The background, is created and executed successfully, but we get 2
    short dumps everytime.
    The short dump is:
    DYNPRO_SEND_IN_BACKGROUND
    The description is:
    Screen output without connection to user.
    The short dump is for the user WF-BATCH.
    I've used DEBUG and the shortdump occurs on the submit command.
    submit zsd
    to sap-spool
    destination 'null'
    immediately ''
    keep in spool 'X'
    without spool dynpro
    and return
    user l_user via job tbtcjob-jobname
    number tbtcjob-jobcount
    with p_vbeln = l_order
    with p_ebeln = l_po
    with p_uname = l_user.
    Nothing should be displayed on the screen.
    I used 'without spool dynpro' to prevent the 'Print Screen List' window
    from appearing.
    I've put this code into a TEST program. I ran the test program
    myself. (under my ID) The program run perfectly. No
    shortdump.
    Similar code is used in other programs and it works perfectly - no shortdumps.
    The short dump occurs when we use ALE/EDI to create a sales order.
    The short dump has the ID WF-BATCH on it.
    I'm guessing the problem is with the WF-BATCH ID. Are printer setting
    missing on a Work Flow ID?
    Any ideas why the 'without spool dynpro' parameter doesn't work for the
    WF-BATCH ID?
    I've tried searching OSS and I looked at the on-line help/documentation
    on Submit. I saw a recommentation to use the
    fuction 'GET_PRINT_PARAMETERS' to set all of the print parameters. I
    tried this, but still got the short dumps.
    Any suggestion on how I can run the Submit command and not get a short dump?
    thanks,
    Michelle

    Hi,
    Try this notes:
    0100915 RSBDCREO: System hangs or parameters not effective
    0377038 HR-CA-ALE: DYNPRO_SEND_IN_BACKGROUND for HR doc. d
    0105165 Dump "DYNPRO_SEND_IN_BACKGROUND" in prog.SAPMSSY0
    0169303 Warning messages displayed for settlement mass pro
    0428489 VL10: Dump 'DYNPRO_SEND_IN_BACKGROUND' with backgr
    [[http://forums.sdn.sap.com/thread.jspa?threadID=14875|http://forums.sdn.sap.com/thread.jspa?threadID=14875]]
    Regards
    HM

  • Background job not automatically poopulating Dependant Demand

    Hi Users,
    We've recently set up a POS & PA using the DP-BOM selection and characteristics, manually created PPM's and generated CVC's using the BOMS. All of this is set up fine in our SCM 7.0.
    The background job has created the forecasts for the ouptput products but NOT the input product.
    Now if I call up the parent material, and then choose to show the input products the dependant demand is generated. If I now return to the material with the dependant demand, it now shows the demand from the parent.
    Or, if the forecast is genereated interactively, then the dependant demand is poopulated.
    Is there an automated method to populate the dependant demand when using background jobs? I would like to think that we don't have to query every sales BOM parent in DP and drill into the input products to load the dependant demand?
    Please let me know if there is an easier way to do this as part of the background processing.
    Thanks
    Edited by: Paul_111 on Mar 31, 2011 4:20 PM

    Hi Andand,
    Thanks for your reply and sorry if my post is confusing.
    As far as the PPM with imputs A & B, output C - I have this relationship working and calcuclating demand in DP no problems.
    If I now add a new PPM combination inpput X, Y and output Z. Create the BOM CVC and TSO so its all set to go. Add to selection profiles and background jobs.
    Now, if I run the background job to create the forecast and this runs successfully. Now I check my products.
    Z has the forecast generated, X & Z have no dependant demand showing.
    The only way I've found that pushes the demand to X & Z is:
    - open product Z in demand planning and then choose the option to show input products from the header
    OR - from demand planning, select the univariate forecast to run interactively.
    My issue:
    The background job (if run alone) does not push the forecast on Z to X & Y.
    And if I show the input products or create forecast (as bove) the dependat demand is shown on X & Y.
    This is going to be a slow process if we have to do this everytime we run the backgound job.
    What am I missing when running the background job?

Maybe you are looking for