Details about HRForm Transaction in ABAP-HR

hi guys,
can anyone plz tell me how to create Infostar,infonet and metanet in HRForms transactions?
thanks & regards
Dasaradh

check http://help.sap.com/saphelp_erp2005vp/helpdata/en/8c/aaae6c061a11d4972200a0c9306433/frameset.htm
Regards
Prabhu

Similar Messages

  • Error when Calling Transaction in ABAP Proxy

    Hi All,
    I'm trying to call a transaction in synchronous ABAP Proxy, but there's a CNTL_ERROR in the details of SXMB_MONI.
    I've checked some threads related to this problem, but they're not solved yet.
    Please advise, can I use "call transaction" in synchronous ABAP Proxy ? Is there any additional setting / code to prevent the error ?
    Thanks in advance,
    Andy S

    Hi Stefan,
    I'm trying to assign marketing attributes in our CRM Business Partner Transaction, which is triggered by messages sent from some 3rd party application.
    Recently, I find out that this transaction (TCode BP) raise the same error (CNTL_ERROR) if run background from SM35. So the problem is not about calling transaction in ABAP Proxy, but due to the TCode BP itself.......
    My ABAPER friend is trying to find the BAPI to replace this call transaction .........
    Thanks a lot for your response........
    Regards,
    Andy S

  • Details about ABAP Function Module

    Hi All,
    I am trying to get information about the data returned by 2 ABAP function modules. These are :-
    1) TH_WPINFO - Shows the number of work processes running on the SAP system. The table fields are:-
    WP_NO
    WP_TYP
    WP_PID
    WP_STATUS
    WP_WAITING
    WP_SEM
    WP_RESTART
    WP_DUMPS
    WP_CPU
    WP_ELTIME
    WP_MANDT
    WP_BNAME
    WP_REPORT
    WP_ACTION
    WP_TABLE
    WP_SERVER
    WP_WAITINF
    WP_WAITTIM
    2) TH_WP_DETAIL_INFO - Shows the additional details about a particular work process. The table fields are:-
    EYEON
    STARTTIME1
    STARTTIME2
    ENDTIME1
    ENDTIME2
    RESPTIME
    ROLLED_OUT
    CPUTIME
    QUEUETIME
    GUITIME
    GUICNT
    GUINETTIME
    L_ENDTIME1
    L_ENDTIME2
    RFCTI
    RFCCNT
    INPUTLEN
    OUTPUTLEN
    MAXROLL
    MAXPAGE
    ROLLINCNT
    ROLLINTI
    ROLLOUTCNT
    ROLLOUTTI
    LOCKCNT
    LOCKTI
    READDIRCNT
    READDIRTI
    READDIRREC
    READDIRBUF
    READSEQCNT
    READSEQTI
    READSEQREC
    READSEQBUF
    PHYREADCNT
    INSCNT
    INSTI
    INSREC
    PHYINSCNT
    UPDCNT
    UPDTI
    UPDREC
    PHYUPDCNT
    DELCNT
    DELTI
    DELREC
    PHYDELCNT
    COMMITTI
    DBPROCCNT
    DBPROCTI
    GENERATETI
    REPLOADTI
    CUALOADTI
    DYNPLOADTI
    SRCLODCNT
    DSQLCNT
    QUECNT
    QUETI
    DDICTI
    MEMSUM
    PRIVSUM
    USEDBYTES
    MAXBYTES
    MAXBYTESDI
    ADCNT
    ADTIME
    DISPCNT
    ACCOUNT
    TRANSID
    TERMINAL
    REPORT
    DYNPRONR
    TCODE
    CUAPRG
    CUAFUNC
    DIA_FILL_1
    EYEOFF
    As you can see, the tables shown by these function modules have lots of columns but there is not much description (In fact, nothing at all) about them. If anybody has used these function modules before can you please point me to a location where I can find documentation for these. I have already searched on SAP help portal but it doesn't show any information about this. I tried with TCODE SM50 on my SAP GUI but it doesn't give precise information. Please suggest on how or where I can find description for these tables.
    Many Thanks in advance!!!
    - John

    Hi John!
    There is no documentation - you can't expect, that <i>every</i> bit is documented in SAP.
    If you are interested in something special, ask this - but I doubt that you will find someone, who writes a FM documentation based on his own experience.
    The most important fields you can guess by the name or comparing with SM50 / SM66.
    Regards,
    Christian

  • DETAILS ABOUT BDC

    Hello Sir ,
    This the second time i am asking u the question
      I am new to <b>ABAP</b> ,so please consider my request
    Please send me the details related to Programming in<b>BDC</b> ie
    session method and call transaction method
    and<b> complete details about BDC</b>
    urs faithfully
    Basavraj <b></b>

    Basavraj,
    Sorry to say, but the Discovery System experts are not equipped to support detail questions such as yours.  If you use the forums or OSS Notes for particular components, they will be more timely and reliable.
    In your case, I recommend you either search SDN such as as this:
    https://www.sdn.sap.com/irj/sdn/advancedsearch?query=bdc%20programming&cat=sdn_all
    Or, seach OSS Notes within component BC-ABA-SC or generally, search within all components for "BCD programming" say within the past year.
    Best,
    Rick

  • Give me details about differrent views in generic extraction give details

    give me details about differrent views in generic extraction give details  such as  database view, projection view, help view, etc please give detail

    Dear Deba,
    Projection view - Just retrieves some fields from a single table.
    Help View - This is used for search help.
    Database View - This is inner join view of one or more tables
    Maintenance View - Helps in creating maintaining data of the application object. The data can be distributed among several tables
    Data Base View:
    A database view is defined in the ABAP Dictionary and automatically created on the database during
    activation. Accesses to a database view are passed directly to the database from the database interface.
    The database software performs the data selection.
    If the definition of a database view is changed in the ABAP Dictionary, the view created on the database
    must be adjusted to this change. Since a view does not contain any data, this adjustment is made by
    deleting the old view definition and creating the view again in the ABAP Dictionary with its new definition.
    The maintenance status defines whether you can only read with the view or whether you can also write
    with it. If a database view was defined with more than one table, this view must be read only.
    The data read with a database view can be buffered. View data is buffered analogously to tables. The
    technical settings of a database view control whether the view data may be buffered and how this should
    be done. The same settings (buffering types) can be used here as for table buffering. The buffered view
    data is invalidated when the data in one of the base tables of the view changes.
    Maintainance View:
    Data that is distributed on more than one table often forms a logical unit, called an application object.
    You should be able to display, change and create the data of such an application object together. Users
    usually are not interested in the technical implementation of the application object, such as the distribution of the data on several tables.
    You can maintain complex application objects in a simple way using a maintenance view. The data is
    automatically distributed on the underlying database tables.
    All the tables used in a maintenance view must be linked with a foreign key. This means that the join
    conditions are always derived from the foreign key in the maintenance view. You cannot enter the join
    conditions directly as in a database view.
    A maintenance interface with which the data of the view can be displayed, changed and created must be
    generated from the definition of a maintenance view in the ABAP Dictionary.
    When the maintenance interface is created, function modules that distribute the data maintained with the
    view on the underlying tables are automatically generated.
    The maintenance interface is generated with the Transaction Generate Table View (Transaction SE54)
    or from the view maintenance screen with Environment -> Tab.maint.generator.
    Database views implement an inner join. You only get those records which have an entry in all the tables
    included in the view.
    Maintenance views implement an outer join.
    Help View:
    A help view is defined analogously to a maintenance view. Help views can only be used as selection
    methods in search helps. Since the R/3 System cannot pass the selection directly to the database using
    a help view, it must generate its own access routines. The database view should therefore be used as
    selection method in preference to the help view.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ecf9446011d189700000e8322d00/frameset.htm
    Difference between "Help View" and "Search Help"
    http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed06446011d189700000e8322d00/frameset.htm
    for more detailed info look on:
    http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+dictionary&
    Regards,
    Ram.

  • Know more detail about the Remote Support Platform for SAP Business One ?

    SAP Business One 9.1 is about to release this year and we can see in the feature enhancements that a significant update is planned in the Remote Support Platform for SAP Business One, more commonly known as RSP. Let’s have a quick look what update is planned for RSP in version 9.1:
    Enhancements planned in Remote Support Platform for SAP Business One 9.1
    RSP is planned to support both SAP Business One on Microsoft SQL Server as well as SAP Business One on HANA Database
    RSP Processes and Reports adapted to SAP HANA Database
    With this plan RSP will help in the areas of Download, Installation, Go-Live Check, Monitoring, Upgrade and Support for SAP Business One both   on SQL Server and HANA.
    But like me (non-SAP B1 Consultant) many of you have the question what is RSP and how it helps in support? Here I have tried to gather all information.
    What is Remote Support Platform for SAP Business One?
    The remote support platform for SAP Business One is designed to protect a SAP Business One installation by providing automated and remote support in a high-volume business.
    The platform monitors the entire SAP Business One environment. By significantly reducing the time between the appearance, identification, and resolution of issues, the remote support platform for SAP Business One minimizes the impact on customer databases and processes.
    Some Key Features of Remote Support Platform:
    Showing alerts to SAP B1 Admin about the events which require their attention, such as low disk space, database backups, etc.
    Incident Reports against the issues identified which require attention of SAP Support
    Company Database Backup and Restore options
    Regular fixes of Company Database inconsistencies
    Check, Download and Install regular updates in SAP Business One
    Upload Logs and required files to SAP Support or to Partner Support on regular basis
    Some details about RSP Backup Management
    Schedule daily, weekly, and monthly backups
    Perform differential and full database backups
    Back up transaction logs
    Back up files to shared folders on a network
    System Status Report through RSP
    From June 1st 2013, it will be mandatory to install, configure and upload the System Status Report (SSR) from Remote Support Platform (RSP) for SAP Business One in order to receive support for messages of a technical nature (upgrades, performance & crashes, etc).
    Database uploads only via RSP
    From June 1st 2013 SAP Business One Support will only accept database uploads to SAP via remote support platform for SAP Business One. In certain exceptional circumstances STFP may be used but this will constitute a minority of cases.
    Microsoft Windows PowerShell Scripting
    In the remote support platform studio, you can create tasks using Microsoft Windows PowerShell scripting. PowerShell enables you to perform remote administrative tasks on customers’ Microsoft Windows operating systems, by providing full access to Component Object Model (COM) and Windows Management Instrumentation (WMI).Some Network Prerequisite for RSP
    To achieve the internet connection test, you must allow port 80 for the RSP external communication
    Disabling antivirus firewall or add the RSP to the trusted zone of the antivirus
    Set the correct proxy
    Disabling Windows firewall in the TP_link Wireless Configuration Utility
    Want to now More about It Click Here :   Remote Support Platform for SAP Business One

    SAP Business One 9.1 is about to release this year and we can see in the feature enhancements that a significant update is planned in the Remote Support Platform for SAP Business One, more commonly known as RSP. Let’s have a quick look what update is planned for RSP in version 9.1:
    Enhancements planned in Remote Support Platform for SAP Business One 9.1
    RSP is planned to support both SAP Business One on Microsoft SQL Server as well as SAP Business One on HANA Database
    RSP Processes and Reports adapted to SAP HANA Database
    With this plan RSP will help in the areas of Download, Installation, Go-Live Check, Monitoring, Upgrade and Support for SAP Business One both   on SQL Server and HANA.
    But like me (non-SAP B1 Consultant) many of you have the question what is RSP and how it helps in support? Here I have tried to gather all information.
    What is Remote Support Platform for SAP Business One?
    The remote support platform for SAP Business One is designed to protect a SAP Business One installation by providing automated and remote support in a high-volume business.
    The platform monitors the entire SAP Business One environment. By significantly reducing the time between the appearance, identification, and resolution of issues, the remote support platform for SAP Business One minimizes the impact on customer databases and processes.
    Some Key Features of Remote Support Platform:
    Showing alerts to SAP B1 Admin about the events which require their attention, such as low disk space, database backups, etc.
    Incident Reports against the issues identified which require attention of SAP Support
    Company Database Backup and Restore options
    Regular fixes of Company Database inconsistencies
    Check, Download and Install regular updates in SAP Business One
    Upload Logs and required files to SAP Support or to Partner Support on regular basis
    Some details about RSP Backup Management
    Schedule daily, weekly, and monthly backups
    Perform differential and full database backups
    Back up transaction logs
    Back up files to shared folders on a network
    System Status Report through RSP
    From June 1st 2013, it will be mandatory to install, configure and upload the System Status Report (SSR) from Remote Support Platform (RSP) for SAP Business One in order to receive support for messages of a technical nature (upgrades, performance & crashes, etc).
    Database uploads only via RSP
    From June 1st 2013 SAP Business One Support will only accept database uploads to SAP via remote support platform for SAP Business One. In certain exceptional circumstances STFP may be used but this will constitute a minority of cases.
    Microsoft Windows PowerShell Scripting
    In the remote support platform studio, you can create tasks using Microsoft Windows PowerShell scripting. PowerShell enables you to perform remote administrative tasks on customers’ Microsoft Windows operating systems, by providing full access to Component Object Model (COM) and Windows Management Instrumentation (WMI).Some Network Prerequisite for RSP
    To achieve the internet connection test, you must allow port 80 for the RSP external communication
    Disabling antivirus firewall or add the RSP to the trusted zone of the antivirus
    Set the correct proxy
    Disabling Windows firewall in the TP_link Wireless Configuration Utility
    Want to now More about It Click Here :   Remote Support Platform for SAP Business One

  • Could you pls give the details about the Unicode conversion during Upgrade

    Hi,
    Can anyone give details about the Unicode conversion during SAP Upgradation fro 4.6C to ECC6.
    Waiting for quick response
    Best Regards,
    Padhy

    Hi,
    These are the few points i gathered during my upgradation project.
    Before starting any upgradation project, it is necessary to take up the back-up of the existing systems. As we are going to upgrade the entire system, we will be changing so many things and if something happens, without back-up, we will be in a trouble.
    So it is advised to keep a back-up of the existing system.
    Say for example we have the existing system E4B which is of Version 4.6C. Now we want to upgrade it to Version 4.7. Let us see how we can do it.
    Version upgrades not only means that we need to run the new Version CD over the existing Version System but only involves some other thing.
    Version Upgrade involves the following Steps.
    Say we want to upgrade for Version 4.7 from Version 4.6, which is in the System E4B. Now we created one more system called as E1B in which the upgradation for Version 4.7 can be done.
    • First copy the entire E4B system into the E1B System which is created for Version 4.7.
    • Apply the Version 4.7 CD provided by SAP over the E1B System.
    • Now check whether all the functionalities that was in E4B system works fine with E1B system also.
    Thus the Version Upgrade involves two steps.
    1. SAP Upgradation with the help of the CD
    2. Manual Upgradation.
    1. SAP Upgradation with the help of the CD
    This is nothing but after taking the copy of the existing system into a new system, the upgradation CD from SAP is applied over the new system.
    2. Manual Upgradation.
    This Manual Upgradation involves
    2.1 Upgradation of Standard Objects
    2.1.1 SPAU Objects
    2.1.2 SPDD Objects
    2.2 Upgradation of Custom Objects.
    Upgradation of Custom Objects can be placed under the following three categories.
    Unicode Compliance
    Retrofit
    Upgrade
    Please Find below some of the common Unicode Errors and their solutions
    1. Error:
    In case of Translate Error; ‘Dangerous use of Translate in Multilingual system.’
    Correction:
    To correct the Error occurring on TRANSLATE statement – use this additional statement before the Translate statement.
    SET LOCALE LANGUAGE sy-langu.
    This statement defines the Text Environment of all the programs & internal sessions in the language specified in the LANGUAGE KEY, which in this case is “sy-langu”, i.e. the log on language of the user.
    2. Error:
    In case of Open Dataset Error; ‘Encoding Addition must be included.’
    Correction:
    This Error occurs only when the MODE is TEXT.
    To correct the Error occurring on OPEN DATASET statement – use this statement instead.
    OPEN DATASET dataset_name FOR access IN TEXT MODE ENCODING DEFAULT.
    Where: dataset_name – NAME OF THE DATASET.
    Access – INPUT or OUTPUT or APPENDING or UPDATE.
    DEFAULT - Corresponds to UTF-8 in UNICODE systems &
    NON_UNICODE in NON-UNICODE systems.
    3. Error:
    In case of the usage of the Obsolete FM UPLOAD/DOWNLOAD or WS_UPLOAD/DOWNLOAD; ‘Function module UPLOAD is flagged as obsolete.’
    Correction:
    The FM GUI_DOWNLOAD/UPLOAD is used.
    The variations to be made in the parameters of the FM:
    1. Filename – It must be of STRING type.
    2. Filetype – “DAT” is not used any longer, instead “ASC” is used.
    3. Field Separator – The default value “SPACE” is used, incase for a TAB separated file “X” can be used.
    4. Error:
    In case of CURRENCY/UNIT Addition Error; ‘Use addition CURRENCY/UNIT when outputting.’
    Correction:
    The CURRENCY addition specifies the currency-dependant decimal places for the output of the data objects of type i or p. To obtain the currency-key, the field CURRKEY of the table TCURX is used. The system determines the number of the decimal places from the field CURRDEC of the selected CURRKEY.
    To correct this error follow the following method:
    WRITE: /3 'TOTAL',' ', TOTAL.
    WRITE: /3 ‘TOTAL’,’ ‘, TOTAL CURRENCY ‘2’. --- Where ‘2’is the Currency Key for Getting 2 decimal places.
    5. Error:
    In case of TYPE X Error; ‘Variable must be of C, N, D, T or STRING type.’
    Correction:
    We need to change all the Type X (Hexadecimal) variables to Type C with their values unchanged.
    So the method to be followed is:-
    1. Load the definition of the class CL_ABAP_CONV_IN_CE or CL_ABAP_CHAR_UTILITIES.
    2. Declare the variable as Type C, and use the method UCCP(‘XXXX’) of the class CL_ABAP_CONV_IN_CE where XXXX represents the 8-bit Hexadecimal value and incase the variable holds a Hex value for a Horizontal Tab , then the Attribute “HORIZONTAL_TAB” of the class CL_ABAP_CHAR_UTILITIES can be used directly instead of using the method UCCP.
    E.g.:
    i) *DATA: TAB TYPE X VALUE 09, “Tab character
    CLASS: CL_ABAP_CHAR_UTILITIES DEFINITION LOAD.
    DATA TAB TYPE C VALUE CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
    ii) * DATA: CHAR TYPE X VALUE 160.
    CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
    DATA CHAR TYPE C.
    CHAR = CL_ABAP_CONV_IN_CE=>UCCP(‘00AO’).
    (Here ‘00A0’ is the Hexadecimal equivalent of the decimal 160).
    3. Incase the TYPE X Variable has a length more than 1, then an internal table must be created for the variable.
    E.g.:
    CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
    DATA : LF(2) TYPE X VALUE 'F5CD'.
    DATA : BEGIN OF LF,
    A1 TYPE C,
    A2 TYPE C,
    END OF LF.
    LF-A1 = CL_ABAP_CONV_IN_CE=>UCCP('00F5').
    LF-A2 = CL_ABAP_CONV_IN_CE=>UCCP('00CD').
    6. Error:
    In case of the Character “-“Error; ‘The Character “-“can’t appear in names in Unicode Programs.’
    Correction:
    The Character “-“(Hyphen) appearing in Variable names is replaced by the character “_” (Under Score) for Unicode/Upgrade Compliance.
    E.g.:
    *wk-belnr LIKE bkpf-belnr,
    *wk-xblnr LIKE bkpf-xblnr,
    *wk-date LIKE sy-datum,
    *wk-wrbtr LIKE bseg-wrbtr,
    *wk-name1 LIKE lfa1-name1,
    *wk-voucher(8) TYPE c.
    wk_belnr LIKE bkpf-belnr,
    wk_xblnr LIKE bkpf-xblnr,
    wk_date LIKE sy-datum,
    wk_wrbtr LIKE bseg-wrbtr,
    wk_name1 LIKE lfa1-name1,
    wk_voucher(8) TYPE c.
    7. Error:
    In case of The SUBMIT-TO-SAP-SPOOL Error; ‘you should not use the statement SUBMIT-TO-SAP-SPOOL without the WITHOUT SPOOL DYNPRO addition. ‘
    Correction:
    1. Declare variables of type PRI_PARAMS, ARC_PARAMS, and a variable of TYPE C which would be used as a VALID FLAG.
    2. Call the FM GET_PRINT_PARAMETERS:
    CALL FUNCTION 'GET_PRINT_PARAMETERS'
    EXPORTING
    ARCHIVE_MODE = '3'
    DESTINATION = P_DEST
    IMMEDIATELY = 'X'
    IMPORTING
    OUT_ARCHIVE_PARAMETERS = archive_parameters
    OUT_PARAMETERS = print_parameters
    VALID = valid_flag
    EXCEPTIONS
    INVALID_PRINT_PARAMS = 2
    OTHERS = 4
    3. Use the SUBMIT-TO-SAP-SPOOL statement.
    E.g.:
    •     submit zrppt500
    •     using selection-set 'AUTO3'
    •     with res_no eq lo_rsnum
    •     with sreserv in preserv
    •     to sap-spool destination p_dest
    •     immediately 'X'. "print immediate
    DATA: print_parameters type pri_params,
    archive_parameters type arc_params,
    valid_flag(1) type c.
    CALL FUNCTION 'GET_PRINT_PARAMETERS'
    EXPORTING
    ARCHIVE_MODE = '3'
    DESTINATION = P_DEST
    IMMEDIATELY = 'X'
    IMPORTING
    OUT_ARCHIVE_PARAMETERS = archive_parameters
    OUT_PARAMETERS = print_parameters
    VALID = valid_flag
    EXCEPTIONS
    INVALID_PRINT_PARAMS = 2
    OTHERS = 4
    Submit zrppt500
    Using selection-set 'AUTO3'
    With res_no eq lo_rsnum
    with sreserv in preserv
    to sap-spool
    SPOOL PARAMETERS PRINT_PARAMETERS
    ARCHIVE PARAMETERS ARCHIVE_PARAMETERS
    WITHOUT SPOOL DYNPRO.
    8. Error:
    In case of Message Error; ‘Number of WITH fields and number of Place Holders are not same ‘.
    Correction:
    Split the statement after WITH into the same number as the place holder for that Message ID.
    E.g.:
    1. * MESSAGE E045.
    MESSAGE E045 WITH '' ''.
    2. in program ZIPI0801
    •     Start of change for ECC6
    •     message e398(00) with 'Could not find access sequence'
    •     'for condition type:'
    •     p_ptype.
    message e398(00) with 'Could not find '
    'access sequence'
    'for condition type:'
    p_ptype.
    •     End of change made for ECC6
    9. Error:
    In case of Move between 2 different Structures; ‘The structures are not mutually convertible in a Unicode program.’
    Correction:
    Make both the Data Types compatible and then assign the contents.
    E.g.:
    The statement –“move retainage_text to temp_text.” Gives an error, where RETAINAGE_TEXT is an internal table and TEMP_TEXT is a string of length 200.
    A Feasible solution for this is to specify from which position to which position of the string, the fields of RETAINAGE_TEXT should be assigned.
    TEMP_TEXT+0(1) = RETAINAGE_TEXT-DQ1.
    TEMP_TEXT+1(1) = RETAINAGE_TEXT-HEX.
    TEMP_TEXT+2(20) = RETAINAGE_TEXT-FILLER1.
    TEMP_TEXT+22(15) = RETAINAGE_TEXT-AMT_DUE.
    TEMP_TEXT+37(8) = RETAINAGE_TEXT-TEXT.
    TEMP_TEXT+45(10) = RETAINAGE_TEXT-DUE_DATE.
    TEMP_TEXT+55(1) = RETAINAGE_TEXT-DQ2.
    10. Error:
    In case of ‘no description found’; ‘add a GUI title’.
    Correction:
    In this type of error gui title is generally missing so add a GUI title to the module pool.
    11. Error:
    In case of ‘writing internal or transparent table’
    Correction:
    Write individual fields.
    E.g.:
    WRITE: / EXT. --> EXT should be a character type field
    WRITE: / EXT-ZZSTATE, EXT-LINE_NO, EXT-LINE_TXT, EXT-AMT, EXT-ZZSKUQTY.
    12. Error:
    In case of ‘combination reference table/field S541-UMMENGE does not exist’
    Correction:
    Was due to error in reference table S541. TABLE S541 has errors
    1)”Foreign key S541- ZZMARKET (ZZMARKET AND KATR2 point to different domains)”
    2)”Foreign key S541-ZZACQUIGRP (ZZACQUIGRP AND KATR8 point to different domains)”
    Changed the domain of ZZMARKET (from ZMKCODE to ATTR2)
    And that of ZMKCODE (from ZACCODE to ATTR8)
    13. Error:
    In case of ‘KEY does not exist’
    Correction:
    The reference table for field KBETR was KNOV earlier changed it to RV61A as KNOV was in turn referring to RV61A.
    14. Error:
    Incase of ‘WRITE’ statement, ‘Literals that take more than one line is not permitted in Unicode systems.’
    Correction: To correct this error, we need to align the spaces accordingly so that the statement doesn’t go beyond the line.
    15. Error:
    Incase of Data statement, ‘The data type ZWFHTML can be enhanced in any way. After a structure enhancement, this assignment or parameter might be syntactically incorrect………..’
    Correction: To correct this error, instead of “like” in the Data statement, use “type”.
    16. Error:
    Incase of DESCRIBE statement, ‘DESCRIBE can be used only with IN BYTE... Or IN CHARACTER mode in Unicode systems.’
    Correction: To correct this error, use additional text, IN BYTE MODE / IN CHARACTER MODE along with this statement.
    CHARACTER MODE is added when the data object is of flat/ character type.
    BYTE MODE is added when the data object is a deep structure.
    Syntax: DESCRIBE FIELD data_obj : LENGTH blen IN BYTE MODE,
    LENGTH clen IN CHARACTER MODE.
    Where blen and clen must be of type I.
    17. Error:
    Incase of DO-LOOP Error,’ In Do loop range addition needed‘
    Correction:
    An internal tables is declared and the two fields (VARYING field and NEXT field) were
    Included inside the internal table
    E.g.: In program SAPMZP02
    DO 11 TIMES
    •     VARYING STATION_STATE FROM STATION1 NEXT STATION2. “ECC6
    CASE SYST-INDEX.
    WHEN ‘1’
    STATION_STATE = STATION1.
    WHEN ‘2’
    STATION_STATE = STATION2.
    WHEN ‘3’
    STATION_STATE = STATION3.
    WHEN ‘4’
    STATION_STATE = STATION4.
    WHEN ‘5’
    STATION_STATE = STATION5.
    WHEN ‘6’
    STATION_STATE = STATION6.
    WHEN ‘7’
    STATION_STATE = STATION7.
    WHEN ‘8’
    STATION_STATE = STATION8.
    WHEN ‘9’
    STATION_STATE = STATION9.
    WHEN ‘10’
    STATION_STATE = STATION10.
    WHEN ‘11’
    STATION_STATE = STATION11.
    18. Error:
    Incase of the parameter QUEUE-ID Error,’ QUEUE-ID’ is neither a parameter nor a select option in program rsbdcbtc.’
    Correction:
    The parameter in program rsbdcbtc is QUEUE_ID and so is changed in this program
    E.g.: In program Z_CARRIER_EDI_INTERFACE
    •     submit rsbdcbtc with queue-id = apqi-qid and return. "ECC6
    •     The parameter name changed by replacing '-' with '_' as in program rsbdcbtc "ECC6
    Submit rsbdcbtc with queue_id = apqi-qid and return. "ECC6
    19. Error:
    Incase of EPC Error,’ Field symbol <TOT_FLD> is not assigned to a field ‘.
    Correction:
    This error couldn't be rectified as the error occurs in a Standard SAP include- LSVIMF29.
    The OS Note - 1036943 needs to be applied.
    Error:
    OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE.
    Correct:
    OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
    Error:
    Constants : c_tab type x value '09' .
    Correct:
    Constants : c_tab type abap_char1 value cl_abap_char_utilities=>horizontal_tab .
    Error:
    Data : begin of output_options occurs 0 . Include structure ssfcompop.
    Data : end of output_options .
    Correct:
    Data : output_options type standard table of ssfcompop with header line .
    Error:
    PARAMETERS : NAST TYPE NAST .
    Correct:
    PARAMETERS : NAST TYPE NAST NO-DISPLAY .
    Replace WS_DOWNLOAD and WS_UPLOAD by
    GUI_UPLOAD and GUI_DOWNLOAD and check the import and export parameter types , do the changes accordingly. Because FILENAME paramater type is different because of this it will give dump.
    For issue during Issue using SO_NEW_DOCUMENT_ATT_SEND_API1 Function module, the solution is After this FM we should put COMMIT WORK.
    Issue:
    Moving data from one structure to another structure if those two structures are not compatible
    Solution:
    we should use move-corresponding or field by filed we need to move it.
    If database structures are different in 4.6c and ECC6.0,
    Then we should go with append structure concept.
    While testing the report if it gives dump at Select query level or any database or view level,then just goto that table or view and goto the data base utility(se14) adjust the database. But make sure that selected radio button in se14 transaction should be activate and adjust database
    Also Check this link.
    http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/frameset.htm
    Reward points if helpful.
    Regards,
    Ramya

  • Information about Integration WebDynpro for ABAP and Business-Workflow

    Hi Experts,
    I'm looking for information about
    • Integration WebDynpro for ABAP and Business-Workflow
    Link, documents and books are welcome!
    Thanks
    mishak

    If you have worked on workflows earlier the procedure is very simple. You just need to enter certain parameter values of your application in SWFVISU for the respective task and re-register your system in UWL administration. Thats it! your webdynpro and workflows are integrated. For details on the parameters check the following link,
    http://help.sap.com/saphelp_nw04/helpdata/en/19/bff5c18ba44da4a4ca68cf572dabda/frameset.htm
    There are also a couple of blogs on "launching webdynpro from UWL" (Procedure for both Java and webdynpro is almost similar). You can also check these for more details.
    Thanks,
    Prasath N

  • Details about invoices

    Hi. I have a wuestion. There are FBL1N and FBL5N transactions in SAP. They give lists of invoices. In both cases when You double click on some position from the list of invoices, a screen with details about invoice appears. Is this some standard event? What should I do to use it in my programm? Greetings. P.

    DATA:
    W_BELNR LIKE BKPF-BELNR,
    W_BUKRS LIKE BKPF-BUKRS,
    W_GJAHR LIKE BKPF-GJAHR.
    ****Assign values to these variables, in FBL!N they contain the record on which you cliked
         SET PARAMETER ID  'BLN' FIELD W_BELNR.
          SET PARAMETER ID  'BUK' FIELD W_BUKRS.
          SET PARAMETER ID  'GJR' FIELD W_GJAHR.
          CALL TRANSACTION 'FB03' AND SKIP FIRST SCREEN.
    *Reward if useful and get back in case of a query
    Message was edited by:
            Tripat Pal Singh

  • Details about Attachment in PO

    Hi Gurus,
    I attached the documents in to ME22N transaction by using a services for Object button on the left side corner of the screen. Now our EP consultant needs a BAPI to get the details about the attached document. Title of the document, Date of the document created and name of the creator.
    Please can any one tell me the BAPI to get the attched document details and also possible tell me how to use that.
    Thanks and Regards
    Abinava Siri...

    goto table SRGBTBREL
    give RELTYPE = ATTA
    INSTID_A = give ur pr no. with pre-attachement of 00
    get details and use them in function module GOS_ATTACHMENT_LIST_POPUP

  • Details about net price calculation

    Hi,
    I have to do a report where when the user clicks on the net prices, a new window raises with details about it like prices, discounts, charges, tax, totals, etc.
    But I don't know where I could find these items, actually even I don't know how the net price is calculated, so I would be very grateful if someone could explain me which tables are used in this calculation, or where can I find the information I need.
    thanks in advance

    I believe all the information you need is in KONV.  For the tax example, if you look at the records in KONV where KAPPL = TX you will see a value in KBETR.  That is the tax rate.  It might not look like a tax rate.  For example, in our system 6% is stored as 60.00. 
    You really need to talk to someone who understands your pricing procedure.  They will be able to help you interpret the values you see in KONV.  Go to the following link to learn more about pricing procedures.
    http://help.sap.com/saphelp_46c/helpdata/en/69/72369adc56d11195100060b03c6b76/frameset.htm
    You can view the configuration for pricing by using transaction SPRO and go to Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control.  Specifically, look at the Pricing Procedures to help you understand how your pricing is setup.
    Maybe someone can find a FM for you to get the data as it looks on the pricing screen in the Billing document.  That would be helpful.
    Brian

  • Details about Process chain

    Details about Process chain

    Hi Vijay,
                Well the major components of Process chain is mentioned as under:-
    A process Chain is a sequence of processes in BI system that executes in the Background.
    Commonly Used Process Types
    1.  Start
    2.  Execute InfoPackage
    3.  DTP
    4.  Attribute Change Run
    5.  Save Hierarchy
    6.  Delete Index
    7.  Generate Index
    8.  Activate DSO data
    9.  Update DSO data
    10. Complete Deletion of Data Target Content
    11. Delete Entire Content of Linked Transactional DSO/ODS
    12. Initial Fill of New Aggregates
    13. Roll up of Filled Aggregates/BIA indexes
    14. Compression of InfoCubes
    15. Read PSA and Update Data Target
    16. AND
    17. OR
    18. XOR
    If you want to include a load process in the process chain, you need to have already created an InfoPackage.
    You cannot load flat file data from a client workstation in the background. For this reason, you have stored your data on an application server.
    Creating Process Chains
    You have the option of creating a process chain in the process chain maintenance screen directly or by using a maintenance dialog for a process:
    Creating a Process Chain Directly in the Process Chain Maintenance Screen
    You are in the BW Administrator Workbench.
           1.      Click on the  Process Chain Maintenance icon in the AWB toolbar.
    The Process Chain Selection dialog window appears.
           2.      Choose Create.
           3.      Enter the technical name and a description of the chain, and confirm your entry.
    The Add Start Process dialog window appears.
           4.      Create a variant for a start process.
    a.       On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
    b.       If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
    The Maintain Start Process screen appears again.
    c.       Save your entries, return to the previous screen and confirm your entries in the Add Start Process dialog window.
    You are taken to the  Plan View of the process chain maintenance screen.
    In the left-hand area of the screen, a navigation area is displayed. In the right-hand area of the screen, the process chain is displayed.
           5.      Use the drag-and-drop function to add the relevant processes into your process chain.
    You use the  Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate  InfoSources and  Data Targets navigation trees.
    If you insert into the chain a process that is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
    Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
    If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
    If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
    Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
    Creating a Process Chain Using the Maintenance Dialog for a Process
    You are in the maintenance dialog of a process that you want to include in a process chain.
           1.      Choose the Process Chain Maintenance pushbutton and create a process variant.
           2.      Save the variant and go back to the previous screen.
    A dialog window appears in which you enter a technical name and a description of the chain that you want to create.
           3.      Confirm your entries.
    The Add Start Process dialog window appears.
           4.      Create a variant for a start process.
    a.       On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
    b.       If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
    The Maintain Start Process screen appears again.
    c.       Save your entries, return to the previous screen and confirm your entries in the Add Start Process dialog window.
    You are taken to the  Plan View of the process chain maintenance screen.
    The various process categories, the application processes, and collection processes are displayed in the left-hand area of the screen. In the right-hand area of the screen, the process chain is displayed.
    If the process that you used to create a chain is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
    Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
    If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
    If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
    Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
           5.      Use the drag-and-drop function to insert any additional relevant processes into your process chain.
    You use the  Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate  InfoSources and  Data Targets navigation trees.
    Additional Steps to Creating a Process Chain
           6.      When you add a process, you need to select a process variant or create a new variant. For collection processes, the system determines the variants.
    Various functions for working with the process are available from the context menu:
    Context Menu Entry for a Process
    Function Information
    Maintain Variants
    With the exception of the variants in the collection process, you can use this function to change all process variants.
    Exchange Variants
    You can swap the variants for an existing variant or a new variant.
    Display Scheduled Jobs
    Once the process chain is active, you can use this function to display the jobs that have been scheduled.
    Display All Jobs
    After at least one run of the process chain, you can display, for a specific process, all of the scheduled jobs for this process and all of the jobs with which this process was run. You arrive at the job overview from where you call up the relevant job log.
    Create Message
    You can also send messages to an application process of the chain, depending on the success or failure of the process.
    1.       From the context menu of a process, create an additional process variant of the Send Message type.
    2.       If you maintain a message, first specify whether you want the message to be sent when the process has been completed successfully or unsuccessfully. Then choose Next.
    3.       You arrive at a window, in which you can select an existing process variant or create a new one.
    4.       If you create a new process variant, edit the document that is going to be sent, and maintain a list of recipients.
    5.       Save your process variant and go back a step.
    The message process variant is now assigned to your application process. When the message is sent, the status information and the process log can also be sent.
    Wait Time
    You use this function only to debug a process run.
    Specify how long (in seconds) you want the delay to be between one event being triggered and the next process starting.
    You can capture the process by using transaction SM37 (Job Overview) or SM50 (Process Overview).
    Remove Process
    You use this function to remove a process from a process chain.
    Manage Data Target
    You use this function in connection with the following types of process variants
    ·         constructing indexes
    ·         deleting indexes
    ·         constructing database statistics
    ·         rolling up filled aggregates
    ·         compressing InfoCubes
    ·         activating ODS object data
    to call up the administration for each of the data targets.
           7.      Hold down the left mouse button to connect the processes through events.
    Before you do this, select the process underneath the process type row, and position the cursor over the required process. When you select the process type row, the whole process is moved into the plan view.
    From the context menu of a link, you can display the event or remove the link again. To do this, highlight the link and right-click with the mouse.
           8.      If necessary, specify whether you want the event to be triggered after the previous process has been completed successfully or unsuccessfully or whether you want the event to be triggered independently of the outcome of the process that precedes it.
           9.      Under Attributes ®Display Components assign a display component to the process chain.
       10.      Maintain additional process chain attributes if necessary.
       11.      Check your process chain in the  Check View and make any necessary corrections.
    The  Legend explains the meaning of the different colors used to display the processes and links.
    From the context menu for a process, you can display the messages resulting from the check.
       12.      Save your process chain if it does not contain any errors.
    Result
    Your process chain can be activated. After activation, the chain starts in accordance with the start process selections. For example, if you scheduled the start process directly and chose Immediately as the start date value, the chain run starts immediately after activation.  In the  Log View, you can display the reports for the chain runs.

  • I have just started to use Muse for our design agency and learning how to build ourselves a new site, I have manged to create a basic lightbox which contains sliding images, what I need to do now is have a pop up window which goes into detail about the pr

    I have just started to use Muse for our design agency and learning how to build ourselves a new site, I have managed to create a basic lightbox which contains sliding images, what I need to do now is have a pop up window which goes into detail about the projects, what I would like is a piece of text  or icon that when you roll over it and then click a separate window pops up with additional information in, once finished reading the info you can then click to close the box, any advice on how to do this?

    The best way to do what you're asking is with the Composition widget. Start with the Tooltip preset, which, by default shows the info on rollover. You can change the option to show on click, which is what you're after. You can also add the close button or have the info disappear on rollout.
    David

  • Is there a way to find out details about, who approved the RMA on system using front end or back end?

    Is there a way to find out details about, who approved the RMA on system using front end or back end?

    But is there a way (simple or not-so-simple) to find
    out EVERY SINGLE FILE that's referenced on a
    timeline? (I have lots of stuff imported into the
    project that I know isn't used on any timeline, but
    I'm afraid of moving or deleting things for fear of
    never finding it again.)
    I'd love to get some sort of "printout" (a list or
    something) of every single file.
    There is, go to browser and cntrl click on any one of the columns,
    and select - show/source. A new column named "source" will pop up and will show where everything "lives". Click on the header at the top and it will justify the column as well. You'll notice this won't show anything for your seq.'s. of course, but will show stills/audio/motion files...
    Once you have the new column, you can drag it next to the "name" column and get a grab of it and print it if you like, or whatever.
    If you want to do this for just 1 seq., then can create a new bin and double click it to open it. Cntrl-A (select all) in your main seq. and just drag all into the new bin. You will see only what's in that seq. with the "source" column right next to it.
    From what I've read, you seem to get the MM thing and it's obviously what you'll need to do to archive as the guys said. But what your missing is a file path system to where everything resides.
    Hope this helps and that I've read you properly,
    Peace
    P-Book 1.5, 17" 2gsRAM   Mac OS X (10.4.4)   FCStudio

  • Is it possible to call std. SAP transaction from abap wd

    Is it possible to call std. SAP transaction from abap wd so that transaction appears and work as in gui? Without portal ofcourse.
    I know that using webgui and/or ITS it is possible so then it must be somehow possible....

    Hi,
    see Web Dynpro ABAP call transaction in the foreground and just carry out a simple search in this forum, then you'll find several threads with similar questions...
    Regards, Heidi

Maybe you are looking for