Interface between Legacy and SAP for Equipment Master

Question

Hello
I got a requirement where I need to develop a interface between legacy system and R/3 system for Equipment Master Data update in R/3. I am thinking of getting a Idoc file from Legacy and then update the changes or any new creation of Equipments in R/3. I found a standard BAPI for this BAPI_EQUIPMENT_CREATE/CHANGE. This BAPI use a strcture BAPI_ITOB for data record of IDoc. But I got more data from legacy except what we have in BAPI_ITOB. I got Partner Data, Classification data also for Equipments. I am thinking of copying the BAPI to a Z function module and modify the Idoc structure , message type and all to capture all the data and then do a update in same way as standard transaction IE01(Equipment Create) is doing in Batch Input. Do you think if there is any better way of doing this? I am not used to transaction BAPI . just wondering if we Can use that in someway to include our modification?
Thanks
Harkamal

Answer 1

20,000 is on quite higher side for IDOC.
IBIP help doc says it needs 2 Kbyte for each record, i.e. 40 Mb for 20,000 rec. that should be ok. Since it has structures for Partner & classification data , I don't think u need to modify the BAPI.
Transaction IE01 - Create equipment
Transaction IE02 - Change equipment
Structure - IBIPEQUI Equipment record
                 |->    IBIPNSTA     New status profile if necessary
                 |->>   IBIPSTAT     User status records
                 |->>   IBIPDOCU     Doc. from Doc. management system
                 |->>   IBIPPART     Partner details (comment below)
                 |-->>  IBIPTEXT     (see comment below)
                          for long text:          TEXT_MARK = " " empty
                          for internal comment:   TEXT_MARK = "1"
                 |-->>  IBIPCLAS    Classification record (eqpmt class)
                     |-->> IBIPFEAT     Classification characteristics,
                                           ie. features for the class
                 |-->>  IBIPBDCD     see below (from screen 102)