Automating offset reqmt date on service order component line

Question

Hi,
I have an issue with automating the offset on component detail screen when creating the new component line.
When creating the new component line we are using EXIT_SAPLCOMK_007 to default plant and storage location based on functional location and stock determination group. this works no problems.
Now based on the same I want to default a value into reqmt date offset on the new component line. I could not find a suitable exit or BADI for this so I enhanced the FM CO_MK_GET_USER_PLANT_STLOC that is calling the exit EXIT_SAPLCOMK_007 and fill the values into the offset fields in resbd structure. the value is set on the offset on the created component line but the reqmt date is not calculated right.
After a little debugging I have concluded that the initial creation of the component line always uses the calendar from the operation, whereas when I manually enter an offset the calendar of the plant is used. I can see that I can implement a BADI so that when entering manually the calendar from the operation is used, but the calculation must be based on the calendar of the plant.
Any ideas how to set the offset automatic on a newly created component line and have the reqmt date calculation work as standard when entered manually?
extra info:
calculation of date is done in FM CX_SCHED_VIA_OPERATING_TIME.
when updated manually its called from FG COMD subroutine FUNCT_BDTER_CHK
when set on creation it is called from FG COMK subroutine BDTER_FILL.
Thanks in advance,
Steffen Høegh.

Answer 1

Hi,
just to update on the solution.
Ended up doing an implicit enhancement at the end of routine bdter_fill in FG comk.
algorithm:
If Offset and manual maintenance of req. mt. date is initial.
  if certain order types
    Logic for determinig offset
       write new offset to resbd_g fields nlfzv and nlfmv
now the rescheduling part in code.
BEGIN determine calendar
Logic for determinig if calendar from plant or operation should be used.
This logic is derived from sub funct_bdter_chk in FG COMD
      TRY.
          GET BADI badi_cx_offset_calid.
   --> call BADI to determine calender for offset
          CALL BADI badi_cx_offset_calid->change_calid
            EXPORTING
              is_caufvd        = caufvd
              is_afvgd         = afvgd
            IMPORTING
              flg_use_wc_calid = flg_wc_cal.
        CATCH cx_badi_not_implemented.
    no implementation
        CATCH cx_badi_multiply_implemented.
        CATCH cx_badi.
      ENDTRY.
      IF NOT flg_wc_cal IS INITIAL.
        l_calid = afvgd-kalid.
      ELSE.
        IF l_t001w-werks <> t001w-werks.
          CALL FUNCTION 'CO_TA_T001W_READ'
            EXPORTING
              t001w_werk = resbd_g-werks
            IMPORTING
              t001wwa    = l_t001w
            EXCEPTIONS
              not_found  = 1
              OTHERS     = 2.
        ELSE.
          l_t001w = t001w.
        ENDIF.
        l_calid = l_t001w-fabkl.
      ENDIF.
END determine calendar
*BEGIN Scheduling
*logic is from above
      IF caufvd-autyp = auftragstyp-fert OR
         caufvd-autyp = auftragstyp-bord.
        CALL FUNCTION 'CX_SCHED_VIA_OPERATING_TIME'
          EXPORTING
            i_date_start = resbd_g-bdter
            i_time_start = resbd_g-bdztp
            i_duration   = resbd_g-nlfzv
            i_unit       = resbd_g-nlfmv
            i_fcalid     = afvgd_g-kalid
          IMPORTING
            e_date_end   = resbd_g-bdter
            e_time_end   = resbd_g-bdztp.
      ELSE.
        IF NOT resbd_g-bdter IS INITIAL.                    "note683510
          IF resbd_g-nlfzv < 0.
            l_time = time_const-beg.
          ELSE.
            l_time = time_const-end.
          ENDIF.
          CALL FUNCTION 'CX_SCHED_VIA_OPERATING_TIME'
            EXPORTING
              i_date_start = resbd_g-bdter
              i_time_start = l_time
              i_duration   = resbd_g-nlfzv
              i_unit       = resbd_g-nlfmv
              i_fcalid     = l_calid
            IMPORTING
              e_date_end   = resbd_g-bdter.
        ENDIF.
      ENDIF.
    ENDIF.
Regards and thanks for the help,
Steffen Høegh
Vestas Wind Systems