SAN device naming conventions with EMC symmetrix

Hi,
How CTD are named using Solaris 8 ssd drivers ?
Regards

I've gotten around this by either using a symbolic link to the device or just doing a mknod to recreate the device special files so the names match across the cluster. You only need to do this for the OCR and Voting devices, you don't need consistent names for ASM.
If you use EMC's PowerPath software the name should be synced across the nodes, if not copy the PowerPath device data files (/etc/emcp_devicesDB.dat and .idx) from 1 nod to the other nodes and reboot. This will sync up the EMC device names too...

Similar Messages

Custom naming convention with File Adapter

Within my BPEL process, I am using File Adapter and writing out a file. The current naming convention only all some static string with either a sequence (%SEQ%) or some sort of system timestamp. I wonder if it is possible to use some runtime data (data value within the Process Variables) as part of the file name being written out.

Hi, the file/FTP adapters support file metadata such as filename and directory to the BPEL process and exclude the payload. set the UseHeaders parameter to true in the file adapter WSDL.
*<jca:operation*
PhysicalDirectory=""
ActivationSpec="oracle.tip.adapter.file.inbound.FileActivationSpec"
PhysicalArchiveDirectory=""
DeleteFile="true"
IncludeFiles=""
PollingFrequency=""
MinimumAge="0"
OpaqueSchema="false" >
UseHeaders="true"
*</jca:operation>*
thanks.

Implementing Transport Naming convention with the help of BAdIs (Urgent)

Hi Gurus,
We need to implement Transport Naming convention in our landscape.
Transport request should follow the following naming conventions and to enable this we have to enable some necessary BAdIs?
Scenario would be like this....!
Customization
LC-<Track>-<Description> (Non Transportable Request)
<Module>-<Track>-<Configuration Type>-<Change No>-<Description of the Customisation.>
ABAP Developments
AB-<Track>-<Configuration Type>-<Development No>-<Description of the Development>
OSS Notes
BC-<Track>-OSS#<OSS Note No>-<Version>-<Patch Number>-<Process Team>-<Note Description>
Authorization
BA-<Track>-<Version>-<Authorisation Description>
Details :
Track : 01 u2013 Hot fixing, 02 u2013 Implementation, 03 u2013 BIW / EP, 04 u2013 Support
Module : SAP Module (FI, CO, MM, SD, PP, etc..)
Configuration Type : I u2013 Initial Configuration, R u2013 Change due to TPR or Additional Functionality
Change No / Development No : Unique no to trance the base documentation
Please suggest .....................!
Which are the necessary BAdIs needs to be enabled and what other configuration needs to be done.
If anybody has any document please provide.
Thanks in advance..............!!!
Regards,
Jai Sach

Hello,
SPRO --> SAP NetWeaver --> Application Server -->
System administration --> Change & Transport domain
--> BADI -->Business Add-In when Editing Requests
IF_EX_CTS_REQUEST_CHECK~CHECK_BEFORE_CREATION
Happy Tony

Device naming convention for san disks

Hi,
Is there a way I can force a san disk to obtain a certain device name? for example if a hitachi device shows up as c6t5000000000, can make it c5t5000000000. Is there some option in /kernel/drv/fp.conf or sd.conf? Is there a way to disable one port on the Qlogic HBA? Thanks for your assistance.

The controller number (c) in ctdt notation is assigned by the OS when it is buillt, and additional controllers added on after are added in numerical order.
Some SANs allow you to specify the "scsi-id" (at the end of the wwpn on FC).
This behavior can be a real pain if you move a SCSI card from slot to slot, each time it gets a new c#, also can be amusing on larger systems (e.g. F-6800) with an OS installed on a domain, that is then expanded to include more I/O devices, the c#s will not necessarily match when the expanded domain is booted from "CD".
In the brave new world of LDOMs there is a fix ! I assign the volumes normally (resulting in different ctdt) on each server, then use DiskSuite to give each LUN the same md### , when presenting the VDIsk you can specify disk ID.
e.g.
server..... ctdt...................... ....... SDS ......... VDSdev.......... VDisk ...Guest sees
primary01 c2t500000ab13t0d5 --> md21 ---> dbdev_u21 --> disk21 c0d21sx
primary02 c3t510000ab13t0da --> md21 ---> dbdev_u21 --> disk21 c0d21sx
Edited by: HarryC on Dec 30, 2009 10:44 AM

The naming convention of the disk device name (/dev/dsk/cXdY)

Hi All,
Please let me know the naming convention of the disk device name (/dev/dsk/cXdY) recognized on OS of a guest domain.
I found from the document of Oracle that the value specified as the id option of ldm add-vdisk command went into Y of cXdY.
However, there is no telling by what kind of rule X portion of cXdY is decided.

Hello
I have found this in the man ldm but I don't know how to related the cN, I mean I don't know where the N comes from. Still checking and trying to get more info.
vdisk
Virtual disks are generic block devices backed by different types of physical devices, volumes, or files. A virtual disk is not synonymous with a SCSI disk and, therefore, excludes the target ID (tN) in the disk name. Virtual disks in a logical domain have the following format: cNdNsN, where cN is the virtual controller, dN is the virtual disk number, and sN is the slice.
Regards
Eze

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>

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

Flatfile conversion with output file has a NAMING CONVENTION

