MS Excel Tab Naming Convention Issue

Issue Description :
Summary excel file was confirming the source of workbook before opening the file.(Message : Excel found untraceable content in - Lex-1(Lex-Total) Summary report. Do you want to recover contents of
workbook? If you trust the source of this workbook, Click Yes.).Where 'Lex-1(Lex-Total) Summary report' is the tab name
Fix :Remove the Brackets from the tab name.
Can you please help us with the root cause of the issue ?  One of our assumptions is that the Excel sheet if created in the machine with English OS & opened in a machine with Japanese OS could be the
root cause of the issue

Hi,
This is the forum for Developing Apps for Office 2013, for your question is more about Excel culture, I will suggest you post your thread in Japanese TechNet for Excel forum.
Japanest TechNet
https://social.technet.microsoft.com/Forums/ja-jp/home
Best Regards
Lan
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Similar Messages

Naming convention of calculated keyfigure

Hi Experts,
This is the first time we are creating any calculated keyfigure in our system and while creating we are getting authorization error. When we contacted our basis friends they told that its a naming convention issue. I want to know what would be the naming convention of a calculated key figure in our system. Can you please help me how to find this naming convention?
Thanks in advance for your help.
Regards,
Brahma Reddy

"You do not have authorization to add or create".
This message purely indicates it is authorization issue. Work with your Basis guys to get the required access.
May be some of the roles are not assigned to your user id. or
In which system you are making changes, if it is prodcution try not to make any changes and make changes in dev system and move to production system.
Hope this helps.
Regards,
Reddy

PSA Table Naming convention

Hi Experts,
Currently I am working on the BW3.5 version. I would like to delete the old PSA req through Process Chain. I need some clarification. Please provide me your suggestions.
I have collected full list of PSA Table in Development system through excel, then i can filter out by source system.
While create the Process Chain for the PSA deletion, i want to add the collected PSA tables(Object Name).
Please refer the screen shot. But i noticed that "differing in naming convention for PSA from Dev to quality & prod!!".
So if i transport this Process chain to quality & production, this will not work same as in Dev.
I have already referred the form and found the thread that discuss about the same issue. But resolution not given.
Please help me to get it this issue resolved. Thanks in advance.
Similar issue thread:
psa
Screen shot:
http://img818.imageshack.us/img818/3963/psa1.jpg
Thanks,
RR

To explain this I will take the systems with this naming Convension.
Dev BW: BWD
Dev ECC: E01
Quality BW: BWQ
Quality ECC: Q01
When we take the conversion in the quality system you should have the below parameters.
BWD to BWQ
E01 to Q01
Q01 to Q01
FLAT File to FLAT FILE.
So lets say the source system related object is goign from D to Q lets say transfer rule, the same will be converted to Quality system based on the conversions maintained in this table: RSLOGSYSMAP.
So the source system related objects will gets converted to the target system objects using the refernce maintained in this place.
Hope this is clear for you now.
Thanks
Murali

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

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>

Regarding file naming convention(while publishing a file to FTP)

Hi,
In one of our usecases, we need to configure the file name based on the client’s requirement.(to place the file in FTP. But the file name should be customized by us.) We referred to the link given below.
http://www.b2bgurus.com/2008/04/customizing-file-naming-convention-in.html
Can you please briefly explain about where should we setup the 'macro' so that we can change the file name(which will be placed in FTP) as we like.
Thanks,
Shanmuga S.
Edited by: user655473 on 16 Oct, 2008 11:42 AM

Hi,
     As you said we had applied the patch(number 7233222).In the Transport parameter, we entered the values for 'filename format' as given in the link,
     http://www.b2bgurus.com/2008/04/customizing-file-naming-convention-in.html.
     But we couldn't put the file in FTP.
     Our usecase is to send file(with customized name) to FTP.
     Before applying the patch, this scenario works fine and we could put the file into FTP. In this case the default file name is '%FROM_PARTY%_%TIMESTAMP%.dat'.
     After applying the patch (number 7233222), we got the entry 'filename format' in 'Transport parameter'. There the default value is given as '%FROM_PARTY%_%TIMESTAMP%.dat'. But in this flow(after applying patch) we couldn't put the file in FTP. No error logs were seen in b2b.log file.
     In 'b2b_dc_transport.log' file, we were getting the following logs,
     "2008.10.17 at 19:47:16:273: Thread-20: (DEBUG) FTPAgent.login(): Enter
     2008.10.17 at 19:47:16:273: Thread-20: (DEBUG) Host name is 'PC022350.cts.com'.
     2008.10.17 at 19:47:16:289: Thread-20: (DEBUG) Host PC022350.cts.com FTP command: USER sss
     2008.10.17 at 19:47:16:289: Thread-20: (DEBUG) FTP Command: USER, reply:
     331 Password required for sss
     2008.10.17 at 19:47:16:289: Thread-20: (DEBUG) Host PC022350.cts.com FTP command: PASS
     2008.10.17 at 19:47:16:289: Thread-20: (DEBUG) FTP Command: PASS, reply:
     230 Logged on
     2008.10.17 at 19:47:16:289: Thread-20: (DEBUG) FTPAgent.login(): Exit
     2008.10.17 at 19:47:16:289: Thread-20: (DEBUG) Host PC022350.cts.com FTP command: PASV
     2008.10.17 at 19:47:16:289: Thread-20: (DEBUG) FTP Command: PASV, reply:
     227 Entering Passive Mode (10,232,65,97,7,197)
     2008.10.17 at 19:47:16:289: Thread-20: (DEBUG) Passive: ip = 10.232.65.97, port = 1989
     2008.10.17 at 19:47:16:289: Thread-20: (STATUS) Connecting to PC022350.cts.com:1989
     2008.10.17 at 19:47:16:289: Thread-20: (DEBUG) Host PC022350.cts.com FTP command: NLST /FTP/Acme
     2008.10.17 at 19:47:16:289: Thread-20: (DEBUG) FTP Command: NLST, reply:
     150 Connection accepted
     2008.10.17 at 19:47:16:304: Thread-20: (ERROR) FTPClient.listNames(): LIST REPLY: 226
     2008.10.17 at 19:47:16:304: Thread-20: (DEBUG) Disconnecting from PC022350.cts.com
     2008.10.17 at 19:47:16:304: Thread-20: (DEBUG) Host PC022350.cts.com disconnected."
     Please help us in resolving this issue.
Thanks,
Shanmuga S.
Edited by: ShanmugaS on 17 Oct, 2008 7:51 PM
Edited by: ShanmugaS on 17 Oct, 2008 7:52 PM

Hard to find ripping naming conventions

?In Mediasource Player 3.3, I had a really hard time finding the naming convention settingsdialog. It is in the media folder format settings option. I ended up with a bunch of ripped tracksthat had the track name twice and couldn't find the option. Hopefully this thread will help someoneso they don't have to struggle as much as I did. In the Settings pop-up the PC Music Library tab,and the Properties button under the first item which is the name of your current PC Music libraryname. I had failed to change the last box on the bottom right from track name to none. Ta paj692

I guess the argument against your argument is that your code should be as self-documenting as possible. In your code, I'll see "Event". Great. java.awt.Event? No (annoyance #1 already). Your base Event? I wouldn't know, need to check the imports first. Aaahh, scrolled up and saw: your special implementation Event it was. Although, I will not see that if I'm not familiar with your package structure and you're doing package imports.
Create packages for functional groups, otherwise you'll end up with loads of unnecessary public declarations because your helper classes are splattered all over the place and can't just rely on in-package visibility.
And by the way, using polymorphism properly like you don't seem to do, you'll screw yourself, because you'll in future have to do things like:
Event ev = new com.mystuff.special.implementation.Event();Because you can't import both the interface/superclass and the implementation. Congratulations.

ADF BC naming convention suggestions

Ok, I havent found too many topics on this matter, but here is a list of naming conventions our team is debating over. I would also like to hear the rest of the community's thoughts.
Entity: Use underlying table's name and postfix with Eo. If the table is a W view, it should prefix with W.
eg. EmployeeEo, WEmployeeEo
View Object (Single entity based): Use the Entity's name postfix with Vo.
eg. EmployeeVo, WEmployeeVo
View Object (Multiple entity based): Use the primary entity's name followed by a "busniess task" name.
eg. DepartmentEmployeeSearchVo (employee search being the task).
View Object (Non-entity based): Use the primary query table name followed by a "busniess task" name.
eg.EmployeeCountVo
View Link & Association: Combine the master entity name and child entity name postfix with Vl/Ao.
eg. DepartmentEmployeeVl, DepartmentEmployeeAo
(The issue with this is our legacy tables are not that intuitivly named, so its hard to distinguish the master/child tables. I was thinking of splitting it with lets say 2, like Department2EmployeeVl)
Application Module: Apply a "busniess process" name and suffix with AppModule.
eg. AcmeAccountingAppModule.
If anyone has any suggestions or see any conventions left out please post them.
Thanks,
Z

Without discounting your object name conventions, don't forget the Java package they are placed in helps gives context for the object. This is what I tend to do:
com.acme.appmodules
com.acme.entities (all entities)
com.acme.entities.associations
com.acme.views (common VOs)
com.acme.views.links (common VO links)
com.acme.views.reference (common read only VO lookups)
com.acme.views.<business task> (to group logical business VOs together)
com.acme.views.<business task>.links
...the last 2 are repeated for each business task area (eg. HR, accounts, etc)
My ideas partially based on the SRDemo from the JDev team.
Hope this helps.
CM.

Question about Best Practices - Redwood Landscape/Object Naming Conventions

Having reviewed documentation and posts, I find that there is not that much information available in regards to best practices for the Redwood Scheduler in a SAP environment. We are running the free version.
1) The job scheduling for SAP reference book (SAP Press) recommends multiple Redwood installations and using export/import to move jobs and other redwood objects from say DEV->QAS->PROD. Presentations from the help.sap.com Web Site show the Redwood Scheduler linked to Solution Manager and handling job submissions for DEV-QAS-PROD. Point and Shoot (just be careful where you aim!) functionality is described as an advantage for the product. There is a SAP note (#895253) on making Redwood highly available. I am open to comments inputs and suggestions on this issue based on SAP client experiences.
2) Related to 1), I have not seen much documentation on Redwood object naming conventions. I am interested in hearing how SAP clients have dealt with Redwood object naming (i.e. applications, job streams, scripts, events, locks). To date, I have seen in a presentation where customer objects are named starting with Z_. I like to include the object type in the name (e.g. EVT - Event, CHN - Job Chain, SCR - Script, LCK - Lock) keeping in mind the character length limitation of 30 characters. I also have an associated issue with Event naming given that we have 4 environments (DEV, QA, Staging, PROD). Assuming that we are not about to have one installation per environment, then we need to include the environment in the event name. The downside here is that we lose transportability for the job stream. We need to modify the job chain to wait for a different event name when running in a different environment. Comments?

Hi Paul,
As suggested in book u2018job scheduling for SAP from SAPu2019 press it is better to have multiple instances of Cronacle version (at least 2 u2013 one for development & quality and other separate one for production. This will have no confusion).
Regarding transporting / replicating of the object definitions - it is really easy to import and export the objects like Events, Job Chain, Script, Locks etc. Also it is very easy and less time consuming to create a fresh in each system. Only complicated job chains creation can be time consuming.
In normal cases the testing for background jobs mostly happens only in SAP quality instance and then the final scheduling in production. So it is very much possible to just export the verified script / job chain form Cronacle quality instance and import the same in Cronacle production instance (use of Cronacle shell is really recommended for fast processing)
Regarding OSS note 895253 u2013 yes it is highly recommended to keep your central repository, processing server and licencing information on highly available clustered environment. This is very much required as Redwood Cronacle acts as central job scheduler in your SAP landscape (with OEM version).
As you have confirmed, you are using OEM and hence you have only one process server.
Regarding the conventions for names, it is recommended to create a centrally accessible naming convention document and then follow it. For example in my company we are using the naming convention for the jobs as Z_AAU_MM_ZCHGSTA2_AU01_LSV where A is for APAC region, AU is for Australia (country), MM is for Materials management and then ZCHGSTA2_AU01_LSV is the free text as provided by batch job requester.
For other Redwood Cronacle specific objects also you can derive naming conventions based on SAP instances like if you want all the related scripts / job chains to be stored in one application, its name can be APPL_<logical name of the instance>.
So in a nutshell, it is highly recommend
Also the integration of SAP solution manager with redwood is to receive monitoring and alerting data and to pass the Redwood Cronacle information to SAP SOL MAN to create single point of control. You can find information on the purpose of XAL and XMW interfaces in Cronacle help (F1).
Hope this answers your queries. Please write if you need some more information / help in this regard.
Best regards,
Vithal

