Seguimiento del cierre de escuelas - Metodología

This configuration step provides access to the transaction IBIP, which can be used for the mass loading or changing of data. It is most commonly used for Plant Maintenance purposes to per-form an initial load of functional location and/or equipment data. Although it can be used to load or change other objects, it is sometimes so difficult to organize the data in the correct for-mat(s) that other data manipulation and loading techniques, possibly including manual entry, are preferable.

Although there is extensive documentation provided by SAP, it can be difficult to follow. An example, for a “simple” data load for equipment is as follows:

Perform transaction SE12 to obtain a data layout for the view “IBIPEQUI.” (IBIPEQUI is the equipment layout for the IBIP (data load) transaction as found in the SAP documentation). This shows a complete listing of the fields and the field lengths.

The input data must be arranged into the format pro-vided in the previous step. The first two fields, TCODE and RECORDNAME should contain IE01 and IBIPEQUI respectively. IE01 is the transaction code for creating a piece of equipment, while IBIPEQUI is the data layout provided.

However the data is accumulated (Microsoft Access is one option), the data must be provided to the IBIP transac-tion as a text, non-delimited file. That means that no commas, tabs, or other characters can be used between fields and that a 10-character field must be 10 characters in length, even if some of the characters are spaces.

Every field is treated as a text field, just as if the data was being entered manually. Additionally, each field will be subjected to the R/3 system’s normal data vali-dation. That means that any invalid data cannot be loaded into the system.

Once the file is in the correct format, a test load can be performed. Provide a file with only one record on the first

attempt. This attempt will serve to ensure that the field lengths are aligned correctly. On subsequent attempts, load perhaps three records once or twice before attempt-ing to load the entire file. If it is important not to load the same piece of equipment more than once, be sure to remove those records already loaded from the input file on subsequent attempts. Keep a full version of the data file for subsequent full data loads, but create partial data files for partial data loads as required.

To perform a data load, there are very few changes required to the settings in the IBIP transaction.

Experiment with the other changes, if required, but listed here are the critical fields:

Process mode—There are three modes:

o A—This processing mode requires user input on every screen. If four screens/tabs are involved for every equipment to be loaded, the

“Enter” key must be pressed for each screen, regardless of whether an error exists. Not rec-ommended for loading many records.

o E—This processing mode only requires user input when an error is encountered. Error cor-rection can be made “on the fly” as the data is being loaded. However, as data corrections are made as the data is loaded, be sure to make the same changes to the original data file to allow error-free entry on subsequent data loads. This is recommended for when the data file is reason-ably error-free but may still contain some prob-lems. This setting is a good compromise, but still requires some watching over the load process.

o N—This processing mode is performed in the background and requires no user intervention until its completion. If this processing mode is used, be sure to check the “Save errors” checkbox below and review the log for errors upon com-pletion of the data load. Selecting this option

eliminates the need to watch over the process, but requires that the error log be reviewed after completion of the process. Any data records for which there were errors will not be loaded, but will have been ignored by the system. All error-free data will have been loaded. Those records for which there were errors must be extracted from the original data load file, corrected, and then loaded by themselves.

The other important field is the “Physical file name”

field in the “File access: Source” data group on the “File Management” tab. Use the “pull-down” to the right of this field (click on the field first) to find the data file. If the data file is on a desktop computer, the “Presentation server” button should also be active.

In addition, a file in which to save errors can be specified in the “Physical file name” field in the bottom data group,

“File access: Objective/saving incorrect transactions.”

For functional location loading, once a functional loca-tion has been loaded, it cannot be loaded again, since the functional location must be unique in the system. If testing a functional location load and a subsequent load must be performed, perhaps change the first character or two for every record in the input file. This will create another functional location hierarchy in the system.

Perform the load in a test system as many times using this technique as necessary in order to eliminate all errors from the load. Once the load is certified error-free, it can be loaded into the “production” system cleanly once only.

For equipment loading, depending on whether internal or external numbering is used, the data may or may not be loaded more than once without changing the data. If internal (system-assigned) equipment numbering is enabled, it is possible to load equipment records more than once. While this simplifies testing the data load, caution is advised when performing a data load into the

“production” system to ensure that the data is not loaded more than once. If external equipment numbering is used, a portion of the equipment number must be changed in order to test load the data more than once.

Regardless of whether the IBIP transaction is used to load data or whether a different method is used, the test loads can follow the same technique described above in order to perform more than one test load. With any method of data loading, ensure that the data loads cleanly in its entirety before performing a data load into the “production” system. Once an entire data load has been cleanly performed, any subsequent changes to the data must trigger a new round of testing before a “pro-duction” data load can be performed, no matter how simple the change may seem.

It is not a simple process to delete functional locations and/or equipment records from the system, so ensure that the process need only be performed once into the

“production” system.

Note: There are several alternatives to transaction IBIP for data loading. One of the best alternatives is the Legacy System Migration Workbench (LSMW), which can be accessed through transaction code LSMW. SAP recom-mends searching for updated documentation for LSMW on the SAP Service Marketplace (service.sap.com) web site. A user ID, normally available through SAP system administrators, is required to access the web site.

LSMW provides an easier method of transferring data from other sources into the SAP R/3 system than developing programs for each data conversion.

Although LSMW can make the data conversion process easier, an understanding of data tables and field mapping is recommended.

Updating the PMIS

Activate Update

This configuration step can be found in the IMG by following the path:

Logistics—General  Logistics Information System (LIS)  Logistics Data Warehouse  Updating  Updating Control  Activate Update

Select the Plant Maintenance option and review the settings.

The settings can be changed by selected a particular info. struc-ture and clicking on the magnifying glass button. Usually, for statistical reporting and analysis, monthly updating is adequate, but that can be changed here.

Consult with those responsible for the CO module to determine whether a fiscal year variant should be used. Typically, this is used to align PMIS reporting periods with financial reporting periods.

Although there are other settings that can be made in the con-figuration for the Logistics Information System, of which the Plant Maintenance Information System is a part, the setting of primary concern is mentioned above.