VC models...BeX naming conventions

Hello,
I have a problem in VC...with naming conventions.
The base Bex queries were not followed Naming Conventions and the VC models were completely designed based on the queries.
Now the management had decided to move the content only with naming conventions...from Bex we can do the query as Save As in a simple way. What about VC? Can we do it similar...i dont think so. Can someone help me with the best solution how to solve this issue.
what i did: I took the copy of VC model and added new datasource (Bex new query followed naming convention). Then i try to drag the input and output links to the new datasource i cant able to do that, is there a best way? my other question is if i change the links from old datasource to new datasource then all the fields and values for the rest of the model are blanked (not copied from the previous model). How to best solve this issue? Please advice...and consider this as high priority.
Note: If there is no solution to my question, how could SAP develop the tools with out thinking these constraints during the Product development. I feel like strange...please respond.
Thanks,
Pandu
Edited by: pandu on Jun 15, 2010 12:29 PM

Hi
I have a doubt regarding your requirement.
If you are creating new Bi queries, (with Save As) so what your are going to do with existing queries? If not, you can continue with same VC model, you just need to change model name as per convention.
Also for the second point you mentioned, VC is just for arranging the layout of the dashboard & the layout will remain same even if you delete exisitng queries & add new queries. Also the Data service (BI Query in this case) is a foundation of VC model & all other things like Input/ Output Form/Table are with reference to data service. So if you are deleting data service obviously all values will get reset. There are few constraints in VC but i dont think this is a constraint.
If possible, follow the naming convention in discripption of query for earlier queries which will not lead to duplication of efforts for earlier queries & Vc models. & You can start following naming convention for new queries.
Regards
Sandeep

Similar Messages

Data Modeler - Naming Conventions

I was using Oracle Designer for several year.
This product could drive you crazy because sometimes, but the strength was in my opinion the datamodelling part.
It saved you a lot of time because you kept stuck to the logical model generated your relational model and had all scripts satisfying all naming conventions you needed.
In Data Modeler i really miss the naming conventions and can't understand some parts, sometimes somebody here can help me if i have overseen something or it is just not implemented.
Naming conventions as example:
We work with surrogate keys.
Two well known tables - Employees (abbreviation EMP), Departments (abbreviation DEP)
They have one relation 1:N one department has many employees
In Designer i would define the EMPLOYEE entity, would set the table-abbreviation, the attributes and the primary key.
The same with DEPARTMENT. I would design it WITHOUT any column for the foreign key constraint.
Then i would create a relation between this two tables.
Last step is to generate the relational model.
a) Designer automatically adds ID as surrogate key on every table (you could configure that, it was dependent on a domain)
b) it automatically adds the table abbreviation as prefix on every column (even here it's configurable)
c) it automatically adds the a foreign key column in the child table with the prefix of the master table (f.e. EMP_DEP_ID or DEP_ID if you prefer not to prefix every column... what i do)
It was really easy to get your scripts.
Things i don't understand in Data Modeler:
In a logical model you should design entities, attributes and relations and don't mess around with FK-columns.
Is there any support for surrogate keys? I don't wanna add an ID manually with every table.
In Data Modeler an additional COLUMN(!) is added with every Foreign key relation, i could live with that, but there is no way to tell
Data Modeler to prefix it automatically. The name can just be changed in the Relational View afterward.
P.S.
Surrogate Keys.... There are some pros and cons for/against this out there. I have seen a lot of Oracle Projects and in all except one i always had a surrogate key column. It really makes life
easier. In the one no-surrogate-key-project we began to add surrogate keys after a while...

COLUMN(!) is added with every Foreign key relation, i could live with that, but there is no way to tell
Data Modeler to prefix it automaticallyLook at "General options>Naming Standard>templates" - you can define template for FK columns/attributes and then apply them for whole relational/logical model using "Apply Naming .." functionality from pop-up menu in the browser. For Logical model (FK attributes) - you also need to clear related setting at "General options>Logical>Keep as the name of originating attribute".
Templates are also used when objects are created, thus when new FK is created, then templates are used to generate name for foreign key and FK columns. Well you have to define table and column abbreviation in order to get them used in generated names - Re: Data Modeler: Naming
There is no support for surrogate keys in current release.
Philip

Transport with CTS+ : Naming convention

