Modifying Default Form Naming Convention

I have a form that, upon completion, can be attached and emailed. The issue is that when the email is drawn up, the pdf form is named some weird default name. Is there a way to populate the saved attachment dynamically with possibly a field name in the form?

This is true. I guess what i'm trying to ask is if there is a way that I can dynmically change the filename to incorporate values stored in the form fields. Ideally, this form would be used across hundreds of users and wanted someway of at least distinguishing one from another.

Similar Messages

Can default target naming convention be altered?

Dear All
We are using Oracle EM Grid Control 11gR2 to manage databases in the environment which hosts about 60+ databases in 11.0.1.7, 11.0.2.1 and 11.0.2.2 versions..
More often than not due to application restrictions, we are forced to use the same DB_NAME for many databases. Atleast 45+ of them have the same DB_NAME running on different machines with different HOSTNAME....
Each time we add a new target after installing the agent on the new target machine we see the Grid control identify this database using DB_NAME. Since often we have the same value for DB_NAME for the database, we happen to first delete the target identified by GRID after agent installation. Later, we manually add the target as HOSTNAME_DB_NAME and thus we are identifying them seperately from Grid Control Console..
At this point, I was wondering if there is some thing that could work around on the OEM Grid so that every time a target is added, the agent instead of supplying the DB_NAME would automatically supply HOSTNAME_DB_NAME... I did search on net and am not successful yet..
Meanwhile I thought I could post this query here and get your views or ideas... hopefully if you happened to come across such situation and share your experiences.. it would help..
Many thanks in advance.
Regards!
Sarat.

Hello Sarat,
I could direct you to the perl script that is used when discovering new targets and let you modify the default naming convention, however:
- This is not Oracle supported !
- This will result in issues not being able to recover a database using OEM GC. At least this was my experience with OEM GC 10.2.0.3, pretty sure this will be the same in OEM GC 11.1
I would choose to use unique naming for your database in your GRID. (Thi is probably not what you are waiting for...)
Regards
Rob
http://oemgc.wordpress.com

Modification of Default Form

How i will modified default form.
eg. i want to add a link button in existing default form colum.
Any idea.....
Regards,
avijit

Hi Avijit,
You may want to consider using something other than Default Form as it is meant for quick testing and may not fit the business requirements. Create your own form or use UDO Form Generator (if applicable) etc.
Regards
Aravind

Adobe Interactive Forms - Standards & Naming Conventions

Does anyone know where I can locate any documentation pertaining to recommended standards and naming conventions for interactive forms within the SAP NetWeaver '04 platform?

Hi David,
I suggest you start here: https://www.sdn.sap.com/sdn/developerareas/was.sdn?page=AdobeForms.htm. This is where we have collected background information, demos, eLearning materials, and links to the standard documentation for the integrated forms solution. We work together with Adobe on the content of this site.
In due course, we will provide more tips & tricks and best practices.

Is the naming convention of new groups (folders) modifiable?

This is nowhere near being a big deal, but I thought I'd ask anyway.
Currently, the default name of a folder is "Group 1".
When we make a copy of this folder, the default name is "Group 1 copy"
Is there a toggle somewhere to make Photoshop call it "Group 2" instead of "Group 1 copy"?
I ask because I almost always create new folders via copy instead of "create new group".
PS: I'm aware we can rename them after the fact.

I am aware that if you copy something, it is a copy (thanks for the confirmation, though). My question had to do with whether or not we have any control I am unaware of on the default naming conventions within Photoshop (like we do when converting RAW files to PSD, for instance).
Clearly the answer is no by now, unless someone stops by and tells us otherwise.

Draft forms in Queue do not have naming convention

When a form is saved as a draft, there isn't any naming conventions such as the Task Display Name, Process #, or Task #, etc. Is it possible to include some type of naming distinction in the draft forms?
We have multiple forms in Draft and when I need to open a specific form, I must open each form to find the specific form.

Search Templates should help here : LiveCycle ES2.5 * LiveCycle ES2.5 Administration Help
It shows the tasks saved in Draft as well :
Thanks,
Wasil

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

[svn:fx-3.x] 12371: The main AccImpl was updated to handle accessible naming conventions differently than before .

