Entry date in blank for limited Contract Type

Hello,
I've set up the feature ENTRY with the value EINDT X for my molga, but when I run a hiring action and in infotype 16, in the field Contract Type I use a Limited contract Type, and when I run the report S_AHR_61016362 (Flexible Employee
Data) the Entry Date Column is in blank but it does not happen when I use Unlimited Contract Type.
Does anyone can help me?

Hi,
This feature provides entry date definition method to function module HR_ENTRY_DATE. In your case it reads following fields from IT0016:
1. EINDT "Initial Entry"
2. KONDT "Date of Entry into Group"
First of all check that you entered one of these fields for employees with temporary contract.
Cheers

Similar Messages

Uploading data in MM01 for different material types

Hi,
I have a doubt regarding uploading the data in MM01 for different material types.
Generally in MM01, we have different views for different material types. The number of views will vary depending upon the material type that we select.
I have a scenario, where in to upload the data, I have a flat file that consists of data for different message types. So, how to upload the data in such case.
Can anyone help me on the same by providing explanation or sample code...? What would be the possible ways to upload data in such scenario.
That would be of great help.
Thanks & Regards,
Pradeep.

See the below code and use FM SELECTION_VIEWS_FIND..
REPORT zjpmuim306 NO STANDARD PAGE HEADING LINE-SIZE 250 MESSAGE-ID
zjpm001.
*&   I N B O U N D V I A   A B A P : Batch input Session method     *
*&   Development ID: IM_DD_306_LJP                                   *
*&   Report        : ZJPMUIM306                                      *
*&   The Purpose of the Object is to interface Create Input Record   *
*&   for SAP Migration from the Material master of BPCS All the      *
*&   information received at BPCS is collected into a single record. *
*&   By using session method upload data from file ,one item is
*&   created for one record                                          *
*&   Change Log:                                                     *
*&   Init       Who              Date         Text                   *
*& MALIKDH1   Seshu Reddy    26-07-2003   Initial Version           *
                         Constants                                   *
CONSTANTS:c_vkorg(4) type c value 'JP20',        " Sales Organization
          c_vtweg(2) type c value 'TR' ,         " Distribution Channel
          c_werks(4) Type c value 'JP01' ,       " Plant
          c_viewlist(15) VALUE 'KDEALBSZXVPCFQG'," View list
          c_scm_view TYPE msichtausw-dytxt VALUE 'SCM View',
          c_sd_view TYPE msichtausw-dytxt VALUE 'SD View',
          c_seq_code(2) VALUE 'Z1',              " Sequential Code
          c_keep(1) TYPE c VALUE 'X',           " Keep
          c_group LIKE apqi-groupid VALUE 'IM306', " Session Name
          c_tcode LIKE tstc-tcode VALUE 'MM02', " Transaction Code
          c_blank(1) VALUE ' ',                   " Blank
          c_intls(1) VALUE 'N'.                  " Logistic Status
              Variables                                      *
DATA: g_flag1(1), " Variable to hold
      g_flag(1),   " Variable to hold
      g_file LIKE rlgrap-filename VALUE
     'C:\Documents and Settings\seshur\Desktop\HCLT123.CSV'. " File name
       Internal tables/ Work area                           *
Internal Table for Delimter
DATA : BEGIN OF t_delim OCCURS 0,
       text(1000),
       END OF t_delim.
Internal table for BDC processing
DATA : t_bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.
Internal table for holding the data which has to be uploaded.
DATA: BEGIN OF t_bpcs OCCURS 0,
      matnr(15) TYPE c, " material no
      dosage(40) TYPE c, " Dosage form(Local)
      appearance(40) TYPE c, " Appearance
      idcode(6) TYPE c,     " Identification Code
      prostformno(10) TYPE c, "SOP
      weitab(7) TYPE c,    " Weight/tablet
      uom1(2) TYPE c,     " UOM of Carton
      uom2(2) TYPE c,     " UOM of Case
      carsize(14) TYPE c, " Carton size
      cassize(14) TYPE c, " Case size
      rupqty(11) TYPE c, " Round up
      abvname(3) TYPE c, " Product short name
      END OF t_bpcs.
