Customer direct input

Hi,
I'm having a problem loading customer data using program RFBIDE00 & tcode XD01.The created session is running successfully till I encounter screen no 210 in pgm: SAPMF02D.
The problem I have is that the batch input session created by RFBIDE00 is giving an error saying that "No batch input data for screen SAPMF02D 0210". I have checked in the display converted data and all the required fields for the screen are getting populated in BKNB1 structure. Also i check the internal table before RFBIDE00 does the BDC insert statment. The internal table FT has all the required data(FNAM and FVAL) for program SAPMF02D screen 0210, but still when i process the session it is giving an error saying that no input for "No batch input data for screen SAPMF02D 0210".
Please guide to solve this problem.
Thanks in advance.
Vishnu Priya

Hi all,
me too I have this problem...
In debug I see that screen fields are populated but no sy-ucomm is added to FT internal table for dynpro 210 (I have the same issue for dynpro 130 - bank data)
I'm wondering If some technical fields are to be filled in structure BKNB1...
At last I think I'll make a custom recording for this
No one has resolved this issue ?
Many thanks
Manuel

Similar Messages

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.

LSMW Direct Input Custom Program

Hi All,
I have been trying to set up a custom (Z Program) for direct input method for LSMW. So far I have dicovered that it can be achieved by modifing SXDA0-3 tables.
Has anyone achieved this successfully? Any example (even the simplest one) or step by step help would be highly appreciated.
Regards,
~Mark

Yes, it does appear that this table contains the data which gives the structures names of the structures used in direct input programs.
Documentation for LSMW is limited, but here are some links.
http://www.erpgenie.com/sap/saptech/lsmw.htm
http://www.sap-img.com/sap-data-migration.htm
http://www.ficoexpertonline.com/downloads/0703.doc
http://help.sap.com/saphelp_nw2004s/helpdata/en/ad/2d54a41d7011d2b42e006094b944c8/frameset.htm
REgards,
RIch Heilman
Message was edited by:
Rich Heilman

Customer Master Conversion - Direct input method

Hi,
I want to extend the sales area of the customers who are already existing using Direct Input Method. But I am getting the Error.
Thanks
Raghavendra

Hi Raghavendra,
Can you tell what error ur getting?Also which structure you are using ? I think the structure BKNVV / BKNZA needs to be extend for this additional extended sales area.
Also try to use Batch input seesion methos. in that you may get the structure name which we need to extend.
Pradeep

How to use copy of standard program for direct input in LSMW

currently we're using object 0085 Purchase Orders and and method 0001 for standard direct input, which is processed with program RM06EEI0
now I want to set an additional flag and avoid creating it by means of BUS PurchaseOrder.CreateFromData1 method (coz the structure is quite different and more complex).
so my question is now how can i assign a copy of the standard program for processing?
for better understanding I've attached a screenshot of the according screen
[img]http://img71.imageshack.us/img71/1558/lsmwcr6.jpg[/img]

ok, solution was to maintain table SXDA1 (SAPDXfer: Data Transfer Objects and Sub-Category).
modify entries for DXPRG, DXPR1 and LOADPRG with custom program names

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

Extending Batch Input or Direct Input

Hello experts,
I am customizing Material Master by adding some custom fields to MARA. I know I can extend the IDoc for loading the data including my custom fields. I was wondering if, and how, to extend the Batch Input or Direct Input to include my custom fields.
Can anyone point me in the correct direction?

Append the MARA structure with your custom fields. (Are these fields available on material master screen as well ?)
Write the code in the appropriate user-exit to populate these fields OR use a BAPI and extensionin parameter to populate your custom fields.

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.

LSMW for equipment creation-Standard Batch/Direct Input

Hi,
We developed an LSMW with standard batch / direct input method for creating equipment masters.
We used Object =0400 ( equipment ) and method = 0001 ( batch input)
We maintained source structures and source fileds. In the source field , we maintained only those fields that we need from table IBIPEQUI but in the order given in this structure.
Also we maintained filed mapping and field convertion rules for the above source fields.
When we run LSMW step - Display converted data , we see that
Transactions Read:                   1
Records Read:                          1
Transactions Written:                0
Records Written:                       0
Not sure what could have gone wrong?
Please provide some clues to the following questions.
1) Should the source structure be same as fields from stuc. IBIPEQUI and should it include all the fields in the source structure?
2) Is field mapping required or not ?
3) We are getting an error - transaction is not supported in direct input mode.
Thanks in advance
Rgds,
Rajesh

1. Source fields are( same as IBIPEQUI structure ; the tab delimited file matches with these fields)
TCODE                          C(020)    Transaction Code
RECORDNAME                     C(008)    Record name
EQUNR                          C(018)    Equipment
DATSL                          C(008)    Valid On
EQTYP                          C(001)    Equipment category
EQKTX                          C(040)    EQKTX
BEGRU                          C(004)    Authorization Group
EQART                          C(010)    Technical obj. type
GROES                          C(018)    Size/dimensions
INVNR                          C(025)    Inventory number
BRGEW                          C(017)    Gross Weight
GEWEI                          C(003)    Weight unit
ELIEF                          C(010)    Vendor
ANSDT                          C(008)
ANSWT                          C(017)    Acquisition Value
WAERS                          C(005)    Currency
HERST                          C(030)    Manufacturer
HERLD                          C(003)    Country of manufact.
BAUJJ                          C(004)    Construction year
BAUMM                          C(002)    Construction month
TYPBZ                          C(020)    Model number
SERGE                          C(030)    ManufSerialNumber
MAPAR                          C(030)    ManufactPartNo.
GERNR                          C(018)    Serial number
GWLEN                          C(008)    Warranty end date
KUND1                          C(010)    Customer
KUND2                          C(010)    End customer
KUND3                          C(010)    Operator
SWERK                          C(004)    Maintenance plant
STORT                          C(010)    Location
MSGRP                          C(008)    MSGRP
BEBER                          C(003)    Plant section
ARBPL                          C(008)    Work center
ABCKZ                          C(001)    ABC indicator
EQFNR                          C(030)    Sort field
BUKRS                          C(004)    Company Code
ANLNR                          C(012)    Asset Number
ANLUN                          C(004)    ANLUN
GSBER                          C(004)    Business Area
KOSTL                          C(010)    Cost Center
PROID                          C(024)    PROID
DAUFN                          C(012)    Standing order
AUFNR                          C(012)    Order
TIDNR                          C(025)    Technical IdentNo.
SUBMT                          C(018)    Construction type
HEQUI                          C(018)    Superord. Equipment
HEQNR                          C(004)    Position
EINZL                          C(001)    Single installation
IWERK                          C(004)    Planning plant
INGRP                          C(003)    Planner group
GEWRK                          C(008)    Main work center
WERGW                          C(004)    Plant for WorkCenter
RBNR                           C(009)    Catalog profile
TPLNR                          C(030)    Functional Location
DISMANTLE                      C(001)    DismIndic.
VKORG                          C(004)    Sales Organization
VTWEG                          C(002)    Distribution Channel
SPART                          C(002)    Division
MATNR                          C(018)    Material
SERNR                          C(018)    BOM explosion number
WERK                           C(004)    WERK
LAGER                          C(004)    LAGER
CHARGE                         C(010)    CHARGE
KUNDE                          C(010)
KZKBL                          C(001)    Load records
PLANV                          C(003)    PLANV
FGRU1                          C(004)    FGRU1
FGRU2                          C(004)    FGRU2
STEUF                          C(004)    Control key
STEUF_REF                      C(001)    STEUF_REF
KTSCH                          C(007)    Standard text key
KTSCH_REF                      C(001)    Std text referenced
EWFORM                         C(006)    EWFORM
EWFORM_REF                     C(001)    EWFORM_REF
BZOFFB                         C(002)    Ref. date for start
BZOFFB_REF                     C(001)    BZOFFB_REF
OFFSTB                         C(007)    Offset to start
EHOFFB                         C(003)    Unit
OFFSTB_REF                     C(001)    OFFSTB_REF
BZOFFE                         C(002)    Ref. date for finish
BZOFFE_REF                     C(001)    BZOFFE_REF
OFFSTE                         C(007)    Offset to finish
EHOFFE                         C(003)    Unit
OFFSTE_REF                     C(001)    OFFSTE_REF
WARPL                          C(012)    Maintenance Plan
IMRC_POINT                     C(012)    Measuring point
INDAT                          C(008)    Inverse date
INTIM                          C(006)    Processing time OC Workbe
INBDT                          C(008)    Start-up date
GWLDT                          C(008)    Guarantee
AULDT                          C(008)    Delivery date
LIZNR                          C(020)    License number
MGANR                          C(020)    Master warranty
REFMA                          C(018)    REFMA
VKBUR                          C(004)    Sales Office
VKGRP                          C(003)    Sales Group
WARR_INBD                      C(001)    Inbound warranty
WAGET                          C(001)    Warranty inheritance poss
GAERB                          C(001)    Indicator: Pass on warran
ACT_CHANGE_AA                  C(001)    ACT_CHANGE_AA
STRNO                          C(040)    STRNO
DATLWB                         C(008)    Date Last Goods Movmnt
UII                            C(072)    UII
IUID_TYPE                      C(010)    IUID Type
UII_PLANT                      C(004)    Plant Responsible for UII
2, source structure is assigned to target structure IBIPEQUI
3. In the assign files step - all settings given above are correctly maintained.
4. Field mapping
TCODE                        Transaction Code
                    Rule :   Default Settings
                    Code:    IBIPEQUI-TCODE = 'IE01'.
