Direct input data

Hi ,
What are some sample Direct input data transfer programs?
Thanks,
Manjula

Direct Input method is used for bulk transfer of data into SAP system.It results in faster execution since no screens are processed and the SAP database will be updated directly using the standard function modules.
In MM for Material Master data - RMDATIND
FI - for Accounting Documents - RFBIBL00
PP - for Independent requirements - RM06IN00
CA - for Classification data - RCCLBI03
Regards,
Maha

Similar Messages

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

Unit Conversion Error in Direct Input method for data transfer

Hi Experts,
I am getting a error "E MG 427: Conversion error: field BMMH6-MEINH; content PAK" When I am uploading Alt. UoM using BMHH6 structure in Direct Input. I checked value for UoM in converted data it is "PAC". I think system is internally converting it to PAK so the error is coming.
Please let me know what need to be done to avoid this error.
Thanks in Advance..
-Harkamal

Hi
Before passing this unit to the program
check the conversion Exit in the Domain of the Field
and use the fun module
CONVERSION_EXIT_ALPHA_INPUT and pass that value and see how it takes
otherwise use the fun module UNIT_CONVERSION_SIMPLE and pass the value to program
Regards
Anji

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

Is it a best practice to Input Data directly to Parent Currency ?

Dear Gurus,
I understand this question is very simple, but I am wondering is it a best practice to Input data directly into <Parent Currency>?
I am having a scenario where users do translation in Oracle and they wish to see the same number in HFM. As the process that they follow is unique in nature by Entity->Account [OR] for all Entities->Account, creating Override accounts is not helping us and rapidly increasing the Override hierarchy month-on-month.
Thanks...
Satya

By overriding the accounts, I assume you are referring to accounts that are translated historically as opposed to the default translation performed by HFM?
If so, I have seen two general approaches to achieve this:
a) Allowing the user to directly override the translation at IsTransCurr (i.e. <parent currency> if parent is in a currency other then entity)
b) Entering in a special currency rate in a rate account and then adjusting the translate routine to translate your account by that rate.
I personally, am a bigger fan of the first option.

LSMW - Direct Input- RMDATIND- Converted data is different.

Hi Experts,
I am working on LSMW - Direct Input- by std. program RMDATIND for material Update,
When I display converted data, its different than data that I see in display read data step,
Each time in step display converted data,one perticular record is displayed.. Even though
I change input data.
I like to know why converted data shown is wrong?
thanks & regards
Ashish

Hi thomas,
thanks for your help....
i created 2 materials in file, i.e. with material no. xxxxx2 & material no.xxxxx 3.
Or even if i created record in iput file with other materila no.
At each end every time I can see only one converted data record eith Material no. Value = xxxxx1.
thanks & regards
Ashish

LSMW - DIRECT INPUT METHOD FOR UPLOADING PP MASTER DATA

Dear Gurus,
A LSMW project (DIRECT INPUT METHOD)has been created for PP master.
But Now They have Lost Previous File which they have prepared Earlier.
Now to Create a file for the Same Project wat fields need to be taken.
By taking only Source structure fields it is giving error.
In project some constant fields are also there.
pls guide me.
With Regards,
GMP

have Lost Previous File
what does that mean? did they lose the source that should be used to load the data from?
without source you cannot load data.
Had you ever got this source file? how? by mail, then check your old mails and take it from there, ask the sender to he/she checks the SENT folder in his mail system. Maybe someone has a local copy of this fille.

Error in LSMW for MM41 - "No batch input data for screen SAPLMGMW 0100"

I'm trying to create an LSMW for MM41 to create new Retail articles en Mass. This will be used to only create the Basic view as other LSMW's already exist to maintain the other views. I've created the Recording and setup the LSMW already. My data is read correctly from the source file. When I execute the batch session it fails with the following error - "No batch input data for screen SAPLMGMW 0100".
I assume the fields in MM41 screen are not setup for batch processing. Could someone with more knowledge or experience in SAP Retail please confirm my assumption and explain where this is setup or provide an alternative to creating new articles en Mass via MM41? The direct input method is more suited for MM01 and not MM41.
Regards
Fawaaz

Hi Guys,
Thanks so much for all the prompt responses. My issue is now resolved.
The issue, I'm sure, was my default settings in the MM41 screen which the recording probably took into account or the batch program didn't like. I deleted my recording and created a new one but before I started the recording, I went into the MM41 screen and removed all default values AND view selections. I made my Basic view selection constant in my recording and also in my field mapping. My LSMW for MM41 is now working perfectly.
Just to answer some of the questions above, my LSMW was Reading and Converting the data in my source file fine. When I display the Read and Converted data, it shows the data fields in the correct place.
Thanks again.
Regards
Fawaaz

Tax issue with Direct Input mode of RFBIBL00