*Internal table for t_bpcs
DATA: BEGIN OF t_mdata OCCURS 0,
      matnr LIKE marc-matnr, " Material number
      zzjp_dos_frm LIKE marc-zzjp_dos_frm, " Dosage form(Local)
      zzjp_aprn LIKE marc-zzjp_aprn, " Appearance
      zzjp_con_id LIKE marc-zzjp_con_id," Identification Code
      zzjp_nyu_sop LIKE marc-zzjp_nyu_sop,"SOP
      zzjp_wei_tab(10) type c , " Weight/tablet
      zzjp_bio LIKE marc-zzjp_bio,"Biologics Indicator
      zzjp_itf LIKE marc-zzjp_itf, " ITF code
      zzjp_car(2) type c, " UOM of Carton
      zzjp_cas(2) type c, " UOM of Case
      zzjp_car_size(11) type c," Carton size
      zzjp_cas_size(11) type c, " Case size
      zzjp_rupqty(11) type c, " Round up
      zzjp_init_ls LIKE marc-zzjp_init_ls, " Logistic Status
      zzjp_re1 LIKE marc-zzjp_re1, "Document type(Local)
      zzjp_re2 LIKE marc-zzjp_re2, "Report type
      zzjp_re3 LIKE marc-zzjp_re3, "Shipping report type
      zzjp_pro_id LIKE mvke-zzjp_pro_id," Product output sequence
      zzjp_bu_id LIKE mvke-zzjp_bu_id, " Business unit indicator
      zzjp_abv_name LIKE mvke-zzjp_abv_name," Product short name
      zzjp_abv_id1 LIKE mvke-zzjp_abv_id1," Product short name output
      zzjp_abv_id2 LIKE mvke-zzjp_abv_id2," Product short name internal
      zzjp_spl_id LIKE mvke-zzjp_spl_id, " Sample internal order
      END OF t_mdata.
Internal table for Mara Table
DATA: BEGIN OF t_mara OCCURS 0,
      matnr LIKE mara-matnr, " material Number
      vpsta LIKE mara-vpsta, " Maintenance status of complete material
      pstat like mara-pstat, " Maintenance status
      END OF t_mara.
Internal table for Material Master View Selection Screens
DATA: BEGIN OF t_bildtab OCCURS 0.
        INCLUDE STRUCTURE mbildtab.
DATA: END OF t_bildtab.
internal table for T_bildtab
DATA: t_bildtab_dup LIKE t_bildtab OCCURS 0 WITH HEADER LINE.
*Work area for T_bildtab internal table(Views Selection)
DATA: BEGIN OF w_data,
      flag1 type c,
      anzd70 TYPE i,
      field1(20) type c,
      field2(20) type c,
      field3(20) type c,
      field4(20) type c,
      count(2) TYPE c,
      END OF w_data.
            Main Processing                           *
START-OF-SELECTION.
Store data from file into internal table
PERFORM f_uplaod_data.
Transfer the uploaded data into t_mdata internal Table
PERFORM f_process_data.
Selecting The views based on Material number
PERFORM f_view_list.
Open a BDC Session
PERFORM f_bdc_open.
*Selecting the fields from mara table
SELECT matnr
         vpsta
         pstat
    FROM mara
INTO TABLE t_mara
FOR ALL ENTRIES IN t_mdata
WHERE matnr = t_mdata-matnr.
SORT t_mara BY matnr.
SORT t_mdata BY matnr.
Transfer the uploaded data into BDCDATA structure
PERFORM f_process_bdc.
Close The BDC Session
PERFORM f_close_group.
*&      Form F_VIEW_LIST                                             *
         Routine to used for Calling the function module            *
          Selection_views_find                                      *
FORM f_view_list.
CALL FUNCTION 'SELECTION_VIEWS_FIND'
       EXPORTING
            bildsequenz     = c_seq_code
            pflegestatus    = c_viewlist
       TABLES
            bildtab         = t_bildtab
       EXCEPTIONS
            call_wrong      = 1
            empty_selection = 2
            OTHERS          = 3.
