CAD Dialog Interfaces

Hi,
We have SAP 4.6C running.
We had CAD Dialog interface to connect our Team Center (PLM application
earlier called Metaphase ) to our SAP 4.6C. We employed CAD RFC SDK's
to implememt such a scenario.
Now we are upgrading to ECC 6.0 .
We would like to know whether the CAD RFC functionality can still be
used to manage the interface.
If yes what is the current level of CAD RFC's which we have to download
and deploy ?
If no What is the alternative solution SAP is giving to achieve the
purpose?
This is very urgent as it happens to be our most important interface to
SAP from which Material Master and Design BOM get's uploaded.
Regards,
Girish

Use a porperty node and write a true to the key focus property of the text control.
If you need the OK button to react to an enter just right click on it, select advanced and key navigation and set the shortcut to enter.
Instead of using a dialog box to retrive the keyboard input though I would just read the keyboard input directly, e.g. using the key down event. Create a shift register to hold the previous keys and add new keys every time that event fires. If the character is a CR process the bar code and clear the shift register.
MTO

Similar Messages

Testing CAD-Desktop interface with CAD-system

Hi,
does anybody know if it is possible to get a CAD-system for free to test the CAD-Desktop interface of SAP?
I am not a key CAD user, I just want to look how CAD Desktop works.
Regards,
Oliver

You do not need CAD system to work with CAD Desktop
call transaction SE37
In Function module enter : CDESK_SHOW
or CDESK_TEST
Fill the import paramenters
Execute it
CAD Desktop will appear

CAD Interface Help

Hi all. Apologies if this query is on the wrong forum but here goes.
I have currently written an interface between our CAD/PDM system and SAP using the cad dialog library. This is mainly to create/change Materials & BOM's. I have been asked to transfer Classification information through this interface and have become a little stuck. I have used the cadsampl.c file which comes with the SAPgui as reference and have managed to create a material with a class type and class number using the function 'MATCR' but I am struggling to transfer the characteristic value across using the function 'matcr cr'. Any suggestions ?

I'm having the same problem. Did you ever find a solution for this?
For reference, my question is located over here: OverFlowException on Oracle ODBC RowCount

Photography

Photography:I have an iMac OSX 10.6.7 loaded with Photoshop Elements 9, connected to a Cannon Pixma ip4300 printer. My problem: Whether using PSE 9 or Photoshop, the colours on my prints do not match the monitor, regardless of the monitor display profile I set on the imac monitor.
I prefer using PSE 9 for editing and printing, but results are awful, possibly because one cannot disable "printer controls colour management" on the Pixma. Prints from Photoshop are better,but still not perfect, and of course editing on mismatched colours on PSE 9 and then printing on Photoshop is a poor gamble.
Questions:
1. Any suggestions on overcoming problem?
2. If I decide to buy a new printer, what is the very best printer for use with the iMac for prints up to and including A4?

