BDC-Direct Input

Please give an example for Direct Input method in BDC.When it is used? what is the advantage and disadvantage?

Hi Khanna Renga ,
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.
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 Call Transaction method while uploading the data u do the validation by fallowing the screen sequence and field sequence where as in Direct Input 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 Direct Input 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.
Direct Input:
With direct input, the SAP function modules execute the consistency checks. However with batch input, these consistency checks are executed with help of the screens. This means that direct input has considerable performance advantages. But there are a few programs for direct input, you can use them if it accomplishes your goal. Direct Input programs work like that they update database tables directly. As you know that it is forbidden to update SAP database tables directly, since consistency and security should be considered. Exceptions are these direct input programs. So you are not able to write custom ABAP direct input programs. But of course you can write ABAP programs to update custom database tables (Z tables), if you are sure all about consistency.
SAP has created direct input programs because SAP wanted to enhance the batch input procedure, since batch input is slower. SAP offers the direct input technique, especially for transferring large amount of data. In contrast to batch input, this technique does not create sessions, but stores, updates, inserts data directly. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to able to activate the restart mechanism, direct input programs must be executed in the background only. To maintain and start these programs, use program RBMVSHOW or transaction BMV0.
Examples for direct input programs are:
RFBIBL00 - FI
RMDATIND - MM
RVAFSS00 - SD
RAALTD11 - AM
RKEVEXTO - CO-PA
Also have a look on below thread..
Re: re: direct input method
Re: Give a BDC example by Direct Input Method
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
Hope it will solve your doubts and problem..
Reward points if useful..
Thanks & Regards
ilesh 24x7

Similar Messages

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...

Can anybody tell me why "Direct Input Method of BDC" said to be Obselete?

Why it is said that "Direct Input Method of BDC" is obselete?

hi,
Direct Input:
A recent technique to input data safely. An alternative to batch input.
With direct input, the SAP function modules execute the consistency checks. However with batch input, these consistency checks are executed with help of the screens. This means that direct input has considerable performance advantages. But there are a few programs for direct input, you can use them if it accomplishes your goal. Direct Input programs work like that they update database tables directly. As you know that it is forbidden to update SAP database tables directly, since consistency and security should be considered. Exceptions are these direct input programs. So you are not able to write custom ABAP direct input programs. But of course you can write ABAP programs to update custom database tables (Z tables), if you are sure all about consistency.
SAP has created direct input programs because SAP wanted to enhance the batch input procedure, since batch input is slower. SAP offers the direct input technique, especially for transferring large amount of data. In contrast to batch input, this technique does not create sessions, but stores, updates, inserts data directly. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to able to activate the restart mechanism, direct input programs must be executed in the background only. To maintain and start these programs, use program RBMVSHOW or transaction BMV0.
Examples for direct input programs are:
RFBIBL00 - FI
RMDATIND - MM
RVAFSS00 - SD
RAALTD11 - AM
RKEVEXTO - CO-PA
I hope it helps.
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
cheers!'sri

Direct input in bdc

Hi all,
Can anyone explain me what is the use of direct input method over call transaction / session method....
Regards,
subbu.

hi,
Data is transferred from an external system into the SAP R/3 System. You use data transfer when you:
Transfer data from an external system into an R/3 System as it is installed.
Transfer data regularly from an external system into an R/3 System.
There are three basic methods for Data Transfer:
Direct Input (DINP)
With direct input, the SAP function modules execute the consistency checks. However with batch input, these consistency checks are executed with help of the screens. This means that direct input has considerable performance advantages. But there are a few programs for direct input, you can use them if it accomplishes your goal. Direct Input programs work like that they update database tables directly. As you know that it is forbidden to update SAP database tables directly, since consistency and security should be considered. Exceptions are these direct input programs. So you are not able to write custom ABAP direct input programs. But of course you can write ABAP programs to update custom database tables (Z tables), if you are sure all about consistency.
So why SAP has created direct input programs? Because SAP wanted to enhance the batch input procedure, since batch input is slower. SAP offers the direct input technique, especially for transferring large amount of data. In contrast to batch input, this technique does not create sessions, but stores, updates, inserts data directly. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to able to activate the restart mechanism, direct input programs must be executed in the background only. To maintain and start these programs, use program RBMVSHOW or transaction BMV0.
Examples for direct input programs are:
RFBIBL00 - FI
RMDATIND - MM
RVAFSS00 - SD
RAALTD11 - AM
RKEVEXTO - CO-PA
CALL TRANSACTION
It seems like batch input method. Data consistency check with help of screen logic.
Batch Input with batch input sessions.
Data consistency check with help of screen logic. Batch Input is a standard technique for transferring large sets of data into the SAP System. The transaction flow is transferred as if it were entered online. The advantage of this is that all relevant check for the transaction are executed, thereby ensuring that the data is consistent.
Hope this helps, Do reward.

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.

