Problem with direct input program while uploading data into database

TABLES:  BGR00,                        " Mappensatz
         BMM00,                        " MM01/MM02  BTCI-Kopfdaten
         BMMH1,                        " MM01/MM02 Hauptdaten
         BMMH2,                        " Länderdaten (Steuern)
         BMMH3,                        " Prognosewerte
         BMMH4,                        " Verbrauchswerte
         BMMH5,                        " Kurztexte
         BMMH6,                        " Mengeneinheiten
         BMMH7,                        " Langtexte
         BMMH8.                        " Referentielle EAN's
       Satztypen
DATA:    MAPPENSATZ  LIKE BMM00-STYPE VALUE '0',
         KOPFSATZ    LIKE BMM00-STYPE VALUE '1',
         HAUPTSATZ   LIKE BMM00-STYPE VALUE '2',
         KUN_SATZ    LIKE BMM00-STYPE VALUE 'Z',
         LANDSATZ    LIKE BMM00-STYPE VALUE '3',
         PROGSATZ    LIKE BMM00-STYPE VALUE '4',
         VERBSATZ    LIKE BMM00-STYPE VALUE '5',
         KTEXTSATZ   LIKE BMM00-STYPE VALUE '6',
         MESATZ      LIKE BMM00-STYPE VALUE '7',
         TEXTSATZ    LIKE BMM00-STYPE VALUE '8',
         EANSATZ     LIKE BMM00-STYPE VALUE '9'.
Common Data Bereich fuer die extern aufgerufenen Routinen
       Initialstrukturen
DATA:  BEGIN OF COMMON PART RMMMBIMY.
DATA:    BEGIN OF I_BMM00.
           INCLUDE STRUCTURE BMM00.    " Kopfdaten
DATA:    END OF I_BMM00.
DATA:    BEGIN OF I_BMMH1.
           INCLUDE STRUCTURE BMMH1.    " Haupdaten
DATA:    END OF I_BMMH1.
DATA:    BEGIN OF I_BMMH2.
           INCLUDE STRUCTURE BMMH2.    " Länderdaten
DATA:    END OF I_BMMH2.
DATA:    BEGIN OF I_BMMH3.
           INCLUDE STRUCTURE BMMH3.    " Prognosewerte
DATA:    END OF I_BMMH3.
DATA:    BEGIN OF I_BMMH4.
           INCLUDE STRUCTURE BMMH4.    " Verbrauchswerte
DATA:    END OF I_BMMH4.
DATA:    BEGIN OF I_BMMH5.
           INCLUDE STRUCTURE BMMH5.    " Kurztexte
DATA:    END OF I_BMMH5.
DATA:    BEGIN OF I_BMMH6.
           INCLUDE STRUCTURE BMMH6.    " Mengeneinheiten
DATA:    END OF I_BMMH6.
DATA:    BEGIN OF I_BMMH7.
           INCLUDE STRUCTURE BMMH7.    " Textzeilen
DATA:    END OF I_BMMH7.
DATA:    BEGIN OF I_BMMH8.
           INCLUDE STRUCTURE BMMH8.    " Referentielle EAN's
DATA:    END OF I_BMMH8.
DATA:  END OF COMMON PART.
DATA: WA LIKE TEDATA-DATA.
       Einzelfelder
DATA:    GROUP_COUNT(6) TYPE C,    " Anzahl Mappen
         TRANS_COUNT(6) TYPE C,    " alte Definition für rmmmbim0
         SATZ_COUNT  LIKE MUEB_REST-TRANC, " Trans.zähler neu
         H_IND_COUNT LIKE MUEB_REST-D_IND, " Index welches Feld zurücks.
         SATZ2_COUNT(6) TYPE C.    " Anz. Sätze je Trans. ohne Kopfsatz
DATA:    XEOF(1)          TYPE C,  " X=End of File erreicht
         XHAUPTSATZ_EXIST TYPE C,  " X=Hauptsatz zum Kopf exi.
         NODATA(1)        TYPE C.  " kein BI für dieses Feld
mk/15.08.94:
DATA:    GROUP_OPEN(1)  TYPE C.             " X=Mappe schon geöffnet
*eject
       Konstanten
DATA:    C_NODATA(1)    TYPE C VALUE '/'.   " Default für NODATA
DATA:    MATNR_ERW     LIKE MARA-MATNR  VALUE '0                 '.
DATA:    MATNR_ERW_INT LIKE MARA-MATNR.  "internal sight of '0      '
DATA:    MATNR_LAST    LIKE MARA-MATNR.  "Material number
mk/11.08.94 2.1H:
If this flag is initial, the database updates will be done directly
during background maintenance instead of using a separate update
task. (no usage of this flag in dialogue mode!)
DATA: DBUPDATE_VB(1) VALUE ' '.       "note 306628
data: matsync type mat_sync. "wk/99a no update in dialog if called
***INCLUDE ZMUSD070.
TABLES: MARA,                          "Material Master: General Data
        MARC,                          "Material Master: C Segment
        MARD,                          "Material Master: St Loc/Batch
        MBEW,                          "Material Valuation
        MVKE,                          "Material Master: Sales Data
        MLGN,                          "Material Data per Whse Number
        MLAN,                          "Tax Classification: Material
        T001W,                         "Plants/Branches
        TBICU.
DATA: BEGIN OF VALUTAB OCCURS 0.
        INCLUDE STRUCTURE RSPARAMS.
DATA: END OF VALUTAB.
DATA: BEGIN OF VARTECH.
        INCLUDE STRUCTURE VARID.
DATA: END OF VARTECH.
DATA: PARMS LIKE ZXXDCONV.
DATA: REC_COUNT      TYPE  I,
      REC_COUNT_BAD  TYPE  I,
      ZJOBID         LIKE  TBIZU-JOBID,
      ZJOBCOUNT      LIKE  TBIZU-JOBCOUNT,
      ZMATNR         LIKE  MARA-MATNR,
      ZTEXT(80)      TYPE  C.
CONSTANTS: LIT_ZERO(18)  TYPE  C            VALUE '000000000000000000',
           LIT_CHAR      TYPE  C            VALUE '_',
           LIT_CREATE    LIKE  BMM00-TCODE  VALUE 'MM01',
           LIT_CHANGE    LIKE  BMM00-TCODE  VALUE 'MM02',
           LIT_CHECK(1)  TYPE  C            VALUE 'X'.
DATA:  BEGIN OF INP_DATA OCCURS 0,
         MATNR(18)  TYPE C,            " Material code
         UMREN(6)   TYPE C,            " Denominator
         MEINH(3)   TYPE C,            " Alternate UOM
         UMREZ(6)   TYPE C,            " Numerator
       END OF INP_DATA.
*eject
SELECTION-SCREEN BEGIN OF BLOCK INOUT WITH FRAME TITLE TEXT-001.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT (13) TEXT-004.
PARAMETERS:     P_PC        RADIOBUTTON GROUP SRC DEFAULT 'X'.
SELECTION-SCREEN COMMENT (6) TEXT-005.
PARAMETERS:     P_UNIX      RADIOBUTTON GROUP SRC.
SELECTION-SCREEN COMMENT (6) TEXT-006.
PARAMETERS:     P_DS_TYP    LIKE     ZXXDCONV-DS_TYP
                               DEFAULT 'ASC'.
SELECTION-SCREEN END OF LINE.
*SELECT-OPTIONS: S_PATH      FOR      PARMS-PATH
                              NO INTERVALS
                              LOWER CASE.
PARAMETERS:  P_PATH TYPE RLGRAP-FILENAME.
PARAMETERS:     P_HDRLIN   LIKE     ZXXDCONV-HDR_LINES
                               DEFAULT 0,
                P_JOBNAM   LIKE     TBICU_S-JOBNAME
                               MEMORY ID BM1,
                P_DI_EXE    AS       CHECKBOX
                               DEFAULT  LIT_CHECK,
                P_MAPPE     LIKE     BGR00-GROUP
                               DEFAULT  'MRP_UOM_LOAD'
                               NO-DISPLAY.
SELECTION-SCREEN END OF BLOCK INOUT.
*eject
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_PATH.
  CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
       EXPORTING
            PROGRAM_NAME  = SYST-REPID
            DYNPRO_NUMBER = SYST-DYNNR
            FIELD_NAME    = 'P_PATH'
       CHANGING
           FILE_NAME     = S_PATH-LOW
            FILE_NAME     = P_PATH
       EXCEPTIONS
            MASK_TOO_LONG = 1
            OTHERS        = 2.
AT SELECTION-SCREEN.
Set up parameter record
  PARMS-UNIX      = P_UNIX.
  PARMS-PC        = P_PC.
  PARMS-DS_TYP    = P_DS_TYP.
  PARMS-JOBNAME   = P_JOBNAM.
  PARMS-MAPPE     = P_MAPPE.
  PARMS-HDR_LINES = P_HDRLIN.
*eject
       Main Processing Routine                                       *
START-OF-SELECTION.
Initialization
  PERFORM 0000_HOUSEKEEPING.
Initialize transaction data in I_BM00
PERFORM 0500_INIT_BMM00.
Process input files
SORT S_PATH BY SIGN OPTION LOW.
     MOVE S_PATH-LOW TO PARMS-PATH.
      MOVE P_PATH TO PARMS-PATH.
LOOP AT S_PATH.
   AT NEW LOW.
      CLEAR   INP_DATA.
     REFRESH INP_DATA.
Read source data into internal table
      PERFORM 1000_GET_SOURCE_DATA TABLES INP_DATA.
Processs each record in internal table
      ZTEXT    = TEXT-007.
      ZTEXT+13 = PARMS-DS_NAME.
      PERFORM 4000_PROGRESS_INDICATOR USING ZTEXT.
Initialize transaction data in I_BM00
  PERFORM 0500_INIT_BMM00.
      LOOP AT INP_DATA.
Reset tables for each record
        BMM00              = I_BMM00.
        BMMH1              = I_BMMH1.
        BMMH6              = I_BMMH6.
Load structures with data
        MOVE-CORRESPONDING INP_DATA TO BMM00.
        PERFORM 2000_WRITE_OUTPUT USING BMM00.
        MOVE-CORRESPONDING INP_DATA TO BMMH1.
        PERFORM 2000_WRITE_OUTPUT USING BMMH1.
        MOVE-CORRESPONDING INP_DATA TO BMMH6.
        PERFORM 2000_WRITE_OUTPUT USING BMMH6.
        REC_COUNT = REC_COUNT + 1.
      ENDLOOP.
   ENDAT.
ENDLOOP.
  IF  REC_COUNT GT 0
  AND P_DI_EXE  EQ LIT_CHECK.
    PERFORM 3000_START_DI_JOB.
  ENDIF.
WRITE: / TEXT-008,
           REC_COUNT.
  PERFORM 9000_END_OF_JOB.
*eject
Include containing common routines used by direct input programs
  INCLUDE ZMUSD071.
*eject
      FORM 0500_INIT_BMM00                                          *
      Initialize I_BMM00 with transaction code and views selected   *
FORM 0500_INIT_BMM00.
***this changes done by samson**
if not inp_data[] is initial.
select single matnr from mara INTO ZMATNR where matnr = inp_data-matnr.
if sy-subrc = 0.
  I_BMM00-TCODE = LIT_CHANGE.
Basic data
  I_BMM00-XEIK1  = LIT_CHECK.
else.
  I_BMM00-TCODE = LIT_CREATE.
Basic data
  I_BMM00-XEIK1 = LIT_CHECK.
endif.
endif.
**this changes above done by samson**
Transaction code
I_BMM00-TCODE = LIT_CHANGE.
Basic data
I_BMM00-XEIK1  = LIT_CHECK.
ENDFORM.
INCLUDE ZMUSD069.
*eject
      FORM 0000_HOUSEKEEPING                                        *
      Initialization routines                                       *
FORM 0000_HOUSEKEEPING.
  PERFORM 0010_LDS_NAME.
  PERFORM 0020_DS_NAME.
  PERFORM 0030_OPEN_FILE.
  PERFORM 0040_INIT_STRUCTS.
ENDFORM.
*eject
      FORM 0010_LDS_NAME                                            *
      Obtain logical file name from DI job details                  *
FORM 0010_LDS_NAME.
Check valid job name
  SELECT SINGLE * FROM  TBICU
                  WHERE JOBNAME EQ PARMS-JOBNAME.
  IF SY-SUBRC EQ 0.
    CALL FUNCTION 'RS_VARIANT_VALUES_TECH_DATA'
         EXPORTING
              REPORT               = TBICU-REPNAME
              VARIANT              = TBICU-VARIANT
         IMPORTING
              TECHN_DATA           = VARTECH
         TABLES
              VARIANT_VALUES       = VALUTAB
         EXCEPTIONS
              VARIANT_NON_EXISTENT = 1
              VARIANT_OBSOLETE     = 2
              OTHERS               = 3.
    IF SY-SUBRC EQ 0.
      READ TABLE VALUTAB WITH KEY 'LDS_NAME'.
      MOVE VALUTAB-LOW TO PARMS-LDS_NAME.
    ELSE.
      MESSAGE I001 WITH PARMS-JOBNAME.
      MESSAGE A099.
    ENDIF.
  ELSE.
    MESSAGE I000 WITH PARMS-JOBNAME.
    MESSAGE A099.
  ENDIF.
ENDFORM.
*eject
      FORM 0040_INIT_STRUCTS                                        *
      Initialize structures for direct input records                *
FORM 0040_INIT_STRUCTS.
Start of standard SAP initialization from example program RMMMBIME
*------- Write session record -
  CLEAR BGR00.
  BGR00-STYPE  = MAPPENSATZ.
  BGR00-GROUP  = PARMS-MAPPE.
  BGR00-NODATA = C_NODATA.
  BGR00-MANDT  = SY-MANDT.
  BGR00-USNAM  = SY-UNAME.
  BGR00-START  = BGR00-NODATA.
  BGR00-XKEEP  = BGR00-NODATA.
  PERFORM 2000_WRITE_OUTPUT USING BGR00.
*----- Initialize structures -
  NODATA = BGR00-NODATA.
  PERFORM INIT_STRUKTUREN_ERZEUGEN(RMMMBIMI) USING NODATA.
End of standard SAP initialization from example program RMMMBIME
ENDFORM.
*eject.
      FORM 3000_START_DI_JOB                                        *
      Start direct input job                                        *