I've never owned a Canon printer, so I can't help there; but, offering a suggestion you asked for: have you looked into the Epson Artisan series?
http://www.epson.com/cgi-bin/Store/jsp/ProductCategory.do?BV_UseBVCookie=yes&oid =-8182
I have the Epson Artisan 810 (the new model is the 835); it works very well and does colors extremely well. I also have no problem with the printing dialog interface; also, the Epson allows many settings on the touchscreen display (don't know what the new 835 offers that I don't have). Mine also offers duplex printing (although I must say I've only used that once), and an excellent scan function. I usually do not use iPhoto, but generally Aperture, PSE 6, Graphic Converter and a few other minor ones and have had no problem printing with those.

Problems printing from Google Chrome browser using my HP Officejet 6500 E709n Series printer

Dear Sir or Madam:
I am using Microsoft Windows XP Home Edition Version 2002 Service Pack 3 desktop computer.
I have a HP Officejet 6500 E709n Series printer.
I am encountering some problems printing from my Google Chrome browser in my Outlook.com account because when I try to change some settings in the print dialog interface the printout comes out incorrectly.
Below are the 2 snapshots of the print dialog interface of Google Chrome browser before printing an email message from my Outlook.com account.
Are there any software updates to correct this problem?
Please reply back soon.
Thanks.
Sincerely,
Etow

Welcome to the forums Etow,
I saw your post about the issue you are having with printing from Google Chrome. Have you tried disabling your pop up blocker to see if that will help? Also see this guide about Printing with Chrome.
If the above does not help, try using Firefox or Internet Explorer to print.
Have a great Friday
R a i n b o w 7000I work on behalf of HP
Click the “Kudos Thumbs Up" at the bottom of this post to say
“Thanks” for helping!
Click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution!

SUN .... When.... JRE 1.4.0 international with auto update

SUN .... When.... JRE 1.4.0 international with auto update
When will you deliver .........
We have a dead line and our product needs the international version 1.4 to be updated on our exsiting user base, one of our customers has over 700 workstations.
If the solution is to manually dowload and install this version then Web Start totally fails as a web centric solution.
I see that creating our own servlet breaches SUN's license agreement, so give us a developer servlet we can use.

The auto download servlet supports both international and us-only versions of Java 1.4.0.
Java Web Start includes the current locale in the request to the servlet, and it returns the
US only version if the locale is en_US , or the international version otherwise.
Curently there is no way to get the servlet to download the international version when the
clients locale is en_US.Sorry but havent you just anwsered the question I put, either the servlet supports international clients or it dosent and your anwser just puts more wood on the fire, it dosent, but it could.
Also we recognize that there is a problem when an application needs the international version, and >>the client already has the US version installed. In this case Java Web Start will not attempt
to contact the servlet since it thinks it has an appropriate version allready.Also if you client requires an international version of the JRE it is because it requires that version period, hence if the version tag within the JNLP file specifies JRE1.4 international, then it dosent matter what Web Start may or may not think, the JNLP file written for the application by the author should determine its fate.
The only reason Web Start should determine locale on a target machine would be the text displayed for the dialog interface between the end user.
Its a simple case of checking do I have 1.4 international, "Yes or No", at this point I dont care if 1.4 English is installed, or locale is English, JNLP file asked Web Start, if 1.4 international was installed, "No", Ok then call servlet and request 1.4 international. Simple....
The JRE license agreement allows customers to repackage and redistribute the JRE.
Many customers are redistributing a JRE with their app. Im sure many are, please read my previous post , if you can get sun to offically confirm this, then I stand corrected.

Tag library 'div' hook

Well, 'div' is not corrupt, but the application programming related to customization of Tag libraries is corrupt.
What is happening:
When Dreamweaver CC is installed, and when it opens fresh html files, it makes a mess of line breaks and indents in the text layout of the code. Using the menu item Commands / Apply source formatting also makes a mess, This menu command mess is a slight improvement over the horrendous mess that Dreamweaver CC makes of code when it opens and when it periodically 'refreshes' the files that it trashes. However, the code is not usable, as with more advanced css and html technique, the code becomes unreadable for Chrome, Internet Explorer, Safari, and presumably all browsers.
DW's mess described:
All indents are as spaces, making manual clean-up repetitive, necessary and extremely tedious.
The head and body tags are indented far inside their content, and that content is also erratically indented.
The use of Tag library editor would seem the expected user path, in seeking a user resolution, and perhaps in defining a programmatic intervention.
All tags are trashed, put going to the heart of the html cascade, we start with the p tag: e.g., p tag in Tag libraries defaults as
Line breaks: before and after tag
Contents: formatted and indented
Case: default
We try numerous combinations of p tag settings in the noted dialog interface.
The p tag settings do not appear to effect the mess. Dreamweaver, ignores default and manual settings, sometimes shuffling the mess a little, but minor shuffling only occurring twice, and without any tag block line break changes.
Perhaps, for a given instance of Dreamweaver installation, within a given simple document's system interface, Dreamweaver settings may reveal something called a 'performance hook' by application programmers. Perhaps we can isolate a hook that is useful for the Adobe support; support that lacking professional attention has maintained Dreamweaver as a failed application for over a year (since October 2012) on my Windows desktop. We move next to the div tag.
Manual intervention 'exposes bad behavior of div tag' hook:
Our simple document layout is... simple. Deploying doctypes for both html5 and xhtml transitional and deploying internal and external style methods, with the same code trashing result, we correctly layout tags as HEAD, BODY, DIV and P. Beginning with the p tag, various tag library settings are applied to determine effect on Apply source formatting command. Various p tag settings have no effect, and p is returned to its DW default setting, as noted above. The following div tag settings disable Apply source formatting command's code trashing specifically of line indents.
Line breaks: before and after tag
Contents: formatted but not indented
Case: default
Unfortunately, with this setting, line breaks between only some tags are maintained during Dreamweaver's auto code trashing (e.g., between closing head and opening body tag): sometimes when Dreamweaver does it's auto (or manual) trashing, these specific line breaks, between block tags, are not preserved. However, with this Tag library setting for the div tag using the noted basic cascade, all tag indents are ignored. But only when code is manually kept against left margin, without any indentation. And, ONLY WITH DIV TAG HOLDING THESE PARTICULAR SETTINGS, FOR THIS PARTICULAR DOCUMENT!
FLAT CODE is preferable to the bigger mess that Dreamweaver routinely imposes as it auto trashes code. Also, allowing any left margin indentation worsens Dreamweaver's code trashing... so, given Dreamweaver's chaotic destructiveness, I don't know if it is correct to imply any significance to my manual Tag library settings management, but it is clear that Dreamweaver is unable to correct the mess it makes, using the manual Apply source formatting command. And this is the first 'performance hook' that has been defined for my desktop in over 400 days. But setting div tag in this way is the only way to stop Dreamweaver trashing code layout line indents (trashing that occurs both during Dreamweaver automatic actions and with user menu action, for the specific noted html layout - a layout that is far too basic to be useful for 99.9% of design work). But only for a given instance of Dreamweaver installation for a given OS installation, and not across OS installations, or with any other file than the file (or files, in relational assessment) targeted for our 'hook' presentation analysis.
Conclusion:
Dreamweaver trashes code layout every time the application applies code formatting (e.g., opening new documents from other sources, applying menu commands, etc.). That is, all user code layout will be trashed by Dreamweaver. However, a specific div tag setting in Tag library editor may maintain a single instance for manual correction of Dreamweaver code trashing, when basic page layout is used with div in the noted cascade, and with div settings manually corrected as noted. This is a hopelessly unacceptable condition that the Dreamweaver application imposes on design work for my Windows 8.1 operating system. Professional designers of global significance and stature using many variants of Mac and PC systems have warned me not to use Dreamweaver, recommending numerous alternatives. I am taking the position that Adobe retains a shred of marketplace survivability, and therefore will promptly fix minor problems when I bring them to Adobe's attention.
IMPORTANT:
Obviously, this is not acceptable application performance. Is support available to Adobe that will now, immediately repair the Dreamweaver application that I use as a paid subscription to eliminate systematic code trashing?

I figured it out. Under the Configuration/TagLibraries,
create a CrossTagAttr folder and stick a .vtm file in it. In the
.vtm file, use the <crosstag_attributes> tag and its
children. See Configuration/TagLibraries/CrossTagAttr/Spry/Spry.vtm
for an example.

Problem in accessing the standard transaction from Portal through RFC

Below is the error we are getting when we run RFC (which has P60) from the portal(JAVA webdynpro) which inturn uses BDC to get the spool id from the standard p60(RPCEOYG0)..
Msgid "00"
Msgno "359"
Msgtx "The transaction was terminated by the user".
But if i keep the debugger inside the RFC after the call_transaction and if I press F8 then I am getting the correct output. Could some one tell me the reason behind this ?
thanks,
Prashanth J R

Hi,
It sounds to me like the BDC or some other component being called from your Z function module requires some sort of dialog interface (maybe an "Are you sure?" type message).
When calling RFC from Web Dynpro, you should ensure that at no point in the call stack does it try to perform any dialog functions (messages, pop-up box, display screens).
You mention that you BDC does a CALL TRANSACTION at some point, you should ensure that this isn't executed when you are calling by RFC from a Web Dynpro.
Your Z function module should be able to execute from start to finish, returning the results without any dialog interaction.
I might be wrong, but it sounds similar to a problem we had a few years ago where someone had coded an "Are you sure?" message into a function module that was called from a stadard R/3 dialog screen as well as Web Dynpro in the Portal, and it broke the portal based stuff.
Cheers,
Chris

WPF control in Photoshop

I want to develop a plugin that has minimum interaction with the host application. For example, once the plugin is loaded, the user is able to open and edit images on the plugin interface. The images can then be saved from the plugin dialog without the need to go through host application. Basically, the plugin will not have any interaction with the host except it will appear in the photoshop drop down menu (for that we need to code PiPL resource I guess?).
I need richer controls in my dialog interface, is it possible to use WPF (windows presentation foundation) forms and user controls instead of using MFC dialog provided in the sample code? Is WPF fully supported by photshop sdk?
Thanks for any help:)

