Transfer Binary JPG from Table to AL11

Hi folks,
I have the problem, that I can not transfer a JPG-File from a Table (stored in bin-format) to
AL11 directory properly.
When I transfer the files to my local harddrive, everything is fine and I can open the picture. When I tranfer it to Al11 instead, I cannot open the file and in IrfanView I get the error, that the JPG-Header could be broken.
Somebody faces similar issues?
Best regards
Davor
Edited by: Davor Serdar on Jun 16, 2009 4:26 PM

Thanks for your reply.
First I use a webservice to get a stream from an url.
Then I use FM SCMS_XSTRING_TO_BINARY to put the stream into a table and then I
try to store the files in the table to AL11.
As I already said, storing the jpgs to my local harddrive works fine.
Here some snippet:
OPEN DATASET var_al11 FOR OUTPUT IN BINARY MODE.
      LOOP AT lt_tab_file INTO ls_tab_file.
        TRY.
            TRANSFER ls_tab_file TO var_al11.
          CATCH cx_sy_conversion_codepage.
            WRITE: / 'Codepage Error'.
        ENDTRY.
      ENDLOOP.

Similar Messages

How can I transfer binary data from a database to another database?

Hi all.
I want to transfer binary data from a MS SQL Server 2000 to anohter SQL Server 2000.
I created JDBC(table) to JDBC(stored procedure) scenario,and
I uploaded a JPG image file to the sender table using the java program I developed.
The JPG data was transfered to receiver,but the transfered data was broken.
I can't not open the file correctly.
Can XI transfer binary data using JDBC adapter?
The sender table structure is following.
column (data type)
id (int 4)
binary (binary 8000)
flag (int 4)
The receiver stored procedure parameter is following.
parameter (data type)
id (smallint)
binary (binary 8000)
flag (smallint)
Regards.
Yuuki

Hi,
Can XI transfer binary data using JDBC adapter?
Ans: Yes
Supported JDBC Types
http://help.sap.com/saphelp_nw04s/helpdata/en/16/9dc9ac8bc72a48b80e639abaa2e497/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
Mapping JDBC types to Java types
http://help.sap.com/saphelp_nw04/helpdata/en/7d/79dfa72d1049bc963f4f272bb1638e/frameset.htm
Regards,
Prateek

Approaches to transfer changed data from a table to another table

Hello expert,
will you please show me all approaches to automatically detect and transfer changed data from a table to another table ? I don't need detail information, but a little comment for those approaches are more welcome.
Many Thanks,
Edited by: 843178 on 19-Dec-2011 2:04 PM

You will want to review information on replication and similar methods
In a nutshell:
Replication allowed data to exist at more than one site and take the Master / original table data and clone it at a different site
As tranporting all of the table data to a remote / clone site got more and more expensive we developed a method
to identify just the 'diffs' and only send those from the master to the clone which needed only the diffs to become a clone of the master table
This has many methods and options, but looking under key words such as
- distributed transations
- materialized views
- replication
... are a few categories that will get you started

Exclude GUID field from tables in tdms transfer.

Hi,
We have been asked chek whether it is possible to exclude GUID fileds from tables in TDMS ERP data transfer.
We ran data replication from ECC to CRM in out pre-prod system, replication populated the CRM GUIDs in ECC. We are going to use pre-prod as sender system for TDMS transfer. GUID field is part of the corresponding object table so the receiver system tables also populated with GUID. What we don't know is how replication behaves when the GUIDs are already populated.
As I know there is a way to set the GUID filed to NULL value in tdms transfer using scrambling rule. The only concern I am having is how this could affect the ISU data in other tables.
Please share your opinions on this.
Thanks
Praveen.

The "GUID fields" are used to normalize the data and is the key fields for all CRM applications. If you don't transfer those the system will be "empty" because data relations cannot be found.
Markus

How can I transfer my photos (jpg) from the computer to the ipad2?