FORM 3000_START_DI_JOB.
  ZTEXT = 'Starting '(021).
  ZTEXT+9 = TBICU-JOBNAME.
  PERFORM 4000_PROGRESS_INDICATOR USING ZTEXT.
  CALL FUNCTION 'BI_START_JOB'
       EXPORTING
            JOBID                 = ' '
            JOBTEXT               = TBICU-JOBNAME
            REPNAME               = TBICU-REPNAME
            SERVER                = TBICU-EXECSERVER
            VARIANT               = TBICU-VARIANT
            NEW_JOB               = 'X'
            CONTINUE_JOB          = ' '
            START_IMMEDIATE       = 'X'
            DO_NOT_PRINT          = 'X'
            USERNAME              = SY-UNAME
       IMPORTING
            JOBID                 = ZJOBID
            JOBCOUNT              = ZJOBCOUNT
       EXCEPTIONS
            JOB_OPEN_FAILED       = 1
            JOB_CLOSE_FAILED      = 2
            JOB_SUBMIT_FAILED     = 3
            WRONG_PARAMETERS      = 4
            JOB_DOES_NOT_EXIST    = 5
            WRONG_STARTTIME_GIVEN = 6
            JOB_NOT_RELEASED      = 7
            WRONG_VARIANT         = 8
            NO_AUTHORITY          = 9
            DIALOG_CANCELLED      = 10
            JOB_ALREADY_EXISTS    = 11
            PERIODIC_NOT_ALLOWED  = 12
            ERROR_NUMBER_GET_NEXT = 13
            OTHERS                = 14.
  IF SY-SUBRC EQ 0.
    WRITE: / 'Direct input job'(022), TBICU-JOBNAME, 'started'.
  ELSE.
    WRITE: / 'Direct input failed with return code'(023), SY-SUBRC.
  ENDIF.
FORM 0020_DS_NAME.
  CALL FUNCTION 'FILE_GET_NAME'
       EXPORTING
            CLIENT           = SY-MANDT
            LOGICAL_FILENAME = PARMS-LDS_NAME
            OPERATING_SYSTEM = SY-OPSYS
       IMPORTING
            FILE_NAME        = PARMS-DS_NAME
       EXCEPTIONS
            FILE_NOT_FOUND   = 1
            OTHERS           = 2.
  IF SY-SUBRC NE 0.
    MESSAGE E002 WITH PARMS-LDS_NAME.
    MESSAGE A099.
  ENDIF.
ENDFORM.
*eject
      FORM 0030_OPEN_FILE                                           *
      Open physical file for output                                 *
FORM 0030_OPEN_FILE.
OPEN DATASET PARMS-DS_NAME FOR OUTPUT IN TEXT MODE. "thg191105
  OPEN DATASET PARMS-DS_NAME FOR OUTPUT IN TEXT MODE
                                 encoding default. "thg191105
  IF SY-SUBRC NE 0.
    MESSAGE E003 WITH PARMS-DS_NAME.
    MESSAGE A099.
  ENDIF.
ENDFORM.
*eject
      FORM 1000_GET_SOURCE_DATA                                     *
      Read source data into internal table                          *
-->  INP_DATA   " Name of internal table passed as parameter       *
FORM 1000_GET_SOURCE_DATA TABLES INP_DATA.
  CALL FUNCTION 'Z_FILE_UPLOAD'
       EXPORTING
            UNIX                = PARMS-UNIX
            PC                  = PARMS-PC
            FILETYPE            = PARMS-DS_TYP
            FILENAME            = PARMS-PATH
            HDR_LINES           = PARMS-HDR_LINES
       TABLES
            DATA_TAB            = INP_DATA
       EXCEPTIONS
            CONVERSION_ERROR    = 1
            FILE_OPEN_ERROR     = 2
            FILE_READ_ERROR     = 3
            INVALID_TABLE_WIDTH = 4
            INVALID_TYPE        = 5
            NO_BATCH            = 6
            UNKNOWN_ERROR       = 7
            INVALID_SOURCE      = 8
            OTHERS              = 9.
ENDFORM.
*eject
      FORM 2000_WRITE_OUTPUT                                        *
      Write record in standard SAP structure to UNIX file           *
-->  I_STRUCT   " Name of record passed as parameter               *
*FORM 2000_WRITE_OUTPUT USING I_STRUCT."SRY28NOV05
FORM 2000_WRITE_OUTPUT USING I_STRUCT TYPE ANY.      "SRY28NOV05
   TRANSFER I_STRUCT TO PARMS-DS_NAME.
  IF SY-SUBRC NE 0.
    MESSAGE E004 WITH PARMS-DS_NAME.
    MESSAGE A099.
  ENDIF.
ENDFORM.
*eject
*&      Form  2100_WS_DOWNLOAD
      text                                                           *
-->  p1        text
<--  p2        text
FORM 2100_WS_DOWNLOAD TABLES INP_DATA.
DATA: FILENAME LIKE RLGRAP-FILENAME.   "SRY28NOV05
  DATA: W_FILENAME TYPE STRING.             "SRY28NOV05
  DATA: W_FTYP(10) TYPE C VALUE 'DAT'.      "SRY28NOV05
MOVE PARMS-DS_NAME TO FILENAME.       "SRY28NOV05
  MOVE PARMS-DS_NAME TO W_FILENAME.      "SRY28NOV05
*BEGIN OF BLOCK COMMENT BY SRY28NOV05
CALL FUNCTION 'WS_DOWNLOAD'
      EXPORTING
        BIN_FILESIZE        = ' '
        CODEPAGE            = ' '
           FILENAME            = FILENAME
           FILETYPE            = 'DAT'
        MODE                = ' '
        WK1_N_FORMAT        = ' '
        WK1_N_SIZE          = ' '
        WK1_T_FORMAT        = ' '
        WK1_T_SIZE          = ' '
        COL_SELECT          = ' '
        COL_SELECTMASK      = ' '
   importing
        filelength          =
      TABLES
           DATA_TAB            = INP_DATA
        FIELDNAMES          =
      EXCEPTIONS
           FILE_OPEN_ERROR     = 1
           FILE_WRITE_ERROR    = 2
           INVALID_FILESIZE    = 3
           INVALID_TABLE_WIDTH = 4
           INVALID_TYPE        = 5
           NO_BATCH            = 6
           UNKNOWN_ERROR       = 7
           OTHERS              = 8.