Naming Convention for path in Application Server

Hello Guru's,
I asked my basis team to create flat file source system. he asked me " what path to follow, any sub directories"?.
they are asking me naming convention for a path in App server to create i think ? usually what will be the naming convention for path.
please help me
Thanks,
Prashanth

Hi,
Create flatfile source system is no need path and sub directory on app server. You can create yourself go TCODE RSA1>Source system>file-->create.
path and sub directory only need if you want to load data from flatfile which is stored in application server. This will be determined in extraction tab of your datasource and infopackage.
Hope this helps.
BR
TRUC

Private vs. protected, naming conventions etc.

I've been grappling with a couple of frustrations with Forte, and I'm
interested in feedback from others on this list regarding approaches
they may have adopted to address these.
One is that in the Forte workshops there is no way to view only the
public methods and attributes of a class (we're still using V2 here; I'm
assuming that V3 has not changed this). While referring to appropriate
technical documentation for a class is obviously important, I still find
myself opening up classes in the workshops to inspect the methods and
attributes available. (What I really want to see is an integrated class
browser. I sure hope Forte is working on something like this, or will
open up their development environment to support third-party extensions.
But that's an aside.)
A convention I just recently adopted in my work is to name private
methods and attributes with a beginning underscore ("_"). That way the
private elements are sorted to the top of the list and can be easily
differentiated from public elements. I'm curious, though, whether others
have adopted similar or different approaches.
I've also felt a bit frustrated over the lack of support for protected
attributes/methods for TOOL classes. This strikes me as a rather
bothersome shortcoming. The only approach I can think of is to make such
elements public, but adopt the same or similar naming conventions as a
strong hint to developers to avoid using these in clients of these
classes. Again, I'd be very interested in hearing how others have dealt
with this issue.
Thanks.
Michael Brennan
Programmer/Analyst
Amgen Inc.

I sent this once before, but the list seemed to be having trouble late last
week. If you get two copies of it... my apologies.
OK, I couldn't resist joining the fray...
At 10:56 AM 11/6/97 -0800, Michael Brennan wrote:
>
A convention I just recently adopted in my work is to name private
methods and attributes with a beginning underscore ("_"). That way the
private elements are sorted to the top of the list and can be easily
differentiated from public elements. I'm curious, though, whether others
have adopted similar or different approaches.You might even designate a single character before the underscore to denote
that, just in case some environment (CORBA) doesn't like the "_". You could
make it something like "Q" or "Z" or something that wouldn't normally be
used alone at the start of a name.
>
I've also felt a bit frustrated over the lack of support for protected
attributes/methods for TOOL classes. This strikes me as a rather
bothersome shortcoming. The only approach I can think of is to make such
elements public, but adopt the same or similar naming conventions as a
strong hint to developers to avoid using these in clients of these
classes. I share your desire for protected methods, but I have to disagree about
protected attributes. Philosophically speaking, protected and public
attributes are EVIL!! (I say "philosophically speaking" because, in the
Forte environment, there are some valid reasons for using them based upon
the visibility constraints of the language. In other languages, C++ and
Java, for example, it's not even philosophically speaking - they're just
evil!!)
One of the principal reasons for adopting the object paradigm is to
tightly control the impact of change - to provide good boundaries of
encapsulation that change does not ripple beyond. If you think about it,
one of the measures of the success of a superclass is the number of
subclasses that it has (especially for a good dabstract interface). This
says you have very nicely captured the semantics of the application domain
in the interface of the superclass. So, let's imagine a superclass with
protected attributes that are used by each of its 100 subclasses (probably
more than you would have, but I'm illustrating my point - incidentally, I'm
not talking about a hierarchy 100 deep; I'm talking about 100 subclasses
that are all direct decendants of the superclass). Now you go and change
one of the attributes. You must go look at all 100 subclasses to determine
the impact of change. This is exactly the kind of thing the object paradigm
was designed to eliminate.
Protected methods, on the other hand, would be nice.
And At 12:06 PM 11/6/97 -0800, Mark S. Potts wrote:
>
Forte inherits in a strange way when attributes are private. A
superclass attribute that is made private is not accessible from any of
its subclasses - this means that many of what you would consider private
attributes in fact have to be public. Well, the definition of private means "not visible outside of the class
where it is defined". I find it useful to think of the level of visibility
the same as secrets. There are things that are not really secrets at all -
it's ok if anyone knows them ("My name is Stephen"). These are public.
Then, there are things that it's ok if my family knows, but I don't want
the world to know - familial secrets, if you will ("I belch at the dinner
table when I'm at home"). These are visible to descendant classes and we
call them protected. Finally, there are things we don't want anyone else
to know, no matter who they are ("I poisoned my mother-in-law"). These are
private. We don't want anyone outside of ourselves to know these things.
These are the classic definitions of public, protected and private (perhaps
classic only because C++ defined them that way and everyone else just
copied what it meant).
Private attributes are not meant to be inherited by their subclasses.
That's why they're private. And, yes, I would argue that that is completely
correct. What you want, if you want them to be visible to subclasses, is
"protected". Now, Forte doesn't support protected, but that's a different
arguement - perhaps even an enhancement request.
We also should not confuse what we need to do in a language/environment
with what good OO principles are. For example, good OO design principles
state that you do not have public or protected attributes. Period! You
access them via accessors and mutators defined on the appropriate class.
Now, in some environments, this will not give you the performance you need,
so you open things up a bit. But, you shouldn't convince yourself that
doing this is the ideal design, just that it was necessary for performance.
The real problem here is that the performance of accessor and mutator
functions is not fast enough. That's why we open it up. Not because it is
good design. The proper way to fix the problem is to make accessors and
mutators fast enough so that they can be used (C++, for example, does this
with "inline" - not that C++ is my favorite language, it's not. But they
have fixed this one area nicely.)
Some would argue that this is correct and that inheritance does break thepure rules
of encapsulation I don't think inheritance, properly handled (and Forte does properly
handle it) breaks any rules of encapsulation. I would argure that the way
they treat private attributes is quite correct.
- but these people dont build applications!Hmmm... let's see... started building OO applications in 1985 (and building
them ever since) in complex application domains like CAD/CAM/CAE, Air
Traffic Control, Graphics/Imaging, Telecommunications, e-commerce,
entertainment,... ...wrote (and teach) the Forte OO Analysis and Design
course.
I guess you're right. I don't build applications. I build robust,
maintainable, extendable applications. ( ;-) ...nudge, nudge!)
Stephen

