Kontakt

Ansicht
Dokumentation

Work Management Interface ( RELNPM_46A_WORK-MANAGEMT )

Work Management Interface ( RELNPM_46A_WORK-MANAGEMT )

CL_GUI_FRONTEND_SERVICES - Frontend Services   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Work Management Interface

Scope of Functions

This interface allows the exchange of data between an R/3 or PM module and a Field Work Mobile/Dispatch external software.

It extends R/3 functionality to support large volumes of field work that are executed by a mobile field force of many technicians, where travel time is a significant productivity factor. Work specifications (SM/PM orders or notifications) can be transferred from R/3 to an external system for subsequent finite resource scheduling and assignment to work crews. The external system can send back status and assignment information to the R/3 system, as well as work completion feedback both during and after the execution of the work.

Effects on Existing Data

Effects on Data Transfer

All data is exchanged using IDocs. The following IDocs were created:

To exchange data from R/3 to the external system:

  • IORDER01 contains SM/PM orders
  • INOTIF01 contains SM/PM notification
  • IWKCEN01 contains Work Center personnel data

To exchange data from the external system to R/3:

  • IMATIS01 contains unplanned material issues
  • IMEASR01 contains measurement readings
  • INTUPD01 contains notifications user status modification and/or completion
  • IORUPD01 contains orders user status modification and/or completion
  • PIECEOFEQUIPMENT_DISMANTLEATFU01 contains equipment dismantlement at functional location
  • PIECEOFEQUIPMENT_INSTALLATFUNC01 contains equipment installation at functional location
  • SERVICENOTIFICATION_CREATEFROM01 contains SM notifications to be created

Effects on System Administration

Effects on Customizing

  1. Maintain the distribution model.
The message types IORDER, INOTIF and IWKCEN must be specified between the R/3 logical system and the external partner logical system.
  1. Maintain the partner profile.
A partner profile must be created for the external partner logical system and must contain the following definitions:
Outbound parameters:
Message type,,,,,,IDoc type
IORDER,,,,,,,,,,IORDER01
INOTIF,,,,,,,,,,INOTIF01
IWKCEN,,,,,,,,,,IWKCEN01
Inbound parameters:
Message type,,,,,,,,,,IDoc type
CONF32,,,,,,,,,,,,,,CON5
PIECEOFEQUIPMENT_DISMATLEATFU,,BAPI
PIECEOFEQUIPMENT_INSTALLATFUNC,,BAPI
IMATIS,,,,,,,,,,,,,,IMAT
IMEASR,,,,,,,,,,,,,,IMEA
SERVICENOTIFICATION_CREATEFROM,,BAPI
INTUPD,,,,,,,,,,,,,,INTU
IORUPD,,,,,,,,,,,,,,IORU
Add necessary configuration to use the standard IDocs for CATS time entry, and employee absence reporting.
  1. Create User status profile.
Example of a possible User Status Profile:
Status no.,,,,,,,,10,,,,20,,,,,,30,,,,,,40
Status,,,,,,,,,,NEW,,,,EXT,,,,,,CHG,,,,,,SAP
Short text,,,,,,,,New,,,,Sent to,,,,Order,,,,Order
,,,,,,,,,,,,,,,,external,,changed,,,,returned
,,,,,,,,,,,,,,,,system,,,,in SAP,,,,to SAP
Init.status,,,,,,,,v
Lowest status no.,,,,10,,,,20,,,,,,20,,,,,,20
Higest status no.,,,,20,,,,99,,,,,,99,,,,,,99
Pos.,,,,,,,,,,1,,,,1,,,,,,1,,,,,,1
Prio.,,,,,,,,,,1,,,,1,,,,,,1,,,,,,1

Update "Object types" to support notifications, tasks, orders and operations.

  1. Assign User status profile to Order types.
  2. Assign User status profile to Notification types

Further Information






Fill RESBD Structure from EBP Component Structure   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 4734 Date: 20240523 Time: 075255     sap01-206 ( 48 ms )