IF sy-subrc <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " F_VIEW_LIST
*&      Form f612_view_sort                                          *
Routine to used for Selecting The views based on Material Number *
FORM f612_view_sort.
t_bildtab_dup[] = t_bildtab[].
Reading the Internal table t_mara
READ TABLE t_mara WITH KEY matnr = t_mdata-matnr.
TRANSLATE t_mara-pstat USING ' $'.
CLEAR: w_data-flag1, w_data-anzd70.
LOOP AT t_bildtab_dup.
    IF t_bildtab_dup-pstat CA t_mara-pstat.
      w_data-anzd70 = w_data-anzd70 + 1.
      IF t_bildtab_dup-kzanz IS INITIAL.
        t_bildtab_dup-kzanz = 'X'.
        w_data-flag1 = 'X'.
        MODIFY t_bildtab_dup.
      ENDIF.
    ELSE.
      IF NOT t_bildtab_dup-kzanz IS INITIAL.
        CLEAR t_bildtab_dup-kzanz.
        w_data-flag1 = 'X'.
        MODIFY t_bildtab_dup.
      ENDIF.
    ENDIF.
ENDLOOP.
TRANSLATE t_mara-pstat USING '$ '.
IF NOT w_data-flag1 IS INITIAL.
    SORT t_bildtab_dup BY kzanz DESCENDING idxbd ASCENDING.
ENDIF.
*Reading The internal table for T_bildtab_dup
READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
IF t_bildtab_dup-kzanz = 'X'.
    WRITE sy-tabix TO w_data-count.
    w_data-count = w_data-count + 2.
    IF w_data-anzd70 > 18.
      w_data-count = w_data-count - 18.
    ENDIF.
    CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field1.
    CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field2.
ENDIF.
READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
IF t_bildtab_dup-kzanz = 'X'.
    WRITE sy-tabix TO w_data-count.
    IF w_data-anzd70 > 18.
          w_data-count = w_data-count + 2.
      w_data-count = w_data-count - 18.
    ENDIF.
    CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field3.
    CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field4.
ENDIF.
ENDFORM.                    " f612_view_sort
*&      Form f_uplaod_data                                           *
Routine to used for Uploading the data from file to Internal table *
FORM f_uplaod_data.
CALL FUNCTION 'WS_UPLOAD'
       EXPORTING
            filename                = g_file
            filetype                = 'DAT'
       TABLES
            data_tab                = t_delim
       EXCEPTIONS
            conversion_error        = 1
            file_open_error         = 2
            file_read_error         = 3
            invalid_type            = 4
            no_batch                = 5
            unknown_error           = 6
            invalid_table_width     = 7
            gui_refuse_filetransfer = 8
            customer_error          = 9
            OTHERS                  = 10.
IF sy-subrc <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF t_bpcs IS INITIAL.
    LOOP AT t_delim.
      SPLIT t_delim-text AT ',' INTO t_bpcs-matnr
                                     t_bpcs-dosage
                                     t_bpcs-appearance
                                     t_bpcs-idcode
                                     t_bpcs-prostformno
                                     t_bpcs-weitab
                                     t_bpcs-uom1
                                     t_bpcs-uom2
                                     t_bpcs-carsize
                                     t_bpcs-cassize
                                     t_bpcs-rupqty
                                     t_bpcs-abvname.
      APPEND t_bpcs.
    ENDLOOP.
ENDIF.
ENDFORM.                    " f_uplaod_data
*&      Form F_BDC_OPEN
      Routine to create BDC Session to be processed
FORM f_bdc_open.
CALL FUNCTION 'BDC_OPEN_GROUP'
       EXPORTING
            client              = sy-mandt
            group               = c_group
            keep                = c_keep
            user                = sy-uname
       EXCEPTIONS
            client_invalid      = 1
            destination_invalid = 2
            group_invalid       = 3
            group_is_locked     = 4
            holddate_invalid    = 5
            internal_error      = 6
            queue_error         = 7
            running             = 8
            system_lock_error   = 9
            user_invalid        = 10
            OTHERS              = 11.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
MESSAGE S000 WITH 'Batch input session is created successfully'(T02).
ENDIF.
ENDFORM.                    " F_BDC_OPEN
*&      Form F_PROCESS_BDC
      Processing of BDCDATA Structure