But does common language runtime (clr) have to be enabled in order to hold wpf control? Is it supported by photoshop SDK?

Out of disk space when exporting

im trying to export a project to quick time and saving it to the desktop..
and a window appears telling out of disk space...
What to do???????
thank you...

You just have to specify the drive you wish to export to, in the export dialog interface...
What other drives do you have available?
K
EDIT - What are you exporting, and what is the current workflow you're following.
If you simply don't have disk space, you could try exporting a reference movie...(uncheck 'make movie self-contained') Be aware that if you do this, you MUST retain all media that the file contains, and it won't work on another system...without the identical material anyway.
But if you're that low on disk space, you really need to find a longer term solution, like an additional drive, or simply delete unnecessary media from a drive.

What's up with CUPS?

i am trying to set some defaults (print at actual size and don't rotate) which /seem/ like they should be defaults but aren't. and between the printer interface and my various OS's and my brain being filled with other stuff i have had a hard time with this. my recollection was that in Snow Leopard this was a terminal command but now in Lion and ML i am reading up on CUPS.
1. can anyone tell me what the reason is that i need to use CUPS? i mean, it is a consequence of the complexity of printing and or the relative lack of development in mac os of the printer dialog interfaces? the variety of printer manufacturers? if understand why i am using it it may help me to get it done.
2. can someone remind me on how to implement the two above defaults like if a dumb monkey distracted by a banana had to implement this? i am reading the online documentation and it appears this is a command line set of entries that i have to enter after getting into terminal (or an online resource??) but also the documentation seems to state specifically (printed page 8 of 10 in Command-Line Printing and Options under Standard Printing Options) that the default for size is "to use the size specified in the file" which /seems/ like it is saying that scale to fit should not be the default which of course it is.
anyway, these command line interfaces get my head spinning especially if i don't understand what the default is or why i am using it but at the same time this is an functionality i would dearly love to click a LOT less when using.
TIA for anything constructive.

CUPS _is_ the printing system on OS X. Drivers do not work by themselves - they work with CUPS.
You can set defaults in the internal CUPS admin page - use a browser to go to
http://localhost:631/admin
If it doesn't work on your Mac (getting into the built-in web page), do this Terminal command then try again:
sudo cupsctl WebInterface=yes

Changing printer presets (big sigh)

i have about twelve mac printer presets for my laptop (Mountain Lion) and twelve for my desktop (Lion) and i expect to be creating more.
today i realize that it might be better for me to have all of these set as two-sided prints and actually i need to check some other settings that i may have missed (because they are squirrelled away in hard to find places).
is it necessary for me to RECREATE each of these presets from scratch?
right now i am going into the EDIT PRESETS pulldown in the PRINT pulldown (for instance i am in Safari right now) then i go select one of these presets, i hit Duplicate - and then i try and change the settings and none of this seems editable. i also tried to edit the original presets in this dialog interface and these items do not seem to be editable.
i can't tell if i am missing something or if this part of lion or mountain lion has simply been profoundly overlooked for some reason. since i print a TON of documents for my work the amount of time spent in here since moving to mac is extremely frustrating and i had thought that spending time making presets for every frequently used print config was the answer to all my headaches but now i am not so sure this isn't another level of headache...
what am i missing?

hotwheels 22 wrote:
hi PAHU.
if i go to File > Print in Safari i get a dialog and then i can run a pulldown for "Presets" and then i get to see all my presets. but if i click on one of these i get a description on the right (with the goofy organization and the arrows that let me open up each of these listings)
This sounds like you have selected the "Show Presets" setting in the Presets menu. No need to do this. Simply select to print and then select the Preset you want to modify from the drop menu.
hotwheels 22 wrote:
but if i go to something like "Copies and Pages" (where of course i am going to find "Two Sided") i see that this two sided setting is off but i don't see any way to edit.
If it is just a checkbox, then put a tick in it. You should have the option to select it. Presets don't lock you out from making changes. They simply set the print dialog to your preferred settings.
hotwheels 22 wrote:
similarly if i go to "Layout" i see another "Two Sided" (good god almighty am i an idiot and this is some kind of different setting for two sided - or is this UI just terrible) - but again i have no way to edit this AFAIK.
The Two-Sided you see in Copies and Pages is like an alias to the same setting in Layout. It just gives the user easy access to the same setting that Apple deems to be important enough to replicate it to the default page (ie Copies and Pages).
Now it does not matter which setting you use, enabling one will enable the other. But you should be able to enable then with the Preset for one sided selected. And after enabling the Two Sided setting, you should then be able to re-save this Preset with the new setting.
hotwheels 22 wrote:
i don't want to sound cranky but man is this UI not sexy enough for a developer to spend a little time making more functional or are they trying to run some kind of passive-aggressive routine where if printing is too much of a hassle they think they can wean me off of paper (i'm just joking but the more i get in here the more tricky it all becomes).
You certainly do appear to have some issue with the print dialog. As a Windows and Mac user, I don't see the Mac print dialog providing any less function or being more complicated than what Windows offers. Maybe in your attempt to simplify your usage you are actually overcomplicating things?
If you find that you still cannot edit an existing Preset then it may be easier to delete it and then create a new one.
I would also suggest that you just create a few Presets for the most common print outputs you require. If you have a Preset for every type of print output that you could ever want, then you are definitely making too much ongoing work for yourself.

Step by step batch input

Hi friends,
Please tell me about how to create a batch input from beginning to end.
How can I achieve the entry of the data?
sm35 or shdb is used to record the transaction steps?
One says sm35, the other says shdb?
Step by step?
Thanks in advance.