How can I transfer my photos (jpg) from the computer to the ipad2? I am not able to upload them to itunes.

Did you do this?

Module pool transfer of data from one table control to another

Hi all,
I have been assigned to module pool object wherein i have to display table control on screen and that table control contains only 10 rows on screen for display. Now my internal table it_out has 15 rows
Describe table it_out
line v_l.     " v_l = 15.
There is a pushbutton below table control and when i select multiple rows and click on that pushbutton it will navigate me to the next screen containing another table control on which i need to display those selected records.
Now the problem is that when i select first record and move cursor down to select last record then i am seeing only last record on next screen table control. why is it happening? please provide me with solution. For rest of cases it is working fine for example if i select first record and second record then i am seeing both these selected records on next screen table control . Only the problem arises when i tried to select first and lets say last record when scrolling down on table control.
I think the problem is with scrolling but when i loop on next screen with moved records i am seeing that 2 records are their but it is transferring only one record to next screen not the last one.
Your response is highly appreciated.
Thanks
Parag

Hi Parag,
Screen 8002 (with table control) --> select records --> press a button --> move to screen 8003 --> display selected records in screen 8002.
First problem that if you select first record in table control and scroll to end to select the last record, the first record in deselected.
Next problem, that if you select say 3 records in table control you want the to be displayed in another table control, the use this code.
Also take another internal table and work area same as the initial internal table and work area used in screen 8002.
On screen 8002, take a button with function code 'PROCESS', on which user clicks the screen 8003 should display selected records.
Now, use this code, its working:-
Take the names of the input/output fields as work_area-field_name and select column in table control as work_area-flag.
Also take a flag field of size 1 datatype character as the last field in the internal table and work area while declaration.
You must have passed a code in PBO of the screen for reading internal table into the table control.
So it reads the internal table into the table control whenever you perform any action on use command.
All you need to do is to write a code to modify the internal table form the table control while performing any user action.
Remember to change the LINE SEL option in attributes of table control as MULTIPLE.
At Screen Logic:-
PROCESS BEFORE OUTPUT.
MODULE status_8002. "for pf-status
LOOP WITH CONTROL po_tab. "po_tab is name of table control
    MODULE pass_data. "to pass data into table control from internal table
ENDLOOP.
PROCESS AFTER INPUT.
MODULE user_command_8002. "to handle other user commands (back and exit)
LOOP WITH CONTROL po_tab. "po_tab is name of table control
    MODULE modify_data. "to modify data from table control into internal table
    MODULE process_data. "to display selected records on another screen
ENDLOOP.
In PBO,
*&      Module STATUS_8002 OUTPUT
MODULE status_8002 OUTPUT.
SET pf-status 'ZAB_PFSTA'. " pf-status
DATA : line_count TYPE i.
DESCIRBE TABLE it_ekpo
LINES line_count.
po_tab-lines = line_count + 10.
" to make table control scrollable
ENDMODULE.                 " STATUS_8002 OUTPUT
*&      Module PASS_DATA OUTPUT
MODULE pass_data OUTPUT.
READ TABLE it_ekpo into wa_ekpo INDEX po_tab-current_line.
ENDMODULE.                 " PASS_DATA OUTPUT
"it_ekpo is internal table and wa_ekpo is the work area
In PAI,
*&      Module MODIFY_DATA INPUT
MODULE MODIFY_DATA INPUT.
MODIFY IT_EKPO INDEX PO_TAB-CURRENT_LINE FROM WA_EKPO.
"modify records from table control into the internal table
ENDMODULE.                 " MODIFY_DATA INPUT
*&      Module PROCESS_DATA INPUT
MODULE PROCESS_DATA INPUT.
CASE sy-ucomm.
    WHEN 'PROCESS'.
      IF wa_ekpo-flag = 'X'.
        wa_ekpo1 = wa_ekpo.
        APPEND wa_ekpo1 TO it_ekpo1. "if record selected move to another internal table
      ENDIF.
