Modify Schedule Date for a Nomination

I tried both the Function Modules  'OIJ_NOM_MAINTAIN' & 'OIJ_MAINTAIN_NOMINATION'. But it is throwing a Dump.
Can anyone please help & let me know which is the actual Function Module to modify the nomination.
The input value is NOMTK (Nomination Key) and need to modify IDATE field value.
Thanks & Regards,
Sowmya

It worked using FM
RFC_TSW_NOM_CHANGEFROMDATA
Thanks!
Providing update indicator 'U' is important. And marking 'X' in the Checkbox as shown below:
l_t_headerdata-nominationnumber_ext = g_nomnr.  "Nomination number
        l_t_headerdata-nominationnumber_sap = g_nomtk.  "Nomination technical Key
        l_t_headerdatax-nominationnumber_sap = g_nomtk.  "Nomination technical Key
        l_t_headerdatax-updkz = 'U'.  "Update indicator = 'U' indicates change
        LOOP AT l_t_oijnomi INTO l_wa_oijnomi.
          l_wa_itemx-nominationnumber_sap  = g_nomtk.
          l_wa_itemx-updkz = 'U'.     "Update indicator = 'U' indicates change
          l_wa_itemx-itemnumber  = l_wa_oijnomi-nomit.
          l_wa_itemx-scheduleddate = 'X'.
          APPEND l_wa_itemx TO l_t_itemx.
          CLEAR l_wa_itemx.
          l_wa_nomi-nominationnumber_sap = l_wa_oijnomi-nomtk.
          l_wa_nomi-itemnumber  = l_wa_oijnomi-nomit.
          l_wa_nomi-scheduleddate = l_wa_oijnomi-idate.
          l_wa_nomi-itemtype = l_wa_oijnomi-sityp.
          APPEND l_wa_nomi TO l_t_nomi.
          CLEAR l_wa_nomi.
        ENDLOOP.
  CALL FUNCTION 'RFC_TSW_NOM_CHANGEFROMDATA'
            EXPORTING
              headerdata_in      = l_t_headerdata
              headerdata_inx     = l_t_headerdatax
            TABLES
              nominationitem_in  = l_t_nomi
              nominationitem_inx = l_t_itemx
              return             = l_t_return.
          IF sy-subrc EQ 0.
            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
          ENDIF.
Thanks & Regards,
Sowmya

