Migrating from Adobe Output Pak to NW04+

Does anyone have any information/documentation regarding the migration path from Adobe Output Pak solutions built on R/3 4.6 (or the like) to Adobe Interactive Forms for ECC 6.0? ; If the client would like to maintain their existing solution on Adobe Output Pak is it supported for NW04+ versions? What are the challenges of moving Adobe Output Pak solutions to Adobe Interactive Forms? Does this require complete rework of the solutions or can the solutions just be migrated? Based on SAP's comments it looks like SAPscript requires modification (but to what extent) and SmartForms can be migrated with minimal to no rework. Is this true?

Thanks for the questions:
Yes, the Output Pak solution will still work and is still supported with NW04 & NW04S systems. So there is really nothing the customer has to do to keep working the way he always has.
As for the conversion from Output Pak to Interactive Forms by Adobe the answer is a little more complicated (sorry). I assume you're working from SAPScript forms. You need to consider the parts of the OutputPak solution that need to be migrated. There is the SAP Print program, the SAPScript layout set and the Adobe form (IFD).
There is no solution for automatically migrating the print program or the layout set into the Forms processing interface and context. The paradigms are just too different. Depending on how customized the print program is, you will either need to re-develop it or go to the SAP standard print program for the scenario and redo any customizations.
You can convert the IFD to an interactive form. The first thing you need is the latest Output Design to be installed on the same workstation as the Adobe Designer. Then, in transaction SFP, go to the Layout tab to bring up the Designer. Then use the "Tools->Import" command to bring the IFD into Designer. That will bring in the structure. Of course the data binding is probably all wrong at this point but it's pretty easy to fix that by just using drag-and-drop from the schema onto the for fields. You may need to do some scripting as well since the old preamble code will not be brought it. There may be other parameters on subforms that you need to set to get the same effects you used to set up in the preamble.
Now for some brutal honesty - I've never done this and I don't know of anyone who has, so you're breaking new ground if you try it.. I know that this should work in theory but...
If you do try it out, please let me know how you make out. If you have questions I'll try to answer them but sometimes it's a while before I can get back to you. If it takes too long, please just prod me at [email protected].
Best of luck
Les

Similar Messages

Migrating forms from Adobe Output Designer 5.5 to Adobe Document Server

Hi,
I have several form templates / layouts that have been created in Adobe Output Designer 5.5 (for mySAP) and I want to migrate these form templates so that they can been used in SAP Adobe Document Server.
Does anyone have any information on this? Any tools available? Documentation? Links?
cheers,
Joseph Gill
SAP Developer

I would think the common sense approach would be to upgrade to ECC 6 first then migrate your forms.
This seems to be just another step in the upgrade process.
We went from 4.7 to ECC 6, but only had Smartforms and SAPScripts. We wound up just re-creating the forms directly in Adobe.

Migration from "Adobe Photoshop Album Decouverte" to "Adobe Photoshop Elements 12"

Hello,
Is it possible to migrate all the data I have in Adobe Photoshop Album Decouverte and import it in Adobe Photoshop Elements 12 ?
Thank you for your advice !
Marc

Finally I could solve the problem.
I tried to import the Backup.tly in Photoshop Elements, but without success. Even there an Error appeared. The conversion tool also still got this failure at a progress of 15% conversion... So I searched a reason for the failure in google and found this helpful article from Adobe. It says that you should look for the corrupt images in the log file. So did I, and I found the error causing picture on the old computer and deleted it. After that I opened Photoshop Album, clicked on "File > Reconnect all missing files" and deleted this picture from the catalog.
Now I didn't want to make the backup again, because the last nearly had 1h. So I decided to try it again by just copying the catalog.psa from the old computer to the new one and to convert it again with the conversion tool. The error came again, but at a progress of 22% So i had to do this a few times: Searching the corrupt image in the log file, deleting it on the old computer, deleting the missing file in Photoshop Album and converting it. And finally, it worked, no error after conversion! I let photoshop elements 13 open the new .pse13 file. Now, all tags and albums were back on Photoshop Elements. Eventually, I let the programm searching the new paths of all the images. It takes a time but it works great now. Thanks for your help, I would recommend the Adobe Community & support!

ASV plugin to FLEX migration from Adobe?

Has Adobe provided any migration path from ASV 3 plugin to
Flex when they announced EOL for ASV plugin and recommended Flex
instead?
I thought it is just a pure common sense to make the
migration path smoother. Yes Adobe wanted to make money and that's
how Flex was born and ASV was trashed. Now, I see everyone is
struggling towards migration from ASV to other alternatives. No
luck there.
Are we supposed to re-write entire SVG generation code to
adapt to Flex technology? Just pure non-sense to me!

trying once again??

Migration from Adobe Elements (Win XP) to Aperture 2