Hi SDNers,
I need your suggestion.
This is wrt CTS+.
My doubt is:
I need to transport changes between the Dev, QA & Production system.
I have a repository in Development system: Repo_Dev
Now I want to create a repository in Quality / Production system, similar to Repo_Dev , but with different Repository names as Repo_QS / Repo_Prod respectively. My doubt is, will I be able to create the repositories in the Quality or Production systems with the name I want.... or is it because I am using CTS.. it will create a repository with the same name i.e Repo_Dev.
With reference to the SAP document "Setup und Use the MDM Change Transport with CTS+ Transport Management Environment", my understading is to
1. Create a repository in QS / Production side.
2. Using the option "Create Transport Reference" , I will get a reference file of Repo_Dev.
3. Then Import the reference file in the Repo_QS / Repo_Prod will result in synchronisation between all 3 (Repo_Dev, Repo_QS, Repo_Prod ) repositories.
This way I can have the same Data modelling etc in all the 3 repositories, with the naming convention as required.
If anyone has worked on it... please confirm it.
Thanks & Regards,
Priti Rani Patnaik

Hi Priti,
For transport with CTS+ you need to follow the steps which you have mentioned. You need to create a repository and then import the ref. in this repository. By doing so you are only importing the tables and fields present in your Dev repository. The sync between all three is only related to data modelling and it will not effect the name of reposiotry as you have already created a repository and I guess renaming of repository is not possible.
I hope I am able to help you.
Thanks & Regards
Dilmit Chadha

BPC Standard Naming Convention

Hi Gurus,
Could you please share BPC naming conventions standards?
I am looking for prefix for objects such as:
Environment
Model
Dimension
Team
Task Profile
Data Access Profile
Member Formulas
Logic Script
Business Rule
Controls
Input Screen
Report
Data Manager Package
Data Manager Package Link
Transformation File
Conversion File
Process Chain
Thanks.

As far as I know there are no naming conventions other than no special characters or spaces. NW is case sensitive, so you need to be careful there. In terms of prefixes, I'm not sure what you mean. Some of the technical objects in NW are in the CPMB namespace but you are not adding that namespace to anything
Here are some comments:
Environment - the description in the BPC admin client can, the technical name on the backend will be generated
Model - same as environment
Dimension - same as environment
Member Formulas - this is driven by member IDs
Input Screen - not sure what this is
Data Manager Package
Process Chain - the out of the box PCs are all in the CPMB namespace, the new ones just need to be copied in there but they wouldn't be created in BPC rather in BW
Hope this make sense,
Akos

Naming Conventions for Workflow

Hello,
does anybody have a document for Naming Conventions for Workflow.
I found nothing the last hour.
Thanks in advance for any help ...
Stefanie

