Controll of Table T090L in transaction AO25 used in FI-AA

Hi SDN
I am currently implementing Fixed assets and have a problem with the security on one of the key tables.
Table T090L accesable via transaction AO25 is a table that holds production and reserve values which are input by Fiscal period / year , however the table security is not controlled via the 'posting period vaiant' control (OB52).
The problem I have is that AO25 will allow you to change the values in prior years/periods even though those periods are now closed and the figures have been used in their appropriate calculations.
I wish to be able to restrict periods for user change to avoid prior period adjustments in line with OB52.
Any insight greatly appreciated
Regards
Mark

Hi
Yes - if you want to control access on line level S_TABU_DIS is the correct object.
But please notice that this object wil require you to implement note 76329, if your going to use it in SE16 - if access is provided through SM30 (or a parameter transaction based on this t-code), this note won't be relevant.
I have created a small How-to guide for customising S_TABU_LIN - you can find it here if interested
http://www.mortenhjorthnielsen.dk/Security/S_TABU_LIN.htm
Regards
Morten Nielsen

Similar Messages

  • WHATS THE USE OF TABLE STRIP CONTROL AND TABLE VIEW CONTROL

    WHATS THE USE OF TABLE STRIP CONTROL AND TABLE VIEW CONTROL

    Subhash,
    You create and distribute a model in BD64. The details of that are stored in this tables.
    A model gives you the details of the sender / receiving systems and what are the message types that are getting transferred between these systems.
    Regarding the IDOC segments issue, can you explaing how are you triggering the IDOC and which message / idoc type you are dealing with.
    Regards,
    Ravi
    Note :Please mark the helpful answers
    Message was edited by: Ravikumar Allampallam

  • How can I change the size of table control in table maintenance re-gen?

    Hello Experts,
    I hv created a maintenance view and after generated table maintenance view for it.
    now it adjusts the size of table control in table maintenance generation.
    I want to change the size (width) of table control and again re-generate the table maintenance.
    But when re-generation occurs, table control size is set to initial.
    why it is happening? and wt to do to solve this issue? any user exit?
    I need the changed size of table control even if its re-generated.
    Regards,
    R.Hanks

    Hello Ronny,
    Goto SM30, Enter your table name for which you have maintained your table maintainence generator .
    When the maintainence screen appears for your table name , Goto System->Status->Screen Program name.
    Copy that program name from there.
    Open that module program through SE80,this is the program name of your SM30 screen which appears when we enter our table name in SM30 transaction.
    In SE80,click the layout of the module program name you have entered there.
    Its layout will display you the table control(of SM30) present to enter your your enteries.
    In the change mode you can change its size , savee it and activate that program.
    Now goto to SM30 again and enter your table name, it will show you the changed size of the table control used to take the enteries.
    Note:This changed size is only for your table name and it will remain of its previous size for other table enteries.
    Hope it helps you.
    Thanks Mansi

  • Whats is table type ? whats the use of it in abap?

    hi,
    i am ahmed abap fresher,
         i want to know what is table type and whats the use of it. at what point/situation we utilize this table type.

    Hi Ahmed ,
    Table is apart of data dictionary.
    Table is a sort of container where we store data.
    For eg. you want to store customer record in the database.Now you will store that customer record against specific fields of the applicable table.
    You can create or see table by means of transaction code se11.
    There are 3 typesof tables available in SAP ABAP:
    1. Transparent table
    2. Pool table
    3. Cluster table.
    Transparent Table:
    A physical table definition in the database for the table definition which is stored in the ABAP Dictionary for transparent tables when the
    table is activated. The table definition is translated from the ABAP
    Dictionary to a definition of the particular database.
    Pooled table:
    Pooled tables can be used to store control data (e.g. screen sequences,
    program parameters or temporary data). Several pooled tables can be
    combined to form a table pool. The table pool corresponds to a physical
    table on the database in which all the records of the allocated pooled
    tables are stored.
    Cluster table:
    Cluster tables contain continuous text, for example, documentation.
    Several cluster tables can be combined to form a table cluster. Several
    logical lines of different tables are combined to form a physical record
    in this table type. This permits object-by-object storage or
    object-by-object access. In order to combine tables in clusters, at
    least parts of the keys must agree. Several cluster tables are stored in
    one corresponding table on the database.
    See the documetation at:
    http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f083446011d189700000e8322d00/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/81/415d363640933fe10000009b38f839/frameset.htm
    Reward if useful ...
    Regards ,
    Shankar GJ

  • Getting the final internal table of a transaction VA05

    Hi,
    Can anyone help me in getting the final internal table of a transaction VA05 when called from a program. I need to use to this internal table for further processing.
    Thanks in advance,
    Vinay.

    Hi,
    Not quite sure what you are after but the following may help.
    For a start VA05 uses FM RV_SALES_DOCUMENT_VIEW_3 to select it's data.  Your program could simply call this.  However, if you are doing a CALL TRANSACTION from your program to VA05 and you want to get the results back then you could utilise some 'old style' userexits available in VA05.
    Two choices here:
    1. At the end of FM RV_SALES_DOCUMENT_VIEW_3 there is a form END_MODIFICATION or
    2. When VA05 calls RV_SALES_DOCUMENT_VIEW_3 it performs a user sort MV75AFZ1(MV75AFZ1)
    Both of these belong to package VMOD which means you can modify them by simply registering the object in OSS (these are 'old style' exits before SMOD/CMOD and are prevelant in SD)
    From either of these you could EXPORT to memory for when control is returned back to your program.
    Thanks,
    Pete

  • Unable to Capture ALV output in an Internal Table, after CALL TRANSACTION

    Dear all,
    My requirement is to run multiple materials in T-code CK86_99 but as we know CK86_99 is only adequate to one material at a time.
    So, I want to capture the Output of the T-code in my Internal table with respect to all the Material Numbers I use in the Select-Options of my Z Program.
    Below is the Code I developed so far, but the Class
    cl_salv_bs_runtime_info=>get_data_ref(
            IMPORTING r_data = lf_ref ).
    is not capturing the Ouput...
    Please have a look and enlighten me how it could be solved.
    TABLES : mara.
    DATA : BEGIN OF wa_mara,
      matnr TYPE mara-matnr,
      END OF wa_mara.
    DATA: it_bdcdata TYPE TABLE OF bdcdata,
          wa_it_bdcdata LIKE LINE OF it_bdcdata,
          it_mara LIKE TABLE OF wa_mara.
    *      BELNR(10).
    FIELD-SYMBOLS:<fs_tab> TYPE ANY TABLE,
    <fs_line> TYPE any.
    DATA:lf_ref TYPE REF TO data,
         lf_ref1 TYPE REF TO data.
    SELECT-OPTIONS so_matnr FOR mara-matnr.
    PARAMETERS p_werks LIKE t001w-werks.
    *BELNR = 'Z92'. " Give Document Number here
    SELECT matnr FROM mara INTO TABLE it_mara WHERE matnr IN so_matnr.
    DATA opt TYPE ctu_params.
    LOOP AT it_mara INTO wa_mara.
      CLEAR wa_it_bdcdata.
    wa_it_bdcdata-program  = 'SAPMKKB0'.
    wa_it_bdcdata-dynpro   = '0300'.
    wa_it_bdcdata-dynbegin = 'X'.
      APPEND wa_it_bdcdata TO it_bdcdata.
      CLEAR wa_it_bdcdata.
    wa_it_bdcdata-fnam = 'BDC_CURSOR'.
    wa_it_bdcdata-fval = 'KKB0-MATNR'.
      APPEND wa_it_bdcdata TO it_bdcdata.
      CLEAR wa_it_bdcdata.
    wa_it_bdcdata-fnam = 'KKB0-MATNR'.
      wa_it_bdcdata-fval = wa_mara-matnr.
      APPEND wa_it_bdcdata TO it_bdcdata.
      CLEAR wa_it_bdcdata.
    wa_it_bdcdata-fnam = 'BDC_CURSOR'.
    wa_it_bdcdata-fval = 'KKB0-WERKS'.
      APPEND wa_it_bdcdata TO it_bdcdata.
      CLEAR wa_it_bdcdata.
      wa_it_bdcdata-fnam = 'KKB0-WERKS'.
    wa_it_bdcdata-fval = p_werks.
      APPEND wa_it_bdcdata TO it_bdcdata.
      CLEAR wa_it_bdcdata.
    wa_it_bdcdata-fnam = 'BDC_OKCODE'.
    wa_it_bdcdata-fval = 'OSNY'."'ONLI'."=CRET'.
      APPEND wa_it_bdcdata TO it_bdcdata.
    *  CLEAR wa_it_bdcdata.
    * wa_it_bdcdata-program  = 'SAPLKKRSOO'.
    * wa_it_bdcdata-dynpro   = '0100'.
    * wa_it_bdcdata-dynbegin = 'X'.
    *  APPEND wa_it_bdcdata TO it_bdcdata.
    *  CLEAR wa_it_bdcdata.
    * wa_it_bdcdata-fnam = 'BDC_OKCODE'.
    *  wa_it_bdcdata-fval = 'BACK'."=CRET'.
    *  APPEND wa_it_bdcdata TO it_bdcdata.
    *  CLEAR wa_it_bdcdata.
    * wa_it_bdcdata-program  = 'SAPMKKB0'.
    * wa_it_bdcdata-dynpro   = '0300'.
    * wa_it_bdcdata-dynbegin = 'X'.
    *  APPEND wa_it_bdcdata TO it_bdcdata.
    *  CLEAR wa_it_bdcdata.
    * wa_it_bdcdata-fnam = 'BDC_OKCODE'.
    * wa_it_bdcdata-fval = 'EXIT'."=CRET'.
    *  APPEND wa_it_bdcdata TO it_bdcdata.
      opt-dismode = 'N'.
    cl_salv_bs_runtime_info=>set(
        EXPORTING display  = abap_false
                  metadata = abap_true
    data     = abap_true ).
      CALL TRANSACTION 'CK86_99' USING it_bdcdata OPTIONS FROM opt.
      TRY.
    cl_salv_bs_runtime_info=>get_data_ref(
            IMPORTING r_data = lf_ref ).
          ASSIGN lf_ref->* TO <fs_tab>.
        CATCH cx_salv_bs_sc_runtime_info.
          MESSAGE 'Unable to retrieve ALV data' TYPE 'E'.
      ENDTRY.
    cl_salv_bs_runtime_info=>clear_all( ).
      IF <fs_tab> IS ASSIGNED.
        CREATE DATA lf_ref1 LIKE LINE OF <fs_tab>.
        ASSIGN lf_ref1->* TO <fs_line>.
      ENDIF.
    *LOOP AT <FS_TAB> ASSIGNING <FS_LINE>.
    *ENDLOOP.

    Hi Abhay,
          If you go to Transaction code SE93, enter the tcode "CK86_99" and click display, you may see the default value for transaction is "KKBB" and the screen field for P_SCREEN = 0300, P_TCODE = ck86_99.
          You may need to copy the transaction code "KKBB" and go to SE93 again, enter the tcode for "KKBB" then click display, now you may see the program name is "RKKB1000".
          Hope this answer your question.
    Thanks
    Hock Lin

  • Changes to sales order item not reflected if Call Transaction is used

    I m updating another Sales Order item quantity and reason for rejection programmatically from another sales order.
    The code is working fine and the quantity does get changed as well as the reason for rejection flag get set (if required). But if I go to the change log from the menu in VA02 for the order item which has been changed. It does not record the changes.
    I have tried using both BDC call transaction method as well as BAPI_SALESORDER_CHANGE in neither case the change log for the order which has been changed reflects the programmatically made changes?
    What m I doing wrong. Here is the code.
    IF v_update_order_flg = 'X'.
          REFRESH t_bdcdata.
          CLEAR s_bdcdata.
          REFRESH t_messtab.
          PERFORM bdc_dynpro USING 'SAPMV45A' '0102'.
          PERFORM bdc_field  USING 'VBAK-VBELN' <wa_r_rtb_posnrs>-zrtbvbeln.
          PERFORM bdc_field  USING 'BDC_OKCODE' '/00'.
          PERFORM bdc_dynpro USING 'SAPMV45A' '4001'.
       For Going to  specific Item Number
          LOOP AT t_schedule_lines.
            PERFORM bdc_field  USING 'BDC_OKCODE' '=POPO'.
            READ TABLE t_item_in WITH KEY itm_number = t_schedule_lines-itm_number.
            PERFORM bdc_dynpro USING 'SAPMV45A' '0251'.
            PERFORM bdc_field  USING 'RV45A-POSNR' t_schedule_lines-itm_number.
            PERFORM bdc_field  USING 'BDC_OKCODE' '=POSI'.
            PERFORM bdc_dynpro USING 'SAPMV45A' '4001'.
            v_ro_qty = t_schedule_lines-req_qty.
            CONDENSE v_ro_qty.
            PERFORM bdc_field  USING 'RV45A-KWMENG(01)' v_ro_qty.
            PERFORM bdc_field  USING 'VBAP-ABGRU(01)' t_item_in-reason_rej.
          ENDLOOP.
          PERFORM bdc_field  USING 'BDC_OKCODE' '=SICH'.
          v_call_transaction_flg = 'X'.
          EXPORT v_call_transaction_flg TO MEMORY ID 'call_transaction'.
          CALL TRANSACTION 'VA02'
                       USING t_bdcdata
                       UPDATE 'S'
                       MODE   'N'
                       MESSAGES INTO t_messtab.
          v_call_transaction_flg = space.
          FREE MEMORY ID 'call_transaction'.

    Hi Srikrisna,
    This is a typical problem with BDC for updating QUANTITY and CURRENCY fields.
    You need to create a character variable of the same length as your quantity field. Move your quantity value to the newly created Character variable.
    Now use this new char variable in the BDC.
    This correction should solve your problem.
    NOTE: BDC RECOGNIZES CHARACTER FIELDS ONLY.
    Regards,
    Prakash Pandey

  • Transaction type used for FA posting to depreciation area 01 (ordinary dep)

    Hi Expert,
    There is a difference between my ordinary dep area 01 and book dep area 03.
    area 01 is having a USD100
    area 03 is having zero USD
    I need to zerolized area 01.
    I have created a new TTY and limit the dep area posting to 01 in OAYA. However, when I tried to post via ABZE, it is giving me an error message AA350.
    Diagnosis
    According to Table T093A, if you use transaction type 050, area 03 has to adopt values from area 01 (chart of depreciation TPGL). However, the specifications made in Table TABWA for the two areas do not agree.
    Procedure
    Maintain the transaction type using the Customizing menu. Both areas have to have either the indicator 'propose for posting' or 'has to be posted'.
    I have checked both tables and it is not allowing me to post to area 01 only. I have done this before by creating a new TTY and post to area 02 and it works.
    Please advise soon how to rectify this.
    Thanks.
    Angel.

    Hi,
    please check ion OABC if area 02 takes over the values identically.
    regards Bernhard

  • What are the transactions we use day to day in the bw before go live

    what are the transactions we use most in the bw before go live?
    Tcodes for backend objects like creating infocube and so on.
    Tcodes for front end objects like creating queries and so on.
    Thank you.
    York

    Hi Les,
    check previous posting
    Transaction Codes for BW Developers
    SAP BW n R/3 transactions.
    table TSTCT contains all the transaction codes
    RSA6 Maintain DataSources
    RSA7 BW Delta Queue Monitor
    RSA8 DataSource Repository
    RSA9 Transfer Application Components
    RSD1 Characteristic maintenance
    RSD2 Maintenance of key figures
    RSD3 Maintenance of units
    RSD4 Maintenance of time characteristics
    RSDBC DB connect
    RSDDV Maintaining Aggregates
    RSIMPCUR Load Exchange Rates from File
    RSISET Maintain InfoSets
    RSKC Maintaining the Permittd Extra Chars
    RSLGMP Maintain RSLOGSYSMAP
    RSMO Data Load Monitor Start
    RSMON BW Administrator Workbench
    RSOR BW Metadata Repository
    RSORBCT BI Business Content Transfer
    RSORMDR BW Metadata Repository
    RSPC Process Chain Maintenance
    RSPC1 Process Chain Display
    RSPCM Monitor daily process chains
    RSRCACHE OLAP: Cache Monitor
    RSRT Start of the report monitor
    RSRT1 Start of the Report Monitor
    RSRT2 Start of the Report Monitor
    RSRTRACE Set trace configuration
    RSRTRACETEST Trace tool configuration
    RSRV Analysis and Repair of BW Objects
    SE03 Transport Organizer Tools
    SE06 Set Up Transport Organizer
    SE07 CTS Status Display
    SE09 Transport Organizer
    SE10 Transport Organizer
    SE11 ABAP Dictionary
    SE24 Class Builder
    SE80 Object Navigator
    RSCUSTA Maintain BW Settings
    RSCUSTA2 ODS Settings
    RSCUSTV*
    RSSM Authorizations for Reporting
    SM04 User List
    SM12 Display and Delete Locks
    SM21 Online System Log Analysis
    SM37 Overview of job selection
    SM50 Work Process Overview
    SM51 List of SAP Systems
    SM58 Asynchronous RFC Error Log
    SM59 RFC Destinations (Display/Maintain)
    LISTCUBE List viewer for InfoCubes
    LISTSCHEMA Show InfoCube schema
    DB02 Tables and Indexes Monitor
    DB14 Display DBA Operation Logs
    DB16 Display DB Check Results
    DB20 Update DB Statistics
    r/3 (bw related)
    SBIW BIW in IMG for OLTP
    BD61 Activate Change Pointers - Generally
    BDLS Convert Logical System Names
    BF11 Application Areas
    RSA2 OLTP Metadata Repository
    RSA3 Extractor Checker
    RSA5 Install Business Content
    RSA6 Maintain DataSources
    RSA7 BW Delta Queue Monitor
    RSA8 DataSource Repository
    RSA9 Transfer Application Components
    RSO2 Oltp Metadata Repository
    RSO3 Set Up Deltas for Master Data
    LO setup table
    OLI1BW INVCO Stat. Setup: Material Movemts
    OLI2BW INVCO Stat. Setup: Stor. Loc. Stocks
    OLI3BW Reorg.PURCHIS BW Extract Structures
    OLI4BW Reorg. PPIS Extract Structures
    OLI7BW Reorg. of VIS Extr. Struct.: Order
    OLI8BW Reorg. VIS Extr. Str.: Delivery
    OLI9BW Reorg. VIS Extr. Str.: Invoices
    OLIABW Setup: BW agency business
    OLIFBW Reorg. Rep. Manuf. Extr. Structs
    OLIIBW Reorg. of PM Info System for BW
    OLIQBW QM Infosystem Reorganization for BW
    OLISBW Reorg. of CS Info System for BW
    OLIZBW INVCO Setup: Invoice Verification
    Check out AHP's reply specifically in the link:
    urgent
    Assign Points if Helpful *****
    Regards,
    Ravikanth

  • Wrong path access table ESKN on transaction COHV

    Hallo.
    When I execute transaction COHV the performance are bad.
    I investigated and I found the statement:
    for example
    select * from eskn where mandt = '100' and aufnr = '1171132' and   loekz = ' ';
    very long beacause it doesn't use the index
    ESKN~G
    with column
    MANDT, AUFNR
    If I execute the statement:
    select * from eskn where aufnr = '1171132' and   loekz = ' ';
    index is used and statement are fast
    So it seems that the MANDT brings the problem.
    I have Oracle 11.2.0.2 and upgraded two months ago from Oracle 10.2.0.4
    When I was in Oracle 10.2.0.4 there wasn't the problem.
    Could you help me?
    Thanks.
    Mario

    I obtain:
    SQL> select distinct(AUFNR) from sapsr3.ESKN;
    AUFNR
    SQL>
    so no value it seems.
    I collect statistics using brtools:
    Detail log:                    cegxzqwd.sta
    BR0801I BRCONNECT 7.20 (16)
    BR0805I Start of BRCONNECT processing: cegxzqwd.sta 2011-10-06 16.49.59
    BR0484I BRCONNECT log file: F:\oracle\TES\sapcheck\cegxzqwd.sta
    BR0101I Parameters
    Name                           Value
    oracle_sid                     TES
    oracle_home                    F:\oracle\TES\11202
    oracle_profile                 F:\oracle\TES\11202\database\initTES.ora
    sapdata_home                   G:\oracle\TES
    sap_profile                    F:\oracle\TES\11202\database\initTES.sap
    system_info                    SAPServiceTES STESVV01 Windows 5.2 Build 3790 Service Pack 2 AMD64
    oracle_info                    TES 11.2.0.2.0 8192 552 3816993493 STESVV01 UTF8 UTF8 773218351
    sap_info                       700 SAPSR3 0002LK0003TES0011Z01163691220013NetWeaver_ORA
    make_info                      NTAMD64 OCI_10201_SHARE Aug  2 2011
    command_line                   brconnect -u / -c -f stats -o SAPSR3 -t ESKN -e null -m E -s P3 -f allsel,collect,method,sample,keep
    stats_owner                    SAPSR3
    stats_table                    ESKN
    stats_dbms_stats               ALL:R:0
    stats_method                   E
    stats_sample_size              P3
    stats_change_threshold         50
    stats_parallel_degree          1
    BR0280I BRCONNECT time stamp: 2011-10-06 16.50.02
    BR0813I Schema owner found in database TES: SAPSR3*
    BR0280I BRCONNECT time stamp: 2011-10-06 16.50.02
    BR0807I Name of database instance: TES
    BR0808I BRCONNECT action ID: cegxzqwd
    BR0809I BRCONNECT function ID: sta
    BR0810I BRCONNECT function: stats
    BR0811I Owner of database schema for processing: SAPSR3
    BR0812I Database objects for processing: ESKN
    BR0851I Number of tables with missing statistics: 1
    Owner SAPSR3: 1
    ESKN
    BR0852I Number of tables to delete statistics: 0
    BR0854I Number of tables to collect statistics without checking: 1
    Owner SAPSR3: 1
    ESKN
    BR0855I Number of indexes with missing statistics: 2
    Owner SAPSR3: 2
    ESKN0       ESKNG
    BR0856I Number of indexes to delete statistics: 0
    BR0857I Number of indexes to collect statistics: 0
    BR0853I Number of tables to check (and collect if needed) statistics: 0
    BR0862I Force option with value 'allsel,collect,keep,method,sample' set
    BR0126I Unattended mode active - no operator confirmation required
    BR0280I BRCONNECT time stamp: 2011-10-06 16.50.02
    BR0877I Checking and collecting table and index statistics...
    BR0280I BRCONNECT time stamp: 2011-10-06 16.50.02
    BR0881I Collecting statistics for table SAPSR3.ESKN with method/sample E/P3 ...
    BR0280I BRCONNECT time stamp: 2011-10-06 16.50.19
    BR0884I Statistics collected for table: SAPSR3.ESKN, rows old/new: -1/4881767
    BR0280I BRCONNECT time stamp: 2011-10-06 16.50.19
    BR0850I 1 of 1 object processed - 0.002 of 0.002 units done
    BR0204I Percentage done: 100.00%, estimated end time: 16:50
    BR0001I **************************************************
    BR0280I BRCONNECT time stamp: 2011-10-06 16.50.19
    BR0879I Statistics checked for 0 tables
    BR0878I Number of tables selected to collect statistics after check: 0
    BR0880I Statistics collected for 1/0 tables/indexes
    BR0894I Tables with the longest duration of collecting statistics for owner SAPSR3
      Pos. Owner    Table                Duration   Rows/old    Rows/new  Meth./Samp.   Space[KB]  Used[KB:%]    Data[KB:%]    Lobs   Space[KB]   Used[KB:%]    Data[KB:%]
                                           [m:s]
        1  SAPSR3   ESKN                    0:17          -1     4881767      E/P3            -1   1113112:100    901029:81       0          0          0:0           0:0
    BR0900I Usage of space allocated in tablespaces for analyzed tables and indexes
    Pos. Tablespace     Tables  Analy.  Space[KB]   Used[KB:%]     Data[KB:%]  Indexes  Valid.  Space[KB]   Used[KB:%]     Data[KB:%]    Lobs   Proc.  Space[KB]   Used[KB:%]     Data[KB:%]
      1  PSAPSR3            -1      1         -1    1113112:100     901029:81       -1      0          0          0:0            0:0       -1      0          0          0:0            0:0
    BR0806I End of BRCONNECT processing: cegxzqwd.sta 2011-10-06 16.50.19
    BR0280I BRCONNECT time stamp: 2011-10-06 16.50.19
    BR0802I BRCONNECT completed successfully

  • TABLES FOR MASTER & TRANSACTIONAL DATA

    Hi all ,
    can some body help me with TABLES FOR MASTER & TRANSACTIONAL DATA
    DP,SNP,PP/DP.
    Thanks

    Hi,
    You can find out it as per your requirement.
    Use transaction SE80 - ABAP workbench  -->
    select Repository Information system  -->
    Select ABAP Dictionary  --> Data base table -->
    In the right hand side window you will get screen in that give details as below
    Standard selection screen
    Table name : enter *
    In the Application Component:
    You will get Tree structure to Select Application Componenet
    in that expand the node of SCM --> SCM APO --> SCM-APO-MD for Master Data
    Here you will get application  -- Double click on the required Application
    e.g. Duble Click on SCM-APO-MD-PR for Product
    Here you will get list of table related to application componenet Product
    <b>/SAPAPO/MATKEY                 Product</b>
    Some of the Master Data Tables:
    /SAPAPO/APNTYPE                APN Type
    /SAPAPO/APNTYPET               Alternative Product Number Type
    /SAPAPO/APO01                  APO Planning Version
    /SAPAPO/APO01DEL               Deletion Log File Versions
    /SAPAPO/APPLOCS                Location Master: Relevant Location Types for Application
    /SAPAPO/APPLS                  Application Types : SAP Application Types
    /SAPAPO/CD_LOC                 Customizing Change Documents Location
    /SAPAPO/CD_PPRFL               Customizing: Change Documents: Product Profiles
    /SAPAPO/CD_PRDHD               Customizing: Change Documents: Product
    /SAPAPO/CD_PRDLC               Customizing: Change Documents: Location Product
    /SAPAPO/CD_PRDLW               Customizing: Change Documents: Storage Type Product
    /SAPAPO/CD_PRDWH               Customizing: Change Documents: Storage Type Product
    /SAPAPO/CONSPROF               Model Consistency Check: Check Profile
    /SAPAPO/CONSPROT               Model Consistency Check: Check Profile Descriptions
    /SAPAPO/CUSTCHK                Model Consistency Check: User-Specific Checks
    /SAPAPO/CUSTCHKT               Model Consistency Check: Descriptions of User-Spec. Checks
    /SAPAPO/GRPTYPE                Product Group Types
    /SAPAPO/GRPTYPET               Description of Product Grouping
    /SAPAPO/LOC                    Locations
    /SAPAPO/LOC_SUB                Mapping Table for Sublocations
    /SAPAPO/LOCCOMP                Table Obsolete Since SCM Release 4.1
    /SAPAPO/LOCMAP                 Mapping Table for Locations
    /SAPAPO/LOCMOT                 Location: Means-of-Transport-Dependent Attributes
    /SAPAPO/LOCPROF                Version-Dependent Location Profile for Penalty Determinati
    /SAPAPO/LOCT                   Locations Short Text
    /SAPAPO/LOCVER                 Location: Version-Dependent Fields
    /SAPAPO/LTTYPE                 Location Resources
    /SAPAPO/LTVER                  Location Resources: Version-Dependent Fields
    /SAPAPO/MARM                   Units of Measure
    /SAPAPO/MATAPN                 Alternative Product Number
    /SAPAPO/MATBOD                 Product BOD Assignment
    Hope this information will be helpful for you work on and find out Important tables for your own BP

  • Problem with maintain table views SM30 Transaction

    Hello All,
    i have a problem with the table maintenance view SM30, it doesn't permit me to modify the rows in the table.
    we have added a field into the table and when i tried to change the table view from menu: Utilities ==> table maintenance generator==> change the system propose me a message that the screen 0001 will be deleted and recreated...but the system has deleted the screen and doesn't recreate it...in somewehere on internet we find that we should use the transaction SE55 menu:
    Environment==> modification ==> Maintenance screen ==> button Layout which open the tool Screen Painter and from that we have created our screen with 4 fields of our table...our result that the screen is created and i can see it from the SM30 transaction but i can't insert rows in the table...when i try to go to maintain table: menu: Utilities ==> Table maintenance generator to try if i can modify something the system give me a message: "set the compare flag dialog ZIV_DP_PLCHAR_LA"
    the ZIV_DP_PLCHAR_LA is the name of my table...
    can you give me some advices please how should i do to fix this problem to insert rows in table throughout the transaction
    SM30 "maintain table views: initial screen"
    if i want to delete the screen from the SE55 transaction to recreate it newly what should i do to take care about some options
    to have a new screen?
    thanks for all
    Bilal

    Hi
    First delete the old table maintainence generator.
    Now Recreate the screen and your table is good to go..
    These error messages come when we add new fields and different version of the table maintainence generator in database.

  • Saving data into two tables "in one transaction"

    Hello everybody!
    My scenario is the following: SAP PI receives message containing some data (header and MULTIPLE details data in one message) and has to transfere this data to a database.
    In the database there are two tables for storing the data contained in the message: one for HEADER data and one for DETAILS data. I need to save all the data (header and MULTIPLE details data) into these two tables "in one transaction" and roll back saving of HEADER data and DETAILS data if saving of some DETAILS data has failed.
    I am going to use receiver JDBC adapter for this purpose.
    My questions are:
    1. How can I save all the data "in one transaction"? Will it work if I transform the source message into the target message which looks something like this?
    <root>
      <StatementName1>
        <dbTableName action=u201CUPDATE_INSERTu201D>
        <table>HEADER_table</table>
        <access>
        <col1>val1</col1>
        <col2>val2</col2>
        </access>
        <key1>
        <col1>val1</col1>
        </key1>
        </dbTableName>
      </StatementName1>
      <StatementName2>
        <dbTableName action=u201CUPDATE_INSERTu201D>
        <table>DETAILS_table</table>
        <access>
        <col1>val1</col1>
        <col2>val3</col2>
        </access>
        <key1>
        <col1>val1</col1>
        </key1>
        </dbTableName>
      </StatementName2>
      <StatementName3>
        <dbTableName action=u201CUPDATE_INSERTu201D>
        <table>DETAILS_table</table>
        <access>
        <col1>val1</col1>
        <col2>val4</col2>
        </access>
        <key1>
        <col1>val1</col1>
        </key1>
        </dbTableName>
      </StatementName3>
    </root>
    2. How to roll back saving of HEADER data in the case of saving of DETAILS data has failed?
    3. What will be the response structure returned by database look like in the case of success?
    Thanks,
    Vika

    I guess the response in my case will be something as following?
    <response>
    <Statement1_response>
    <row>
    <update_count>1</update_count>
    <insert_count>0</insert_count>
    </row>
    </Statement1_response>
    <Statement2_response>
    <row>
    <update_count>0</update_count>
    <insert_count>1</insert_count>
    </row>
    <row>
    <update_count>0</update_count>
    <insert_count>1</insert_count>
    </row>
    </Statement2_response>
    </response>
    Vika

  • Event ID 1114: Table was marked as in use while releasing a database session...

    I'm running Exchange 2010 SP2 RU1 in a two node DAG. 
    All the databases are mounted and healthy. Running ESEUTIL /G returned no errors (just some warnings about "orphaned scrubbed LV(401) detected" and said an offline defrag would fix it). Running ESEUTIL /K on the databases comes back clean as well.
    For about two weeks now I've been getting clusters of 1114 warnings in the Application log of the server which has the active database. Unfortunately, I've been almost completely unable to find any information on this warning; the one thing I was able to
    find pointed to a harmless issue with Advanced Search in Outlook 2007/2010, but that was fixed in SP1 RU4. 
    Any ideas? At this point I think I'm ready to just create a new database and move my mailboxes over.
    Log Name:      Application
    Source:        MSExchangeIS Mailbox Store
    Date:          5/17/2012 12:41:13 PM
    Event ID:      1114
    Task Category: General
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      Exchange1.HQ.Donohoe
    Description:
    Table was marked as in use while releasing a database session on database "DCC".  Problem will automatically be fixed.
     Table type was tbtBody, table name was Body-30a6-165EB03, and transaction level was 0. 
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeIS Mailbox Store" />
        <EventID Qualifiers="32774">1114</EventID>
        <Level>3</Level>
        <Task>6</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-05-17T16:41:13.000000000Z" />
        <EventRecordID>45433</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Exchange1.HQ.Donohoe</Computer>
        <Security />
      </System>
      <EventData>
        <Data>tbtBody</Data>
        <Data>Body-30a6-165EB03</Data>
        <Data>0</Data>
        <Data>DCC</Data>
      </EventData>
    </Event>

    Same here. Outlook 2013 seems to be the problem.
    Has anybody got any idea?<o:p></o:p>
    What I’ve done so far:
    checked and repaired corruption on the edb
    offline defrag
    updated to SP3<o:p></o:p>
    The
    problem still persists.
    Just ignore it.

  • Can we record two transactions and use for  a Call-transaction BDC?

    can we record two transactions and upload data using Call-transaction method in BDC ?IF not why?

    Hi Prakash,
    Here i used two transactions.
    REPORT zra_gl_cr NO STANDARD PAGE HEADING LINE-SIZE 255.
    TYPE-POOLS: truxs.
    DATA: it_raw TYPE truxs_t_text_data.
    DATA:messtab1 LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
    DATA:messtab LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
    DATA: bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.
    DATA: BEGIN OF i_mess OCCURS 0,
      l_mstring(480),
      msgnr(5),
      msgv1(15),
      END OF i_mess.
    DATA:i_mess1 LIKE i_mess OCCURS 0 WITH HEADER LINE.
    DATA: l_mstring(480),l_mstring1(480).
    DATA: BEGIN OF it_itab OCCURS 0,
          saknr(10),    "G/L a/c number.
          bukrs(4),     "Company Code.
          ktoks(4),     "G/L a/c group.
          xplacct(1),   "P&L statement account.
          xbilk(1),     "Balance sheet account.
          txt20_ml(20), "G/L a/c short text.
          txt50_ml(50), "G/L a/c long text.
          waers(5),     "Account currency.
          MWSKZ(2),
          mitkz(1),     "Reconciliation a/c for a/c type.
          xopvw(1),     "Open item management
          xkres(1),     "Line item display.
          zuawa(3),     "Sort Key.
          fstag(4),     "Field status group.
          xintb(1),     "Post automatically only.
          hbkid(5),     "House bank.
          hktid(5),     "Account id.
          vzskz(2),     "Interest indicator
          END OF it_itab.
    DATA: hdate LIKE sy-datum.
                          Selection Screen                       *****
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 5(15) text-103. " FOR FIELD P_FILE1.
    SELECTION-SCREEN POSITION 25.
    PARAMETERS : p_file1 LIKE rlgrap-filename.
    SELECTION-SCREEN END OF LINE.
                          Initialization                         *****
    INITIALIZATION.
                       At Selection Screen                       *****
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file1.
    Perform file_selection will help to select the location of the file
      PERFORM file_selection.
                       Start-Of-Selection                        *****
    START-OF-SELECTION.
    Perform data_upload will help to upload the data from the flat file
    to the internal table.
      PERFORM data_upload.
    PERFORM open_group.
       Peform bdc_upload will help to upload the data from the internal
       table into its respective fields.
    PERFORM bdc_fspo.
      PERFORM bdc_upload.
      PERFORM exp_log.
    PERFORM close_group.
       Perform display_log will prepare a log for the data that has been
       uploaded
       PERFORM display_log.
                        End-Of-Selection                           ****
    END-OF-SELECTION.
    *&      Form  file_selection
          To select the location of the file
    FORM file_selection .
      CALL FUNCTION 'WS_FILENAME_GET'
        EXPORTING
          def_filename     = ' '
          def_path         = 'C:\'
          mask             = ',.txt,.xls.'
          mode             = 'O'
          title            = 'Open a excel file'
        IMPORTING
          filename         = p_file1
        EXCEPTIONS
          inv_winsys       = 1
          no_batch         = 2
          selection_cancel = 3
          selection_error  = 4
          OTHERS           = 5.
    ENDFORM.                    " file_selection
    *&      Form  data_upload
         To upload the data from the file location to the internal table.
    FORM data_upload .
      CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
        EXPORTING
        I_FIELD_SEPERATOR        =
          i_line_header            =  'X'
          i_tab_raw_data           =  it_raw
          i_filename               =  p_file1
        TABLES
          i_tab_converted_data     = it_itab
       EXCEPTIONS
          conversion_failed        = 1
          OTHERS                   = 2.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
    ENDFORM.                    " data_upload
    *&      Form  bdc_upload
    To upload the data from the internal table into its respective fields.
    FORM bdc_upload .
      LOOP AT it_itab.
    perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=ACC_CRE'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'GLACCOUNT_SCREEN_KEY-SAKNR'.
    perform bdc_field       using 'GLACCOUNT_SCREEN_KEY-SAKNR'
                                  it_itab-SAKNR.
    perform bdc_field       using 'GLACCOUNT_SCREEN_KEY-BUKRS'
                                  it_itab-BUKRS.
    perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=2102_GROUP'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'GLACCOUNT_SCREEN_COA-KTOKS'.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-KTOKS'
                                  it_itab-KTOKS.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-XPLACCT'
                                  it_itab-XPLACCT.
    perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=2102_BS_PL'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'GLACCOUNT_SCREEN_COA-XBILK'.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-KTOKS'
                                  it_itab-KTOKS.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-XPLACCT'
                                 it_itab-XPLACCT.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-XBILK'
                                  it_itab-XBILK.
    perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=ENTER'.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-KTOKS'
                                  it_itab-KTOKS.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-XBILK'
                                  it_itab-XBILK.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-TXT20_ML'
                                  it_itab-TXT20_ML.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-TXT50_ML'
                                 it_itab-TXT50_ML.
    perform bdc_field       using 'BDC_CURSOR'
                                  'GLACCOUNT_SCREEN_COA-BILKT'.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-BILKT'
                                  it_itab-saknr.
        PERFORM bdc_dynpro      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=TAB02'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'GLACCOUNT_SCREEN_COA-KTOKS'.
        PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                                       it_itab-ktoks.
        PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-TXT20_ML'
                                       it_itab-txt20_ml.
        PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-TXT50_ML'
                                       it_itab-txt50_ml.
        perform bdc_field       using 'BDC_CURSOR'
                                  'GLACCOUNT_SCREEN_COA-BILKT'.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-BILKT'
                                  it_itab-saknr.
    perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=TAB02'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'GLACCOUNT_SCREEN_COA-KTOKS'.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-KTOKS'
                                     it_itab-KTOKS.
    perform bdc_field       using 'BDC_CURSOR'
                                  'GLACCOUNT_SCREEN_COA-KTOKS'.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-KTOKS'
                                  it_itab-KTOKS.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-XBILK'
                                 it_itab-XBILK.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-TXT20_ML'
                                  it_itab-TXT20_ML.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-TXT50_ML'
                                  it_itab-TXT50_ML.
    perform bdc_field       using 'GLACCOUNT_SCREEN_COA-BILKT'
                                 it_itab-saknr.
    perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=ENTER'.
    perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-WAERS'
                                  it_itab-waers.
    perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-MWSKZ'
                                  it_itab-MWSKZ.
    perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-MITKZ'
                                  it_itab-mitkz.
    perform bdc_field       using 'BDC_CURSOR'
                                  'GLACCOUNT_SCREEN_CCODE-XOPVW'.
    perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-XOPVW'
                                  it_itab-XOPVW.
    perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-XKRES'
                                  it_itab-XKRES.
    perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
                                 it_itab-ZUAWA.
        PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                                       it_itab-xplacct.
        PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-XBILK'
                                       it_itab-xbilk.
           IF it_itab-xbilk = 'X'.
       PERFORM bdc_dynpro USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
       PERFORM bdc_field       USING 'BDC_OKCODE'
                                     '=TAB03'.
       PERFORM bdc_field       USING 'BDC_CURSOR'
                                     'GLACCOUNT_SCREEN_CCODE-WAERS'.
       PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-WAERS'
                                      it_itab-waers.
         PERFORM bdc_field USING 'GLACCOUNT_SCREEN_CCODE-XOPVW'
                                  it_itab-xopvw.
         PERFORM bdc_field USING 'GLACCOUNT_SCREEN_CCODE-MITKZ'
                                  it_itab-mitkz.
       ENDIF.
       PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-XKRES'
                                      it_itab-xkres.
       PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
                                      it_itab-zuawa.
       PERFORM bdc_dynpro      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
       PERFORM bdc_field       USING 'BDC_OKCODE'
                                     '=SAVE'.
       PERFORM bdc_field       USING 'BDC_CURSOR'
                                     'GLACCOUNT_SCREEN_CCODE-FSTAG'.
       PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-FSTAG'
                                      it_itab-fstag.
       PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-XINTB'
                                      it_itab-xintb.
       PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-HBKID'
                                      it_itab-hbkid.
       PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-HKTID'
                                      it_itab-hktid.
       PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-VZSKZ'
                                      it_itab-vzskz.
    perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=TAB03'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'GLACCOUNT_SCREEN_CCODE-WAERS'.
    perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-WAERS'
                                  it_itab-WAERS.
    perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-MWSKZ'
                                  it_itab-MWSKZ.
    perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-MITKZ'
                                  it_itab-MITKZ.
    perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
                                 it_itab-ZUAWA.
    perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=ENTER'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'GLACCOUNT_SCREEN_CCODE-FSTAG'.
    perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-FSTAG'
                                 it_itab-FSTAG.
    perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=SAVE'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'GLACCOUNT_SCREEN_CCODE-FSTAG'.
    perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-FSTAG'
                                  it_itab-FSTAG.
       PERFORM bdc_transaction USING 'FS00'.
        CALL TRANSACTION 'FS00' USING bdcdata MODE 'A'
                                              UPDATE 'S'
                                             MESSAGES  INTO messtab1.
        PERFORM mess1.
        REFRESH bdcdata[].
      ENDLOOP.
    ENDFORM.                    " bdc_upload
    *&      Form  bdc_fspo
          text
    FORM bdc_fspo .
      LOOP AT it_itab.
        PERFORM bdc_dynpro      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=ACC_CRE'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'GLACCOUNT_SCREEN_KEY-SAKNR'.
        PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_KEY-SAKNR'
                                      it_itab-saknr.
        PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_KEY-KTOPL'
                                      '1000'.
        PERFORM bdc_dynpro      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=2102_GROUP'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'GLACCOUNT_SCREEN_COA-KTOKS'.
        PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                                      it_itab-ktoks.
        PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                                       it_itab-xplacct.
        PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-XBILK'
                                      it_itab-xbilk.
        PERFORM bdc_dynpro      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=SAVE'.
        PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                                       it_itab-ktoks.
        PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                                       it_itab-xplacct.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'GLACCOUNT_SCREEN_COA-TXT50_ML'.
        PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-TXT20_ML'
                                       it_itab-txt20_ml.
        PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-TXT50_ML'
                                       it_itab-txt50_ml.
    *perform bdc_transaction using 'FSP0'.
        CALL TRANSACTION 'FSP0' USING bdcdata MODE 'A'
                                              UPDATE 'S'
                                             MESSAGES  INTO messtab.
        PERFORM mess.
        REFRESH bdcdata[].
      ENDLOOP.
    ENDFORM.                    " bdc_fspo
    *&      Form  mess
          text
    -->  p1        text
    <--  p2        text
    FORM mess .                                                 "fsp0
      LOOP AT messtab.
        CALL FUNCTION 'FORMAT_MESSAGE'
          EXPORTING
            id        = messtab-msgid
            lang      = messtab-msgspra
            no        = messtab-msgnr
            v1        = messtab-msgv1
            v2        = messtab-msgv2
            v3        = messtab-msgv3
            v4        = messtab-msgv4
          IMPORTING
            msg       = l_mstring
          EXCEPTIONS
            not_found = 1
            OTHERS    = 2.
        CONDENSE l_mstring.
        i_mess1-l_mstring = l_mstring(250).
        i_mess1-msgnr = messtab1-msgnr.
        i_mess1-msgv1 = messtab1-msgv1.
        APPEND i_mess1.
      ENDLOOP.
    ENDFORM.                    " mess
    *&      Form  mess1
          text
    -->  p1        text
    <--  p2        text
    FORM mess1 .                                                "fs00
      LOOP AT messtab1.
        CALL FUNCTION 'FORMAT_MESSAGE'
          EXPORTING
            id        = messtab1-msgid
            lang      = messtab1-msgspra
            no        = messtab1-msgnr
            v1        = messtab1-msgv1
            v2        = messtab1-msgv2
            v3        = messtab1-msgv3
            v4        = messtab1-msgv4
          IMPORTING
            msg       = l_mstring1
          EXCEPTIONS
            not_found = 1
            OTHERS    = 2.
        CONDENSE l_mstring1.
        i_mess-l_mstring = l_mstring1(250).
        i_mess-msgnr = messtab1-msgnr.
        i_mess-msgv1 = messtab1-msgv1.
        APPEND i_mess.
      ENDLOOP.
    ENDFORM.                                                    " mess1
    *&      Form  exp_log
          text
    -->  p1        text
    <--  p2        text
    FORM exp_log .
      CALL FUNCTION 'GUI_DOWNLOAD'
        EXPORTING
          filename = 'c:\temp\error_fsp0.txt'
          filetype = 'DAT'
        TABLES
          data_tab = i_mess1.
      CALL FUNCTION 'GUI_DOWNLOAD'
        EXPORTING
          filename = 'c:\temp\error_fs00.txt'
          filetype = 'DAT'
        TABLES
          data_tab = i_mess.
    ENDFORM.                    " exp_log
    *&      Form  bdc_dynpro
          text
         -->PROGRAM    text
         -->DYNPRO     text
    FORM bdc_dynpro USING program dynpro.
      CLEAR bdcdata.
      bdcdata-program  = program.
      bdcdata-dynpro   = dynpro.
      bdcdata-dynbegin = 'X'.
      APPEND bdcdata.
    ENDFORM.                    "BDC_DYNPRO
           Insert field                                                  *
    FORM bdc_field USING fnam fval.
      CLEAR bdcdata.
      bdcdata-fnam = fnam.
      bdcdata-fval = fval.
      APPEND bdcdata.
    ENDFORM.                    "BDC_Field
    ********Rewards some points.

Maybe you are looking for