I am moving from a Windows XP machine with Adobe Elements 4 to an iMac and Aperture 2.1. I need to move thousands (6000 ??) of images to Aperture 2.1 and hopefully keep my metadata (keywords, tags and ratings) in the process. Both machines are connected to a LAN and I also have a network drive which I use as a backup device and shared storage. The majority of the files are JPEG (95%) with a few Canon RAW images in the mix.
Is there a recommended method of migrating Adobe Elements 4.0 files to Aperture 2.1?

I, too, would like to migrate from Photoshop Elements 4.0 on Windoze XP to Aperture 2.0 on OS X. And I'm hoping there's a way to migrate all 601,012 of my tags to Aperture instead of having to redo them all as Aperture keywords manually.
Does anyone know if this is possible? Or perhaps there's a utility to write Elements' tags as EXIF/IPTC prior to moving the files over and importing them into Aperture?

Help in migrating from adobe forms 6.0 to 7.1

Hi
I have a set of adobe templates that have been developed in Adobe Livecycle designer version 6.0.
Now I will have to move these to Adobe LiveCycleDesigner 7.1
I could get a document 'Compatibility of Adobe Designer 6.0 for designs with Adobe LiveCycle Designer 7.1"
I read abt the text formatting compatibility and event model compatibility of the form designs.
What could be the best way to do this?
If i open the version 6.0 in Adobe LiveCycle Designer 7.1 and do a simple "save-as"...will it work??
Appreciate your response
Thank you

It is not the Designer per se that decides what is supported in your template ...it is the target version that you are designing to. So when you open it in Designer 7.1 then go into Form Properties/Defaults you will be given additional options for the target version. If you target version 7 then you can test the things that you mentioned .....if it causes you issues then you can change the target version to 6 and all should be the same as before.
Paul

Migrating from Adobe Lightroom to Aperture

What is the best way to do this and maintain keywords, settings, etc.. I have imported folders as projects from my Lightroom library, but I'm not sure that I got exposure corrections this way. I think that I just got the original Raw files.
Thanks,
Ken

Aperture can't currently read sidecar files, even though it can generate them.
But that would still only bring across keywords and metadata, not any of the image adjustments.
Ian
EDIT - if you mean exporting converted files (TIFFs or JPEGs) then everything should come across, but of course you'd be losing the advantage of lossless changes to RAW files.

Migrating settings from Adobe Acrobat X to Adobe Acrobat XI

Hi,
Due to the deployment of Office 365 I need to upgrade 300+ people from Adobe Acrobat X to Adobe Acrobat XI.
Most of these users sign documents using digital signatures and therefore have a Digital ID and one or more custom Signature Appearances.
After upgrading to Adobe Acrobat XI, the Digital ID and Signature Appearances settings aren't migrated from Adobe Acrobat X.
Does anyone know whether it is possible to migrate the setting during the installation, or programmably after the installation completes?
Thanks,
Anne.

Hi Sukrit,
Thanks for taking the time to provide some advice, it is much appreciated.
Unfortunately the link you provided doesn't explain how to export/import the security settings during the installation of a new version of Adobe or programmably after the installation completes.
Regards,
Anne

Adobe Output Designer Migration

Hello,
our customer has implemented Adobe Output Designer version 5.6 in Poland. We were asked for outsourcing of their Adobe printing solution. Could somebody help us please to answer the following questions:
1) Is it possible to migrate content of Adobe Central Output Server resp. Adobe Output Designer without physically moving hardware? If yes, how can be such migration provided?
2) Do we need to install the same version 5.6 of the Adobe Output Designer or we can install the version 5.7 and migrate the Adobe Output Designer content?
Thank you
Martin Dedouch

Look here: http://www.adobe.com/products/server/outputdesigner/overview.html
There is a link at the top to have Adobe contact you.

Migrating from Windows (Adobe PE + Bridge(?)) to Mac (iPhoto + Adobe PE)

I have a family member who is thinking about switching from Windows to a Mac. She is currenlty using Adobe stuff on Windows (PE 4) where she edits and organizes her photo's.
I've set her up for trial with one of my Macs with PE 4 installed. Now the question is, will she be using iPhoto or Adobe Bridge on the Mac and what is more important, how can she migrate in either situation?
Personally, I think iPhoto/PE is the best solution, but how should she migrate her Windows photo database to het Mac and might migrating to Adobe bridge not be easier?