ENDCASE.
"modify records from table control into the internal table
ENDMODULE.                 " PROCESS_DATA INPUT
Now if you select some records in this table control the values will retain in internal table.
Screen 8003 with selected records to be displayed in another table control.
At Screen Logic:-
PROCESS BEFORE OUTPUT.
MODULE status_8003. "for pf-status
LOOP WITH CONTROL po_tb. "po_tb is name of table control
    MODULE pass_data1. "to pass data into table control from internal table
ENDLOOP.
PROCESS AFTER INPUT.
MODULE user_command_8003. "to handle other user commands (back and exit)
LOOP WITH CONTROL po_tb. "po_tb is name of table control
    MODULE modify_data1. "to modify data from table control into internal table
ENDLOOP.
In PBO,
*&      Module STATUS_8003 OUTPUT
MODULE status_8003 OUTPUT.
SET pf-status 'ZAB_PFSTA'. " pf-status
DATA : line_count1 TYPE i.
DESCIRBE TABLE it_ekpo1
LINES line_count1.
po_tb-lines = line_count1 + 10.
" to make table control scrollable
ENDMODULE.                 " STATUS_8003 OUTPUT
*&      Module PASS_DATA1 OUTPUT
MODULE pass_data1 OUTPUT.
READ TABLE it_ekpo1 into wa_ekpo1 INDEX po_tb-current_line.
ENDMODULE.                 " PASS_DATA1 OUTPUT
"it_ekpo is internal table and wa_ekpo is the work area
In PAI,
*&      Module MODIFY_DATA1 INPUT
MODULE MODIFY_DATA1 INPUT.
MODIFY IT_EKPO1 INDEX PO_TB-CURRENT_LINE FROM WA_EKPO1.
"modify records from table control into the internal table
ENDMODULE.                 " MODIFY_DATA1 INPUT
Hope this solves your problem.
Thanks & Regards,
Tarun Gambhir

Reg transfer of data from excel to internal table

hi
i need to upload datas from Excel sheet to Internal Table.For this i use d FM
ALSM_EXCEL_TO_INTERNAL_TABLE.but the problem is if a particular field has no value in excel sheet,then its not uploaded into internal table.then next field value has come to that blank place in d internal table. what i need is if the excel sheet has a blank value for a field then a blank value is added in d inetrnal table also.

Use below program logic
Program : ZLWMI151_UPLOAD(Data load to ZBATCH_CROSS_REF Table)
Type : Upload program
Author : Seshu Maramreddy
Date : 05/16/2005
Transport : DV3K919574
Transaction: None
Description: This program will get the data from XLS File
 and it upload to ZBATCH_CROSS_REF Table
REPORT ZLWMI151_UPLOAD no standard page heading
 line-size 100 line-count 60.
*tables : zbatch_cross_ref.
data : begin of t_text occurs 0,
 werks(4) type c,
 cmatnr(15) type c,
 srlno(12) type n,
 matnr(7) type n,
 charg(10) type n,
 end of t_text.
data: begin of t_zbatch occurs 0,
 werks like zbatch_cross_ref-werks,
 cmatnr like zbatch_cross_ref-cmatnr,
 srlno like zbatch_cross_ref-srlno,
 matnr like zbatch_cross_ref-matnr,
 charg like zbatch_cross_ref-charg,
 end of t_zbatch.
data : g_repid like sy-repid,
 g_line like sy-index,
 g_line1 like sy-index,
 $v_start_col type i value '1',
 $v_start_row type i value '2',
 $v_end_col type i value '256',
 $v_end_row type i value '65536',
 gd_currentrow type i.