Re: direct input

Hi,
What is the difference between direct input and BDC.
What is the main advantage of using direct input method.
rgds
p.kp

just to add one or two more aspects:
BDC does a CALL TRANSACTION. So each and every case (document, master data,...) is committed to the database on commit. The commit occurs after completion of the transaction.
Direct input will commit the data to the database when the commit is requested explicitly.
During BDC and direct input relevant DB tables are locked, they can not be updated by other processes. After commit they are unlocked.
Thus a program using direct input must care for intermittent commits to avoid an overflow of the lock tables. For master data, a lock table overflow may occur for more than (roughly) 2000 cases.
Although direct input does not do any screen input, the same routines are passed as BDC with (simulated) screen input.
Hope it helps,
C.

Abt Direct Input Method

Hi Experts,
How can Handle Direct Input Method in BDC.wht is Direct Input Method, wht purpose they can use.
Thanks
Srinadh

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
Regards,
Priyanka.

Fields mobile no, house no is not there LSMW direct input customer master

Hi All,
In LSMW direct input method for customer master(RFBIDE00) fields mobile number, house number is not available. But field street(STRAS) is available there is no field like house number .
How to proceed futher. please let me know the suggestion . It's is urgent.
Regards,
Karthik.

1) read documentation to rfbide00 with se38
2) if you want to use the new adress-fields from table adrc you must use bapi or bdc to xd01
A.

Direct Input for Purchase Order

Hi Gurus,
I want to create LSMW direct input for creating Purchase Order,
I have make to file for this, Header and Item,
for the Header, i only use this field : STYPE, BUKRS(Company Code), EKORG(Purch.Org), EKGRP(Purch Group), BSART(Order Type), LIFNR(Vendor), WAERS(Currency)
for the Item, : STYPE
EBELP
EMATN
MATKL
WERKS
EINDT
MENGE
MEINS
NETPR
WAERS
now, when i run this direct input program, it always error with this message " The Material xxxx does not exist or is not activated"
i have check the material, it already created and the purchasing tab also have created
what is the problem ? maybe i miss another field that i should entry in the source field LSMW ?
really need help for this issue
Regards,
Marufat

