cancel
Showing results for 
Search instead for 
Did you mean: 

LX42 transaction returns Maintenance orders also in addition to PP orders

sap_pp13
Active Contributor
0 Kudos

Hi,

  We use the PP-WM interface and we are looking at the usage of LX42 transaction which states 'Evaluation PP order from WM view'. On Executing the same with out providing any selection criteria in the screen, the transaction returns other types of orders like maintenance orders in addition to PP orders.

Not sure why the transaction description is specific to PP while other order types/diff order categories also come out. Any pointers to use the transaction correctly/pre-reqs if any etc., will be very much appreciated.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

The order field in the report selection is mapped to AFPO-AUFNR, just cross check whether your output matches with AFPO entries. Also you can find out the details about this report by clicking the information button in the selection.

Regards

Vijay

sap_pp13
Active Contributor
0 Kudos

Thanks a lot Vijaya. We checked in the AFPO table. The maintenance orders we report appear with plant/planning plant columns(PWERK/DWERK) as blank and very surprisingly with an order category (DAUTY) as 32.

Normally we do not get to see this order category at all in the SAP standard. 30 is the standard PM order category as it is like 10 for PP orders.

We will revert back after checking further on this.

sap_pp13
Active Contributor
0 Kudos

Hi, We did raise an OSS but could not get a convincing reason for why the Order category cannot be used a criteria to filter out PP orders alone in the LX42 output. The reply was the order category does not make any significance from a WM functionality point of view and order integration is not fully supported. Also no developments are planned in the near future also.

However we could get an answer to why Order category appears as 32 instead of the standard 30 which is set in order configuration.
Any PM order with standard Order category 30 and which is set Refurbishment order in config will gets saved as 32 in the backend tables as in below information.

[Definition of Order categories is in include LCOKOTYP:

CONSTANTS:
BEGIN OF auftragstyp,
fert TYPE auftyp VALUE '10', "Fertigungsauftrag
netw TYPE auftyp VALUE '20', "Netzplan
inst TYPE auftyp VALUE '30', "Instandhaltung
hiko TYPE auftyp VALUE '31', "Instandhaltung - Historie
rma TYPE auftyp VALUE '32', "SM Rma-Auftrag (für AFPO)
bord TYPE auftyp VALUE '40', "Prozeßauftrag
qamm TYPE auftyp VALUE '50', "Prüfabwicklung
pord TYPE auftyp VALUE '60', "Personal Order
vert TYPE auftyp VALUE '70', "Versandterminierung].

We also do not see any point in using LX42 further and hence marking the message as complete.

Answers (0)