Sdl_image vs. xf86-input-mouse naming convention

This is really a minor issue, but I just wanted to point out that, people, we should pick either underscores or hyphens. Because mixing them just gets confusing. I realize it can be really hard to make all package naming completely perfect, because of the whole problem where you have to kind of name a package after the application contained therein. But you know, it's just a thought.
I'm switching to Hyphen Linux: "We Have Our Package Naming Conventions Totally Under Control."
Oh, and I'll say it first: "Yawn..."

The reason for this: it's following upstream stuff. xf86-input-mouse is named this way upstream, sdl_image is also named this way upstream.

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

When using Creative Cloud Library assets created in Illustrator why are the naming conventions I use not being pulled over into the Photoshop layers?

I create the Creative Cloud Library asset in illustrator and give it a name such as "camera-icon". It shows up in my Creative Cloud Library pane in Photoshop as "camera-icon". When I use that asset in Photoshop the layer is randomly named "a56bd81d-d81f-4815-82b3-5795d410b527". Why is this happening? Shouldn't that layer resolve the name back to "camera-icon" so that when I extract files for use in my application the naming convention is correct. Right now I have to manually rename that layer again. Is this a bug or have I just not done something correctly?

I think you have pasted the entire crash log. In case of such issues in future, please paste the error screenshot.
Seems to be a permission issue. Lets follow the below suggestions:
Solution 1: Rename the following folders on your machine:
'/Library/ColorSync/Profiles/Profiles'
'/Library/ColorSync/Profiles/Recommended'
Solution 2: Rename the following files:
'/Library/Application Support/Adobe/caps/Media_db.db'
'/Library/Application Support/Adobe/caps/pdb.db'
Make sure you dont touch caps.db under the same folder. Now run the installer again. Let me know if you need more help.
Solution 3:
Please Run following commands on terminal on the machine (this will remove the corrupt fonts and should allow you to run the installer successfully) -
sudo mv "/Library/Fonts/ACaslonPro-Bold.otf" /tmp/
sudo mv "/Library/Application Support/Adobe/SavedFonts/current/AdobeArabic-Bold.otf" /tmp/
sudo mv "/Library/Application Support/Adobe/HelpCfg/de_DE/goURL_lr_photoshop_de.csv" /tmp/
Please feel free to respond to this thread if you have any questions about the steps listed within the document. If you could also respond with the specific error message you receive, It would be appreciated.

