Error detail in data migration?

Hi all,
I'm migrating an Access database to Oracle using SQL Developer and the migration workbench.
When I run the data migration, it almost all works, but one table has one error.
I get a list of tables, with rows, total rows, errors and total errors.
Only one error is reported in the summary. 2208 out of 2209 records migrated in this table.
How do I find out what the problem is?
Is there a log anywhere?
Is the data migration script visible anywhere?
Thanks,
Greg H

Hi Dermot,
It turns out there's some corrupt data in the Access database. That or it's in a language that I don't have installed on my machine.
Access displays it as a bunch of squares.
I guess if Access can't figure out how to display it, it would be unreasonable to expect a migration tool to.
The Export Table Data failed with "error #5 Invalid procedure call or argument" and did not create the file for this table.
I'll send this one record back to the business and let them figure out which record it is and if it's important.
Thanks for your help,
Greg H

Similar Messages

Error handling in DATA MIGRATION

hi
i am a beginner in sap abap. i am learning data migration techniques . so i wanted to know that what are the possible error in bdc and lsmw apart from error of data in flat file.And how handle those errors. if anyone can share his/her experience based on real time projects then it will be very helpful.
thanks'
akash

Hi
That depends on how you load the data in the system
It can think there are two ways to upload the data:
- Asynchronous: the data are picked up (from file) and loaded in different sessions (for example: a program read data from file and then prepare a BDC session)
- Synchronous: the data are picked up and loaded in the same session (for example a program read data from file and load them by BAPI)
In the first solution you can't know if a record is ok or not ok you need to elaborate it by BDC session: so here yuo need to decide what to do,
The BDC session keeps the wrong transaction so you can elaborate it manually (anyway it's better to be sure the file is correct before creating a BDC session)
In the second case you can use many soltuon because you can know if a record is ok or not after running BAPI, so (for example) you can generate a new file with the wrong record only, in order to try to elaborate it again.
Max

Error Message during Data Migration.

Hi All,
I have to migrate data for opportunity. I read the data and passed it to "BAPI_BUSPROCESSND_CREATEMULTI". This FM returns a message i.e. "A log has been generated for single document". When i am passing the GUID to FM "BAPI_BUSPROCESSND_SAVE" it is giving an error message i.e. "The document could not be saved".
I am not able to find why it is not saving that GUID. if anyone has any idea or if you the sample code then please reply.
      CALL FUNCTION 'BAPI_BUSPROCESSND_CREATEMULTI'
        TABLES
          HEADER               = lt_bapibus20001_header_ins
          OPPORTUNITY      = lt_bapibus20001_opportunity
          INPUT_FIELDS     = lt_bapibus20001_input_fields
          PARTNER            = lt_bapibus20001_partner_ins
          STATUS               = lt_bapibus20001_status_ins
          RETURN             = lt_bapiret2.
      lw_objects_to_save-guid = lv_guid.
      APPEND lw_objects_to_save TO lt_objects_to_save.
      CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
        EXPORTING
          update_task_local = space
          save_frame_log    = GC_X
        IMPORTING
          LOG_HANDLE        = LOG_HANDLE
        TABLES
          objects_to_save   = lt_objects_to_save
          saved_objects     = lt_saved_objects
          return            = lt_bapiret2.

I was going through the log and there is an error 250 in there too.

Error in asset data migration thru LSMW

Hi u all,
i have an issue while running an lsmw for asset data loads here, when i did it in foreground it saves the asset but when i run it in background its erring out
i am doin it thru as91 whichis legacy transfers the error is
Field RALT_DYNP_STRUC-ANBTR02(7) is not an input field AS91 1 SAPLALTD 1100 14 S 00 347
Field RALT_DYNP_STRUC-ANBTR03(7) is not an input field AS91 1 SAPLALTD 1100 14 S 00 347
this ANBTR02(7) n ANBTR03(7) are the *** spl dep fields for TAX and AMT in the takeover values tab,where we were giving the values of spl dep (Bonus value which is taken off in the acquisition yr)
all is goin good in foreground but its giving the error whichi pasted above saying ..is not an input field, when i did it in background not able to figure out...
Any help would be really grateful and appreciated......Thanka a lot in advance.

Hi Nathan,
as i mentioned earlier, it goes smooth when it is done manually or lsmw foreground, and answering to ur ques'n yes the fields are open. i am getting the error when i do it in batch input....
Thanks ya
Jay

Best practice for data migration install v1.40 - Error 2732 Directory manag

Hi
I'm attempting to install SAP Best Practice for Data migration 1.40 on Win Server 2008 R2 (64 bit).
Prerequisite error
Installation program stops with missing file error
The following file was not found
... \migration\InstallationWizard\BusinessObjects Data Services\setup.exe
The file is necessary for successful installation. Please connect to internet or refer to Quick Guide (available on SAP note 1527151) for information regarding the above file.
Windows installer log displays
Error 2732 Directory Manager not initialized
SAP note 1527151 does not exist or is internal.
Any help appreciated on what is the root cause of the error as the file does not exist in that folder in the installation zip file.
Other prerequisite of .NET 3.5.1 met already.
Patch is released since 20.11.2011 so I presume that it is a good installation set.
Thanks,
Alan

Hi Alan,
There are details on data migration v1.4 installations on SAP website and market place. The below link should guide to the right place. It has a power point presentation and other useful links as well.
http://help.sap.com/saap/sap_bp/DMS_V140/DMS_US/html/index.htm
Arun

HT4796 windows migration assistant has errors in preparing data on my PC

Hi,
just got my new iMac and want to migrate files from my Windows XP machine using Windows Migration Assistant for Lion. It seemed to install OK on the PC but it will not run. It comes up with an message saying found errors in preparing data. Any ideas?
Peter

Are you using wifi to migrate?

Error in Data Migration

Hi Experts,
We are Trying to upload Journal entry datas from SAP Business one Data Migration Tool.
We have maintained Header and Item Templates.
But System is giving a error which is having following Description.
Key JdtNum iS Too short,error 65171.
Can anyone please help us in overcoming the problem?
Thanks in advance

Hi Ravi,
Please check this thread to have some ideas:
Re: DTW journal entry problem for many line accounts
Thanks,
Gordon

Error in updationg the opportunity in data Migration program

Hi,
I am getting an error in updationg the opportunity in data Migration program. I am using
CALL FUNCTION 'BAPI_BUSPROCESSND_CHANGEMULTI'
          TABLES
            HEADER        =    li_header
            ITEM          =        lt_bapibus20001_item
            OPPORTUNITY   = lt_bapibus20001_opportunity
            INPUT_FIELDS = lt_bapibus20001_input_fields
            PARTNER       = lt_bapibus20001_partner_ins
            STATUS        = lt_bapibus20001_status_ins
            PRICING       = li_pricing
            TEXT          = li_text
            RETURN        = lt_bapiret2.
after save when it is to be commited. I am getting the following error.
Express Document: Updation terminated author by "XYZ"
Thanks in advance.

HI Piyush,
Tyr to use CRM_order_maintain. If you are trying to change partner,pricing,status,header,item then ORDER_MAINTAIN is the good one to use.
Its very easy to identify the parameters that need to be populated for this FM

Error message while doing data migration

Hi all
When im doing data migration for material master through Z transaction ,it is updating global DIR documents for material while doing this ,im getting the error and the transaction is stopped intermediately the error message is CHANGE MASTER STATUS DOES NOT ALLOW CHANGES no error message number.
Kindly sujjest where is that error is coming,it would be very helpful

It seems you are using engineering change management and your change number's status is not proper (CC01, CC02, CC03; table AENR).
Configuration of the status is in T419S (use SM30 + T419S) - but I guess the problem is about your change number not about config...
How your Z-program is working, we don't know; contact the responsible functional/technical consultants.
Edited by: Csaba Szommer on Aug 19, 2011 8:41 AM

Capturing the details of data in which error occured during uploading

Hi, anyone tell me how to Capturing the details of data in which error occured during uploading the file using BDC in backgroung mode. Please do the needful
Thanks & Regards.
Aniruddha

hi,
This declaration is used to capture the error msg. V is the std table that captures that.i have given a sample code with this..pls chk it out..
data: err type standard table of bdcmsgcoll with header line.
SAmple code:
report z_aru_bdc_new4
       no standard page heading line-size 255.
include bdcrecx1.
Generated data section with specific formatting - DO NOT CHANGE ***
parameters: p_file like rlgrap-filename obligatory.
data: err type standard table of bdcmsgcoll with header line.
data: mess(200) type c.
data: begin of it_err occurs 0,
msg(200) type c,
end of it_err.
data: begin of record occurs 0,
data element:
        viewname_001(030),
data element: VIM_LTD_NO
        ltd_dta_no_002(001),
data element: ZEMPID3
        zempid3_003(004),
data element: ZENAME3
        zename3_008(040),
data element: ZEDEPID
        zedepid_009(004),
data element:
        zsalkey_010(005),
data element:
        salary_011(013),
data element: ZENAME3
       ZENAME3_008(040),
data element: ZEDEPID
       ZEDEPID_009(004),
data element:
       ZSALKEY_010(005),
data element:
       SALARY_011(013),
      end of record.
End generated data section ***
start-of-selection.
at selection-screen on value-request for p_file.
call function 'WS_FILENAME_GET'
exporting
DEF_FILENAME           = ' '
DEF_PATH               = ' '
   mask                   = '.,..'
   mode                   = 'O' " O -- open, S -- Save.
   title                  = 'OPEN'
importing
   filename               = p_file
RC                     =
exceptions
   inv_winsys             = 1
   no_batch               = 2
   selection_cancel       = 3
   selection_error        = 4
   others                 = 5.
start-of-selection.
call function 'UPLOAD'
exporting
CODEPAGE                      = ' '
   filename                      = p_file
   filetype                      = 'DAT'
ITEM                          = ' '
FILEMASK_MASK                 = ' '
FILEMASK_TEXT                 = ' '
FILETYPE_NO_CHANGE            = ' '
FILEMASK_ALL                  = ' '
FILETYPE_NO_SHOW              = ' '
LINE_EXIT                     = ' '
USER_FORM                     = ' '
USER_PROG                     = ' '
SILENT                        = 'S'
IMPORTING
FILESIZE                      =
CANCEL                        =
ACT_FILENAME                  =
ACT_FILETYPE                  =
tables
    data_tab                      = record
exceptions
   conversion_error              = 1
   invalid_table_width           = 2
   invalid_type                  = 3
   no_batch                      = 4
   unknown_error                 = 5
   gui_refuse_filetransfer       = 6
   others                        = 7
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
*perform open_dataset using dataset.
*perform open_group.
delete record index 1.
loop at record.
*read dataset dataset into record.
*if sy-subrc <> 0. exit. endif.
perform bdc_dynpro      using 'SAPMSVMA' '0100'.
perform bdc_field       using 'BDC_CURSOR'
                              'VIEWNAME'.
perform bdc_field       using 'BDC_OKCODE'
                              '=UPD'.
perform bdc_field       using 'VIEWNAME'
                              record-viewname_001.
perform bdc_field       using 'VIMDYNFLDS-LTD_DTA_NO'
                              record-ltd_dta_no_002.
perform bdc_dynpro      using 'SAPLZSHAP' '0001'.
perform bdc_field       using 'BDC_CURSOR'
                              'ZEMPTAB1-ZEMPID3(01)'.
perform bdc_field       using 'BDC_OKCODE'
                              '=NEWL'.
perform bdc_dynpro      using 'SAPLZSHAP' '0002'.
perform bdc_field       using 'BDC_CURSOR'
                              'ZEMPTAB1-SALARY'.
perform bdc_field       using 'BDC_OKCODE'
                              '=SAVE'.
perform bdc_field       using 'ZEMPTAB1-ZEMPID3'
                              record-zempid3_003.
perform bdc_field       using 'ZEMPTAB1-ZENAME3'
                              record-zename3_008.
perform bdc_field       using 'ZEMPTAB1-ZEDEPID'
                              record-zedepid_009.
perform bdc_field       using 'ZEMPTAB1-ZSALKEY'
                              record-zsalkey_010.
perform bdc_field       using 'ZEMPTAB1-SALARY'
                              record-salary_011.
perform bdc_dynpro      using 'SAPLZSHAP' '0002'.
perform bdc_field       using 'BDC_CURSOR'
                              'ZEMPTAB1-ZENAME3'.
perform bdc_field       using 'BDC_OKCODE'
                              '=UEBE'.
perform bdc_field       using 'ZEMPTAB1-ZENAME3'
                              record-zename3_008.
perform bdc_field       using 'ZEMPTAB1-ZEDEPID'
                              record-zedepid_009.
perform bdc_field       using 'ZEMPTAB1-ZSALKEY'
                              record-zsalkey_010.
perform bdc_field       using 'ZEMPTAB1-SALARY'
                              record-salary_011.
perform bdc_dynpro      using 'SAPLZSHAP' '0001'.
perform bdc_field       using 'BDC_CURSOR'
                              'ZEMPTAB1-ZEMPID3(01)'.
perform bdc_field       using 'BDC_OKCODE'
                              '=SAVE'.
perform bdc_dynpro      using 'SAPLZSHAP' '0001'.
perform bdc_field       using 'BDC_CURSOR'
                              'ZEMPTAB1-ZEMPID3(01)'.
perform bdc_field       using 'BDC_OKCODE'
                              '=BACK'.
perform bdc_dynpro      using 'SAPMSVMA' '0100'.
perform bdc_field       using 'BDC_OKCODE'
                              '/EBACK'.
perform bdc_field       using 'BDC_CURSOR'
                              'VIEWNAME'.
perform bdc_transaction using 'SM30'.
*enddo.
*perform close_group.
*perform close_dataset using dataset.
endloop.
loop at it_err.
write : / it_err-msg.
endloop.
form error.
call function 'FORMAT_MESSAGE'
exporting
   id              = sy-msgid
   lang            = '-D'
   no              = sy-msgno
   v1              = sy-msgv1
   v2              = sy-msgv2
   v3              = sy-msgv3
   v4              = sy-msgv4
importing
   msg             = mess
exceptions
   not_found       = 1
   others          = 2
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
it_err-msg = mess.
append it_err.
clear it_err.
endform.
If it is session method u can find the session in SM35 from where u can get the error log.
Hope this helps u,
Regards,
Arunsri

Details of Test Data Migration Server(TDMS)

Hi Friends,
I am very much interested in the new tool Test Data Migration Server(TDMS).Can anyone of u r aware of this tool.i had a detailed search in google & SAP sites.But i could not find much information.Plz help me out in finding about this tool.
Thanx
Rajeev

Hi Rajeev,
There are documents available on these pages:
Service Marketplace
http://service.sap.com/customdev-tdms
SAP Homepage
http://www.sap.com/services/customdev/tdms
If you have specific questions, just let me know.
Regards,
Manfred

Error in data migration through DTW

Hi All,
      I am creating a template for user define Master data table from DTW, when i am trying to port data by using that template through DTW. it is giving error like--'Master data type User table cannot add row'
So can any one have solution for this.
Regard's
Hari

hi,
object name is U_SCRAPMAST
Code     Name     U_SCD     U_SDSC     U_Status
Code     Name     U_SCD     U_SDSC     U_Status
1          SCR1     SCR1
2          SCR2     SCR2
regard's
Hari

Data Migration from Legacy System in IS-U

Hi All,
We are going to Implement a new IS-U project, I have a problem with LSMW(Legacy System Migration Workbench ), I have some Conversion Objects of IS-U and I need to know whether Data Migration is possible or not, please tell me how to find these Objects and how to know Data Migration is possible or not.
Objects are like.,
1. Accounts
2. Actuate Reports
3. Business Partner Relationships
4. Active Campaigns/Campaign Content/Dispositions
5. Connection Object
6. Contacts
7. Contracts
8. Opportunities
9. Payment Arrangement History
10. Payments
11. Premises
12. Rate Changes
13. Security Deposits
these are few and there are some more..,
Thanks in Advance,
Sai.

Hi Ram,
Use Transaction Code EMIGALL. It will ask for company code. By default Company Code is SAP. If you entered with the SAP you will get all the objects.Then goto menu IS-U Migration-->User Handbook. It will give you details Idea.
Also Check the following Procedure
You can find detailed documentation of EMIGALL in SAP itself. Use Transaction EQ81 to display it. It provides all the concepts and procedures to work with EMIGALL.
Here are some points about EMIGALL :
1. It Migrates data Business Object wise
2. It uses Direct Input Technique
3. It has more than 100 objects of IS-U
and the steps for implementation goes like this:
1)You have to create a user specially for migration which will have all the authorizations related to migration workbench, BASIS and IS-U
2)You have to create your own company in EMIGALL. There is a default company called SAP.
3)Company SAP contains all the Business Objects
4)You have to figure out what business objects u need and then u have to copy those business objects to ur company from Standard Company SAP
5)Each objects contains more than one structure and each structure can contain more than one fields. The relation goes like this
Object ---> Structure ---> Field
6)You have to define field rules for each required field of the object. You have to mark "Not required" for fields u don't need
7)After field rules for a given object is set u have to generate load report i.e. actual Direct Input Program which will migrate data. This program is generated on basis of field rules set by u.
8)After the load report is generated u have to prepare an input file (import File) for migration. The import file should be according to structure provided by SAP and must be in binary format. SAP Provides the structure of file according to your configurations. You have to write ur own Data conversion program(in any language) for this task.
9)You take import file as input and migrate the data using generated load program
10)Finally u can check the Migration Statistics and Error Log
Thanks and Regards,
Jyotishankar Dutta
Message was edited by:
Jyotishankar Dutta
Message was edited by:
Jyotishankar Dutta

Data migration ALE or idocs and bapis

hi ,
thank you guys for the support.
i am into a data migration project.
i need the initial setup for the idocs and bapis.
i dont know anything about these so can u send me the process for the setup and the data migration process too with idocs and bapis.
i didnt understand when they asked me if we can data migrate with a ALE, is that the same as using idocs and bapis or is it a different approach.
u can send me at any inofrmation connected to my eamil addr.
i would really appreciate that.
thank you.

Hi,
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
just refer to the link below
http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
for BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://www.planetsap.com/Bapi_main_page.htm
http://www.topxml.com/sap/sap_idoc_xml.asp
http://www.sapdevelopment.co.uk/
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
Also refer to the following links..
www.sap-img.com/bapi.htm
www.sap-img.com/abap/bapi-conventions.htm
www.planetsap.com/Bapi_main_page.htm
www.sapgenie.com/abap/bapi/index.htm
Checkout !!
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
Example Code
U need to give the step_nr, item_nr, cond_count and cond_type so the correct conditon will be updated. If no condition exists for the given parameters, a new condition will be created.
U can find these parameters for a particular condition type in table KONV.
*& Form saveTransactionJOCR
text
--> p1 text
<-- p2 text
FORM saveTransactionJOCR .
data: salesdocument like BAPIVBELN-VBELN,
order_header_inx like bapisdh1x,
order_header_in like bapisdh1,
return type standard table of bapiret2 with header line,
conditions_in type standard table of bapicond with header line,
conditions_inx type standard table of bapicondx with header line,
logic_switch like BAPISDLS,
step_nr like conditions_in-cond_st_no,
item_nr like conditions_in-itm_number,
cond_count like conditions_in-cond_count,
cond_type like conditions_in-cond_type.
salesdocument = wa_order_information-VBELN.
LOGIC_SWITCH-COND_HANDL = 'X'.
order_header_inx-updateflag = 'U'.
conditions
clear conditions_in[].
clear conditions_inx[].
clear: step_nr,
item_nr,
cond_count,
cond_type.
step_nr = '710'.
item_nr = '000000'.
cond_count = '01'.
cond_type = 'ZCP2'.
CONDITIONS_IN-ITM_NUMBER = item_nr.
conditions_in-cond_st_no = step_nr.
CONDITIONS_IN-COND_COUNT = cond_count.
CONDITIONS_IN-COND_TYPE = cond_type.
CONDITIONS_IN-COND_VALUE = 666.
CONDITIONS_IN-CURRENCY = 'EUR'.
append conditions_in.
CONDITIONS_INX-ITM_NUMBER = item_nr.
conditions_inx-cond_st_no = step_nr.
CONDITIONS_INX-COND_COUNT = cond_count.
CONDITIONS_INX-COND_TYPE = cond_type.
CONDITIONS_INX-UPDATEFLAG = 'U'.
CONDITIONS_INX-COND_VALUE = 'X'.
CONDITIONS_INX-CURRENCY = 'X'.
append conditions_inx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
SALESDOCUMENT = salesdocument
ORDER_HEADER_IN = order_header_in
ORDER_HEADER_INX = order_header_inx
LOGIC_SWITCH = logic_switch
TABLES
RETURN = return
CONDITIONS_IN = conditions_in
CONDITIONS_INX = conditions_inx
if return-type ne 'E'.
commit work and wait.
endif.
ENDFORM. " saveTransactionJOCR
Bdc to Bapi
The steps to be followed are :
1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).
for VA01 use BAPI_SALESORDER_CREATEFROMDAT2
2. Create a Z program and call the BAPi (same as a Funtion module call).
2. Now, if you see this BAPi, it has
-> Importing structures.
eg: SALESDOCUMENT: this will take the Sales order header data as input.
-> Tables parameters:
eg: ORDER_ITEM_IN: this will take the line item data as input.
Note :
Only specify fields that should be changed
Select these fields by entering an X in the checkboxes
Enter a U in the UPDATEFLAG field
Always specify key fields when changing the data, including in the checkboxes
The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
Maintain quantities and dates in the schedule line data
Possible UPDATEFLAGS:
U = change
D = delete
I = add
Example
1. Delete the whole order
2. Delete order items
3. Change the order
4. Change the configuration
Notes
1. Minimum entry:
You must enter the order number in the SALESDOCUMENT structure.
You must always enter key fields for changes.
You must always specify the update indicator in the ORDER_HEADER_INX.
2. Commit control:
The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.
For further details... refer to the Function Module documentation for the BAPi.
Bapi to VB(Visual Basic)
Long back I had used the following flow structure to acheive the same.
Report -> SM59 RFC destination -> COM4ABAP -> VB.exe
my report uses the rfc destination to create a COM session with com4abap. com4abap calls the vb.exe and manages the flow of data between sap and vb exe.
You need to have com4abap.exe
If com4abap is installed you will find it in sapgui installatin directory , C:\Program Files\SAPpc\sapgui\RFCSDK\com4abap.
else refer OSS note 419822 for installation of com4abap
after making the settings in com4abap to point to the vb program and setting up rfc destination in sm59 to point to com4abap session , you can use the following function modules to call the vb code.
for setting up com4abap and rfc destination please refer to the documentation for com4abap.
Invoke NEW DCOM session
call function 'BEGIN_COM_SESSION'
exporting
service_dest = service_dest "(this will be a RFC destination created in SM59)
importing
worker_dest = worker_dest
exceptions
connect_to_dcom_service_failed = 1
connect_to_dcom_worker_failed = 2
others = 3.
call function 'create_com_instance' destination worker_dest
exporting
clsid = g_c_clsid
typelib = g_c_typelib
importing
instid = g_f_oid
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
call function 'com_invoke' destination worker_dest
exporting
%instid = g_f_oid
%method = 'UpdatePDF'
sntemp = g_v_const_filent
snsysid = sy-sysid
snflag = 'N'
tables
rssaptable = g_t_pdfdetail1
%return = g_t_pdfdetail1 "t_test
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
then close the com session , using
FM delete_com_instance
FM END_COM_SESSION
Thanks and regards,
Sarada