Revision: 12371
Revision: 12371
Author:   [email protected]
Date:     2009-12-02 08:51:12 -0800 (Wed, 02 Dec 2009)
Log Message:
The main AccImpl was updated to handle accessible naming conventions differently than before. This change was made to make the 3.x branch consistent with the trunk changes. The updated methods allows the accessibilityName property to overwrite the logic that was previously used to build the accessible name for components that were inside of forms. This method also provides a method to allow developers to specificy that no form heading or form item label should be included in the accessibilityName for the form field by using a space.
QE notes: none
Doc notes: none
Bugs: n/a
Reviewer: Gordon
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/AccImpl.as

Revision: 12371
Revision: 12371
Author:   [email protected]
Date:     2009-12-02 08:51:12 -0800 (Wed, 02 Dec 2009)
Log Message:
The main AccImpl was updated to handle accessible naming conventions differently than before. This change was made to make the 3.x branch consistent with the trunk changes. The updated methods allows the accessibilityName property to overwrite the logic that was previously used to build the accessible name for components that were inside of forms. This method also provides a method to allow developers to specificy that no form heading or form item label should be included in the accessibilityName for the form field by using a space.
QE notes: none
Doc notes: none
Bugs: n/a
Reviewer: Gordon
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/AccImpl.as

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

How to add a new tab on modify user form

Hi,
In OIM11g, we can assign roles to a user using a tab named Roles in the modify user form. I want to add a new custom tab alongside all the already present tabs.
The new custom attribute functions the same as 'Roles' in OIM.
Does OIM11g provide any functionlity to do so?
Thanks..

Have you seen the 11g tutorial thing about adding a Custom ADF tabs in OIM Self Service Console at
http://apex.oracle.com/pls/apex/f?p=9830:37:3242381082783477::NO:RIR:IR_PRODUCT,IR_PRODUCT_SUITE,IR_PRODUCT_COMPONENT,IR_RELEASE,IR_TYPE,IRC_ROWFILTER,IR_FUNCTIONAL_CATEGORY:,,,OIM_11g,,,
Is that any help?
Also, more general advice on customising OIM 11g is available at:
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e14309/uicust.htm
Try metalink too because there may be examples of how to do stuff with OIM 11g there.
Good luck

Naming convention in template css file

Is there a specific reason for having the theme "name" hardcoded in many css definitions ?
For example consider the css for the rows in a report:
In the css files for each theme it is defined in a different way:
Theme1: td.t1data
Theme2: td.t2data
Theme3: td.t3data
...Overriding these values and manipulating the styles using Javascript gets a bit cumbersome if it should work across themes.
Are there any naming conflicts or is it just for historic reasons that don't apply anymore in the 2.0 release?
In other words, would it be safe to use just td.data in new templates or will I run into problems doing this?
Thanks,
~Dietmar.

Hi Carl,
thanks for the clarification. I had figured that you had a good reason to do so.
It's a tradeoff, either approach has pros and cons.
Most likely we will stick with that type of naming convention, but we'll look into it again.I would like to throw in an idea. You can add multiple css classes to an html tag, e.g.
<td class="t12data data">The css for the class data would be empty.
This way we could have both, different class names for different themes, but also having the elements "tagged" the same way so that the javascript should work.
Haven't thought it out, it just came to my mind. You might consider it.
And yes using td.data should be just fineI guess I will go down that route.
I will create only a single theme and then use multiple css style sheets to modify the look and feel.
This way I can switch the theme on the fly by switching style sheets only.
Javascript modifications will work since the css class names are the same.
All customized region templates will only have to be created once (and not for all themes).
Thanks and a Happy New Year,
~Dietmar.

Best practices in Internal table naming convention GT , GS , LT , LS ??

Hi Gurus,
 Are GT_ , GS_ , LT_ , LS_ --- the Best practices in Internal table naming convention ????
 I have seen this naming convetions adhered in standard programs .
 What each one of the below signify
 GT_ , GS_ , LT_ , LS_ ???????
Regards
Jaman
Message was edited by:
 ABAP Techie

