F1 Documentation - Fields

All,
Here is the issue.
I have custom dialog application, contains 100 screens , and within these screens some of the fields don't have F1 documentation. Now i need list down all fields that don't have F1 documentation. Go each screen and check whether the fields have F1 documentation or not checking is difficult. I am looking for easier way to do this?
All fields declared in the screen are made of type DDIC fields references .

Hi a®s,
You may try to use internal statement IMPORT dynpro to get screen fields and then use i.e fm DDIF_FIELDINFO_GET (or other DD_* fm) for each field and check if F1 help applies to it.
I think it should imported like this:
  DATA: BEGIN OF L_DYNNAME,
          PROGRAM LIKE DYNPROFIELDS-PROGNAME,
          DYNPRO  LIKE DYNPROFIELDS-DYNPRO,
        END OF L_DYNNAME.
  DATA: H LIKE D020S OCCURS 0 WITH HEADER LINE,
        F LIKE D021S OCCURS 0 WITH HEADER LINE,
        E LIKE D022S OCCURS 0 WITH HEADER LINE,
        M LIKE D023S OCCURS 0 WITH HEADER LINE.
      L_DYNNAME-PROGRAM = DYNPROFIELDS-PROGNAME = DYNPROTAB-PROGRAM.
      L_DYNNAME-DYNPRO  = DYNPROFIELDS-DYNPRO  = DYNPROTAB-DYNPRO.
      IMPORT DYNPRO H F E M ID L_DYNNAME.  "F table should hold field list
Regards
Marcin

