MM-SRV Interfaces

MM-SRV Interfaces
Overview

MM-PUR Interface
Purchase requisitions
Purchase orders
MM-IM Interface
MM-IV Interface
CO Interface (commitments)
PM Interface
Report MEDEBUG

Service Purchase Requisitions (MM-PUR Interface)

Interface components
Function module: MS_SERVICE_PACKAGE
Function group: MLSP
Communication structure: COMSRV
Global accounting table (internal): ACC_TAB
Transaction ME51
Main MM-PUR program: SAPMM06B
subroutine: DIEN_MAINTAIN
Transaction ME51N
Main MM-PUR program: SAPLMEGUI
Function module: MS_SERVICE_PACKAGE_PBO
External requisition processing
Main MM-PUR program: SAPLEBNE
subroutine: DIEN_MAINTAIN
External process creates purchase requisitions via function module ME_REQUISITION_EXT
Examples: BAPI_REQUISITION_CREATE; Transaction IW31, IW32 (PM Orders), CN21, CN22 (Networks)
How to check BAPI problems:
Function module: BAPI_REQUISITION_CREATE

Execute SE37 with BAPI in test mode using test data directory (note 420331 describes how to fill BAPI structures)
Breakpoint in BAPI_REQUISITION_CREATE at "PERFORM requisition_create_data", check XESLL, XESKL, XESUH
Breakpoint in program LEBNEF04 (CREATE_SRV_POS), check the delivered data from function module
MS_FILL_TABS_FROM_EXT_DATA
Breakpoint in program LEBNEF17 (form DIEN_MAINTAIN

Service Purchase Orders (MM-PUR Interface)

Interface components
Function module: MS_SERVICE_PACKAGE
Function group: MLSP
Communication structure: COMSRV
Global accounting table (internal): ACC_TAB
Transaction ME21
Main MM-PUR program: SAPMM06E
subroutine: form DIEN_MAINTAIN
Transaction ME21N
Main MM-PUR program: SAPLMEGUI
Function module: MS_SERVICE_PACKAGE_PBO

Debugging and message processing hints

Account assignment of requisition or PO item is wrong: breakpoint in function module MS_SERVICE_PACKAGE -> check entries in
internal table ACC_TAB -> if ACC_TAB is correctly filled, the error must be searched in MM-PUR, otherwise in MM-SRV
How to find entries in table ESLL: use view ML_ESLL with document and item number
Service account assignment or services are missing by copying services from requisition: check entries (item number, document number,
package number) in table ESLH -> correction report RMPRKONT
How to check BAPI problems:
Function module: BAPI_PO_CREATE or BAPI_PO_CREATE1 (since 46C)
Execute SE37 with BAPI in test mode using test data directory (note 420332 describes how to fill BAPI structures)
Breakpoint in include LMEWPF01 (form PO_ITEM_GENERATE), check CESLL, CESKL, CESUH
Breakpoint in function module ME_CREATE_PO_ITEM, check returned entries in XESUC, XESLL, XESUH, XESKN from
function module MS_FILL_TABS_FROM_EXT_DATA

Service Entry Sheet Acceptance (MM-IM Interface)

MM-PUR Interface
Purchase requisitions

Purchase orders
MM-IM Interface
MM-IV Interface
CO Interface (commitments)
PM Interface
Report MEDEBUG

Material document is created via ML81N or ML81

not possible to use transaction MIGO (MB01) for service items
transaction MBST is also not allowed (due to an error it was possible in the past, corrected with note 323521)
Delivery costs are not supported for services (consulting note 381030)
In case of GR-Based IV the number of lines in the material document corresponds to the number of lines in table ESKN
In case of Service-Based IV the number of lines in the material document corresponds to the number of lines in table ESKL
Function group: EINR
Function module: ME_READ_ITEM_GOODS_RECEIPT
subroutines:
XEBEFU_AUFBAUEN_DIEN
XEBEFU_AUFBAUEN_DIEN_L in case of PO items with service based GR"-Flag
content of internal table XEBEFU is taken over to MM-IM
Important internal tables
XEBEFU: item information for GR (more than one entry per item
XESLL: service package
XESKL: mapping account assignment to service line
XESKN: total account assignments
POT: PO items (EKPO)
KNT: PO item account assignment

possible)

Debugging hints
Main question: is this a MM-SRV or a MM-IM problem ?
Breakpoint in function module ME_READ_ITEM_GOODS_RECEIPT (EINR) and check entries in internal table XEBEFU
If XEBEFU is ok > MM-IM problem
If XEBEFU not ok > MM-SRV problem
Errors during acceptance
Breakpoint in program LMLSRF0W (form ACCEPTANCE) at call function MB_CREATE_GOODS_MOVEMENT' ". In EMKPF can be
analysed which field is wrong or empty.

Invoice Verification (MM-IV Interface)

MM-PUR Interface
Purchase requisitions
Purchase orders
MM-IM Interface
MM-IV Interface
CO Interface (commitments)
PM Interface
Report MEDEBUG
Function group: EINR
Function module: ME_READ_ITEM_INVOICE
subroutines:
XEK08R_AUFBAUEN_DIEN
XEK08R_AUFBAUEN_DIEN_L in case of PO items with service based GR"-Flag
XEK08R_AUFBAUEN_REPL in case of PO items with invoicing plans
Internal table XEK08RN contains the suggested values to MM-IV
Important internal tables
XEK08RN: item information for IV
TEKSEL: Table of selected purchase orders, gets populated with function ME_SELECT_DOCUMENTS
XESLL: service package
XESKL: mapping account assignment to service line
XESKN: total account assignments
POT: PO items (EKPO)
KNT: PO item account assignment

Commitments (CO Interface)

MM-PUR Interface
Purchase requisitions
Purchase orders
MM-IM Interface
MM-IV Interface
Commitments (CO Interface)
PM Interface
Report MEDEBUG
Prerequisites
Commitment update for controlling area must be active (Transaction OKKP)
cost objects must be active for commitment (Transaction KOT2 for orders, KS02 for cost centers)
Unit of measure used at item level must be set up for value based commitment (trx. CUNI), otherwise the commitment reduction will be
wrong (notes: 93951, 38744)
Commitment is created for purchase requisitions and purchase orders
Function group: EINS
Function modules: ME_STATISTICS_RKO (PO commitment) ME_STATISTICS_EBAN_RKO (requisition commitment)
subroutines:
DIEN_BEREITSTELLEN (PO commitments)
Internal table XEKBP contains the suggested values to CO in case of PO commitment
Internal table XEKPR contains commitment values in case of requisition commitment
Commitment reduction
Purchase requisition commitments will be reduced by PO's created with reference to this requisition
PO commitments will be reduced by GR postings in case of valuated GR
PO commitments will be reduced by IV postings in case of non-valuated GR
PO commitments can be completely reduced by setting the final delivery flag (for valuated GR) or by setting the final invoice flag (in case
of non-valuated GR)
Report RKANBU01 rebuilds the commitment
Important tables and fields
The commitment values can be found in table COOI
Important fields in table COOI:
REFBN - document number (PO or requisition)
RFPOS - item number
BLDAT - document date
ORGWTH - total commitment value in local currency
WHGBTR - rest commtiment value in local currency
Table COSPA contains the sum values for PO's and requisitions
Report RKACSHOW can be used to see the commitment values

Interface PM/PS
MM-PUR Interface
Purchase requisitions
Purchase orders
MM-IM Interface
MM-IV Interface
Commitments (CO Interface)
PM Interface
Report MEDEBUG
Transaction IW31
Main program: SAPLMLSP
subroutine: INT_ORDER_PBO
Function module: CO_IH_MMSRV_INFO_GET (information from PM),
CO_IH_MMSRV_INFO_SET (information to PM),

ME_REQUISITION_EXT (to create/update requisitions)

Report MEDEBUG
Debugging help tool
Execute report MEDEBUG via SE38
For each topic (grouped in tab titles) several breakpoints possible
After setting the breakpoints it is not necessary to restart the transaction

Important tables in MM-SRV -1-

Important tables, views, and structures in MM-SRV -2-