Hi,
I am sending you naming convention which we followed in our project.
Workflow Template & Standard Task:
SAP/R3 Limitations:
Workflow Template & Standard Task names are limited to 12 bytes.
Standard:
Bytes 1-3 of the Workflow Template & Standard Task (see following table) are intended to give an overview of general information regarding the Workflow Template & Standard Task.
Characters 4-12 of the name should be chosen to impart some idea of the Workflow Template & Standard Tasku2019s use and/or contents. (The portion of the Workflow Template & Standard Task name that forms the unique identifier may, or may not, contain underscores characters to enhance Workflow Template & Standard Task name readability.)
Position Description Sample Values Sample Meanings
1 Table system life Z/Y Permanent/Temporary
2 Application Type * See Application Designators (Appendix B)
3 OPCO/Region * See OpCo Initial Chart (Appendix A)
4-12 Unique identifier text Unique identifier; may include underscores
Example: ZS7_IDEL9 (I:-Inbound, DEL: - OILDEL 9:- Original)
Business Object:
SAP/R3 Limitations:
Business Object names are limited to 10 bytes.
Standard:
Bytes 1-3 of the Business Object (see following table) are intended to give an overview of general information regarding the Business Object.
Characters 4-12 of the name should be chosen to impart some idea of the Business Objectu2019s use and/or contents. (The portion of the Business Object name that forms the unique identifier may, or may not, contain underscores characters to enhance Business Object name readability.)
Position Description Sample Values Sample Meanings
1 Table system life Z
Y Permanent
Temporary
2 Application Type * See Application Designators (Appendix B)
3 OPCO/Region * See OpCo Initial Chart (Appendix A)
4-12 Unique identifier text Unique identifier; may include underscores
Example: ZS7_OILDEL (Business Object for OILDEL Message Type)
Methods
Method names should begin with a verb:
Examples: GET_STATUS, CREATE_ORDER, DETERMINE_PRICE
For Parameters:
IMPORTING parameters IM_<parameter name>
EXPORTING parameters EX_<parameter name>
CHANGING parameters CH_<parameter name>
RESULT RE_<result>
Events
Event names should have the form
<noun>_<participle>:
Examples: BUTTON_PUSHED, COMPANY_CODE_CHANGED, BUSINESS_PARTNER_PRINTED
Note: There is no specific naming convention for Container Variables in workflow & for Key Fields & Attributes in Business Object. These variables name should be chosen to impart some idea of the variablesu2019 use and/or contents.
Appendix A
ABAP Programming Standards: OpCo/Region Initial Chart
Old # Company Name Proposed # Accounting Location
98 Common A San Ramon
95 FSC B San Ramon
80 Chevron Chemical Company C San Ramon
89 Chevron USA-Downstream & General D Walnut Creek
75 Chevron Real Estate Management E San Francisco
76 Chevron Information Technology Company F San Ramon
77 Gulf Oil Great Britain G London
85 Corporation (Acct. by Corp.) H San Francisco
83 Chevron International Oil company J San Ramon
87 Chevron U. K. Limited K England
86 Corporation (Acct. - Local Office) L Various
96 P&M Coal & Mining Company M Denver
94 Corporation (New York) N New York
90 Chevron Pipeline Company P San Ramon
79 Chevron Canada Resources, Ltd. R Calgary
92 Chevron Shipping Company S San Francisco
81 Chevron Petroleum & Tech Co. T Houston
91 Chevron USA Upstream U Concord
78 Chevron Canada, Ltd. V Vancouver
93 CUSA Warren Petroleum W Tulsa
84 Chevron Overseas Petroleum, Inc. X San Ramon
88 Chevron Research & Tech. Company Y Richmond
- Corp. GLX Common validations Z San Ramon
- PCA 3 San Ramon
- Tax 4 San Ramon
- Audit 5 San Ramon
- Asia-Pacific 6 Global
- Africa 7 Global
- Latin America 8 Global
Appendix B
ABAP Programming Standards: Application Designators
A Assets Accounting
C PPC
D DASS (control station)
E RIVA/IS-Oil
F Financial Accounting (incl. Joint Venture)
G General Ledger
H Human Resources Planning
I Plant Maintenance
J Publishing
K Cost Accounting
L Inventory Management
M Materials Management
N Hospital
O unassigned
P Human Resources
Q QSS (Quality assurance)
R PRA (Prod & Revenue Acctg)
S Basis
T Projects
U Enterprise Data Model
V Sales
W MMS (Merchandise mgt. System)
X unassigned
Y Customer head office
Z Customer branch
<inappropriate content removed by moderator>
Thanks
Yogesh Sharma
Edited by: Mike Pokraka on Jul 2, 2008 10:34 AM

Naming Convention - Best Practices

Hi,
Do you'll have a recommendation for naming convention/standards in BPC. I am referring to naming convention for objects like Dimensions, Models, Task Profiles, Data Access Profiles, Rules, Process Flows and so on...
Thanks in advance for your support
Thanks.

Hi Jon,
Usually no. Quite often we try to create names as much familiar to user as we can. Since like: dimensions the ID is what is shown in the reports, and despite have a description, you can't use this description as the main mask for that dimension. So the ID should be a "semantic" name, something the user identify what it is. Models, Rules and Process Flows is the same.
The exception is regarding security. I.e. data access profiles depends on the client you can create some sort of standards. Such as: The security is made by entity and cost center, so my DAP is:
- EEEE_CCCCCCC_T
Where: E = Entity ID
C = Cost Centre ID
T = Type: R - Read, W - Write and D - Denied.
But it's all very generic. The only thing I reckon important is to keep coherence while creating objects.
Cheers.
Lucas

Project Naming Conventions?

Would anyone care to share the naming conventions they use for projects? I have a manageable number now so naming doesn't matter so much, but I can see having a large number of projects soon. Thanks!

