Best Practice for re-usable forms in multiple Countries

Dear experts,
i'm seeking for suggestions about the best design which could help saving time on development for multiple forms i should produce for a multi-national client.
In more details, the client is asking to create a number of forms in the SD area (Order advice, delivery note/Bill of Lading, Payment slips and in particular Billing outputs) for different Countries in North and South America.
I'm striving to avoid creating separate forms for separate Countries, as ideally i'd want to create just one form per type (i.e. one form for Billing, one form for Delivery note...) and re-use the same forms for all Countries, where specific data should differ from one Country to the other.
We've been working on similar topics in the past, adding some logic behind some texts which we've made "parametric", meaning different standard texts are printed in the same box depending on some organizational values (i.e. sales organization or company code), but we're looking for something "smarter", where having different pricing structures in different Ctries, for instance, might still work if those Conutries use the same billing form
Is there any best practice you'd like to share with me with regards to this? Is there any new functionality SAP has delivered recently which helps in this direction?
Many thanks to all who will want to reply to my weird question.
Regards,
Fabio

Hi Scott.
Storing two columns of spatial data is fine in SQL Server. And you are correct that there is no built-in reprojection in SQL Server, most folks do that as part of data loading. There was talk of porting parts of ogr2ogr to SQLCLR, but I don't think anyone
did that.
Cheers, Bob

Similar Messages

SAP Best practice for Material request form

Hai Sap gurus,
Do we have any sap best practice for material request form? If so please help me to find this best practice provided by the SAP. I searched through sap help but i was unable to find one.
Same way i also need to find the sap best practice for Change request form too...
Thanking you all in advance.

Hi,
Check these links
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2b50ac90-0201-0010-d597-8d833833f9e0
and using the service market place link to down load the best practices
http://www.sap.com/services/bysubject/servsuptech/index.epx

Best Practice for PDF print forms based on SAP standard

Hi,
I have copied the SAP standard PDF form F_D_INT_SCALE_00 to a Z form, and am using it in conjunction with the standard print program RFDZIS01_PDF. However I need to output some additional fields that are not supplied by the print program / interface (for example Customer VAT number).
What is the best practice for achieving this? As far as I can see the only way is to take a copy of the standard print program and modify it to select the extra data, and modify the interface. I never like taking copies of standard programs though for obvious reasons.
If I had this requirement with a smartform it would be a simple case of embedding ABAP code into the Z smartform and leaving the print program alone, but unfortunately there is no provision for the non-PDF version of the Interest Letter to be sent by email.
Thanks in advance,
Vindaloo

Thanks for your reply Robert.
However I think you are referring to Smartforms when you mention Code Initialization and Global Data declarations. I need to know the best way to modify copies of standard Adobe Print Forms.
Regards,
Vindaloo

Best Practice for the Service Distribution on multiple servers

Hi,
Could you please suggest as per the best practice for the above.
Requirements : we will use all features in share point ( Powerpivot, Search, Reporting Service, BCS, Excel, Workflow Manager, App Management etc)
Capacity : We have 12 Servers excluding SQL server.
Please do not just refer any URL, Suggest as per the requirements.
Thanks
srabon

How about a link to the MS guidance!
http://go.microsoft.com/fwlink/p/?LinkId=286957

Best Practice for thinning Oracle Forms

We are considering upgrading from 10g (10.1.2.3) to (probably) 11g forms initially whist long term migrating to ADF.
Our system is 15 years old and has many issues that go along with a system this old i.e. database keys/indexes missing, forms with lots of code etc.
We have very few resources so thought the best way to go about this would be to thin out all our Oracle forms in 10g prior to upgrade (as this is mainly just a recompile in 11g) but was looking at if there were any best practices as to what level this should be done.
For example we heavily use PLLs. Should the majority of this code be moved into packages or are PLLs ok to use. I take it the majority of program units should be moved to db.
How thin should we aim to make the form. i.e if we are using post queries for something as simple as select customername into :nondbitem from customer where customerid =:customerid. Should we be making this a function in the db and reusing the code in the necessary places?
Just wondering what people would deam best practice before we start.
Thanks