RECORDNAME                   IBIP: Name of the Data Transfer Record
                    Rule :   Default Settings
                    Code:    IBIPEQUI-RECORDNAME = 'IBIPEQUI'.
EQUNR                        Equipment Number
                    Source: ZIE01_002_SOURCE-EQUNR (Equipment)
                    Rule :   Transfer (MOVE)
                    Code:    if not ZIE01_002_SOURCE-EQUNR is initial.
                               IBIPEQUI-EQUNR = ZIE01_002_SOURCE-EQUNR.
                             endif.
DATSL                        Date valid from
                    Source: ZIE01_002_SOURCE-DATSL (Valid On)
                    Rule :   Transfer (MOVE)
                    Code:    if not ZIE01_002_SOURCE-DATSL is initial.
                               IBIPEQUI-DATSL = ZIE01_002_SOURCE-DATSL.
                             endif.
EQTYP                        Equipment category
                    Source: ZIE01_002_SOURCE-EQTYP (Equipment category)
                    Rule :   Transfer (MOVE)
                    Code:    if not ZIE01_002_SOURCE-EQTYP is initial.
                               IBIPEQUI-EQTYP = ZIE01_002_SOURCE-EQTYP.
                             endif
When I read data with 1 record uploaded ( in the assign fields step , I did not choose "fields names at start of file" and also saved the file with tab delimited text format without field names), it shows as
Transactions Read:                    2
Records Read:                         2
Transactions Written:                 2
Records Written:                      2
I uploaded only one record but it reads as 2 records and can not figure out why 2 records?
Also when I checked display converted data , it shows 2 records .
First record shows
TCODE         Transaction Code                                             IE01
RECORDNAME    IBIP: Name of the Data Transfer Record                       IBIPEQUI
EQUNR         Equipment Number
DATSL         Date valid from                                              05072010
EQTYP         Equipment category                                           H
EQKTX         Description of technical object                              PNEUMATIC PIPE BENDER
BEGRU         Technical object authorization group
EQART         Type of Technical Object                                     MECH-PRESS
GROES         Size/dimension                                               1000X500X1500MM
INVNR         Inventory number
BRGEW         Gross Weight     : IBIP Character Structure                  50
GEWEI         Weight Unit                                                  KG
ELIEF         Vendor number
ANSDT         Acquisition date
ANSWT         Acquisition Value: IBIP Character Structure
All the fields following this , are blank.
2nd record shows
TCODE         Transaction Code                                             IE01
RECORDNAME    IBIP: Name of the Data Transfer Record                       IBIPEQUI
EQUNR         Equipment Number                                             2009
DATSL         Date valid from
EQTYP         Equipment category                                           S
EQKTX         Description of technical object                              1006324
BEGRU         Technical object authorization group
EQART         Type of Technical Object
GROES         Size/dimension                                               20100406
uploaded values are jumbled in 1st and 2nd record.
Hope to receive your valuable ideas for finding out the reason and corrective action required.
Rgds,
Rajesh
I
Edited by: Rajesh63 on Jul 6, 2010 10:37 PM