Similar Messages

  • Creating a modifiable form field

    Hi,
    I would like to create a modifiable form field that maps onto a directory server multi-valued field. This field should have the ability to add a value or remove a value as well as displaying the contents of the list. I've spent time reviewing the Workflows, Forms and Views (v8) document but it's not clear how to achieve this sort of field. Is it possible?
    Regds
    CK

    The ListEditor component is what you are looking for.
    Check out this code snippet directly from the documentation:
    <Field name='accounts[Sim1].Group'>
      <Display class='ListEditor' action='true'>
        <Property name='listTitle' value='stuff'/>
        <Property name='allowTextEntry'>
          <Boolean>true</Boolean>
        </Property>
        <Property name='ordered'>
          <Boolean>true</Boolean>
        </Property>
      </Display>
      <Expansion>
         <ref>accounts[Sim1].Group</ref>
      </Expansion>
    </Field>The important stuff in this case is the field name, in this case accounts[Sim1].Group. This means you are displaying/modifying the contents of an attribute "Group" on resource "Sim1". Change this to suit your needs.

  • Adding new Fields In Relational Model

    Hi ,
    I am brand new to the world of data modeling as well to Oracle SQL Developer DM. I am currently using version 3.0.0.665 of the data modeler. While doing the data modeling there are tables that get the data from UI screens and then there are tables which store processed data (think of them as summary tables from DWH).
    My requirement is that for the UI linked tables I need standard set of columns in relational model but I don't want to add them in my logical model as these are just technical columns. To elaborate consider this employee details screen.
    UI Screen Elements:-
    Employee Name
    Department Name
    Manager
    Salary.
    To store data from this screen I create a logical model with only 4 attributes to map my UI screen elements. In my relational model though I would need employee_id, department_id, manager_id which are not part of my UI elements. Apart from this specific requirement for employee table I have a generic requirement for all UI screen linked tables to capture the create date, create id, create screen, version number, update date, update screen and another column called deleted to indicate if the record is logically deleted or not. These additional 8 columns are not part of the logical design and should be present only in the relational domain that too for UI linked tables only.
    Any inputs in helping me out with understanding how to implement this would be greatly appreciated.
    Thanks and Regards
    Sagi

    You sound like you need to read up on entity relationship modeling first (start with Wikipedia). Also check out the SDDM videos on the Oracle site (http://www.oracle.com/technetwork/developer-tools/datamodeler/overview/index.html), and walk throught he tutorial that comes with SDDM. Logical models are not really for documenting fields that appear on a screen. It goes way beyond that.

  • Auto renewable subscription verify receipt, unexpected value in expires_date field

    During renewable IAP subscription receipt verification I need to get the end date of the latest reciept.
    Apple has documented the receipt field "expires_date" field as giving the number of milliseconds since 1 jan 1970 but it actually contains the formatted date. Apple has warned not to use undocumented fields but there is an undocumented field called "expires_date_ms" that does give a millisecond value. So i have a choice to use the undocumented field that gives the documented expected value or the documented field that gives an unexpected value. It doesn't seem like either field will be reliable. What is the solution?
    Apples documentation on receipt fields:
    https://developer.apple.com/library/ios/releasenotes/General/ValidateAppStoreRec eipt/Chapters/ReceiptFields.html#//apple…

    can you remove this from WSDL  <wsdl:definitions> tag.
    xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:cc="urn:ebay:apis:CoreComponentTypes"
    and add name="yourmessage interface" in <wsdl:definitions> tag.

  • Documentation and object-related issues

    There is no way to automatically document BRFplus rules. We are investigating into this area. Maybe as an addition to NW 703 / 731 (in an SP) we will provide some kind of report generation tool. However, as of today no commitments can be given.
    With NW 703/731 the documentation field when filled results in an icon and menu entries shown for the objects at the place of usage (e.g. expression in a rule).
    You cannot pass instances of classes as of today. What you can do with the call procedure is to call static methods and function modules. In such a method you may access any ABAP memory and return the data to BRFplus.

    What model of computer are we discussing here? 

  • Solar2 - In General documentation tab delete buttopn coming in display

    Hi
    I want to delete a document from General Documentation field. But delete buttons are showing a display. Please help

    hi
    for implementation project this all limited. if you want to edit, you can do by "copy to project documentation tab",
    The functionality for Implementation projects is limited on this tab. You can display, export, and sort documents.
    You can copy general documents into your project documentation for editing and use,
    with Copy to Project Documentation Tab. You can check to  which other structure
    elements a document is assigned with Where-Used List.
    please chk this
    [http://help.sap.com/saphelp_sm32/helpdata/EN/96/c2c83a6a860107e10000000a11402f/content.htm|http://help.sap.com/saphelp_sm32/helpdata/EN/96/c2c83a6a860107e10000000a11402f/content.htm]
    Thanks,
    Jansi

  • How to use Iden SDK with WTK 2.5.1 ?

    I have installed WTK, and it has been working but I realized I forgot to add the iden SDK for my motorola phone. I installed the SDK but I assume I need to link the files to WTK somehow?
    What I am wanting to do :
    So... I think I know what I need... I thought I had installed the iDEN SDK from Motorola, but I never did. So I installed the SDK but now I don't know how to use it with WTK. For you people proficient with this I am sure this is a simple task, but for me I am lost.
    The SDK has a class file called StatusManager which can retrieve phone battery level...
    From documentation:
    "Field Detail
    BATTERY_LEVEL
    public static final int BATTERY_LEVEL
    This is the value passed to the status manager to retrive the battery levels
    The return value is in the range of [0 - 3] with 0 being no charge and 3 being a full battery.
    BATTERY_LEVEL has a value of 0"
    QUESTION IS: Where do I put the SDK files so WTK can use them? I am lost here.
    I found the StatusManager.class file in :
    C:\Program Files\Motorola\iDEN SDK for J2ME (MIDP 2_0)\lib\i730\com\mot\iden\device\
    Can someone give me the detailed process of using the SDK with WTK... please??

    Thanks Sree.
    Is there something so called as the back-door approach to it.
    I read in the articles of Struct Objects and Connection that:
    If connection is obtained via:
    weblogic.jdbc.jts.connection jtsConn = getConnection();
    OracleConnection oracleConn = jtsConn.conn;
    And this should ideally work in WLS5.1,
    but still i wonder how did they obtain the connection.
    It would be obligatory if someone could help me with it.
    Thanks,
    Kavita
    "Sree Bodapati" <[email protected]> wrote:
    Hi Kavita,
    This is not possible to do this via a connection from the pool. Oracle
    implements non standard methods which require OracleConnection object
    instead of standard java.sql.Connection object which the pool returns.
    You
    have to use a direct connection using the thin driver.
    sree
    "Kavita Rajdeo" <[email protected]> wrote in message
    news:3c6fc1f5$[email protected]..
    The connection pool is created using the Oracle thin driver. The connection
    so obtained when passed to the ArrayDescriptor throws a
    ClassCastException at ArrayDescriptor.createDescriptor(connection con.
    While deployment,deployer throws an exception saying unresolved reference
    to
    oracle/sql/Datum, either include the class files for the same or remove
    the
    reference using the file.
    Would u kindly help me with this as urgently as possible.
    Thanking in anticipation.
    Kavita

  • Usage of BAPI BAPI_CUSTOMER_CREATEFROMDATA1

    Hi all,
    I'm thinking to use BAPI BAPI_CUSTOMER_CREATEFROMDATA1 as a call to ECC from 3rd party system.
    I found SAP Note 390045 - Usage of BAPI_CUSTOMER_* of function group V02D
    which says that the BAPI and other FMs in function group V02D is supposed to be used "exclusively for use in the SAP Online Store and the SAP Internet Sales R/3 Edition"
    So my question is if someone used this BAPI in Z* programs in SAP system system.
    If this BAPI is not used can you suggest alternative BAPI for Customer master data creation?
    Thanks.
    m./

    Hi Martin,
    from the function module documentation:
    - Fields of import parameter PI_COPYREFERENCE:
    R/3 reference customer, sales area data (sales organization,
    distribution channel, division)
    Note on reference customer:
    The reference customer should be created bearing in mind that its
    sole purpose is to provide data for customers that are created via
    the BAPI.
    That is, the reference customer is not an operative customer in the
    business sense. As a result, the customer should be created with a
    separate account group with internal number assignment. In addition,
    the reference customer must exist in the organizational data that is
    transferred to the BAPI.
    If company-code-independent data is transferred to the BAPI, the
    reference customer must be created for a company code.
    So, if you have created a reference customer already, you should know the organizational data (Org/DistrChan/Division and Company code).

  • SUCCESS WITH SOME ERRORS

    HI FRIENDS
    I AM DOING 2 SCENARIOS. ONE IS FILE TO IDOC SCENARIO AND ANOTHER ONE IS IDOC TO FILE SCENARIO.
    IN FILE TO IDOC SCENARIO I AM GETTING THE SUCCESSFUL MESSAGE IN THE SXMB_MONI BUT IT WAS GENERATING THE IDOC WITH ERROR CODE 51 i.e., IDOC NOT FULLY PROCESSED. HOW CAN I RECTIFY THAT ONE.
    IN THE SAME SCENARIO I AM USING AN XML FILE. IN THAT I AM HAVING 2 RECORDS. SO IN R3 2 IDOCS WILL BE GENERATED. BUT IT WAS GENERATING ONLY ONE IDOC. I FOLLOWED THE BLOG FROM MICHEL, STILL I AM GETTING THE SAME PROBLEM. I USING ORDINARY SCENARIO NOT BPM.
    IN THE IDOC TO FILE SCENARIO EVERYTHING IS DONE IN IR, ID. THING IS I AM NOT ABLE TO SEND THE IDOC FROM R3 TO XI. IN R3 TCODE SM58 IT SHOWS THE ERROR AS "NO SERVICE FOR THE SYSTEM SAP<SID>, CLIENT XXX IN THE INTEGRATION DIRECTORY.
    CAN ANYONE KNOWS PLEASE HELP ME..
    THANKS IN ADVANCE
    REGARDS
    VASUDEVA RAO

    Hi senthil
    My SENDER DATATYPE XSD IS
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://file.idoc" targetNamespace="http://file.idoc">
         <xsd:complexType name="dt_idoc_file_new1">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   8b9baf504a1b11dbaf8d00096bf1d97b
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="ROOT" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             f5fd248047a711db81b1f8920a646754
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:complexType>
                             <xsd:sequence>
                                  <xsd:element name="POLIST" minOccurs="0" maxOccurs="unbounded">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            f5fd248147a711db8675f8920a646754
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="HEADER" minOccurs="0" maxOccurs="unbounded">
                                                      <xsd:annotation>
                                                           <xsd:appinfo source="http://sap.com/xi/TextID">
                                                           f5fd248247a711db98ecf8920a646754
                                                           </xsd:appinfo>
                                                      </xsd:annotation>
                                                      <xsd:complexType>
                                                           <xsd:sequence>
                                                                <xsd:element name="CURRENCYID" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
                                                                     <xsd:annotation>
                                                                          <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                          f5fd248347a711dbc0e9f8920a646754
                                                                          </xsd:appinfo>
                                                                     </xsd:annotation>
                                                                </xsd:element>
                                                                <xsd:element name="TRANSDATE" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
                                                                     <xsd:annotation>
                                                                          <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                          f5fd248447a711dba57df8920a646754
                                                                          </xsd:appinfo>
                                                                     </xsd:annotation>
                                                                </xsd:element>
                                                                <xsd:element name="VENDORID" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
                                                                     <xsd:annotation>
                                                                          <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                          f5fd248547a711dbc164f8920a646754
                                                                          </xsd:appinfo>
                                                                     </xsd:annotation>
                                                                </xsd:element>
                                                                <xsd:element name="DOCUMENTTYPE" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
                                                                     <xsd:annotation>
                                                                          <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                          f5fd248647a711db8ab9f8920a646754
                                                                          </xsd:appinfo>
                                                                     </xsd:annotation>
                                                                </xsd:element>
                                                                <xsd:element name="POID" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
                                                                     <xsd:annotation>
                                                                          <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                          f5fd248747a711db9d8af8920a646754
                                                                          </xsd:appinfo>
                                                                     </xsd:annotation>
                                                                </xsd:element>
                                                           </xsd:sequence>
                                                      </xsd:complexType>
                                                 </xsd:element>
                                                 <xsd:element name="DETAILS" minOccurs="0" maxOccurs="unbounded">
                                                      <xsd:annotation>
                                                           <xsd:appinfo source="http://sap.com/xi/TextID">
                                                           f5fd248847a711dbbf09f8920a646754
                                                           </xsd:appinfo>
                                                      </xsd:annotation>
                                                      <xsd:complexType>
                                                           <xsd:sequence>
                                                                <xsd:element name="ITEMID" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
                                                                     <xsd:annotation>
                                                                          <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                          f5fd248947a711db9fa8f8920a646754
                                                                          </xsd:appinfo>
                                                                     </xsd:annotation>
                                                                </xsd:element>
                                                                <xsd:element name="QUANTITY" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
                                                                     <xsd:annotation>
                                                                          <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                          f5fd248a47a711dbb3edf8920a646754
                                                                          </xsd:appinfo>
                                                                     </xsd:annotation>
                                                                </xsd:element>
                                                                <xsd:element name="UOM" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
                                                                     <xsd:annotation>
                                                                          <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                          f5fd248b47a711db9512f8920a646754
                                                                          </xsd:appinfo>
                                                                     </xsd:annotation>
                                                                </xsd:element>
                                                           </xsd:sequence>
                                                      </xsd:complexType>
                                                 </xsd:element>
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                             </xsd:sequence>
                        </xsd:complexType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>
    and MY IDOC xsd is
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <xsd:element name="WPUWBW01">
              <xsd:complexType>
                   <xsd:sequence>
                        <xsd:element name="IDOC" type="WPUWBW.WPUWBW01" minOccurs="0" maxOccurs="9999999999" />
                   </xsd:sequence>
              </xsd:complexType>
         </xsd:element>
         <xsd:complexType name="WPUWBW01.E1WPG01">
              <xsd:annotation>
                   <xsd:documentation>
                   POS interface, inbound, goods movements, header segment
                   </xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="BELEGDATUM" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Date of Document
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="8" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="BONNUMMER" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             External reference no. (GR/I slip)
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="15" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="KASSIERER" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Cashier
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="AUTORISIER" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Authorized by
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="E1WPG02" type="WPUWBW01.E1WPG02" maxOccurs="9999999999" />
              </xsd:sequence>
              <xsd:attribute name="SEGMENT" type="xsd:string" fixed="1" use="required" />
         </xsd:complexType>
         <xsd:complexType name="WPUWBW01.E1WPG02">
              <xsd:annotation>
                   <xsd:documentation>
                   POS interface, upload goods movements, items
                   </xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="QUALVORG" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Qualifier reference transaction
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="REFERENZNR" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Number of reference transaction
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="25" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="LITEM" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Item of POS document
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="QUALARTNR" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Qualifier for following field
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="ARTNR" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Article Number
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="25" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="BEWART" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Movement Type
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="MEINH" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Sales Unit
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="MENGE" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             POS goods movement quantity
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="LIEFMENGE" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Delivery note quantity
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="WAERS" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Currency code
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="WERT" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Value
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="EXBWR" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             External Valuation Price
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="ZFILIALE" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             POS target store
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="KUNDNR" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Number
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="25" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="VERKAEUFER" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Personnel Number
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="LGORT" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Storage Location
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="CHARG" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Batch
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="LIFNR" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Vendor Number
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="SAKNR" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             G/L Account
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="KOSTL" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Cost Center
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="SOBKZ" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Special Stock Indicator
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="ELIKZ" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Delivery Completed Indicator?
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="KZBEW" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Movement Indicator
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="GRUND" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Reason for Movement
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="VFDAT" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             POS shelf-life expiration date or use-by date
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="8" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="CHECK" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Goods Movement Check
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="UMLGO" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Storage Location
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="E1WXX01" type="WPUWBW01.E1WXX01" minOccurs="0" maxOccurs="9999999999" />
              </xsd:sequence>
              <xsd:attribute name="SEGMENT" type="xsd:string" fixed="1" use="required" />
         </xsd:complexType>
         <xsd:complexType name="WPUWBW01.E1WXX01">
              <xsd:annotation>
                   <xsd:documentation>
                   Segment for Customer Enhancements to be used as Required
                   </xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="FLDGRP" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Field Group
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="5" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="FLDNAME" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Field Name
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="FLDVAL" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Field Value
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="40" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
              </xsd:sequence>
              <xsd:attribute name="SEGMENT" type="xsd:string" fixed="1" use="required" />
         </xsd:complexType>
         <xsd:complexType name="EDI_DC40.WPUWBW.WPUWBW01">
              <xsd:sequence>
                   <xsd:element name="TABNAM" type="xsd:string" fixed="EDI_DC40">
                        <xsd:annotation>
                             <xsd:documentation>
                             Table Structure Name
                             </xsd:documentation>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="MANDT" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Client
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="DOCNUM" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             IDoc Number
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="16" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="DOCREL" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             SAP IDoc Release
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="STATUS" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             IDoc Status
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="DIRECT">
                        <xsd:annotation>
                             <xsd:documentation>
                             Direction
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:enumeration value="1">
                                       <xsd:annotation>
                                            <xsd:documentation>
                                            Outbound
                                            </xsd:documentation>
                                       </xsd:annotation>
                                  </xsd:enumeration>
                                  <xsd:enumeration value="2">
                                       <xsd:annotation>
                                            <xsd:documentation>
                                            Inbound
                                            </xsd:documentation>
                                       </xsd:annotation>
                                  </xsd:enumeration>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="OUTMOD" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Output Mode
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="EXPRSS" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Overriding in Inbound Processing
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="TEST" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Test Flag
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="IDOCTYP" type="xsd:string" fixed="WPUWBW01">
                        <xsd:annotation>
                             <xsd:documentation>
                             Basic Type Name
                             </xsd:documentation>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="CIMTYP" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Enhancement (Customer-Defined)
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="30" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="MESTYP" type="xsd:string" fixed="WPUWBW">
                        <xsd:annotation>
                             <xsd:documentation>
                             Message Type
                             </xsd:documentation>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="MESCOD" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>
                             Message Variant
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="MESFCT" minOccurs="0">
      

  • Where is the best target location to put configuration files (.csv), report templates (,dotm) and instructions (.pdf) when building a LabVIEW program and installer?

    I am unsure of the best location to the above type of support files.  I would like the files to be available to all users accounts.  If I place them into something like c:\LabVIEW support files this can create an issue if manual changes are made to any of these files by a user without administrative rights.  I can also place them into public documents.  Any recomendations?
    Related.  I have added a PDF "help" file to the project. and given a path in the VI properties documentation field.  I have then added a custom runtime menu with "Help for This VI".  Running the application on my development machine, it works just fine.  Making this in an application installed on a test machine, results in the application crashing.  The PDF file is in the correct location on the target machine.  Any ideas?

    It seems you want to put the files where just any user can't get to them to edit them. Unfortunately, if the user account can't get to them, I don't think LV will be able to get to them. I could be wrong. To test this out, use a target location somewhere under your user account folder and then have another user try to run the app. if LV finds them then that gives you more options. If not, then you are going to have to have a common location that users are not likely to go to.
    I generally create a dedicated folder structure for LV apps on a target system as shown below.  I also make this the My Documents folder so that the LabView Data folder is created under this structure. Yea, it means that users can get to the files but that's where training needs to be executed.  If you are in a network environment, you can place the templates, config (ini) files, etc on a network location and users are a bit less likely to inadvertently navigate to them.
    I use both for some apps, Local folders for system specific files and Common folders on the network for files that all systems will share.
    Not sure if this will address your location issues but thought I would share it nonetheless.
    Doug
    "My only wish is that I am capable of learning each and every day until my last breath."

  • URGENT-Usage Of -BAPI_CUSTOMER_CREATEFROMDATA

    HI CONSULTANTAS,
    i have got this document(SEE BELOW) form SAP-0SSNOTES,
    1.WT DOES REALLY MEAN.
    2.<b>CAN I CALL THIS FROM REPORT PROG TO CREATE THE CUSTOMER
      OR CAN I HAVE TO USE BDC ONLY</b>
    Symptom
    This note is meant to provide an explanation of the usage of function modules BAPI_CUSTOMER_* of function group V02D.
    Other terms
    BAPI_CUSTOMER_CREATEFROMDATA, BAPI_CUSTOMER_CREATEFROMDATA1,
    BAPI_CUSTOMER_CHANGEFROMDATA, BAPI_CUSTOMER_CHANGEFROMDATA1
    BAPI_CUSTOMER_GETDETAIL, BAPI_CUSTOMER_GETDETAIL1
    BAPI_CUSTOMER_SEARCH, BAPI_CUSTOMER_SEARCH1
    BAPI, SAP Online Store, ISA, ISA-R3, ISA-R/3, consumer, create customer
    Solution
    The BAPIs of the function group V02D are intended exclusively for use in the SAP Online Store and the SAP Internet Sales R/3 Edition, that is you can create or change consumers from the SAP Online store and SAP Internet Sales R/3 Edition in the R/3 system. You cannot use them to create or change customer masters or consumers in the standard system; you can only do this using ALE or Batch Input.
    When you use the above-mentioned BAPIs outside of SAP Online Store or SAP Internet Sales R/3 Edition, or with customer master records that were created or edited outside of the SAP Online Store or SAP Internet Sales R/3 Edition, there is a danger that you will lose data.
    PLZ HELP ME
    REGARDS
    HARI

    Hi Martin,
    from the function module documentation:
    - Fields of import parameter PI_COPYREFERENCE:
    R/3 reference customer, sales area data (sales organization,
    distribution channel, division)
    Note on reference customer:
    The reference customer should be created bearing in mind that its
    sole purpose is to provide data for customers that are created via
    the BAPI.
    That is, the reference customer is not an operative customer in the
    business sense. As a result, the customer should be created with a
    separate account group with internal number assignment. In addition,
    the reference customer must exist in the organizational data that is
    transferred to the BAPI.
    If company-code-independent data is transferred to the BAPI, the
    reference customer must be created for a company code.
    So, if you have created a reference customer already, you should know the organizational data (Org/DistrChan/Division and Company code).

  • Using Requirements Gateway with LabVIEW classes

    Does anyone know how to get the NI Requirements Gateway to read coverage information from the documentation contained in a LabVIEW class (.lvclass)?
    Requirements Gateway appears to load the documentation content fine from VIs, controls, .llb, .lvlib, .lvproj etc, but not .lvclass? My LabVIEW keeps crashing out when I try to point Requirements Gateway at a project with .lvclass files!
    If this can't be done then is there a neat way to add requirements coverage information (you know, the "Covers: ID" field) into the class properties, or something near the class maybe, that Requirements Gateway can read?
    Thoric (CLA, CLED, CTD and LabVIEW Champion)
    Solved!
    Go to Solution.

    Hi Manooch,
    Thank you for your prompt reply. The example you attached, with a little alteration to include the coverage ID tag in the class documentation field, does precisely what I need, thank you. The snapshot below shows the LabVIEW class satisfying requirement 2:
    However, this doesn't work in my project. I have similar content, and when I ask Requirements Gateway to analyse the project it shows nothing and then LabVIEW crashes! I'll have to try stripping my project down to the bare bones to find the problematic element. I hate it when this happens....
    Thoric (CLA, CLED, CTD and LabVIEW Champion)

  • Maximum Row Count - dynamically change

    Hi,
    How can I change dynamically (eg. from some item) value "Maximum Row Count" in "Report Attributes -> Layout and Pagination"?
    Is this possible?
    best regards,
    Jarek

    Thank you for your answer, but I want to do something else.
    I want to show all rows from my query in report with pagination.
    The number of rows increases.
    According to documentation, field "Number of Rows" sets the number of rows which I can see on one page and field "Maximum Row Count" sets the maximum number of rows which I can see on all pages (number of rows to query).
    I thougth, that when I set (before page is shown) a variable from eg. query "SELECT count(*) FROM table", I will be able to put this variable name in "Maximum Row Count" field, to see all rows from my query. However this field is the numeric field and I can't put any variable name there :(
    The only way to always show all records from my query is to set "Maximum Row Count" field to very high number? Is this natural way in apex? Is this only way?
    best regards,
    Jarek

  • How to edit the WSDL

    I noticed a few limitations of an automatically generated web service
    under WLS 7.0, and I am wondering if there is a way to manually edit
    files to overcome these limitations:
    - the parameter names have no meaningful names, such as string0,
    string1, etc. This needs to be changed to at least use the names given
    to the parameters in the EJB. I remember putting in a CR a while back,
    but this has not been implemented yet.
    - The documentation field says 'todo'. It would be nice to be able to
    add some explanatory text there.
    I looked for the WSDL file in the web-services.war file but could not
    find it. Any pointers as to whether/how this stuff can be edited?
    Thanks,
    Joop Kaashoek

    Indeed, you can do this. But if you have non-built in data types as paramaters
    it gets pretty tricky.
    manoj cheenath wrote:
    You can change the parameter/operation name in the generated
    WSDL file by editing the web-services.xml file in the web-inf dir
    (inside the war file). This file is generated by servicegen, but can
    replaced before deploying the service.
    regards,
    -manoj
    "Joop Kaashoek" <[email protected]> wrote in message
    news:[email protected]...
    Hi Mike,
    Thanks very much for your help, I have sent a request to '[email protected]'.
    Regards,
    Joop
    Michael Wooten wrote:
    Hi Joop,
    I see. No, I don't work in "development" or have any knowledge of what
    features are
    going to be in the product. I work in the "services" (i.e. professionalservices)
    division, which is primarily tasked with figuring out (and showingothers) how the
    stuff works :-)
    Individuals from "development" (i.e. product managers, developers,architects, etc.)
    do monitor this newsgroup, so I think you should create another postthat has a subject
    like "Need static or JSP-based WSDL added back to .war". The subject forthis current
    post, sounded like you wanted to know how to edit the WSDL (which Ithink I answered
    to your satisfaction), but it sounds like you really just want acapability that
    was in WLS 6.1, back in WLS 7.0 :-)
    I'm assuming that you already know that you can extract the "static"WSDL from the
    client.jar and put it anywhere in the .war, you like. The context rootwill be the
    name of the .war file, without the file extension. For instance, if your.war file
    is hello.war, the context root will be hello. If you then put the"static" WSDL (which
    you extracted from the client.jar), into the root directory for for thisWeb Application,
    the URL to it would be something like:
    http://localhost:7001/hello/HelloService.wsdl
    Regards,
    Mike Wooten
    Joop Kaashoek <[email protected]> wrote:
    Your explanation makes sense, but the implementation does not make
    sense
    to me. This should
    clearly be on the list of things to fix. Our partners use .NET or other
    technologies, we
    want to be able to publish a meaningful self-documented WSDL document(with
    meaningful
    parameter names and documentation) on our server, not as part of aweblogic-specific
    Java
    client jar.
    Can you indicate whether this is being worked on?
    Regards,
    Joop
    Michael Wooten wrote:
    Hi Joop,
    The assumption here, is that the client will download your client.jar(or whatever
    you named it in your <clientgen> Ant task), and use a file:// URL to
    access
    it (the
    "persisted" WSDL file) from within this archive :-)
    If you use the Web Services Technology Stack from BEA
    (lib\webserviceclient.jar)
    on the client-side, editing this file affects the construction of theSOAP message
    that is sent to the Web service, which I'm assuming is hosted on an
    instance
    of WLS
    7.0. The names for the input parameters (and return value), will be
    set
    to those
    that you specified in this WSDL, which is one of the things you said
    you
    wanted to
    be able to do.
    If you don't use the Web Services Technology Stack from BEA on the
    client-side,
    there
    is still a very high probability that the WSDL processor of the tool
    you
    use, will
    use this WSDL to create the SOAP message sent to your web service,
    which
    again is
    assumed to be hosted on an instance of WLS 7.0.
    If you use the "dynamically generated" WSDL (as opposed to the one inthe client.jar),
    you will get the "generic" parameter names specified in it. The
    "dynamically
    generated"
    WSDL is accessed by concatenating "?WSDL" to the location attribute,
    of
    your <service>
    element.
    Make sense?
    Regards,
    Mike Wooten
    Joop Kaashoek <[email protected]> wrote:
    Mike,
    How can editing this client file make any difference to the web
    service
    itself?
    Joop
    Michael Wooten wrote:
    Hi Joop,
    The "persisted" WSDL file is in the .jar file, for the client ;-)
    The name of this .jar file is set using either of the following:
    1. The clientJarName attribute, of the <client> sub-element for
    your
    <servicegen>
    task, or
    2. The clientJar attribute, of the <clientgen> task.
    The path leading to the .wsdl file, is determined by the value youassign
    to the
    packageName attribute (in either of the above tasks).
    Regards,
    Mike Wooten
    Joop Kaashoek <[email protected]> wrote:
    I noticed a few limitations of an automatically generated web
    service
    under WLS 7.0, and I am wondering if there is a way to manuallyedit
    files to overcome these limitations:
    - the parameter names have no meaningful names, such as string0,
    string1, etc. This needs to be changed to at least use the namesgiven
    to the parameters in the EJB. I remember putting in a CR a whileback,
    but this has not been implemented yet.
    - The documentation field says 'todo'. It would be nice to beable
    to
    add some explanatory text there.
    I looked for the WSDL file in the web-services.war file but couldnot
    find it. Any pointers as to whether/how this stuff can be edited?
    Thanks,
    Joop Kaashoek

  • How can we modify alv output list

    Hi
    this is fazil.
    Please tell me any body How can we modify alv output list.
    Thanks & Regards
    Fazil
    [email protected]

    Fazil,
    check the program,
    You can find the code in this program 'BCALV_FIELDCAT_TEST'
    *& Report  BCALV_FIELDCAT_TEST                                         *
    This report allows to modify the fieldcatalog of a corresponding
    output table and to view the effects of your changes directly.
    Note that for some changes you need to newly display the whole
    ALV Grid Control, e.g., DDIC-Fields are read only the first time
    you call SET_READY_FOR_FIRST_DISPLAY.
    Note also that not all scenarios can be tested since the output
    table does not comprise all fields to test available features
    of the fieldcatalog. Copy this program and extend the output
    table accordingly if you want to test such a special feature.
    (The field CARRNAME in 'gt_sflight' was added to test field REF_FIELD
    and TXT_FIELD of the fieldcatalog - see what happens if you
    calculate subtotals by carrier-id).
    report  bcalvt_fieldcatalog           .
    data: ok_code               type sy-ucomm,
          save_ok_code          type sy-ucomm,
    fieldcatalog for output table
          gt_fieldcat           type lvc_t_fcat,
    fieldcatalog for fieldcatalog itself:
          gt_fcatfcat           type lvc_t_fcat,
          gs_fcatlayo           type lvc_s_layo.
    Output table
    data: begin of gt_sflight occurs 0.
    data: carrname type s_carrname.
            include structure sflight.
    data: end of gt_sflight.
    data: g_max type i value 100.
    data: g_all type c value SPACE.
    Controls to display gt_sflight and corresponding fieldcatalog
    data: g_docking type ref to cl_gui_docking_container,
          g_alv     type ref to cl_gui_alv_grid.
    data: g_custom_container type ref to cl_gui_custom_container,
          g_editable_alv     type ref to cl_gui_alv_grid.
    LOCAL CLASS Definition
    class lcl_event_receiver definition.
      public section.
        methods handle_data_changed
          for event data_changed of cl_gui_alv_grid
          importing er_data_changed.
    endclass.
    class lcl_event_receiver implementation.
      method handle_data_changed.
    at the time being, no checks are made...
      endmethod.
    endclass.
    data: event_receiver type ref to lcl_event_receiver.
    end-of-selection.
      set screen 100.
    *&      Module  STATUS_0100  OUTPUT
          text
    module status_0100 output.
      set pf-status 'BASIC'.
      set titlebar 'BASICTITLE'.
    create ALV Grid Control in the first run
      if g_docking is initial.
        perform create_and_init_controls.
      endif.
    endmodule.                             " STATUS_0100  OUTPUT
    *&      Module  USER_COMMAND_0100  INPUT
          text
    module user_command_0100 input.
      save_ok_code = ok_code.
      clear ok_code.
      case save_ok_code.
        when 'SUBMIT'.
    set the frontend fieldcatalog
    ATTENTION: DDIC-Fields are not updated using this method!
    (see 'RESTART')
          call method g_alv->set_frontend_fieldcatalog
               exporting
                 it_fieldcatalog = gt_fieldcat.
          call method g_alv->refresh_table_display.
          call method cl_gui_cfw=>flush.
        when 'RESTART'.
    Destroy the control currently visible and display it again
    using the changed fieldcatalog.
          perform restart_sflight.
        when '&ALL'.
          perform switch_visibility.
      endcase.
    endmodule.                             " USER_COMMAND_0100  INPUT
    *&      Form  CREATE_AND_INIT_CONTROLS
          text
    -->  p1        text
    <--  p2        text
    form create_and_init_controls.
      create object g_docking
          exporting
               dynnr = '100'
               extension = 150
               side = cl_gui_docking_container=>dock_at_bottom.
      create object g_alv
          exporting
               i_parent = g_docking.
      create object g_custom_container
          exporting
               container_name = 'CC_0100_FIELDCAT'.
      create object g_editable_alv
          exporting
               i_parent = g_custom_container.
    register events
      create object event_receiver.
      set handler event_receiver->handle_data_changed for g_editable_alv.
      call method g_editable_alv->register_edit_event
                    exporting
                       i_event_id = cl_gui_alv_grid=>mc_evt_modified.
      perform build_fieldcatalogs changing gt_fieldcat gt_fcatfcat.
      perform modify_fieldcatalog changing gt_fcatfcat.
      perform select_data.                 "CHANGING gt_sflight
      call method g_alv->set_table_for_first_display
              changing
                   it_outtab       = gt_sflight[]
                   it_fieldcatalog = gt_fieldcat[].
    optimize column width of grid displaying fieldcatalog
      gs_fcatlayo-cwidth_opt = 'X'.
    Get fieldcatalog of table sflight - alv might have
    modified it after passing.
      call method g_alv->get_frontend_fieldcatalog
                importing et_fieldcatalog = gt_fieldcat[].
      call method cl_gui_cfw=>flush.
    Display fieldcatalog of table sflight:
      call method g_editable_alv->set_table_for_first_display
              exporting
                   is_layout       = gs_fcatlayo
              changing
                   it_outtab       = gt_fieldcat[]
                   it_fieldcatalog = gt_fcatfcat[].
    register events
      create object event_receiver.
      set handler event_receiver->handle_data_changed for g_editable_alv.
    endform.                               " CREATE_AND_INIT_CONTROLS
    *&      Form  restart_sflight
          text
    -->  p1        text
    <--  p2        text
    form restart_sflight.
      data: ls_fieldcat type lvc_s_fcat.
    free g_docking and thus g_alv
      call method g_docking->free.
      clear g_docking.
      clear g_alv.
    create new instances
      create object g_docking
          exporting
               dynnr = '100'
               extension = 150
               side = cl_gui_docking_container=>dock_at_bottom.
      create object g_alv
          exporting
               i_parent = g_docking.
    This is an internal method to invalidate all fields in the fieldcat
      loop at gt_fieldcat into ls_fieldcat.
        clear ls_fieldcat-tech_comp.
        modify gt_fieldcat from ls_fieldcat.
      endloop.
    Newly display the list with current fieldcatalog.
      call method g_alv->set_table_for_first_display
              changing
                   it_outtab       = gt_sflight[]
                   it_fieldcatalog = gt_fieldcat.
    Get fieldcatalog - it might be changed by ALV in the last call
      call method g_alv->get_frontend_fieldcatalog
              importing
                   et_fieldcatalog = gt_fieldcat[].
      call method g_editable_alv->refresh_table_display.
      call method cl_gui_cfw=>flush.
    endform.                               " restart_sflight
    *&      Form  select_data
          text
    -->  p1        text
    <--  p2        text
    form select_data.
      data: lt_sflight type table of sflight with header line,
            ls_scarr type scarr.
    select data of sflight
      select * from sflight into table lt_sflight up to g_max rows.
    copy data to gt_sflight and update CARRNAME
      loop at lt_sflight.
        move-corresponding lt_sflight to gt_sflight.
        select single * from scarr into ls_scarr
           where carrid = gt_sflight-carrid.
        gt_sflight-carrname = ls_scarr-carrname.
        append gt_sflight.
      endloop.
    endform.                               " select_data
    *&      Form  BUILD_FIELDCATALOGS
          text
         <--P_GT_FIELDCAT  text
         <--P_GT_FCATFCAT  text
    form build_fieldcatalogs changing p_fieldcat type lvc_t_fcat
                                      p_fcatfcat type lvc_t_fcat.
      data: ls_fcat     type lvc_s_fcat.
    Fieldcatalog for table SFLIGHT: p_fieldcat
    generate fieldcatalog automatically
      call function 'LVC_FIELDCATALOG_MERGE'
          exporting
               i_structure_name       = 'SFLIGHT'
            I_CLIENT_NEVER_DISPLAY = 'X'
           changing
                ct_fieldcat            = p_fieldcat[]
       EXCEPTIONS
            INCONSISTENT_INTERFACE = 1
            PROGRAM_ERROR          = 2
            OTHERS                 = 3
      if sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      endif.
    shift all column positions to the right except for MANDT
      loop at p_fieldcat into ls_fcat.
        if ls_fcat-fieldname ne 'MANDT'.
          add 1 to ls_fcat-col_pos.
          if ls_fcat-fieldname = 'CARRID'.
            ls_fcat-txt_field = 'CARRNAME'."link CARRNAME to CARRID
          endif.
          modify p_fieldcat from ls_fcat.
        endif.
      endloop.
    create a new line for CARRNAME in p_fieldcat
      clear ls_fcat.
      ls_fcat-fieldname = 'CARRNAME'.
      ls_fcat-ref_table = 'SCARR'.
      ls_fcat-col_pos = 1.
    insert new line before CARRID (do not forget MANDT!).
      insert ls_fcat into p_fieldcat index 1.
    Fieldcatalog for table LVC_T_FCAT:p_fcatfcat
    Generate fieldcatalog of fieldcatalog structure.
    This fieldcatalog is used to display fieldcatalog 'p_fieldcat'
    on the top of the screen.
      call function 'LVC_FIELDCATALOG_MERGE'
          exporting
               i_structure_name       = 'LVC_S_FCAT'
            I_CLIENT_NEVER_DISPLAY = 'X'
           changing
                ct_fieldcat            = p_fcatfcat[]
       EXCEPTIONS
            INCONSISTENT_INTERFACE = 1
            PROGRAM_ERROR          = 2
            OTHERS                 = 3
      if sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      endif.
    Hide all fields that are not documented (valid for release 4.6A)
      perform hide_fields changing p_fcatfcat.
    endform.                               " BUILD_FIELDCATALOGS
    *&      Module  EXIT_PROGRAM  INPUT
          text
    module exit_program input.
      leave program.
    endmodule.                             " EXIT_PROGRAM  INPUT
    *&      Form  MODIFY_FIELDCATALOG
          text
         <--P_GT_FCATFCAT  text
    form modify_fieldcatalog changing p_fcatfcat type lvc_t_fcat.
      data ls_fcat type lvc_s_fcat.
      loop at p_fcatfcat into ls_fcat.
        ls_fcat-coltext = ls_fcat-fieldname.
        ls_fcat-edit = 'X'.
        if ls_fcat-fieldname = 'COL_POS' or ls_fcat-fieldname = 'FIELDNAME'.
          ls_fcat-key = 'X'.
        endif.
        modify p_fcatfcat from ls_fcat.
      endloop.
    endform.                               " MODIFY_FIELDCATALOG
    form hide_fields changing p_fieldcat type lvc_t_fcat.
      data: ls_fcat type lvc_s_fcat.
    Only show documented fields of fieldcatalog.
    For a documentation choose "Help->Application Help" in the menu.
      loop at p_fieldcat into ls_fcat.
        if not (
             ls_fcat-fieldname eq 'CFIELDNAME'
        or   ls_fcat-fieldname eq 'COL_POS'
        or   ls_fcat-fieldname eq 'COLDDICTXT'
        or   ls_fcat-fieldname eq 'COLTEXT'
        or   ls_fcat-fieldname eq 'CURRENCY'
        or   ls_fcat-fieldname eq 'DD_OUTLEN'
        or   ls_fcat-fieldname eq 'DECIMALS_O'
        or   ls_fcat-fieldname eq 'DECMLFIELD'
        or   ls_fcat-fieldname eq 'DO_SUM'
        or   ls_fcat-fieldname eq 'DRAGDROPID'
        or   ls_fcat-fieldname eq 'EDIT_MASK'
        or   ls_fcat-fieldname eq 'EMPHASIZE'
        or   ls_fcat-fieldname eq 'EXPONENT'
        or   ls_fcat-fieldname eq 'FIELDNAME'
        or   ls_fcat-fieldname eq 'HOTSPOT'
        or   ls_fcat-fieldname eq 'ICON'
        or   ls_fcat-fieldname eq 'INTLEN'
        or   ls_fcat-fieldname eq 'INTTYPE'
        or   ls_fcat-fieldname eq 'JUST'
        or   ls_fcat-fieldname eq 'KEY'
        or   ls_fcat-fieldname eq 'LOWERCASE'
        or   ls_fcat-fieldname eq 'LZERO'
        or   ls_fcat-fieldname eq 'NO_OUT'
        or   ls_fcat-fieldname eq 'NO_SIGN'
        or   ls_fcat-fieldname eq 'NO_SUM'
        or   ls_fcat-fieldname eq 'NO_ZERO'
        or   ls_fcat-fieldname eq 'OUTPUTLEN'
        or   ls_fcat-fieldname eq 'QFIELDNAME'
        or   ls_fcat-fieldname eq 'QUANTITY'
        or   ls_fcat-fieldname eq 'REF_FIELD'
        or   ls_fcat-fieldname eq 'REF_TABLE'
        or   ls_fcat-fieldname eq 'REPREP'
        or   ls_fcat-fieldname eq 'REPTEXT'
        or   ls_fcat-fieldname eq 'ROLLNAME'
        or   ls_fcat-fieldname eq 'ROUND'
        or   ls_fcat-fieldname eq 'ROUNDFIELD'
        or   ls_fcat-fieldname eq 'SCRTEXT_L'
        or   ls_fcat-fieldname eq 'SCRTEXT_M'
        or   ls_fcat-fieldname eq 'SCRTEXT_S'
        or   ls_fcat-fieldname eq 'SELDDICTXT'
        or   ls_fcat-fieldname eq 'SELTEXT'
        or   ls_fcat-fieldname eq 'SP_GROUP'
        or   ls_fcat-fieldname eq 'SYMBOL'
        or   ls_fcat-fieldname eq 'TECH'
        or   ls_fcat-fieldname eq 'TIPDDICTXT'
        or   ls_fcat-fieldname eq 'TOOLTIP'
        or   ls_fcat-fieldname eq 'TXT_FIELD' ).
          ls_fcat-tech = 'X'.
        endif.
        modify p_fieldcat from ls_fcat.
      endloop.
    endform.
    form switch_visibility.
    data:  lt_fcatfcat type lvc_t_fcat,
            ls_fcat type lvc_s_fcat.
    call method g_editable_alv->get_frontend_fieldcatalog
                 importing ET_FIELDCATALOG = lt_fcatfcat.
    if not g_all is initial.
         perform hide_fields changing lt_fcatfcat.
         g_all = SPACE.
    else.
        loop at lt_fcatfcat into ls_fcat.
           if ls_fcat-tech eq 'X'.
               ls_fcat-tech = SPACE.
               ls_fcat-no_out = 'X'.
               modify lt_fcatfcat from ls_fcat.
           endif.
        endloop.
        g_all = 'X'.
    endif.
    call method g_editable_alv->set_frontend_fieldcatalog
                exporting it_fieldcatalog = lt_fcatfcat.
    call method g_editable_alv->refresh_table_display.
    endform.
    Don't forget to rewaard if useful..

