Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-CIC (Application Component) Interaction Center WinClient⤷
INSC (Package) Application Development R/3 Plant Maintenance Customizing
IMG Activity
| ID | SIMG_CFMENUOLIAOIDV | Download Structures to PC |
| Transaction Code | S_ALR_87000891 | IMG Activity: SIMG_CFMENUOLIAOIDV |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUOLIAOIDV | Download Structures to PC |
| Customizing Activity | SIMG_CFMENUOLIAOIDV | Download Structures to PC |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOLIAOIDV |
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
&#x
Business Attributes
| ASAP Roadmap ID | 255 | Create Interfaces |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUOLIAOIDV | 0 | HLA0009533 O | |
| SIMG | SIMG_CFMENUOLIAOIDV | 1 | HLA0009595 O | |
| SIMG | SIMG_CFMENUOLIAOIDV | 2 | HLA0009594 | Service Notifications |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| IMGDUMMY | D - Dummy object | OIDV | 330 | Define Download Structures |
History
| Last changed by/on | SAP | 20000204 |
| SAP Release Created in |