Kenneth Kirksey wrote:
Would anyone care to share the naming conventions they use for projects? I have a manageable number now so naming doesn't matter so much, but I can see having a large number of projects soon.
hi, ken
do you have clients?
my folder/project naming conventions...
main subject with projects below
for example,
Beach (main subject)
Jetty (sub subject)
Nature (main subject)
Birds (sub)
Birds of Prey (sub sub)
Fashion (main sub)
Model Name (sub)
Calvin Klein (sub sub)
(MGM Grand) (sub sub)
Music (main)
Artist Name (sub)
name of Project currently working on (sub for artist)
I hide photos in yellow folders to keep other clients from viewing photos from others
sometimes 2008 Beach to keep the year separated
victor

Storage Location Naming Convention without WM!

Dear all
We are facing serious problem in our Storage Location for Raw Material.
We have 4 types of Raw Material Seating (S), Panel (P), Metal (M), Wood (W). And they are all stored under Storage Location: RWSL.
Requirement:
Although we have visual guideline as to which industrial rack will store the type of Material, it is insufficient. We need a more refined storage location down to which BIN of the rack we will put the Raw Material.
Due to limited time and resource, we cannot have WM implemented right now. Thus, we have come out with 2 alternative to overcome this problem:
Alternative 01:
We will use the Fixed Bin field in Storage Data 02 by putting the Bin number assigned to each Rack.
E.g. For Seating material code:SEAT01, we will maintain the Fixed Bin as R12A01/A02, it means this Seating material SEAT01 will be stored at Rack 12, fixed bin A01 or A02.
Question to Alternative 01: Will it cause problem in GR, GR, Transfer Posting and Stock Count?
Alternative 02:
Instead of going into details to put Fixed Bin field in Storage Data 2, we will abandan the existing Storage Location RMSL by introducing new format for Storage Location
Here is the example of Alternative 02:
For raw materials, we will use 4 digits location numbers, consistent with other Storage locations, the 4 digits storage location will start with u201CR _ _ _u201D to represent each location
And,
R _ _ _ is:
R = Raw materials
2nd digit = Division (S= Seating, P =Panel, W=Wood, M=Metal and W=Wood)
3rd digit = Rack Number (A, B, C, Du2026 and etc.)
4th digit = Rack Zone - each rack will broken down into zone, each rack can possibility have 2 to 3 zone. 1 Zone can be 1 colume of the Rack
An example of a possible location and its meaning will be
RSA1 = Raw materials warehouse, Seating division, Rack A, Zone 1
RPB3 = Raw materials warehouse, Panel Division, Rack B, Zone 3
The challenge of this is that instead of having 1 Raw Material Storage Location like RMSL, we will have a lot more storage locations each for division of Raw material due to the Rack Number we have as well as the Rack Zone.
Question to Alternative 02:
If we use this alternative, will it impact our future implementation of WM? From design wise, is it feasible?
Please advise what is the best approach and the feasible design on it.
Many thanks in advance.
Edited by: Daimos on May 13, 2009 10:15 AM

Hi, here is the Pro and Co of both approaches:
Method 01: Use existing SLOC and add the Storage Bin info
e.g. SLOC: STM1
         Storage Bin: RSC3, where RS = Rack Seating, C3 = column 3
Pro 01:
It will cause less effort as we only need to use LSMW for material master to add in the Storage Bin data for all material of SCM.
Pro 02:
I have tested out that in TCode MIGO, apart from SLOC, the pertaining Storage Bin data also appear. Based on my discuss with Xian Chen, sometimes they use MB1C(GR), MB1A(GI) rather than MIGO due to speed issue, I will need to check the field status if can have Storage Bin field APPEAR, if can, it will solve the problem
Con 01:
The Storage Bin information will only appear in MMBE (Stock Overview) but will not appear in the standard SAP Inventory Report (e.g. MB52 Warehouse Stock). To view it from SAP Inventory Report, we may need to customize the standard report to show the new field Storage Bin. It needs Abap effort.
Con 02:
We must have a very good naming convention for Storage Bin. And again, in the above example, if a material is put in SLOC STM1 at Storage Bin RA A1 or C4, it will set a very rigid rule in the future if we need to change it, as I fear that one the Storage Bin has been used up. It will not allow us to change (need to do testing to find out)
Con 03:
Do we have the time to define all the Storage Bin for each SLOC? Operation wise, the store personnel needs to design it
Method 02: Use the new SLOC
Pro 01:
RSA1 = Raw materials warehouse, Seating division, Rack A, Zone 1. More organized. Easy to tell the material is at which Rack and which Zone of the Rack.
Assumption:
01. we must not have too many rack for one Seating division and also not too many Zone for each
      Division, else it will cause confusion