Hi, I have a problem using RFBIBL00 (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 information message: 'Specify a tax jurisdiction key'. 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.

LSMW direct input method

Hi
What is the procedure to include a specific program / report in the drop down box of program name of Direct Input method in LSMW?
What is the diff. between Physical path and Logical path?
How can we give our input data using logical path when we execute some standard batch or direct input programs?
Ex. RMDATIND.

http://help.sap.com/saphelp_erp2005vp/helpdata/en/87/f3ae63e68111d1b3ff006094b944c8/frameset.htm
Regards,
Amit

Problem while updating the forecast value in m.master by direct input menth

Hi All
Good Day
I am updating the forecast value in material master by direct input method.
my program is working fine when I am running it online.
but when i am runnig in back ground I am getting one error which is mentioned below
 Job ZM_OPTIMIZA_UPLOAD: Data does not match the job definition; job terminated BD 078 E
Please anyone can help ne in above case.
Thanks in advance.
Cheers
Vallabhaneni

Hi Hakim
How are you
Thanks for your valuable suggestion.
I am executing my program in background with bmv0 transaction with variant, in development I can run this job in background with out any logical errors but in QA I am getting errors.
Can you please help me in the above case.
In Bmv0 transaction first I defined the job and in program rmdatind (execute) screen first I mentioned the Max. no of logical errors as 500 and Transactions per commit unit as 500 and I run the program in background in bmv0 transaction and I am getting the message background job terminated immediately
Because of this again I changed the Max. no of logical errors 500 to 99999 and transaction per commit unit 500 to 999999 and then i scheduled my program in background.
Alomost it ran for 27 hours and then it has given the message background job terminated.
Job log entries are as follows.
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040840; material number SUJ82J8400; error gravity E
22.12.2008 11:19:46 Transaction 0000040840: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040841; material number SUJ84G3001; error gravity E
22.12.2008 11:19:46 Transaction 0000040841: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040842; material number SUJ84G3002; error gravity E
22.12.2008 11:19:46 Transaction 0000040842: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040843; material number SUJ86G0100; error gravity E
22.12.2008 11:19:46 Transaction 0000040843: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040844; material number SUJ86G0300; error gravity E
22.12.2008 11:19:46 Transaction 0000040844: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040845; material number SUJ86G0900; error gravity E
22.12.2008 11:19:46 Transaction 0000040845: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040846; material number SUJ86G9600; error gravity E
22.12.2008 11:19:46 Transaction 0000040846: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040847; material number SUJ86G9601; error gravity E
22.12.2008 11:19:46 Transaction 0000040847: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040848; material number SUJ86J0000; error gravity E
22.12.2008 11:19:46 Transaction 0000040848: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:20:54 Transaction 0000040848 completed Mat. no. No. of log. errors 0000040848
22.12.2008 11:21:30 ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
22.12.2008 11:21:30 Job cancelled
I know it has taken long time to process the job because of I changed the transactions per commit unit (500 to 999999) it kills the system
But I am supposed to provide some number < 999999 in transactions per commit unit
actually I haven't tried like I said above < 999999 because i don't have any hopes.
Please look at this problem and help me in this case.
Thanks in advance.
Vallabhaneni

Direct input (DINP) in Lsmw

Hii All,
I am using direct input method for uploading Material Forecasting in SAP server ...
But the problem is that , I m not able to get the error log ie im not getting the material no.
that are ended up in error while uploading. Actually, i can see the material that are in
error but im not abe to save it or download it,So as to pass it to functional Consultants.
Im using the RMDATIND program to upload the file.
Requesting all to provide some suggestion to get /capture the error data.
Thanks in Advance.
Chandan

hi Venu
can you please tell me why do u want to upload data from adrc table.
thanks
abdul

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.

LSMW Direct input for Material Master

Hi,
I need to upload the following views data into SAP using direct input (RMDATIND)
Basic Data 1
Basic Data 2
Classification
Sales: Sales Org. Data 1
Sales: Sales Org. Data 2
Sales: General/Plant Data
Foreign Trade: Export Data
Sales Text
Purchasing
Foreign Trade: Import Data
Purchase Order Text
Work Scheduling
General Plant Data / Storage 1
General Plant Data / Storage 2
Accounting 1
Accounting 2
Costing 1
Costing 2
Is it possible to upload these views through direct input or is there any limitation with the direct input method because i'm able to map the below fields only once
Country of Origin
Region of Origin
Excemption Certificate
Ex. Certificate number
Issue date of Cert. No.
Indicator: Military goods
the above fields are repeated twice for the views
Foreign Trade: Export Data
Foreign Trade: Import Data
If anybody has done material master in lsmw please let me know.
Thanks in advance.
Poorna

Hi,
I need to upload the following views data into SAP using direct input (RMDATIND)
Basic Data 1
Basic Data 2
Classification
Sales: Sales Org. Data 1
Sales: Sales Org. Data 2
Sales: General/Plant Data
Foreign Trade: Export Data
Sales Text
Purchasing
Foreign Trade: Import Data
Purchase Order Text
Work Scheduling
General Plant Data / Storage 1
General Plant Data / Storage 2
Accounting 1
Accounting 2
Costing 1
Costing 2
Is it possible to upload these views through direct input or is there any limitation with the direct input method because i'm able to map the below fields only once
Country of Origin
Region of Origin
Excemption Certificate
Ex. Certificate number
Issue date of Cert. No.
Indicator: Military goods
the above fields are repeated twice for the views
Foreign Trade: Export Data
Foreign Trade: Import Data
If anybody has done material master in lsmw please let me know.
Thanks in advance.
Poorna

Doubt in BDC direct input method

Hi experts
I dont know how to upload data in SAP data base by using BDC direct input coding method. Can u people explain this with coding?
Thanks in advance.
Regards
Antony

Hi,
DI is used when u r going upload large amount of data for single application.
Better example where direct input method will be used is... uploading the data for material master.....it includes lot of views so its very much difficult to capture all the views and record the tcode and map the data in such conditions its better to go with DI methods
advantages:
in session method or CT method while uploading the data u do the validation by fallowing the screen sequence and field sequence where as in DI validations can be done set of code so this make the process very fast so its advantageous to upload large amout of data.
you always use the standard sap provided program for this.
Here in DI method very important thing is structure of flat file... so to know the structure first of all you have to download the data for one record into the internal table with the use of the same program then with the use of that structure u have to desing the flat file and upload the data.
Re: re: direct input method
Award points if useful.
Thanks,
Ravee...

Direct input data

Similar Messages

Maybe you are looking for