data: itab like alsmex_tabline occurs 0 with header line.
data : t_final like zbatch_cross_ref occurs 0 with header line.
selection-screen : begin of block blk with frame title text.
parameters : p_file like rlgrap-filename obligatory.
selection-screen : end of block blk.
initialization.
g_repid = sy-repid.
at selection-screen on value-request for p_file.
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 PROGRAM_NAME = g_repid
 IMPORTING
 FILE_NAME = p_file.
start-of-selection.
Uploading the data into Internal Table
perform upload_data.
perform modify_table.
top-of-page.
CALL FUNCTION 'Z_HEADER'
EXPORTING
 FLEX_TEXT1 =
 FLEX_TEXT2 =
 FLEX_TEXT3 =
*& Form upload_data
 text
FORM upload_data.
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
 EXPORTING
 FILENAME = p_file
 I_BEGIN_COL = $v_start_col
 I_BEGIN_ROW = $v_start_row
 I_END_COL = $v_end_col
 I_END_ROW = $v_end_row
 TABLES
 INTERN = itab
 EXCEPTIONS
 INCONSISTENT_PARAMETERS = 1
 UPLOAD_OLE = 2
 OTHERS = 3.
IF SY-SUBRC <> 0.
 write:/10 'File '.
ENDIF.
if sy-subrc eq 0.
 read table itab index 1.
 gd_currentrow = itab-row.
 loop at itab.
 if itab-row ne gd_currentrow.
 append t_text.
 clear t_text.
 gd_currentrow = itab-row.
 endif.
 case itab-col.
 when '0001'.
 t_text-werks = itab-value.
 when '0002'.
 t_text-cmatnr = itab-value.
 when '0003'.
 t_text-srlno = itab-value.
 when '0004'.
 t_text-matnr = itab-value.
 when '0005'.
 t_text-charg = itab-value.
 endcase.
 endloop.
endif.
append t_text.
ENDFORM. " upload_data
*& Form modify_table
 Modify the table ZBATCH_CROSS_REF
FORM modify_table.
loop at t_text.
 t_final-werks = t_text-werks.
 t_final-cmatnr = t_text-cmatnr.
 t_final-srlno = t_text-srlno.
 t_final-matnr = t_text-matnr.
 t_final-charg = t_text-charg.
 t_final-erdat = sy-datum.
 t_final-erzet = sy-uzeit.
 t_final-ernam = sy-uname.
 t_final-rstat = 'U'.
 append t_final.
 clear t_final.
endloop.
delete t_final where werks = ''.
describe table t_final lines g_line.
sort t_final by werks cmatnr srlno.
Deleting the Duplicate Records
perform select_data.
describe table t_final lines g_line1.
modify zbatch_cross_ref from table t_final.
if sy-subrc ne 0.
 write:/ 'Updation failed'.
else.
 Skip 1.
 Write:/12 'Updation has been Completed Sucessfully'.
 skip 1.
 Write:/12 'Records in file ',42 g_line .
 write:/12 'Updated records in Table',42 g_line1.
endif.
delete from zbatch_cross_ref where werks = ''.
ENDFORM. " modify_table
*& Form select_data
 Deleting the duplicate records
FORM select_data.
select werks
 cmatnr
 srlno from zbatch_cross_ref
 into table t_zbatch for all entries in t_final
 where werks = t_final-werks
 and cmatnr = t_final-cmatnr
 and srlno = t_final-srlno.
sort t_zbatch by werks cmatnr srlno.
loop at t_zbatch.
 read table t_final with key werks = t_zbatch-werks
 cmatnr = t_zbatch-cmatnr
 srlno = t_zbatch-srlno.
 if sy-subrc eq 0.
 delete table t_final .
 endif.
 clear: t_zbatch,
 t_final.
endloop.
ENDFORM. " select_data
Reward points if it is helpful
Thanks
Seshu

To transfer time events from external time recording system to sap r/3