FORM f_process_bdc.
LOOP AT t_mdata.
    PERFORM f612_view_sort.
    PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0060'.
    PERFORM f_bdc_field USING 'BDC_CURSOR'
                                  'RMMG1-MATNR'.
    PERFORM f_bdc_field USING 'BDC_OKCODE'
                                  '=AUSW'.
    PERFORM f_bdc_field USING 'RMMG1-MATNR'
                                  t_mdata-matnr.
    PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0070'.
    PERFORM f_bdc_field USING 'BDC_CURSOR'
                              'MSICHTAUSW-DYTXT(01)'.
    IF w_data-anzd70 > 18.
      PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                  '=P+'.
      PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0070'.
      PERFORM f_bdc_field USING 'BDC_OKCODE' '/00'.
    ENDIF.
reading the t_bildtab internal table
    READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
    IF t_bildtab_dup-kzanz = 'X'.
      PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                    w_data-field1.
      PERFORM f_bdc_field       USING w_data-field2 'X'.
      g_flag = 'X'.
    ENDIF.
reading the t_bildtab internal table
    READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
    IF sy-subrc EQ 0.
      g_flag = 'X'.
    ENDIF.
    IF t_bildtab_dup-kzanz = 'X'.
      PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                    w_data-field3.
      PERFORM f_bdc_field       USING w_data-field4 'X'.
      g_flag1 = 'X'.
    ENDIF.
    IF g_flag = 'X' AND g_flag1 = 'X'.
      PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0080'.
      PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                    'RMMG1-VTWEG'.
      PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                    '=ENTR'.
      PERFORM f_bdc_field       USING 'RMMG1-WERKS'
                                    c_werks.
      PERFORM f_bdc_field       USING 'RMMG1-VKORG'
                                    c_vkorg.
      PERFORM f_bdc_field       USING 'RMMG1-VTWEG'
                                    c_vtweg.
      CLEAR g_flag.
      CLEAR g_flag1.
    ELSE.
      IF g_flag = 'X'.
        PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0080'.
        PERFORM f_bdc_field       USING 'RMMG1-WERKS'
                                    c_werks.
        PERFORM f_bdc_field      USING 'BDC_OKCODE' '/00'.
      ELSE.
        IF g_flag1 = 'X'.
          PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0080'.
          PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                        'RMMG1-VTWEG'.
          PERFORM f_bdc_field       USING 'RMMG1-WERKS'
                                      c_werks.
          PERFORM f_bdc_field       USING 'RMMG1-VKORG'
                                        c_vkorg.
          PERFORM f_bdc_field       USING 'RMMG1-VTWEG'
                                        c_vtweg.
          PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                         '=ENTR'.
        ENDIF.
      ENDIF.
    ENDIF.
*Processing of SCM View
    PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '4000'.
    PERFORM f_bdc_field       USING 'BDC_CURSOR' 'MARC-ZZJP_DOS_FRM'.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_DOS_FRM'
                                  t_mdata-zzjp_dos_frm.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_APRN'
                                  t_mdata-zzjp_aprn.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_CON_ID'
                                  t_mdata-zzjp_con_id.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_NYU_SOP'
                                  t_mdata-zzjp_nyu_sop.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_WEI_TAB'
                                  t_mdata-zzjp_wei_tab.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_CAR'
                                  t_mdata-zzjp_car.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_CAS'
                                  t_mdata-zzjp_cas.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_CAR_SIZE'
                                  t_mdata-ZZJP_CAR_SIZE.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_CAS_SIZE'
                                  t_mdata-ZZJP_CAS_SIZE.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_RUPQTY'
                                   t_mdata-ZZJP_RUPQTY.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_BIO'
                                  t_mdata-zzjp_bio.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_ITF'
                                  t_mdata-zzjp_itf.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_INIT_LS'
                                  t_mdata-zzjp_init_ls.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_RE1'
                                  t_mdata-zzjp_re1.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_RE2'
                                  t_mdata-zzjp_re2.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_RE3'
                                  t_mdata-zzjp_re3.
    PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