Maybe you are looking for

  • Printing Month View in the Normal 8x11 View

    This was a HUGE problem in the past and hoping it may be better. Have never been able to print any of the iCal views in the "tall" 8x11 view. iCal only prints in the "wide" "11x8" view. There were a few pain in the neck work-arounds and I am hoping t

  • How do you create array of enums for transitions in a state machine?

    Hello, I am trying to build a state machine, but, I am struggling with understanding the methods for determining which state to transition to next.  In other words, I have several states, but, I don't want to go in any particular sequence.  If I have

  • Keeping music from another persons itunes library

    I got a 30G video ipod for christmas, and I used my sisters itunes to put some of her music on it while I was home from school. Now i'm back at school on my computer and itunes is telling me if i want to link my ipod to MY itunes library, it will rep

  • Selcect/ update attribute value using xpath navigator/ linq to xml

    Hi Folks, below is my xml string and the highlighted bold attribute value needs to update. Since this element contains prefix im not able to select teh particular element. if i remove the prefixx im able to select but i need to keep prefix.     <IOP:

  • Exciting LabVIEW Development role in Calgary, Alberta, CANADA

    Exciting LabVIEW Development position Available – Calgary, Alberta, Canada Want to work for a Great company that truly values it’s employees?  This is a highly respected oil and gas services company that offers a Corporate Culture second to none.  We