LSMW Routing- Standard Batch Input BDC_INSERT, screen .&. is invalid

Hello All,
I am preparing LSMW for routing upload along with inspection characteristics with standard batch input method.
At the time of 'Create batch input session' I am facing an error 'BDC_INSERT, screen .&. is invalid'.
I have checked the forums for the same issue but it wasn't fruitful. However I cam across one thread which mentions to ensures the data in falt file, which I did checke and confirmed.
What could be the reason?
Awaiting your replies...
Mimiri

Hello all.
I was facing the same problem.
To solve,I filled BI001-TCODE with 'QP01' (constant) in Maintain Field Mapping and Conversion Rules.
I know, this is a old question, but when I was searching I didn't find anything with this.
Regards.
Cássio Oliveira

Similar Messages

  • LSMW Routing Standard Batch Input Create Batch Input Session

    Hello All,
    I am using LSMW for routing upload, using standard batch input method. Program RCPTRA01.
    I am facing this quite peculiar problem.
    I have tried first with separate text file for every source structure. Everything works fine till convert data step.
    But when I go for 'Create Batch Input Session' it creates session for tables MAPL, PLKO, PLPO, PLMZ, PLMK. Other tables remain balnk (EAPL, PLFL, PLAB, PLFH, PLPH, PLFT, PLFV, PLWP). Because of this while running the session only the header and material assignment to task list get uploaded. Rest data, operation, MIC, component allocation do not get uploaded.
    I have also tried for one text file for multiple structure. In that I face porblem for BDC creation. While debugging I faced th same thing in this also.
    Could anyone please explain me the soution for this? Do I need to amend any progrm fior this?
    Expecting lightning fast replies from Gurus....
    Mimiri

    Hello All,
    I am awaiting your reply on this.......
    Mimiri

  • Standard batch input program for Routing

    Hi,
    Please inform me if there is any standard batch input program for uploading routing data.
    Regards
    Ramakanth

    Hi
    Pls check RCPTRA00

  • LSMW Standard Batch Input Program

    Hi,
    I have one requirement on creating BOM.
    I have to upload data from legacy system to SAP for T-Code ' CS01'
    I have to use the Standard Batch input Program 'RCSBI010'.
    I have source structure and Target Structure.
    In Source structure i have Header and item data.
    In Header i have 11 fields and in Item i have 23 fields.
    In Target Structure i have upto 130 fields.
    In the Standard program who have 4 structures and each structure have fields.
    So How many  fields i have to map with Standard structure. and in my source structure i dont have the fields like T-code, session name, user name,and xkeep.
    So how to pass these fields (T-code, session name, user name,and xkeep) to the standard structure. and is it necessary to pass these fields to the standard batch input program.
    Advance thanks,
    Kumar A

    Hi,
        Hi,
    Record type 0: one session record (structure BGR00) per session..
    The session header contains general administrative data on the batch input session to be created. All records that follow the header in the sequential file are assigned to the current session, until the next header occurs in the file.
    Record type 1: one session record (structure BICSK) for each BOM
    The BOM header record contains the transaction code (for example, CS01 Create material BOM) and the header data
    Record type 2: one item record (structure BICSP) per item
    All BOM item records are assigned to the preceding BOM header, until the next BOM header or session header occurs in the sequential file
    Record type 3: one sub-item record (structure BICSU) per sub-item
    All BOM sub-item records are assigned to the preceding BOM item, until the next item header, BOM header, or session header occurs in the sequential file
    and x-line which will be used as index while retreiveing
    and the file to be imported should contain values in this format
    BGR00 data will be in first line (0-stype)
    BICSK in second line (1 stype)
    BICSP in 3rd line
    BICSU in 4th line
    e.g:
    0 sessname 800
    1 CS01 123
    2 values req
    3 values req
    Hope this gives u some idea...
    <b>Reward points</b>
    Regards

  • Standard Batch Input Programs for Profit Center Creation

    Dear all;
    I am in 4.0B version that doesnt have BAPI_PROFITCENTER_CREATE. Writing a BDC for this would be complicated as my data is compiled in a different way.
    Are there any Standard Batch Input Programs for Profit Center Creation ?

    Hi Srivathsan,
    You can make use of  Standard BAPI by LSMW.
    Business Object   BUS1116      Profit Center Group
    Method                CREATE                      Create
    Message Type      PROFITCENTERGROUP_CREATE   
    Basic Type           PROFITCENTERGROUP_CREATE
    Regards,
    Sivaram.

  • Standard Batch Input

    Hi Sap Gurus,
    I just want to know, can we upload mass data to product catalog using standard batch input sessions ie using tcode-sm35.if yes then how?
    Please help me.
    I will definitely reward points..
    Thanks in advance.
    Regards,
    Shweta

    Hi Srivathsan,
    You can make use of  Standard BAPI by LSMW.
    Business Object   BUS1116      Profit Center Group
    Method                CREATE                      Create
    Message Type      PROFITCENTERGROUP_CREATE   
    Basic Type           PROFITCENTERGROUP_CREATE
    Regards,
    Sivaram.

  • No batch input data screen SAPLSDH4 0200

    Hi,
    While doing Check deposit transaction, i got the below error
    " No batch input data screen SAPLSDH4 0200". When i press enter, it is going to FS01 screen and showing the customer number as * =D.xxxx (customer number)*  and a dialogue box is appeared, in that search item and customer number is displayed. When i press enter, it is not accepting. When i clear it and press enter, it is showing all customers. I have selected the customer which i gave at the time of customizing and press enter. Then it is showing the "OK code" again selected ok.. Then the batch process competed. But when i go to SM35, i cant able to see the session again.
    I dont understand why this problem is coming. But the posting were done properly. Can anyone explain me what exactly the problem with this transaction.
    Regards
    Sabera

    Hi,
    These error normally comes if the screen control branches out to different view or a screen.If a session is created for error logs, process the session in foreground mode and see at which point the OK CODE branches out to this particular screen. you also need to debug the particular record which is failing to see if its a data related issue or any particular field value is being wrongly processed. If your program is not creating any session for error logs i request you to generate a session for error logs or else if you are using call transaction ,run it in MODE 'A' to check whats happening.It's quite common to come accross such issues while developing a BDC.

  • Batch Input Overview Screen

    Hi All,
               Some of my Mlis mirrors posting files uploaded are not found in the Batch input Overview screen . For example, files named KJCFS3101, KJCDM2701, and all named KJCDM****  .How can I retrieve them.
    Brgds
    Asha Banu A

    Hi Chakra,
    Please explain your requirement further.
    1. A program creates SM35 sessions. A periodic job is defined for that.
    2. Another program or a person processes those sessions.
    3. A third one should be scheduled to run right after that.
    If my assumption is true, I have some questions about it. How are the sessions processed? Are they manually processed or are they scheduled in batch processing?
    I have a couple of scenarios in mind.
    <u>Scenario 1.</u>
    1. One program creates the sessions and also processes them by using RSBDCSUB program. This program will be scheduled as step 1 of the job.
    2. Program 2 will be scheduled as step 2 of the job.
    <u>Scenario 2.</u>
    1. One program creates the sessions. This will be step 1 of the job.
    2. RSBDCSUB will be scheduled as step 2.
    3. Program 2 will be scheduled as step 3.
    <u>Scenario 3.</u>
    1. One program takes of creating the sessions, then submitting the RSBDCSUB to process and then submits the program2. You can then schedule one job for this one program.
    If you can give more details of your requirement may be I can help.
    Regards,
    Srinivas

  • LSMW for routing with standard batch input

    Hello All,
    I am trying to prepare one LSMW for routing upload for PP module. Routing data contains header data, operation data and master inspection characteristics data.
    I have created three source structures viz. material- task list header, task header data, operation and inspection.
    Header has been assigned to target structure BIMPL- Batch Input Structure for Allocation of Mat. to Task Lists,
    Task header data source structure has been assigned to BIPKO- Batch Input Structure for Task List Header,
    Operation source structure has been assigned to target structure BIPPO- Batch input structure for task list operation,
    and inspection source structure has been assigned to BIPMK- Inspection characteristics for batch input of task lists.
    Every source structure has been identified with an identifier value of which have been set as H, I,J,K for all source structures resp.
    The excel file has been prepared as follows,
    H     MATNR     WERKS     PLNNR     PLNAL               
    H     100045     1000     50000043     1               
    H     100045     1000     50000043     2               
    I     MATNR     WERKS     PLNNR     PLNAL     VALID_FROM     USAGE     STATUS
    I     100045     1000     50000043     1     01012000     1                1
    I     100045    1000     50000043     2     01012000     1                 1
    I have mentioned here the combination of first two structures only. But it contains data of other two source structures as well (for identifier J & K).
    The data from the excel is copied to the flat file and same is specified in LSMW in the step 'Specify file'.
    In 'Assign file' step the flat file is assigned to all the four source structure.
    Now at the time of reading data system is throwing me an error as 'Ensure field sequence is correct for data for mutiple source structures' Message no. /SAPDMC/LSMW_OBJ_060026
    How to overcome this?
    <removed by moderator> answers will be greatly appreciated........
    Mimiri
    Edited by: Thomas Zloch on Jul 11, 2011 10:16 AM

    Hello ,
    have you maintained this check box for the key fields"
    LSMW>Maintain Source fields>double click on fieds : MATNR WERKS PLNNR PLNAL
    Selection Parameter for "Import/Convert Data"-->Tick this check box
    regards

  • FLB2 - Lockbox Screen Error: "No Batch Input for screen SAPDF05X 3100"

    I'm not familiar with Lockbox processing ... was asked to help debug an error & not having much luck doing so.
    When processing a file via FLB2, we have one customer for which the postings work fine.  For another customer, however, we get an error:
    "Accounts receivable posting Error: (00 344) No batch input data for screen SAPDF05X 3100."
    I've checked multiple Notes & postings on SDN, still at a loss and getting no closer troubleshooting within the system.
    Can anyone offer ideas of what to check?
    Thanks,
    John

    Hi,
    I believe the problem should be in the input file. There should an error in the file. Can you create a one line item file for the Customer and processs it. If the Lockbox is working for one Customer it should work for all Customers. Secondly, check whether Lockbox is maintained for the Customer in the master data.
    Thanks
    Murali.

  • No Batch Input for Screen 0300

    Hello
      I am doing an inter-company asset transfer using ABT1(Call Transaction).
      However for few assets its giving me the error as 'No Batch input found for screen' '0300' even though
      the message type in MESSTAB table is 'S'.And one I run the program again for same asset it works   properly.
        PERFORM 450_DYNPRO USING:
                   'X' 'SAPLAMDP_OLD' '0100',
                   ' ' 'RAIFP1-BLDAT'  L_SYDATE,          " Document Date
                   ' ' 'RAIFP1-BLART'  'AA',              " Document Type
                   ' ' 'RAIFP1-BUDAT'  L_PSTDAT,          " Posting Date
                   ' ' 'RAIFP1-TRAVA'  P_VAR,             " Transfer Variant
                   ' ' 'RAIFP1-BZDAT'  L_BZDAT,           " Asset Value Date
    Posting Specifications
                   ' ' 'RAIFP2-BUKRS' PWA_ASSET-BUKRS,    " From Company
                   ' ' 'RAIFP2-ANLN1' PWA_ASSET-ANLN1,    " Asset
                   ' ' 'RAIFP2-ANLN2' '0000',             " Sub Asset No
    To
                ' ' 'RAIFP3-BUKRS' P_BUKRTO,              " To Company from i/p screen
                   ' ' 'RAIFP3-XNANL' 'X',                " New Asset
    Revenue
                   ' ' 'RAIFP2-XERBW' 'X',                " NBV from area button
                   ' ' 'RAIFP2-AFABE' '01',               " Default 01
                   ' ' 'BDC_OKCODE' '/00',                " Enter
    *Second Screen
                   'X' 'SAPLAIST'    '2110',
                   ' ' 'ANLZ-KOSTL'  P_KOSTL,        " Cost Center
                   ' ' 'BDC_OKCODE' '=DETA'.         " Push  additional data
    Enter allocations tab Common for ABT1 and AS11 transaction
        PERFORM 450_DYNPRO USING:
          'X' 'SAPLAIST'    '1000',
          ' ' 'BDC_OKCODE'  '=TAB03',          " Go to Allocations tab
          'X' 'SAPLAIST'    '1000',
          ' ' 'ANLA-GDLGRP' P_GDLGRP,          " Enter value for eval. Grp 5
          ' ' 'BDC_OKCODE' '=TAB08'.
    In the screen create
        PERFORM 450_DYNPRO USING:
          'X' 'SAPLAIST'    '1000',
          ' ' 'BDC_OKCODE'  '=RW'.              " Go back to Second screen
        PERFORM 450_DYNPRO USING:
          'X' 'SAPLAIST'    '2110',
          ' ' 'BDC_OKCODE'  '=CREA',            " Create the transaction
       'X' 'SAPMSSY0'    '0120',
       ' ' 'BDC_OKCODE'  '=&ONT',
    Save the transaction
          'X' 'SAPLAMDP_OLD' '0100',
          ' ' 'BDC_OKCODE' '=SAVE'.
    Could anyone pls help in knowing me whats the problem?
    Thanks and Regards

    I think U need to handle screen 0300 .. and need to pass
    data ('No Batch input found for screen' '0300' )

  • Batch-input and screens

    Hi,
    I have one program, that calls VA03 and print Billing document immediately.
    Now they want stop batch-input at Issue output screen, and after they fill the options that want and continue the program.
    Can you tell me if it is possible?? And if yes,what is the soluction for this?
    Thanks ina advance.
    All ideas are welcome.

    I found one solution.
    Batch-input code:
    t-code = 'VA03'.
      REFRESH bdcdata.
      PERFORM bdc_dynpro      USING 'SAPMV45A' '0102'.
      PERFORM bdc_field       USING 'BDC_OKCODE' 'DRCK'.
      PERFORM bdc_field       USING 'VBAK-VBELN' tab-vbeln.
      PERFORM bdc_dynpro      USING 'SAPLVMSG' '0200'.
      PERFORM bdc_field       USING 'BDC_OKCODE' '=OPTS'.
    CALL TRANSACTION 'VA03' USING bdcdata MODE 'E'
                            UPDATE 'S'
                            MESSAGES INTO messtab.
    Thank you by all helps.
    Ana

  • LSMW Standard/Batch Input Method

    Hi,
             I am trying to learn LSMW. Can anybody pls tell me what is the meaning of Object & Method in Standard Input method in LSMW? I am having one example of LSMW for updating vendor master. The Object & Method used in this document are 0040 & 0002 respectively. How do I get these nos. like 0040 for vendor master. can you pls explain the meaning of this.
    Thanks & Regards
    Swati Ghadge.
    Moderator Message: These are not training forums. Take a classroom course if you need help.
    Edited by: kishan P on Oct 12, 2010 2:52 PM

    It is quite simple. Header structure reproduces the contents of fields in table STXH.
    Find out which is the object and the text id.
    How? Create the text manually in the online transaction and check on table STXH what is the object and text id created by using date and user name.
    Then you can go on by following the steps on this blog
    http://scn.sap.com/community/erp/logistics-mm/blog/2012/12/28/lsmw-long-text-load-by-direct-input-method

  • XK01 -- Batch Input Program Screen Sequence Issue

    Guyz,
    I created a recording in shdb for xk01 and generated the program from shdb itself and modified the program (both selection screen & processing logic).... suprisingly, when i execute the program, screen sequence is different when compared to the sequence from shdb recording..... i even downloaded the BDCTABLE contents during debugging and compared with recording in SHDB which is fine....
    any pointers ?
    after filling lifnr, bukrs & account group on initial screen of xk01, usually NAME & ADDRESS details screen comes up in online and SHDB recording, but during program execution in 'ALL SCREEN' & 'SYNCHRONOUS' mode (call transaction), i'm getting first screen (as expected) but its skipping NAME & ADDRESS details screen and thus my program getting stuck?
    appreciate your pointers.....
    thanks

    On the first screen, you have to set a check-box that is normally hidden:
        perform dynpro
          tables bdcdata
          using:
         'X' 'SAPMF02K'     '0105',         "Create Vendor: Initial Screen
          ' ' 'RF02K-BUKRS'             '0001',
          ' ' 'RF02K-KTOKK'             'ZZZZ',
          ' ' 'USE_ZAV'                 'X'.         "<=======Here
    This will cause the program to use the screen in Central Address Management.
    I also think you will probably use screen 0100 rather than 0105 that I have used above.
    Rob
    Message was edited by:
            Rob Burbank

  • 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

Maybe you are looking for