Try to make 1 manual PO for that material check whether it is allowing to make,
Best option to use is BAPI_PO_CREATE1 for uploading PO.
LSMW does not provide the table control features in BDC or recording.
Check below link for more details,
[LSMW PO|http://forums.sdn.sap.com/thread.jspa?messageID=10155752#10155752]

Difference between batch input method and direct input method in LSMW.

Hi all,
what is difference between batch input method and direct input method in LSMW. are they same?if differences are there tell me with details?

Hi,
Here are few differences bw Batch Input and Direct Inputs methods.
Batch Input: Uses classical BDC approach, but doesn't required an ABAP program to be written to format the BDC DATA. The user has to format the data using predefined structures and store it in a flat file. Yet it is a slower updation method.
Direct Input: Works similar to Batch Input programs. The difference is, instead of processing screens they validate fields and directly load the data into tables using standard function modules. Much faster and suits for large volume of data.
Thanks.
DhanaLakshmi M S

Difference between Batch input and Direct Input

Hi please tell me the difference between Batch Input and Direct Input in BDC?

hi aparna,
DIRECT INPUT
TO ENTER THE DATA INTO THE CORRESPONDING DATABASE TABLES DIRECTLY, THE SYSTEM CALLS A NUMBER OF FUNCTION MODULES THAT EXECUTE ANY NECESSARY CHECKS. IN CASE OF ERRORS, THE DIRECT INPUT TECHNIQUE PROVIDES A RESTART MECHANISM. HOWEVER, TO BE ABLE TO ACTIVATE THE RESTART MECHANISM, DIRECT INPUT PROGRAMS MUST BE EXECUTED IN THE BACKGROUND ONLY. DIRECT INPUT CHECKS THE DATA THOROUGHLY AND THEN UPDATES THE DATABASE DIRECTLY.
TO MAINTAIN AND STRAT THESE PROGRAMS, USE PGM RBMVSHOW OR THE TRANSACTION BMVO.
BATCH INPUT
TYPES SESSION METHOD, CALL TRANSACTION, DIRECT INPUT.
TO SAVE DATA IN THE BDCTAB, USE THE FIELDNAME BDC_OKCODE AND FIELD VALUE OF /11.
BDCDATA
THIS IS A STRUCTURE WHICH CONTAINS THE FOLLOWING FIELDS.
PROGRAM NAME OF TH MOD PROG ASSOCIATED WITH THE SCREEN. SET ONLY FOR THE FIRST RECORD OF THE SCREEN.
DYNPRO SCREEN NUMBER. ALSO SET ONLY FOR FIRST RECORD.
DYNBEGIN INDICATES THE FIRST RECORD OF THE SCREEN. SET X FOR FIRST RECORD OTHERWISE .
FNAM FIELD NAME.
FVAL VALUE FOR THE FIELD NAMED IN FNAM.
THE FIRST STEP IN BDC IS TO UPLOAD DATA FROM THE FLAT FILE OR SEQUENTIAL FILE TO THIS BDCTABLE.
SESSION METHOD
WE USE 3 FUNCTION MODULES IN THIS SESSION METHOD.
1) BDC_OPEN_GROUP
 USER NAME: USER NAME
 GROUP: NAME OF THE SESSION
 LOCK DATE: THE DATE ON WHICH YOU WANT TO PROCESS THE SESSION.
 KEEP: THIS PARAMETER IS PASSED AS X WHEN YOU WANT TO RETAIN SESSION AFTER PROCESSING IT OR TO DELETE IT AFTER PROCESSING.
THIS CREATES A SESSION
2) BDC_INSERT
 TCODE: TRANSACTION NAME
 DYNPROTAB: BDC DATA
THIS CREATES A SEESION AND DATA IS TRANSFERRED O SESSION.
3) BDC_CLOSE_GROUP THIS CLOSES THE BDC GROUP.
ONLY ONE SESSION CAN BE CREATED USING BDC_OPEN_GROUP. BUT MULTIPLE TRANSACTIONS CAN BE PROCESSED USING BDC_INSERT.
CALL TRANSACTION
CALL TRANSACTION <TCODE> USING <BDCTAB>
 MODE <A/N/E>
 UPDATE <S/A>
 MESSAGES INTO <MSGTAB>.
