How to create UNIT info catalog

Anyone has the steps to create InfoObject catalog for info object type UNIT ?

Hi Bee, Unit info object  is SAP defined info object, which is available in Business contect.
No need to creat.
if you want to assign A unit of measure to particuler key figure while creating the key figure itself you assign "unit of measure" as "0unit".
if you want to assign a fixed measure u can select or you simp[ly metion variable in Key figure info object change screen.
Hope it will help.
Regards,
Shailaja

Similar Messages

  • How to create a product catalog in crm(by the end user of the system)?

    how can we an end user create a product catalog?
    what is the diff b/n prod cat and prod?
    we download the prod from r/3.
    how we get the prod cat done in crm for the customers and consumers and how it is done?
    thank you,

    hi
    first of all we need to look at what is catalog management before proceding with product and product catalog.
    You use this business scenario to create a centralized product catalog that contains product descriptions, multimedia objects, pricing, and associated literature. The catalog enables quick and easy customer access to timely and personalized product information, structured in such a way that most meets your customers needs.
    Product catalogs are implemented in sales processes and are of particular importance in CRM Web Channel for presenting your products in the Web shop.
    difference between the product and product catalog
    this is not the thing that product and product catalog are completely different entity.
    Product catalog :   A grouping together of products from your product master data, in a structured hierarchy.
    You use product catalogs to group together products to present them in the Web shop, Interaction Center, or in other forms of media, for example printed format or CD-ROM.
    You can create various catalogs for your products in the product master and use them according to a validity date. For example, you could use certain products for the summer season, and other products for the winter season.
    You can also tailor your product catalog to meet other needs by creating catalog variants. For example, you can create a catalog in English with the prices displayed in US Dollars.
    so by above definition it is very much clear that products are actually assign to the catalog,i will give you an analogy that museum is a kind of catalog and you add different pictures to the museum,in the same way you add product to the product catalog according to the acatlog variant.
    Now how you assign product to product catalog
    Product Assignment
    You assign products manually or automatically to a catalog area, depending on the catalog type. The product ID, product description, and status of all products is displayed, as is the information as to whether the item contains accessories or if it is a configurable product.
    Prerequisites
    You have created products in your product master in SAP CRM under Accounts and Products
    Process
    You select a catalog area in your product catalog, and edit the item list by assigning products to the area.
    Manual Assignment
    You can assign products manually on an individual basis or by copying a catalog area. You tend to choose manual product assignment for marketing-oriented catalogs that are subjected to editorial controls.
          Individual assignment
          In this case you select the catalog area in which the product should be assigned, manually search for the product in the product master, and assign it to the area.
          Copying items from catalog areas
          You select an area or subarea from another catalog and copy it to your new catalog. The system copies all products from the copied area to the new catalog, as long as they belong to the distribution chain assigned to the target catalog variant. From these products, you can then manually determine which products from the copied area you want to keep and which items you wish to delete.
    The following is true for manually assigned products:
          You can activate or deactivate items on an individual basis.
          You can edit the list of accessories for manually assigned products. The system determines which accessories are maintained for the product in the product master and displays them in the item area of the catalog. You select which accessories should be displayed for the product in the catalog and activate them.
          Manually assigned products can be included or removed from catalog views on an individual basis.
    Automatic Assignment
    You can assign products automatically to a catalog by transferring product hierarchies from your product master to the catalog areas. The categories, items, attributes, and documents contained in the product hierarchy are copied to the new catalog.
    You use automatic product assignment mainly for functional catalogs, where products can be copied with very few changes, from the product categories of the product master. It enables a standardized characterization of your products in the catalog.
    The following is true for products assigned to the catalog using product hierarchy transfer:
          Product categories which make up the hierarchies become catalog areas in the catalog.
          Product categories in the product hierarchy must be assigned to the distribution chain to which the target catalog variant is assigned. Otherwise the category is not transferred. The same applies to the items, texts, and documents assigned to the category.
          Items are always active and cannot be individually activated or deactivated.
          Accessories maintained for transferred product in the product master are automatically included and displayed in the catalog.
          Transferred items cannot be individually included in catalog views or removed from them. Instead all items of the hierarchy are always contained in the view.
          Lists of characteristics for transferred categories and items can be automatically created when transferring product hierarchies. The transferred values are included in the item overview of the product catalog.
    how to create a product catalog
    just have a look at this link
    http://help.sap.com/saphelp_crm60/helpdata/en/1c/12b2dc57d644d19ea3a5c4156f904f/frameset.htm
    your query regarding the products you have uploaded from the R3,now as above i said how you maintain and create the product catalog ,you just assign the products uploaded from the R3 to the product cataloag created in CRM.
    more detail info you can see in these links
    http://help.sap.com/saphelp_crm60/helpdata/en/91/be9642e5ef0731e10000000a1550b0/frameset.htm
    http://help.sap.com/saphelp_crm60/helpdata/en/46/27f09d25da5a68e10000000a1553f7/frameset.htm
    http://help.sap.com/saphelp_crm60/helpdata/en/46/037716cfc604a9e10000000a114a6b/frameset.htm
    if you read carefuly what i have said,it is pretty easy to implement ,you will see it yourself
    guess it will help you
    do revert back in case of any doubt
    best regards
    ashish

  • How to create a info structure for product allocation functionality

    Hi Experts,
    how to create a info structure for product allocation functionality
    For allocating fixed quantities to the specified customers at sales order
    Especially i need help in selecting the key figures and key charecterstics for at mc21 and mc24 t.codes(source feilds)
    plase provide product allocation functionality with screenhots
    thanks in advance
    rp
    Edited by: rajendraprasad vasam on May 21, 2008 2:19 PM
    Edited by: rajendraprasad vasam on May 21, 2008 2:19 PM
    Edited by: rajendraprasad vasam on May 21, 2008 2:20 PM

    Hello,
    please have a look at the infostructure S140 in transaction MC23 and MC26.
    this is the standard infostructure for product allocation.
    I hope that the information are helpful.
    Regards
    Claudia

  • HOW TO CREATE UNIT OF MEASURMENT IN SAP

    HI ALL,
    PLEASE HELP HOW TO CREATE UNIT OF MEASURMENT  IN SAP NM/S
    GIVE ME THE SCREEN SHOT OR STEPS IMM.
    THANKS
    HAPPY

    HI,
    please check the below link for creation of UOM.
    http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/create-unit-of-measure-1339786
    transaction code to create uom is CUNI and you should have an ISO code for that.
    Regards,

  • How to Create BI Beans Catalog

    I am using latest version of Oracle 10g data base, latest patch installed. All OLAP patches installed.
    I want to use JDeveloper along with BI beans. BI Beans Catalog is not created and populated with data yet. Can anyone suggest how BI Beans catalog can be created and populated.

    Please refer to the documentation provided on the BI Beans section of OTN. This explains how to create the BI Beans catalog schema.
    For populating the catalog with presentations etc please refer to the samples, white papers and viewlets posted on the BI Beans section of OTN. These will explaing everything you need to know about the BI Beans catalog and how to use it.
    Hope this helps
    Business Intelligence Beans Product Management Team
    Oracle Corporation

  • How to create a master catalog of edited images without exporting from client catalog (in DNG or JPEG).

    I create a LR catalog for each client which works great as I have many repeat clients and can easily access all of their images. However, I want to have a master studio catalog that includes the edited images from all of the
    jobs.  When I have imported these images into the master, the lightroom adjustments are lost. How can I import import the edited images showing LR adjustments?

    I can answer your question literally, exactly what you have asked.
    Or I could suggest something else, more elegant, which may address your real needs better.
    Let me do the first:
    Use the command "export as catalog" for the new delta of the current job of that repeat client. For the first job you do not need this, as the total catalog is just about the portion you want to have in your master catalog.
    Then open your master catalog and use the command "import from another catalog", select this exported portion, and you are done. But caveat: now the same image file is referenced by 2 catalogs, which may lead to,problems, e.g. If you move the image within Lightroom.
    Alternative suggestion: just work with 1 master catalog and use a collection set per each of your clients, one collection per job underneath. If appropriate, create more collections in that client's set, e.g. only for images he/she bought actually.
    So far I have not understood what an individual catalog per client gives you, what a collection (set) would not?
    Cornelia

  • How to create unit conversions and translation type

    hi,
        i need to create translation typre for unit conversion, plese provide with tcode for translation creation and table for seeing the unit conversion rates

    TCode for Unit Conversion : RSUOM
    Table: T006
    Hope this helps

  • How to Create Field Catalogs (More than one Source Table)

    Hi Data Archiving Experts,
    Could you please help me how to create the Field Catalogs (More than one Source Table). If any one is having example that will help.
    My scenario:
    Currently we are archiving on CRM Data archiving project. We are facing one issue on creating field catalog with more than one source table.
    Ex: ST -- BP1
                  BP2
                  BP3
    ST info store in one table and BP1 -- BP 3 info sotre in another table. with current field catalog we are getting ST -- BP1. Our requirment is we need to show the ST  -- BP3 How we can achive this.
    Regards,
    Srini

    Hi,
    I don't think its possible to create fieldcatalog for different tables,
    but if you want to do so create a dummy table which has all the fields which you want in fieldcatalog.
    populate the data from different table to that dummy table
    then create fieldcatalog for that table and pass it in the function module...
    Regards,
    Siddarth

  • What is Infoset and How to create

    HI Experts
    Can any one please explain me what is the purpose of INFOSET in BW
    and how to create a info Set between A Info Object and Cube
    Thanks

    Dear bw user,
    Check the below link
    http://help.sap.com/saphelp_nw04s/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
    Purpose is,
    1.To join required data from basic InfoProviders
    2.This allows building a relational BI data model with unified views for reporting (seeveral InfoProviders,but only one view). Therefore, we recommend keeping data in smaller, basic InfoProviders that can be flexibly joined for reporting purposes.
    3. To allow BEx Reporting on a DataStore object without turning the BEx Reporting indicator on
    4. To evaluate time dependencies (for example, join time dependent master data InfoObjects)
    5. To be able to create self joins and left outer joins
    Creatind in simple steps
    Infoset is a Virtual Infoprovider.
    Click on InfoProvider under modeling in RSA1 > Select InfoArea > right click Create Infoset > give name and description.
    Select the ODS / Master Data Object or more than one ODS and maintain the link.
    Infoset works on Join operation.
    you can include Infocube if it is BI 7.
    chk this link...
    http://help.sap.com/saphelp_nw70/helpdata/en/a3/96663bd194a978e10000000a11402f/frameset.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f5aa43f-0c01-0010-a990-9641d3d4eef7
    Aslo see this link contents
    Creating InfoSets
    Prerequisites
    Make sure that the objects for which you want to define the InfoSet are active. Create any required InfoObjects that do not
    exist already and activate them.
    Instead of creating a new InfoSet, you can transfer one of the InfoSets that are delivered with SAP Business Content.
    Procedure
    1. You are in the InfoProvider tree of the Modeling function area in the Administrator Workbench.
    Choose the Create InfoSet function from the context menu (right mouse-click) of the InfoArea in which you want to create an
    InfoSet. You get to the Create InfoSet dialog box.
    2. Type in the following information for your new InfoSet:
    ¡ technical name
    ¡ long description
    ¡ short description
    3. In the Start with InfoProvider section, you determine which InfoProvider you want to use to start defining the InfoSet.
    ¡ Select one of the object types that the system offers you:
    ODS Object
    InfoObject
    Choose an object.
    If you want to choose an InfoObject, it must be a characteristic with master data. The system provides you with the
    corresponding input help.
    4. Choose Continue. You get to the Change InfoSet screen. For more information on editing InfoSets see Editing InfoSets.
    When you create an InfoSet, the system generates a corresponding entry for this InfoSet in the subtree of the InfoArea. The
    following functions are available from the context menu (right mouse-click) of this entry:
    • Change
    • Delete
    • Object overview
    Editing InfoSets
    Prerequisites
    Before you can get to the screen where you edit InfoSets, the following prerequisites have to be met:
    • You have created a new InfoSet.
    • You have selected the Change function from the context menu of an InfoSet entry in the InfoProvider tree of the Modeling
    function area in the Administrator Workbench.
    • You have called the InfoSet Builder transaction, and selected the Change function. You can find additional information
    under Additional Functions in the InfoSet Builder .
    Procedure
    1. You are in the Change InfoSet screen.
    Choose a layout for the InfoProvider tree:
    InfoArea
    InfoProviders Used
    All ODS Objects
    All InfoObjects
    For more information on the screen layout, particularly the layout of the InfoProvider tree, see Screen Layout: Changing
    InfoSets.
    2. Use the function Where-Used List via AWB to determine which BW objects use the InfoSet that you have selected. You get to
    the Administrator Workbench: Where-Used List screen. You are able to work out what would happen in the system if you made
    changes to the InfoSet. This helps you to decide whether or not it is sensible to make these changes at this particular point
    in time.
    3. You define the InfoSet by inserting one or more InfoProviders into the join.
    There are several ways of inserting an InfoProvider into the join control:
    ¡ From the InfoProvider tree:
    § In the InfoProvider tree, double-click on the entry that corresponds to the InfoProvider that you want to add to the join
    control.
    § Use the drag-and-drop function to move the InfoProvider into position.
    ¡ Choose the Add InfoProvider function, to add a particular ODS object or a particular InfoObject independently of the
    current layout of the InfoProvider tree. You get to the dialog box of the same name. Enter the data that the system asks you
    for.
    If you know the technical name of the InfoProvider that you want to add, this method is quicker than switching the layout of
    the InfoProvider tree.
    When this function is complete, the InfoProvider that you selected is displayed in the join control. For more information on
    the structure of the join control, see Join Control.
    4. Define the join conditions. For more information see Defining Join Conditions.
    5. You can get general information such as object version, date created and date changed via Goto ® Global Settings. You can
    also set the indicator Most recent Reporting for InfoObjects from here. You can find additional information under Most recent
    Reporting for InfoObjects.
    6. Via the button Documents, which appears on the pushbutton bar, you can access document editing for this InfoSet.
    7. You can use Check to check the correctness of the InfoSet definition. The log display is shown in the screen area under
    the join control.
    8. Save the InfoSet. The log display is shown in the screen area under the join control.
    9. Activate the InfoSet. After activation, the system executes the checks. The result of the activation is displayed in the
    log in the screen area under the join control.
    Additional Functions in the InfoSet Builder
    You can also use transaction RSISET to call up the InfoSet Builder when you want to edit an InfoSet. Select the InfoSet that
    you want to edit. Value help is available for this. Additional functions are also available to help you edit and manage your
    InfoSet.
    Compare
    You use this function from the main menu to check if the InfoProviders used in the InfoSet have been changed and the InfoSet
    needs to be adjusted as a result. For more information, see Matching InfoSets.
    Jump to object maintenance
    You use the InfoObjects and ODS Objects functions to jump to the maintenance screen for the InfoProviders included in the
    InfoSet definition.
    Info functions
    There are various info functions on the status of the InfoSets:
    • The Object Catalog Entry
    • The log display for the save, activate, and delete runs of the InfoSet.
    Display in tree
    You use this function to display in a tree structure all the properties of the A version (active) of the selected InfoSet.
    • Header data
    • InfoProvider and its fields
    • On condition
    • Wherecondition
    The display is empty, if no active version is available.
    Version comparison
    You use this function to compare the following InfoSet versions:
    • The active (A version) and modified (M version) versions of an InfoSet
    • The active (A version) and content (D version) versions of an InfoSet
    • The modified (M version) and content (D version) versions of an InfoSet
    The Display InfoSet screen appears. Depending on which option you choose, the system displays either all of the differences
    between the two versions of the selected InfoSet or all of the properties of both versions in a tree structure.
    Transport connection using AWB
    You use this function to transport an InfoSet into another system.
    The Administrator Workbench: Transport Connection screen appears.
    The system has already collected all the BW objects that are needed to guarantee the consistency of the target system.
    InfoSet data display
    You use this function to access the data target browser. If you have already loaded data into the InfoProviders included in
    the InfoSet, you can display this data.
    Delete
    You use this function to delete an existing InfoSet.
    Copy
    You use this function to copy an existing InfoSet and, if necessary, edit it further.
    Show/hide technical names
    You can use this function to show alias names for fields. These alias names are necessary in InfoSets, for example to be able
    to map self joins. Field alias names start with F, followed by a five-digit number.
    Defining Join Conditions
    Use
    A join condition determines the combination of records from the individual objects that are included in the resulting set.
    Before an InfoSet can be activated, the join conditions have to be defined in such a way (as equal join condition) that all
    the available objects are connected to one another either directly or indirectly.
    Usually, however, only rows containing a common InfoObject or rows containing InfoObjects that share the same basic
    characteristic are connected to one another.
    Connect tables T1 and T2 using a join and set as a join condition that the F1 field from T1 must have the same value as F2
    from T2. For a record from table T1, the system determines all records from T2 for which F2(T2) = F1(T1) is true. In
    principle, as many records from T2 can be found as required. If one or more records are found, the corresponding number of
    records is included in the result set, whereby the fields from T1 contain the values from the record from T1 under
    consideration, and the fields from T2 contain the values of the records found from T2.
    Procedure
    There are various ways of defining join conditions:
    Using a mouse-click
    Position the cursor over a row in an InfoObject. Press the left mouse-button and, keeping the left mouse-button pressed down,
    trace a line between this row and a row in another object. Providing that the join condition between the two rows that you
    have indicated is a valid join condition, the system confirms the join condition by displaying a connecting line between the
    two rows.
    Using the Link Maintenance pushbutton
    You get to the Link Maintenance dialog box.
    In a tree structure on the left-hand side of the screen, all of the InfoProviders that are already included in the join are
    displayed along with their fields or attributes. If you double-click on one of these fields or attributes, the system
    displays on the right-hand side of the screen all of the fields or attributes with which you are able to create a join
    condition.
    In the Selection column, set one or more of the indicators for the fields or attributes for which you want to create a join
    condition. The system generates valid join conditions between the fields or attributes that you specify.
    You use the Delete Links pushbutton to undo all of the join conditions.
    You use the All Characteristics or the Basic Characteristics Only pushbutton to choose between the corresponding display
    variants.
    We recommend that you use the Basic Characteristics Only option. The All Characteristics setting displays all of the
    technical options involved in a join. If you are not able to find a join condition on the basic characteristic level, then
    the All Characteristics setting is useful, but this is an exceptional case.
    When you have finished making your settings, click on the Continue icon.
    We recommend this method, because the system searches for all the possible join conditions for any field or attribute that
    the user specifies, ensuring that the join conditions are defined without errors.
    Using the Context Menu Left Outer Join – Inner Join
    Usually inner-join operators connect all the objects in a join to one another. You can also connect each object with any of
    the many other objects by using a left outer join operator.
    You can find additional information about usage and special features under Left Outer Join.
    If you want to use a left-outer join operator to connect an object, select the object and choose the corresponding function
    from the context menu.
    The system displays all of the valid join conditions that originate from this object. The connecting lines that represent
    these join conditions are labeled as Left Outer Join . InfoProviders, on which a left outer join condition is affixed, are
    differentiated by color from the InfoProviders that are connected using an inner join operator.
    If you used a left outer join operator to connect two objects, you have to make sure that all on conditions are linked except
    for these two objects with the formulation of join conditions.
    Note that you cannot add an object, which you have already connected by using the left outer join operator, to another
    object.
    If you want to use an inner-join operator instead of the left-outer join operator, select the object that you want to
    connect, and choose the Inner Join option from the context menu. Again the system displays all the valid join conditions that
    originate from this object, and labels the connecting lines accordingly.
    Result
    Once the join conditions have been defined in such a way as to connect all the available objects to one another, either
    directly or indirectly, the InfoSet is ready to be activated.
    You click on the Check pushbutton in the pushbutton toolbar to find out if these preconditions for the activation have been
    met.
    For objects that are joined by a left-outer join operator, there is one extra condition that has to be met, namely that all
    the other objects have to be connected to one another either directly or indirectly.
    http://help.sap.com/saphelp_erp2004/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
    http://help.sap.com/saphelp_nw70/helpdata/en/a3/96663bd194a978e10000000a11402f/frameset.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f5aa43f-0c01-0010-a990-9641d3d4eef7
    Hope itr helps
    Regards
    Bala
    Also

  • How to create test scripts

    Hi,
    I'd like to know whether someone can advise me some white paper or documentation regarding tips about how to create unit testing procedures.
    Thanks!

    I know only one Unit testing frame work for PL/SQL, not sure whether it is useful to you or not
    http://utplsql.oracledeveloper.nl/

  • How to Create, Save and Restore a Custom Catalog in PE 6?

    I am having great difficulty in trying to create a custom catalog using the organizer function of PE 6. Upon opening the organizer I have many photos already depicted in it. So, I highlight them all and delete them obtaining a blank screen with no photos. I then import the file containing only the custom photos I want to catalog. I then backup this catalog using the following procedure http://www.backuphowto.info/how-to-backup-adobe-photoshop-elements-6-catalogue Everything looks fine until I try to restore it at a future time. It doesn't restore! In fact I can browse to the saved file but am unable to get the locate backup file location to change to it??
    What am I doing wrong and can anyone help me acheive my objective of creating a custom catalog that I can save and retrieve intact for later use?
    Thanks, in advance, for any help provided. Oh, and I need to add I am relatively new to PE 6 having only previously used PE 4 and never used the organizer in it which is to say -  lead me very simply please.
    Sanray19

    sanray19 wrote:
    I am having great difficulty in trying to create a custom catalog using the organizer function of PE 6. Upon opening the organizer I have many photos already depicted in it. So, I highlight them all and delete them obtaining a blank screen with no photos. I then import the file containing only the custom photos I want to catalog.
    I can't imagine the purpose of a "custom catalog". Seems to me you have done a lot of work when I am 100% sure there is an easier way to do whatever it is you are trying to accomplish. Further, it seems like you are trying to create a backup of only some of your photos, and I can't imagine the purpose of that either ... I would presume you would want to make backups of your entire collection of photos.
    Just as a general rule, there usually isn't a good reason to have more than one catalog (unless you have separate categories of photos, like personal and work).
    Everything looks fine until I try to restore it at a future time. It doesn't restore!
    Can you give us a detail or two about what happens when "it doesn't restore"? Can you give us more details about what you actually did? And most importantly, can you describe what you see on the screeN? Screen captures would be even better.

  • How to create field catalog using field-symbols in normal alv report?

    hi all,
    how to create field catalog using field-symbols in normal alv report? i.e, using function modules...reuse_alv_list_display/grid_display?
    regards,
    jack

    HI
    LIKE THIS
    TYPE-POOLS : slis.
    DATA : t_fieldcat TYPE slis_t_fieldcat_alv,
           st_fieldcat TYPE slis_fieldcat_alv.
    st_fieldcat-fieldname     = 'STATUS'.
      st_fieldcat-seltext_l     = 'STATUS INDICATOR'.
      st_fieldcat-outputlen     = 17.
      APPEND st_fieldcat TO t_fieldcat.
      CLEAR st_fieldcat.
      st_fieldcat-fieldname     = 'VBELN'.
      st_fieldcat-do_sum        = ' '.
      st_fieldcat-seltext_l     = 'Sales Document No.'.
      st_fieldcat-outputlen     = 10.
      APPEND st_fieldcat TO t_fieldcat.
      CLEAR st_fieldcat.
      st_fieldcat-fieldname     = 'AUDAT'.
      st_fieldcat-do_sum        = ' '.
      st_fieldcat-seltext_l     = 'Document Date'.
      st_fieldcat-outputlen     = 10.
      APPEND st_fieldcat TO t_fieldcat.
      CLEAR st_fieldcat.
      st_fieldcat-fieldname     = 'VBTYP'.
      st_fieldcat-do_sum        = ' '.
      st_fieldcat-seltext_l     = 'Document Type'.
      st_fieldcat-outputlen     = 4.
      APPEND st_fieldcat TO t_fieldcat.
      CLEAR st_fieldcat.
      st_fieldcat-fieldname     = 'AUART'.
      st_fieldcat-do_sum        = ' '.
      st_fieldcat-seltext_l     = 'Category'.
      st_fieldcat-outputlen     = 1.
      APPEND st_fieldcat TO t_fieldcat.
      CLEAR st_fieldcat.
      st_fieldcat-fieldname     = 'AUGRU'.
      st_fieldcat-do_sum        = ' '.
      st_fieldcat-seltext_l     = 'Reason'.
      st_fieldcat-outputlen     = 3.
      APPEND st_fieldcat TO t_fieldcat.
      CLEAR st_fieldcat.
      st_fieldcat-fieldname     = 'NETWR'.
      st_fieldcat-do_sum        = 'X'.
      st_fieldcat-seltext_l     = 'Net Amount'.
      st_fieldcat-outputlen     = 15.
      APPEND st_fieldcat TO t_fieldcat.
      CLEAR st_fieldcat.
      st_fieldcat-fieldname     = 'WAERK'.
      st_fieldcat-do_sum        = ' '.
      st_fieldcat-seltext_l     = 'Unit'.
      st_fieldcat-outputlen     = 5.
      APPEND st_fieldcat TO t_fieldcat.
      CLEAR st_fieldcat.
    *sortinfo
      st_sort-fieldname = 'AUART'.
      st_sort-up        = 'X'.
      st_sort-subtot    = 'X'.
      APPEND st_sort TO t_sort.
      CLEAR st_sort.
      st_sort-fieldname = 'VBTYP'.
      st_sort-up        = 'X'.
      st_sort-subtot    = ' '.
      APPEND st_sort TO t_sort.
      CLEAR st_sort.
      st_sort-fieldname = 'WAERK'.
      st_sort-up        = 'X'.
      st_sort-subtot    = 'X'.
      APPEND st_sort TO t_sort.
      CLEAR st_sort.
      st_sort-fieldname = 'VBELN'.
      st_sort-up        = ' '.
      st_sort-subtot    = 'X'.
      APPEND st_sort TO t_sort.
      CLEAR st_sort.
    CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
       EXPORTING
         i_list_type     = 0
       IMPORTING
         et_events       = it_eventcat
       EXCEPTIONS
         list_type_wrong = 1
         OTHERS          = 2.
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
      IF grid = 'X'.
        CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
         I_INTERFACE_CHECK                 = ' '
         I_BYPASSING_BUFFER                = ' '
         I_BUFFER_ACTIVE                   = ' '
          i_callback_program                = g_program
          I_CALLBACK_PF_STATUS_SET          = 'SET_PF_STATUS'
         I_CALLBACK_USER_COMMAND           = ' '
          I_CALLBACK_TOP_OF_PAGE            = 'TOP_OF_PAGE'
         I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
         I_CALLBACK_HTML_END_OF_LIST       = ' '
         I_STRUCTURE_NAME                  =
         I_BACKGROUND_ID                   = ' '
         I_GRID_TITLE                      =
         I_GRID_SETTINGS                   =
         IS_LAYOUT                         =
           it_fieldcat                       = t_fieldcat
         IT_EXCLUDING                      =
         IT_SPECIAL_GROUPS                 =
          it_sort                           = t_sort
         IT_FILTER                         =
         IS_SEL_HIDE                       =
         I_DEFAULT                         = 'X'
         I_SAVE                            = ' '
         IS_VARIANT                        =
         IT_EVENTS                         =
         IT_EVENT_EXIT                     =
         IS_PRINT                          =
         IS_REPREP_ID                      =
         I_SCREEN_START_COLUMN             = 0
         I_SCREEN_START_LINE               = 0
         I_SCREEN_END_COLUMN               = 0
         I_SCREEN_END_LINE                 = 0
         I_HTML_HEIGHT_TOP                 = 0
         I_HTML_HEIGHT_END                 = 0
         IT_ALV_GRAPHICS                   =
         IT_HYPERLINK                      =
         IT_ADD_FIELDCAT                   =
         IT_EXCEPT_QINFO                   =
         IR_SALV_FULLSCREEN_ADAPTER        =
       IMPORTING
         E_EXIT_CAUSED_BY_CALLER           =
         ES_EXIT_CAUSED_BY_USER            =
          TABLES
            t_outtab                          = it_final
          EXCEPTIONS
            program_error                     = 1
            OTHERS                            = 2
        IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
    REWARD IF USEFULL

  • I have mistakenly created two separate catalogs, one in 5.6 and one in Lightroom 5 original.  The latter is on my external drive, the former is on my hard drive. How do I merge them and upgrade the 5.0 main catalog?

    In trying to dump my Elements 10 catalog into my LR catalog, I can see I have mistakenly created a second catalog.  My main catalog is on the external drive and remains in the original 5.0 version, the "elements 10 upgraded" was imported into the 5.6 upgrade of LR and is on my hard drive.  Can you advise how I can fix this?
    Thanks in advance.
    Barb in Virginia

    OK Jim Hess, that step is done.  So on the hard drive, can I now delete:
    1. the "extra" LR catalog?
    2. the Elements 10 Catalog (which I had previously imported into one of the LR catalogs?
    That leaves me with a single catalog on an external drive.  The only question is: what about backup catalogs? how do I determine where my "new consolidated" catalog is backing up to?
    thanks in advance.

  • Is it possible to print the info. from the help window. (ex. how to create a smart list)

    is it possible to print the info. for the help window. (ex. how to create a smartlist... i tunes)

    Yes, click the gear icon and select print.

  • How to create and assign a help document to INFO button on ALV grid

    Hi All,
    Can somebody tell me how to create an 'END USER DOCUMENTATION' document and the 'FUNCTION MODULE' to call it and display in the form of F1 help screen.
    OR
    Is there any standard method to call & display a help document, when the user clicks the INFO(i) button on the ALV grid standard toolbar?
    Thanks in advance.
    Rkumar

    Hello Rkumar
    If you have defined a documentation for your ALV report which you want to display when the INFO button is pushed you can use the following coding:
    CALL FUNCTION 'DSYS_SHOW_FOR_F1HELP'           
        EXPORTING                                  
             DOKCLASS           = 'RE'                                          " = report
             DOKNAME            = '<name of your ALV report>'
             SHORT_TEXT         = 'X'              
        EXCEPTIONS                                 
             OTHERS             = 1.     
    Regards
      Uwe

Maybe you are looking for