Thanks for all your input.
Although the current database design is not correct we are going to correct the existng database rather than rewriting it.
So were hoping to correct this also!
But what im doing now to get rid some of this post queries for nondbnames is im creating a view of all information i need to display on one pertaining record.
Then i used this view like block basic procedure like relationship to the transactional block.So if you make queries or insert (need to run query the block view) it will give all the necessary record display"
{CODE}
This sounds sensible but we havs hundreds of tables with lots of columns. How are you managing the views/deciding how manytables/columns to include on the forms?

Best practice for TM on AEBS with multiple macs

Like many others, I just plugged a WD 1TB drive (mac ready) into the AEBS and started TM.
But in reading here and elsewhere I'm realizing that there might be a better way.
I'd like suggestions for best practices on how to setup the external drive.
The environment is...
...G4 Mac mini, 10.4 PPC - this is the system I'm moving from, it has all iPhotos, iTunes, and it being left untouched until I get all the TM/backup setup and tested. But it will got to 10.5 eventually.
...Intel iMac, 10.5 soon to be 10.6
...Intel Mac mini, 10.5, soon to be 10.6
...AEBS with (mac ready) WD-1TB usb attached drive.
What I'd like to do...
...use the one WD-1TB drive for all three backups, AND keep a copy of system and iLife DVD's to recover from.
From what I'm reading, I should have a separate partition for each mac's TM to backup to.
The first question is partitioning... disk utility see's my iMac's internal HD&DVD, but doesn't see the WD-1TB on the AEBS. (when TM is activity it will appear in disk utility, but when TM ends, it drops off the disk utility list).
I guess I have to connect it via USB to the iMac for the partitioning, right?
I've also read the benefits of keeping a copy of the install DVD's on the external drive... but this raises more questions.
How do I get an image of the install DVD onto the 1TB drive?
How do I do that? (install?, ISO image?, straight copy?)
And what about the 2nd disk (for iLife?) - same partition, a different one, ISO image, straight copy?
Can I actually boot from the external WD 1TB while it it connected to the AEBS, or do I have to temporarily plug it in via USB?
And if I have to boot the O/S from USB, once I load it and it wants to restore from the TM, do I leave it USB or move it to the AEBS? (I've heard the way the backups are created differ local vs network)>
I know its a lot of question but here are the two objectives...
1. Use TM in typical fashion, to recover the occasion deleted file.
2. The ability to perform a bare-metal point-in-time recovery (not always to the very last backup, but sometimes to a day or two before.)

dmcnish wrote:
From what I'm reading, I should have a separate partition for each mac's TM to backup to.
Hi, and welcome to the forums.
You can, but you really only need a separate partition for the Mac that's backing-up directly. It won't have a Sparse Bundle, but a Backups.backupdb folder, and if you ever have or want to delete all of them (new Mac, certain hardware repairs, etc.) you can just erase the partition.
The first question is partitioning... disk utility see's my iMac's internal HD&DVD, but doesn't see the WD-1TB on the AEBS. (when TM is activity it will appear in disk utility, but when TM ends, it drops off the disk utility list).
I guess I have to connect it via USB to the iMac for the partitioning, right?
Right.
I've also read the benefits of keeping a copy of the install DVD's on the external drive... but this raises more questions.
Can I actually boot from the external WD 1TB while it it connected to the AEBS, or do I have to temporarily plug it in via USB?
I don't think so. I've never tried it, but even if it works, it will be very slow. So connect via F/W or USB (the PPC Mac probably can't boot from USB, but the Intels can).
And if I have to boot the O/S from USB, once I load it and it wants to restore from the TM, do I leave it USB or move it to the AEBS? (I've heard the way the backups are created differ local vs network)
That's actually two different questions. To do a full system restore, you don't load OSX at all, but you do need the Leopard Install disc, because it has the installer. See item #14 of the Frequently Asked Questions *User Tip* at the top of this forum.
If for some reason you do install OSX, then you can either "transfer" (as part of the installation) or "Migrate" (after restarting, via the Migration Assistant app in your Applications/Utilities folder) from your TM backups. See the *Erase, Install, & Migrate* section of the Glenn Carter - Restoring Your Entire System / Time Machine *User Tip* at the top of this forum.
In either case, If the backups were done wirelessly, you must transfer/migrate wirelessly (although you can speed it up by connecting via Ethernet).

Best practices for sharing iPhoto libraries across multiple Macs

I have a pair of iMacs running 10.6.x. and iPhoto 11 connected via Ethernet to an Airport Extreme. I am looking for a way to share my iPhoto library between the two Macs.
I found an Apple Support note on the topic (http://support.apple.com/kb/HT1198) which states that a disk image is a supported location for a shared iPhoto library (with limitations acceptable to me) and it strikes me that this would be a way of hosting a shared iPhoto library onto a NAS device.
Am I missing a simpler solution or, more importantly, am I missing any blindingly obvious caveats? I'd love to hear from anybody who has tried this (successfully or otherwise) or anybody who has a better idea. I haven't bought a NAS device yet, so I'm open to alternative suggestions.
Specific requirements:
Members of my family use either one of a pair of iMacs.
The only user who edits the iPhoto library is me and I only need read/write access from one machine.
iPhoto library access limited to one user at a time is acceptable and practical in my case.

Easiest:
If the other users only get to see the Library then just use iPhoto Sharing.
Enable sharing in the iPhoto Preferences on the Host machine, then go to the other macgine and in the same location enable 'Look for Shared Libraries'
Other forms of sharing will give the users read/write access to the Library.
A strong warning: If you're trying to edit the Library (that is, make albums, move photos around, keyword, make books or slideshows etc.) or edit individual photos in it via Wireless be very careful. Dropouts are a common fact of wireless networking, and should one occur while the app is writing to the database then your Library will be damaged. Simply, I would not do this with my Libraries.
Regards
TD

Best practice for sharing LOV's over multiple Application Definitions?

We want to define/generate (complex) LOV's in 1 place and use them in multiple sub-applications (different application definition files).
What is the best practive to accomplish this?
Frank

Frank,
Here is what you do:
- Generate the LOV the "normal" way using your first app def file
- In all other app def files, you create a "dummy" LOV group by the same name with the same items, so you can associate items with the LOV and specifiy return values
- For each "dummy" LOV group uncheck the checkboxes "Generate Pages", "Generate Page Definitions" and "Generate Controller Group". (only visible in expert mode)
- Make sure you first generate the first app def file before you run the [ages generated by other app def files.
Steven Davelaar,
JHeadstart Team.

Best practice for setting up iCloud with multiple devices using a single AppleID

Hi there
Me and my wife have an iPhone each, and are looking at getting both of us using iCloud. The problem is that we only use one Apple ID for our music library.
Is getting a separate Apple ID necessary for each device on iCloud, or can multiple devices have seperate settings/photos/music, etc.?

Using different Apple ID for iCloud is not necessary, but in most cases it is recommended.
You can however choose to use separate Apple IDs for iCloud and continue to use the same Apple ID for iTunes, thereby being able to share all your purchases of music, apps and books.

Best practice for code structure to control multiple devices in a 2 stage-sequence

I have a question about code architecture and getting multiple devices controlled and sychronized for one experiment. This is an "architecture"-type inquiry, so I am hoping for some suggestions on how to proceed.
I run an experiment in which I control 2 NI PCI-6733. I am soon to add a Tektronix AFG 3022B, and have long been putting off an opportunity to rewrite my labview code from the ground up. I inherited it from an earlier research, and while functional, I would like to make it easier to modify and break up into subVi's and such. Link to the current program (labview 8.6.1) is here if you would like to see the code that is currently used, and the subvi's are in a zip file. The current version of the experiment consists of just one stage, all the writing of the data to the PCI cards is saved for the end. I need to change this in my new setup though.
The new experiment consists of 2 stages. The first will run (looping an output array to the PCI cards) until it hears a "true" from another computer (connected via TCP). At that point, it should switch to stage 2 and run a sequence (usually 10^5 timeunits in length, where the time unit is 0.1 ms) that outputs to the two PCI cards, the AFG 3022B, and with the flexibility to add more devices in the future.
Most appreciated would be structural advice. How to arrange the VIs, if it's good to use a "master" VI that would control the two subVi's of stage 1 and 2, etc... Feel free to ask for more details if it would help clarify my question. Thanks!
Solved!
Go to Solution.

Programs of this type usually use a state machine of some sort. You can find many tutorials on LabVIEW state machines in these forums or the LAVA forums. If you are doing a rewrite, I would also recommend you consider LabVIEW classes. They help modularize your code and make the subparts more reuseable. You may end up with less to maintain, as a result.
<shamelessPlug>You may also want to consider TestStand. It was designed to run sequences of tests, so may make your life easier. It could also be gross overkill.</shamelessPlug>
Let us know if you run into issues with state machines or classes.
This account is no longer active. Contact ShadesOfGray for current posts and information.

Best Practice for Storing Spatial Data in Multiple Projections?

From what I've been able to determine MS SQL can't do reprojections is that correct? Assuming it is, the state of Washington requires that our GIS data be managed in Washington Stat Plane South
but for our web mapping sites need the data in Web Mercator. Is it OK then to have two geometry columns in a spatial enabled table, say a county table, one in WSPS and the other in WM?
I’m coming at this from a 30 year background in GIS using ESRI software.
Usually we would store the shape / geometry in one projection and project it to other on the fly when needed.
That way there is only one definitive source. I don’t see a way to do this in MS SQL.

Hi Scott.
Storing two columns of spatial data is fine in SQL Server. And you are correct that there is no built-in reprojection in SQL Server, most folks do that as part of data loading. There was talk of porting parts of ogr2ogr to SQLCLR, but I don't think anyone
did that.
Cheers, Bob

Best practices for referencing external video across multiple computers

I have made a .swf that references an external .f4v . The swf plays fine on my own computer, but does not play on a colleagues computer, or another computer which we tested. The file is not for upload to web , it is for local playback. I assume this is a file path issue, but I have tried many different things including specifying a path and then recreating the same directory structure on the other computer. What am I missing? The f4v file can playback on the colleagues computer (I did install ffdshow , although another tested mp4 also plays back fine) but not the .swf. Please , any help would be greatly appreciated!
Thank you!

This could be a security context issue, is it possible on your own machine you have allowed access to that file or folder containing the F4V file, maybe using the global-security-settings in flash player? Have a read of the following just in case:
http://www.adobe.com/products/flashplayer/articles/localcontent/

Best practice for test reports location -multiple installers

Hi,
What is recommended best practice for saving test reports with multiple installers of different applications:
For example, if I have 3 different teststand installers: Installer1, Installer2 and Installer3 and I want to save test reports of each installer at:
1. C:\Reports\Installer1\TestReportfilename
2. C:\Reports\Installer2\TestReportfilename
3. C:\Reports\Installer3\TestReportfilename
How could I do this programatically as to have all reports at the proper folder when teststand installers are deployed to a test PC?
Thanks,
Frank

There's no recommended best practice for what you're suggesting. The example here shows how to programmatically modify a report path. And, this Knowledge Base describes how you can change a report's filepath based on test results.
-Mike
Applications Engineer
National Instuments

JSR 168 best practice for saving inter-portlet state

The portlet specification doesn't yet cover inter-portlet communication. Until
it does, what is the best practice for saveing state so that multiple portlets
can use the same data?

The portlet session is layered on top of the HTTP session except for
attribute scoping. So, all portlets in a webapp share the same
HTTP/portlet session for a given client.
All APPLICATION_SCOPEd portlet session attributes are automatically
available to other portlets. With PORTLET_SCOPEd attributes, portlet
containers namespace attribute names, so it would be hard to get
attributes by name (but still possible).
Subbu
Chris Jennings said the following on 10/14/2003 09:17 AM:
If I set an attribute in a PortletSession, though, it isn't visible form another
PortletSession... right? Please tell me that's wrong ;-) If that's right, how
can I have portlet B get to something set by portlet A?
Subbu Allamaraju <[email protected]> wrote:
Chris,
For sharing transient state, the only possible mechanism in V1.0 is to
use sessions.
Subbu

Best practice for distributing/releasing J2EE applications.

Hi All,
We are developing a J2EE application and would like some information on the best
practices to be followed for distributing/releasing J2EE applications, in general.
In particular, the dilemma we have is centered around the generation of stub, skeleton
and additional classes for the application.
Most App. Servers can generate the required classes while deploying the EJBs in the
application i.e. at install time. While some ( BEA Weblogic and IBM Websphere are
two that we are aware of ) allow these classes to be generated before the installation
time and the .ear file containing the additional classes is the one that is uploaded.
For instance, say we have assembled the application "myapp.ear" . There are two ways
in which the classes can be generated. The first is using 'ejbc' ( assume we are
using BEA Weblogic ), which generates the stub, skeleton and additional classes for
the application and returns the file, say, "Deployable_myapp.ear" containing all
the necessary classes and files. This file is the one that is then installed. The
other option is to install the file "myapp.ear" and let the Weblogic App. server
itself, generate the required classes at the installation time.
If the first way, of 'pre-generating' the stubs is followed, does it require us to
separately generate the stubs for each versions of the App. Server that we support
? i.e. if we generate a deployable file having the required classes using the 'ejbc'
of Weblogic Ver5.1, can the same file be installed on Weblogic Ver6.1 or do we
have to generate a separate file?
If the second method, of 'install-time-generation' of stubs is used, what is the
nature/magnitude of the risk that we are taking in terms of the failure of the installation
Any links to useful resources as well as comments/suggestions will be appreciated.
TIA
Regards,
Aasif

Its much easier to distribute schema/data from an older version to a newer one than the other way around. Nearly all SQL Server deployment features supports database version upgrade, and these include the "Copy Database" wizard, BACKUP/RESTORE,
detach/attach, script generation, Microsoft Sync framework, and a few others.
EVEN if you just want to distribute schemas, you may want to distribute the entire database, and then truncate the tables to purge data.
Backing up and restoring your database is by far the most RELIABLE method of distributing it, but it may not be pratical in some cases because you'll need to generate a new backup every time a schema change occurs, but not if you already have an automated
backup/maintenance routine in your environment.
As an alternative, you can Copy Database functionality in SSMS, although it may present itself unstable in some situations, specially if you are distributing across multiple subnets and/or domains. It will also require you to purge data if/when applicable.
Another option is to detach your database, copy its files, and then attach them in both the source and destination instances. It will generate downtime for your detached databases, so there are better methods for distribution available.
And then there is the previously mentioned method of generating scripts for schema, and then using an INSERT statement or the import data wizard available in SSMS (which is very practical and implements a SSIS package internally that can be saved for repeated
executions). Works fine, not as practical as the other options, but is the best way for distributing databases when their version is being downgraded.
With all this said, there is no "best practice" for this. There are multiple features, each offering their own advantages and downfalls which allow them to align to different business requirements.

Best Practice for re-usable forms in multiple Countries

Similar Messages

Maybe you are looking for