Direct Input Programs in SAP

Hi,
Can anybody provide me the list of Direct Input programs available in SAP.
Thanks,
Sunil.

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
Regards
Kiran Sure

LSMW Direct Input Method - Change Documents

Hello experts,
Could anyone please tell me how to enable the change documents(not just runtime) for LSMW direct Input method? There is also one option "Change Documents" in the last step of the process, will this write into any table that I see the changes later If I run the last step with selected this option? If yes, What are the application (customer master data, vendor master data, material master data, etc) specific tables?
Is there anyway that I could populate this method changes into the CDHDR & CHPOS tables?
SAP documenation on this:
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
http://help.sap.com/erp2005_ehp_04/helpdata/EN/fa/097174543b11d1898e0000e8322d00/content.htm
Since this tool writing data into database tables directly skips the CDHDR & CDPOS recording..
Is there any other possible way for the complete change logs (change pointers???)? ( Or only table logging?)
Please share your experience on this.
Thanks,
Himadama

No response received..

LSMW - Direct Input - Sales order - item texts

Hi Gurus,
To transfert all orders from old system to new SAP system, I make this with LSMW and program RVINVB10.
The creation of header and item of orders is good but I have a problem with item texts.
In LSMW, I have create one structure et I have affected this to the struct BTEXHKOM and BTEXLKOM.
In BTEXHKOM, the field LAISO = 'FR' and TDID='ZM03' (Id of customer text).
In BTEXLKOM, the field TXTPARAGRAPH='/' and TXLINE='BLABLABLABLA' (no more 72 char).
In actions 'Read Data' and 'Convert Data', I see this two structs. But after execution of Direct Input program, I don't see text in my item of sales order.
I think I miss something.
Can you help me ???
Thanks a lot
Laurent Guilloteau

Hi Laurent Guilloteau,
I am facing a similar issue.
We are trying to upload sales order data using LSMW Standard Batch/Direct input using program name RVINVB10 and program type D. We are not able to upload item text but we are not having any problem in uploading remaining data.
the details we are passing to BTEXHKOM structure are......
BTEXHKOM-OLDNR = IHEADER-OLDORD_NO.
BTEXHKOM-LAISO = 'EN'.
BTEXHKOM-TDID = 'Z009'.
and the for structure BTEXLKOM
BTEXLKOM-OLDNR = IHEADER-OLDORD_NO.
BTEXLKOM-TXPARGRAPH = '/'.
CONCATENATE LITEM-DEPTID LITEM-DEPTNAME
INTO BTEXLKOM-TXLINE SEPARATED BY ' '.
we have three input source structures.
IHEADER                Header structure
LITEM                     Line item structure ( Material data )
IPARTN                   Partners structure
The structure relationships are
BTEXHKOM <<< IHEADER.
BTEXLKOM <<< IHEADER.
Please let me know if I am doing some thing wrong or some thing else need to be done.
Thanks,
Chindam.

LSMW - Direct Input for XD01

Hi All,
I m facing a problem in LSMW - direct input for XD01Transaction (Create Customer).
while testing the file from Application server using BATCH INPUT SESSION. At the end, my Session fails and it shows an error in the log "Function code cannot be selected" and under that line 1 more comment is there - "Transaction Error".
please help me in this issue.
Edited by: Rahul Gautam on Sep 17, 2008 1:53 PM
Edited by: Rahul Gautam on Sep 17, 2008 2:25 PM

Hi
I found the Solution
Thanks

LSMW using Direct Input

Hi,
can anyone tell me in details how to create lsmw using direct input and using BAPI?
please let me know.

Hi,
Refer this link..
LSMW using Direct Input
http://learningabap.wordpress.com/2007/03/28/step-by-step-guide-for-using-lsmw-to-update-customer-master-records/
Using BAPI..
http://www.****************/Tutorials/LSMW/BAPIinLSMW/BL1.htm
Regards
Sowmya

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

Customer direct input

Similar Messages

Maybe you are looking for