hi all,
I have a task to make an interface program between external time recording and sap r/3, and then to transfer the time events from that external system to sap system with the help of an rfc, i have got some information like the data first has to be transferred to the table CC1TEV and then from this table the data will be uploaded to 2011 infotype with the help of a standard program, but i am unable to find a solution for making the interface program and the RFC or BAPI which will transfer the records from external system.
if anybody has any information on this plz help me out to solve this problem.

Which recorgding terminals using to capture time events? They should have give some guidelines about this?
Regards
niranjan

How do I transfer RAW+jpg to cloud storage under iOS 8?

I want to transfer Canon RAW+jpg CR2 files, imported from the camera via the camera connection kit, from my iPad to cloud storage in Dropbox. Prior to iOS 8, I could accomplish this by exporting from the photography workflow app PhotosInfoPro. That functionality is now broken. The app performs correctly when handling pure jpg files, or handling pure RAW files, but fails when handling RAW+jpg. The operation completes without any error messages, but only the jpg data from the RAW+jpg has been uploaded to the cloud. The RAW sensor data isn't there.
Is there an alternate method to transfer these files from the iPad to cloud storage - either Dropbox or Google Drive? I have tried many different things, none of which were successful. I can get the jpg portion into the cloud, but not the RAW portion. If you know of a method or an app that is performing this successfully under iOS 8, please help. I am at my wits end.

How can I transfer the photos to the Cloud to free up some space?
iCloud does not store photos long term. You can share your photos to your Photo Stream to transfer them, but you need to download them on another device, before you delete them from your iPhone.
Back them up on a computer, before you delete them from your iPhone.
For example, by:
Import photos directly into iPhoto or Aperture on your computer.
Save photos to your computer using iTunes.
Regards

I have 2 imac computers and here are my questions: first, how to I transfer the information from my contact directory from my old imac into my new imac and once the information is transfered how can I print it? Second: I have a large music collection in m

have 2 imac computers and here are my questions: first, how to I transfer the information from my contact directory from my old imac into my new imac? Once the information is transfered how can I print it? Second: I have a large music collection in my old Imac computer how do I transfer this information to my new computer? Also how can I share this information with other computers at home?

