What are the following Fields meant to contain...?

What info are the following Fields in iTunes meant to contain?
'Comments', 'Description', 'Category', 'Grouping'?
Thanks.

They're not meant to contain anything, so they may be blank. However, those fields are there for various purposes. For example, pick any song or Podcast in your Library:
Comments: this field can have a note about the song, Podcast etc. etc. Amazon use the Comments field to make a note of the Amazon ID they assign a song when they sell it to you. You can edit the Comments field if you wish, adding any note that you want, for your own purposes.
Description: is used by Podcasters. They enter a description of their Podcast, typically a little information about that particular show. This field for a song etc, can be found (and edited) on the Videos tab of the song, (even if it's not a video!). Not all Podcasters make use of this field and not usually used in songs.
Category: Used by iTunes Radio services, to identify the type of programming they offer. Also used by Podcasters. Not always used by either service and not usually used in songs.
Grouping: Ah! Now, this is a good and useful field. Suppose you want a song to be in two different genres. Well, that cannot be done. However, if you want one song with genre "Rock" to also be included with all your "70's Pop" genre, simply type Rock into the grouping field and then create a Smart Playlist which has the rules: Genre is 70's Pop and Grouping is Rock. This Smart Playlist will have all the "70's Pop" genre in it and any song that you have typed "Rock" into the Grouping field. It will not have any of the other Rock genre in the list.
Actually, a Smart Playlist can make use of any of the fields you have mentioned. So it's possible to create a Smart Playlist that picks out any song or Podcast etc. containing a particular word in the Description field and a different word in the Comments field.

Similar Messages

  • What are the key fields used to group double orders in t-code SDD1?

    What are the key fields used to group double orders in t-code SDD1?
    Cheers,
    VT

    Hi,
    You can group the duplicate sales documents with the help of the following fields,
    Sold-To-Party,Document type,date and sales area details.
    Regards,
    Gopal.

  • What are the Corresponding fields in CRM for sales order in ECC

    HI! Experts,
    While creating a standard sales order in CRM I want to poulate these fields in ECC Sales order, these fields are
    VBKD-BSARK - Purchase order type
    VBAK-BNAME - Name: user ordered
    VBKD-IHREZ - Web Confirmation Number
    VBAK-TELF1 - Telephone number
    Or the other way round I want to know what are the corresponding fields in CRM for these fields so that when I pass the data in crmd_order in those fields it gets populated in the above mentioned fields.
    Thanks and Regards
    Mayank

    Mayank,
    May I suggest you to create an Order in R/3 with these fields and check that back in CRM. This is not as easy as it may sound. It is possible that some of these fields are "determined" by the system - for example the "Sold-To"'s first telephone number maintained in VBAK-TELF1. So, though it becomes a part of the Order header in R/3, CRM, generally doesn't duplicate them in the transaction but allows to refer back to the master data from the transaction!
    Check the following fields in CRM and see if you find the data you require.
    VBKD-BSARK - Purchase order type There is a field in CRM that "holds" this value. ACTIVITY CATEGORY. This can be found in the ACTIVITY_H set of the transaction. Filed name CATEGORY. Problem with this is, - "Category Type" of a CRM Activity to be mapped to PO type? Didn't workout good for us since the master data for both vary widely. So, we used custom Header Extension data for this (EEWB). So, you have to work
    VBAK-BNAME - Name: user ordered Is usually CREATED_BY in the CRM Order Header (CRMD_ORDERADM_H). But this fills up the VBAK_ERNAM bit not the BNAME.See the next item, that may give a clue if this is related to the next item.
    VBAK-TELF1 - Telephone number is usually "determined". Usually the Sold-To's first telephone number maintained in the Business Partner "Communication" section for that Sold-To.
    VBKD-IHREZ - Web Confirmation Number Actually it is Customer's or vendor's internal reference as per standard use. Looks like your customer is using it for custom purposes. Well, if you maintain the relationship  "Is Correwspondence Recipient for" with the Sold-To partner in CRM, and maintain the details of this Person, then this will be transferred to R/3.
    Hint: Once you have the R/3 order in CRM, try using the Report program (SE38)  CRM_ORDER_READ in CRM. This is a good tool to "dissect and see" and order in CRM. The program needs only the Transaction Number as the input.
    Easwar Ram
    http://www.parxlns.com

  • What are the following entries doing in the following configuration file?

    What are the following entries doing in the following configuration file?
    Thank you
    <include>coherence-pof-config.xml</include>
    <allow-interfaces>true</allow-interfaces>
    <allow-subclasses>true</allow-subclasses>
    <?xml version="1.0"?>
    <!DOCTYPE pof-config SYSTEM "pof-config.dtd">
    <pof-config>
    <user-type-list>
    <!-- coherence POF user types -->
    <include>coherence-pof-config.xml</include>
    <!-- com.tangosol.examples package -->
    <allow-interfaces>true</allow-interfaces>
    <allow-subclasses>true</allow-subclasses>
    </pof-config>

    <allow-interfaces> - The allow-interfaces element indicates whether the user-type class-name can specify Java interface types in addition to Java class types. Valid values are "true" or "false". Default value is false.
    <allow-subclasses> - The allow-subclasses element indicates whether the user-type class-name can specify a Java class type that is abstract, and whether sub-classes of any specified user-type class-name will be permitted at runtime and automatically mapped to the specified super-class for purposes of obtaining a serializer. Valid values are "true" or "false". Default value is false.
    <user-type-list> - The user-type-list element contains zero or more user-type elements. Each POF user type that will be used must be listed in the user-type-list. The user-type-list element may also contain zero or more include elements. Each include element is used to add user-type elements defined in another pof-config file.
    <include> The include element specifies the location of a pof-config file to load user-type elements from. The value is a locator string (either a valid path or URL) that identifies the location of the target pof-config file.
    http://wiki.tangosol.com/display/COH35UG/user-type-list
    http://wiki.tangosol.com/display/COH35UG/pof-config
    Thanks,
    Everett Williams
    Coherence Team

  • What are the mandatory fields while creation of material master in differen

    what are the mandatory fields while creation of material master in different views?

    Hi Gopi,
      This is purely depends on the function configuration, which would be done MM consultants.  Kindly check with them.
    thanks & regards
    Kishore Kumar Maram

  • What are the mandatory fields needed to setup/register the SIP phone manually in CUCM

    What are the mandatory fields needed to setup/register the SIP phone manually.Also, if someone can let me know the mandatory fields for Cisco based SIP phone and also the third party SIP hard phones like Avaya or any other Third party SIP phones both Soft phone and physical phone requirements...in CUCM
    Please suggest...I need to know if MAC address is mandatory for all Cisco SIP phone to setup 

    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/7_1_2/ccmcfg/bccm-712-cm/b09sip3p.html
    http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-version-70/112110-phone-add-00.html

  • What are the corresponding field names

    Hi,
    What are the corresponding field names for the followings:
    (1) Last post goods issue date
    (2) No of finished goods movement days
    (3) Unit price per carton
    (4) Per carton quantity
    Thanks.

    hello, friend.
    you can find out the technical names (to include table and field names) by going to the fields themselves, and clicking on 'F1'.  the "Performance Assistant" will appear.  in this latter screen, go to the menu and click on the 'Technical Info' icon that looks like a hammer and wrench.  you will find your info there.
    regards.

  • What are the following:1)Cisco 1600 Series IOS WIRELESS LAN RECOVERY. 2)Service Provider Option 60 for Vendor Class Idenfier

    What are the following:1)Cisco 1600 Series IOS WIRELESS LAN RECOVERY. 2)Service Provider Option 60 for Vendor Class Idenfier
    These items are listed with 1600 series AP but I'm unable to understand what are these things & the use of them

    DHCP Option 60:  Go HERE.

  • What are the following script doing?

    What are the following script doing? What does symbol *<* stand for?
    protected Map<Member, List<String>> divideWork(Set members, List<String>
    fileNames)
    Thank you

    su_penguin wrote:
    Side note: http://en.wikipedia.org/wiki/Operator_overloading
    Extra credit: What trick does Java's syntax use to allow Generics to compile with or without whitespace between the angle brackets? Ex: Map< Member, List< String > >
    Why doesn't it work in C++?Does this have something to do with the comment "Note that it is not an LL(1) grammar"? [http://java.sun.com/docs/books/jls/third_edition/html/syntax.html]

  • RV_INVOICE_CREATE for this FM what are the mandatory fields

    Hi guru,
            in my process development, first i am creating the sales order using the BAPI FM SD_SALESDOCUMENT_CREATE, From this FM i get the sales order no, after that i use this fm RV_INVOICE_CREATE , then i pass the VBELN (sales order no), but it is not created the invoice no,
    what are the fields i have to pass for this FM.
    What is the use of this FM : RV_INVOICE_DOCUMENT_ADD, is it useful in my scenario.
    plz give the details briefly
    thanks & regards
         raj.

    HI ,
    call function 'RV_INVOICE_CREATE'
        exporting
          with_posting = 'B'
          vbsk_i       = i_xvbsk
        importing
          vbsk_e       = i_xvbsk
        tables
          xkomv        = xkomv
          xvbpa        = xvbpa
          xvbrp        = xvbrp
          xvbrk        = xvbrk
          xkomfk       = i_komfk
          xthead       = xthead
          xvbfs        = i_vbfs
          xvbss        = i_vbss.
    These table are not optional , these all are mand...
    Reagrds,
    Bharani

  • What are the common fields in table KONV = J_1IEXCHDR,EKKO,EKPO,MSEG

    Helo everyone,
    I need wht are the common fields between table of KONV and J_1IEXCHDR,EKKO,EKPO,MSEG. Pls give me details
    thanks in advance
    suresh

    check out LIFNR,KUNNR ETC

  • What are the mandatory fields in DTW for opening balances imports?

    Hi All,
    As the title mentions could you please help by listing all the mandatory fields in DTW for importing opening balances ?
    Thank you for your help,
    MB

    Hi Gordon and all,
    I have a look at the SDk help files and almost cried but am i right in thinking it is Account Code, Debit and Credit fields that are the mandatory fields for opening balances?
    These sdk help files are awful by the way...really awful.
    MB

  • What are the Mandatory Fields in Transaction ME51

    Hello Seniors,
    I have a requirement about purchase order creation. In this process, I am using the BAPI named   " BAPI_PO_CREATE1 ". I have passed all the fields but when I debug and look into the internal tables, I couldn't find certain records. I even debugged " bapiret2"  and I see an error which reads "" All mandatory fields are missing"". I have even created a PO  in ME51 and found out the mandatory fields but in vain. BAPIRET2 still says, there are some more mandatory fields missing. I need to know what are all the mandatory fields to create a Purchase order using TCODE - ME51.
    Your reply is most awaited and rewarded.
    Thanks and Regards,
    MARKIV

    hi ,
    Functionality
    Function module BAPI_PO_CREATE1 enables you to create purchase orders. The BAPI uses the technology behind the Enjoy purchase order transaction ( ME21N).
    Alternatively, the IDoc type PORDCR1 is available. The data from this IDoc automatically populates the interface parameters of the function module BAPI_PO_CREATE1.
    Functionality in Detail
    Authorization
    The following authorization objects are checked when an Enjoy purchase order is created (activity 01):
    M_BEST_BSA (document type in PO)
    M_BEST_EKG (purchasing group in PO)
    M_BEST_EKO (purchasing organization in PO)
    M_BEST_WRK (plant in PO)
    Controlling adoption of field values via X bar
    For most tables, you can determine via your own parameters in the associated X bar in each case (e.g. PoItemX) whether fields are to be set initial, values inserted via the interface, or default values adopted (e.g. from Customizing or master records) (for example, it is not mandatory to adopt the material group from an underlying purchase requisition - you can change it with the BAPI).
    Transfer
    Header data
    The header data of the Enjoy purchase order is transferred in the table PoHeader.
    Item data
    The item data of the Enjoy purchase order is stored in the table PoItem (general item data). The delivery schedule lines are stored in the table PoSchedule.
    Use the table PoAccount to specify the account assignment information. If account assignments have been specified for services and limits, you show the relevant account assignment line in PoAccount in the table PoSrvAccessValues via the package number of the service or the limit.
    Services and limits
    Services, free limits and limits with contract reference can be specified in the tables PoServices, PoLimits, and PoContractLimits.
    Conditions
    Conditions are transferred in the table PoCond; header conditions in the table PoCondHeader. Price determination is reinitiated via the parameter CALCTYPE in the table PoItem.
    Vendor and delivery address
    The vendor's address can be specified individually in the table PoAddrVendor; the delivery address in the table PoAddrDelivery. If you do not make any individual specification, the fields will be populated via the central address managementfacility.
    Note
    In this method, the following restrictions apply with regard to addresses:
    Addresses can only be created with this method - they cannot be changed. You can only change address data with the method BAPI_ADDRESSORG_CHANGE.
    When you create addresses, they are not checked by the method. An Enjoy purchase order may therefore contain faulty address data.
    Partner roles
    The partners can be maintained individually via the table PoPartner (with the exception of the partner role "vendor").
    Import/export data
    Import/Export data can be specified per item in the table PoExpImpItem. Foreign trade data can only be transferred as default data for new items.
    Texts
    Header and item texts can be transferred in the tables PoTextHeader and PoTextItem. Texts for services are imported in the table PoServicesText.
    Version Management
    You can make use of the Version Management facility via the table AllVersions.
    Return
    The PO number is returned in the parameter ExpPurchaseOrder. In addition, all information except the service and export/import tables is placed in the output structures.
    Return messages
    Messages are returned in the parameter Return. This also contains information as to whether interface data has been wrongly or probably wrongly (heuristical interface check) populated. If a PO has been successfully created, the PO number is also placed in the return table with the appropriate message.
    Example
    Example of population of BAPI interface in the Function Builder
    Parameter: POHEADER
    COMP_CODE = 1000
    DOC_TYPE = NB
    ITEM_INTVL = 00001
    VENDOR = 0000001000
    PMNTTRMS = 0001
    PURCH_ORG = 1000
    PUR_GROUP = 001
    CURRENCY = EUR
    Parameter: POHEADERX
    COMP_CODE = X
    DOC_TYPE = X
    ITEM_INTVL = X
    VENDOR = X
    PMNTTRMS = X
    PURCH_ORG = X
    PUR_GROUP = X
    Parameter: POITEM
    PO_ITEM = 00001
    MATERIAL = 100-100
    PLANT = 1000
    STGE_LOC = 0001
    QUANTITY = 15.000
    TAX_CODE = V0
    ITEM_CAT = 0
    ACCTASSCAT = K
    Parameter: POITEMX
    PO_ITEM = 00001
    MATERIAL = X
    PLANT = X
    STGE_LOC = X
    QUANTITY = X
    TAX_CODE = X
    ITEM_CAT = X
    ACCTASSCAT = X
    Parameter: POSCHEDULE
    PO_ITEM = 00001
    SCHED_LINE = 0001
    DELIVERY_DATE = 02.12.2002
    QUANTITY = 6.000
    PO_ITEM = 00001
    SCHED_LINE = 0002
    DELIVERY_DATE = 03.12.2002
    QUANTITY = 5.000
    PO_ITEM = 00001
    SCHED_LINE = 0003
    DELIVERY_DATE = 04.12.2002
    QUANTITY = 4.000
    Parameter: POSCHEDULEX
    PO_ITEM = 00001
    SCHED_LINE = 0001
    PO_ITEMX = X
    SCHED_LINEX = X
    DELIVERY_DATE = X
    QUANTITY = X
    PO_ITEM = 00001
    SCHED_LINE = 0002
    PO_ITEMX = X
    SCHED_LINEX = X
    DELIVERY_DATE = X
    QUANTITY = X
    PO_ITEM = 00001
    SCHED_LINE = 0003
    PO_ITEMX = X
    SCHED_LINEX = X
    DELIVERY_DATE = X
    QUANTITY = X
    Parameter: POACCOUNT
    PO_ITEM = 00001
    SERIAL_NO = 01
    QUANTITY = 15.000
    GL_ACCOUNT = 0000400000
    COSTCENTER = 0000001000
    CO_AREA = 1000
    Parameter: POACCOUNTX
    PO_ITEM = 00001
    SERIAL_NO = 01
    QUANTITY = X
    GL_ACCOUNT = X
    COSTCENTER = X
    CO_AREA = X
    Parameter: POCOND
    ITM_NUMBER = 000001
    COND_ST_NO = 001
    COND_TYPE = PB00
    COND_VALUE = 79.900000000
    CURRENCY = EUR
    CURRENCY_ISO = EUR
    COND_UNIT = KG
    COND_P_UNT = 1
    CHANGE_ID = U
    Parameter: POCONDX
    ITM_NUMBER =  000001
    COND_ST_NO =  000
    ITM_NUMBERX =  X
    COND_TYPE =  X
    COND_VALUE =  X
    CURRENCY =  X
    CHANGE_ID =  X
    Parameter: POPARTNER
    PARTNERDESC =  OA
    LANGU =  EN
    BUSPARTNO =  0000001100
    PARTNERDESC =  GS
    LANGU =  EN
    BUSPARTNO =  0000001200
    PARTNERDESC =  PI
    LANGU =  EN
    BUSPARTNO =  0000001000
    Help in the Case of Problems
    1. Note 197958 lists answers to frequently asked questions (FAQs). (Note 499626 contains answers to FAQs relating to External Services Management.)
    2. If you have detected an error in the function of a BAPI, kindly create a reproducible example in the test data directory in the Function Builder (transaction code SE37). Note 375886 tells you how to do this.
    3. If the problem persists, please create a Customer Problem Message for the componente MM-PUR-PO-BAPI, and document the reproducible example where necessary.
    Customer Enhancements
    The following user exits (function modules) are available for the BAPI BAPI_PO_CREATE1:
    EXIT_SAPL2012_001 (at start of BAPI)
    EXIT_SAPL2012_003 (at end of BAPI)
    The following user exits (function modules) are available for the BAPI BAPI BAPI_PO_CHANGE:
    EXIT_SAPL2012_002 (at start of BAPI)
    EXIT_SAPL2012_004 (at end of BAPI)
    These exits belong to the enhancement SAPL2012 (see also transaction codes SMOD and CMOD).
    There is also the option of populating customer-specific fields for header, item, or account assignment data via the parameter EXTENSIONIN.
    Further information
    1. Note 197958 contains up-to-date information on the purchase order BAPIs.
    2. If you test the BAPIs BAPI_PO_CREATE1 or BAPI_PO_CHANGE in the Function Builder (transaction code SE37), no database updates will be carried out. If you need this function, please take a look at Note 420646.
    3. The BAPI BAPI_PO_GETDETAIL serves to read the details of a purchase order. The BAPI cannot read all details (e.g. conditions). However, you can use the BAPI BAPI_PO_CHANGE for this purpose if only the document number is populated and the initiator has change authorizations for purchase orders.
    4. Frequently used BAPIs for purchase orders are BAPI_PO_CREATE, BAPI_PO_CREATE1, BAPI_PO_CHANGE, BAPI_PO_GETDETAIL, BAPI_PO_GETITEMS, BAPI_PO_GETITEMSREL, and BAPI_PO_GETRELINFO.
    5. For more information on purchase orders, refer to the SAP library (under MM Purchasing -> Purchase Orders) or the Help for the Enjoy Purchase Order, or choose the path Tools -> ABAP Workbench -> Overview -> BAPI Explorer from the SAP menu.
    regards
    reena

  • What are the Mandatory fields????

    Hi.... Experts...
       Please spend your valueble time for me.... I can get back to you with 10 points....
    Here I got a requirement to create contract with VA41 transaction...
    But I am in confusion with feilds which should be must record...
    Please guide me on mandatory fields of VA41 transaction....
    Thanks,
    Naveen.I

    Hi,
    When ever you want to know the required fields for any transaction just try to run the Transaction In SHDB in forgroud mode with a recording name.
    You will easily get to know the required fields to be entered for a given transaction.
    Sometimes when we run this VA41, eventhough some fields are not mandatory we dont pass them but we willnt b able to create the document eventhough some fields are not mandatory to fill> To have the clear idea abt the manadotry fields try to run in SHDB.
    for this VA41, ther mandatory fields are-
    contract type (VBAK-AUART)
    Sales Area is a combintaiotn of SAles Org, SAles divnsion, Distirbution channel hende all 3 are required to be filled.
    1st screen-
    Sales Area(VBAK-VKORG)
    Division(VBAK-SPART)
    D.Channel(VBAK-VTWEG),
    2nd screen-
    Customer code(kunnr),
    Contract validity,
    material code(matnr),
    quantity
    plant(werks).
    Best Wishes,
    Chandralekha
    Edited by: Craig Cmehil on Jun 30, 2008 11:24 AM

  • When running the ISG CreateAndMaintainSalesOrders what are the required fields?

    I keep getting the error:
    Please provide correct Organization Id
    When trying the web service call:
    CreateandMaintainSalesOrders
    Internal Name
    oracle.apps.ont.services.oexoeord.OEXOEORDServices_DocStyle
    Type
    Java
    Product
    Order Management
    I've entered on the html test form:
    OEXOEORDServices_DocStyle_Service endpoint
    For a formal definition, please review the Service Description.
    Download the JavaScript Stub (BETA) for OEXOEORDServices_DocStyle and see its documentation .
    OEXOEORDServices_DocStyle
    Operation :   updateSalesOrder
    deleteSalesOrder
    querySalesOrder
    createSalesOrder   HTML Form XML Source   
    Reliable MessagingInclude In Header 
    WS-SecurityInclude In Header
    User Name
    xsd:string
    Password
    xsd:string
    header
    Responsibility
    ORDER_MANAGEMENT_USER
    xsd:string
    Include In Message
    RespApplication
    ONT
    xsd:string
    Include In Message
    SecurityGroup
    STANDARD
    xsd:string
    Include In Message
    NLSLanguage
    AMERICAN
    xsd:string
    Include In Message
    Org_Id
    103
    xsd:string
    Include In Message
    ViewAndUpdateSalesOrderHeaderDetails 
    ViewAndUpdateSalesOrderLineDetailsInclude In Message
    SoldToPhoneAreaCode
    xsd:string
    Include In Message
    SoldToPhoneNumber
    xsd:string
    Include In Message
    SoldToPhoneCountryCode
    xsd:string
    Include In Message
    SoldTo
    xsd:string
    Include In Message
    DefaultFulfillmentSet
    xsd:string
    Include In Message
    SoldToPhoneExtension
    xsd:string
    Include In Message
    QuoteNumber
    xsd:decimal
    Include In Message
    OrderNumber
    46832
    xsd:decimal
    Include In Message
    VersionNumber
    xsd:decimal
    Include In Message
    CustomerNumber
    xsd:string
    Include In Message
    BlanketNumber
    xsd:string
    Include In Message
    ContractTemplate
    xsd:string
    Include In Message
    ContractSource
    xsd:string
    Include In Message
    AuthoringParty
    xsd:string
    Include In Message
    BlanketAgreementName
    xsd:string
    Include In Message
    OrderedDate
    xsd:date
    Include In Message
    QuoteDate
    xsd:date
    Include In Message
    SoldToContact
    xsd:string
    Include In Message
    OrderType
    Standard Sales Order
    xsd:string

    I filled in the following values:
    WS-Security Section
    User Name = SYSTEMINTEGRATION
    Password = **********
    Header Section
    Responsibility = ORDER_MANAGEMENT_USER
    RespApplication = ONT
    SecurityGroup = STANDARD
    NLSLanguage = AMERICAN
    Org_ID = 103
    Body Section
    P_API_VERSION_NUMBER = 1.0
    P_INIT_MSG_LIST = T
    P_RETURN_VALUES = T
    P_ACTION_COMMIT = T
    P_HEADER_REC
    TRANSACTIONAL_CURR_CODE = USD
    OPERATION = CREATE
    P_HEADER_VAL_REC
    ORDER_TYPE = Standard Sales Order
    *** the key was the OPERATION code being set to "CREATE".  Other valid values are DELETE and UPDATE

Maybe you are looking for