*Processing of SD View
    PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '4000'.
    PERFORM f_bdc_field       USING 'BDC_CURSOR' 'MVKE-ZZJP_PRO_ID'.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_PRO_ID'
                                  t_mdata-zzjp_pro_id.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_BU_ID'
                                  t_mdata-zzjp_bu_id.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_ABV_NAME'
                                  t_mdata-zzjp_abv_name.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_ABV_ID1'
                                  t_mdata-zzjp_abv_id1.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_ABV_ID2'
                                  t_mdata-zzjp_abv_id2.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_SPL_ID'
                                  t_mdata-zzjp_spl_id.
    PERFORM f_bdc_field      USING 'BDC_OKCODE' '/00'.
    PERFORM f_bdc_dynpro      USING 'SAPLSPO1' '0300'.
    PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                  '=YES'.
perform f_bdc_insert.
REFRESH T_BDCDATA.
ENDLOOP.
ENDFORM.                    " F_PROCESS_BDC
*&      Form f_bdc_dynpro
p_prog is the program name to which data is passed                *
p_dyno is the screen number to which the data is passed
    Routine for populating the BDCDATA structure with the
    Screen related information
FORM f_bdc_dynpro USING    p_prog
                           p_dyno.
t_bdcdata-program = p_prog.
t_bdcdata-dynpro   = p_dyno.
t_bdcdata-dynbegin = 'X'.
APPEND t_bdcdata.
CLEAR t_bdcdata.
ENDFORM.                    " F_bdc_dynpro
*&      Form F_BDC_FIELD
      p_fnam is the field name to which value is passed
      p_fval is the field value which is passed
   p_fnam is the field name to which value is passed
   p_fval is the field value which is passed
FORM f_bdc_field USING    p_fnam
                          p_fval.
t_bdcdata-fnam = p_fnam.
t_bdcdata-fval = p_fval.
APPEND t_bdcdata.
CLEAR t_bdcdata.
ENDFORM.                    " F_bdc_field
*&      Form F_PROCESS_DATA                                          *
     Routine to used for moving data from T_bpcs internal table to *
     t_mdata Internal Table                                         *
FORM f_process_data.
LOOP AT t_bpcs.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
         EXPORTING
              input = t_bpcs-matnr
         IMPORTING
              output = t_mdata-matnr.
    MOVE t_bpcs-dosage TO t_mdata-zzjp_dos_frm.
    MOVE t_bpcs-appearance TO t_mdata-zzjp_aprn.
    MOVE t_bpcs-idcode TO t_mdata-zzjp_con_id.
    MOVE t_bpcs-prostformno TO t_mdata-zzjp_nyu_sop.
    MOVE t_bpcs-weitab TO t_mdata-zzjp_wei_tab.
    MOVE c_blank TO t_mdata-zzjp_bio.
    MOVE c_blank TO t_mdata-zzjp_itf.
    MOVE t_bpcs-uom1 TO t_mdata-zzjp_car.
    MOVE t_bpcs-uom2 TO t_mdata-zzjp_cas.
    MOVE t_bpcs-carsize TO t_mdata-zzjp_car_size.
    MOVE t_bpcs-cassize TO t_mdata-zzjp_cas_size.
    MOVE t_bpcs-rupqty TO t_mdata-zzjp_rupqty.
    MOVE c_intls TO t_mdata-zzjp_init_ls.
    MOVE c_blank TO t_mdata-zzjp_re1.
    MOVE c_blank TO t_mdata-zzjp_re2.
    MOVE c_blank TO t_mdata-zzjp_re3.
    MOVE c_blank TO t_mdata-zzjp_pro_id.
    MOVE c_blank TO t_mdata-zzjp_bu_id.
    MOVE t_bpcs-abvname TO t_mdata-zzjp_abv_name.
    MOVE c_blank TO t_mdata-zzjp_abv_id1.
    MOVE c_blank TO t_mdata-zzjp_abv_id2.
    MOVE c_blank TO t_mdata-zzjp_spl_id.
    APPEND t_mdata.