I think you may find helpful information here:
A Basic Guide for Migrating to Intel-Macs
The Knowledgebase article Intel-based Mac: Some migrated applications may need to be updated refers to methods of dealing with migrating from PowerPC chips to Intel with the Migration Assistant safely. The authors of this tip have not had a chance to verify this works in all instances, or that it avoids the 10.6.1 and earlier Guest Account bug that caused account information to get deleted upon use of the Migration/Setup Assistant. However, a well backed up source that includes at least two backups of all the data that are not connected to your machine will help you avoid potential issues, should they arise. In event it does not work, follow the steps below.
If you are migrating a PowerPC system (G3, G4, or G5) to an Intel-Mac be careful what you migrate. Keep in mind that some items that may get transferred will not work on Intel machines and may end up causing your computer's operating system to malfunction.
Rosetta supports "software that runs on the PowerPC G3, G4, or G5 processor that are built for Mac OS X". This excludes the items that are not universal binaries or simply will not work in Rosetta:
Classic Environment, and subsequently any Mac OS 9 or earlier applications
Screensavers written for the PowerPC System Preference add-ons
All Unsanity Haxies Browser and other plug-ins
Contextual Menu Items
Applications which specifically require the PowerPC G5 Kernel extensions
Java applications with JNI (PowerPC) libraries
See also What Can Be Translated by Rosetta.
In addition to the above you could also have problems with migrated cache files and/or cache files containing code that is incompatible.
If you migrate a user folder that contains any of these items, you may find that your Intel-Mac is malfunctioning. It would be wise to take care when migrating your systems from a PowerPC platform to an Intel-Mac platform to assure that you do not migrate these incompatible items.
If you have problems with applications not working, then completely uninstall said application and reinstall it from scratch. Take great care with Java applications and Java-based Peer-to-Peer applications. Many Java apps will not work on Intel-Macs as they are currently compiled. As of this time Limewire, Cabos, and Acquisition are available as universal binaries. Do not install browser plug-ins such as Flash or Shockwave from downloaded installers unless they are universal binaries. The version of OS X installed on your Intel-Mac comes with special compatible versions of Flash and Shockwave plug-ins for use with your browser.
The same problem will exist for any hardware drivers such as mouse software unless the drivers have been compiled as universal binaries. For third-party mice the current choices are USB Overdrive or SteerMouse. Contact the developer or manufacturer of your third-party mouse software to find out when a universal binary version will be available.
Also be careful with some backup utilities and third-party disk repair utilities. Disk Warrior, TechTool Pro , SuperDuper , and Drive Genius work properly on Intel-Macs with Leopard. The same caution may apply to the many "maintenance" utilities that have not yet been converted to universal binaries. Leopard Cache Cleaner, Onyx, TinkerTool System, and Cocktail are now compatible with Leopard.
Before migrating or installing software on your Intel-Mac check MacFixit's Rosetta Compatibility Index.
Additional links that will be helpful to new Intel-Mac users:
Intel In Macs
Apple Guide to Universal Applications
MacInTouch List of Compatible Universal Binaries
MacInTouch List of Rosetta Compatible Applications
MacUpdate List of Intel-Compatible Software
Transferring data with Setup Assistant - Migration Assistant FAQ
Because Migration Assistant isn't the ideal way to migrate from PowerPC to Intel Macs, using Target Disk Mode, copying the critical contents to CD and DVD, an external hard drive, or networking will work better when moving from PowerPC to Intel Macs. The initial section below discusses Target Disk Mode. It is then followed by a section which discusses networking with Macs that lack Firewire.
If both computers support the use of Firewire then you can use the following instructions:
1. Repair the hard drive and permissions using Disk Utility.
2. Backup your data. This is vitally important in case you make a mistake or there's some other problem.
3. Connect a Firewire cable between your old Mac and your new Intel Mac.
4. Startup your old Mac in Transferring files between two computers using FireWire.
5. Startup your new Mac for the first time, go through the setup and registration screens, but do NOT migrate data over. Get to your desktop on the new Mac without migrating any new data over.
If you are not able to use a Firewire connection (for example you have a Late 2008 MacBook that only supports USB:)
1. Set up a local home network: Creating a small Ethernet Network.
2. If you have a MacBook Air or Late 2008 MacBook see the following:
MacBook (13-inch, Aluminum, Late 2008) and MacBook Pro (15-inch, Late 2008)- What to do if migration is unsuccessful;
MacBook Air- Migration Tips and Tricks;
MacBook Air- Remote Disc, Migration, or Remote Install Mac OS X and wireless 802.11n networks.
Copy the following items from your old Mac to the new Mac:
In your /Home/ folder: Documents, Movies, Music, Pictures, and Sites folders.
In your /Home/Library/ folder:
/Home/Library/Application Support/AddressBook (copy the whole folder) /Home/Library/Application Support/iCal (copy the whole folder)
Also in /Home/Library/Application Support (copy whatever else you need including folders for any third-party applications)
/Home/Library/Keychains (copy the whole folder) /Home/Library/Mail (copy the whole folder) /Home/Library/Preferences/ (copy the whole folder) /Home /Library/Calendars (copy the whole folder) /Home /Library/iTunes (copy the whole folder) /Home /Library/Safari (copy the whole folder)
If you want cookies:
/Home/Library/Cookies/Cookies.plist /Home/Library/Application Support/WebFoundation/HTTPCookies.plist
For Entourage users:
Entourage is in /Home/Documents/Microsoft User Data Also in /Home/Library/Preferences/Microsoft.
Credit goes to Macjack for this information.
If you need to transfer data for other applications please ask the vendor or ask in the Discussions where specific applications store their data.
5. Once you have transferred what you need restart the new Mac and test to make sure the contents are there for each of the applications.
Written by Kappy with additional contributions from a brody.Revised 5/21/2011