Hi,
BDC option
ABAP Runtime Environment (BC-ABA)
Batch Data Communication option.
BDC options define the processing mode for a batch input session.
Examples of modes used for processing sessions are:
     Display all records.
     Display for error dialogs only.
     Process session in the background.
     Process session on the screen.
Purpose
During data transfer, data is transferred from an external system into the SAP R/3 System. You can use data transfer when you:
     Transfer data from an external system into an R/3 System as it is installed.
     Transfer data regularly from an external system into an R/3 System. Example: If data for some departments in your company is input using a system other than the R/3 System, you can still integrate this data in the R/3 System. To do this, you export the data from the external system and use a data transfer method to import it into the R/3 System.
Implementation considerations
Before creating your own data transfer program, you should use the Data Transfer Workbench to find the data transfer programs that are delivered by SAP.
The Data Transfer Workbench
Purpose
The Data Transfer Workbench supports the automatic transfer of data into the R/3 System.
The Workbench is particularly useful for large amounts of data. It guarantees that data is transferred efficiently and ensures that data in the R/3 System is consistent.
Features
The Data Transfer Workbench provides the following functions:
     Integration of standard data transfer programs
     Registration and integration of your own data transfer programs
     Various techniques to load data into R/3.
The data is read from a transfer file in SAP format and loaded into the R/3 System using one of the techniques below:
     Administration and organization of data transfer projects
     Tools for analyzing the required SAP structures
     BAPI interface
     Batch input
     Direct input
Integration
SAP applications support the data transfer of numerous SAP business objects. The data transfer program specifies the data format definition that is necessary to import the data into the R/3 System. Adapt your conversion program for exporting the data from the external system to this definition.
Once the data has been exported, you can import it into your system using a generated data transfer program.
Features
     Data transfer from other, external systems
     Generation of data transfer programs
     Generation of function modules that can be used as an interface to the R/3 System
Initial Data Transfer
Prerequisites
Before you start the initial data transfer, you should have answered the following questions:
     Which business objects are to be transferred?
The objects to be transferred depend on the business applications you are using. If you are using sales and distribution processing, for example, you should transfer the material master records as well as the sales master records .
     How should the business objects be transferred?
Various techniques are available to load the data into the R/3.
Process Flow
The process of transferring data can be divided into the steps:
1.     Preparing the data transfer
     Analyzing and Cleaning Legacy Data
     Analyzing SAP Structures
     Developing Programs, Function Modules and BAPIs
     Creating a Program or FM for Data Extraction
     Creating a Mapping Program
     Registering Programs, Function Modules and BAPIs
1.     Executing the data transfer
     Organizing the Transfer in Projects
     Executing Data Transfer Runs, monitoring (CCMS) and processing (log)
     Checking transferred objects in R/3 using a function module or report (task type AUD).
The graphic below describes the steps involved in transferring the data:
ThThe The Data Transfer Workbench is an integrated project management for all the required steps involved in transferring data to your R/3 System.
You need to use programs or function modules for the various steps. SAP provides a range of BAPIs for loading data into R/3.
You could also carry out all the steps, except for loading the data via BAPIs, without using the Data Transfer Workbench.
In the first step you extract the existing data from a source system into a file and clean it there, if necessary.
To load data into R/3 you need a transfer file in an appropriate SAP format.
Using a mapping program you have to map the extracted data to the structures of the transfer file.
To load the data into the R/3 System one of the Techniques is used depending on the type of business object . I f more than one of these techniques is provided for a particular object type, you should read the documentation to find out what the different uses are .
Once you have created a project, you can start a run. The tasks of the run definition are processed in order.
After the data has been successfully loaded into the R/3 System, it can be checked here.
Result
You have transferred the data into the relevant R/3 application and checked it here.
Data Transfer
Purpose
During data transfer, data is transferred from an external system into the SAP R/3 System. You can use data transfer when you:
     Transfer data from an external system into an R/3 System as it is installed.
     Transfer data regularly from an external system into an R/3 System. Example: If data for some departments in your company is input using a system other than the R/3 System, you can still integrate this data in the R/3 System. To do this, you export the data from the external system and use a data transfer method to import it into the R/3 System.
Implementation considerations
Before creating your own data transfer program, you should use the Data Transfer Workbench to find the data transfer programs that are delivered by SAP.
Integration
SAP applications support the data transfer of numerous SAP business objects. The data transfer program specifies the data format definition that is necessary to import the data into the R/3 System. Adapt your conversion program for exporting the data from the external system to this definition.
Once the data has been exported, you can import it into your system using a generated data transfer program.
Features
     Data transfer from other, external systems
     Generation of data transfer programs
     Generation of function modules that can be used as an interface to the R/3 System
Data Transfer Methods
You can use the following methods to transfer data:
     Direct input: With direct input, the SAP function modules execute the consistency checks. However with batch input, these consistency checks are executed with the help of the screens. This means that direct input has considerable performance advantages.
     CALL TRANSACTION: Data consistency check with the help of screen logic.
     Batch input with batch input sessions : Data consistency check with the help of screen logic.
Difference between Batch Input and CALL TRANSACTION
If the direct input cannot be used for your task, this makes creating a data transfer program easier since the underlying transactions ensure that the data consistency checks are executed.
In the case of an error during the data transfer (if data records are inconsistent, for example), you can restart the transfer at the point in the program where the error occurred.
Batch input methods
With the batch input method, an ABAP program reads the external data that is to be entered in the R/3 System and stores the data in a "batch input session". The session records the actions that are required to transfer data into the system using normal SAP transactions.
When the program has generated the session, you can run the session to execute the SAP transactions in it. You can explicitly start and monitor a session with the batch input management function (by choosing System  Services  Batch input), or have the session run in the background processing system.
CALL TRANSACTION methods
In the second method, your program uses the ABAP statement CALL TRANSACTION USING to run an SAP transaction. External data does not have to be deposited in a session for later processing. Instead, the entire batch input process takes place inline in your program.
The information in Choosing Data Transfer Methods will help you decide which is the best data transfer method.
Data Transfer: Overview of Batch Input
Prerequisites
Before beginning the initial data transfer, you should answer the following questions:
     Which business objects are to be transferred?
