Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Some advice from the past dozen migrations or so I was involved in:</p> <ul> <li><p>Do NOT try to bypass the SAP system and import into the SAP database directly. Don't even think of it. If anything goes wrong, you have shredded a production system - and you're the one who's getting the blame.</p></li> <li><p>Decide whether you want a migration-type scenario (a single transfer) or a permanent interface (transfer every n minutes/hours/days). This makes a huge difference (for example: in migration scenarios you'll usually won't have to worry about updating the same record over and over again - in a permanent interface, you'll have to take care of this). If you have to change your decision later on, you'll usually have to start from scratch.</p></li> <li><p>Get someone who knows both the SAP module involved and the way the module is customized and used in your system. You might need various experts - a consultant with in-depth knowledge of the module and a key user with detailed knowledge about the way the actual data is entered and used.</p></li> <li><p>Make yourself familiar with the data dictionary structures involved. You'll need this knowledge to correctly map your input data to the SAP structures.</p></li> <li><p>Ask the expert if there are any interfaces available. If there are, then the expert should be able to tell you more about it, including documentation. If there aren't any, you'll have to create something yourself.</p></li> <li><p>For a migration scenarion: Perform a manual entry of representative records with a key user to make sure you have all of the details covered (Which field contents go where in the SAP system? Do we have all data for all of the required fields?). In many cases, you can use the transaction recorder (SHDB) to keep track of what you entered and especially of the technical field names.</p></li> <li><p>Take a look at the <a href="http://help.sap.com/saphelp_NW04s/helpdata/en/ad/2d54a41d7011d2b42e006094b944c8/frameset.htm" rel="noreferrer">Legacy Systems Migration Workbench (LSMW)</a>. It might seem a bit complicated first, but it's a great tool for many purposes.</p></li> </ul> <p>As always, YMMV. Oh, and - be prepared to learn ABAP. You should at least be able to read it, understand what's going on and step through programs in the debugger, otherwise things will get very frustrating.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to import data to SAP
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USvwegert
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to import data to SAP
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload