Shakti - What you're describing sounds like the storage and retrieval of the images of the documents that are output from various SAP processes - not the data. LIS/SIS store some of the data (but not all of it!), but they definitely don't store copies of the output. To use standard SAP transactions to see a BoL, delivery note, etc. generally you're going to reproduce that output, rather than see an image of the original. The transaction code to see that would be the same one that created it - VL02N will let you recreate an output for a delivery note, for example. This is not a true copy, as it will include changes since the original output, that were made to the master data, or the transactional data, or the print program, or the forms, etc. Typically, the entire issue of long term storage falls into Archiving, which is made up of the Data archiving as well as the Optical (or Document, or Image) archiving. Data is typically archived when it is no longer needed in the online system, but Optical archiving is typically done at the time the output is produced. Because of that, if you do Optical archiving, you can retrieve true copies of the original documents immediately after they were originally created. The transactions to use here can vary depending on the Archiving solution you implement, but if it's a product that integrates properly, you can use the display version of the various transactions (i.e. VL03N for a delivery), select the output you need, and hit the "display originals" function. The reason I'm not giving you lists of reports and transaction codes is that it depends. For each type of document that you're interested in, you need to find out how, in your company, that output gets created. From there, you need to find out how to display the output for that type. If I've understood your need wrong, then you're talking about the data and not the outputs. If that's the case, then I don't understand your need to store the data in a separate system - SAP is by far the best place to store and retrieve SAP data. There is no USA statutory requirement to store the data again in another system - or ANY system if you are paper based. If you must proceed anyhow, then you are going to need a lot of discovery and the assistance of the people in your organization - the list of tcodes would be only a drop in the bucket against the information you're going to need about how to retrieve the data. Also, finding the tcodes to perform standard SAP tasks is a job for your trainers - not for us here on the forum. Dave
| | | ---------------Original Message--------------- From: shakti dash Sent: Wednesday, October 26, 2011 2:02 AM Subject: Tcode for Bill of Lading ERMS means Enterprise Records management system, In USA it is mandatory for companies to store datas as records in system for legal & auditing purpose. So the company wants to store each and every transactional data in ERMS system which is different than SAP system and we have to use interface to extract datas from LIS or SIS. So I need to know each and every tcode and Reports available in LIS or SIS ? Now my questine is what is the tcode to view the Bill of Lading, Way bills, Box lists, Customer consolidated delivery notes, Export clearance and certificates, Forwarder consolidated delivery notes, Export documentation available in LIS or SIS ? Including Bill of ladding If you can tell me all the reports and Tcodes it would be more helpful to me. Thanks and Regards, Shaktiprasad Dash + 91 7204246238 | | __.____._ Copyright © 2011 Toolbox.com and message author. Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251 | | Dave Thornburgh SAP Logistics Sales and Distribution Enthusiast
Contributed 100 posts in a group to earn a Bronze Achievement Popular White Papers In the Spotlight _.____.__ |