Skip to Content

This post will pick up where last week’s post left off.  This post will actually come from the SAP documentation.  They do a good job of defining what needs to be extracted in order to make this step useful.  In this step you can create your own databases for MS Access which correspond to the structures of the SAP System.

This gives you the option of loading data into a PC environment from the SAP System and analyzing it there or processing it with PC programs. The report creates Microsoft Access databases automatically. Access 2.0 databases are created with tables that have a structure corresponding to the SAP structures.

In addition to the tables, a Dictionary is created in the required language which you can access while programming your MS Access or Visual Basic application.

Now, much of this process is contingent on setting up the RFC’s to access this information.  For more details on how to create the RFC’s, please check out the following link:

http://paperstreetenterprises.com/service-management-creating-rfc-download/

Now, the issue I encountered is that you apparently need an additional component, that my license does not grant me, in order to get these files.

Now, to begin the process, let’s show the SPRO.

/wp-content/uploads/2014/05/blog1_01_455046.png

Now, the last part is easy.

/wp-content/uploads/2014/05/blog1_02_455047.png

Enter in the database you want to populate, and the RFC destination created.  Now, the Table Name is the piece that make take several iterations.  According to the SAP documentation, you will need the following pieces:

Define Destination and Database for PC Download

In this step you can define to which PC (via TCPIP address) lists are transferred from plant maintenance.

Standard settings

The default setting contains entries for the application area

SPACE – is used to download report lists.

N – is used to download maintenance notifications.

O – is used to download maintenance orders.

Note

The download function of maintenance notifications and maintenance orders can be activated via print diversion. Using this, you can load your PM papers on a PC instead of printing them.

It is important that, from the point of view of the SAP System, the download is handled as a printout. This means that the papers have the status ‘Printed’ after the download.

Activities

Maintain your RFC destination and the key of the record under which the dataset to be downloaded is stored.

Download Structures to PC

In this step you can create your own databases for MS Access which correspond to the structures of the SAP System.

This gives you the option of loading data into a PC environment from the SAP System and analyzing it there or processing it with PC programs. The report creates Microsoft Access databases automatically. Access 2.0 databases are created with tables that have a structure corresponding to the SAP structures.

In addition to the tables, a Dictionary is created in the required language which you can access while programming your MS Access or Visual Basic application.

Example for Maintenance Notifications

************************************************************************

To download notifications, the following structures are necessary:

RIHQMEL Maintenance notification

|

|—>DIIHPA    Partner

|—>DIQMFE    Notification Item + Causes

|   |

|   |—>DIQMMA    Activities for the item in the notification

|   |—>DIQMSM    Tasks for the item in the notification

|   |—>DICLASS   Class

|       |

|       |—>DICLDAT   Characteristic value assignment

|

|—>DIQMMA    Activities for the notification

|—>DIQMSM    Tasks for the notification

In report variant SAP_NOTIF, the corresponding tables are already listed.

The link between partners and notification is made by the OBJNR field of the notification header. It is simultaneously part of the key of table DIIHPA.

Any long texts that may exist are made available in structure IBIPTEXTLN. The key for the notification tables is made up as follows:

Object               | TDOBJECT   | TDNAME             | TDID

———————————————————————

Notification header:   “QMEL”     | QMNUM              | “LTXT”

Notification item:   | “QMFE”     | QMNUM+FENUM        | “LTXT”

Cause:               | “QMUR”     | QMNUM+FENUM+URNUM  | “LTXT”

Task:                | “QMSM”     | QMNUM+FENUM+MANUM  | “LTXT”

Activity:            | “QMMA”     | QMNUM+FENUM+MANUM  | “LTXT”

The notification download can be made directly from the notification change transaction and is recorded just like the notification printing by status tracking and print protocol.

************************************************************************

To download maintenance orders or service orders, the following structures are necessary:

RIHAUFK Maintenance order

|

|—>DIIHPA     Partner

|—>RIHAFVC    Operations

|   |

|   |—>RIHRESB    Materials

|   |—>DIAFFH     Tools

|

|—>DIOBJK Object list

The link between partners and order is carried out via the OBJNR field of the order header. It is simultaneously part of the key of table DIIHPA.

Any long texts that may exist are made available in structure IBIPTEXTLN. The key for the order tables is made up as follows:

Object            |  TDOBJECT     |  TDNAME               |  TDID

———————————————————————

Order header:     | “KOPF”       |  MANDT+AUFNR          | “AUFK”

Operation:        | “AVOT”       |  MANDT+AUFPL+APLZL    | “AUFK”

Material:         | “MATK”       |  MANDT+RSNUM+RSPOS    | “AUFK”

Utilities:        | “FHMT”       |  MANDT+AUFPL+PZLFH    | “AUFK”

The order download can be made directly from the order change transaction and is recorded just like the order printing by status tracking and print protocol.

************************************************************************

A download can also be carried out from reporting. The various PM Reporting lists serve as a basis for this:

Single-level lists

Report   |  Name                                | Structure

———|————————————-|——————

RIAFVC20 |  Maintenance operation list         | RIHAFVC

RIAUFK20 |  Maintenance order list             | RIHAUFK

RIEQUI20 |  Equipment list                     | RIHEQUI

RIIFLO20 |  Display functional location        | RIHIFLO

RIIRLO20 |  Reference location list            | RIHIRLO

RIMARA20 |  Material list                       | MARAV

RIMPLA00 |  Maintenance plan list              | MPLA

RIMPOS00 |  Maintenance item list              | RIHMPOS

RIQMEL20 |  Notification list                  | RIHQMEL

RIVEDA20 |  Contract list for tech. object     | RIHVEDA

Structure displays:

Report   | Name                                 | Structure(s)

———|————————————-|——————

RIIFLO10 | FunctLocation structure display     | RIHIFLO

         |                                       | RIHEQUI

         |                                       | RIHSTPO

RIEQUI10 | Equipment structure display         | RIHIFLO

         |                                       | RIHEQUI

         |                                       | RIHEQUI

         |                                       | RIHSTPO

RIIRLO10 | RefLocation structure display       | RIHIRLO

RIMARA10 | Bill of material structure display  | RIHSTPO

Multi-level lists:

Report   |  Name                                | Structures

———|————————————-|——————

RIIFLO30 | Functional location list            | DIEQUI

         |                                      | DIEQUZ

         |                                       | DIIHPA

         |                                       | RIHIFLO

         |                                       | RIHQMEL

         |                                       | RIHAUFK

         |                                       | DICLASS

         |                                       | RIHCLDA

         |                                       | DIDRAD

         |                                       | DIINET

RIEQUI30 |  Equipment list                     | DIEQUI

         |                                       | DIEQUZ

         |                                       | DIIHPA

         |                                       | RIHIFLO

         |                                       | RIHQMEL

         |                                       | RIHAUFK

         |                                       | DICLASS

         |                                       | RIHCLDA

         |                                       | DIDRAD

         |                                       | DIINET

RIQMEL10 |  Notification list                  | RIHQMEL

         |                                       | RIHIFLO

         |                                       | DIEQUI

         |                                       | DIIHPA

         |                                       | DIQMFE

         |                                       | DIQMMA

         |                                       | DICLASS

         |                                       | RIHCLDA

         |                                       | DIQMSM

         |                                       | RIHAUFK

RIAUFK10 |  Order list                          | RIHAUFK

         |                                       | DIIHPA

         |                                       | RIHIFLO

         |                                       | DIEQUI

         |                                       | RIHQMEL

         |                                       | RIHAFVC

         |                                       | RIHAFRU

         |                                       | RIHRESB

         |                                       | DIAFFH

For the batch input back into the SAP System, you need a number of structures that begin with IBIP*. Please read the documentation on report RIIBIP00 for more information.

So…  once you get through all of this, you’re ready to start using the print diversion to download the actual data to MS Access.

Thanks for reading,

If you’re interested in great tips and tricks on SAP service management, variant configuration or production planning, check out my blog at: http://paperstreetenterprises.com/blog/ There is also a link to some SAP Easy Buttons =)

Thanks for reading,

Mike CTO – JaveLLin Solutions, LLC

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply