Channel and Dist naming standards

I'd like to solicit any advice on naming standards for Channels and
Distributions. We are in our design phase and looking to put standards
in place that could easily scale to a larger entity if necessary.
Thank you,
Dave

On Thu, 26 Jan 2006 18:30:13 GMT, [email protected] wrote:
> I'd like to solicit any advice on naming standards for Channels and
> Distributions. We are in our design phase and looking to put standards
> in place that could easily scale to a larger entity if necessary.
very hard to do that in a short time.. for channels
1) figure out what you want to patch / install / do
2) figure out which kind of services you have you want to do 1) with
3) figure out which kind of hardware / os you are running 2) on
4) figure out which locations have different requirements to 1) to 3)
5) think about having an at least 2 phase approach, better 3 to rollout
distributions, 2 phase = testing and rollout, 3 phase = testing, initial
rollout, final rollout
for example...
some people would like to patch their webservers... so you create a
webserver channel... but perhaps not all of them have to same content... so
you create another channel for every content
some people would like to use ZDM application distribution so they create
an app channell... but than they figure out they would like to do
loadbalancing in a site so you need one channel for every site...
some people would like to patch their nw server... but it is not a good
idea to rollout the patch to all servers at the same time... so you create
a channel to test the patch, one channel to do a initial install on a
average of you server environment, and another one for the rest of the
servers..
and so on ;-)
best way is to really play around with the product first to find the
limitations to your ideas and after that good planning.
if you put 1 to 5 into the channelname the channels should scale very well
distribution naming is similar
Marcus Breiden
If you are asked to email me information please change -- to - in my e-mail
address.
The content of this mail is my private and personal opinion.
http://www.edu-magic.net