*END OF BLOCK COMMENT BY SRY28NOV05
*BEGIN OF BLOCK ADDED BY SRY28NOV05
  CALL FUNCTION 'GUI_DOWNLOAD'
    EXPORTING
      FILENAME                        = W_FILENAME
      FILETYPE                        = W_FTYP
    TABLES
      DATA_TAB                        = INP_DATA
   EXCEPTIONS
     FILE_WRITE_ERROR                = 1
     NO_BATCH                        = 2
     GUI_REFUSE_FILETRANSFER         = 3
     INVALID_TYPE                    = 4
     NO_AUTHORITY                    = 5
     UNKNOWN_ERROR                   = 6
     HEADER_NOT_ALLOWED              = 7
     SEPARATOR_NOT_ALLOWED           = 8
     FILESIZE_NOT_ALLOWED            = 9
     HEADER_TOO_LONG                 = 10
     DP_ERROR_CREATE                 = 11
     DP_ERROR_SEND                   = 12
     DP_ERROR_WRITE                  = 13
     UNKNOWN_DP_ERROR                = 14
     ACCESS_DENIED                   = 15
     DP_OUT_OF_MEMORY                = 16
     DISK_FULL                       = 17
     DP_TIMEOUT                      = 18
     FILE_NOT_FOUND                  = 19
     DATAPROVIDER_EXCEPTION          = 20
     CONTROL_FLUSH_ERROR             = 21
     OTHERS                          = 22.
  IF SY-SUBRC NE 0.
     MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
           WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
  ENDIF.
*END OF BLOCK ADDED BY SRY28NOV05
ENDFORM.                               " 2100_WS_DOWNLOAD
*eject
      FORM 4000_PROGRESS_INDICATOR                                  *
      Write progress text to status bar                             *
-->  TEXT   " Text passed as parameter                             *
FORM 4000_PROGRESS_INDICATOR USING TEXT.
  CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
       EXPORTING
            PERCENTAGE = 0
            TEXT       = TEXT
       EXCEPTIONS
            OTHERS     = 1.
ENDFORM.
*eject.
      FORM 9000_END_OF_JOB                                          *
      Close files on UNIX                                           *
FORM 9000_END_OF_JOB.
  CLOSE DATASET PARMS-DS_NAME.
ENDFORM.
FORM 1000_GET_SOURCE_DATA TABLES INP_DATA.
  CALL FUNCTION 'Z_FILE_UPLOAD'
       EXPORTING
            UNIX                = PARMS-UNIX
            PC                  = PARMS-PC
            FILETYPE            = PARMS-DS_TYP
            FILENAME            = PARMS-PATH
            HDR_LINES           = PARMS-HDR_LINES
       TABLES
            DATA_TAB            = INP_DATA
       EXCEPTIONS
            CONVERSION_ERROR    = 1
            FILE_OPEN_ERROR     = 2
            FILE_READ_ERROR     = 3
            INVALID_TABLE_WIDTH = 4
            INVALID_TYPE        = 5
            NO_BATCH            = 6
            UNKNOWN_ERROR       = 7
            INVALID_SOURCE      = 8
            OTHERS              = 9.
ENDFORM.
*eject
      FORM 2000_WRITE_OUTPUT                                        *
      Write record in standard SAP structure to UNIX file           *
-->  I_STRUCT   " Name of record passed as parameter               *
*FORM 2000_WRITE_OUTPUT USING I_STRUCT."SRY28NOV05
FORM 2000_WRITE_OUTPUT USING I_STRUCT TYPE ANY.      "SRY28NOV05
   TRANSFER I_STRUCT TO PARMS-DS_NAME.
  IF SY-SUBRC NE 0.
    MESSAGE E004 WITH PARMS-DS_NAME.
    MESSAGE A099.
  ENDIF.
ENDFORM.
*eject
*&      Form  2100_WS_DOWNLOAD
      text                                                           *
-->  p1        text
<--  p2        text
FORM 2100_WS_DOWNLOAD TABLES INP_DATA.

Hi,
Thnaks for your reply, This is my requirement.
Here my problem is i am trying to upload the data from flatfile which contain materil number, denominator, Actual UOM, Nominator field values.
Which is the data i need to upload into MM02 and MM01, if material number is new then it has to create the material, if material is already existing it has to update the UOM values.
here i am getting data into my internal table INP_DATA, from that i am trying to upload the data to database by using job name MRP_MATERIAL_MASTER_DATA_UPLOAD with direct input program RMDATIND.
when i execute my program i am getting success message all the records writtin from flatfile to application server. and job started message.
then if i go into sm37 screen there i execute the job it is also giving active message. if i refresh it it is showing job completed message.
then i look at job log status. there i found that for existing material it is expecting material type, for new material it is giving some gravity error.
So could u help me in this it will be gr8.
Thanks & Regards,
RamNV