Hello
I use the following naming conventions:
- G = global variable
- L = local variable
- T = internal table
- S = structure
- D = field
That's how the combinations look like:
- GT_ITAB = global itab
- GS_STRUC = global structure
- GD_FIELD = global field
- LT_ITAB = local itab
- LS_STRUC = local structure
- LD_FIELD = local field
Function module parameters have to stick to the following rules:
- I = importing
- E = exporting
- [C = changing -> never used]
- IT_ITAB = imported table type (itab)
- IS_STRUC = imported structure
- ID_FIELD = imported field
- ET_ITAB = exported table type (itab)
- ES_STRUC = exported structure
- ED_FIELD = exported field
Depending on their semantics TABLES parameters look like:
- IT_ITAB = imported data
- ET_ITAB = exported data
- XT_ITAB = changing data (import & export)
Here are the conventions for FORM routine parameters:
- UT_ITAB = using itab (data are usually treated like constants; no changes will be transfer - although possible - to the calling program)
- CT_ITAB = changing itab (if it is semantically an exporting itab then one of the very
first statements in the routine is: REFRESH ct_itab. )
- US_STRUCT
- UD_FIELD
- CS_STRUCT
- CS_FIELD
Conventions for class/interface parameters:
- IT_ITAB = importing table type
- IS_STRUC = importing structure
- ID_FIELD = importing field
- ET_ITAB = exporting table type
- ES_STRUC = exporting structure
- ED_FIELD = exporting field
- RT_ITAB = returning table type
- RS_STRUC = returning structure
- RD_FIELD = returning field
Conventions for class/interface attributes:
- MT_ITAB = table type
- MS_STRUC = structure
- MD_FIELD = field
- MC_CONST = constant
Question: Are there any advantages of such elaborated naming conventions?
My answer to this question is: Yes, definitively.
I believe that the advantage of semantically differentiating TABLES parameters of function modules is quite obvious:
CALL FUNCTION 'Z_BAD_NAMING'
 TABLES
 itab1 = ...
 itab2 = ...
 itab3 = ... .
CALL FUNCTION 'Z_GOOD_NAMING'
 TABLES
 it_itab1 = ...
 et_itab2 = ...
 xt_itab3 = ... .
I also believe that my naming conventions clearly enhance readability and maintainability of my programs.
Regards
Uwe

ABAP Naming Conventions

Hi All,
I'm looking for a document describing ALL basic ABAP Naming Conventions. For example, how to name data types such as tables, structures, predefined ABAP types, and so on. Furthermore, it would be desirable to know how the declaration changes in different contexts - report, form, function module, class, and so on.
Thank you.

Hi,
as I am working as a consultant for lots of companies in last 10 years, I know that there is no such document. Each company has it's own naming conventions and programming guides. The only thing that is common for all companies is: All customer defined stuff starts with a Z or a Y and in case the company registered it's own name space it starts with /<name space/. May be, somebody can send you these guides coming from whatever company.
regards
Siggi

Code Inspector - Naming conventions &mExtended Naming conventions for Progs

Hi experts,
I had a look into the naming conventions enforced by 'DEFAULT' variant of code inspector (SCI).
the relevant categories are: "Naming Conventions", and "Extended Naming conventions for Programs" under "Programing conventions".
in the "Extended Naming conventions for Programs" category, for functions, (applicable while calling the functions) it says,
importing parameter : I[:type:]_
exporting parameter : E[:type:]_
changing parameter : C[:type:]_
tables parameter : T[:type:]_
but in the "naming conventions" category, for functions (applicable while defining the functions), it says,
importing parameter : P_*
exporting parameter : P_*
changing parameter : P_*
tables parameter : P_*
I felt, while defining the function too, its better to have beginning with I_, E_, C_ or T_ instead of P_
is the 'DEFAULT' variant of code inspector is provided and recommended by SAP?
for easier maintenance and clearer understanding, which naming convention is more suitable, or is there any official guidelines released by SAP for ABAP developers.
appreciate the opinions from experienced abap developers.
thanks,
Madhu_1980

Frank,
Thanks for your answer.
But what about Entity Objects, View Objects, View Links, and Application Modules.
I would like my developers to have an easy way to name them and also find them via intellisense.
So I was thinking in naming them the following way :
Entity Objects :
EO_Employee
EO_Department
View Objects :
VO_Employees
VO_Departments
View Links :
VL_EmployeesToDepartments
Application Module :
AM_HRService
However the use of "_" is not so "Java naming oriented".
So other alternatives would be:
1. take the "_" :
1.1 EOEmployee (I don't like the fact of having 3 capital letters together).
1.2 EoEmployee (I don't like the fact of having Entity Object with a lowercase "o").
2. Use the prefix at the end, but this way I loose the intellisense feature I want:
ex: EmployeeEO
Which naming approach are you using for big projects ?
Thanks,
Claudio.

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

Modifying Default Form Naming Convention

Similar Messages

Maybe you are looking for