The business objects to be transferred depend on the business applications that you will be using. If you are using sales and distribution processing, for example, you must transfer the material masters as well as the sales documents from your legacy system.
     How are the business objects to be transferred?
The data can be transferred either manually or automatically, using an SAP data transfer program or using your own transfer program.
Process flow
During the initial data transfer, data from the external system is converted into a sequential data transfer file and then transferred into the R/3 System using an SAP data transfer program. The data transfer file is the prerequisite for successfully transferring data as it contains the data in a converted format that is suitable for the R/3 System.
1.     Check to see if an SAP data transfer program (direct input, batch input or CALL TRANSACTION) exists for this data using the Data Transfer Workbench. Refer to the notes for this transfer program.
If no SAP data transfer program exists, proceed as follows:
2.     Determine the SAP transactions that a user would use to enter data records.
3.     Record these transactions using the batch input recorder. Ensure that you have filled all of the relevant fields with data.
4.     Use this data to generate a data transfer program.
5.     Display the Data Transfer Workbench and create your own data transfer object.
6.     Now follow the steps for transferring data using the Data Transfer Workbench.
The Transaction Recorder
Use
You can use the transaction recorder to record a series of transactions and their screens.
Features
You can use the recording to create
     Data transfer programs that use batch input or CALL TRANSACTION
     Batch input sessions
     Test data
     Function modules.
The recording can be executed several times. The screens are run in exactly the same way as they were run during the recording.
You can edit recordings that you have already made using an editor.
Activities
1.     To display the batch input initial screen, choose System  Services  Batch input Edit.
2.     Choose Recording. The system now displays the initial screen of the batch input recorder.
3.     Make a recording of the relevant transactions.
4.     Generate one or several of the objects named above.
Special features
     F1 -, F4 - and self-programmed F1 - and F4 help ( PROCESS ON HELP-REQUEST , PROCESS ON VALUE-REQUEST ) are not recorded. The same applies to all commands in the System and Help menus.
     Error and warning dialogs are not recorded. This means that only the OK code field and the field contents that lead to successful further processing in the current screen.
     " COMMIT WORK " in a transaction flow indicates the successful end of the transaction as regards batch input. The recording also ends successfully.
     " LEAVE TO TRANSACTION " in the course of a transaction indicates that it is not suitable for batch input. The recording is terminated.
     In ScreenPainter screens, movements in the scrollbar are not recorded. Use the function keys F21-F24 for positioning.