02. 1 material should stick to 1 Rack 1 zone as much as possible, else later the PP consultant will
     have hard to to perform GI due to too many SLOC assigned to a material.
Pro 02:
In report wise, we are able to show the SLOC in inventory report. No need to enhance the existing inventory report as we do not use Storage Bin.
Con 01:
If there are too many SLOC creation due to it. It may cause problem for PP perform GI as too many selection available for a material. This can be avoided if stick to the General Rule that one material is tied with one SLOC.
Edited by: Daimos on May 16, 2009 5:07 AM

File name naming convention in File Adapter configuration in ID

Hi All ,
I have a query related to xml filename created in IDOC-XI-FILE scenario based on value of one of IDOC field .
The scenario is like this :
I have to send one xml file per store for material master . In this case how can I define my file name with store name in File adapter configuration in ID .
Naming convention should be
<storename>_date_masterdataname.xmlwhere store name is one of field of IDOC .
Plz help me .
Thanks in Advance
Regards
Prabhat Ranjan

Hi Prabhat,
take a look at this weblog:
/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii
you have to specify variable substitution
(in the file adapter)
and give the path to the store name (in the variable sustitution table)
you file name schema (from the file communication channel can look like this)
%storename%_date_masterdataname.xml
Regards,
michal
Message was edited by: Michal Krawczyk

Is it possible to control the naming convention used by Aperture when importing photos? If so, how

When I import photos from my camera, I have them placed into projects based on the date the photos were taken. However, I do not like the naming convention used by Aperture as it causes the projects to sort into a non-chronologial order. The convention is MMM-DD-YYYY and I want to change it to YYYY-MM-DD. Is it possible in Aperture 3.2.4 to do this?

In the Import panel you can edit the preset for the file name format to "Image year - image month - image day - index" for example; the preset for folder names seems to be gone in Aperture 3,3 - at least I cannot find it any longer. You only seem to be able to enter the folder name manually in the Import panel.

Best practice for naming convention in BI 7.0

Hi All,
Is there a Best Parctice document for naming convention in BI 7.0?
Thanks,
S.B

hi,
chk this links...
http://help.sap.com/saphelp_nw04/helpdata/en/ba/83343ea7ff6a38e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/da/0318025d64a84b94542641ed77ee74/frameset.htm
hope this helps,
partha

Looking for best practice on naming conventions

Does anyone out there have a best practice on naming conventions that they could share.
I'm starting to find the need to create objects and associated variables and actions.
I can see this getting very messy, very quickly and would love to learn if someone has come up with a good set of guidelines that are both easy to follow and make perfect sense. (I know....what a balance to ask for!)
Thanks
Alan

Hi Alan,
Welcome to Adobe Community.
There are couple of things that you can keep in mind while naming objects.
When creating custom text caption styles, be sure to follow the correct naming conventions. Each caption style has a unique name, and you must
use this name at the beginning of each associated bitmap filename. For example, if you create a text caption style named “Brightblue,” the five
bitmap images that constitute the new style should be named as follows:
Brightblue1.bmp, an image with no callouts
Brightblue2.bmp, an image with a callout to the right or upper-right
Brightblue3.bmp, an image with a callout to the left or upper-left
Brightblue4.bmp, an image with a callout to the lower right
Brightblue5.bmp, an image with a callout to the lower left
Flash button-naming conventions
Each SWF button contains three layers: a button, an icon, and an action layer.
The SWF filename consists of the following elements:
Acronym for playback control (“pbc”)
Playback element identifier (“Btn” for button, “Bar” for bar, and so on)
Name of the button (“play”).
Hope this helps!
Thanks!

Inconsistent naming conventions for Adobe Reader in software scan

