What is the use of GUI status in Dialog programming

what is the use of GUI status in Dialog programming,, how can it be used there,, as screen are alredy defined..

Hi,
The use of GUI Status is that when we have to change some thing in Menu Bar, Toolbar and Function Keys. Say For Example we have to create any Custom Button in the application toolbar etc.
It can be used in Dialog Programming via defining the Status in the PBO module of the screen.
eq. created a screen 9000
          on clicking it->
                               PROCESS BEFORE OUTPUT.
                                         MODULE status_9000.
On double clicking on this "Module status_9000" - you can write "SET PF-STATUS 'STATUS_9000'".
Now u can create GUI staus with name "'STATUS_9000'".
Let me know in case you have any further doubts.
Thanks

Similar Messages

  • What is the use of "#ec *  in a abap program

    Hi,
    i want to know that is the use of "#ec *  in an abap program.
    i heard that it is used to supress the warning messages which we get when we do extended syntax check.
    fist of all i want to know is it true r false and if its true then i want to know more about it.
    regards,
    maqsood

    Hi
    Yes it's true.
    If you put "#ec * at the end of a abap code row, you can suppress the warnining messages of extended program check.
    Every kind of warning has own sign, you find out them while running extended check.
    It's a way to clear the useless messages.
    For example, you have created an include where you have defined several routines you have to use in several programs, but every program don't use all routines of that include, or you dynamically call those routines, so if you run the extend check for a certain program you can get a warning like that:
    FORM PLUTO not called directly
    Now you can't delete the routine from the include, because it can be used by other program, but you can hide that message by "#ec CALLED:
    FORM <MY_FORM>. "#EC CALLED
    ENDFORM.
    Max

  • What is the use of Withholding tax identification number field?

    Hello SAP Experts,
    I posted this question earlier but had to close because of no replies from anybody. Posting it again to see if I am lucky to get some answer this time.
    Can someone tell what is the use of field Withholding Tax Identification Number? Does it help with the reporting? Where does it get populated on the report if given at vendor or master record or within the withholding tax customization for company code? What is the difference between creating it in the customization for withholding tax information for company code and vendor/customer master record?
    As per SAP:  Withholding tax identification number
    This is a number issued by the tax authorities per withholding tax type.
    This number must be specified in Customizing either:
    (a) As part of the withholding tax information defined for the company code, or
    (b) As part of the withholding tax information defined in the customer or vendor master record.

    Hi Pete,
    The only thing that I could check is the content used in US:
    See content of this field for US:
    LFA1-STCD1      Social security number
    LFA1-STCD2      Employer identification number
    LFBW-WT_WTSTCD  Withholding tax identification number for WT Type
    In order to populate it, please kindly check the following:
    The reason why you cannot fill in the field WT_WTSTCD in transaction
    Fk02 however you can do it in XK02 (Change vendor centrally) can be due
    to wrong customizing of the field status group.
    Kindly check the following:
    SPRO->
    Finantial accounting -> Accounts receivable and accounts payable ->
    Define screen layout per activity (vendors) -> Change Vendor(Accounting)
    Company code data -> W/holding tax data, w/h tax 2 ->
    FIELD Withholding tax code,w/h tax 2 will be probably just available to
    display. Please, change it to optional entry.
    I hope I could be of assistance.
    Kind Regards,
    Fernando Evangelista

  • What is the use of 'ALTER DATABASE CLOSE'?

    Hello Everybody,
    SQL*Plus: Release 10.1.0.2.0 - Production on Ma Aug 15 21:28:30 2005
    Copyright © 1982, 2004, Oracle. All rights reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL> conn / as sysdba
    Connected.
    SQL> startup force
    ORACLE instance started.
    Total System Global Area 171966464 bytes
    Fixed Size 787988 bytes
    Variable Size 145750508 bytes
    Database Buffers 25165824 bytes
    Redo Buffers 262144 bytes
    Database mounted.
    Database opened.
    SQL> select status from v$instance;
    STATUS
    OPEN
    SQL> alter database close;
    Database altered.
    SQL> select status from v$instance;
    STATUS
    MOUNTED
    SQL> alter database open;
    alter database open
    ERROR at line 1:
    ORA-16196: database has been previously opened and closed
    If i have to shutdown the instance and database then
    WHAT IS THE USE OF 'ALTER DATABASE CLOSE' ?
    I need explanation. Why should i shutdown?
    Dont give me this answer.
    ORA-16196: database has been previously opened and closed
    Cause: The instance has already opened and closed the database, which is allowed only once in its lifetime.
    Action: Shut down the instance.

    If you read the documentation you will see that there is no ALTER DATABASE CLOSE command.
    This is an undocumented Oracle command, which we are not supposed to use. Consequently we are not allowed to complain about the way that it works. Instead we're supposed to use SHUTDOWN IMMEDIATE.
    Cheers, APC

  • What is the use of access level

    Hi Experts,
    What is the access level and what is use of each option in access level
    1  Application
    2  Superior component
    3. Top Component
    4. Sap
    5. Global
    and in Details section what is the use Properties tab
    1. Application Component
    2. Software Component
    3. Development Package
    4. Settings Class
    Please explain Each option use.
    Thank you in advance,
    Srini M.

    Hi Srini,
    just read the documentation (although the current status on SAP Help Portal isn't really up-to-date):
    1. [Entry point|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/cc/85414842c8470bb19b53038c4b5259/frameset.htm]
    2. [Setting an Access Level|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/32/6aba9c49fd41a5a14f710e121220f1/content.htm]
    W/r to "Application Component" etc., docu on Help Portal is definitely not sufficient. Here, the following applies:
    An application offers attributes for the application component and the software component. The application component and software component have to be the same as defined for the development package. Application and software component are automatically derived from the development package if they are not set explicitly.
    For the definition of the development package, application component, and software component, we recommend that you choose the same values that are in effect for the software solution that you want to enhance by a new BRFplus application. This simplifies all activities related to the software infrastructure, especially transports.
    CU
    Claus

  • What is the Use of  "Alter database activate standby database"

    Hi ,
    I appreciate your time.
    I just wanted to know what is the use of "Alter database activate standby database" command when doing the failover. How different it will act in failover process. Can we use this command in SwitchOver.
    Thanks in advance.

    Hi Uwe Hesse,
    Wonderfull... good info....
    So my understanding is that the use of "ACTIVATE PHYSICAL STANDBY DATABASE" is conditional and depends on the redo log gap and the Database status(Able to mount or not).
    Condition 1: If the Db is in Mount state and Redo log gap is successfully filled.
    1) Flush any unsent redo from the primary database to the target standby database.
    SQL> ALTER SYSTEM FLUSH REDO TO target_db_name;
    Note: If the above Statement Completes successfully without any errors.
    2) Stop Redo Apply.
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    3) Finish applying all received redo data.
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH;
    4) Verify that the target standby database is ready to become a primary database.
    SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
    5) Switch the physical standby database to the primary role.
    SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WITH SESSION SHUTDOWN;
    Condition 2: If the DB is not able Mount and Redo Gap can't be filled.
    Important Note: If the the above command in STEP3 gives error, some received redo data was not applied. Try to resolve the cause of the error and re-issue the statement before proceeding.
    If the error condition cannot be resolved, a failover can still be performed (with some data loss) by issuing the following SQL statement on the target standby database:
    SQL> ALTER DATABASE ACTIVATE PHYSICAL STANDBY DATABASE;
    Thanks in advance.

  • What is the use of OASV transaction in Asset accounting

    Dear Experts,
    Could you please advise me clearly what is the use of OASV transaction in Asset accounting and which GL account we need to use for debit and credit while using this t code. Can you please provide me along with examples for better understand and that would be great for me.
    Thanks in Advance,
    Murali

    Transfer Balances
    In this step you can post balances to G/L accounts which have already   been defined as reconciliation accounts. You can only post these   corrections in company codes which have implementation status.
         The transfer of legacy asset data using the legacy asset transaction  does not affect the balances of the corresponding reconciliation  accounts in Financial Accounting. Therefore no automatic balance formation or reconciliation takes place and you will need to manually  reconcile the balances. You can ascertain the Asset Accounting values  using of the asset list. When you start this report, specify January 1st  of the current fiscal year as the report date. The system will then  provide data as of December 31st of the previous fiscal year (in other words, no depreciation from the current fiscal year is included).
    Activities
    Copy the balances from any suspense accounts to the Asset Accounting  reconciliation accounts.

  • What is the Successfull processed IDOC status number?

    Hi Experts
    What is the Successfull processed IDOC status number?
    arjent Please.
    Thanks in advance
    Sekhar

    Hi Chandra,
    Below are IDoc Process Codes
    For outboud Idocs:
    1 IDoc created
    2 Error passing data to port
    3 Data passed to port OK
    4 Error within control information of EDI subsystem
    5 Error during translation
    6 Translation OK
    7 Error during syntax check
    8 Syntax check OK
    9 Error during interchange handling
    10 Interchange handling OK
    11 Error during dispatch
    12 Dispatch OK
    13 Retransmission OK
    14 Interchange Acknowledgement positive
    15 Interchange Acknowledgement negative
    16 Functional Acknowledgement positive
    17 Functional Acknowledgement negative
    18 Triggering EDI subsystem OK
    19 Data transfer for test OK
    20 Error triggering EDI subsystem
    21 Error passing data for test
    22 Dispatch OK, acknowledgement still due
    23 Error during retransmission
    24 Control information of EDI subsystem OK
    25 Processing despite syntax error (outbound)
    26 Error during syntax check of IDoc (outbound)
    27 Error in dispatch level (ALE service)
    28 Not used
    29 Error in ALE service
    30 IDoc ready for dispatch (ALE service)
    31 Error - no further processing
    32 IDoc was edited
    33 Original of an IDoc which was edited
    34 Error in control record of IDoc
    35 IDoc reloaded from archive
    36 Electronic signature not performed (timeout)
    37 IDoc added incorrectly
    38 IDoc archived
    39 IDoc is in the receiving system (ALE service)
    40 Application document not created in receiving system
    41 Application document created in receiving system
    42 IDoc was created by test transaction
    50 IDoc added
    For Inound Idocs
    51 Error: Application document not posted
    52 Application document not fully posted
    53 Application document posted
    54 Error during formal application check
    55 Formal application check OK
    56 IDoc with errors added
    57 Test IDoc: Error during application check
    58 IDoc-Copy from an R/2 connection
    59 Not used
    60 Error during syntax check of IDoc (inbound)
    61 Processing despite syntax error (inbound)
    62 IDoc passed to application
    63 Error passing IDoc to application
    64 IDoc ready to be transferred to application
    65 Error in ALE service
    66 IDoc is waiting for predecessor IDoc (serialization)
    67 Not used
    68 Error - no further processing
    69 IDoc was edited
    70 Original of an IDoc which was edited
    71 IDoc reloaded from archive
    72 Not used, only R/2
    73 IDoc archived
    74 IDoc was created by test transaction
    Regards,
    Satish

  • What is the use of change pointer concept in ale?

    what is the use of change pointer concept in ale?
    Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

    ALE Architecture:
    It consists of an Outbound process, an Inbound process, and an Exception – Handling process.
    Outbound Process:
    ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
    1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
    2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
    3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
    4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
    Inbound Process:
    The inbound process receives an IDoc and creates a document in the system.
    1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
    2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
    3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
    Over view of IDocs:
    IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
    IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDoc’s definition and IDoc Data is an instance of the IDoc Type.
    IDoc Types:
    IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
    An IDoc is an instance of an IDoc Type and consists of three types of records.
    i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
    ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
    iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
    Message in IDoc Type:
    A Message represents a specific type of document transmitted between two partners.
    Outbound Process in IDocs:
    Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
    The Customer Model:
    A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
    Message control:
    Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
    Change Pointers:
    The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
    Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
    IDoc Structure:
    A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
    Selection Program:
    Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection program’s design depends on the triggering mechanism used in the process.
    Filter Objects;
    Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
    Port Definition:
    A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
    RFC Destination:
    The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
    Partner Profile:
    A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDoc’s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
    Service Programs and Configuration Tables:
    The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
    Creation of IDoc:
    Basic Type:
    Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
    Segments:
    Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
    Steps in creating Segments:
    T.Code WE31
    Enter the name for your segment type and click on the create icon.
    Type the Short text.
    Enter the variable names and data elements.
    Save and Go back.
    Go to Edit -> Set Release.
    Repeat the steps to create more segments.
    IDOC TYPE:
    Business data is exchanged with an external system using the IDoc Interface.
    IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
    Steps in creating IDoc Type:
    T.Code WE30 to create IDoc Type.
    Enter the Object Name, Select Basic Type and click Create Icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDoc name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press enter
    The system transfers the name of the segment type to the IDoc editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation.
    Save it and go back.
    Go to Edit -> Set Release.
    Message Type:
    Steps in Creating Message Type:
    T.Code WE81.
    change the details from Display mode to Change mode
    After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back.
    Assign Message Type to IDoc Type:
    T.Code WE82
    Change the details from Display mode to change mode.
    After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back.
    <REMOVED BY MODERATOR>
    Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

  • What is the use of the business partner cockpit ?

    Hello All
    What is the use of the business partner cockpit ?
    Regards
    Jacopo Francois

    Hi,
    BP cockpit is also called as BP factsheet. It gives the 360 degree view of the BP transations. Its a BSP application on GUI. To enable the factsheet you will have to activate the relevent BSP services in sicf.
    For more informatio refer
    http://help.sap.com/saphelp_crm50/helpdata/en/8d/b65a42a0836255e10000000a155106/content.htm
    Reward points if helpful.
    Shridhar

  • What is the use of 'pick' in interactive reporting

    hi
    what is the use of 'pick' in interactive reporting.

    Hi
    We will use this event whene setting PF-Status for Function Key F2.
    Reward All Helpfull Answers.........

  • What is the use  implemention of work flow

    Hi guis,
      can u plz tell me what is the uses, u implement a workflow, and also please give the one scenrio on purchase order or invoice or anything, one scenrio explain me.

    Workflow is a tool for automating the business process so that the process itself flows smoothly, without bottlenecks and without dead ends. Critical parts of the process can be streamlined with deadline monitoring and contingency options. Participants are informed of milestones in the process. The process definition itself is powerful enough to allow business re-engineering with re-training and to eliminate the impact of workforce changes on the basic business process.
    SAP Business Workflow is the R/3 tool for handling the process automation within R/3 or between R/3 systems and other systems involved in the business process. It is flexible enough to handle ad hoc processes such as the circulation of an electronic document. It is robust enough to handle mission critical process in the production system such as the creation of a material master.
    The different R/3 applications supply standard workflows for the commonly occurring processes. Once these workflow templates are activated, they are ready for immediate use. A complete set of workflow tools, including the workflow editor and workflow generation wizard, are provided to enhance these standard workflows or create new workflows. These tools are complemented with transactions for monitoring, tracking and the statistical analysis of the processes.
    Because the business process often does not step at the R/3 boundary, various interfaces and third party tools are available for extending the process across systems.
    Workflow is the technique for automating business processes. It is particularly beneficial
    u2022 when different people are involved in different parts of the process
    u2022 when a process only occurs sporadically and the users need to be reminded of what they need to do
    u2022 when the duration of the process is critical and deadlines have to be met
    u2022 when the process definition is likely to change on the fly and retraining users is not possible.
    By automating the process, you free the users from having to know what to do when. Work items are sent to the participants notifying them of what they have to do, and a single click on the notification calls the correct transaction and navigates to the relevant screen.
    When the workflow runs it creates work items which are like e-mails, but
    u2022 they have the advantage that they contain the intelligence needed to execute the relevant task with the correct data when the operational user executes them,
    u2022 they provide their own functionality so that the operational user has access to everything that is useful to improve the flow of the process,
    u2022 they disappear on their own when they have been executed by someone else or made obsolete.
    These work items can be received in the R/3 business workplace, MS Outlook (or any other MAPI compatible client), Lotus Notes, or work item notifications can be distributed by e-mail.
    SAP Business Workflow:
    u2022 accelerates the workflow across applications, functional areas, organizational units, and time periods,
    u2022 supplements the integrated management of processes in the SAP System with individually tailored options for automating and actively controlling business and communication processes,
    u2022 combines integrated organizational management with flexible assignment of tasks and responsibilities to locations, positions, jobs, groups, or individuals,
    u2022 actively supports a quick implementation of workflow technologies through predefined workflow templates, Workflow Wizards and flexible adjustment options,
    u2022 integrates every employee in the value chain by providing a versatile integrated inbox ("universal inbox") at their work centers that can be configured individually,
    u2022 provides a Workflow Information System that is the foundation for process change management and continuous business engineering,
    u2022 was designed to be a change-management tool,
    u2022 simplifies continuous business engineering and process change management with user-friendly tools for defining and dynamically changing workflow tasks
    u2022 conforms to the workflow standards of the Workflow Management Coalition (WfMC)
    u2022 interfaces to other mail clients such as Lotus Notes and MS Outlook
    Check these links.
    http://www.sapgenie.com/workflow/index.htm
    Link workflow business objects to your collaboration tasks!!
    http://help.sap.com/saphelp_nw04/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm
    http://help.sap.com/saphelp_bw33/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm
    http://help.sap.com/saphelp_bw31/helpdata/en/8d/25f94b454311d189430000e829fbbd/content.htm
    http://www.sap-press.com/product.cfm?account=&product=H950
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://www.workflowing.com/id18.htm
    http://www.e-workflow.org/
    http://www.sap-img.com/workflow/sap-workflow.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
    http://www.sap-img.com/workflow/sap-workflow.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
    Hope this resolves your query.
    raj

  • WHAT IS  THE USE OF COPY/MATCH OPTION  IN BUISNESS CONTENT

    WHAT IS  THE USE OF COPY/MATCH OPTION  IN BUISNESS CONTENT  GIVE DETAILS

    Hi,
    Match (X) or Copy
    If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.
    With the most important object types, the active version and the SAP delivery version can be matched.
    From a technical point of view, the SAP delivery version (D version) is matched with the M version. As in most cases the M version is identical to the active version (A version) in a customer system, this is referred to as a match between the D and A versions for reasons of simplification.
    When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually. A match can be performed automatically for properties if you can be sure that the object is to be used in the same way as before it was transferred from Business Content.  When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be transferred from the delivery version.
    Example of an automatic match
    Additional customer-specific attributes have been added to an InfoObject in the A version. In the D version, two additional attributes have been delivered by SAP that do not contain the customer-specific attributes.  In order to be able to use the additional attributes, the delivery version has to be installed from Business Content again. At the same time, the customer-specific attributes are to be retained. In this case, you have to set the indicator (X) in the checkbox.  After installing the Business Content, the additional attributes are available and the customer-specific enhancements have been retained automatically. However, if you have not checked the match field, the customer-specific enhancements in the A version are lost.
    Example of a manual match
    An InfoObject has a different text in the A version than in the D version. In this case the two versions have to be matched manually. When Business Content is installed, a details screen appears which asks you to specify whether the text should be transferred from the active version or from the D version.
    The Match indicator is set as default in order to prevent the customer version being unintentionally overwritten. If the Content of the SAP delivery version is to be matched to the active version, you have to set the Install indicator separately.
    The active version is overwritten with the delivery version if
    ¡        the match indicator is not set and
    ¡        the install indicator is set.
    In other words, the delivery version is copied to the active version.
    If the Install indicator is not set, the object is not copied or matched. In this case, the Match indicator has no effect.
    In the context menu, two options are available:
                                a.      Merge All Below
    The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Match.
                                b.      Copy All Below
    The Match indicators are removed for the object in the selected hierarchy level and all objects in the lower levels of the hierarchy. If the Install indicator is also set, these objects are copied from the delivery version to the active version.
    The most important properties which are taken into account when versions are matched are now listed.
    When referring to InfoObjects it is important to differentiate between:
    §         Characteristics
    §         Time characteristics
    §         Key figures and
    §         Units
    Valid for All InfoObjects Named Above:
    Properties Matched Automatically:
    Properties Matched Manually:
    ·        Texts
    ·        Description
    If texts/descriptions in the delivery version do not yet exist in the active version, they are transferred.
    ·        Attribute only (flag)
    ·        Short and long text (description)
    ·        Time dependency of attributes
    ·        Transfer routine
    Valid for Characteristics
    Properties Matched Automatically:
    Properties Matched Manually:
    ·        Compounding
    New InfoObjects are included in compounding
    ·        Referenced characteristic
    Reference characteristics are transferred automatically. A warning is issued.
    ·        Attributes / navigation attributes
    New attributes are included.
    If an attribute is added by the customer, the settings for this attribute are transferred (for example, F4 sequence).
    ·        Application components
    If the entry for the active version is initial, the delivery version is used.
    ·        BEx display
    ·        Characteristic constants
    ·        Default member
    ·        Authorizations (flag and field)
    ·        Selection (CHASEL)
    ·        InfoObject is document attribute
    ·        Data type
    ·        Length
    ·        Output length
    ·        Conversion routines
    ·        Lower case allowed (flag)
    ·        Contains master data (flag)
    ·        Master data is authorization relevant (flag)
    ·        Export DataSource (Flag)
    ·        F4 query design
    ·        F4 query runtime
    ·        Check ODS object
    ·        Contains text tables (flag)
    ·        Texts are language-dependent (flag)
    ·        Short, medium and long texts exist (each with flag)
    ·        Default currency
    ·        GIS attribute
    ·        Hierarchies exist (flag)
    Valid for Key Figures
    Properties Matched Automatically:
    Properties Matched Manually:
    ·        Type of key figure
    ·        Fixed unit
    ·        Fixed currency
    ·        Aggregation
    ·        Exception aggregation
    Valid for Units
    Properties Matched Automatically:
    Properties Matched Manually:
    ·        See the table above (Valid for Characteristics), if these properties are also relevant for the units.
    When referring to InfoProviders it is important to differentiate between:
    ¡        MultiProviders
    ¡        InfoCubes
    ¡        ODS Objects and
    ¡        InfoObjects
    InfoObjects are discussed above (see the first table Valid for All Objects Named Above).
    Valid for All InfoProviders Named Above:
    Properties Matched Automatically:
    Properties Matched Manually:
    ·        New InfoObjects
    If InfoObjects in the delivery version do not yet exist in the active version, they are transferred.
    ·        Manual matching is not necessary.
    Valid for MultiProviders
    Properties Matched Automatically:
    Properties Matched Manually:
    ·        New InfoProviders
    If InfoProviders in the delivery version do not yet exist in the active version, they are transferred.
    ·        Manual matching is not necessary.
    Valid for InfoCubes
    Properties Matched Automatically:
    Properties Matched Manually:
    ·        New dimensions
    If dimensions in the delivery version do not yet exist in the active version, they are transferred.
    ·        Manual matching is not necessary.
    With the InfoObject catalog object type, InfoObjects that are assigned to a catalog in the delivery version are transferred to the active version automatically. Manual matching is not necessary.
    With the transfer rule object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional attributes) are added automatically when the match is performed.  Manual matching is not necessary.
    With the process chain object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional objects in the process chain) are added automatically when the match is performed.  Manual matching is not necessary.
    ·        Active Version Available
    In this column, the following display options are available:
    ¡        : The object is available in an active version. You decide whether you want to retain this version or reinstall the latest version of the object.
    ¡        Date symbol: The object is already available in an active version. However, the active version belongs to an older Content release. SAP recommends that you install the latest version.
    ¡        Gray symbol: An activated version of the object is available in the system. However, the object status is inactive. If an object version is activated, this indicates that all metadata for the object can be created successfully. The inactive object status indicates that the processed object is inconsistent and cannot currently be used for processing data. Transfer the object again from the SAP delivery version (D version).  If this is not enough to change the object status from “inactive” to “active” the object has to be postprocessed. You find notes on postprocessing in the activation log.
    Postprocessing: An inactive object status may also occur for an InfoObject if changes are made to the structure at field level. Postprocessing the object involves converting the relevant tables in accordance with the activation log.
    ¡        No indicator: The object is not available in an active version.
    7. Make Settings in the Selection List and Install.
    Make the required settings in the  Install selection list:
    Installation Type
    Installation Type
    Information
    Simulate installation
    The system runs a test to see whether any errors are likely to occur during the installation. However, not all errors that may occur can be identified during simulation: Some error messages can only be generated when a real A version (and not just a simulation) is available in the system. You should, therefore, only use the simulation function as a rough guide to help you identify and remove basic errors.
    Install
    The selected objects are installed immediately.
    Install in background
    The selected objects are installed in the background.
    Install and transport
    The selected objects are installed immediately and then written to a transport request.
    SAP recommends you use the Install in background option because installing a large number of objects can take a long time. Modifying objects that are already active can take an especially long time to complete. Make sure that when you install objects in the background that the versions are not matched. It is always the delivery versions that are installed. These are not matched with any available customer versions.
    Refer
    Business Content (Versions)
    http://help.sap.com/saphelp_nw04/helpdata/en/c1/ea683cc5e8ca68e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a66d5e07211d2acb80000e829fbfe/frameset.htm
    Thanks,
    JituK

  • What is the use of CVI_BDT_ADAPTER class ?

    Hi Freinds,
    what is the use of CVI_BDT_ADAPTER class ? can any one explain ?
    thnx n regards
    Vijaya

    Hi,
    This class is used for following cases:
    1.modify fields depending on customer status
    2.modify fields depending on vendor status
    3.to check user has the authorization
    to view/change/create data in the specified sales area

  • What is the best FREE GUI Builder in Eclipse plugin??

    hello experts!!!
    nid ur help... does anyone here uses Eclipse editor?? i am using Jigloo Gui Builder plugin to create GUI
    BUT there GROUP layout manager it sucks its so diffucult to layout..
    what is the best FREE GUI Builder in Eclipse plugin??

    kagaw3000 wrote:
    i am not an english speaker and i am not an American citizen.And many others here are not primary or secondary English speakers either. How can you expect them to understand you if you use strange abbreviations? Programming is an exercise in precision. If you have a question here, you would do well to communicate it precisely.
    At the site [How to Ask Smart Questions|http://www.catb.org/~esr/faqs/smart-questions.html#writewell] :
    h1. Write in clear, grammatical, correctly-spelled language
    We've found by experience that people who are careless and sloppy writers are usually also careless and sloppy at thinking and coding (often enough to bet on, anyway). Answering questions for careless and sloppy thinkers is not rewarding; we'd rather spend our time elsewhere.
    So expressing your question clearly and well is important. If you can't be bothered to do that, we can't be bothered to pay attention. Spend the extra effort to polish your language. It doesn't have to be stiff or formal � in fact, hacker culture values informal, slangy and humorous language used with precision. But it has to be precise; there has to be some indication that you're thinking and paying attention.
    Spell, punctuate, and capitalize correctly. Don't confuse �its� with �it's�, �loose� with �lose�, or �discrete� with �discreet�. Don't TYPE IN ALL CAPS; this is read as shouting and considered rude. (All-smalls is only slightly less annoying, as it's difficult to read. Alan Cox can get away with it, but you can't.)
    More generally, if you write like a semi-literate boob you will very likely be ignored. So don't use instant-messaging shortcuts. Spelling "you" as "u" makes you look like a semi-literate boob to save two entire keystrokes. Worse: writing like a l33t script kiddie hax0r is the absolute kiss of death and guarantees you will receive nothing but stony silence (or, at best, a heaping helping of scorn and sarcasm) in return.
    If you are asking questions in a forum that does not use your native language, you will get a limited amount of slack for spelling and grammar errors � but no extra slack at all for laziness (and yes, we can usually spot that difference). Also, unless you know what your respondent's languages are, write in English. Busy hackers tend to simply flush questions in languages they don't understand, and English is the working language of the Internet. By writing in English you minimize your chances that your question will be discarded unread.
    the main issue here is my questionMy recommendation: learn to do Swing without a code-generator. You gain a much better understanding of the underpinnings of Swing, the layout managers, and you gain extremely good control of component placement.

Maybe you are looking for