A ALL SCREEN MODE. ALL THE SCREEN OF THE TRANSACTION ARE DISPLAYED.
N NO SCREEN MODE. NO SCREEN IS DISPLAYED WHEN YOU EXECUTE THE TRANSACTION.
E ERROR SCREEN. IF THE SCREEN HAS ERROR RECORD, THEN THAT SCREEN WILL BE DISPLAYED.
S - IF YOU CHANGE DATA OF ONE TABLE THEN ALL THE RELATED TABLES GETS UPDATED. AND SY-SUBRC IS RETURNED I.E., SY-SUBRC IS RETURNED FOR ONCE AND ALL.
A - WHEN YOU CHANGE DATA OF ONE TABLE, THE SY-SUBRC IS RETURNED. AND THEN UPDATING OF OTHER AFFECTED TABLES TAKES PLACE. SO IF SYSTEM FAILS TO UPDATE OTHER TABLES, STILL SY-SUBRC RETURNED IS 0 (I.E., WHEN FIRST TABLE GETS UPDATED
WHEN YOU UPDATE DATABASE TABLE, OPERATION IS EITHER SUCCESSFUL OR UNSUCCESSFUL OR OPERATION IS SUCCESSFUL WITH SOME WARNING. THESE MESSAGES ARE STORED IN INTERNAL TABLE, WHICH YOU SPECIFY ALONG WITH MESSAGE STATEMENT. THIS INTERNAL TABLE SHOULD BE DECLARED LIKE BDCMSGCOLL, A STRUCTURE AVAILABLE IN ABAP/4. IT CONTAINS THE FOLLOWING FIELDS: TCODE, DYNAME, DYNUMB, MSGTYP, MSGID.
DIFFERENCE BETWEEN SESSION AND CALL TRANSACTION
 SESSION METHOD CALL TRANSACTION
1. DATA IS NOT UPDATED IN DATABASE TABLE UNLESS SESSION IS PROCESSED. IMMEDIATE UPDATION IN DATABASE TABLE.
2. NO SY-SUBRC IS RETURNED. SY-SUBRC IS RETURNED.
3. ERROR LOG IS CREATED FOR ERROR RECORDS. ERRORS NEED TO BE HANDLED EXPLICITLY
4. UPDATION IN DATABASE TABLE IS ALWAYS SYNCHRONOUS
 UPDATION IN DATABASE TABLE CAN BE SYNCHRONOUS OR ASYNCHRONOUS.
5. ASYNCHRONOUS PROCESSING SYNCHRONOUS PROCESSING
6. TRANSFERS DATA FOR SINGLE TRANSACTIONS TRANSFERS DATA FOR MULTIPLE TRANSACTIONS
ERROR HANDLING IN CALL TRANSACTION
1) CREATE AN INTERNAL TABLE SIMILAR TO THE STRUCTURE OF YOUR LOCAL FILE.
2) CREATE BDCTAB LIKE BDCDATA.
3) CREATE BDCMSG LIKE BDCMSGCOLL.
4) CREATE AN INTERNAL TABLE SIMILAR TO THE 1ST INTERNAL TABLE.
5) UPLOAD FN UPLOADS DATA FROM THE LOCAL FILE TO THE ITAB.
6) LOOP AT ITAB.
POPULATE BDCTAB TABLE.
CALL TRANSACTION STATEMENT.
PERFORM CHECK.
REFRESH BDCTAB.
ENDLOOP.
7) FORM CHECK.
IF SY_SUBRC <> 0.
CALL FUNCTION FORMAT_MESSAGE.
APPEND ITAB2.
ENDFORM.
TRANSACTION FOR RECORDING SHDB.
MAX TIME ALLOWED FOR ONLINE EXECUTION 300 SECONDS.

Pls reward if helpful.

Error in uploading the PO while running Direct Input porgram RM06EEI0

Hi all
i have written one conversion program to upload PO. Here in the program i am populating the batch input structures MBEPOH and MBEPOI and finally writing it to the unix file.
Finally when i execute the direct input program RM06EEI0
using the logical filename , it gives the error as 'Net price should be greater than 0' .
i have also checked the file in the unix directory , there the net price is getting populated correctly. Also i debugged the direct input program and found out that net price is getting passed correctly to FM ME_CREATE_PO_ITEM but somewhere the KOMP structure is not getting populated ,that is why net price becomes 0.
Can anybody please tell whether there is some issue in writing the conversion program or i am missing some parameters to be passed in MBEPOH or MBEPOI, or what has to be done.
Please help me , it is urgent .
Thanks and Regards,
Syed

I have the same problem, could somebody help?
Thanx, Marian

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

"Indicator: GR-Based Invoice Verification" direct input Upld PO LSMW

Hi, Im using lsmw direct input method. I am uploading the PO. But the GR Based invoice verification field was not checked ON. Im trying this using USER_EXIT in enhancement MM06E005, with EXIT_SAPMM06E_017.
Any body can tell me how i can check ON the field WEBRE( GR based invoice verification) while creating the PO through LSWM.
regards
RAJ

Hi,
How you solved, kindly explain
Also explain how to upload PO through LSMW in the case of multiple line items for single PO?
Thanks & Regards
Ravi

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

BDC-Direct Input

Similar Messages

Maybe you are looking for