Dear SAP experts,
I need some advise regarding my scenario.
I am converting a message into flatfile. (customized .csv)
But, the output .csv flatfile must have a naming convention.
E.g. Globus_20071020 (Customer name_YearMonthDate)
Can somebody give me ideas/inputs on what will I configure in File Receiver (FCC) in order to have an output file having a naming convention indicated above.
Or do i need additional configurations?
Please advise.
Thank you very much in advance.
Fred

Hi,
You could pass this kind of File name from mapping at runtime or
You could use the variable substitutions to create the fiel neame as per naming convention as adding date .
With reference to Variables youcould set file name as Globus_%payload.<Date>%
Pass the value in date field of payload
Refer
Variable Substitution
How to use Variable substituion
/people/sameer.shadab/blog/2005/09/23/an-interesting-usage-of-variable-substitution-in-xi
/people/sravya.talanki2/blog/2005/08/11/solution-to-the-problem-encountered-using-variable-substitution-with-xi-sp12
how to use attributes in variable substitution???:(
Dynamic file name
/people/jayakrishnan.nair/blog/2005/06/20/dynamic-file-name-using-xi-30-sp12-part--i --> Dynamic File Name using XI 3.0 SP12 Part I
/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii --> Dynamic file name(XSLT Mapping with Java Enhancement) using XI 3.0 SP12 Part -II
Dynamic File name in File adapter
/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14
1. In the sender file adapter , select Adapter Specific Attributes --> FileName.
2. Use the code in this link to read the filename inside a UDF in your mapping.
DynamicConfiguration conf = (DynamicConfiguration) container
.getTransformationParameters()
.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create(
http://sap.com/xi/XI/System/File,
FileName);
String filename = conf.get(key);
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/03612cdecc6e76e10000000a422035/content.htm
Thanks
Swarup

Mpxio or Powerpath -- with EMC SANs?

We have some new T3-1B's running on Solaris 10.
We normally use PowerPath, but I'm trying to see if we can just use mpxio and be done. However, the issue I'm running into is the following.
1. I dont have any way of determining which LUN is what -- in the CX500--I use the LUN Name to determine what the disk needs to be assigned to. I see only the WWN. With Oracle RAC, it's extremely important to make sure the disks are correct to each node.
2. When adding new disks to the host, the new LUN does not appear on the host even after luxadm probe, and repeated devfsadm. Am I missing anything else? Any help would be appreciated.

I'm not sure what kind of commentary you are looking for.
We use Powerpath on Solaris 10 (x86 now, but in the past on T5120s) for multipathing to LUNs on EMC VNX and CX4 SANs. We followed the EMC Powerpath setup guide for Solaris 10 exactly.
After disabling MPxIO, Powerpath was able to take control. Some older versions of powerpath had a bug where the pseudo names for LUNs would change causing some headaches.
We keep a mapping of LUN to pseudo name to solaris dsk labels
If you use ZFS I have found a 1:1 match between the zfs_max_vdev_pending value and the max queued-IOs value shown in Powerpath
When we've had to fail/trespass LUNs over to other SPs on the EMC SANs, Powerpath has handled this elegantly with the expected warnings in /var/adm/messages
I recall that we had to explicitly set the powerpath options for CLARiiON and VNX to managed and the policy to claropt
When adding LUNs, to see all paths there is a routine to go through with cfgadm, devfsadm and the powerpath utilities. We use qlogic HBAs and the qlc leadville driver.

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

Revised naming convention for photo-merging

After a photomerge from Bridge from "Process Collections in Photoshop", the filenames seem arbitrary and could be more helpful.
I would prefer something like the first file in the merge, then either the last, or the count of files involved. Also, consider having the "pano" at the end so it is easier to associate the pano with the files that make up the pano.
IMG_1234.dng
IMG_1235.dng
IMG_1236.dng
IMG_1237.dng
would become either
IMG_1234_4.psd
or
IMG_1234__IMG_1237_pano.psd

john.giarrusso wrote:
Is it possible to change the naming convention for photo's on a device from IMG_0001 (as an example) to something else?
Sorry, no, not on the device itself.

EMC Symmetrix Installation and Administration on Solaris

Hi,
Could anyone tell me where i can get good documents on Installation and administration of EMC Symmetrix devices with a volume manager on a Solaris box.
Thanks.

On another note... is there a Sparc equivalent for the mod_wl_ohs.conf where we would place
<Location /<deployed app>>
SetHandler weblogic-handler
WebLogicHost <weblogichost>
WebLogicPort 7001
</Location>
It appears that this goes into the apache httpd.conf file, correct? Or does the mod_wl_ohs.conf equivalent exist?
We have just about completed everything in regard to being able to include a solaris host in our list of hosts that are tied to OAM. The webgate was created and software installed, the deployed app protected, etc... Everything that we have done for Linux and XP in the past we have done for this Sparc host.
When we try to access the Sparc's protected uri... nothing happens. The browser stays blank... the url does not change to display the oamsso login.html (as the other installs do)... nothing is returned... no error, no remarks, no logfile entries... just a blank browser.

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
<b><storename>_date_masterdataname.xml</b>where 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 <b>file name schema</b> (from the file communication channel can look like this)
%storename%_date_masterdataname.xml
Regards,
michal
Message was edited by: Michal Krawczyk

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!

SAN device naming conventions with EMC symmetrix

Similar Messages

Maybe you are looking for