Regarding Archiving customer

Hi i want to archive  customers which are not in use and which don't have any transactions
iam trying to do the same through SARA .When i have gone through this process and scheduled the job
the spool job doesn't contain any data .any guess for the reason????

Hi There,
Archiving of any master data is not as simple. you have to follow certain steps , Please check the link below for archiving process :
Archiving
Thanks,
Raja

Similar Messages

  • How to archive custom tables???

    Hello gurus,
    I have been assigned to a archiving assignment..
    To archive standard tables SAP provided with standard archiving object.. but how to archive custom tables and how to creat customized archiving object..
    each reply will be rewarded...
    Regards
    RR

    Hi Ramana,
    Check the following links:
    Re: Archiving of Z Table
    Re: Archiving
    These contain the information you need to archive custom table.
    These may be helpful to you.
    Regards.
    Rajat

  • Regarding Archiving

    Hi Support,
    I am doing archiving project. Now I am doing tests in development system. The archiving object is MM_EKKO, archiving location is at a directory in same server. In variant I mentioned a single purchase document. The background job is finishing well after about 30 seconds. But no archive file is creating. see the background job log.
    Job log overview for job:    ARV_MM_EKKO_WRI20140513165632 / 16563200
    |Date      |Time    |Message text                                                             |Message class|Message no.|Message type|
    |13.05.2014|16:56:32|Job started                                                              |     00      |    516    |     S      |
    |13.05.2014|16:56:32|Step 001 started (program RM06EW47, variant TEST_WRITE, user ID VTGBASIS)|     00      |    550    |     S      |
    |13.05.2014|16:57:02|Archiving session 000058 is being created                                |     BA      |    276    |     S      |
    |13.05.2014|16:57:02|0 of 0 purchasing docs processed                                         |   KEN_01    |    004    |     S      |
    |13.05.2014|16:57:03|Job finished                                                             |     00      |    517    |     S      |
    What is the problem for it?
    Please help me.
    Asad

    Hi Md . Asaduzzaman
    You must complete the customizing configuration before archive any objects:
    Can you confirm that you had done the following configuration?
    Data Archiving Customizing Settings (Archiving Workbench) - Overview of the Archiving Workbench - SAP Library
    Tx sara-> customizing
      Technical Settings
      Check and Delete
      Technical Settings
      Archive Routing
      Cross-Client File Names/Paths
      Client-Specific File Names
      Maintain account type life
      Maintain document type life
    Cheers

  • Details regarding Create customer master record

    Hi,
    Can anyone gv info regarding Creating customer master record.
    I need Existing Bapi's for the same.
    Thanks in advance.
    Purna

    Check out the bapi:BAPI_CUSTOMER_CREATEFROMDATA1.
    To know of how to use it, check its documentation, it is very well documented.
    hi karthik, shaik can not reward points as he did not mark this as a question.
    Regards
    Gopi

  • Please clear my following doubt regarding TR (customizing / work bench).

    Dear experts,
    Greetings,
    Please clear my following doubt regarding TR (customizing / work bench).
    TR can be created for Either its customizing or work bench ?
    Both need to release in order to get it in another client?
    If different client are in one server, then in that case release is required or not. Or simply I can copy it using  T.Code SCC1 in the target client.
    Thanks & Regards,
    M S Ansari

    Hi,
    Depends, are you using ChaRM? Then the TOC would suffice.
    Please speak to BASIS person, he would provide you more insights.
    Hope it Helps!
    Thanks and Regards,
    Varshal Kachole

  • Regarding the Customer Proprietary Network Information Notice

    >> Duplicate post removed to comply with Verizon Wireless Terms of Service.  See Regarding the Customer Proprietary Network Information Notice <<
    Message was edited by: Verizon Moderator

    You do realize you opted in the day you signed up for verizon, right? As for certain parts, you can opt out via your my verizon

  • Filing a complaint with Verizon regarding a customer who is harassing me

    I am looking for the correct(and best) way to file a complaint with Verizon regarding a customer of theirs who is sending me harassing emails, attacking my website from his home.
    I do know his IP address and I know that he is a Verizon customer.
    Any direction would be greatly appreciated.
    thanks.

    Log into your Verizon account.  At the bottom of the page you will see contact us.  Click on that, but you can't send an e-mail.  You have to send your complaint via US mail.  They will give you the address.  I know it is ridiculous but there is no e-mail address to address your problem.
    Hope this helps!

  • Would you like help me regarding archiving please .. ?

    Dear All,
    We're in the archiving project ..
    We here have scenario to reload/restore archived data from BW Production to BW Development server ...
    I did try it: I moved the archived file to archived known storage in BW Development, but it didn't recognize it ..
    My questions:
    1. Is it possible to get the scenario be done ??? How can i make it ??
    2. I run t-code AOBJ and found that there is reload program (e.g. of the program: SBOOKL), What is it for ?? Could this program solve my case above ??
    Really need ur guidances all.
    Best regards,
    Niel.

    Data Archiving
    Data Archiving u2013 a service provided by SAP u2013 removes mass data that the system no longer needs online, but which must still be accessible at a later date if required, from the database.
    Data Archiving removes from the database application data from closed business transactions that are no longer relevant for the operational business. The archived data is stored in archive files that can be accessed by the system in read-only mode.
    The following graphic illustrates the archiving process:
    Reasons for Archiving
    There are both technical and legal reasons for archiving application data. Data Archiving:
    Resolves memory space and performance problems caused by large volumes of transaction data
    Ensures that data growth remains moderate so that the database remains manageable in the long term
    Ensures that companies can meet the legal requirements for data storage in a cost-efficient manner
    Ensures that data can be reused at a later date, for example, in new product development
    Data Archiving Requirements
    Data archiving is intended to do more than simply save the contents of database tables. Data archiving must also take the following requirements into consideration:
    Hardware independence
    Release dependence
    Data Dependencies
    Enterprise and business structure
    Optical Archiving
    The term u201Coptical archivingu201D generally describes the electronic storage and management of documents in storage systems outside of the SAP Business environment. Examples of documents that can be stored in this way include:
    Scanned-in original documents, such as incoming invoices
    Outgoing documents, such as invoices created in mySAP Financials that are created electronically, then sent in printed form
    Print lists created in mySAP Business Suite
    Residence Time and Retention Periods
    The residence time is the minimum length of time that data must spend in the database before it meets the archivability criteria. Residence times can be set in application-specific Customizing.
    The retention period is the entire time that data spends in the database before it is archived. The retention period cannot be set.
    Ex: If the residence time is a month, data that has been in the system for two months will be archived. Data that is only three weeks old remains in the database.
    Backup & Restore
    Backup is a copy of the database contents that can be used in the case of a system breakdown. The aim is that as much of the database as possible can be restored to its state before the system breakdown. Backups are usually made at regular intervals according to a standard procedure (complete or incremental backup).
    Reloading the saved data into the file system is called restoring the data.
    Archiving Features
    Data Security
    Data archiving is carried out in two steps (a third step u2013 storage of archive files u2013 is optional: In the first step, the data for archiving is copied to archive files. In the second step, the data is deleted from the database. This two-step process guarantees data security if problems occur during the archiving process.
    For example, the procedure identifies network data transfer errors between the database and the archive file. If an error occurs, you can restart the archiving process at any time because the data is still either in the database or in an archive file. This means that you can usually archive parallel to the online application, that is, during normal system operation, without having to back up the database first.
    You can further increase data security if you store the archive files in an external storage system before you delete the data from the database. This guarantees that the data from the database will only be deleted after it has been securely stored in an external storage system.
    Data Compression
    During archiving, data is automatically compressed by up to a factor of 5. However, if the data to be archived is stored in cluster tables, no additional compression takes place.
    Storage Space Gained
    Increased storage space in the database and the resulting performance gains in the application programs are the most important benefits of data archiving. Therefore it is useful to know how much space the data to be archived takes up in the database. It may also help to know in advance how much space the archive files that you create will need.
    Note: - Data is compressed before it is written to the archive file. The extent of the compression depends on how much text (character fields) the object contains.
    Archiving without Backup
    With SAP Data Archiving, data can be archived independently from general backup operations on the database. However, SAP recommends that you backup archive files before storing them.
    Accessing Archived Data
    Because archived data has only been removed from the database and not from the application component itself, the data is always available. Archive management allows three types of access:
    1.     (Read) access to a single data object, such as an accounting document
    2.     Analysis of an archive file (sequential read)
    3.     Reload into the database (not possible for all archiving objects)
    Converting Old Archive Files
    When archived data is read, the system automatically makes the conversions required by hardware and software changes.
    When old archive files are accessed, the Archive Development Kit (ADK) can make allowances for changes to database structures (field types, field lengths, new fields, and deleted fields) after the data was archived and for changes to hardware-dependent storage formats. This is only done on a temporary basis during read access. The data in the archive file is not changed. The following items are changed (if necessary) during automatic conversion:
    Database table schema (new and deleted columns)
    Data type of a column
    Column length
    Code page (ASCII, EBCDIC)
    Number format (such as the use of the integer format on various hardware platforms)
    If database structures in an application have undergone more changes than the ADK can handle (for example, if fields have been moved from one table to another or if one table has been divided into several separate tables), then a program is usually provided by the relevant mySAP Business Suite solution for the permanent conversion of existing archive files.
    Link to External Storage System
    Archive files created by Data Archiving can be stored on tertiary storage media, such as WORMs, magnetic-optical disks (MO), and tapes using the SAP Content Management Infrastructure (which also contains the ArchiveLink/CMS interface). This can be done manually or automatically.
    You can also store archive files in the file system of an HSM system. The HSM system manages the archive files automatically. For storage, the HSM system can also use tertiary storage media, such as MO-disks.
    CMI/R u2013 Content Management Infrastructure / Repository
    HSM u2013 Hierarchical Storage Management Systems
    Archiving Procédure
    The basic Archiving procedure is carried out in three steps, 
    Creating the Archive Files
    Storing Archive Files
    Executing the Delete Programs 
    Security Vs Performance
    Optionally, you can store archive files after the delete phase. To do this, you must mark Delete Phase Before Storage in archiving object-specific Customizing.
    If security is your main concern, then you should not schedule the delete phase until after the archive files have been stored. In this way you know that the data will only be deleted from the database after the archive files have successfully been moved to the external storage system. In addition, you can set the system to read the data from the storage system and not from the file system.
    However, if your main concern is the performance of the archiving programs, then you should schedule the delete program first and then store the files.
    Creating Archive Files (WRITE)
    In step one, the write program creates an archive file. The data to be archived is then read from the database and is written to the archive file in the background. This process continues until one of following three events occurs:
    All the data is written to an archive file
    Archiving is not complete, but the archive file reaches the maximum size specified in archiving object-specific Customizing
    The archiving is not yet finished, but the archive file contains the maximum number of data objects specified in Customizing.
    If in cases 2 and 3 there is still data to be archived, the system will create another archiving file.
    Storing Archive Files (STORE)
    Once the write program has finished creating archive files, these can be stored. There are several ways of storing archive files:
    Storage Systems:
    If a storage system is connected to mySAP Business Suite: At the end of a successful write job, a request is sent to this system to store the new archive files (provided the appropriate settings were made in Archiving Object-Specific Customizing. You can also store archive files manually at a later point if you do not want them to be stored automatically. Storage is carried out by the SAP Content Management Infrastructure (which contains the ArchiveLink/CMS interface).
    HSM Systems:
    If you use an HSM system, it is sufficient to maintain the file name in Customizing (Transaction FILE). You do not then need to communicate with the storage system using the SAP Content Management Infrastructure, because the HSM system stores the files on suitable storage media according to access frequency and storage space.
    Existing Storage Media:
    Once the delete program has processed the relevant archive file, you can manually copy archive files to tape.
    Running Delete Programs
    After closing the first archive file, the archive management system creates a new archive file and continues with the archiving process. While this happens, another program reads the archived data from the completed archive file and deletes it from the database. This procedure guarantees that only data that has been correctly saved in the archive file is deleted from the database.
    If you do not carry out deletion until after the data has been stored, you can make a setting in Archiving Object-Specific Customizing so that the system will read archive files the from the storage system during deletion. In this way, you can detect errors in good time which might arise when transferring or saving the archive files in the storage system.
    When the last archive file is closed, a delete program starts to run for this file. The graphic shows that several delete programs are running simultaneously for previously created archive files. Because, unlike the delete program, the write program does not generally carry out any transactions that change data in the transactions, the write program creates new archive files faster than they can be processed by the delete program. This decreases the total archiving runtime because the database is used more efficiently.
    Note:-
    Scheduling the Archive jobs outside SARA
    WRITE:-
    Using an external job scheduler (SM36, SM62)
    WRITE Run followed by EVENT - SAP_ARCHIVING_WRITE_FINISHED,
    Parameter is Session Number
    To analyze the archiving information of a particular session, use FM
         ARCHIVE_GET_FILES_OF_SESSION
         Input is Session Number
    DELETE:-
    Using an external job scheduler (SM36, SM62)
    Using program RSARCHD, input u2013 Obj Name, Max. no. of files, Max no. of sessions, Max no. of jobs,
              Background User
    DELETE run followed by EVENT - SAP_ARCHIVING_DELETE_FINISHED
         Parameter is Session Number
    To analyze the archiving information of a particular session, use FM
         ARCHIVE_GET_FILES_OF_SESSION
         Input is Session Number
    Archiving Object
    The archiving object is a central component of SAP Data Archiving. The archiving object specifies precisely which data is archived and how. It describes which database objects must be handled together as a single business object and interprets the data irrespective of the technical specifications at the time of archiving (such as release and hardware).
    Note:-
         An archiving object has a name of up to ten characters in length.
         Transaction code to maintain the Archiving Object is AOBJ.
    The following programs must (or can) be assigned to an archiving object. The SAP System contains programs (some of which are optional) for the following actions:
    Preprocessing (Optional)
    Some archiving objects require a preprocessing program that prepares the data for archiving. This preprocessing program marks data to be archived, but it does not delete any data from the database. Preprocessing programs must always be scheduled manually and are run from Archive Administration.
    Write
    This program creates archive files and writes data to them. At this point, however, no data is being deleted from the database.
    You can specify in archiving object-specific Customizing whether the next phase (delete) is to take place automatically after the archive files have been created. Delete jobs can also be event-triggered. To do this, you set up the trigger event in archiving object-specific Customizing.
    Delete
    This function can entail several activities. The activities are always dependent on the existing archive files. Normally, the data is deleted from the data base. However, in some case, the archived data in the database may only have a delete indicator.
    In archiving object-specific Customizing, you can specify that archive files, after successful processing, are to be transferred to an external storage system using the SAP Content Management Infrastructure (which contains the ArchiveLink/CSM interface).
    Postprocessing (Optional)
    This function is usually carried out after deletion has taken place. It is not available for all archiving objects. If the data has not yet been deleted from the database by the delete program, it is deleted by the postprocessing program.
    Reload Archive (Optional)
    You can reload archived data from the archive files into the database using this function. It is not available for all archiving objects. To access this function, choose Goto ® Reload.
    Index (Optional)
    This function builds (or deletes) an index that allows individual access. It is not included in every archiving object.
    Data Object
    A data object is the application-specific instance of an archiving object, that is, an archiving object filled with concrete application data. The Archive Development Kit (ADK) ensures that data objects are written sequentially to an archive file. All data objects in an archive file have the same structure, which is described in the archiving object.
    Archive Administration (SARA)
    All interaction relating to data archiving takes place in the Archive Administration (transaction SARA). Features of Archive Administration:
    Preprocessing
         Write
         Delete
         Postprocessing
         Read - Enables you to schedule and run a program that reads and analyzes archived data.
         Index
         Storage System - Enables archive files to be transferred to a connected storage system and  
                                             enables stored archive files to be retrieved from a storage system. 
         Management - Offers an overview of archiving sessions for one archiving object.
    Depending on the action you have selected, you can use Goto on the menu to access the following menu options:
         Network Graphic
         Reload
         Customizing
         Job Overview
         Management
         Stored Files
         Database Tables
         Infosystems
         Statistics
         Interrupting and Continuing
    Archive Development Kit
    The Archive Development Kit (ADK) is a tool for developing archiving solutions. It also prepares the runtime environment for archiving. From a technical viewpoint, it is an intermediate layer between the application program and the archive that provides all the functions required for archiving data.
    The ADK functions are required for archiving and for subsequent access to archived data. The ADK automatically performs the hardware-dependent adjustments (such as code page and number format) and structural changes that are required when archive files are created. When the archive files are accessed later, the ADK temporarily converts data that was archived using earlier SAP releases.
    Note:-
    S_ARCHIVE is the SAP delivered user authorization check object over archiving objects. The Archive Development Kit (ADK) performs the check when an archive file is opened for one of the following actions:
    Write
    Delete
    Read
    Reload
    Database Tables in Archive Administration (DB15)
    This enables you to display all of the tables for a specific archiving object and as well as allows to display the list of Archiving Objects on a particular database table. Also enables to display the storage and space statistics. This also provides further information, such as the time and number of the last archiving session and various details on the client used.
    Network Graphic
    You can use the network graphic to show any existing dependencies between archiving objects. It shows business process flows and contexts that can influence the archiving sequence. In particular, at the start of an archiving object, you can use the network graphic to obtain a good overview of related documents.
    In an archiving session, you must take into account any dependencies between archiving objects that require a specific archiving sequence. In general, you cannot archive data for an archiving object that has preceding objects until these preceding objects have been archived.
    You can use the network graphic to determine whether the archiving object that you want to use has preceding objects. If so, the preceding objects should be implemented before the current archiving object. The nodes in the network graphic represent the archiving objects. A node displays the following information:
    Archive Object Name
    Application Component Name
    Short Description
    Date of last archiving
    Status of the session
         If status is u2018Greenu2019
         Archiving and Deletion is Successful
         If status is u2018Yellowu2019
         Successfully archived, but not yet deleted, or Archiving still running, or Delete in progress or
    Delete Cancelled
    If status is u2018Redu2019
    Not yet archived, or Archiving cancelled
    Standard Log (Spool List)
    During archiving, a log is usually generated. This can be done during the write, delete, read, or reload phases. This is usually in the form of a standard log. In some cases, an application-specific log may be generated.  Depending on the archiving action that was carried out, the standard log contains statistical information per archiving session or archive file according to the following categories:
    Archiving session number
    Number of data objects for processing
    Archive session size in megabytes
    Total header data in %
    Table space in MB occupied for:
              Tables
              Indexes
    Number of table entries processed
    You can call the standard log from the screen Archive Administration: Overview of Archiving Sessions. Choose Spool List.
    Accessing Archived Data
    Data that was archived using SAP Data Archiving has been relocated from the database but not placed beyond the application. Data is still available for read access and analysis. In some cases, archived data can even be reloaded into the database.
    Note:-
    A prerequisite of read access and reload access, is that the file can be found in the file system.
    Three types of access are possible:
    (Read) access to a single data object, such as an accounting document
    Direct access or single document access requires an index that can be built either during archiving or at a later point. A complex search of the documents stored in the archive files, in which all orders of an article in a particular batch are required for a product recall action, is not possible.
    The Archive Information System (AS) supports direct access using archive information structures that can be generated automatically either when the archive files are being written, or at a later point.
    Analysis of an archive file (sequential read)
    It is possible to run an analysis for one or several archiving sessions. The results of the analyzed data objects are displayed in a list. Furthermore, some archiving objects offer the option of a combined analysis. With this option, you can link current data in the database and archived data.
    Reloading into the database
    Archived data does not usually need to be reloaded because it remains accessible by the applications. There is also a lot of data that cannot be reloaded or for which reloading is problematic. For this reason, reload programs do not exist for all archiving objects.
    Archiving Session Overview
    On this screen, you can display and edit management information on archiving sessions. One archiving session is equal to Write and Delete jobs.  Within a status area, archiving sessions are, by default, organized in groups of 20. The sessions are ordered according to different status.
    Interrupting and Continuing
    In order that Data Archiving can be seemlessly integrated into the production system, you can interrupt an archiving session during the write phase and contine it at a later time. This enables you to react, during archiving, to specific time constraints or hard-disk space shortages. You can continue and complete interrupted archiving sessions when you have more time or more storage space. 
    To interrupt an archiving session:
    The archiving object must be registered in transaction AOBJ as interruptible, otherwise the Archive Development Kit (ADK) is unable to inform the write program of the interruption request.
    The write program must be able to process the interruption request.
    The archiving session must be run in production mode (not test mode) and be in process.
    The delete phase must be able to start before the write phase has finished (setting in transaction AOBJ).
    To continue an archiving session:
    The session must have been interrupted within the context of the interrupution concept. Archiving sessions that were interrupted for other reasons or that were terminated by archive management cannot be continued.
    The delete phase must have completed for the data that was archivied up to the point of interruption, that is, the archiving session must have the status completed.
    Database Action Before and After Archiving
    Archiving uses application software that depends on and affects the organization of the database data. You should therefore organize the database before and after archiving.
    Before Archiving
    Archiving application data helps to prevent storage and performance bottlenecks. Since relocating data can, in some circumstances, in itself, impair performance u2013 this is the case if you need to access archived data u2013 you need to consider carefully what data to archive. To determine whether or not you should archive data, consider the following questions:
    If there are memory problems, can more memory be assigned to the table?
    How likely is it that you will need to access the archived data again? How often?
    Is the data accessed using an optimal index?
    Does the application perform a full table scan on the tables that contain the data to be archived?
    After Archiving
    Reorganize index: If data has been archived or simply deleted and the associated tables were accessed via an index, the index should be reorganized. Deleting table entries leaves holes in the table which are still indexed. Reorganization can shorten the access paths, reducing response times.
    Update the database statistics: If your database uses a cost-based optimizer, you must choose Update Statistics to recalculate the access paths.
    Reorganize tablespace or database space: Whether you should reorganize the tablespace depends on the reason for archiving.
    Do you expect a lot of new data for the archived tables?
    Do you want to make space for other tables?
    Note:-
    Reorganization takes a long time and may need to be repeated after archiving. Throughput during a reorganization:
         With export/import     :           approximately. 60-100 MByte/hour.
           With unload/load     :           approximately. 250-300 MByte/hour.
    Perform an SQL Trace after reorganization.
    Statistics
    When writing, deleting, reading, or reloading, statistical data on each archiving run is automatically generated and is persistently stored in the database The data archiving administrators can analyze these figures so that they can better plan future archiving projects and request the necessary resources. Statistics also provided pertinent information on the role of data archiving in reducing the data volume in the database.
    You can call this screen directly from the Archive Administration (SARA), or using the transaction SAR_DA_STAT_ANALYSIS. It displays the following information:
         Archiving Session Number
         Archiving Object Name
         Client ID on which the archiving session was carried out
         Date on which the archiving session was carried out
         Status of the session number
         Portion of the Header data in the archiving session
         DB Space (WRITE) u2013 Virtual storage space in MB, which is occupied by an incomplete archiving                          session in the database
         DB Storage Space (DELETE) - Virtual storage space in MB, which is occupied by an incomplete                               archiving session in the database
         DB Space (Reload) u2013 Virtual storage space in MB
         Written Data Objects in an incomplete archiving session
         Deleted Data Objects for an incomplete archiving session in database
         Reloaded Data Objects
         Number of delete jobs
         Write job duration
         Delete job duration
         Reload job duration
    Logical Path and File
    Archive files are stored in the file system under a physical path and file name that is derived from a user-definable logical path or file name. The definition can be divided into the following steps:
    Definition of the logical path name
    Definition of the logical file name
    Assignment of the logical fine name for the archiving object
    By default, the system uses the logical file name ARCHIVE_DATA_FILE and the logical path name ARCHIVE GLOBAL PATH as defaults. Consequently, the names only need to be changed if they have to be adjusted to meet special requirements.
    Data Archiving Monitor
    Use this indicator to activate or deactivate the data archiving monitor (transaction SAR_SHOW_MONITOR. If you mark this checkbox before data archiving, archiving-relevant information on the write and delete jobs is updated. This information can be analyzed using the data archiving monitor. If there are errors, alerts are issued.
    The data archiving monitor offers the following information:
    Overview of all the archiving objects that have been run
    Detailed information on the individual archiving sessions
    Processing status display
    Help on analyzing open alerts

  • Regarding Archiving Object

    Hello Experts,
    I have few questions about Archiving object:
    1. How to create an archiving object for set of Z tables? shall i create a new archiving object by clicking on new entry or shall i copy an existing archiving object.
    2.is there any restrictions on number of tables being used in an archiving object? in our scenario there are around 15 Z tables...
    3. in T code AOBJ, i want to maintain customizing settings, but the screen is greyed out,which authorzation role will give me the access to this screen.
    4.what are the retrieval methods avaialable in system???
    5.in our scenario we have created a new archivie info structure,shall we use standard field catalog or need to create a new one???
    awaiting your reply
    Regards
    Ramana Reddy

    hi
    ans 4 :
    you should call 4 function modules in sequence to retrive the archived data from archiving files to your report program.
    see the below sample code:
    data declaration
    data: handle                 like sy-tabix,
          buffer                 type arc_buffer,
          sbook_wa               like sbook,
          number_of_records_read type i.
    open existing archive files
    call function 'ARCHIVE_OPEN_FOR_READ'
         exporting
              object         = 'BC_SBOOK01'
         importing
              archive_handle = handle
         exceptions
              others         = 1.
    if sy-subrc <> 0.
      write: / 'No file can be accessed'(001).
      stop.
    endif.
    clear number_of_records_read.
    loop to get the next data object from the archive file(s)
    do.
      call function 'ARCHIVE_GET_NEXT_OBJECT'
           exporting
                archive_handle = handle
           exceptions
                end_of_file    = 1
                others         = 2.
      if sy-subrc <> 0.
        exit.
      endif.
    get data records from the data container
      do.
        call function 'ARCHIVE_GET_NEXT_RECORD'
             exporting
                  archive_handle   = handle
             importing
                  record           = buffer-segment
                  record_structure = buffer-rname
             exceptions
                  end_of_object    = 1
                  others           = 2.
        if sy-subrc <> 0.
          exit.
        endif.
        add 1 to number_of_records_read.
      enddo.
    enddo.
    write: / 'Total number of records read: '(002), number_of_records_read.
    skip.
    write / 'Last record read: '(003).
    skip.
    case buffer-rname.
      when 'SBOOK'.
        sbook_wa = buffer-segment.
        write: / 'CARRID    :', sbook_wa-carrid,
               / 'BOOKID    :', sbook_wa-bookid,
               / 'CONNID    :', sbook_wa-connid,
               / 'FLDATE    :', sbook_wa-fldate,
               / 'CUSTOMID  :', sbook_wa-customid,
               / 'ORDER_DATE:', sbook_wa-order_date,
    when ...
    If the archive object contained more than one table
    (different buffer-rname), more cases would be needed.
    endcase.
    close the archive session
    call function 'ARCHIVE_CLOSE_FILE'
         exporting
              archive_handle = handle.
    ans 5:
    you can either use standard field catalog, from the available field in field catalog you can select the required fields alone to your info structure.
    regards
    mano

  • Regarding the Customer Setup for ISA B2B using SAP J2EE 6.4 and NWDS

    Hi
    Does someone knows how we can setup a customer project using
    SAP J2EE 6.4 and NWDS.
    I've tried to setup the project but facing a weird problem..
    I've ISAWAC640SP11 and ant buildtool to build the application.
    I didn't get any "sda_build.xml" in this patch (ISAWAC640SP11).
    i've used "sda_build.xml" of ISAWAC40SP11.
    I've build the application using build tool but when i try to deploy it
    on SAP J2EE 6.4 using SDM i get a weird message stating
    <b>"com.sap.sdm.util.sduread.IllFormattedSduFileException: The archive must be deployed with a 6.20 SDM, which has a SDM-SDA compatible version 1 or greater."</b>
    Does anyone knows from where can i get the sda_build.xml file compatible with
    ISAWAC640SP11 ??
    Also can some one suggest me to setup a customer project for extension and
    modification of ISA B2B 640 on NWDS and SAP J2EE 6.4....
    Thanks & Regards
    Sandeep Solanki

    Hi,
    I am Rajesh..and it seems that you and I are facing the same problem. Well, I am really finding it hard to find material like PDF's files on Build Tool. and ISA Development and Extension Guide. 
    I would really appreaitate if you could send me some material. Well, My project is very simple and I have been given the task to first submit a simple demo of B2C on R/3 system. ( Not CRM ). I have also installed the NWDS and everything including the ISA WAC Java components. I am having real hard time in modifying them....
    Can you please shed light on it...You can also email to me at [email protected]
    Thanks in Advance for your kind consideration.
    Rajesh.

  • Unable to Archive Customer only with General Data

    Hi,
    I am trying to archive the Customer master only with General Data. I followed the below steps.
    1.Execute SAPF047 - To establish the link b/w customer and vendor
    2.Tran: XD99 , Set the del flag and confirm the same in xd03
    3.Tran: F56A , Select FI_ACCRECV object and perform the following
       1. Preproc => Preprocess resulted that no data found in this category
       2.Write => Preprocess resulted that no data found in this category
       3.Delete  => No data found
    Note : I selected "General Master Records" and also tried with "SD Data" and "FI Data".
    All resulted the same. Any Hints on this ?
    Regards
    Prasath

    Hi Prasath,
    Please follow the following steps...
    1)Go to Transaction <SARA> and give the object name FI_ACCRECV and press ENTER
    2)Go to Customizing -> Application-Specific Customizing->Mark customer for deletion (centr.) and mark the customers for deletion(This screen can alternatively be reached using transaction XD06).
    3)Schedule the Write variant and execute the jobs
                   Data To Be Archived ---> General Data
                   Customer -
    > Give Customer No to be archived
                   Consider Del Indic----
    > Checked (If you are not doing step2, this can be unchecked)
                   Processing option----
    > Select Production mode
    4)Select Delete in SARA and run the delete jobs for the data which has been archived in step 3.
    I dont see a preprocessing program available for the archiving object FI_ACCRECV. If you have that option available then it should automatically set the deletion indicator when u run the program , ie in that case step 2 can be avoided)
    Hope this input helps you.
    Regards
    Asish

  • Issue regarding the customer specific price

    Hi Guru:
    Please see my case as below:
    1 I created the table condition 805 (sold to specific price) and 806 (ship to specific) and had assigned these two table conditions to the access sequence ca01,and I created the condition type ca01,I assigned the access sequence ca01 and price procedure caa001 in it,and finally I maintained them in ovkk with the specific sales organization/distribution/division channel.
    2 Then I maintained the price condition type via vk11 as below,please note that sold to 1 linked with ship to 16,
    sold to 1 ,material 64,50 eur/kg
    ship to 16,material 64,55 eur/kg
    3 And I went to the transaction va01 and was going to place the sales order for them to have a test,it looks good for picking 1 as sold to as well as ship to,and the price of material 64 is 50 eur/kg
    But when I chose customer 1 as sold to whereas 16 as ship to,the price of the material 64 still be 50 eur/kg
    My question is that normally the price of ship to specific should override the one with sold to specific,so based on my example above,the price of material 64 should be 55 eur/kg
    So am I missing something in customization? Please help to fix!

    Hi,
    U have assigned Access Seq - tables in following sequence as per result u have written
    805  Exclusive Ticked
    806  Exclusive Ticked
    Now in both tables records maintained ...
    Now when u run order .. system goes to first table --- condition record found so it will never go to second table which is Ship to.
    Hence the way you have defined logic is wrong.
    Desired Logic - If u need that if Ship to Diferent frm sold to then pick price from ship to or if ship to and sold to are same pick price from sold to.
    If this is what u had desired. then u can maintain only one table with Ship-to and maintain prices for all ship to. so even the sold to in sap is ship to unless we specify seperately so if u maintain for all ship to the result will be as u desired like
    Condition record in Ship to table - (delete sold to table from access seq)
    1. Customer 1 - 50
    2. Customer 2 - 55
    Now if u run order and give sold to 1 then by default ship to = 1 so price 50 now if u chnage ship to in this order to 16 then price will be 55.
    Regards
    Krishna

  • Regarding the Customer and Vendor insurance

    Hi Gurus,
    My client is dealing with food materials,the requirement of the client is he will take an insurance policy say for 1cr and is valid accross India.The moment any sale or purchase takes place and which is transported in a truck,the invoiced amount should be automatically deducted from the policy and the system should warn them if the amount or validity date is near lapse so that they can renew the policy.
    If any customer is picking the goods then the amount should not be deducted from the policy.Can anyone please help me in this issue.
    Thanks in advance,
    Ramesh.
    Edited by: malladirb on Jul 28, 2011 7:18 AM
    Edited by: malladirb on Jul 29, 2011 11:37 AM

    Dear Sreenivas,
    My client deals with food materials.He buys the raw materials from farms and transports from different locations to the main plant where the material is processed.Similar is the scenario with the sales.The customers of the  Client r in different locations in the country.The requirement here is,if the client sells or procures any material which involves transportation by a truck (in case of any accident taking place) he can claim the insurance for the amount.
    What ever the amount which is invoiced in the above explained scenarios should be deducted from the insurance policy which is an Inland Transit Insurance policy and similar is the case with the expots also.
    I hope my explanation is clear to u.
    Thanks & Regards,
    Ramesh.

  • Archiving custom(z) table or changing standard se16 screen

    Hi Abapers,
    My requirement is i need a selection screen1 to enter the z table name, when i select the table and execute on screen1, it should direct me to the selection screen2 which contains the key fields of the table mentioned as a selection screen elements. Then i enter the key field values and execute the 2nd selection screen, it should archive the records corresponding to the mentioned selection criteria. Could you please tell me the idea to achieve the same.
    The solutions i am thinking of are
    1. to enhance the se16 screen(where the same sequence of screens come) by adding a button to archive. If this is possible how do i can do this??
    2. By creating from scratch by creating a report, in this case i am struck with the dynamic selection screen creation.
    Your suggestion/help is very much in need.
    Thanks
    Shruthi

    Hi  Shruthi,
    I don't think we can have a generic transaction to archive Ztable records. May be in case if you wanna delete you can do so, but since archived records needs to be stored somewhere you may need to create several tables that holds the archived data.
    Regards,
    Karthik D

  • Regarding Linking Customer Name in Purchase Order PLD

    Dear Experts,
    I need to show the Customer Name in Purchase Order PLD. Purchase Order's base document is Sales Order.  Eventhough i mapped the sales order table and customer name in the Purchase PLD, the system is hanging and coming slowly like some 1234 blank pages.
    How to show the same ?
    Pl help, Thanks
    Regards
    Sundaram

    Hi Sunrag......
    If your PO is linked with SO. Then you can fetch customer name easily by FMS in PO.
    From there you ca gte the Customer Name into your PLD and it wont hang also.....
    Regards,
    Rahul

Maybe you are looking for

  • How many ipod can i have on one computer??

    Currently have a 2G 8 gig, wanna get a 3g 32 or 64gig. I want to keep my 8 gig though also for the GF to use. Can i use the same computer and Itunes account for both of these?? Thre are apps and stuff off of the 8 gig i want to use on the new one.

  • Texting issues between Iphone and IPAD

    I set up my young daughter's IPAD using my Apple ID.  Quickly we realized that she was getting the texts that I was sending from my Iphone (to other people) on her Ipad.  She was reading things she shouldn't have been....so I need to change this.  I

  • Line wrap in JSE 8

    Hi, Is there a way to wrap around long line on the editor? I don't want a hard wrap, just a soft wrap around the window. Couldn't find any such option. Thanks.

  • New Mac old settings

    Hi! I just placed an order for a new iMac on the Apple store. Currently I sync my iPhone, iPad and iPods with my PowerBook G4. Once the new Mac arrives I plan to sync my iOS devices with it, I understand that there is a migration or setup assistant t

  • Backup interface command

    if i use this command do I need to include a route for that interface ? how does it exactly work ?