Recording Transactions
The recording forms the basis of generating data transfer programs, sessions, test data and function modules.
Procedure
1.     Display the initial screen of the batch input recorder.
2.     Assign a name to your recording.
3.     Choose Create.
4.     On the subsequent dialog box, enter the transaction code that you want to record and choose Continue.
The system displays this transaction.
5.     Execute the transaction in the usual way.
6.     When you have finished processing the transaction, the system displays an overview of the transaction and your input.
Choose Get transaction if no errors occurred while the transaction was being recorded.
If you do not want to keep the last recording that you made, go to the next step.
7.     Choose Next transac. If you want to record an additional transaction. Then continue from point 4.
8.     Save your recording when you have finished.
Recording
Once you have recorded the transaction, you can process it again later.
Procedure
1.     Display the initial screen of the batch input recorder (Transaction SHDB).
2.     Choose Overview.
The system displays an overview of all recordings.
3.     Position the cursor on the relevant recording and choose Execute.
4.     Choose one of the following processing modes:
A : Display all screens.
E : Display errors only. In the case of an error, the system displays the screen on which the error occurred. Once this error has been corrected, the system continues to process the recording until the next error occurs.
N : No display. The recording is not processed visibly.
5.     Choose the update mode:
A : Asynchronous update
S : Synchronous update
L : Local update
6.     You begin to process the recording when you choose Enter to exit the dialog box. When the recording is complete, the system displays a log that lists the name of the transaction, the system field SY-SUBRC and the system messages that were output.
Using the Recording Editor
The recording editor contains functions that you can use to edit your recordings.
Procedure
1.     Display the initial screen of the batch input recorder (Transaction SHDB).
2.     Choose Overview.
The system displays an overview of all recordings.
3.     Position the cursor on the relevant recording and choose Change.
4.     The following functions are available on the overview that the system displays:
Delete transaction from the recording: This deletes the selected transaction.
Add a new transaction to the recording: The transaction is added at the end of the recording.
Editing: You can edit the current recording.
If you choose Editing, proceed as follows:
5.     The system displays an editor where you can add and delete individual lines. You can also change the contents of these lines.
6.     If these editor functions are insufficient for your requirements, you can choose Export to download the recording onto your presentation host and use a PC editor to edit it there.
7.     Choose Import to import this file back into the R/3 System. Ensure that the file is still in the correct format.
8.     Choose Check to ensure that the edited version of the recording is still syntactically correct.
9.     Save your changes to the recording when you have finished editing it.
Generating Batch Input Sessions From the Recording
The data from the recording is transferred into batch input sessions that you can process for test purposes using the usual mechanisms.
Prerequisites
Before you can generate a batch input session, you must record the transactions through which the data is to enter the R/3 System. You use the batch input recorder to do this.
Procedure
1.     Display the initial screen of the batch input recorder (Transaction SHDB).
2.     Choose Overview.
The system displays an overview of all recordings.
3.     Position the cursor on the relevant recording and then choose Generate session.
4.     Enter a session name, a user with whose authorizations the session is to be processed, the identification whether the session is to be deleted once it has been processed and the processing date.
5.     Choose Continue to exit the dialog box.
You have generated a batch input session that uses the same data for the input fields that you entered when you created the recording. You can now process this as usual.
Generating Data Transfer Programs
Prerequisites
Before you can generate a data transfer program, you must record the transactions using which the data is imported into the R/3 System. You use the batch input recorder to do this.
Procedure
1.     Display the initial screen of the batch input recorder (Transaction SHDB).
2.     Choose Overview.
The system displays an overview of all recordings.
3.     Position the cursor on the relevant recording and choose Create program.
4.     On the following screen, specify a program name.
5.     You can also choose how the maintained field contents of the recorded screens are to be filled:
Transfer the values that were used during the recording. If you require a flexible data transfer, you must modify this program.
Set the parameters of the input values to be maintained and import these values from a data file. To set the parameters, the system creates a data structure and imports the data records from an external file into this data structure. The program assumes that the external file has been adapted to this data structure.
6.     If you have decided to set parameters for the input values to be maintained, it is useful if you create a test file when you generate the program. To do this, flag the checkbox and enter a name for the test file. For more information, see creating a test file.
7.     Choose Continue.
8.     The system displays the attribute screen of the program editor. Choose the relevant attributes here and save the program.
Result
You have now generated a data transfer program that you can use to import data into the R/3 System. The program can execute the data transfer using batch input or CALL TRANSACTION .
Generating Function Modules
Prerequisites
Before you can generate a data transfer program, you must record the transactions using which the data is imported into the R/3 System. You use the batch input recorder to do this.
Procedure
1.     Display the initial screen of the batch input recorder (Transaction SHDB).
2.     Choose Overview.
The system displays an overview of all recordings.
3.     Position the cursor on the relevant recording and choose Create function module.
4.     On the subsequent dialog box, enter a function module name, a function group and a short text for the function module. Exit the dialog box by choosing Continue.
The system automatically creates the function module.
Result
You have now generated a function module that you can use as an interface for your R/3 System. As well as information relevant for the data transfer, the function module's import interface has a parameter for each input field of the transaction recorded.
Using Function Modules
Prerequisites
The function module was generated from a recording made using the batch input recorder.
Procedure
1.     Cal the function module.
2.     Supply the generic interface of the function module:
CTU : Flag whether the data is to be transferred using batch input method CALL TRANSACTION USING . The system generates a batch input session if this flag is not set.
MODE : Processing mode:
A     Display all
E     Display only errors
N     No display
UPDATE : Update mode:
S     Synchronous
A     Asynchronous
L     Local update
GROUP : (If CTU is already specified): Name of the batch input session to be generated
USER : (If CTU is already specified): User with whose authorizations the session is to be processed
KEEP : Specifies whether this session is to be deleted once it has been processed
HOLDDATE : Specifies the earliest processing date for the error session
NODATA : Defines the NODATA character
3.     Supply the function module's special interface.
For each input field that was filled when you recorded the transactions, the system creates an import parameter. The recorded value is used as the default value for this import parameter.
Creating Test Files
To test the data transfer program that you have created, you can create a data record in a sequential file. This data record contains all the field contents from the recording that are relevant to the data transfer in the format required by the data transfer program. It is therefore useful if you align the format of your conversion program data file with the format of the test file.
Prerequisites
Before you can generate a data transfer program, you must record the transactions using which the data is imported into the R/3 System. You use the batch input recorder to do this.
Procedure
1.     Display the initial screen of the batch input recorder (Transaction SHDB).
2.     Choose Overview.
The system displays an overview of all recordings.
3.     Position the cursor on the relevant recording and choose Create test data.
4.     Enter a test file and exit the dialog box by choosing Continue.
You have now created a test file.
If the test file you have specified already exists, the system appends the new data record.
If you do not specify the path, the system archives the test file in the working directory of the current application server.
Executing the Data Transfer
Purpose
You generally use the Data Transfer Workbench to execute the data transfer. The following section describes how you transfer data directly using the batch input method.
Prerequisites
You require a data transfer program. This may be an SAP data transfer program, or you can create your own program.
Process flow
1.     Provide the data to be imported in a data file. Ensure that the data is in the correct format.
2.     If you are using a generated data transfer program, you can choose a data transfer method.
If you are only dealing with one data record, you can import this directly using a generated function module.
3.     Execute the data transfer program.
4.     Analyze the program and correct any errors that occur.
Writing Data Conversion Programs
The data conversion program is responsible for the following tasks:
     Converting the data that is to be transferred into the R/3 System as required by the SAP data structure or transactions that you are using.
If you are using an SAP batch input standard program, you must generate the data structure from the SAP standard data structure (see generating an SAP data structure).
If you develop your own batch input program, the data structure is determined by the R/3 System when the program is generated. Generate a test file from the recording and align the format of your conversion program with the format of the test file.
A conversion may be necessary for data type and length data type and length. The data type required by all standard SAP batch input programs is C, character data. You can find the required field lengths either in your analysis of the data declaration structure of the generated batch input program or in the data structures that you generate.
     The data is exported in SAP format to a sequential file. The batch input program in the R/3 System reads the data in from this file.
Process flow
The tasks involved in writing a data transfer program are shown in the diagram and list below.
Writing Data Conversion Programs
The data conversion program is responsible for the following tasks:
     Converting the data that is to be transferred into the R/3 System as required by the SAP data structure or transactions that you are using.
If you are using an SAP batch input standard program, you must generate the data structure from the SAP standard data structure (see generating an SAP data structure).
If you develop your own batch input program, the data structure is determined by the R/3 System when the program is generated. Generate a test file from the recording and align the format of your conversion program with the format of the test file.
A conversion may be necessary for data type and length data type and length. The data type required by all standard SAP batch input programs is C, character data. You can find the required field lengths either in your analysis of the data declaration structure of the generated batch input program or in the data structures that you generate.
     The data is exported in SAP format to a sequential file. The batch input program in the R/3 System reads the data in from this file.
Process flow
The tasks involved in writing a data transfer program are shown in the diagram and list below.
Selecting a Data Transfer Method
When you transfer data in ABAP, you have three options to submit the data for the data transfer. Only the first two methods can be recommended without reservation. The third method, by way of CALL DIALOG, is outmoded. CALL DIALOG is less comfortable than the other methods. You should use it only if you must.
     Use the CALL TRANSACTION USING statement
Summary: With CALL TRANSACTION USING, the system processes the data more quickly than with batch input sessions. Unlike batch input sessions, CALL TRANSACTION USING does not automatically support interactive correction or logging functions.
Your program prepares the data and then calls the corresponding transaction that is then processed immediately.
The most important features of CALL TRANSACTION USING are:
o     Synchronous processing
o     Transfer of data from an individual transaction each time the statement CALL TRANSACTION USING is called
o     You can update the database both synchronously and asynchronously
The program specifies the update type
o     Separate LUW (logical units of work) for the transaction
The system executes a database commit immediately before and after the CALL TRANSACTION USING statement
o     No batch input processing log
     Create a session on the batch input queue.
