Cross client tables

Hi,
I am trying to authorize a user for maintaining the cross client tables with SM30.
I have added the Authorization object S_TABU_CLI with the change permission and regenerated
the profile and assigned to the user. But the user is still unable to maintain the cross client tables
like V_DDAT. How to enable a user to maintain cross client tables.
Thanks in Advance,
Ramakrishna.

One thing. I saw in your response that you have not assigned an authorization group on S_TABU_DIS?
This is necessary, as the system always checks on the auth group.
If the table is not classified in TDDAT, it will check against &NC&.
Tables are protected through S_TABU_DIS for client-dependant tables AND S_TABU_CLI as extra protection fro cross-client tables.

Similar Messages

  • How to disable Cross client Table Access

    Hi All,
    i have created a Sand box client and i have set its cross client object value to
    "No Changes to repository and cross client customizing objs"
    but still users are able to run transactions like SR13 which are cross client tables
    please help

    HI Zeeshan,
    Once u run the Tcode like SR13, the users would be able to enter the Tcode and have a new entry varinat created..but during SAVE the system would sure prompt the message... " Changes to Repository or cross-client Customizing are not allowed. Please press DISPLAY or CANCEL" ..
    so the changes would not be saved hence forth and have to be cancelled out..
    hope this is what u have been looking for..
    Br,
    Sri
    Award points for helpful answers

  • Merging SAP Clients - Reporting on Cross Client Table Compare Results

    Hey folks,
    We are trying to merge two clients into one (on the cheap), i think that cross client table comparision is the best way to find differences and possible issues and clashes with the two systems configuration, but i was wondering if there is anyway to report on these differences, so we can pull them out to word/excel document to anaylse and document them prior to making the changes.
    Does anyone know if this possible?
    Thanks a lot,
    Greg

    Hello Mr. Newman,
    I think using SCU0 is going to be the way to go but the output is not always the best. However you should be able to show the differences and download to excel to analyse further. If this doens't fit then I think you will have to look at copying the tcode / report and improving the output to meet your needs.
    Alternatively post to basis folks and see if they have some better ideas!
    Hope this helps,
    Cheers,
    Dan
    Edited by: Danny boy on Mar 31, 2010 3:00 PM

  • How to create a cross-client table maintenance dialog?

    Hello everybody,
    I have a client specific table (mandt is the first key field) that should be maintained cross-client: In the table maintenance dialog, I want to change/create/insert values belonging to clients other than the current logon client. Can I do this with a generated maintenace dialog? If yes, how?
    Thank you for your help, regards, Kathrin!

    Hi Kathrin,
    I think you can't, you must create your own dialog maintenance program.
    They are some program to copy data from client to others .. but never seen any dialog cross client. (or remove the mandt  in your key).
    Regards
    Frédéric

  • Cross client database tables

    Hi ,
    can someone please let me know any cross client database tables in SAP R/3..
    Thanks,
    Raghav

    Hi Raghavendra Manchippa  ,
    Any table which have a field MANDT and it should be Primary Key so that table be Cross Client Table..
    If satisfied,,,rewards me..
    Kind Regards
    Yogesh Gupta

  • What r crosss-client tables??

    what r crosss-client tables?? is it the same as client independent table

    Hi Prasanth,
    Cross client tables are client independent tables.
    These tables hold data that is influenced by business processes, such as
    1) Data that represents the organizational structures of the enterprise and
    2) Parameters that control business processes
    Thanks,
    Vinay

  • Cross-client activation issue with LBWE

    Hi,
    I am running into the same problem as the following links:
    Problem with setup table fillup
    Cross-client problem
    We have the configuration client 300 and the loading client 310. The structures in client 100 are active but are inactive in client 310. The first link says that I have to go into LBWE in the loading client to activate the structures, but I have the same issue relating to the second link. This is happening in the DEV system.
    Is the fix for the second issue relating to Basis who would allow me to do the activation on the loading client - opening the system for me to activate? Or is it the Developer's issue to find the workaround?
    I don't see why the restriction on the configuration for DEV client systems. This is for BW related Configuration issues and nothing is relating to SAP Business Configuration that had to be so restricted.
    Please advise how to get the inactive structures to be active in the loading client.
    Thanks

    Hi,
    It is a very common issue.  You can solve it by logging in to 310 client, going to SCC1 transaction and replicating changes from the transport orders that you created in the other DEV client.
    It's like transporting from one DEV client to the other, but please note that the request does not need to be released.
    I hope this helps.
    Best regards,
    Maximiliano Ariel López

  • Cross client data read

    Hi Experts
    select * from zemp
             into corresponding fields of table itab
             where sy-mandt = 391.
    Can we read data of database table from cross clients.
    i used abv query, says error.
    regards
    Rajaram

    Hi
    I trid as follows
    SELECT * FROM zemp CLIENT SPECIFIED INTO table itab
    WHERE MANDT = '392'.
    But am getting the error as follows,
    The work area "ITAB" is not long enough. long enough.
    What could be the reason,
    regards
    Rajaram

  • SAP BI Cross Client

    Hi SDN Guru,
    Actualy my Customer using 3 Landscape in ECC Systems Dev,Qty, Prd. But in SAP BI using only two Landscape
    Dev & Prod.
    Actualy Mapping with  ECC Dev to  BI Dev Sys , But, Unfortunately my management asking please collect the data from ECC QTY to BI Dev.
    We have only data's avilable ECC Qty, there is no data in ECC Dev.
    My Question is how to collect the data in different Client (or) Cross Client.
    *how to connect cross client then how to extract the data from ECC Qty to BI Dev System.
    Can you please provide me solution ASAP...
    Thanks in Adance Guru's.
    Regards,
    Kumar

    Hi,
    You have to map your ECC QUA to BI Dev system.
    Communication Setting between BW and R/3
    Step 1: Define Logical System in R/3
    Step 2: Assigning Logical System to Client
    Step 3: Setting Up an RFC Destination
    Step 4: Distributing Data Model
                  Message Types Involved in Process of Data Loading
    Step 5: Generating Partner Profile
    Step 6: Maintaining Message types in T-Code WE20
    Cross check the system mappings in RSLOGSYSMAP table in both systems.
    You can search some step by step docs in SDN.......
    Regards,
    Suman

  • Cross-Client

    hi..
    what is cross-client...?
    plz explain me clearly..
    thnx.
    Ashraf

    hi,
    cross-client is associated with tables..the data of which tables are accessable from all the clients or you can say it to be central data source.the tables which dont have MANDT field you can say it to be cross client
    regards,
    pankaj singh
    <b>**** reward all helpful answers</b>

  • Split database to client specific and cross client

    Hi
    Do we have a known method to split an existing MaxDB database into two .
    1. Client Specific database
    2. Cross client database
    Thanks and Regards
    Sri

    What you can do is to use TDMS (Test Data Migration Server), it´s a separate product and it enable you to setup test/training systems with a reduced amount of production data.
    This system makes use of technologies to determine, whether a table is client depend and client independent.
    Your problem is, that the client specific data NEEDS the cross client data, it relies on the customizing, that is cross client.
    If your pupose is to e. g. extract some kind of data because parts of your company was sold or if you bought a new company, then you should contact the SLO group (http://service.sap.com/slo) that does those kinds of "separations" too.
    From a technical level, it´s certainly possible but wihtout knowing your initial intent why you want to do that, one can give just advises, what we "think" what the reason might be.
    Markus

  • What is meant by cross client

    hai
        waht is meant by cross client while defining new table?
    hav a nice time

    Hi,
    The changes that you make in the ABAP Workbench are placed in the Repository tables of the SAP database. The contents of these tables are known as Repository data or Repository objects. Apart from a few exceptions, the Repository data is cross-client. As with cross-client Customizing, changes to Repository objects affect all clients of an SAP System
    Tables which are having MANDT field is called as client dependent tables. Tables which are not having MANDT field is called as client dependent tables.
    Client independent
    a table/object that is valid for all clients in a system. E.g table SCC4. This table will be the same no matter which client you view it from. If you try to make changes in SCC4, you'll get a popup with a warning that the table is cross client.
    Client dependent
    a table/object that is only valid for the client it is changed in. E.g the user tables USR*. You have to create users in each client.
    Hope it helps. Please reward if useful.
    Thanks & Regards
    Sadhu Kishore

  • Error while creating Cross-reference table using Xreftool (PIP Ins)

    Error while running xref.sh script unable to create cross reference table.
    **Error: Exception in thread "main" java.lang.NoClassDefFoundError: oracle/tip/xref/tool/AdminTool**
    Could not find xref directory within tip folder (/OracleAS_1/bpel/docs/workflow/oracle/tip)
    searched for similar issue in OTN it says issue fixed by upgrading Oracle AS, we are using 10.1.3.4 MLR#8
    http://kr.forums.oracle.com/forums/thread.jspa?threadID=835446
    steps followed.
    Creating Cross-Reference Tables
    Complete the following procedure to create cross-reference tables.
    To create cross-reference tables
    1 Navigate to the following directory:
    %SOAHOME%/SiebelODOPPIP/scripts/
    2 Open the following file for editing:
    xref.sh
    3 Set the userid and passwd for logging into BPEL console on the appropriate lines.
    4 Set the correct SOA_HOME location on the appropriate line.
    5 Save and close the file.
    6 Make the file executeable:
    chmod +x xref.sh
    dos2unix xref.sh
    7 Change directory (cd) to integration/esb/bin under %SOAHOME%.
    8 Execute ../../../SiebelODOPPIP/scripts/xref.sh.
    I am using SOA suite 10.1.3.3 and getting same error
    Error: Exception in thread "main" java.lang.NoClassDefFoundError: oracle/tip/xref/tool/AdminTool

    Hi Abhijeet,
    please check in transaction FI01, about your data consistencies. You can use this wiki help in terms of Address, it it found any useful facts for you
    Address Checks - Business Address Services (BC-SRV-ADR) - SAP Library

  • How to create cross-client variant?

    Hi Experters:
    Can someone tell me how create cross-client variant in ECC6.0?
    in 4.6, we can define the client or define cross-client transaction variant,
    how to create cross-client variant in ECC6.0?
    Regareds,

    Hi,
    In se93 there is a check box cross-client .
    The Cross-client switch identifies which transaction variants are cross-client and which are client-specific. If the switch is set, the transaction variant is cross-client. If the switch is not set, the transaction variant is client-specific.
    A client-specific transaction variant can only exist in the client where it was created. The field contents of the transaction variant only have to be available in the particular client. A cross-client transaction variant is available in the system regardless of which client is currently active. The field contents of the transaction variant have to be available in all clients.
    http://****************/Tutorials/ABAP/TransactionVariant/Create.htm

  • Urgent: Error-Record 39,779, segment 0001 is not in the cross-record table

    Hi Gurus,
    This is an urgent production issue: I got the following error-
    I am updating data records from a DSO to Infocube in delta mode,
    1.Record 39,779, segment 0001 is not in the cross-record table
    2.Error in substep: End Routine
    I dont know problem is in the End Routine or somewhere else,
    The End routine is this:
    PROGRAM trans_routine.
          CLASS routine DEFINITION
    CLASS lcl_transform DEFINITION.
      PUBLIC SECTION.
    Attributs
        DATA:
          p_check_master_data_exist
                TYPE RSODSOCHECKONLY READ-ONLY,
    *-    Instance for getting request runtime attributs;
        Available information: Refer to methods of
        interface 'if_rsbk_request_admintab_view'
          p_r_request
                TYPE REF TO if_rsbk_request_admintab_view READ-ONLY.
      PRIVATE SECTION.
        TYPE-POOLS: rsd, rstr.
      Rule specific types
        TYPES:
          BEGIN OF tys_TG_1,
         InfoObject: ZVEHICLE Unique Vehicle ID.
            /BIC/ZVEHICLE           TYPE /BIC/OIZVEHICLE,
         InfoObject: ZLOCID Mine Site.
            /BIC/ZLOCID           TYPE /BIC/OIZLOCID,
         InfoObject: ZLOCSL Location Storage Location.
            /BIC/ZLOCSL           TYPE /BIC/OIZLOCSL,
         InfoObject: 0VENDOR Vendor.
            VENDOR           TYPE /BI0/OIVENDOR,
         InfoObject: ZNOMTK Nomination Number.
            /BIC/ZNOMTK           TYPE /BIC/OIZNOMTK,
         InfoObject: ZNOMIT Nomination Item.
            /BIC/ZNOMIT           TYPE /BIC/OIZNOMIT,
         InfoObject: ZNOMNR Nomination number.
            /BIC/ZNOMNR           TYPE /BIC/OIZNOMNR,
         InfoObject: ZVSTTIME Vehicle Starting Time Stamp.
            /BIC/ZVSTTIME           TYPE /BIC/OIZVSTTIME,
         InfoObject: ZVEDTIME Vehicle Ending Time Stamp.
            /BIC/ZVEDTIME           TYPE /BIC/OIZVEDTIME,
         InfoObject: ZNETWT Net Weight.
            /BIC/ZNETWT           TYPE /BIC/OIZNETWT,
         InfoObject: TU_GRS_WG Gross Wgt.
            /BIC/TU_GRS_WG           TYPE /BIC/OITU_GRS_WG,
         InfoObject: ZTU_TRE_W Tare Wgt.
            /BIC/ZTU_TRE_W           TYPE /BIC/OIZTU_TRE_W,
         InfoObject: ZCUSTWT Customer Weight.
            /BIC/ZCUSTWT           TYPE /BIC/OIZCUSTWT,
         InfoObject: ZCAR_NO Car Number.
            /BIC/ZCAR_NO           TYPE /BIC/OIZCAR_NO,
         InfoObject: ZINBND_ID Train Consist Inbound ID.
            /BIC/ZINBND_ID           TYPE /BIC/OIZINBND_ID,
         InfoObject: ZOTBND_ID Train Consist Return Load.
            /BIC/ZOTBND_ID           TYPE /BIC/OIZOTBND_ID,
         InfoObject: 0SOLD_TO Sold-to Party.
            SOLD_TO           TYPE /BI0/OISOLD_TO,
         InfoObject: 0CUSTOMER Customer Number.
            CUSTOMER           TYPE /BI0/OICUSTOMER,
         InfoObject: 0SHIP_TO Ship-To Party.
            SHIP_TO           TYPE /BI0/OISHIP_TO,
         InfoObject: ZVEHI_NO Vehicle Number.
            /BIC/ZVEHI_NO           TYPE /BIC/OIZVEHI_NO,
         InfoObject: ZCARSTDAT Car Start Date.
            /BIC/ZCARSTDAT           TYPE /BIC/OIZCARSTDAT,
         InfoObject: ZCAREDDAT Car End Date.
            /BIC/ZCAREDDAT           TYPE /BIC/OIZCAREDDAT,
         InfoObject: ZCARSTTIM Car Start Time.
            /BIC/ZCARSTTIM           TYPE /BIC/OIZCARSTTIM,
         InfoObject: ZCAREDTIM Car End Time.
            /BIC/ZCAREDTIM           TYPE /BIC/OIZCAREDTIM,
         InfoObject: 0COMPANY Company.
            COMPANY           TYPE /BI0/OICOMPANY,
         InfoObject: ZCONTRACT Contract.
            /BIC/ZCONTRACT           TYPE /BIC/OIZCONTRACT,
         InfoObject: 0PLANT Plant.
            PLANT           TYPE /BI0/OIPLANT,
         InfoObject: ZLOADTIME Total Vehicle Loading time.
            /BIC/ZLOADTIME           TYPE /BIC/OIZLOADTIME,
         InfoObject: ZSHIPDATE Shipping Date.
            /BIC/ZSHIPDATE           TYPE /BIC/OIZSHIPDATE,
         InfoObject: ZSHIPTIME Shipping Time.
            /BIC/ZSHIPTIME           TYPE /BIC/OIZSHIPTIME,
         InfoObject: ZMNEDDT Manifest End Date.
            /BIC/ZMNEDDT           TYPE /BIC/OIZMNEDDT,
         InfoObject: ZMNEDTM Manifest End Time.
            /BIC/ZMNEDTM           TYPE /BIC/OIZMNEDTM,
         InfoObject: ZLDEDDT Loaded End Date.
            /BIC/ZLDEDDT           TYPE /BIC/OIZLDEDDT,
         InfoObject: ZLDEDTM Loaded End Time.
            /BIC/ZLDEDTM           TYPE /BIC/OIZLDEDTM,
         InfoObject: ZMANVAR Manifest Variance.
            /BIC/ZMANVAR           TYPE /BIC/OIZMANVAR,
         InfoObject: ZTU_TYPE Trpr Unit Type.
            /BIC/ZTU_TYPE           TYPE /BIC/OIZTU_TYPE,
         InfoObject: ZACTULQTY Actual posted quantity.
            /BIC/ZACTULQTY           TYPE /BIC/OIZACTULQTY,
         InfoObject: ZVEDDT Vehicle End Date.
            /BIC/ZVEDDT           TYPE /BIC/OIZVEDDT,
         InfoObject: ZVEDTM Vehicle End Time.
            /BIC/ZVEDTM           TYPE /BIC/OIZVEDTM,
         InfoObject: ZVSTDT Vehicle Start Date.
            /BIC/ZVSTDT           TYPE /BIC/OIZVSTDT,
         InfoObject: ZVSTTM Vehicle Start Time.
            /BIC/ZVSTTM           TYPE /BIC/OIZVSTTM,
         InfoObject: ZTRPT_TYP Vehicle type.
            /BIC/ZTRPT_TYP           TYPE /BIC/OIZTRPT_TYP,
         InfoObject: 0CALMONTH Calendar Year/Month.
            CALMONTH           TYPE /BI0/OICALMONTH,
         InfoObject: 0CALYEAR Calendar Year.
            CALYEAR           TYPE /BI0/OICALYEAR,
         InfoObject: ZLOEDDT Quality Sent End Date.
            /BIC/ZLOEDDT           TYPE /BIC/OIZLOEDDT,
         InfoObject: ZLOEDTM Quality sent End Time.
            /BIC/ZLOEDTM           TYPE /BIC/OIZLOEDTM,
         InfoObject: ZATMDDT At Mine End Date.
            /BIC/ZATMDDT           TYPE /BIC/OIZATMDDT,
         InfoObject: ZATMDTM At Mine End Time.
            /BIC/ZATMDTM           TYPE /BIC/OIZATMDTM,
         InfoObject: ZDELAY Delay Duration.
            /BIC/ZDELAY           TYPE /BIC/OIZDELAY,
         InfoObject: ZSITYP Schedule type.
            /BIC/ZSITYP           TYPE /BIC/OIZSITYP,
         InfoObject: ZDOCIND Reference document indicator.
            /BIC/ZDOCIND           TYPE /BIC/OIZDOCIND,
         InfoObject: 0BASE_UOM Base Unit of Measure.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
         InfoObject: 0UNIT Unit of Measure.
            UNIT           TYPE /BI0/OIUNIT,
         InfoObject: ZACT_UOM Actual UOM.
            /BIC/ZACT_UOM           TYPE /BIC/OIZACT_UOM,
         Field: RECORD.
            RECORD           TYPE RSARECORD,
          END   OF tys_TG_1.
        TYPES:
          tyt_TG_1        TYPE STANDARD TABLE OF tys_TG_1
                            WITH NON-UNIQUE DEFAULT KEY.
    $$ begin of global - insert your declaration only below this line  -
    ... "insert your code here
    $$ end of global - insert your declaration only before this line   -
        METHODS
          end_routine
            IMPORTING
              request                  type rsrequest
              datapackid               type rsdatapid
            EXPORTING
              monitor                  type rstr_ty_t_monitors
            CHANGING
              RESULT_PACKAGE              type tyt_TG_1
            RAISING
              cx_rsrout_abort.
        METHODS
          inverse_end_routine
            IMPORTING
              i_th_fields_outbound         TYPE rstran_t_field_inv
              i_r_selset_outbound          TYPE REF TO cl_rsmds_set
              i_is_main_selection          TYPE rs_bool
              i_r_selset_outbound_complete TYPE REF TO cl_rsmds_set
              i_r_universe_inbound         TYPE REF TO cl_rsmds_universe
            CHANGING
              c_th_fields_inbound          TYPE rstran_t_field_inv
              c_r_selset_inbound           TYPE REF TO cl_rsmds_set
              c_exact                      TYPE rs_bool.
    ENDCLASS.                    "routine DEFINITION
    $$ begin of 2nd part global - insert your code only below this line  *
    ... "insert your code here
    $$ end of 2nd part global - insert your code only before this line   *
          CLASS routine IMPLEMENTATION
    CLASS lcl_transform IMPLEMENTATION.
          Method end_routine
          Calculation of result package via end routine
          Note: Update of target fields depends on rule assignment in
          transformation editor. Only fields that have a rule assigned,
          are updated to the data target.
      <-> result package
      METHOD end_routine.
    *=== Segments ===
        FIELD-SYMBOLS:
          <RESULT_FIELDS>    TYPE tys_TG_1.
        DATA:
          MONITOR_REC     TYPE rstmonitor.
    *$*$ begin of routine - insert your code only below this line        *-*
    Fill the following fields by reading Nomination and Vehicls DSO
    SOLD_TO, Customer
    data: L_TIMESTAMP1 TYPE timestamp,
          L_TIMESTAMP2 TYPE timestamp,
          L_TIMESTAMP3 type CCUPEAKA-TIMESTAMP,
          L_TIMESTAMP4 type CCUPEAKA-TIMESTAMP,
          L_TIMESTAMP5 type CCUPEAKA-TIMESTAMP,
          L_TIMESTAMP6 type CCUPEAKA-TIMESTAMP,
          L_TIMESTAMP7 TYPE timestamp,
          L_TIMESTAMP8 TYPE timestamp,
          L_TIMESTAMP9 type timestamp,
          L_TIMESTAMP10 type TIMESTAMP,
          L_CHAR1(14),
          L_CHAR2(14),
          l_duration type I,
          L_TS TYPE TZONREF-TZONE,
          l_flag,
          l_nomit TYPE /BIC/OIZNOMIT,
          l_error_flag.
    l_TS = 'CST'.
    Data: EXTRA_PACKAGE type tyt_TG_1.
    data: extra_fields type tys_TG_1.
    LOOP at RESULT_PACKAGE ASSIGNING <RESULT_FIELDS>.
    clear l_error_flag.
    Get sold_to and customer from nomination table.
       Select single SOLD_TO /BIC/ZLOCSL /BIC/ZCONTRACT COMPANY
                     /BIC/ZMNEDDT /BIC/ZMNEDTM /BIC/ZLDEDDT
                     /BIC/ZLDEDTM SHIP_TO /BIC/ZACTULQTY
                     /BIC/ZLOEDDT /BIC/ZLOEDTM /BIC/ZDELAY
                     /BIC/ZATMDDT /BIC/ZATMDTM
                     /BIC/ZSITYP /BIC/ZDOCIND
               into (<RESULT_FIELDS>-SOLD_TO,
                     <RESULT_FIELDS>-/BIC/ZLOCSL,
                     <RESULT_FIELDS>-/BIC/ZCONTRACT,
                     <RESULT_FIELDS>-company,
                     <RESULT_FIELDS>-/BIC/ZMNEDDT,
                     <RESULT_FIELDS>-/BIC/ZMNEDTM,
                     <RESULT_FIELDS>-/BIC/ZLDEDDT,
                     <RESULT_FIELDS>-/BIC/ZLDEDTM,
                     <RESULT_FIELDS>-SHIP_TO,
                     <RESULT_FIELDS>-/BIC/ZACTULQTY,
                     <RESULT_FIELDS>-/BIC/ZLOEDDT,
                     <RESULT_FIELDS>-/BIC/ZLOEDTM,
                     <RESULT_FIELDS>-/BIC/ZDELAY,
                     <RESULT_FIELDS>-/BIC/ZATMDDT,
                     <RESULT_FIELDS>-/BIC/ZATMDTM,
                     <RESULT_FIELDS>-/BIC/ZSITYP,
                     <RESULT_FIELDS>-/BIC/ZDOCIND)
               from   /BIC/AZTSW_0000
               where /BIC/ZNOMTK = <RESULT_FIELDS>-/BIC/ZNOMTK
                AND  /BIC/ZNOMIT = <RESULT_FIELDS>-/BIC/ZNOMIT.
    Select Invalid Nominations
      if sy-subrc <> 0.
        l_error_flag = 'X'.
      endif.
       <RESULT_FIELDS>-customer = <RESULT_FIELDS>-SOLD_TO.
    Prepare time stamp for Time Differences
    Vehicle Starting Time Stamp
      clear : L_TIMESTAMP9,L_TIMESTAMP10.
      CONVERT DATE <RESULT_FIELDS>-/BIC/ZCARSTDAT TIME
                   <RESULT_FIELDS>-/BIC/ZCARSTTIM
               INTO TIME STAMP L_TIMESTAMP9 TIME ZONE l_TS.
    Vehicle Ending Time Stamp
      CONVERT DATE <RESULT_FIELDS>-/BIC/ZCAREDDAT TIME
                   <RESULT_FIELDS>-/BIC/ZCAREDTIM
               INTO TIME STAMP L_TIMESTAMP10 TIME ZONE l_TS.
      Clear : L_TIMESTAMP3, L_TIMESTAMP4,
             <RESULT_FIELDS>-/BIC/ZVEDTIME,
             <RESULT_FIELDS>-/BIC/ZVSTTIME.
      <RESULT_FIELDS>-/BIC/ZVEDTIME = L_TIMESTAMP10.
      <RESULT_FIELDS>-/BIC/ZVSTTIME = L_TIMESTAMP9.
      L_TIMESTAMP3 = L_TIMESTAMP10.
      L_TIMESTAMP4 = L_TIMESTAMP9.
    Caliculate the load time
    IF L_TIMESTAMP3 is initial.
       clear <RESULT_FIELDS>-/BIC/ZLOADTIME.
    elseif L_TIMESTAMP4 is initial.
       clear <RESULT_FIELDS>-/BIC/ZLOADTIME.
    else.
       CALL FUNCTION 'CCU_TIMESTAMP_DIFFERENCE'
         EXPORTING
           timestamp1       =  L_TIMESTAMP3
           timestamp2       =  L_TIMESTAMP4
         IMPORTING
           DIFFERENCE        = <RESULT_FIELDS>-/BIC/ZLOADTIME
    ENDIF.
    Caliculate the Manifest Variance
       clear : L_TIMESTAMP5,L_TIMESTAMP6,L_TIMESTAMP7,L_TIMESTAMP8.
       CONVERT DATE <RESULT_FIELDS>-/BIC/ZMNEDDT TIME
                    <RESULT_FIELDS>-/BIC/ZMNEDTM
               INTO TIME STAMP L_TIMESTAMP7 TIME ZONE l_TS.
       CONVERT DATE <RESULT_FIELDS>-/BIC/ZLDEDDT TIME
                    <RESULT_FIELDS>-/BIC/ZLDEDTM
               INTO TIME STAMP L_TIMESTAMP8 TIME ZONE l_TS.
      L_TIMESTAMP5 = L_TIMESTAMP7.
      L_TIMESTAMP6 = L_TIMESTAMP8.
    Caliculate the Maniefest Variance
    IF L_TIMESTAMP5 is initial.
       clear <RESULT_FIELDS>-/BIC/ZMANVAR.
    elseif L_TIMESTAMP6 is initial.
       clear <RESULT_FIELDS>-/BIC/ZMANVAR.
    else.
       CALL FUNCTION 'CCU_TIMESTAMP_DIFFERENCE'
         EXPORTING
           timestamp1       =  L_TIMESTAMP5
           timestamp2       =  L_TIMESTAMP6
         IMPORTING
           DIFFERENCE        = <RESULT_FIELDS>-/BIC/ZMANVAR
       IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
       ENDIF.
    ENDIF.
    Delete datapackets with blank nominations
    Delete datapackets with blank shipdate and Invalid Time Stamps
    *IF <RESULT_FIELDS>-/BIC/ZNOMTK IS INITIAL OR
      <RESULT_FIELDS>-/BIC/ZSHIPDATE IS INITIAL.
    l_error_flag = 'X'.
    *ENDIF.
    <RESULT_FIELDS>-/BIC/ZVEHI_NO = 1.
      <RESULT_FIELDS>-CALMONTH = <RESULT_FIELDS>-/BIC/ZSHIPDATE(6).
      <RESULT_FIELDS>-CALYEAR  = <RESULT_FIELDS>-/BIC/ZSHIPDATE(4).
    if l_error_flag = 'X'.
    Looks like Monitor Entries are not working in SP11.
    Hence the following is commented temporarily.
    CLEAR MONITOR_REC.
    MONITOR_REC-MSGID = '0M'.
    MONITOR_REC-MSGTY = 'S'.
    MONITOR_REC-MSGNO = '501'.
    MONITOR_REC-MSGV1 = <RESULT_FIELDS>-/BIC/ZNOMTK.
    MONITOR_REC-recno = sy-tabix.
    APPEND MONITOR_REC to MONITOR.
    RAISE exception type CX_RSROUT_ABORT.
    DELETE RESULT_PACKAGE index sy-tabix.
    CLEAR L_ERROR_FLAG.
    else.
       MODIFY RESULT_PACKAGE FROM <RESULT_FIELDS>.
    endif.
    clear l_nomit.
    l_nomit = <RESULT_FIELDS>-/BIC/ZNOMIT.
    extra_fields = <RESULT_FIELDS>.
    Actual Qty and Contract details
       Select /BIC/ZLOCSL /BIC/ZNOMIT /BIC/ZCONTRACT /BIC/ZACTULQTY
              /BIC/ZSITYP /BIC/ZDOCIND
              SOLD_TO SHIP_TO COMPANY
               into (extra_fields-/BIC/ZLOCSL,
                     extra_fields-/BIC/ZNOMIT,
                     extra_fields-/BIC/ZCONTRACT,
                     extra_fields-/BIC/ZACTULQTY,
                     extra_fields-/BIC/ZSITYP,
                     extra_fields-/BIC/ZDOCIND,
                     extra_fields-SOLD_TO,
                     extra_fields-SHIP_TO,
                     extra_fields-company)
               from  /BIC/AZTSW_0000
               where /BIC/ZNOMTK = <RESULT_FIELDS>-/BIC/ZNOMTK AND
                     /BIC/ZNOMIT <> l_NOMIT.
           INSERT extra_fields into table EXTRA_PACKAGE.
       endselect.
    ENDLOOP.
    Append lines of extra_package to RESULT_PACKAGE.
    *--  fill table "MONITOR" with values of structure "MONITOR_REC"
    *-   to make monitor entries
    ... "to cancel the update process
       raise exception type CX_RSROUT_ABORT.
    $$ end of routine - insert your code only before this line         -
      ENDMETHOD.                    "end_routine
          Method inverse_end_routine
          This subroutine needs to be implemented only for direct access
          (for better performance) and for the Report/Report Interface
          (drill through).
          The inverse routine should transform a projection and
          a selection for the target to a projection and a selection
          for the source, respectively.
          If the implementation remains empty all fields are filled and
          all values are selected.
      METHOD inverse_end_routine.
    $$ begin of inverse routine - insert your code only below this line-
    ... "insert your code here
    $$ end of inverse routine - insert your code only before this line -
      ENDMETHOD.                    "inverse_end_routine
    ENDCLASS.                    "routine IMPLEMENTATION

    Hi,
    Most probably you are appending some records in the data package or deleting from the data package through end routine or expert routine or start routine.
    I just solved it.....you will have to import the note 1180163.
    Then modify the code which you are using....and include the function module as mentioned in the note 1223532.
    You need to add the function module just before you append the records.This will work perfectly.
    Thanks
    Ajeet

Maybe you are looking for