Similar Messages

  • While uploading data into the r/3 using call transaction or session method

    hi experts
    while uploading data into the r/3 using call transaction or session method error occured in the middle of the processing then how these methods behaves it transfers next records or not?

    hai
    Session method: The records are not added to the database until the session is processed. sy-subrc is not returned. Error logs are created for error records. Updation in database table is always Synchronous.
    Call Transaction method: The records are immediately added to the database table. sy-subrc is returned to 0 if successful. Error logs are not created and hence the errors need to be handled explicitly. Updation in database table is either Synchronous or Asynchronous.
    While to transfer the data from the through if any errors occurs until the errors are the complete the data is not transfer to the SAP system.
    the system compulsory shows the errors. that errors are stored into the error logs (Transaction is SM35).
    so the session method should not return any value.
    In call transaction method data is directly pass to the SAP system.
    So its compulsory return the value.
    Because of the call transaction is the function.
    A function should return the value mandatory
    In session method errors stroed in SYSTEM GENRATED ERROR LOG.
    IN CALL TRANSACTION TO CAPTURE THE ERRORS WE SHOULD PERFORM THE FOLLOWING.
    FIRST ME MUST DECLARE AN INTERNAL TABLE WITH THE STRUCTURE OF BDCMSGCOLL TABLE.
    THEN WHILE WRITING THE CALL TRANSACTION STATEMENT WE SHOULD PUT THE 'E' MODE FOR CAPTURING ALL THE ERRORS.
    THEN FINALLY THE CAPTURED ERRORS MUST TO SENT TO THE INTERNAL TABLE WHICH WE DECLARED IN THE BEGINNING WITH BDCMSGCOLL BY USING THE FUNCTION MODULE "FORMAT_MESSAGE"
    AND THUS THE ERROR MESSAGES WILL BE SENT TO THE INTERNAL TABLE WHICH WE DECLARED AT THE BEGINNING.

  • Error while uploading data into cube

    I am trying to upload data into my content cube but I got an error it says"
    "Time conversion from 0CALDAY to 0FISCPER (fiscal year S1 ) failed with value 20040303"     
    I checked the data in the PSA it's there but the first record is not green light it has red light. Could you please give me some idea how to solve this problems.
    Thank you in advance
    sajita

    If you don't know if you want to take over all settings (especially exchange rates may be critical) the problem is probably found in the fiscal year variant. So if you just take over the fiscal year variants.
    If the problem remains you could check the following things:
    In SPRO -> Global Settings -> Fiscal Year Variants (or similar) check:
    Does a fiscal year variant S1 exist?
    Is it time dependent? If yes, is it valid for Mar 3rd 2004?
    If it is a self defined variant check if there is a period defined for March 3rd 2004.
    Best regards
       Dirk

  • LSMW updating problem with direct input method

    Hi!
    Using version 4.0.0 of the LSM Workbench from 2001-07-01 on SAP R/3 4.7, I need to update the purchase order text and wanted to use the direct input method.  I found a tutorial on SAPTechnical which I followed.  All went well, the input data was converted and at last I got the message:
    "Long Texts in Total : 2
    Successfully Transferred Long Texts : 2
    Non-Transferred Long Texts : 0"
    My trials are recorded in table STXH with date and time and also in the material master change history.  However, the result in the material master is that the purchase order text is NOT updated.
    Can anyone tell me why this might be?

    Hi Santosh!
    First of all, thank you very much for posting an answer.  But unfortunately it was of no help.  I want to update the purchase order text on a material that already has the purchasing and purchase order text views. When I compare the PO text before and after my "Successfuly Transferred Long Texts" there is no change.  I hope that this make it more clear but it is still a mystery to me.

  • Some problem with IDoc's Settings while loading data

    Hey Experts,
    Previously i tried data loading using LIS & LO, but i was not able to load data, i was taking it as some transfer structure problem.
    But just today i tried to load Master Data, and its displaying the same error. I feel its something related to IDoc/Basis settings, please see the below wrror described and try to help.
    <b>Error when updating Idocs in Business Information Warehouse
    Diagnosis
    Errors have been reported in Business Information Warehouse during IDoc update:
    Could not find code page for receiving system</b>
    When i am checking the details its saying:
    Transfer (IDocs and TRFC): Missing messages or warnings ,
    Request IDoc : sent, not arrived ; Error passing data to port.....
    Please suggest the solution?
    Thanks.....

    Hey Roberto,
    in the details tab of RSMO, before that IDOC, i m getting this error message also:
    1. Requests (messages): Everything OK
    1.1 Data request arranged
    1.2 Confirmed with: OK
    2Extraction (messages): Missing messages
    2.1Missing message: Request received
    2.2Missing message: Number of sent records
    2.3Missing message: Number of sent records
    after that its
    Transfer (IDocs and TRFC): Errors occurred
    If it can add something extra in getting the solution.....
    Message was edited by: BI Project

  • Error -- While Uploading Data into Planning Book

    Hi all...
    working on SCM 4.1...
    In Planning book...while loading the data of one SKU-Location into the PB , i am getting the below error...
    "Overflow during propagation calculation: Number too large"
    Message no. /SAPAPO/OM_TS078
    Diagnosis
    An overflow occurred while propagating a change to a key figure within the LCA routine.
    In this case an internal error in the LCA routine is concerned.
    *ProcedureCreate an OSS message as detailed in SAP Note 167280.*
    can anybody help me to resolve the same as i couldnot ablt to view the data in planning book for one of the Product-location.
    Regards,
    Rajesh Patil

    Hi Senthil,
    For Some of the SKUs it is giving the Error , some abrupt values are stored in Live Cache for these SKUs(CVC), thats why it giving the Error.
    The only solution is ..i have to delete the CVCs and create new one...
    But i will loose the data as we cant take the Backup of Old CVC data  --> Giving COM Error
    The reason of Abrupt  Values in Live Cache  Could Be -->.>
    Macro/Alerts
    How can we fix these types of Error , as regularly i am getting these Error??
    Is there any Note/Patch to overcome this issue?
    Will be GR8 if i will get the solution..
    Regards,
    Rajesh Patil

  • Problem in getting data into database with standard direct input program

    HI All,
    I am having problem which is not updating the records in MM01 or MM02 with standard direct input program. i have data in internal table. from that table i am trying to upload into database by using background job MRP_MATERIAL_MASTER_DATA_LOAD.
    when i execute my program it is showing message job is started. then i go into sm37 and seethe job status by executing. there also i am seeing job completed succesfully.
    but if i go to mm03 and find the materials are updated or created there i couldn't find the material numbers which are from internal table.
    So if ny one help me it wil be great.
    Thanks in Advance
    Venkat N

    Hi Anil,
    Thanks for your answer, but i am facing problem is i have material no and denominator and Actual UOM and nominator field values in the flat file.....
    by using RMDATIND direct input program with MRP_MATERIAL_UPLOAD as job name for background job while uploading data into database.
    here i am not getting data in to database, but when i execute the job in sm37 it is showing that message job processing successfully completed...this is my status..
    if u can help me in this it will be gr8ful..
    Thanks,
    Venkat N

  • EAN/UPC check digit creation with Direct Input

    Hi Experts,
    I am working on Material data transfer using Direct Input. Requirement is to update the EAN/UPC for each Alt. UOM in Additional data view of Material master.
    Further we need to set Indicator for automatic Determining the check digit for EAN .
    I got Direct IP structure BMMH8 and BMMH6 for transfeering this data but didnt got Indicator field which I can set to automatic determining the check digit for EAN
    Please let me know how to pass indicator for finding the check digit automatically while creating materials using Direct Input method.
    Thanks in Advance...
    <i>-Harkamal</i>

    Hi,
    Thnaks for your reply, This is my requirement.
    Here my problem is i am trying to upload the data from flatfile which contain materil number, denominator, Actual UOM, Nominator field values.
    Which is the data i need to upload into MM02 and MM01, if material number is new then it has to create the material, if material is already existing it has to update the UOM values.
    here i am getting data into my internal table INP_DATA, from that i am trying to upload the data to database by using job name MRP_MATERIAL_MASTER_DATA_UPLOAD with direct input program RMDATIND.
    when i execute my program i am getting success message all the records writtin from flatfile to application server. and job started message.
    then if i go into sm37 screen there i execute the job it is also giving active message. if i refresh it it is showing job completed message.
    then i look at job log status. there i found that for existing material it is expecting material type, for new material it is giving some gravity error.
    So could u help me in this it will be gr8.
    Thanks & Regards,
    RamNV

  • How to store data into database by reading sql statements from text file

    how to write java program for storing data into database by reading sql statements from text file

    Step 1: Create a property file to add various queries.
    Step 2: Read the properties file using ResourceBundle
    Step 3: Use the jdbc to execute the query read from the property file.
    So in future if you need to change query no need do any modifications in java program. But depends on how you use the property file.

  • Problem while uploading data with GUI UPLOAD Function

    Hi,
      I am facing problem while uploading data with FM GUI UPLOAD    in out text file there are 7 row  but after the FM GUI UPLOAD  there are 14 entries are coming in Internal table   and each alternate row is coming as blank  with  0000 in some column   in internal table first row is proper and second line is blank so on.
    what can be the problem .
    The program in which we are using this we are using it from last 2 year but we are facing problem today only.
    regards,
      zafar

    Hi,
      The file formate is same as it is from last two years it is automatically generated by one another bar code server and there is no change  in the file formate.
      So waht can be the problem  to check any inconsistancy in system  i have develop a samll program fro  uploading a text file with same function module ,  but it is working fine.
    regards,
      zafar

  • Problem while uploading data from flat file

    hi friends,
    suppose if there are 100 records in flat file , if 20 records uploaded with out any problem and if error occurs while uploading remaing data . is necessary to upload entire data again or else only remaining data should be uploaded?
    i had used call transaction for purchase order application?
    please give me reply  soon its urgent
    thanks & regards
    priya

    Hi Hari,
    you have to upload the remaining data.
    as u have used CT method, do 1 thing trap the error data in runtime & prepare another flat file. next time correct the data in new flat file. & run the DBC program again with this new flat file.
    Reward if useful
    Regards
    ANUPAM

  • Problems with special characters uploading data into oracle database

    Greetings
    I have a problem uploading data into oracle tables from sybase datasource. The data that I want to upload is in Spanish, for example when I have a varchar field with the data 'Consultoría', in oracle table the data upload with interrogation symbols.
    I have my source and target datastores configured as follows.
    Any suggestion? Thank you for your time

    Chack section 10 Locales and Multi-byte Functionality in the SAP Data Services Reference Guide for an exhaustive description of NLS settings.
    As a summary, following settings are required:
    locales in the datastore definitions match the actual locale used in the associated databases
    the locale of the DS engine allows for source to target translation
    the character set in the target database supports storage of accented characters

  • Tax issue with Direct Input mode of RFBIBL00

    Hi, I have a problem using <b>RFBIBL00</b> (direct input mode) to create A/R invoices. There is no tax associated with the invoice, however, when I use direct input mode, instead of posting immediately, a batch input session is created. In the log, an <b>information</b> message: <i>'Specify a tax jurisdiction key'</i>. The BDC session is processed with no error.
    When using Call transaction mode for RFBIBL00, the document is posted immediately but the requirement is to use Direct input mode.
    There is no converted data in the BBTAX structure since the doc. does not need to post to tax account. Do I need to populate the Tax amount, Tax code and jurisdiction code in this structure and BBSEG in order to by pass the information message?
    Any advice is appreciated.
    - Minami

    Problem solved. Just need to untie the relationship between the ITEM import structure and the BBTAX so the Direct Input program will not require a tax jurisdiction code.

  • Problem with Direct OC, i assume

    So recently during playing some games, such as Heroes of Newerth and Wow for the most part ive been experiencing some random spiking(especially around parts where some animations happen fast) in the games and when i tab out and check processes on *system manager?*(not sure if its that in english) Direct OC takes some serious amount of memory, allmost allways its around 50% of what my current game is taking. Im not really familiar with Direct OC's business so i usually just reboot it and keep doing what im doing, usually it helps the experience sometimes it doesnt. Also i have a second problem with Direct OC, well maybe not a problem but i assume its related to it. When i have Direct OC on and computer idles ~30mins or so with screen power saving or screen saver on the recovery from screen saving takes a little while to react with desktop or so, mouse keeps moving and all but cant really do anything. So when i thought it was an issue with Direct OC, i tried without it ending up with recovery not really happening...ever! Mouse keeps moving like usual but when i try to interact with anything nothing happens and at around 10-20clicks with mouse the whole OS just freezes and thats about it for it until i force boot comp. So im guessing with this problem Direct OC is actually boosting my cpu to overcome the recovery process from the saving, but im not really too familiar with all this so im trying my luck here now.
    My Build:
    Intel Core i5 759 2.67GHz
    MSI P55M-GD45 (MS-7588)
    XFX Radeon 5850HD 1024MB
    4GB of 1600MHz DDR3
    Win7 Ultimate

    Hello,
    Please check the following note which has details for handling customer specific fields in Direct input program.
    Note 44410 - Integrating cust.-specific fields in matl master
    Cheers!
    Sam Kandas

  • Error  while uploading data in table t_499s through BDC Prog

    Hi
    am facing problem while uploading data in table t_499s through BDC Program  , if there is more than 15 records in file its not allowing to upload kindly suggest what to do
    Thanx
    Mukesh s

    Hi,
    See if you want to update only single table, which has User maintenance allowed
    Use Modify statement.
    EX:
    LOOP AT ITAB INTO WA_TAB.
        MOVE-CORRESPONDING WA_TAB TO T499S.
        MODIFY T499S.
        CLEAR T499S.
      ENDLOOP.
    It will update the table, to check go to sm30 , and check in V_T499S.
    Rgds
    Aeda

Maybe you are looking for

  • No sound when i plug my HMI cable into my RCA TV

    When i first used my HDMI cable to shound worked perfectly, but just the other day I clicked something om the volume settings and it quit working. Te sound plays through my computer and not my TV. I have windows 8 i haven't updated it at all since i

  • Projector compatability?

    hi all, i'm interested in a toshiba projector (costs around £230) but wasn't sure if it is compatible with the mac. I emailed toshiba and this is what they said; "thank you very much for you inquiry via e-mail. In general, the TDP-S8 supports any SVG

  • APP ... credit Memo

    Hi experts, Is it possible ,credit memo payment in APP.? what is the configuration required for processing credit memo in APP. Thanks in advance chin

  • Edit in Gimp with iPhoto 9.5.1

    When I try to select an external program for editing photos in iPhoto 9.5.1 Photoshop show up as the only alternative. How can I select Gimp in stead? Both Photoshop and Gimp are installed in my Macbook Pro running Maverics. Br Tellef

  • BI Bean and iPlanet server

    Hi, I am trying to deploy BI Bean on iPlanet web server 6.0 The beans work within jDeveloper (using embedded OC4Jserver) and I am able to view the output in IE. But when I deploy to the web server, I get BIB exception. I assumed the config file refer