I just want to see if anyone knows why Adobe's free pdf Reader appears both as "Adobe Reader" AND "Adobe Acrobat Reader". I manage software licenses for an organization of 400+, and it's difficult to know if, for instance Adobe Acrobat - Reader 6.0.2 Update - 6.0.2, should or should not be counted as a purchased license without actually visiting each workstation to verify. I've spoken with our network operations personnel and they confirmed that it is not manually entered by our personnel, but that it is something in the software. ??
Furthermore, why are the naming conventions not consistent even among those that can be identified easily? The list below is what I see when I run a report for all Adobe software on our network.
Adobe Acrobat - Reader 6.0.2 Update - 6.0.2
Adobe Acrobat 4.0 - 4.0
Adobe Acrobat 5 -- SC Install
Adobe Acrobat 5.0
Adobe Acrobat 5.0 - 5.0
Adobe Acrobat 5.0 - 5.1
Adobe Acrobat 5.0 SC Support
Adobe Acrobat 6.0 Professional - 006.000.000
Adobe Acrobat 6.0 Standard - 006.000.000
Adobe Acrobat 6.0.1 Professional - 006.000.001
Adobe Acrobat 6.0.1 Standard - 006.000.001
Adobe Acrobat 7.0 Professional - 7.0.0
Adobe Acrobat 7.0.1 and Reader 7.0.1 Update - 7.0.2
Adobe Acrobat 7.0.2 and Reader 7.0.2 Update - 7.0.3
Adobe Acrobat 7.0.3 and Reader 7.0.3 Update - 7.0.4
Adobe Acrobat 7.0.5 Professional - 7.0.5
Adobe Acrobat 7.0.7 Professional - 7.0.7
Adobe Acrobat 7.0.8 Professional - 7.0.8
Adobe Acrobat and Reader 6.0.3 Update - 6.0.3
Adobe Acrobat and Reader 6.0.4 Update - 6.0.4
Adobe Acrobat and Reader 6.0.5 Update - 6.0.5
Adobe Acrobat Reader 3.01
Adobe Acrobat Reader for Pocket PC 1.0
Adobe Reader 6.0 - 6.0
Adobe Reader 6.0.1 - 006.000.001
Adobe Reader 7.0 - 7.0.0
Adobe Reader 7.0.5 - 7.0.5
Adobe Reader 7.0.5 Language Support - 7.0.5
Adobe Reader 7.0.7 - 7.0.7
Adobe Reader 7.0.8 - 7.0.8
Adobe Reader Chinese Simplified Fonts - 1.0
Adobe Reader Japanese Fonts - 1.0
Adobe Reader Korean Fonts - 1.0
If anyone can answer this, I'd appreciate it. Thanks.

Junlie et al,
Starting with Acrobat 9 (announced on 6/2/08), Adobe will support the new ISO/IEC 19770-2 standard for universal software tagging. The new standard will allow customers to correctly identify the name, version, type and licensing status of Adobe software (starting with the Acrobat 9 family and later on as new versions of the products are introduced later this and next year).
I DO understand your frustration with the in consistencies in the naming of our software, but the problem of software discovery goes well beyond our lack of discipline. This is one of the many reasons why Adobe invested time and effort with the industry group defining the new open standard, and in software asset management in general.
More information about tagging standard can be found here: http://www.agnitioadvisors.com/info/content/view/44/1/
- Juan-Carlos

.tpz files naming convention / export from PI 7.0

Hi,
When I export the repository or Directory content from PI 7.0 the naming convention PI gives its own naming convention. Starting wit XI3_0 * .tpz
Why does it start with XI3_0*.tpz for we have PI 7.0?
Do we need to change any Visual admin or exchange profile parameter to get the naming convention to PI7_0*.tpz
Thanks
Sachin

Hi,
The import and export functionality of XI 7.0 uses the expression 'XI 3.0' instead of 'XI 7.0' in all transport screens of the Integration Builder. Furthermore the name of XI 7.0 exports will always start with the prefix 'XI_3_0' and not 'XI_7_0'.
Reason and Prerequisites
The reason for this behaviour is that the transport code and format of XI 7.0 and XI 3.0 is identical.
Solution
There is no fix for the naming convention, but there is a positive consequence: XI 3.0 export files can be produced by XI 3.0 and XI 7.0 and can be imported into XI 3.0 and XI 7.0.
Refrence Note
Note 936254 - XI 3.0 Imports and Export in XI 7.0
Award points if helpful.
Thanks,
Tanuj

AppleScript To Save Messages As PDFs With Specific Naming Convention