Similar Messages

  • Updating Scheduling data for Purchase Order

    Hi,
    I need a function module which can update the scheduling data for purchase order in EKET table. Normally we create Purchase Order as a reference from purchase requisition through BAPI_PO_CREATE1. That time it takes care of all the scenarios. But as per the requirement I want to create a PO which is created from more than one Purchase Requistions so I can't use the said BAPI. But still I am using this BAPI and after creation is completed I am updating the Requistions. The same scenario is taken care in ME59N, but I can't copy that code because of some requirements. So could any one please give me the idea to replicate the same functionality with any function module or other ways.
    Thanks
    Somnath paul

    try to pass all u sheduling related fields to POSCHEDULE and make sure u have enabled POSCHEDULEX along with sheduling related fields .....also (if no changes  are there  leave it with space )...
    this will definetly update not only eket table ....it will update every table regarding to purchase order,ekpo,ekko,eket ...etc
    Example of population of BAPI interface in the Function
    Parameter: POHEADER
    COMP_CODE            =                    1000
    DOC_TYPE             =                    NB
    ITEM_INTVL           =                    00001
    VENDOR               =                    0000001000
    PMNTTRMS             =                     0001
    PURCH_ORG            =                     1000
    PUR_GROUP            =                     001
    CURRENCY             =                     EUR
    Parameter: POHEADERX
    COMP_CODE            =                     X
    DOC_TYPE             =                     X
    ITEM_INTVL           =                     X
    VENDOR               =                     X
    PMNTTRMS             =                     X
    PURCH_ORG            =                     X
    PUR_GROUP            =                     X
    Parameter: POITEM
    PO_ITEM              =                     00001
    MATERIAL             =                    100-100
    PLANT                =                    1000
    STGE_LOC             =                    0001
    QUANTITY             =                    15.000
    TAX_CODE             =                    V0
    ITEM_CAT             =                     0
    ACCTASSCAT           =                    K
      Parameter: POITEMX
      PO_ITEM              =                    00001
      MATERIAL             =                    X
      PLANT                =                    X
      STGE_LOC             =                    X
      QUANTITY             =                    X
      TAX_CODE             =                    X
      ITEM_CAT             =                    X
      ACCTASSCAT           =                    X
      Parameter: POSCHEDULE
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0001
      DELIVERY_DATE        =                    02.12.2002
      QUANTITY             =                    6.000
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0002
      DELIVERY_DATE        =                    03.12.2002
      QUANTITY             =                    5.000
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0003
      DELIVERY_DATE        =                    04.12.2002
      QUANTITY             =                    4.000
      Parameter: POSCHEDULEX
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0001
      PO_ITEMX             =                    X
      SCHED_LINEX          =                    X
      DELIVERY_DATE        =                    X
      QUANTITY             =                    X
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0002
    Parameter: POACCOUNT
    PO_ITEM              =                    00001
    SERIAL_NO            =                    01
    QUANTITY             =                    15.000
    GL_ACCOUNT           =                    0000400000
    COSTCENTER           =                    0000001000
    CO_AREA              =                    1000
    Parameter: POACCOUNTX
    PO_ITEM              =                    00001
    SERIAL_NO            =                    01
    QUANTITY             =                    X
    GL_ACCOUNT           =                    X
    COSTCENTER           =                    X
    CO_AREA              =                    X
    Parameter: POCOND
    ITM_NUMBER           =                    000001
    COND_ST_NO           =                    001
    COND_TYPE            =                    PB00
    COND_VALUE           =                    79.900000000
    CURRENCY             =                    EUR
    CURRENCY_ISO         =                    EUR
    COND_UNIT            =                    KG
    COND_P_UNT           =                    1
    CHANGE_ID            =                    U
    Parameter: POCONDX
    ITM_NUMBER           =                    000001
    COND_ST_NO           =                    000
    ITM_NUMBERX          =                    X
    COND_TYPE            =                    X
    COND_VALUE           =                    X
    CURRENCY             =                    X
    CHANGE_ID            =                    X
    Parameter: POPARTNER
    PARTNERDESC          =                    OA
    LANGU                =                    EN
    BUSPARTNO            =                    0000001100
    PARTNERDESC          =                    GS
    LANGU                =                    EN
    BUSPARTNO            =                    0000001200
    PARTNERDESC          =                    PI
    LANGU                =                    EN
    BUSPARTNO            =                    0000001000
    reward points if helpful....

  • Issue with update_task API for updating Scheduled Dates for Task..

    Hi All,
    We have a requirement to update the project and task dates to a specified period from the current dates. I dont want to update all the tasks, and hence using the update_task API. The scheduled_finish_Date is the column from "pa_proj_elem_ver_schedule" which we want to update. As, this is the date which is shown on the Workplan tab for the tasks for (Scheduled Start and Scheduled Finish Date). I want to extend this scheduled_finish_Date to some days , say for eg. 60 days.
    To achieve, that update_task api is being used and the parameter for the scheduled_date is : p_scheduled_finish_date, this is passed as call to pa_project_pub.update_task API.
    We are also updating the completion data, which is happening fine and is updating the pa_tasks : completion_date column.
    Problem is with scheduled date, Please let me know how to go about this issue.
    Here is the sample code for calling the API :
    pa_project_pub.update_task
    (p_api_version_number => l_api_version_number_i,
    p_commit => l_commit,
    p_init_msg_list => l_init_msg_list,
    p_msg_count => l_msg_count,
    p_msg_data => l_msg_data,
    p_return_status => lt_return_status,
    p_pm_product_code => l_pm_product_code,
    --p_structure_updates_flag      => g_no,
    p_pm_project_reference => l_proj_reference,
    p_pa_project_id => p_project_id_i,
    p_pm_task_reference => p_pm_task_reference_i,
    p_pa_task_id => p_task_id_i,
    p_task_name => p_task_name_i,
    p_task_number => p_task_number_i,
    p_pa_parent_task_id => p_parent_task_id_i,
    p_task_completion_date => p_tsk_actual_finish_date_i,
    --Transaction Date (shown on the screen)
    p_scheduled_finish_date => p_tsk_sched_end_date_i,
    -- Scheduled Date (shown on the screen)
    p_out_pa_task_id => l_pt_task_id,
    p_out_pm_task_reference => l_pt_task_ref
    I am really not sure if I am missing anything here, please suggest as to how to update the Schedule Start and Finish Dates using the API.
    Waiting in anticipation!
    Thank you
    Anand.

    Hello,
    Make sure the wf is active in QA (re-activate if possible), check the transport for errors, check authorizations for WF-BATCH perhaps delete and recreate via SWU3?), refresh the buffers (SWU_OBUF).
    Please let me know if any of this helps.
    regards
    Rick Bakker
    Hanabi Technology

  • Goods receipt to be done earlier to scheduled date for scheduling agreement

    Dear Experts,
    We have a scenario where in the goods is received earlier than the scheduled date mentioned in the scheduling agreement, but system does not allow to do the GR. Everytime Stores people have to contact the purchase guys to change the scheduled date.
    Please let me know how to overcome this.
    Regards,
    Praveen

    sapPraveen wrote:
    Dear Experts,
    >
    > We have a scenario where in the goods is received earlier than the scheduled date mentioned in the scheduling agreement, but system does not allow to do the GR. Everytime Stores people have to contact the purchase guys to change the scheduled date.
    > Please let me know how to overcome this.
    >
    > Regards,
    > Praveen
    Hello Praveen,
    Set Message Number 254 (Work Area M7) to warning in customizing for Inventory Management and Physical Inventory under Define attributes of the system message.
    This should solve your problem!!
    Thanks,
    Reetesh

  • Modify Classification data for IL02

    Hi,
      I want to modify the classification data for Functional location.
    Is there any function modules available to change. I know the functional module for Material classification, but Functional location its not working.
    SO pls tell me the function modules or any other method is available.
    I was unable to do to in BDC.
    regards
    Rajesh V

    Hi,
    CALL FUNCTION 'BAPI_OBJCL_CHANGE'
      EXPORTING
        objectkeynew    = lv_funcloc
        objecttablenew  = 'IFLOT'
        classnumnew     = lv_class
        classtypenew    = '010'
      TABLES
        allocvaluesnum  = li_numc
        allocvalueschar = li_char
        allocvaluescurr = li_curr
        return              = li_return.
    if not li_return[] is initial.
    read table li_return into lwa_return with key TYPE = 'E'.
    if sy-subrc ne 0.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    endif.
    endif.
    Fill the new characteristic values into table parameters li_numc, li_char, li_curr depending on the data type (field ATFOR) of the characteristic value.
    Inside the FM it uses BAPI_OBJCL_GETDETAIL to get the old characteristic values and make comparision with table parameters li_numc, li_char, li_curr and updates the characteristic data for the functional location and class.
    Regards,
    Dwaraka.S
    Edited by: Dwarakanath Sankarayogi on Jan 29, 2009 10:49 AM

  • Not able to modify the data for infotype 0008 using FM

    Hi All ,
    I have got a requirement for updating the infotype 0008 data  using FM : HR_MAINTAIN_MASTER_DATA.
    While trying to modify the wagetypes data which is of blank ..unable to upload the amount for that partcular field ..
    For this am herewith the link  of o/p :
    http://i55.tinypic.com/28jfw2c.jpg for this am also posting the code...
    Please suggest me furthur in what way i can upload..
          SELECT * FROM pa0008 INTO TABLE itab_pa0008
    FOR ALL ENTRIES IN itab
        WHERE pernr = wa_data-pernr
        AND begda = wa_data-begda_out
        AND endda = wa_data-endda_out.
        DESCRIBE TABLE itab_pa0008 LINES lin.
        IF lin EQ  0.
          c_action = 'INS'.
        ELSE.
          c_action = 'MOD'.
        ENDIF.
        LOOP AT itab INTO wa_itab WHERE pernr = wa_data-pernr.
          CLEAR: wa_bapireturn, wa_bapireturn1, wa_hr_return.
          REFRESH: it_pprop[],it_modified_keys[].
          it_pprop-infty = '0008'.
          it_pprop-fname  = 'P0008-TRFAR'.                 "1
          it_pprop-fval = wa_itab-trfar.
          APPEND it_pprop.
          CLEAR it_pprop.
          it_pprop-infty = '0008'.
          it_pprop-fname  = 'P0008-TRFGB'.                 "2
          it_pprop-fval = wa_itab-trfgb.
          APPEND it_pprop.
          CLEAR it_pprop.
          it_pprop-infty = '0008'.
          it_pprop-fname  = 'P0008-TRFGR'.                  "3
          it_pprop-fval = wa_itab-trfgr.
          APPEND it_pprop.
          CLEAR it_pprop.
          it_pprop-infty = '0008'.
          it_pprop-fname  = 'P0008-TRFST'.                  "4
          it_pprop-fval = wa_itab-trfst.
          APPEND it_pprop.
          CLEAR it_pprop.
          flag = flag + 1.
    *****************************************************************************************************5
          BREAK-POINT.
          IF NOT wa_itab-lga1 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA01'.
            it_pprop-fval = wa_itab-lga1.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet1.
          ENDIF.
          IF NOT wa_itab-bet1 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET01'.
            it_pprop-fval = wa_itab-bet1.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************6
         IF NOT wa_itab-lga2 IS INITIAL.
           it_pprop-infty = '0008'.
           it_pprop-fname  = 'P0008-LGA02'.
           it_pprop-fval = wa_itab-lga2.
           APPEND it_pprop.
           CLEAR it_pprop.
           bet1 = wa_itab-bet2.
         ENDIF.
          IF NOT wa_itab-bet2 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET02'.
            it_pprop-fval = wa_itab-bet2.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************7
          IF NOT wa_itab-lga3 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA03'.
            it_pprop-fval = wa_itab-lga3.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet3 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET03'.
            it_pprop-fval = wa_itab-bet3.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************8
          IF NOT wa_itab-lga4 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA04'.
            it_pprop-fval = wa_itab-lga4.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet4 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET04'.
            it_pprop-fval = wa_itab-bet4.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************9
          IF NOT wa_itab-lga5 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA05'.
            it_pprop-fval = wa_itab-lga5.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet5 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET05'.
            it_pprop-fval = wa_itab-bet5.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************10
          IF NOT wa_itab-lga6 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA06'.
            it_pprop-fval = wa_itab-lga6.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet6 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET06'.
            it_pprop-fval = wa_itab-bet6.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************11
          IF NOT wa_itab-lga7 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA07'.
            it_pprop-fval = wa_itab-lga7.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet7 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET07'.
            it_pprop-fval = wa_itab-bet7.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************12
          IF NOT wa_itab-lga8 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA08'.
            it_pprop-fval = wa_itab-lga8.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet8 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET08'.
            it_pprop-fval = wa_itab-bet8.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************13
          IF NOT wa_itab-lga9 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA09'.
            it_pprop-fval = wa_itab-lga9.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet9 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET09'.
            it_pprop-fval = wa_itab-bet9.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************14
          IF NOT wa_itab-lga10 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA010'.
            it_pprop-fval = wa_itab-lga10.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet10 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET010'.
            it_pprop-fval = wa_itab-bet10.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************15
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-LGA11'.
       it_pprop-fval = wa_itab-lga11.
       APPEND it_pprop.
       CLEAR it_pprop.
       bet1 = wa_itab-bet2.
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-BET11'.
       it_pprop-fval = wa_itab-bet11.
       APPEND it_pprop.
       CLEAR it_pprop.
    ********************************************************************************************************16
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-LGA12'.
       it_pprop-fval = wa_itab-lga12.
       APPEND it_pprop.
       CLEAR it_pprop.
       bet1 = wa_itab-bet2.
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-BET12'.
       it_pprop-fval = wa_itab-bet12.
       APPEND it_pprop.
       CLEAR it_pprop.
    ********************************************************************************************************17
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-LGA13'.
       it_pprop-fval = wa_itab-lga13.
       APPEND it_pprop.
       CLEAR it_pprop.
       bet1 = wa_itab-bet2.
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-BET13'.
       it_pprop-fval = wa_itab-bet13.
       APPEND it_pprop.
       CLEAR it_pprop.
    ********************************************************************************************************18
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-LGA14'.
       it_pprop-fval = wa_itab-lga14.
       APPEND it_pprop.
       CLEAR it_pprop.
       bet1 = wa_itab-bet2.
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-BET14'.
       it_pprop-fval = wa_itab-bet14.
       APPEND it_pprop.
       CLEAR it_pprop.
    BREAK-POINT.
          CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
            EXPORTING
              number = wa_itab-pernr
            IMPORTING
              return = wa_bapireturn1.
          BREAK-POINT.
         IF c_action = 'INS'.
           CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
             EXPORTING
               pernr           = wa_itab-pernr
               actio           = 'INS'
             tclas           = 'A'
               begda           = wa_data-begda_out             "'20110401'
               endda           = wa_data-endda_out             "'99991231'
               dialog_mode     = '2'
             luw_mode        = '1'
             IMPORTING
               return          = wa_bapireturn
               return1         = wa_bapireturn1
               hr_return       = wa_hr_return
             TABLES
               proposed_values = it_pprop
               modified_keys   = it_modified_keys.
           IF NOT wa_bapireturn IS INITIAL.
             WRITE : / wa_bapireturn.
             CLEAR : wa_itab , wa_bapireturn.
           ENDIF.
         ELSEIF c_action = 'MOD'.
            CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
              EXPORTING
             infty         = '0008'
                pernr           = wa_itab-pernr
                actio           = 'MOD'
                begda           = wa_data-begda_out             "'20110401'
                endda           = wa_data-endda_out             "'99991231'
          record        =  p_record
             recordnumber  = wa_itab-SEQNR
             operation     = change
             nocommit      = nocommit
                dialog_mode     = '0'
             IMPORTING
                return          = wa_bapireturn
                return1         = wa_bapireturn1
                hr_return       = wa_hr_return
              TABLES
                proposed_values = it_pprop
                modified_keys   = it_modified_keys.
            IF NOT wa_bapireturn IS INITIAL.
              WRITE : / wa_bapireturn.
              CLEAR : wa_itab , wa_bapireturn.
            ENDIF.
         ENDIF.
          CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
            EXPORTING
              number = wa_itab-pernr
            IMPORTING
              return = wa_bapireturn1.
        ENDLOOP.
      ENDLOOP.

    Here is a sampe, and the logic you are using for wages goes in the internal table for wages (you already have the enqueue & dequeue so you don't have to worry about that, so you only have to add the BAPI_TRANSACTION_COMMIT):
    CALL FUNCTION 'BAPI_BASICPAY_CHANGE'
      EXPORTING
        employeenumber             = pa0008-pernr
        subtype                    = pa0008-subty
        objectid                   = pa0008-objps
        lockindicator              = pa0008-sprps
        validitybegin              = pa0008-begda
        validityend                = pa0008-endda
        recordnumber               = pa0008-seqnr
        payscaletype               = pa0008-trfar
        payscalearea               = pa0008-trfgb
        payscalegroup              = pa0008-trfgr
        payscalelevel              = pa0008-trfst
    *   NEXTINCREASE               =
    *   LOCALALLOWLEVEL            =
    *   PARTNERSHIP                =
    *   CURRENCY                   =
    *   COMPARISONPAYSCLTYPE       =
    *   COMPARISONPAYSCLAREA       =
    *   COMPARISONPAYSCLGRP        =
    *   COMPARISONPAYSCLLVL        =
    *   COMPNEXTINCREASE           =
    *   CAPACITYUTILLEVEL          =
    *   HOURSWORKEDPERPERIOD       =
    *   ANNUALSALARY               =
    *   CASEGROUPCATALOG           =
    *   CASEGROUP                  =
    *   CURRENCYANNUALSALARY       =
    *   REASON                     =
    *   NOCOMMIT                   =
    * importing
    *   return                     =
    TABLES
       wagetypes                  = wages.
    Regards,
    Ryan Crosby

  • Project Server 2010 - Different Schedule Dates for Different Users -- Same File

    We have an issue regarding users viewing the same schedule, different machines.
    The PMs have a schedule that was built in 2007 by the offshore team.  We are running Project Server 2010 corporate, and they the PMs here on site have Project Professional 2010.  Within the last couple of weeks, the PMs have noticed changes in
    the dates.
    When I open the schedule, I see the expected dates rendered in both PWA and Project Professional.  Both draft and published versions are the same regardless of where the schedule is opened for editing.  There are two PMs managing the schedules. 
    One sees what I see--the expected dates.  The other sees differences in dates--months, in fact.  Scheduled end date is 10/22/2013.   When the second PM opens the schedule, he sees a scheduled end date of 2/17/2014.
    I advised them that the offshore team needed to upgrade to 2010 due to the differences between 2007 and 2010.  Additionally, and I could be wrong, having the server run in compability mode for so long (the upgrade was done in May 2013), is not ideal. 
    (Offshore team has since updated to 2010.)
    Any thoughts on what could be causing this issue?  Corrupt version of Professional?  Settings askew?
    Thank you,
    L.D.

    My bad, I didn't know that you were not using Project Server.
    Then the file might be corrupted.
    Try the
    XML export and the
    save for sharing method to repair it.
    Hope this helps,
    Guillaume Rouyre, MBA, MCP, MCTS |

  • PO - Schedule Date

    HI all
    I have one query regading Schedule date (Purchase order).
    While creating PO , CUSTOMER fills the schedule Date for ITEMS to be delivered.
    Now when Vendor Sends confirmation,He states DELIVERY date in confirmation.
    How many days difference is possible/allowed in SCHEDULE DATE and DELIVERY date.
    For example: if SCHEDULE date is 12th NOVEMBER 2006
    WHAT could be last possible DELIVERY DATE that a vendor can fill while confirming for that PO?
    Thanks in Advance.
    Vijay Raheja

    Hi Viajay,
    I don't think SAP have any real control over the delivery date specified by the vendor.
    It can not be enforced in a standard system.We can use user exits to control this behavior.
    SAP has given the user exit to determine Earliest Delivery Date (GR Check (PO Only) ) EXIT_SAPLEINR_004 at the time of GR.
    Hope this helps you to some extend.
    Thank you.
    Regards,
    Karun.M

  • Read PO delivery schedule data

    Hi SAPPERS,
    Is there any FM or table, were I can find delivery schedule data from purchase order-?
    thanks for your help
    Saso

    Hi,
    You can get delivery schedule data for each line item of PO in EKET table.
    Regards
    Radhika

  • Modify EXIF date?

    iPhoto '11 (9.2.2) lets me set a date for photos, but apparently this new date is known only to iPhoto. Even if I check the "Modify original files" box when I set the date, the original date of the photo in its EXIF data is unchanged. This can be a problem, as when exporting photos or uploading photos to Flickr, which either can't see or ignores the  date set by iPhoto and uses the date in the EXIF data instead. Is there a way to change the date in the EXIF data?
    I saw one post (from 2007) that said checking the "Modify original files" option WOULD change the EXIF date and another post that described changing individual photo dates through the Info mode. Neither works for me. Is that a bug? I have to use Batch Change to modify the date for even a single photo, and even if I do that with "Modify original files" checked, the EXIF data is not changed.

    Sorry if I'm not being clear. Here's a summary:
    1. A photo is taken in August of 1966 and developed as a slide.
    2. Last summer the slide is digitized: EXIF date is 6/7/11.
    3. A month or so later I add the photo  to iPhoto, which still reports the date as 6/7/11.
    4. On 3/7/12, I edit the photo in iPhoto and use the Batch Change feature to set the date to when the photo was actually taken: 8/1/66. As expected, iPhoto Info now shows the date as 8/1/66.
    5. On 3/12/12 I use the Flickr uploader in iPhoto to upload the photo to my Flickr set. Flickr reports the date of the photo as 6/7/11.
    6. Today, 3/21/12, I look at the file information for the photo in two places: Finder and Tools Inspector in Preview. Both of these places report the same Created and Modified date: 3/7/12 (the date I edited the photo in iPhoto).
    So, what is unexplained is:
    1. When I change the date in iPhoto, why does the file creation date and modification date change to the present day instead of the date I set?
    2. When I upload the photo to Flickr, why does the creation date revert to the date when the image was first digitized from the slide?
    And, of course, my only goal is that the date I set in iPhoto show up in Flickr when I upload it there.

  • STO scheduling dates

    HI All,
    I have created two sales order for STO process. In first sales order (6001) I have four line items.  Each has different scheduled dates:
    For Eg.:
    1st 10th Aug
    2nd 13th Aug
    3rd 16th Aug
    4th 19th Aug
    For the second sales order (6002) also I have taken the same material and it is showing the scheduled dates as per material availability.
    1st 10th Aug
    2nd 13th Aug
    3rd 17th Aug
    4th 20th Aug.
    The problem here it is, the system supposed to deliver the goods as per the schedulied dates.  But  here it is taking on the basis of the sales order.  It is giving the preference to order (60001).  It is taking and confirming all the line items of the first order(6001) and it is picking only first line item of the second order (6002)
    Please provide me solution to deliver on the basis of the scheduled dates.
    It is urgetnt
    Thanks in advance
    regards
    RP.

    Hi Nayak,
    I am asking STO with reference to sales order.
    thanks
    regards
    RP

  • How to display "No data for yesterday" in a scheduled report on Webi

    Hi All,
    In Webi, I am working on scheduling reports and was asked by a user if the scheduled report on Webi can display "No data for yesterday/no orders for yesterday" when the report returns no data due to No Orders submitted or a business holiday. This sounded a good idea to me as this report only looks for previous days orders/sales and there are many instances when the report will return blank page due to no activity the day before.
    Can anyone please guide me on the possibility of achieving something like this on Webi using Bex query.
    Any help will be appreciated .
    Thanks
    Gaurav

    Hi,
    You can format the blocks in the report as "Hide When Empty" or "Hide When [some formula]" and have a blank cell added behind these blocks with a text "No Data for Yesterday"
    Need to set the relative position and ordering for this accordingly.

  • Calculate all days in month from schedule line delivery date for 12 mths

    Hi experts,
    I am trying to solve a problem and would appreciate any help! Im on BI7.
    The user will input a date for the schedule line delivery date via a variable.
    From this date I need to go forward 12 months exactly and display a key figure (outstanding value) by months but the first and last months must only use the days in that month i.e not the whole month if not selected by the user.
    I.e if the user types in 13.05.2008
    The display need to show (columns)
    May 08 (13th to end of May 2008)
    June 08   (All)
    July 08    (All)
    August 08    (All)
    Sept 08    (All)
    Oct 08     (All)
    Nov 08     (All)
    Dec 08    (All)
    Jan 09     (All)
    Feb 09    (All)
    Mar 09    (All)
    April 09   (All)
    May 09  (1st to 12)
    So I neen to restrict the key figure (Outstanding Value) by Schedule Line Delivery Date and display as above on a 12 month forecast basis from the day (sch line delivery daye) entered as a variable by the user.
    I also need the first month to only show the dates in the month remaining including the date entered as a variable. The last month must go up to the day before exactly a year in front.
    I have created the 12 months as a structure and can include the key figure and the schedule line delivery date. The schedule line delivery date for each period needs to be restricted. How can I do this to achieve the above?
    Thanks in advance. Will assign good points for a speedy solution.
    Best
    Steve.

    Hi,
        Check "OVLY" and "OVLZ" and If the sceduling is active for he shipping point /sales document type.  Check "OVXD" and see If the Loading time/ Pick/pack time is determined from it. If they are getting determined from shipping point check the shipping point calender in "SCAL" .If it has saturday and sunday as holidays ,then you may have to change them. And check If the customer has goods recieving hours assigned to him (In customer master unloading point). If he has only 5 working days and If he accepts only goods at 8 am in the morining then system would propose like this.Kindly please let me know If you need any more Information on this.
    Regards
    Ram Pedarla

  • No Schedule Lines for Delivery upto selected date

    Hi,
    I have a scenario for Repairs order. Following are the steps of my scenario:
    1. Create a Repair Order.
    2. Create return delivery to recieve the faulty item.
    3. Create Outbound Delivery to send a loaner item to customer (This item would be returned once the returned item is repaired and sent to customer)
    4. Send the item after repairing.
    5. Receive the loaner item.
    When I am trying to create outbound delivery for Loaner item, i am getting an error "No Schedule Lines for Delivery upto selected date".
    I have checked and verified the schedule line date.
    I have checked for Confirmed Quantity.
    Below are the screenshots. Please let me know how can this issue be resolved.

    Hi,
    With reference of your screens,I can see there is no qty in the field loner hence you are getting issue.
    1.May I know ,why you have checked indicator -Repair?
    because ,you are not going to repair the goods.You are just sending loner items to customer.In this case what is the use of to indicate repair ?.
    Thanks,
    Naren

  • GR Date for Delivery Schedule line

    Vendor On-Time Delivery Report
    We have vendor On-Time Delivery report requirement, where we rate the
    goods-delivery of a vendor as "On-Time" or "Early" or "Late". The
    rating is given based on the difference between "Statistical Delivery
    date" and "GR date" (in the PO/Scheduling Agreement).
    In case of Scheduling Agreement (SA) we have to give delivery rating
    for each Delivery Schedule Line - Based on the difference
    between "Statistical Delivery date" and "GR date"
    The Goods Receipt is done at Schedule line item level and not at
    Delivery Schedule Item level, the GR date is not populated at Delivery
    Schedule Line level and we are not able to find the GR date for each
    Delivery Schedule Line.
    Once we get the "GR date" at SA Delivery Schedule line level, then from
    the difference between this date and "Statistical Delivery" date, we
    can rate the delivery of vendor as "On-Time" or "Early" or "Late".
    Is there any way that we can populate/get the GR date (GR creation date) for each delivery
    schedule line?
    Thanks in advance.

    Hi Rahul,
    I am working on the same requirement. Appreciate ur help on the same. The notes helps in understanding how quantities are distributed while GR. did u implemented any logic for this distribution or something else to compare the dates. I believe by checking the open quantity (EKET) (scheduled - GR quantity) we can see if there is open quantity for any schedule for the previous day then tht falls under the delayed quantity and if there is zero open quantity, it is on time delivery.
    thnx,
    Upender

Maybe you are looking for