Data migration in LSMW with CRM_XIF_PARTNER_SAVE

Hi,
for a data migration of business partners from a legacy system into a CRM 5.0 system I want to use the CRM_XIF_PARTNER_SAVE or CRM_XIF_PARTNER_SAVE_M IDoc. Everything works fine when I migrate a business partner with only one address and only one bank account, but what settings I have to make that I'm able to migrate a business partner with multiple addresses and bank accounts?
I hope you can help me. Thanks in advance,
Timo

Hi Timo,
you need to repeat the corresponding IDoc segements for "Bank Details",
eg for IDoc CRMXIF_PARTNER_SAVE01 (display via WE30 or navigate via BDFG).
here the example for phone data: (I didn't expand all nodes)
CRMXIF_PARTNER_SAVE01    IDoc Structure for Data Type
CRMXIF_PARTNER_SAVE01      IDoc Structure for Data Type CRMXIF_PARTNER_COMPLEX
5 E1010821140028             Complex structure for business partners                 CRMXIF_PARTNER_COMPLEX
4 E1010821140029             Header structure for business partners                  CRMXIF_PARTNER_HEADER
        5 E1010328105722             External Interface: Central Data                        BUS_EI_CENTRAL_DATA
4 E1010328105723             External Interface: Central Business Partner Data       BUS_EI_BUPA_CENTRAL
            4 E1010328105735             External Interface: Roles                               BUS_EI_ROLES
            4 E1010328105737             External Interface: Bank Details                    BUS_EI_BANKDETAIL
            4 E1010328105741             External Interface: Credit Card Details         BUS_EI_CREDITCARD
            4 E1010328105745             External Interface: Industries                         BUS_EI_INDUSTRYSECTOR
            4 E1010328105750             External Interface: Identification Numbers   BUS_EI_IDENTIFICATION
            4 E1010328105755             External Interface: Tax Numbers                   BUS_EI_TAXNUMBER
            5 E1010328105801             External Interface: Communication Types     BUS_EI_COMMUNICATION
5 E1010328105802             External Interface: Communication Data Telephone   BUS_EI_TEL_DATA
5 E1010328105803             External Interface: Data for Telephone       BUS_EI_BUPA_TELEPHONE
4 E1010328105804             External Interface: Data for Creating a Telephone Number     BUS_EI_BUPA_TELEPHONE_CON
                        4 E1010328105807             External Interface: Communications Notes        BUS_EI_COMREM
****start to repeat here your IDoc data, that means insert these segements for each new phone number
                    5 E1010328105803             External Interface: Data for Telephone      BUS_EI_BUPA_TELEPHONE
4 E1010328105804             External Interface: Data for Creating a Telephone Number     BUS_EI_BUPA_TELEPHONE_CON
                        4 E1010328105807             External Interface: Communications Notes      BUS_EI_COMREM
****end insertion
                4 E1010328105811                 External Interface: Communication Data Fax    BUS_EI_FAX_DATA
You can try the same for address data. Note: you don't need to renumebr the repeated segments in the IDoc, the "system" is doing it ...
Be sure that the sequence of the other segements after the duplication is still the same, or you get an error.
Go to transaction WE19. There you key in an existing and successfully posted IDoc. Then you can edit this Idoc, insert the new segements for additional phone numbers for testing.
Rgds
JP
Message was edited by:
        Jörn Peter

Error detail in data migration?

Similar Messages

Maybe you are looking for