Similar Messages

  • Enforcing use of class word as naming standard via data modeler preferences

    Using data model preferences, I have set both the "attribute" and "column" naming standards to have mandatory name parts of both "prime word" and "class word". I have also used data model preferences to specify a glossary that has several terms of type "class word" defined.
    My assumption is that if I set a column naming standard preference to have class word as a mandatory name part, then I can apply the default design rules in my relational model and it will list an error "column with wrong naming standards" if any of my column names don't have a name part that is on the list of class words in the specified glossary. Is that assumption correct? If so, it doesn't seem to be working for me...
    How does SDDM determine if a class word is missing? I.e., how can I enforce a naming standard that all attribute/column names must have a class word from our approved list of class words?
    Thanks!

    My assumption is that if I set a column naming standard preference to have class word as a mandatory name part, then I can apply the default design rules in my relational model and it will list an error "column with wrong naming standards" if any of my column names don't have a >name part that is on the list of class words in the specified glossary. Is that assumption correct? yes it's correct.
    If so, it doesn't seem to be working for me...one of the settings cannot be changed - it's "Abbreviated only" in "Preferences>Data Modeler>Naming Standard". So only abbreviated part from glossary is taken into account - I logged bug for that.
    You can change it - it's in dl_settings.xml file in your design's directory - find - abbreviated_only="true".
    How does SDDM determine if a class word is missingIt needs glossary and separator setting.
    You can read more here http://www.oracle.com/technetwork/developer-tools/datamodeler/datamodelernamingstandards-167685.pdf
    Also can look at examples here Data Modeler: Naming
    Philip

  • Problem with Applying Naming Standards to Keys and Constraints

    Hi
    I have an issue, and not sure where to go. I have 3 relational models in 1 design. I set up my foreign key template. I applied it to the first relational model, and it worked like a charm. When I bring up the "Apply Naming Standards" window for the second model and click on OK, nothing happens. The window just stays there and the OK button turns gray. I checked the log, but no messages are written. I just have to click on cancel to close the window. Has anyone got any suggestions on what to do? I even went back in and changed a table name to make sure that a foreign key name should change, and still nothing happens.

    Hi Joep,
    thanks for design. I logged bug for that problem - some FK columns keep information about non existent foreign keys.
    Here is a transformation script you can run for relational model:
    columns = model.getColumnSet().toArray();
    for (var t = 0; t<columns.length;t++){
    column = columns[t];
    nodes = column.getRefColAndAssocIDs().toArray();
    for (var i = 0;i<nodes.length;i++){
       node = nodes;
    if(node.fkAssocId!=null){
    fk = column.getDesign().getDesignObject(node.fkAssocId);
    if(fk==null){
    column.removeFKAssociation(node.fkAssocId);
    column.setDirty(true);
    And of course you have to save design - it's better to use "save as".
    Philip                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Mixing and exporting for more than 8 channels and non-standard multichannel setups

    I am trying to do something kind of unconventional, although I have seen people on the forums trying to do similar things. Unfortunately, it's unclear if they succeeded or not, and if they did, how.
    I'm trying to figure out how to mix sound for an environment that has many (somewhere between 8 and 16) independent speakers, all connected to an audio interface. I know that WAV, AAC, and other audio file formats can carry that many channels and I can map them to the individual speakers. My question is how to edit/mix. Specifically,
    Is this possible in Audition? It seems like it might be in CC, but not previous? (I have CS6.)
    How do you set up the project file. When I create a new multitrack project, I can choose mono, stereo, or 5.1. The 5.1 option allows me to assign sounds to the five speakers in a standard 5.1 setup and the LFE. Is it possible mix for an environment with more than that? Or with a different configuration of speakers? In Audio MIDI Setup (for Windows people, that's where in OSX you set the more advanced audio preferences) I can configure up to 7.1 as well as geometric arrangements like quadrophonic, hexagonal, and octagonal. Is it possible in Audition to mix for anything like these?
    There have been some threads where people talk about using 16 discrete outputs in Audition. How is this possible? Is each track able to be routed to a different output? If so, is it possible to write a file that has all of these tracks assigned to their discrete output channels?
    Is it possible to nest audio sessions like you can nest Premiere sequences? For example, can I create a multitrack project with mono output and have that session be embedded into another multitrack session or do I have to finish editing the first one and write a file from it to use it in another project? Can buses be used to do this? What I'm wondering is if what I describe in #3 above IS possible, then how to have more than just a single pre-made audio file going to each of the outputs, to allow me to mix each channel with various sounds.
    Sorry that's a few questions, but they all revolve around how to work with multi-channel sound that isn't stereo or 5.1.
    Thanks!

    SpdCncpt wrote:
    I'm trying to figure out how to mix sound for an environment that has many (somewhere between 8 and 16) independent speakers, all connected to an audio interface. I know that WAV, AAC, and other audio file formats can carry that many channels and I can map them to the individual speakers. My question is how to edit/mix. Specifically,
    Is this possible in Audition? It seems like it might be in CC, but not previous? (I have CS6.)
    As you have probably gathered, this is effectively a work in progress...
    How do you set up the project file. When I create a new multitrack project, I can choose mono, stereo, or 5.1. The 5.1 option allows me to assign sounds to the five speakers in a standard 5.1 setup and the LFE. Is it possible mix for an environment with more than that? Or with a different configuration of speakers? In Audio MIDI Setup (for Windows people, that's where in OSX you set the more advanced audio preferences) I can configure up to 7.1 as well as geometric arrangements like quadrophonic, hexagonal, and octagonal. Is it possible in Audition to mix for anything like these?
    At present, this is restricted to what you can see, but there's sort-of a workaround - albeit not an ideal one...
    There have been some threads where people talk about using 16 discrete outputs in Audition. How is this possible? Is each track able to be routed to a different output? If so, is it possible to write a file that has all of these tracks assigned to their discrete output channels?
    If you have a multichannel sound device, and all the outputs are visible to Audition, then yes, each track can be assigned directly to a different output. And if you set one up, you can do this with buses as well...
    Is it possible to nest audio sessions like you can nest Premiere sequences? For example, can I create a multitrack project with mono output and have that session be embedded into another multitrack session or do I have to finish editing the first one and write a file from it to use it in another project? Can buses be used to do this? What I'm wondering is if what I describe in #3 above IS possible, then how to have more than just a single pre-made audio file going to each of the outputs, to allow me to mix each channel with various sounds.
    It's not possible to nest sessions at present in any version, and this has been asked about before. There are some significant issues with this, mainly to do with things like sample rates, output formats, etc. Doesn't mean that it won't happen, but don't hold your breath... As I said, there's a workaround, and yes, it's buses. Since you can effectively submix to a bus, and the bus output can go directly to hardware, then you can do what you want. The compromise is that in order to save the overall result, you'll end up with all of your source files, and a session file. And you'll have to play the whole thing back in Audition, rather than export it to a single file and be able to play it on a multichannel player. But yes, it should work.

  • Logical Model Naming Standard (Title Case) and Foward ENGINEERING how to???

    Hi,
    I just installed the datamodeler v3.3.0.747.
    I want to use the Title Case style as separator style in my logic Model... To do this, i go to the Preferences Settings (Tools > Preferences > Naming Starndard > Logic Model) and set the Title Case as separator Style...
    However, when i do foward engineering of the logical model... The Style is omitted and everything is like the logical model... For example,
    If i create an entity called: ManagedAccount, i will expected that when i do fwd enginnering, the table associated to that entity will be call as Managed_Account; However, i still getting ManagedAccount...
    So, What am i doing wrong??? or this is a bug???
    Thanks!

    Hi,
    in order to get it working in current release you need to create glossary even empty one and set its property "Incomplete Modifiers" to true (check the check box with that name), and to to add that glossary in "Tools>Preferences>Data Modeler>Naming Standard".
    We'll change it in next release to work without glossary for this particular case.
    Philip

  • Relation between Sales org , Dist Channel and Division

    Hello all ,
        I need to know where the relation between Sales Org. , dist channel and Div is stored in CRM . I need to create search help which will get Dist channel and Division for a particular sales orgnization .
        Helpful answers will be rewarded .
    Thanks ,
    Shounak M.

    Any Suggestions ?
    Thanks ,
    Shounak M.

  • Configure common dist channel and division

    hi
    how to configure common distribution channel and division
    regards
    hema

    Define Common Distribution Channels
    T.Code: VOR1
    The master data shared by several distribution channels applies to conditions and customer and material master data.
    This helps you minimize the cost of creating and maintaining the master data.
    You can also update statistics for each distribution channel and division without creating the master data for the different sub-areas of the organization.
    Define Common Divisions
    T.code: VOR2
    The common master data across various divisions refer to the conditions and the customer master data.
    You thus minimize the effort of entering and managing master data.
    In addition, you can extrapolate your own statistics per division without having to create master data in the different organizational subareas
    regards
    AK

  • How to know a users company, sales org, dist. channel and division...

    Hello Experts,
    Is there a way to know which company, sales org, distribution channel and most importantly division a
    user is currently affiliated? Really need help on this one guys since I am gonna use it for authorizations.
    Thank you guys and take care!

    Hi,
    If your informations are not in SU03 or XD03, so  I think you can't have these informations.
    (Maybe with column "Terminal name" in SM04 ?? If this information has been normed in your company)
    Regards,
    Stéphane.

  • Use of common distribution channel and division in CRM

    Hi,
    I have a requirement where the customer master will be created in a single dist channel and division combination in ECC and downloaded to CRM. However this customer will be used in different sales area combinations in CRM and ECC.
    In ECC there is as standard setting wherein we can refer a sales area to other sales area.
    Do we have any such functionality in CRM?
    I went through posts and even tried to run Transaction CRMD_DOWNLOAD_SB and CRMD_DOWNLOAD_OM but the tables were not populated in CRM.
    For information we are creating the org structure in CRM itself and not generating it from ECC.
    Regards,
    PP

    dear PP,
    first, you can have a look the relevant master data division and distr. channels settings in config
    here are the paths for CRM 7.0  system config (might be a bit different for previous versions):
    spro->customer relationship management->master data->organisational management->division settings
    spro->customer relationship management->master data->organisational management->organisational data for sales scenario
    and second, the Assignment of Organisational Units from SAP ECC (same CRM spro config):
    spro->customer relationship management->master data->organisational management->Assignment of Organisational Units from SAP ECC
    please do not forget to check out the Data transfer (just one node lower) : Copy SAP ECC Sales Structure
    t-code CRMC_R3_ORG_GENERATE
    good luck!
    regards,
    PPIO

  • How to set naming standards for SQL Developer

    I am using SQL Developer version 3.0.04.
    In the newly integrated and very useful Data Modeler, we can set preferences for the naming standards to be applied when creating logical and relational model objects ( primary keys, foreign keys, et cetera). I would like to know if there is a way to set naming standards for the relational objects we create in SQL Developer on existing tables ( ( primary keys, foreign keys, et cetera).
    Any help in setting such preferences would be appreciated.

    Hi,
    If you want to set up a diagram for an existing database, you can use File/Data Modeler/Import/Data Dictionary to import its definitions.
    Alternatively you can open a Data Modeler Browser (using View/Data Modeler/Browser), expand the node for Design "Untitled_1",
    expand the node for Relational Models, and select Show from the Right-click drop-down menu for "Relational_1" to create a Relational Model diagram.
    You can then drag Tables from SQL Developer's Connections tree onto the diagram.
    Once you have a Relational Model you can reverse engineer it to an Entity-Relationship model using the << button in the button bar
    (or by selecting "Engineer to Logical Model" from the drop-down menu for the Relational Model).
    Note that there is now a separate forum for SQL Developer Data Modeler topics: SQL Developer Data Modeler
    David

  • SAPScript: how tu adjust heigh and width of standard text (logo)?

    Hi!
    how to adjust heigh and width of standard text (logo)?
    I do not want to edit the logo, because it is used elsewhere, so I need to adjust heigh and width when using it in a form.
    For now stadard text comes over the window. Here is how I use it:
    INCLUDE ZHEX-LOGO OBJECT TEXT ID ST
    Will reward,
    Mindaugas

    Hi Mindaugas,
    While uploading using RSTXLDMC. You have to maintain your size of the logo.
    Go through below mentioned document.
    Upload TIFF files to SAPscript texts
    Description
    The report RSTXLDMC allows a TIFF graphics file to be uploaded from the file system of the R/3 GUI to a standard text in the R/3 word processor SAPscript. (TIFF is a registered trademark of the Aldus Corporation.)
    When uploading, the TIFF graphic is converted either into a black and white raster image (parameter type=BMON ) or as a color raster image with a maximum of 256 colors (parameter type=BCOL).
    The black and white raster images ( BMON) can be printed using the following printer types:
    PCL-5 printer
    PostScript printer
    Kyocera PRESCRIBE printer
    Device type SAPWIN (with SAPlpd 32-bit as of Version 2.41 for Windows NT or Windows 95)
    The color raster images (BCOL) can be printed using the following printer types:
    PCL-5 printer with color capability (e.g. HP Color LaserJet). Color graphics are not printed properly on monochrome PCL-5 printers (e.g. HP LaserJet 5), because the printer cannot set the color palette as required and does not perform any gray-level conversion.
    PostScript printer (color graphics are automatically converted to gray levels on black and white printers using PostScript) Device type SAPWIN (with SAPlpd 32-bit as of Version 2.41 for Windows NT or Windows 95) During TIFF graphic import, the basic set " Baseline TIFF 6.0 " of the TIFF specification 6.0 is supported.
    To maintain compatibility with earlier versions of the report RSTXLDMC, it is also possible to convert the TIFF graphic directly into a black and white raster image for a particular printer type when uploading. These are the three printer types PCL-5 (parameter type=PCL ), PostScript (parameter type=POST) and Kyocera PRESCRIBE (parameter type=PRES ). A raster image uploaded in this manner can only be printed using the appropriate printer type.
    Besides TIFF raster graphics, direct printer commands in the respective printer language (PCL-5, PostScript or Prescribe) can also be contained in the file which is to be uploaded (printer macros). They are then transferred to the standard text unmodified.
    The graphics are output by inserting the standard text into the document which is to be printed, directly or using an INCLUDE command. The printer commands, which for example draw a company logo on the page, are only output if the print request is processed by the printer driver corresponding to the macro type, otherwise they are ignored. Example: A macro of type PCL is contained in a print request. If the request is output to a printer with type HPLJIIID (to which the driver HPL2 is assigned), the macro data is sent to the printer. If the request is printed on a printer of type POSTSCPT (to which the driver POST is assigned), the output of the macro data is suppressed.
    In the standard text, the printer commands are inserted between the HEX ... ENDHEX command lines in hex notation. Various report parameters allow the graphic or printer macro to be placed on the page or at the current text position. Note: When the /:HEX command line which precedes the macro appears in the text, a line break is generally made before the graphic is output. The output of the macro therefore begins in the next text line at the left window border of the current page window, as long as a shift to the right is not specified (see below).
    If your own printer macros are uploaded and not TIFF files, you must ensure yourself that the normal (text) output of the driver is not impaired when the printer commands are inserted in the output from the uploaded file. The printer drivers pass the data contained in the file to the printer unmodified, therefore without control over the individual actions this triggers on the printer. For example, syntax errors should not be generated by the PostScript commands (type POST), or form feeds should not be contained in the file (unless this was intended) for PCL-5 (type PCL).
    Restrictions:
    In general, the output of graphics generated via RSTXLDMC from R/3 is not suitable for mass printing (that is, unless you are using the "Graphic resident on printer" feature): the R/3 spooler has to hold significantly more data in its output files. If the graphics occur several times in a spool request, the data also reoccurs. Apart from this, the network is more heavily loaded in sending the increased volume of data to the printer and the printer output is slowed significantly (varies according to printer model) if raster graphics are output as well as the text.
    If your graphics reside on your printer during a printing job, the degree of 'correctness' with which they are printed depends on the amount of memory available in your printer. R/3 print drivers are unable to determine whether the amount of memory available is enough! If one of the graphics that you have marked as resident is not displayed, try reloading the graphic and switching off the parameter "Graphic resident on printer".
    When printing black and white graphics on PCL-5 printers, image data is compressed in order to greatly reduce the file size.
    The output of graphics and macros on PCL-5 printers, PostScript printers and device type SAPWIN (type BMON, BCOL, PCL, POST) is adapted to the page orientation used, that is if landscape is used instead of portrait, the graphic is also turned when output. This is not the case for the PRESCRIBE printers (type BMON, PRES)! With these printers, the graphic is not automatically turned when landscape is used, but appears on the page in the identical position as for portrait. You are therefore recommended not to output raster images when printing in landscape on PRESCRIBE printers.
    PRESCRIBE printers do not support the resolutions 200 and 600 dots per inch when printing raster images.
    Not all PCL-5 compatible printers support the resolutions 200 and 600 dots per inch when printing raster images.
    TIFF graphics with compression type 2 ("CCITT Group 3 1-Dimensional Modified Huffman run length encoding ") can currently not be imported although this is a component of the Baseline TIFF 6.0 specification for monochrome images.
    Color TIFF graphics with full color representation (ie. a lot more than 256 colors) are automatically converted into 256 gray levels when uploading with type BCOL.
    When TIFF graphics are converted to black and white raster images (type BMON, PCL, POST, PRES) there is no default simulation of gray levels or colors of the original image on the printer (for example, by using different tones of gray). Each pixel of the original image is converted to a white or black pixel on the printer according to its intensity value.
    The parameter "Number of TIFF gray levels" does, however, allow a simulation of gray/colour tones of the original image through levels of gray on the printer, when using type PCL, POST or PRES. This parameter is ignored for type BMON.
    The conversion of TIFF graphics can be so time-consuming that it is recommendable to execute the report RSTXLDMC in batch processing. Note: in batch, the file is always read from the file system of the application server (ie. not from the file system of the GUI).
    The length of an individual text in the text file is limited. When importing TIFF graphics with very large dimensions, especially if more than 2 gray levels are used, a termination can therefore occur when saving the standard text ("EXPORT_TOO_MUCH_DATA"). This restriction can only be avoided by reducing the TIFF graphics. Note: The display of a raster image in Postscript or PRESCRIBE format needs from two to three times as much space as displaying in PCL-5.
    When processing very large TIFF images on PostScript printers, a print termination can occur with PS error message "limitcheck". In this case the internal memory of the printer is insufficient to scale the required raster image. This implementation limit cannot be influenced by changing the report parameters when importing.
    Requirement
    The file which is to be uploaded can contain the following formats/ commands:
    Baseline TIFF 6.0 raster image files. The image information of the TIFF file is converted into black and white/color raster images when uploading. Note: As the TIFF format allows a variety of variants, only a basic set of TIFF 6.0 formats is supported here described in the TIFF 6.0 specification as Baseline TIFF 6.0.
    PCL : PCL-5, Hewlett Packard Printer Control Language 5 for HP LaserJet 3, 4, 5 series and compatible printers. The data is output by the printer driver HPL2 only.
    PRES: Kyocera PRESCRIBE for Kyocera laser printers. The data is output by the printer driver PRES only.
    POST: Adobe PostScript or EPS format (encapsulated PostScript ) for PostScript printers. The data is output by the printer driver POST only. In the upload, one of the end-of-file markers (CTRL-D, hex $04) which may be contained in the PostScript file is not transferred.
    For PostScript files which contain a bounding box entry (for example, all EPS files) the macro/graphic can be scaled to a size specified by the user. In this case, a small lead text and trailer are generated by the report for the macro data and inserted in the standard text.
    Parameters of RSTXLDMC
    File name
    Path and file name of the file to be uploaded in the file system of the R/3 frontend (dialog processing) or in the file system of the application server (batch processing)
    Type
    Way which the data contained in the file is to be converted. Possible values are BMON, BCOL, PCL, POST and PRES. With parameter values BMON and BCOL, a TIFF 6.0 file is expected. This is converted into either a black and white raster image (BMON) or a color raster image (BCOL). These raster images are printer-independent and can be printed using various printer types (see above).
    With parameter values PCL, POST and PRES, either a TIFF 6.0 file or a file with printer commands in the appropriate printer langauge is expected. If the file is a TIFF file, it is converted into a black and white raster image for the printer type specified in the parameter. The presence of a TIFF file is recognized automatically. If the file is not a TIFF file, the file contents are regarded as the printer macro of the respective type. Data loaded with type PCL, POST or PRES can only be printed on the respective printer type.
    Resolution for TIFF raster images
    Resolution which should be used when importing a TIFF raster image, in dots per inch (dpi). If an allowed value is entered here, this overrides the resolution information in the TIFF file. The allowed values are:
    75 dpi
    100 dpi
    150 dpi
    200 dpi (not for type PRES, for PCL only HP LaserJet 4,5 series)
    300 dpi
    600 dpi (not for type PRES, for PCL only HP LaserJet 4,5 series)
    Changing the resolution affects the size of the graphic on the printer. If a resolution of 300 dpi is stated in the TIFF file and this parameter is set to 75 dpi, the graphic is four times as big when printed as at the outset.
    Note: Kyocera PRESCRIBE printers do not support 200 and 600 dpi resolutions.
    Note: Not all PCL-5 printers support resolutions 200 and 600 dpi, for example HP LaserJet 3 series does not, but LaserJet 4 and 5 series do.
    Graphic Resident on Printer
    Normally, graphics that occur more than once in a printing job (a company logo that appears on each page, for example) are sent to the printer repeatedly each time they are needed. In order to avoid this kind of redundancy, you can select this checkbox on the selection screen. The R/3 print driver then stores the graphic in the printer's memory and the printer retrieves the 'resident' graphic memory every time that re-occurs in your job.
    Caution: Whether or not the printer correctly reproduces the graphic depends on the amount of memory available in the printer during the printing job! You should avoid using this feature with color graphics since they take up a lot more memory than monochrome graphics.
    This parameter can only be used with types "BMON" and "BCOL".
    Absolute positioning
    Determines whether the macro/graphic is positioned absolutely or is to be output at the current text position. If this checkbox is selected, the graphic is positioned absolutely (parameters "X-position" and "Y-position" are used), if this checkbox is not selected, the graphic is positioned at the current text position (parameters "Reserved height" and "Shift to right" are used)
    Absolute X-position
    Horizontal position (space from left border) of the macro/graphic, if absolute positioning is required. This is the parameter XPOS of the HEX command.
    Absolute Y-position
    Vertical position (space from upper border) of the macro/graphic, if absolute positioning is required. This is the parameter YPOS of the HEX command.
    Reserve height automatically
    If this checkbox is selected, the system automatically inserts the actual height of the graphic during printing into the subsequent "Reserved height" parameter.
    Reserved height
    If positioned at the current text position, this parameter specifies the horizontal spacing to be reserved for the macro/graphic, which must not be printed with text from the paragraph. This is the parameter HEIGHT of the HEX command.
    Shift to right
    If positioned at the current text position, this parameter specifies the space between the left border of the macro/graphic and the left border of the page window. If this value is increased, the macro/graphic is shifted to the right. This is the parameter LEFT of the HEX command.
    Unit of measurement for positioning
    The unit of measurement in which the position values (X,Y, height, shift) are specified. Possible values are CM (centimeters), MM (millimeters), IN (inches), PT (typographic point = 1/72 inch), TW (1/20 point = 1/1440 inch)
    Text title
    Comment used for the attribute "Title" of the standard text generated as well as as a comment line in the text itself
    Line width
    Number of columns to be used in the standard text when generating the HEX...ENDHEX command lines. The default value is 132
    Text name
    Name of the standard text to be generated. If an * character occurs in the name, it is replaced by the value of the parameter "Printer type". For example, if the entry is ZHEX-IMAGE1-* and the printer type = PCL, the text name ZHEX-IMAGE1-PCL is generated. The default value for the name is ZHEX-MACRO-<printer type>, but the standard text can be named as required (take into account customer reserve). Standard texts are client-dependent!
    Note: The name of a standard text can be up to 32 characters long !
    Text ID
    ID of the standard text to be generated. The default value is ST (general standard texts)
    Text language
    Language key of the standard text to be generated. The default value is the logon language
    PostScript scaling
    Flag which determines how the macros/graphics of type POST are handled. If set to 'X', the report expects a PostScript comment line in the file
    %%BoundingBox llx lly urx ury (e.g. %%BoundingBox -1.5 0 21.4 14.1)
    as present, for example, in all EPS files, in which the dimensions and the position of the macro/graphic are specified (if a bounding box comment is not included, 0 0 1 1 is assumed as the default value). This information is then used by the report to insert PostScript commands which scale the macro/graphic to the size specified in the parameters "Width" and "Height" (listed below).
    If the flag is set to ' ' (blank), the PostScript file is transferred to the standard text without any additions (any transformations to the coordinate system used by the printer driver must already be contained in the file).
    The flag must be set to 'X' for the import of TIFF files for type POST.
    Width according to PS scaling
    Required width of the macro/graphic if the flag PostScript scaling is set. Can remain at zero for the import of TIFF files, the size is then determined by the resolution of the graphic.
    Height according to PS scaling
    Required height of the macro/graphic if the flag PostScript scaling is set. Can remain at zero for the import of TIFF files, the size is then determined by the resolution of the graphic.
    If you want to scale the PostScript graphic with these parameters, one of the two values, width or height, can be specified with zero. The graphic is then scaled so that the width-to-height ratio remains unchanged and the original graphic is not distorted.
    Unit of measurement for PS scaling
    Unit of measurement in which the parameters "Width" and "Height" are specified. Possible values are CM (centimeters), MM (millimeters), IN (inches), PT (typographic point = 1/72 inch), TW (1/20 point = 1/1440 inch)
    Number of TIFF gray levels
    Number of gray tones which are to be used on the printer for displaying the original image. Note: This parameter is only evaluated when using types PCL, POST or PRES!
    Possible values are 2,4,9. With the default value 2, each pixel of the original image is converted either to a white or a black pixel on the printer. With the value 4, each pixel of the original image is converted on the printer with 4 pixels, which simulate 4 different gray levels. With the value 9, each pixel of the original image is converted on the printer with 9 pixels which simulate 9 different gray levels.
    Note: With values 4 or 9 the resolution of the image is doubled or tripled. The restrictions on the possible resolutions (see previous parameter) then apply for the resulting resolution.
    Output
    Individual steps of the upload procedure are logged in the report list generated and, if necessary, errors reported. The uploading of TIFF graphics, in particular, is cancelled if there is a variant which is not supported. A message to this effect is then issued. If execution is successful, the report generates a standard text with the key specified in the parameters. If the standard text already exists, a window appears with a warning before the text is overwritten.
    Regards,
    Ameer Baba.

  • Naming Standards: What are you using?

    I'd like to hear what different organizations are using for naming standards to manage their XI environment.
    When you have a new interface or need to call up an existing interface, how do you know where to find them?  
    Do you break out your interfaces by Sender SC, XI SC and receiver SC?
    How do you organize namespaces?

    Hi Mark,
        Well, The name space itself it means that it used for unique identifier.Normally in realtime business cases lot  of process would be involved..when you are developing the interface and when you start up with namespace..The name space should give you the what exactly the scenario..for which type of scenarios..
      Let me take an example suppose if u are implementing the all sales order scenario you can probably implement a name space such that it should reflect the all sales order related objects.
      <b>Ex: http://xyzcompany.com./salesorders</b>
      The above namespace tell you that the vendor is xyzcompany and the corresponding objects of slaes orders.
    Hope I am clear.
    Thanks and Regards,
    Chandu.

  • Datamodeler - Naming Standards - technical white paper no longer available?

    Hi,
    I am wondering, is this document no longer available?
    http://www.oracle.com/technology/products/database/datamodeler/pdf/DataModelerNamingStandards.pdf
    I a m trying to learn how to apply Naming standards in data modeler but i cannot retrieve this document.
    On the datamodeler homepage, on tab "Documentation"
    clicking "Naming Standards (Technical White paper - pdf)"
    keeps me redirecting into the tab "Overview"
    regards,
    E.
    As I look at the content description of this document(i found that content description somewhere on the www), i believe i would find it very helpfull
    Contents of this Oracle SQL Developer Data Modeler Naming Standardization reference guide
    Introduction ............ 1
    Overview . 2
    Defining Templates for Keys, Indexes and Constraints....... 3
    Applying the Templates to the Relational Model ............. 5
    Prefix Management ........... 6
    Setting Name Patterns for Elements..... 7
    Defining Word Classification Types .. 8
    Supporting Naming Patterns with SQL Developer Data Modeler ... 8
    Reviewing Separator Settings for Elements in a Logical Model ..... 9
    Reviewing Additional Settings for Elements in a Relational Model . 9
    Using a Glossary .. 10
    Defining Glossaries ......... 10
    Using the Glossary Editor 10
    Importing Glossaries........ 12
    Importing a CA Erwin Data Modeler Naming Standard Glossary . 13
    Using Abbreviations............. 13
    Using the Name Abbreviations Utility............. 14
    Name Translation . 16
    Setting Model Level Name Restrictions ............. 18
    Using Design Rules Validation Related to Naming Standards ......... 19
    Conclusion ........... 20
    Resources ............ 20

    it's temporary problem and document will be available soon.
    Meanwhile you can look at this thread Data Modeler: Naming
    Philip

  • DataModeler v3.3.0 - Naming standards template for surrogate keys creation

    I'm using DM 3.3.0.734 and in the logical model we now can define in the entity properties to "Create Surrogate Key".
    When we use Engineer to relational model, for each entity is automatically created a new column using the naming template {entity}_ID as NUMERIC (without precision) and is defined as primary key.
    My questions are:
    Is possible to define a different naming standard for surrogate key creation?. We define id_{entiry}
    Is possible to set the precision of NUMERIC surrogate key?
    If we define entity's column as Primary UID, these columns are included in an unique constraint, but are using the naming standards for PK.
    As consequence are created the following:
    Unique constraint name: entity_PK
    Primary key(surrogate)name: entity_PKv1
    There is any way to define naming standards like "{entity}_UID" for unique constraints, or even, "{entity}_SK" for surrogate primary key name?
    Can anyone help with some of these topics?
    Regards,
    Ariel.

    Hi Ariel,
    Naming standards template for surrogate keys creation I logged enhancement request for that.
    How to change those bad names (going to change them one by one is not an option):
    1) If those "transformed" unique keys are the only ones you have in relational model then simply can apply naming standards
    2) You can write transformation script to do that for you
    3) you can use new functionality - search, export to excel file, change the names there (using find/replace will be faster) and return changed data back to relational model
    you can find description for that here:
    https://apex.oracle.com/pls/apex/f?p=44785:24:13179871410726::NO:24:P24_CONTENT_ID,P24_PREV_PAGE:6621,16
    http://www.thatjeffsmith.com/archive/2012/11/sql-developer-data-modeler-v3-3-early-adopter-search/
    http://www.thatjeffsmith.com/archive/2012/11/sql-developer-data-modeler-v3-3-early-adopter-collaborative-design-via-excel/
    You should search for _PK, then filter result on Index and you can export result using report functionality (to XLS or XLSX output format). You can create template and include only table and name (of index) as properties to be included into report.
    Regards,
    Philip

  • Sql Developer Data Modeler 3.0 EA1: Preference- Naming standard- Templates

    I am trying to figure out how the naming standard templates work.
    When I go to:
    Preference -> Naming standard -> Templates
    It says that 'Attribute Relation' is '{ref entity} {ref attribute}'
    What is the consequence of this?
    I thought, it would mean that when creating a primary key attribute (ID) on an entity (DEPARTMENT), the related "foreign key" attribute (that is automatically created in related detail entities, such as EMPLOYEES) would be named DEPARTMENT ID.
    Instead it is just called ID. Is that the intended behavior?
    - Marc de Oliveira
    Edited by: marc66 on 2010-10-29 05:59

    Marc,
    you should check "FK Attribute name synchronization" setting in "Preferences>Data Modeler>Model>Logical model" - probably it's checked and you cannot change the name of FK attribute.
    I found another bug here - FK attribute doesn't follow changes in referred entity - I logged it in bug database. As workaround you can apply defined templates at entity level (there is button in entity dialog) or for whole logical model (using pop-up menu in the browser).
    Philip

Maybe you are looking for