Gerben:
If Photo Bridge can write the metadata, primarily the keywords, to the files then importing the folders that the file are located in will create rolls in iPhoto with the same title as those folder. Also the keywords should be read by iPhoto and included in its database.
As you know iPhoto is a image management application but one with the additional features of slideshows, books,etc. It can group photos by whatever criteria the user want. Bridge is primarily a browser type application.
To migrate her Windows photos to iPhoto she should first copy the folders of image files to the Mac. Then download and run BatChmod on each folder with the settings shown here, putting your administartive name in the owner and group sections. You can either type in the path to the folder or just drag the folders into that field. This will assure that the permissions/ownership are properly set before importing into iPhoto.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've written an Automator workflow application (requires Tiger), iPhoto dB file backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Hi all, i am missing the output to web and pdf in Bridge , any option to get it in the bridge from adobe creative cloud

Hi all, i am missing the output to web and pdf in Bridge , any option to get it in the bridge from adobe creative cloud
@bridge

Have a look at Install Adobe Output Module

Migrate an Adobe form from sfp into developer studio

Hello,
does anyone know if there is a way to migrate an Adobe print-form out of the SFP-transaction into the Netweaver developer studio? (so that it can be integrated into a web dynpro)
I know it is possible if the forms are designed in the Adobe Designer as a stand-alone application..
And I have also already tried downloading the form as an xml-file from the SFP-transaction and then renaming it .xdp to be able to import it into the designer.
But I noticed in the xml file that the SFP-transaction generates items that makes the template useless for other applications.
Anne Kathrine

Adobe Reader (which is showing you your PDF even inside SAP) has built in function allowing to scale document to the size of paper in the printer. But this is function of Adobe Reader (not the form itself) and can help only if you are ready for some "help" from the user at the time of printing.
If you want to do it directly (without user intervention), than I'm afraid there are no built-in function for page scaling inside PDF. But you can include two master pages of different sizes in the design of your Adobe form and choose one of them during form generation according to your needs. Please have a look at my old post [here|Is it possible to trigger the pages differently; on how to do it.

Does FCP 7 support 4k from Sony NEX-FS700UK Super 35 Camcorder? Or should i migrate to Adobe?

Does FCP 7 support 4k from Sony NEX-FS700UK Super 35 Camcorder? Or should i migrate to Adobe?

You might be interested in this article.
MtD

I just migrated from one Mac to another and I got a msg to contact Adobe tech support and report error code 150:30. What do I do?

I just migrated from one Mac to another and I got a msg to contact Adobe tech support and report error code 150:30. What do I do?@

Reinstall the software properly. Migration is useless due to the specifics of the activation system.
Mylenium

Upgrade + migration from nw04 on windows 2000 to nw04s on windows 2008

Dear all,
I need to upgrade and migrate my nw04 java system from windows 2000 to nw04s on windows 2008.
From the PAM I can see that NW04 is not supported on windows 2008 and that nw04s (7.0) is not supported on windows 2000.
So, which is the correct upgrade path? Do I need an intermediate win 2003 server which is supported from both the releases?
Thanks and regards in advance
Federico

Hello my friend
This will be a very interesting project for sure. As you know, kernel 640 is not supported on win2008 and 700 is not supported on win2000, so here there must be a win2003 as a transition platform for this upgrade+ migration, not to mention migration from 32bit to x64 is also involved. You didn't mention the DB versions in source and target systems, as well as the SAP product you're trying to go with. Here's a brief checklist right now for what I can think of, once you're back with more details then let's make it intact:
I assume your source OS/DB is win2000SQL2000 32bit, target one is win2008SQL2008 x64.
1. Install a win2003 x64 server and SQL2000 32bit;
2. Install a new SAP instance same as your source system release in 32bit compatible mode;
note: if the system being migrated is BW, then be aware of that you might want to bring new features in SQL2008 of row compression and table partitions.
3. Detach the source DB from old SQL2000, and attach it to new SQL2000; some post configuration for DB copy will be required (STM tool). Now you've finish a migration from win2000 to win2003 32bit;
4. Start upgrading NW04 to 7.0, 640 to 700, find details in upgrade guide; Now you have your 700 instance on win2003 x64+SQL2000 32bit;
note: since release 701(700 EHP1) is available now, which you might want to upgrade instead of 700.
5. Change the collation 850BIN2 for SQL2000 32bit, detach DB;
6. Since migration from 32bit to x64 cannot be done smoothly, now you have to uninstall everything and reinstall win2003 and SQL2008 x64, followed by a new 700 or 701 instance;
7. Attach the source DB, post configuration for DB copy will be required (STM tool); Now you have your 700 or 701 instance on win2003 x64+SQL2008 x64;
8. Detach the SQL2008 DB;
9. Now go to your target win2008 OS, install SQL 2008 x64 and new 700 or 701 instance;
note: there might be some restrictions for NW 7.0 on win2008, go with the latest release (SR3 or newer).
10. Attach DB to this final OS/DB version: win2008 x64+SQL2008 x64, post configuration for DB copy will be required (STM tool).
Helpful?
Regards,
Effan

Migrating from Adobe Output Pak to NW04+

Similar Messages

Maybe you are looking for