Summary: Offers management of sessions, support for playing back and correcting sessions that contain errors, and detailed logging.
Your program prepares the data and stores it in a batch input session. A session is a collection of transaction data for one or more transactions. Batch input sessions are maintained by the system in the batch input queue. You can process batch input sessions in the background processing system.
Your program must open a session in the queue before transferring data to it, and must close it again afterwards. All of these operations are performed by making function module calls from the ABAP program.
The most important aspects of the session interface are:
o     Asynchronous processing
o     Transfers data for multiple transactions
o     Synchronous database update
During processing, no transaction is started until the previous transaction has been written to the database.
o     A batch input processing log is generated for each session
o     Sessions cannot be generated in parallel
The batch input program must not open a session until it has closed the preceding session.
     Use the CALL DIALOG statement
Summary: Not recommended if you can enter data by way of sessions or CALL TRANSACTION USING.
Your program prepares data for a sequence of dialog screens, and calls a dialog module for immediate processing.
The most important aspects of the CALL DIALOG interface are:
o     Synchronous processing
o     Transfers data for a sequence of dialog screens
o     No separate database update for the dialog
A database update occurs only when the calling program executes a commit operation.
o     Shares LUW with calling program
o     No batch input processing log is generated
Executing Data Transfer Programs
Procedure
If you are using an SAP data transfer program, follow the procedure specified in the program documentation.
If you are using a generated data transfer program, proceed as follows:
1.     Start the data transfer program.
2.     Decide which batch input method you want to use for the data transfer.
a) CALL TRANSACTION USING:
You must specify the:
Processing mode: You use this parameter to specify whether processing should take place in the background or in dialog mode.
Possible values are:
A     Display all
E     Display only errors
N     No display
Update mode: This parameter determines how the data is to be updated:
Possible values are:
S     Synchronous
A     Asynchronous
L     Local update
Error session: Here you have the option to specify a session name for a batch input session in which data is to be written in the case of an error. You can use this to identify incorrect data records after the batch input program has run and to import the records into the R/3 System once you have corrected them.
If you are creating an error session, you must also specify:
User: Specify the user with whose authorizations the sessions are processed.
Keep session: This specifies whether or not the session should be deleted once it has been processed.
Lock date: Specify the processing date for the error session.
b) Generate session:
Session name: Specify a name for the batch input session to be generated.
User: Specify the user with whose authorizations the sessions are processed.
Keep session: This specifies whether or not the session should be deleted once it has been processed.
Lock date: Specify the processing date for the error session.
3.     Specify a character that is to be used as the NODATA character.
4.     Specify the path of the data file from which the data is to be imported into the R/3 System.
5.     Execute the program.
6.     If you have generated a session, or if errors occurred in CALL sTRANSACTION USING mode, you must now edit the generated sessions. You can find information on this in BC - System services in batch input sessions.
Batch Input Authorizations
You do not need special authorization - other than the ABAP run time authorization (authorization object S_PROGRAM - to run a program that creates batch input. Any user can create batch input sessions.
Starting processing for a session once it is in the queue is another matter, however. You can find more information on this in batch input sessions.
Creating a Session with BDC_OPEN_GROUP
Use the BDC_OPEN_GROUP function module to create a new session. Once you have created a session, then you can insert batch input data into it with BDC_INSERT.
You cannot re-open a session that already exists and has been closed. If you call BDC_OPEN_GROUP with the name of an existing session, then an additional session with the same name is created.
A batch input program may have only one session open at a time. Before opening a session, make sure that any sessions that the program closes any sessions that it previously had opened.
BDC_OPEN_GROUP takes the following EXPORTING parameters:
     CLIENT
Client in which the session is to be processed.
Default: If you don't provide a value for this parameter, the default is the client under which the batch input program runs when the session is created.
     GROUP
Name of the session that is to be created. May be up to 12 characters long.
Default: None. You must specify a session name.
     HOLDDATE
Lock date. The session is locked and may not be processed until after the date that you specify. Only a system administrator with the LOCK authorization for the authorization object Batch Input Authorizations can unlock and run a session before this date.
Format: YYYYMMDD (8 digits).
Default: No lock date, session can be processed immediately. A lock date is optional.
     KEEP
Retain session after successful processing. Set this option to the value X to have a session kept after it has been successfully processed. A session that is kept remains in the input/output queue until an administrator deletes it.
Sessions that contain errors in transactions are kept even if KEEP is not set.
Default: If not set, then sessions that are successfully processed are deleted. Only the batch input log is kept.
     USER
Authorizations user for background processing. This is the user name that is used for checking authorizations if a session is started in background processing. The user must be authorized for all of the transactions and functions that are to be executed in a session. Otherwise, transactions will be terminated with "no authorization" errors.
The user can be of type dialog or background. Dialog users are normal interactive users in the R/3 System. Background users are user master records that are specially defined for providing authorizations for background processing jobs.
Adding Data to a Session: BDC_INSERT
Use the BDC_INSERT function module to add a transaction to a batch input session. You specify the transaction that is to be started in the call to BDC_INSERT. You must provide a BDCDATA structure that contains all of the data required to process the transaction completely.
BDC_INSERT takes the following parameters:
     TCODE
The code of the transaction that is to be run.
     POST_LOCAL
Parameter to update data locally. If POST_LOCAL = X, data will be updated locally.
(refer to the keyword documentation of SET UPDATE TASK LOCAL for more information)
     DYNPROTAB
The BDCDATA structure that contains the data that is to be processed by the transaction.
DYNPROTAB is a table parameter in the function module.
Closing a Session: BDC_CLOSE_GROUP
Use the BDC_CLOSE_GROUP function module to close a session after you have inserted all of your batch input data into it. Once a session is closed, it can be processed.
Function Module BDC_CLOSE_GROUP
Exception parameters
Parameter     Function
NOT_OPEN     Client
QUEUE_ERROR     Internal use
BDC_CLOSE_GROUP needs no parameters. It automatically closes the session that is currently open in your program.
You must close a session before you can open another session from the same program.
You cannot re-open a session once it has been closed. A new call to BDC_OPEN_GROUP with the same session name creates a new session with the same name.
Processing Batch Input Sessions
When you create a batch input session, it remains in the batch input queue until it is explicitly started. Session processing can be started in two ways:
     An on-line user can start the session using the batch input menu options. (To access the batch input options, choose System  Services  Batch Input.)
     You can submit the background job RSBDCSUB to start a session in background processing. If several sessions have the same name, RSBDCSUB starts them all.
Its possible to coordinate the generation and execution of a session in the background processing system.
You can, for example, schedule both the batch input program and RSBDCSUB in the background. If you designate the batch input job as the predecessor for RSBDCSUB, then RSBDCSUB will be started automatically when the batch input job successfully completes.
Alternatively, you can schedule both the batch input program and RSBDCSUB as job steps in a single background job. In this case, however, RSBDCSUB is started even if the batch input program should terminate abnormally.
For detailed information about processing batch input sessions, see Managing Batch Input Sessions in the System Services guide.
Frequent Data Transfer Errors
The most frequent errors include:
     The BDCDATA structure contains screens in incorrect sequence.
     The BDCDATA structure assigns a value to a field that does not exist on the current screen.
     The BDCDATA structure contains a field that exceeds the specified length.
General guidelines
You should be aware of the following guidelines when you create sessions and call transactions or dialogs:
     You must provide data for all required fields on a screen.
     You can only specify the initial data for a screen. The system does not accept input as a response to a warning or an error message.
     If there is more than one possible screen sequence for a transaction or dialog, your program specifies the screen sequence for the transaction. You must transfer all screens that the dialog user sees to the selected screen sequence. This applies even if the screen itself is not used to input data.
Direct Input
To enhance the batch input procedure, the system offers the direct input technique, especially for transferring large amounts of data. In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not process screens. 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. To maintain and start these programs, use program RBMVSHOW or Transaction BMV0.
Examples for direct input programs are:
Program     Application
RFBIBL00     FI
RMDATIND     MM
RVAFSS00     SD
RAALTD11     AM
RKEVEXT0     CO-PA
Pls reward points.
Regards,
Ameet

HT5839 Save files under Tags without single virtual location

Today I was wondering about the OS X Mavericks tagging system. Sometimes I try to save a file, such as an image, in the TAGS section of the finder window in Mac OS X. As soon as I do so, because it is not a location rather a search algorithm that searches for files in multiple locations, because the computer to hang. I wanted to ask if you can actually save the file as a tag,and if not then why allow it appear available in the save dialog pop-up window.it appears within the save dialog interface, and so I tried it out various times. My computer just hangs and Finder becomes unusable.my Logic says, it cannot be possible to save the file under tags, unless OS X has programmed itself to save the files and SQL data instead of as an actual file.
This would require database settings and reprogramming into the OS X Mavericks system. I should definitely think about saving files under the tag section,if it is possible, and how one will achieve it as a programmer and developer. It would be an excellent way to file things without any necessity, for knowing where they are. So long as one saves every file with the right tags. Of course one could then save under a main tag and add more tags in the text dialogue interface which pops up when you are saving a file.
Or one could remove it from the save dialogue interface completely, to avoid crashes and confusion.attack is not a particular location but then again neither is a folder really. Both folders and tags are just virtual binary code translated into pixels on the screen. I therefore do not really see any difference between an album, a folder, a photo stream, or attack or I could take very. To the binary system they are just different waysof presenting virtual data in a visual way so that humans can interface with it.but tags can be added to a file as more than one tag. And this allows for multiple terminologies and search filters to be used when searching for a file. It allows for cross reference searching.
Tagging files in OSX is an art and a science, which one must learn and have a very strict regimen with oneself, in order to achieve a truly organized filing system. but, if you truly must of this ought and I strict enough with yourself to organize your tags properly, you can have an extremely powerful way of accessing your data without having to have too many folders and visual interfaces to find them with. This requires that you manually name and tag all of your files of costs which if you work with hundreds of files a day is rather tiresome.
but that is like planting a field of flowers, you must plod along every day until you have thousands of them and it becomes enough to be called a field. Once you have planted plenty, and that means you have created lots of tags, and have the discipline to name every saved file under is relevant tags, then finally, once you have thousands of files, this will become an indispensable way of arranging and searching for your work files

Thanks for input. The price changes occur infrequently - Norton/ Symantec software. Not a lot of sku's to make a database plus page is flowery and does not need to be searched on by the user. Links connect directly to Norton. Now I make the changes on one page and "Save as" to the others but my button links fail. It is curious CS4 would make the change from images of the link in the actual link box in html. In view it works fine but on site buttons are not visible?

Illustrator SDK sample: Windows plug-in error when exporting to EMF

Hi All,
I'm trying to create a plug-in that exports a whole AI document or just a selected portion of it to an EMF file.
I've used classes from [SnippetRunner] SDK sample, i.e. from \Code Snippets folder, and I've encountered a very strange behavior when calling
SnpDocumentActionHelper::ExportDocument(ActionDialogStatus dialogStatus, AIActionParamValueRef parameters)
with formats such as WMF, EMF etc.
If function sAIActionManager->PlayActionEvent() is called with 'kDialogOff' status an error message "The plugin cannot complete because of an unknown error" appears, although the export is completed and the return code is 'kNoErr'.
If I try exporting with a dialog interface (omit parameters or 'kDialogOn') everything is fine.
I checked it both for CS3 and CS4 SDK, as well as for WinXp and WinVista.
I also tested with the actual sample plug-in (SnippetRunner), same behavior.
Is this an SDK bug? Any ideas?

I don't have a lot of experience with this kind of problem, but the first thing I'd check is the parameter block you're passing the action call. I don't know why it would matter if the dialog appeared or not, unless the export settings block wasn't being filled in with everything it needs?
You might try recording an export you perform manually via the action palette, and then saving it to a file. You can open it up manually and compare it (even if it's a binary block) to what you're doing in code. You might spot something that way.
I don't know what else to suggest though. It's unlikely to be an SDK bug, though it could be a bug in the action-aware part of the exporter.

CAD Dialog Interfaces

Similar Messages

Maybe you are looking for