Nikon D800 raw files taken with Sandisk extreme plus 32GB SDHC card got corrupted. Able to preview them in Lightroom4.4 Library, but not able to import or transfer the files from card to computer. Any ideas on how to save images from Library Window in Lig

Hi, I have shot few pictures on 31st December night in RAW mode using Nikon D800 and Sandisk extreme plus 32GB SDHC card. It looks like card got some memory errors so not able to transfer the files from Card to computer. However I am able to view the pics thru Lightroom ver 4.4 Library, but when I tried to import them, it gives me an error stating that file can't be read.
Is there a way to save the pics from Library window in lightroom overcoming the card read errors ?
Thanks in advance

Hi SSPRENGEL,
Thank you for your response. Here is the error message I am receiving, I tried with various destination folders in the computer but it still gives the same error:. Just to let you know, I am able to import pictures into these folders from other memory cards.
I am able to finally at least extract the jpgs using the option suggested by elie-d

Error while creating datasource from table MBEWH

Hi all,
I am facing an error message while creating datasource from table MBEWH
"Invalid extract structure template MBEWH of DataSource "; This operation failed, because the template structure quantity fields or currency fields, for example, field LBKUM refer to a different table.
Can anyone help me that why system is not allowing me to generate generic datasource for table MBEWH to transfer my month wise inventory data.
thanks and regards.

Hi Zakir,
      This was comming for classification data... when ever you want to extract some classification related data then we can't create generic datasources directly.. for that you need to go with CTBW ( tcode ) and   create one datasource...
   so, you need to check that   related table also.. for that MBEWH table..
    ALL THE CLASSIFICATION RELATED DATASOURCES WE CAN'T CREATE DIRECTLY... JUST LIKE AUSP table also.. liek this..
regards
@jay

Is there any way to transfer photos, music from my PC to my new iPad(3)?

Is there any way to transfer photos, music, from my PC to my new iPad(3)?

Another way. You can use a USB flash drive & the camera connection kit.
Plug the USB flash drive into your computer & create a new folder titled DCIM. Then put your movie/photo files into the folder. The files must have a filename with exactly 8 characters long (no spaces) plus the file extension (i.e., my-movie.mov; DSCN0164.jpg).
Now plug the flash drive into the iPad using the camera connection kit. Open the Photos app, the movie/photo files should appear & you can import. (You can not export using the camera connection kit.)
Secrets of the iPad Camera Connection Kit
http://howto.cnet.com/8301-11310_39-57401068-285/secrets-of-the-ipad-camera-conn ection-kit/
IOS: Syncing with iTunes
http://support.apple.com/kb/HT1386
Apple - Support - iPad - Syncing
http://www.apple.com/support/ipad/syncing/
ITunes: Syncing media content to your iOS devices
http://support.apple.com/kb/ht1351
 Cheers, Tom

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
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.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

How do you validate transfer of data from legacy to SAP (Tcode: SQVI)?

Hello PP members:
I would like to know how to validate transfer of data from legacy to SAP
A friend of mine was telling it has to do with SAP quick viewer(SQVI) but could not able to much leads on it
I would be thankful if can provide insights into the subject
Thanks for your time,
Suren R

Suren,
Yes, you could create queries in SAP with SQVI and get the data in SAP. But you need to be aware of all the relevant tables in SAP.
For information for creating queries use link:
http://help.sap.com/saphelp_47x200/helpdata/en/05/2b1df9209411d6b1d500508b6b8b11/frameset.htm
For getting the relevant tables the easiest way is :
1) Goto Se16.
2) Choose F4,
3) Click on SAP applications and drill down to the relevanttable.
Hope this is useful. If yes reward poins and close this thread.
Regards
Ram

Transfer Binary JPG from Table to AL11

Similar Messages

Maybe you are looking for