I am looking for an Applescript that:
1: Prompts and allows the user to select one or more Apple Mail email messages from within Mail (10.4, 10.5, 10.6).
2: Prompts and allows the user to select a save-to folder.
3: For each message, saves it as a PDF file in the save-to folder, using the following naming convention for the PDF file:
"YYYY-MM-DD HH.MM.SS Email From FIRSTNAME LASTNAME - SUBJECT",
"YYYY-MM-DD HH.MM.SS Email To FIRSTNAME LASTNAME - SUBJECT",
where in the email date-sent stamp (if I am the sender) or date-received stamp (if I am the recipient):
YYYY = the year
MM = the two-digit month
DD = the two-digit day
HH = the two-digit hour (in 24-hour time)
MM = the two-digit minute
SS = the two-digit second
FIRSTNAME is the email sender's first name for email that I receive (or is the email recipient's first name for email that I send)
LASTNAME is the email sender's last name for email that I receive (or is the email recipient's first name for email that I send)
SUBJECT = the email's subject line
For example: 2010-04-10 16.32.48 Email From Kris Ryan - Status Of Payroll Updates.pdf
For example: 2010-04-10 16.33.55 Email To Sue Anderson - RE Status Of Payroll Updates.pdf (Colon omitted after "RE".)
4: For each attachment to the message, saves it as a PDF file in the same directory using the naming convention:
"YYYY-MM-DD HH.MM.SS Email From FIRSTNAME LASTNAME Z Attachment - NUMBER - FILENAME",
where:
YYYY-MM-DD HH.MM.SS Email From FIRSTNAME LASTNAME = as above
NUMBER = an integer representing the attachment number (1, 2, ...) sorted according to filename alphabetical order
FILENAME = the name of the file attached to the email, including its extension (.docx, .xlsx, etc.)
The letter "Z" sorts the attachment PDFs after its respective parent email in the directory.
For example: 2010-04-10 16.32.48 Email From Kris Ryan Z Attachment - 1 - List Of Suggestions To Moore.doc.pdf
For example: 2010-04-10 16.32.48 Email From Kris Ryan Z Attachment - 2 - Proposed Salary Adjustments.xls.pdf
For example: 2010-04-10 16.32.48 Email From Kris Ryan Z Attachment - 3 - Salary History.pps.pdf
Note: The email attachment may consist of a PDF or MS Office file (Word, Excel, Power Point); however, a smart implementation will be able to handle any attachment kind. If the attachment is a PDF file, then save it "as is" using the stipulated naming convention, without passing it through Distiller.
Thank you.
Kurt Todoroff

Well, that's quite a spec sheet.
Here's a start, you can easily edit the script to get what you need:
<pre style="
font-family: Monaco, 'Courier New', Courier, monospace;
font-size: 10px;
font-weight: normal;
margin: 0px;
padding: 5px;
border: 1px solid #000000;
width: 720px; height: 340px;
color: #000000;
background-color: #E6E6EE;
overflow: auto;"
title="this text can be pasted into the AppleScript Editor">
Set a Mail Rule to Save Message and Attachment to Desktop.
To save attachments to another another folder on the desktop (i.e. Attachments) create the folder and then
change tell application "Finder" to set pathToAttachments to (path to desktop folder as string) & "Attachments:"
using terms from application "Mail"
on perform mail action with messages theMessages
tell application "Finder" to set ptd to (path to desktop folder) as string
tell application "Finder" to set pathToAttachments to (path to desktop folder) as string
tell application "Mail"
repeat with theMessage in theMessages
set d_recd to date received of theMessage as string
set d_recd to ReplaceText(d_recd, ":", " ") of me
set d_recd to ReplaceText(d_recd, ",", " ") of me
set theText to content of theMessage
if theMessage's mail attachments is not {} then
repeat with theAttachment in theMessage's mail attachments
set theFileName to pathToAttachments & (theMessage's subject) & " (Attachment From " & (theMessage's sender) & " Sent " & d_recd & ")" & space & theAttachment's name
try
save theAttachment in theFileName
on error errnum
end try
end repeat
end if
set theFile to ptd & (theMessage's subject) & " (From " & (theMessage's sender) & " Sent " & d_recd & ")" & ".txt"
set theFileID to open for access file theFile with write permission
write theText to theFileID
close access theFileID
end repeat
end tell
end perform mail action with messages
end using terms from
on ReplaceText(theString, fString, rString)
set current_Delimiters to text item delimiters of AppleScript
set AppleScript's text item delimiters to fString
set sList to every text item of theString
set AppleScript's text item delimiters to rString
set newString to sList as string
set AppleScript's text item delimiters to current_Delimiters
return newString
end ReplaceText</pre>

VC models...BeX naming conventions

Similar Messages

Maybe you are looking for