Naming Convention and way to locate Table Names in B.I

Hello All,
I like to know information about
How to find a table
Naming convention of table
Important Tables
I will be thankful ,if anyone provide this information..

Hi Path,
I will provide information what i had got through various sources...
1) Identifying Table
The best way to find out from which tables the data source is getting updated is to search in help.sap.com by using the selection criteria "datasource and the name of the data source".
This displays a table which gives the name of the fields and the table names
2) Naming Convention
1./bic/f (cube name) is the fact table of a content cube
2./bic/D (cube name) P is the package dimension of a content cube
3./bic/D(cube name) U is the unit dimension of a content cube
4./bic/D(cube name) T is the time dimension of a content cube
5./bic/D(cube name) I is the user defined dimension of a content cube
6./bic/m (object name) master data of object
7./bic/t (object name) text data of object
8./bic/H (object name) hierarchy data of object
9./BIC/I* SID Structure of Hierarchies
10./BIC/K* Conversion of Hierarchy Nodes - SID
11./BIC/P* Master Data (Time-Ind.): Characteri
12./BIC/Q* Master Data (Time-Ind.): Characteri
13./BIC/S* Master Data IDs: InfoObject
14./BIC/T* Texts: Char.
15./BIC/X* Attribute SID Table: InfoObject
16./BIC/Y* Attribute SID Table (Time-Dep.):
17./BIC/B* Transfer structure PSA/Changelog
18./BIC/A* ODS Active records
19./BIC/F* Info cube F-Fact table
20.BIC/E* Info cube E-Fact table (compressed records)
21./BIC/D* info cube dimension tables
3) Important tables
I has collected some important tables that may help you..
authorization:
RSSTOBJDIR (Management Table for Authorization Objects): Link between specific authorization object and Info source (table used by transaction RSSM)
InfoPackage
RSLDPIO Links datasource to infopackages
RSLDPIOT InfoPackage Text Description
RSLDPRULE ABAP source code for InfoPackages
RSLDPSEL Hardcoded selections in InfoPackages
ProcessChain
RSEVENTCHAIN Event Chain Processing Event Table
RSEVENTHEAD Header for the event chain
RSEVENTHEADT Header for the event chain
RSPCCHAIN Process chain
RSPCCHAINATTR Attributes for a Process Chain
Queries
RSZELTDIR Directory of the reporting component elements
RSZELTTXT Texts of reporting component elements
RSZELTXREF Directory of query element references
RSRREPDIR Directory of all reports (Query GENUNIID)
RSZCOMPDIR Directory of reporting components
Workbooks
RSRWBINDEX?
List of binary large objects (Excel workbooks)
RSRWBINDEXT?
Titles of binary objects (Excel workbooks)
RSRWBSTORE?
Storage for binary large objects (Excel workbooks)
RSRWBTEMPLATE?
Assignment of Excel workbooks as personal templates
RSRWORKBOOK?
Where-used list for reports in workbooks

MS Excel Tab Naming Convention Issue

Similar Messages

Maybe you are looking for