ENDLOOP.
ENDFORM.                    " F_PROCESS_DATA
*&      Form f_bdc_close
      Routine to close the BDC Session
FORM f_close_group.
CALL FUNCTION 'BDC_CLOSE_GROUP'
       EXCEPTIONS
            not_open    = 1
            queue_error = 2
            OTHERS      = 3.
IF sy-subrc <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " f_close_group
*&      Form f_bdc_insert
     routine to input batch data into the Transaction MM02 from the
     session created
FORM f_bdc_insert.
CALL FUNCTION 'BDC_INSERT'
         EXPORTING
              tcode            = c_tcode
         TABLES
              dynprotab        = t_bdcdata
         EXCEPTIONS
              internal_error   = 1
              not_open         = 2
              queue_error      = 3
              tcode_invalid    = 4
              printing_invalid = 5
              posting_invalid = 6
              OTHERS           = 7.
    IF sy-subrc <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
ENDFORM.                    " f_bdc_insert
Reward Points if it is useful
Thanks
Seshu

How to maintain PO Header Text entry in table T166K for different PO Type

Hi,
Can anyone tell me if there is a config transaction ( or path ) to maintain PO Header Text entry in table T166K for different PO Types
Thanks
Shrikant

Spro->Material Management->Purchasing->Purchase Order->Texts for Purchase Orders.
There are 4 config setting to do for this.
Read information text.
regards,nishant
please reward if this helps

How to maintain PO Header Text entry in table T166K for different PO Types

Hi,
Can anyone tell me if there is a config transaction ( or path ) to maintain PO Header Text entry in table T166K for different PO Types
Thanks
Shrikant

Resolved.

FAGLL03- Entry Date showing blank in the report

Hi Gurus,
We have observed that the field "Entry Date" in the GL report FAGLL03 is not showing entry dates of documents posted . We are using ECC6.0 and CUPDT field is already there in the report FAGLL03.
Need advise how to achieve this? is there any sap note available for the same
Regards,
Vijay

Thanks for your quick responce.
I have one question.
The standard layout of report FAGLL03 is having the field ENTRY DATE.
Still is it require to maintain as special field in customization under below path? to get values(i.e. Entray Dates) in the report.
Path is: SPRO->Financial Accounting (New)->General Ledger Accounting (New)->Master Data->G/L Accounts->Line Items
->Define Special Fields for Line Item Display.
BKPF-CUPDT-Entry Date
Regards
Vijay.
Edited by: Vijaya kumar on Jun 24, 2010 7:19 AM

Data source creation for service contract configuration

Hello all,
I have to create a data source for extraction of service contract configuration. I think this could work like data source creation for sales order creation, but I don't know waht to enter in transaction CTBW. Anyone here has done this previously? Any pointers and/or the strategy you've used will be useful.
Kind regards,
Simon

Hi,
If you are asking about "CRM sales contracts", The following help gives the info about standard ODS and Datasource.
http://help.sap.com/saphelp_nw2004s/helpdata/en/d5/9fcd3b869e7d72e10000000a11402f/frameset.htm
With rgds,
Anil Kumar Sharma .P

Transfer Custom OM Infotype data through ALE for HRMD_ABA Message type

Hello Folks,
I have created a Custom OM Infotype.When i run the PFAL transaction. All the standard infotype data is getting filled, but i dont see custom infotype data getting filled.
Example: HRP9001 is the custom infotype.
Please let me know the step by step process to populate the Custom infotype data in ALE Transfer.
Thanks & Regards,
Nishanth Kumar

I think function module RH_MASTER_IDOC_DISTRIBUTE_HRMD shows some odd behaviour. It calls EDI_DOCTYPS_OF_MESTYP, which returns the name of the extension in an internal table named "doctyps". But later on, function module MASTER_IDOC_DISTRIBUTE is called with a structure "f_idoc_control". In this structure, the field "cimtyp" should hold the name of the extension, but it NEVER gets filled, although the value is present in doctyps-cimtyp.
So what I have done, is to activate userexit #004, which is called just before MASTER_IDOC_DISTRIBUTE and modifies structure f_idoc_control, if desired.
Call transaction CMOD and create a project in a non-SAP namespace: Zxxxx. The enhancement we need is "RHALE001" (HR-CA: Enhancement for ALE functionality in HR). One of its components is EXIT_SAPLRHA0_004, which consists of include ZXHALU08. In this include I called EDI_DOCTYPS_OF_MESTYP again to fill f_idoc_control-cimtyp.
Here is my code for include ZXHALU08
DATA: z_doctyps TYPE STANDARD TABLE OF edidocs WITH HEADER LINE.
CALL FUNCTION 'EDI_DOCTYPS_OF_MESTYP'
EXPORTING
    mestyp         = f_idoc_control-mestyp
