Production Version naming convention

Hi all,
We are using PDS and it is being transferred from R/3.
The problem is in R/3, in many cases different materials are having the same production version numbers.
If we have the same production version number will it cause any problem / confusion while transfer to APO and in further planning process in APO ?
Current situation in R/3 :
Product A : Production Versions 0011,0012,0013....
Product B : Production Versions 0012,0013,Z014..... Is this ok ?
Or is it better to delete and create with unique production version number in R/3 before transferring ?
Kindly guide.
Durai

Hi Durai,
The PDS will get the combo structure of product-location-version no only.
So, there is no harm in having different products having same production version numbers.
Regards
R. Senthil Mareeswaran.

Similar Messages

  • JDK version naming convention?

    When I run "java -version" from command line, the output is:
    C:\>java -version
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
    Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
    I wonder what do the "1.4.2" and "build 1.4.2-b28" and "build 1.4.2-b28 mixed mode" mean separately?
    What about Sun Java 2 SDK 1.4.2_03?
    As for java version, does sun have an official naming convention?
    Any help will be appreciated.
    -yunfeng

    I hope these documents answer your question:
    http://java.sun.com/j2se/versioning_naming.html
    http://java.sun.com/j2se/codenames.html
    I think "mixed mode" refers to the level JIT compilation; "mixed mode" means that the virtual machine interpretes parts of the byte code and compiles parts to machine code. If you run the VM in interpreted mode instead (java -Xint -version) it will say "interpreted mode."

  • Versions naming conventions on Duplicate Project

    I love adding "v001" at the end of project name, but when I duplicate the project:
    [project name] v001
    [project name] v001 1
    [project name] v001 2
    and I hope it will be:
    [project name] v001
    [project name] v002
    [project name] v003
    and I found if you fcpx just allow this naming convention
    [project name] 1
    [project name] 2
    [project name] 3
    and I thought it was the "v" problem, then I remove the v from "v001", it results:
    [project name] 001
    [project name] 2
    [project name] 3
    the "00" disappear! so will fcpx fix that? so I can use v001, v002 or someone v01, v02 or 001,002,003

    Andy Scott3 wrote:
    Maybe someone could help me out here.
    In L7 I was able to open a page where I could name tracks before recording them but now in 9 I still haven't found out how to do this so land up with numbered tracks which I then rename in the bin.
    As for track, channel, mixer naming...what a nightmare! I often land up having to rename almost everything twice per session and even then the mixer often displays something else! I'm almost at the point of having to just ignore names and go by region names and track numbers instead.
    Create the amount of audio tracks you want and double click on their title (i.e. Audio 1, Audio 2 etc) on the arrangement layout or their title on the mixer layout and rename the track/s to what you want before you record.
    If you forget to do this prior to recording and you name the tracks later, you can easily rename all the regions at once by selecting region > track names to regions
    I would recommend setting up a template file with all your common recording tracks named so that you don't have to do this each time you start a project.

  • Versions naming conventions

    If I create versions of masters, the versions are named: "[name of master] Version 1".
    I want to change der part "Version xy" to "-xy" so that the word "Version" is replaced by a dash to keep names short.
    Is this possible?
    regards,
    Markus

    Select the images you want to change. Go to Metadada, Batch Change. At Current version name choose edit. Erase what's in the box and select Custom name with counter. Type the name and select the number of digits and the starting number. Click OK and then click OK in the Batch Change box and you're done.
    Jeff

  • Version Naming Convention for Internet Explorer

    Notice on the far right side there is a
    Emoticon smiley face on the far right side.  This comes directly out of something I read and also did almost twenty years ago.  Did this cause the version update to 11?  I am not familiar with the metrics to call for a higher
    version.  It also appears to be deactivated.  I believe the w3c html is readily available as well as the specific compliers to develop a browser. 

    Hi, the emoticon is actually a feedback tool for Internet Explorer incorporated into the 9879 build. It's supposed to work by clicking on the icon when you come across a problem for whatever web page your on and reporting the problem on the spot instead
    of using the windows feedback app.

  • Inconsistent naming conventions for Adobe Reader in software scan

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

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

  • 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

  • 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

  • XML Schema Component Naming Convention

    Is there a naming convention when you create an XML Schema? For example,
    When you create a Type component, then the first letter of its name should be upper case ie. BMW, Honda, AutombileEngine ...etc.
    When you create an Element component, then the first letter of its name is lowercase ie. engine, car, guestCar ..etc.
    Do we have such naming convention for XML Schema?
    Thanks

    I am giving this from my document which i prepared for one of my customer
    2     General Guidelines for design of XML schema documents
    The representation of data in an XML format will be a key component of development within SOA. Therefore, the design and development of XML schemas should be as rigorous an activity as designing and developing code or designing database schemas. As such, when creating an XML schema you should be working within a development process and working to a set of design guidelines and coding standards (when writing the XML schema file). XML schemas should be reviewed for accuracy and compliance with guidelines and standards. Each of the requirements in the list below is a general requirement for all XML schemas to be deployed in the SOA environment.
    •     Understandable: XML schemas should be clear, consistent and unambiguous. They should contain human readable documentation and, where appropriate, links to requirements or design documents.
    •     Semantically Complete: An XML schema should define, for one or more target XML documents, each and every element and attribute that is understood by your solution when processing target documents.
    •     Constraining: XML schemas are used as contracts between both publisher and consumer. As such, they must be able to be validated as concisely as possible. When designing an XML schema constraints should be identified for the values for all the elements and attributes that the application uses and relies on to the set of values that the application can handle. A valid document should imply valid data within the limits of what can be specified by the XML Schema language.
    •     Uniquely identifiable: XML schemas should import and include other XML schema files rather than duplicating types and elements locally.
    •     Reusable: XML schemas should be specified in such a way that types and other XML schemas can leverage elements. Every type defined in an XML schema that is the content type of an attribute or an element should be defined globally (i.e., at the top level in the Schema). Types that are defined globally can be reused in other XML schemas. Schemas should be separated into logical sections which can be included into the main schema file.
    •     Extensible: Schemas should be designed to be extensible—that is, new elements and attributes can be inserted throughout the document.
    Every schema should use at least two namespaces – the targetNamespace and the XML Schema (http://www.w3.org/2001/XMLSchema) namespace.
    Create typed elements that can be referred to by object elements:
    Example:
    <?xml version="1.0"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    targetNamespace="http://www.soa.com"
    xmlns="http://www.soai.com"
    elementFormDefault="qualified">
    <xsd:complexType name="PersonType">
    <xsd:sequence>
    <xsd:element name="Name" type="xsd:string"/>
    <xsd:element name="SSN" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    <?xml version="1.0"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    targetNamespace="http://www.company.org"
    xmlns="http://www.company.org"
    elementFormDefault="qualified">
    <xsd:include schemaLocation="Person.xsd"/>
    <xsd:include schemaLocation="Product.xsd"/>
    <xsd:element name="Company">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="Person" type="PersonType" maxOccurs="unbounded"/>
    <xsd:element name="Product" type="ProductType" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    •     Recognize that with XML Schemas you will not be able to express all your business rules.
    o     Express those business rules using XSLT.
    •     Use type definitions
    Elements vs Attributes
    •     Use attributes for metadata about the parent element.
    •     Use attributes for data that is semantically tied to the enclosing element.
    •     Use elements for data that have a meaning separate from the enclosing element.
    •     Use attributes when the value will be frequently present in order to improve the human readable form of an XML instance document or reduce its size.
    •     If you don't know which to use, then use the element form (which is more extensible).
    2.1.1     Element, Types and attribute names
    Create a descriptive name without it being excessively long (no more than 32 characters).
    Elements and Types should be named in Upper Camel Case. Upper Camel Case capitalizes the first character of each word and compounds the name (remove all whitespace).
    Attributes should be named in Lower Camel Case. Lower Camel Case capitalizes the first character of each word except the first word and compounds the name.
    Simple and Complex type names
    XML Schema has separate symbol space for elements and types so they may have the same name. The best practice is to append the word "Type" to all simple and complex type names to aid in human readability and comprehension.
    Element, attribute and type names MUST be in a singular form unless the concept itself is plural.
    2.1.1.1     XML Schema versioning
    Use major and minor version tracking:
    Major—completely different structure and semantics, most likely not backward compatible
    Minor—backward compatible changes which introduce new features without removing or changing the semantics of existing structures
    2.1.1.2     Indication of version in the namespace URI
    Specify a namespace URI as follows
    http://$domain/$groupSpecifier/$namespaceTitle/$version
    The groupSpecifier can include several levels, e.g., /www.soa.com/SOA/USA/.
    An example namespace could be:
    http://www.soa.com/SOA/order/2

  • Data Modeler - Naming Conventions

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

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

  • -cvs, -git, -snv... is really a good naming convention?

    The unstable packages have the name of their relative stable one with added in suffix the concurrent version system installed.
    I think it is a bad convention since it mixes implementer choices with the the concept of lastest unstable version.
    I think it is better decide a single suffix (e.g., -unstable or -dev) and always use it without difference between the implementer choices of programming.
    Moreover it avoids renaming headaches if someone changes program for keeping versions.
    No flame wars. I decide nothing. It is only a thought.

    Profjim wrote:
    I've seen this discussed before on the forums...
    Edit: http://bbs.archlinux.org/viewtopic.php?id=25938
    I found this in the forum search: http://bbs.archlinux.org/viewtopic.php?id=25938
    It doesn't seem like anything came out of that discussion. I haven't really found the naming convention confusing; it is the large variety of SCMs that is confusing, and that is not going to change anytime soon. The current package naming conventions are unproblematic for me so you'd have to point out exactly where a real problem has cropped up.

  • ArrayOfClass naming convention in webservice

    When I generate array of any class through autotype, the name of the serialiser, deserialise and type name in wsdl generated as ArrayOfClassName.
    But according to WSI basic profile 1.0 naming convention (R2112), bea should not use ArrayOfClassName.
    Here is the sample code snippet..
    <autotype                    javatypes="[LPackage.Interest;"
    targetNamespace="${namespace}"
         packageName="XX.YY"                    encoding="literal"                    destDir="${build}/NonBuiltType" />
    Can someone please tell me if autotype has any flag or facility to change the naming convention?
    Thanks in advance. A reply would be very much appreciated.
    cheers
    Biswa

    Hi Deepti,
    we have the following naming convention:
    Aggregation Level similar to Cube:
    e.g. Cube = ZPP_RC01 --> PP for Production Planning; RC for Real-time Cube and 01 just a sequential number
    than the Aggregation Level will become ZPP_AL01 --> AL for Aggregation Level
    Filter:
    starting with AL name and just a sequential number: e.g. ZPP_AL01_F1
    Planning function:
    e.g. ZPF_01 ... PF for Planning Function and sequential number
    Planning Sequence
    e.g. ZPS_01 ... PS for Planning Sequence and sequential number
    Best greetings,
    Peggy

  • 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

  • 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

  • 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

Maybe you are looking for