TABLES
    doctyps        = z_doctyps
EXCEPTIONS
    invalid_mestyp = 1
    OTHERS         = 2.
IF sy-subrc = 0.
LOOP AT z_doctyps.
    f_idoc_control-cimtyp = z_doctyps-cimtyp.
ENDLOOP.
ENDIF.
Hope this helps

How to insert long text data in oracle for LONG column type??

Anybody who can tell me what is best way to store long text (more than 8k) in Oralce table.
I am using Long datatype for column but it still doenst let me insert longer strings.
Also I am using ODP.Net.
Anybody with a good suggestion???
Thanks in advance

Hi,
Are you getting an error? If so, what?
This works for me..
Greg
create table longtab(col1 varchar2(10), col2 long );
using System;
using System.Data;
using Oracle.DataAccess.Client;
using Oracle.DataAccess.Types;
using System.Text;
public class longwrite
public static void Main()
// make a long string
StringBuilder sb = new StringBuilder();
for (int i=0;i<55000;i++)
sb.Append("a");
sb.Append("Z");
string indata = sb.ToString();
Console.WriteLine("string length is {0}",indata .Length);
// insert into database
OracleConnection con = new OracleConnection("user id=scott;password=tiger;data source=orcl");
con.Open();
OracleCommand cmd = new OracleCommand();
cmd.CommandText = "insert into longtab values(1,:longparam)";
cmd.Connection = con;
OracleParameter longparam = new OracleParameter("longparam",OracleDbType.Long,indata .Length);
longparam.Direction = ParameterDirection.Input;
longparam.Value = indata ;
cmd.Parameters.Add(longparam);
cmd.ExecuteNonQuery();
Console.WriteLine("insert complete");
//now retrieve it
cmd.CommandText = "select rowid,col2 from longtab where col1 = 1";
OracleDataReader reader = cmd.ExecuteReader();
reader.Read();
string outdata = (string)reader.GetOracleString(1);
Console.WriteLine("string length is {0}",outdata.Length);
//Console.WriteLine("string is {0}",outdata);
reader.Close();
con.Close();
con.Close();
}

BAdI/method for limiting Delivery type list for webshop

Hello everyone,
I need your help: I have requirement is to limit some Deliver types when ordering in the b2b webshop (webshop only not others). I'm searching for a BAdI (I don't want to hardcode in order.jsp) and debuging/looking into CRM_ISA_BASKET_HEAD. Can someone please tell me which BAdI and method? or any suggestions?
Thanks, Jin

Hi Freda,
Check CRM_SHIPPING_MAINTAIN_OW or CRM_SHIPPING_CHANGE_OW.
hope it helps....
Regards,
Anil.

Entry date blank in FAGLL03

Hi All,
New GL is active,
In FAGLL03, the entry date is blank for all the documents,
i have to click on each documents and see the entry date of each. But it should show the entry date in FAGLL03 itself.
Appreciate your quick response,
Thank you,
Vidya

Hi Vidya,
In the FAGLL03 you can display data from different tables and different
selection logics.
1st
If an account is 'OpenItem/LineItem' managed, the displayed data is
selected in a Join of the index tables BSIS/BSAS and the NewG/L line
item table.
2nd
If an account has the 'Clearing Specific to ledger Groups' se, the
displayed data is selected in a join of the tables FAGLBSIS/FAGLBSAS
and the NewG/L line item table.
3rd
In the case of an account which is NOT 'OpenItem/LineItem' managed, th
displayed data is selected from BKPF, NewG/L line item table and the
BSEG table.
Referring to your case, the ledger group is only available in the
BKPF and the FAGLBS*S tables.
The CPUDT is even only available in the BKPF.
As all the different logics to select use the same 'fieldcatalog' to
display the data, there might be some fields which are not filled
in relation to the master data settings of the accounts.
To avoid this, you should define the two fields as special fields:
BKPF LDGRP
BKPF CPUDT
This can be done in the IMG path:
Financial Accounting (New)
General Ledger Accounting (New)
    Master Data
      G/L Accounts
        Line Items
          Define Special Fields for Line Item Display
After you defined and stored them there, please also run the report
BALVBUFDEL.
About the special fields in general, refer to the 984305.
I hope this can help further.
Kind Regard,
Fernando Evangelista

Modification in ML87 upload program to change contract type

Hi Experts.
I need your help regarding ML87 transaction code. I want to change contract type for uploading prog. Currently I am uploading for default contract type XYZ1 and now i want to change it as XY as new default contract so can you tell me the process to make changes for contract type .
Thanks
Regards
Rajas01

Hi, use LSMW, Import method - recording

"Mfr part profile" setup for various material types

Hello All,
I'd like to set a default value of "Mfr part profile" field ("Purchasing" screen in 01 Std industry sequence) different for various material types. Currently I have 2 entries maintained in MaterialsManagement>Purchasing>MaterialMaster>DefineManufacturerPartProfile (one with AMPL management and one without). I'd like to get the first entry set as default for HAWA material type and the 2nd for ROH.
Thanks in advance for your help on this!
Jacek

Hi Troinski,
Its not possible in SAP, you can create Z transaction for create material wth dafult values.
Thanks
Bala

Config of contract type

Anyone knows the configuration for the contract type.how to config the contract thru SPRO.
I wanna to config the contract types with repect to sales area.
plz send it urgently.......

Hi,
Contract types are configured through Tcode VOV8 (Sales document types maintaince).
Once you configure the document type,assign this contract type to your desired sales area in Assignment of document types to sales area.
Maintain the proper copy control for furthur processing.
Reward points if useful
Regards,
Amrish Purohit

Sourcefire - Contract Type Name

What are the name of Sourefoire contract types ?
Normal IPS license required IPS contract like SUSA. Please advise if there are some Sourcefire specific contract type names for SF IPS, URL Filtering, and also a Malware and application control license. Also, if there is a certain contract type which require special handling, please describe.
Thank you,
Haruka

Marvin, thank you. I am looking for "service contract type". What I mean by "service contract type" can be found in this spread sheet, column D. Sourcefire related contract types are not listed on this master file yet.
https://ecm-link.cisco.com/ecm/view/objectId/090dcae18132b8e5/versionLabel/CURRENT
Based on the topic search, it seems "ASAFP" was one of the service contract types for sourcefire. Do you have entire list for service contract type?
Thank you,
Haruka

I have used SAP doc mgmt for years. We copied a client and now when I configure a Class to my DMS DIR and go to CV01n Additional Data NONE of the characteristic entry boxes show up. Additional Data is blank.

I have used SAP doc mgmt for years. We copied a client and now when I configure a Class to my DMS DIR and go to CV01n Additional Data NONE of the characteristic entry boxes show up. Additional Data is blank.
It appears there must be some high level setting missing in the client. I have checked all authorizations and cannot find a difference between this client and all of the other clients we have. Only this one client does not show the class characteristics in the Additional Data tab.
Any ideas of why this standard function is not working). It does not matter which DIR I config the 017 class to, nothing shows on Additional Data.

Hi,
The issue is resolved. We are working in a sandbox with Class configuration on a DMS issue related to standard class 017. There are no standard settings in SPRO - Cross-Application Components | Maintain Object Types and Class Types | for the object type DRAW that will allow "auto-populating" characteristic values as we do with VC class 300.
For whatever reason DRAW and class 017 are not configured by SAP in the same manner as class 300 for example.
We made a config entry for DRAW Class 017 VBAP. Let's just say the system did not like that.
We are exploring other options.

Entry date in blank for limited Contract Type

Similar Messages

Maybe you are looking for