output determination in im

8/9/2019 Output determination in IM

http://slidepdf.com/reader/full/output-determination-in-im 1/32

Outp u t Dete rm in at i on i n

Inven to ry Management



SAP Online Help 20.11.01

Output Determination in Inventory Management (MM-IM) 2

Copyright

© Copyright 2001 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft®, WINDOWS

®, NT

®, EXCEL

®, Word

®, PowerPoint

®and SQL Server

® are registered

trademarks of Microsoft Corporation.

IBM®, DB2

®, OS/2

®, DB2/6000

®, Parallel Sysplex

®, MVS/ESA

®, RS/6000

®, AIX

®, S/390

®, AS/400

®,

OS/390®, and OS/400

® are registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation.

INFORMIX®-OnLine for SAP and Informix

® Dynamic Server

TM

are registered trademarks of InformixSoftware Incorporated.

UNIX®, X/Open

®, OSF/1

®, and Motif

® are registered trademarks of the Open Group.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web

Consortium,Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology

invented and implemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAPEarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over theworld. All other products mentioned are trademarks or registered trademarks of their respectivecompanies.





Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax





Table of Contents About this document ................................................................................................................................5

General information .................................................................................................................................5

Troubleshooting Guide for Non-Developers ............................................................................................6

Troubleshooting guide with debugging ................................................................................................7

List of symptoms...............................................................................................................................8

Elements of Output Determination.........................................................................................................18

Print version for transaction (T158-WEVER) .....................................................................................18

Field ‘Print’ (RM07M-XNAPR) ............................................................................................................18

Print indicator for movement type (T156-KZDRU) .............................................................................19

Output type (WE01, MLFH...).............................................................................................................19

Message schema (ME0001) ..............................................................................................................20

Condition table ...................................................................................................................................20

Condition records ...............................................................................................................................21

Access sequence ...............................................................................................................................21

Layout sets (SAPScript) .....................................................................................................................21

Collective slips....................................................................................................................................22

Requirements .....................................................................................................................................22

Number of GR/GI slips (MSEG-WEANZ)...........................................................................................23

Labels .................................................................................................................................................23

Partner functions ................................................................................................................................24

Missing part mails...............................................................................................................................24

Mail text ..............................................................................................................................................27

GR/GI slips for stock transfers ...........................................................................................................27

Multiple accounting sheet...................................................................................................................27

Language............................................................................................................................................27

Printer determination ..........................................................................................................................28

Program Logic for Developers ...............................................................................................................29

Output records for a material document (table NAST).......................................................................29

Automatic output records................................................................................................................29

Manual output records ....................................................................................................................29

Deleting output records ......................................................................................................................30

Output determination processing: Graphical overview ...................................................................... 31

Terminology English - German..............................................................................................................32





About this documentThis document describes the output determination in Inventory Management.

• The section Trouble-Shooting guide for non-developers concentrates on troubleshooting and ismainly intended for non-developers. The first part gives a list of important breakpoints and checks.

The second part is organized in the major symptoms that arise when dealing with OSS messagesabout output determination in MM-IM.

• The section Elements of Output Determination describes the single elements of outputdetermination. Some are purely MM-IM, others are general output determination concepts. Thissection may be used as reference when dealing with a special part of the output determination. Itcontains general explanations as well as technical descriptions.

• The section Program logic for Developers deals with the program logic and is mainly intended for developers. However, non-developers can read it, too.

• The last section Terminology English - German contains a list of all output determination terms inEnglish and German.

General informationThe output determination (also called message control ) generates output records (messages) for amaterial document. The messages can be GR/GI slips (e.g. output type WE01), mails (output typeMLFH for missing part mails) or even workflow events (not in standard but can be customized bycustomer).

The output determination program is a central functionality outside MM-IM. It is also used by MM-PUR,SD etc.

Component for the central program (if bug is not due to calling application like MM-IM):CA-GTF-BS-MC

Principle:

The application using the output determination provides the output determination program withapplication data (like plant, storage location) through communication structures (MM-IM:communication structures KOMKBME for header data and KOMPBME for item data). The outputdetermination program uses these application data to determine – with the help of extremely flexibleand complex tables – whether an output type is relevant or not. If an output type can be found for thegiven criteria (application data), an output record will be generated.

For more information about Customizing of Output determination see Implementation Guide.





Troubleshooting Guide for Non-DevelopersBear in mind that the majority of printing problems are attributable to incorrect Customizing or to theuse of user-defined developments. Problems which arise as a result cannot be dealt with by SAPSupport. If you require help with troubleshooting, you can call our Remote Consulting Service.

Before you enter a message in SAP Service Marketplace (OSS) for SAP Support, makesure that there are no errors in Customizing or a user-defined development is notinvolved.

In SAP Service Marketplace (OSS) you will find two notes that will help you checking the outputdetermination in your system:

• note 426554: check lists for output determination and printer determination for goods movements

• note 426648: Check list for missing parts mail for goods movements

http://service.sap.com/notes


http://service.sap.com/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700006555532001E













Troubleshooting guide with debugging

Use this troubleshooting guide only if your are familiar with ABAP programming and debugging.

Important checks:

• Does the customer use own condition tables?Check 1:Customizing MM-IM >Output Determination > Output types: note access sequence.

Check 2: Access sequence: check condition table. Standard tables range from 070 to 079. Customer rangeis 5xx. If a customer uses own condition tables and the system cannot find any output record or finds too many of them, this is a consulting problem.

• Does the customer use own print program?Check in Customizing MM-IM > Output Determination > Assign forms and programs (or SE16table TNAPR). Routines like ENTRY_ZE01 or program ZM07MDR are not standard. It mightexplain that a NAST record will not be printed or has wrong data. Ask to change back to standard

and see if the bug still occurs before you go on troubleshooting.Important programs:

• SAPLV61B: output determination program

• SAPM07DR : print program (reads all data per SELECT on database and calls SAPScript layout set.

Important Form-Routines for breakpoints:

• MM07MFD0, DRUCK_PRUEFEN:

the version ( MKPF-WEVER ) is set depending on field RM07M-XNAPR and default version in T158.

Field RM07M-XNAPR itself is set on first screen (dialog) or from parameter NDR

(MB_CREATE_GOODS_MOVEMENT).

• MM07MFN0, KOPFDIALOGSTRUKTUR_FUELLEN and POSIDIALOGSTRUKTUR_FUELLEN

communication structures KOMKBME and KOMPBME are given to the output determinationinterface. There you can check the version (MKPF-WEVER), the print indicator (T156-KZDRU)and the transaction type (MKPF-VGART)

• MB_CREATE_GOODS_MOVEMENT:

the user given in IMKPF-PR_UNAME or IMKPF-USNAM is used for reading parameter NDR in

DRUCK_PRUEFEN and is used for the printer determination in LV61BF0P,PRINTER_PARAMETER_LESEN

• LV61BF0N, NACHRICHTENSTATUS_SCHREIBEN

the output determination program loops over all output types and tries to find a condition record. If a condition record is found (IF XKNUMH NE SPACE), an entry is added to internal table XNAST.

• LV61BF0P, PRINTER_PARAMETER_LESEN

The printer is found in tables TNAD7 and TNAD9 (CASE INDEX. WHEN ‘7’. WHEN ‘9’).

• MM07MFB9, BUCHEN_AUSFUEHREN, CALL FUNCTION RV_MESSAGES_GET

can be used to check the internal table XNAST just before posting (before commit work)

• SAPM07DR, Form ENTRY_...

the data is read from the database (using SELECT *) by the print program. The print routine alsocalls the layout set and the text elements that have to be printed.

• MM07MFT0 for mails only

reads the data and fills mail text. Set parameter for mail processing (call transaction)

• Even if an output record from NAST has been printed immediately in the update task,it is possible to repeat the output with MB90 and debug the print program in dialog.





• It is not possible to debug the print program SAPM07DR during the posting of amaterial document as it is processed in the update task. If an update terminationRV_MESSAGE_UPDATE occurs during the creation of a material document, changethe processing time 4 (immediately) to 3. That way the material document will beposted without update termination and you will be able to debug SAPM07DR in dialogusing MB90.

List of symptoms

Symptom 1: No output record created for material document

Symptom 2: GR/GI slip is printed on wrong printer

Symptom 3: Update termination in RV_MESSAGE_UPDATE

Symptom 4: Wrong data is printed on GR/GI slip

Symptom 5: No mail MLFH

Symptom 6: Mail MLFH is sent without text or to wrong recipient or cannot be processed with CO06

Symptom 7: GR/GI slip is printed although field ‘Print’ is not set (note 205450)








Symptom 1: Nothing gets printed

Step Question Check answer in... If yes,go to

If no,go to

1 Output record generated inNAST?

MB03, item detail, output or SE16 tableNAST with Objkey =MBLNR* (example0050013456*)

15 2

Version MKPF-WEVER

2 Version is set?( MKPF-WEVER )

Breakpoint: MM07MFN0,KOPFDIALOGSTRUKTUR_FUELLEN

(or SE16 table MKPF if document wasposted)

7 3

3 Default version for transaction?(T158-WEVER )

SE16, T158 or breakpoint in MM07MFD0,

DRUCK_PRUEFEN. Can be set in

customizing.

4 Cust.

4 Field ‘Print’ is set ?(RM07M-XNAPR ) Breakpoint: MM07MFD0, DRUCK_PRUEFEN 7 5

5a Parameter NDR is set? (MB01) Check in user data, parameter NDR 7 User

5b Parameter NDR is set?(MB_CREATE_GOODS_MOVEMENT)

Breakpoint: MM07MFD0, DRUCK_PRUEFEN,

IF NOT XMBWL IS INITIAL. Check if the

correct user is set (step 6). The user is setby the caller of MB_CREATE_GOODS_MOVEMENT.

7 6

6 Correct user is set? Breakpoint: MB_CREATE_GOODS_MOVEMENT: fields

IMKPF-PR_UNAME or IMKPF-UNAME.

Check if user has parameter NDR=X (user data).

7 User

Print parameter T156-KZDRU

7 Mvt type has print indicator?

(customizing of movementtypes

SE16 table T156 or breakpoint in MM07MFN0,

POSIDIALOGSTRUKTUR_FUELLEN .

8 Cust.

Condition records found, XNAST entries

8a Condition record exists for theoutput type that should beprinted?

Ask the customer which output type hewants to print (or send mail). E.g. WE01

In customizing of output determination,check

1) Access sequence for output type? (e.g.0003)

2) Condition table for access sequence?(072)

3) Key fields for condition table (e.g.version, print indicator, transaction type)

4) SE16 for condition table (e.g. B072):check if entries match the data given in

KOPFDIALOGSTRUKTUR and

POSIDIALOGSTRUKTUR_FUELLEN

8b Cust.

8b Program finds the conditionrecord?

Breakpoint in LV61BF0N,

NACHRICHTENSTATUS_SCHREIBEN,

9 8a/8c





IF XKNUMH NE SPACE. (loop at KOMT1)

8c Output type in schema? Same breakpoint, check table KOMT1. If output type not in KOMT1, checkcustomizing schema

9 Cust.

9 Printer determination set

correctly?

See symptom 2 step 5c 10 Cust.

10 Condition records are kept untilCOMMIT?

BP in : MM07MFB9, BUCHEN_AUSFUEHREN,

RV_MESSAGES_GET (check XNAST)

15 11

11 XNAST gets refreshed? Breakpoint in RV_MESSAGES_REFRESH

(might be called by another application)

Bug! 15

Output record is generated in NAST but not in spool

15 Output record has status‘Printed’?

SE16 table NAST or MB03, item detail,output

18 16

16 Output record appears inMB90?

MB90 o.k. 17

17 Condition record has correctprocessing time?

MN22 for output type. Check processingtime

• 4 = during posting of material document.

• 3 = print with MB90

• 2 = print with RSNAST00

Only 3 and 4 can be processed with MB90

Cust.

18 Output can be repeated withMB90

Try MB90 19 17

19 Customer uses own print

program?

Check Cust. > Assign forms/programs (or

SE16, table TNAPR).If yes, ask him tochange to std

Modifi

cation

20

20 Text in spool but no immediateprint?

Check printer determination, parameters for printer (read IMG) or breakpoint in

M07DRSON, OPEN_FORM , check structure

ITCPO.





Symptom 2: Wrong printer


If no,go to

1 Check printer in NAST MB03, item detail, output, communication or

SE16 table NAST with Objkey =MBLNR*(example 0050013456*) field LDEST

2 Printer entered manually inMB01?

Ask customer or check field NAST-MANUE o.k.? 3

3 Printer from condition record MN23, display condition record for outputtype(check also if customer has created owncondition table with user)

Customizing

4

4 Printer from printer parameter? Customizing output types 5

5a Printer parameter 7 (TNAD7)? Check SE16 TNAD7 against KOMPBME in MM07MFN0, POSIDIALOGSTRUKTUR .

If goods receipt for PO with assignment, anentry with storage location blank isnecessary

Cust.

5b Printer parameter 9 (TNAD9)? Check SE16 TNAD9 against KOMPBME in MM07MFN0, POSIDIALOGSTRUKTUR .

If goods receipt for PO with assignment, anentry with storage location blank isnecessary.

Check parameter ID ND9 (user group) inuser data. User name is set in MM07MFD0,

DRUCK_PRUEFEN and send to SAPLV61B in

KOPFDIALOGSTRUKTUR .

Cust.

5c Entry for printer determinationis found by program?

Breakpoint in LV61BF0P,PRINTER_PARAMETER_LESEN, CASE

INDEX. WHEN ‘7’. WHEN ‘9’.

6 Printer is found before posting? Breakpoint in MM07MFB9,BUCHEN_AUSFUEHREN, CALL FUNCTION

RV_MESSAGES_GET. Check XNAST

7 Printer is changed by printing

program?

Check print program with SE16 table

TNAPR (see symptom 3 steps 1 and 2).Standard program: breakpoint in M07DRSON, OPEN_FORM , check structure

ITCPO.





Symptom 3: Update termination RV_MESSAGE_UPDATE.

Can happen if OPEN_FORM without CLOSE_FORM or if language is not set.


If no,go to

1 Condition record set to printimmediately in update task?(Processing time = 4)

MN22: check condition record for outputtype. Solution: set time to 3 (print with MB90)so that the customer is able to post thematerial document without termination andyou are able to debug in dialog with SE16.

2 2

2 Output type printed withstandard program?

SE16 table TNAPR (e.g. SAPM07DR,

ENTRY_WE01 for output type WE01)

3 Modif cation

3 Where does the terminationoccurs?

Debug in SAPM07DR (if time set to 3)





Symptom 4: Wrong data printed on GR/GI slip


If no,go to

1 Output type printed withstandard program and withstandard layout set?

SE16 table TNAPR (e.g. SAPM07DR,ENTRY_WE01 and layout set

WESCHEINVERS1 for output type WE01)

2 Modification

2 Wanted field has been added inthe layout set?

SE71, check text elements of windows(especially MAIN)

3 SE71

3 Data read by the program? Debug in routine ENTRY_.... Make sure thetable is read by program and the work area(e.g. MSEG) is filled correctly whenSAPscript element is called by

WRITE_FORM . Be careful that for a field for

window KOPF (only collective slips) has to

be saved in helpdata1 and helpdata2because of the delayed process.

4 Bugor modification

4 Text element is processed byprint program?

Same breakpoint as step 3. Set watchpointat call function ‘ WRITE_FORM’. Check the

text elements called by WRITE_FORM

against text elements in layout set

Bugor modification





Symptom 5: No mail MLFH


If no,go to

1 Does the system gives warning‘Material is a missing part?

Ask the customer or check yourself 4 2

2 Is the missing part customizingset correctly?

Set a breakpoint at the beginning of FEHLTEILE_PRUEFEN (FM07MEF0). If the

program stops at one of the checks,customizing is not set correctly.

3 Cust.

3 Is the material a missing partaccording to MRP?

Breakpoint in FEHLTEILE_PRUEFEN

(FM07MEF0), function module

MISSING_PARTS_CHECK (Routine name in

3.0/3.1: MD_FEHLTEILE_WE) Check internal

XTFEHL. If it is empty, it means either

material is not a missing part or MRPcustomizing is not set correctly.

4 SendOSStoMRP

4 Output record MLFH created for material document?

SE16 table NAST or MB03, item detail,output

5

5 Output record processed bystandard program?

SE16 table TNAPR

Standard: program: RSNASTSO, routineSAPOFFICE_AUFRUF

6 Cust.

6 Condition record exists for MLFH

MN22 for MLFH 7 Cust.

7 Condition record found by

program?

Breakpoint in LV61BF0N,

NACHRICHTENSTATUS_SCHREIBEN,IF XKNUMH NE SPACE (loop at KOMT1)

9 8

8 Output type in schema? Same breakpoint, check table KOMT1. If output type not in KOMT1, checkcustomizing schema

9 Cust.

9 Condition record kept in XNASTuntil commit?

Breakpoint in MM07MFB9,BUCHEN_AUSFUEHREN, CALL FUNCTION

RV_MESSAGES_GET. Check XNAST





Symptom 6: Mail MLFH is sent without text or to wrong partner or cannot beprocessed with CO06s

Step Question/Problem Check answer in... If yes,

go to

If no,

go toMail without text

0 Notes 205951 + 213264

And note 212682.

Check coding 1

1 MLFH is sent to recipient buthas no text

Customizing output types: check if one lineof text has been maintained for MLFH. Readalso IMG for an example of text

2 Cust.

2 Output type MLFH hasprocessing routine for text?

Customizing output types: text routineTEXT_FEHLT_FUELLEN

3 Cust.

3 Text routine is processed? Breakpoint in MM07MFT0,

TEXT_FEHLT_FUELLEN

4 1

4 Text is processed in step 3 butdeleted before posting

Breakpoint in function moduleCOMMIT_TEXT. An external application

might delete our text memory by calling theCOMMIT_TEXT without specifying an

application

Bugor modification

Mail sent to wrong recipient

5 Check recipient name MB03, item data, output or SE16 table NAST 6 6

6 Recipient defined directly incondition record for MLFH

(symptom: mail always sent tosame recipient)

MN22 for MLFH, check communication. Nopartner should be defined there as recipient

is determined dynamically from MRPcontroller

Customizing

7

7 MRP controller has mailpartner?

Breakpoint in FEHLTEILE_PRUEFEN

(FM07MEF0), function module

MISSING_PARTS_CHECK (Routine name in

3.0/3.1: MD_FEHLTEILE_WE) Check field

VM07M-DUSER . Can be set in customizing.

8 Cust.

8 Partner function set correctly? SE16 table NAST: partner should be DP(technical name)

MN22 for MLFH. Press F4 on partner role tofind correct partner name (German version:DP, English version differs, usually PS)

9 Cust.

9 Partner role correctly given tocommunication structure?

Breakpoint: MM07MFN0,POSIDIALOGSTRUKTUR_FUELLEN

Debug single steps in the function modulesuntil function module KOMPBME_FILL.

Cust.or User-Exit

10 Partner exists as Sapofficeuser?

This part does not belong to MM-IManymore. Debugging possible inRSNASTSO, SAPOFFICE_AUFRUF or in

SAPLV61B (RV_MESSAGES_UPDATE)

Mail processing does not get to CO06 or to the wished transaction

11 Text parameters set correctly inoutput record?

MB03, item detail, output, communication.Check parameters against IMG of condition

?? 12











records

12 Parameter routine set correctlyfor output type?

Customizing output types. Parameter routineis TEXT_PARAMETER in SAPMM07M

13 Cust.

13 Condition record has a calltransaction and parameter

names?

MN22 for MLFH, communication. Checktransaction and parameters according to

IMG

14 Cust.

14 Parameter Ids set correctly? Breakpoint MM07MFT0, TEXT_PARAMETER 15

15 Text routine processed? Breakpoint MM07MFT0, TEXT_FEHLT_

FUELLEN (Parameter Ids are set there)

3





Symptom 7: GR/GI slip is printed although field ‘Print’ is not set (note 205450)

Can happen if customer uses own condition tables without print version.


If no,go to

1 Output type has an owncondition table ?

Customizing MM-IM:

• Output types: check access sequence(e.g. 0003) on detail screen

• Access sequence: check conditiontable (e.g. 072) and fields: ‘Printversion’ (WEVER) is missing

Note205450:consultingissue

2

2 Field ‘Print’ set internally? Breakpoint : MM07MFN0,

KOPFDIALOGSTRUKTUR_FUELLEN : field

MKPF-WEVER is set?

3

3 Check why MKPF-WEVER isset although field ‘Print’ initial.

See steps 2 to 6 of symptom 1 for debugging

Modification?









Elements of Output Determination

Print version for transaction (T158-WEVER)

Radio buttons on initial screen of MB01

There are 3 print versions (‘1’, ‘2’, ‘3’). The description of the print versions (individual slip, collectiveslip) is only correct if the customizing is set as SAP recommends. If the customer creates a conditionrecord for an individual slip with the version 3 (collective slip), he will get an individual slip when theusers chooses radio button ‘collective slip’.

Default-Version (T158-WEVER ): determines which print version is set on initial screen of transaction.

If field ‘Print’ is not set, the version will be cleared. That way the system will not find any conditionrecord and will not print any slip.

MB_CREATE_GOODS_MOVEMENT

Because MB_CREATE_GOODS_MOVEMENT works without initial screen, we always use defaultversion for transaction from T158. If printing with MB_CREATE_GOODS_MOVEMENT does not work,check that the IMKPF transaction has a print version in T158. In case of goods receipt for purchaseorders with multiple account assignments, the default version of T158 in only used if ‘1’ or ‘2’. In caseof collective slips, the version is changed to ‘1’ after application of note 442706 in order to beconsistent with the dialogue (transaction MB01).

MIGO

In transaction MIGO the print version is available since note 315434.

Field ‘Print’ (RM07M-XNAPR)

Check box on initial screen and header data screen of MB01. Is set from user parameter NDR = X.

X has to be written in capital letters, otherwise basis error 00002 ‘please enter valid value’ on initialscreen.

With this field it is possible to deactivate the printing of GR/GI slips (but not to deactivate mails)

Technically the field is used in Form routine DRUCK_PRUEFEN (MM07MFD0) to reset the print version

( MKPF-WEVER ). That way all output types working with the print version are deactivated.

Deactivation of output determination not possible !With the field ‘Print’ it is not possible to deactivate the output determination completely(sometimes wished by customer for performance reasons). The output determination isalways processed, even if field ‘Print’ is not set, because it still might be necessary togenerate some mails. The output determination can only be deactivated through codingmodification.

Field ‘Print’ only works for condition tables with version !If the customer uses own condition tables without the version, the field ‘Print’ will have noeffect. The system will find a condition record and will print a slip. Explained in note205450.














Setting of field ‘Print’ and user name in MB_CREATE_GOODS_MOVEMENT

Because MB_CREATE_GOODS_MOVEMENT works without initial screen, field ‘Print’ is setexclusively from the parameter ID NDR of a user record. It is possible to giveMB_CREATE_GOODS_MOVEMENT a user name for print in field IMKPF-PR_USNAM (if initial, the

system works with IMKPF-USNAM . If IMKPF-USNAM is initial, the system works with SY-UNAME). The

value of parameter NDR is read directly from the user data (table USR05) and not through GETPARAMETER NDR , because the user might work parallely with MB11 and there change the parameter

NDR from field RM07M-XNAPR.

If printing with MB_CREATE_GOODS_MOVEMENT does not work, check the user has parameter NDR = X.

Selecting or deselecting NDR does not react like a selection ON/OFF in a transaction if you use aBAPI.

The parameter and the BAPI are in two different memories. The BAPI cannot then recognize that theparameter has been deselected.

MIGO

The field still exists as header data (field GOHEAD-XNAPR on header tabstrip ‘General’).

MIGO bug repaired with note 354033 / 357346: if you create a material document with field ‘Print’ setto X, then display a material document, then create a new one without leaving MIGO and display it, thesecond document might have no field ‘Print’ (= no NAST entries). The reason is that we did not refreshthe function group SAPLV61B after posting.

Print indicator for movement type (T156-KZDRU)

Because most movement types do not need a specific GR/GI slip, we do not use the movement typedirectly in the condition tables. Instead we use the print indicator from table T156.

• Most movement types have print indicator ‘1’ (normal GR/GI slip).

• Mvt 122 has print indicator ‘2’ to distinguish a return delivery slip from a GR slip.

• Mvt 541 has print indicator ‘3’ because it needs a special condition table with debit/credit indicator (SHKZG) so that only one line is printed and not the automatic line.

• Mvt 501 has print indicator ‘6’ (4.0) because it is possible to create 501M lines in MB01. MB01prints normally a GR slip with PO data (mvt 101 uses output type WE01), but mvt 501 needs a GRslip without PO data (output type WA01). As both mvt types use the same condition table, it wasnecessary to distinguish them with the print indicator.

Output type (WE01, MLFH...)

The output type determines what kind of output (slip, mail, workflow event) is generated. Output typesfor GR/GI slips are directly linked to a SAPScript layout set and to a read routine in table TNAPR .

Individual slips and collective slips have different output types because they use different layout setsand have different read routines. Furthermore the output type has a printer parameter (7, 9, U, X) thatis used for the printer determination.

For more information see IMG.

Common errors:

• Customer has assigned the wrong program to an output type in table TNAPR. For example hewants to have PO data on the slip but uses the routine for other goods receipt (Consulting)

• Customer has entered an own read program in TNAPR that does not work (Consulting).

Always check table TNAPR when analysing an output type for an OSS message.











Message schema (ME0001)

A schema gathers all output types that have to be checked by the output determination. In InventoryManagement we use only one schema ‘ ME0001’. The schema is a program constant and cannot be

changed by the customer. The customer can add his own output types to our standard schema.

The output determination program loops over all output types that are defined in the schema and triesto find a condition record for that output type in the corresponding condition table.

In the schema it is possible to define a requirement (Bedingung) for an output type. For example,collective slips need requirement 173 so that they will be printed for the first line only. For that purposethe Form routine KOBED_173 (in SAPLV61B) is processed.

Condition table

A condition table contains the criteria that are relevant for an output type. Our normal condition table isB072 for normal GR/GI slips (can be displayed with SE16). Table key:

• KAPPL Application (always ‘ME’)

•

VGART Transaction type (WE, WA, WR) from T158. Never use WO because we do not printslips for MB04. The transaction type cannot be changed by the customer.

• WEVER Print version from T158 (1 and 2 for individual slip, 3 for collective slip)

• KZDRU Print indicator for movement type (1, 2, 3, 6)

Mails and mvt 541 have their own condition tables.

Customer may create an own condition table but we do not recommend it.

New field in field catalog

A customer may create a condition table with all fields that are contained in our field catalog. The fieldcatalog is defines in table KOMK and is filtered for each application in table T681F. It is filled by our communication structures KOMKBME and KOMPBME. Customer may add and fill new fields as wehave user-exits for all communication structures, but they have to add the fields to the application fieldcatalog (table T681F, can be maintained with transaction NACE)

User name in customer condition table (note 207326)Common customer error:

Customer created an own condition table with the user (ERNAM), but ERNAM is not filledwith the user name (MKPF-USNAM) in our communication structure, so it never worked.Field ERNAM is used for mail MLGR and is filled with the user of purchase order. Thesystem behaves correctly. UNAME (in structure KOMKBME) is filled but is not in our fieldcatalog.

Solution:

In most cases the customer does not need the user in a condition table; the user can beused in the printer determination with 4.0. (This is described in IMG). This is a pureconsulting issue. If customer wants to create his own condition table with user name, hehas to take UNAME in field catalog of application ME (transaction NACE). This is theresponsibility of the consultant only.








The print programs (e.g. SAPM07DR, form ENTRY_WE01) calls the following function modules towork with the layout set:

• OPEN_FORM : to open the layout set and give the printer data

• START_FORM : to give the language

•

WRITE_FORM (e.g. EXPORTING ELEMENT = ‘W1LGMAT’ to print a particular text element.• CONTROL_FORM : e.g. to start a new page, a new window

• CLOSE_FORM to close the layout set and be able to open a new one. Two OPEN_FORMs without

a CLOSE_FORM = update termination in RV_MESSAGES_UPDATE.

Because the text elements are called by the program (in call funtion WRITE_FORM exporting element...) the customer may copy a layout set but still has to make sure that the text elements called byprogram still exist in his layout set.

When a text element is called, all fields to be printed should have already been read by the program. As we read all data (like MKPF, MSEG, EKPO) before calling text elements in standard, there ispractically no risk that a field is empty when the text element is being processed. As we fill thecomplete work area for MSEG, EKPO etc. the customer may add any field from these tables in a text

element.

Only text element for the window KOPF (header data) have a delayed process (not duringWRITE_FORM but after the whole page has been processed. For that reason, it was necessary tostore the work area in ‘old’ fields in the routines HELPDATA1 and HELPDATA2 in SAPM07DR. For the customer it means that you cannot add an MSEG field in the window KOPF because you willalways get the data from the next item and not from the current item.

Collective slipsWe have 3 collective slips: WE03, WA03, WLB3 (used for 541).

A collective slip contains all items of a material document.

It would be logical to have a collective slip at material document level but we do only outputdetermination at item level. That is why we create a collective slip for item 0001. It might a problem if the customer deletes item 0001 before posting. Bug is solved in MIGO only. No solution for MB01.

Common customer errors:

Collective slip printed for all items:

A collective slip is printed for all items. Solution: customer has deleted the requirement 173 for WE03,WA03, WLB3 in the schema.

Header of collective slips contains data from the last item:

In a collective slip it is not possible to add an MSEG field to the header data because you will alwayshave the data of the last item. You can only add an item field in the text element processing the item

data.

Requirements

Requirements are small coding parts (usually IF condition with subsequent setting of a return code)that are used in addition to the condition table check. If a condition record is found for an output typebut the requirement is not fulfilled, the output type will not be generated. Requirements are assigned toan output type in the schema table. They can be maintained with transaction VOFM (also accessible inCustomizing). We use requirements for collective slips and mails.

For example, collective slips need requirement 173 so that they will be printed for the first line only.For that purpose the Form routine KOBED_173 (in SAPLV61B) is processed.

You can find the coding of a requirement either with SE80 for program SAPLV61B or with VOFM.

See also common error for collective slips.





No print if empty requirement:

If an output type has a requirement that is not used, it might happen that the output record will notgenerated. The technical reason is that the program SAPLV61B checks the return code (SY-SUBRC =0) after the execution of a requirement. So if a return code was set (SY-SUBRC <> 0) before arequirement, the system considers that the requirement gives a return code and thus is not fulfilled.Solution: remove the requirement from the output type if the requirement is empty or always set SY-

SUBRC = 0 in the requirement..

If you use your own requirements, do not forget to reset the return code (SY-SUBRC = 0) if therequirement is fulfilled.

Number of GR/GI slips (MSEG-WEANZ)Used only for individual slips because it depends on material. Output types: WE01, WE02, WF01,WF02. The idea is to print a number of slips that corresponds to number of pallets delivered. If amaterial always has a fixed quantity by pallet, you can maintain it in the material master (quantity GRslips on storage location view). It will be proposed in MB01.

WEANZ is recalculated when the quantity is distributed among storage locations. Note 432947.

Set in program SAPM07DR , Forms AUSGABE_WE01, AUSGABE_WE02 etc.(Include M07DRAUS).

The Number of GR/GI slip is active for goods receipts only in the old MBxx transactions. Itis never read in case of goods issue! A customer tried to print labels on the base of

field WEANZ during goods issue, but the field is not filled if you create the items on thedetail screen. It is only filled per chance on the list screen. WEANZ should not be used for GI.

MIGO:Here WEANZ is processed for all goods movements, but in the print programs it is onlyimplemented in the GR slips WE01 and WE02.

“Number of GR/GI slip” in MIGO 4.6B/4.6C?

We implemented the entry field in MIGO with note 333860. However in 4.6C it is necessary to set thefield as visible in MIGO customizing (note 403003).

Which output types can use WEANZ to calculate the number of slips/labels?

In the print program there are only two kind of output types working with field WEANZ:

• Individual GR slips WE01 and WE02: in form ENTRY_WE01 and ENTRY_WE02 we perform theslip printing as many times as indicated in WEANZ. The field is not active in a collective slip as it isan item information. If item 1 says 10 slips and item 2 says 4 slips, how many collective slipsshould we print? It does not make sense in a collective slip.

• Labels: field MSEG-WEANZ can be used for the determination of the number of copies (tableT159E see below) for all goods movements in MIGO since note 333860. In MBxx transactions, itworks only for goods receipts as WEANZ is not filled for goods issues.

Labels

There is an own customizing step for setting label printout. The idea is that you have a layout set withtext element ETIKETT. The system determines the number of labels to be printed from the itemquantity and prints the same quantity of text elements (called by WRITE_FORM). In each text elementyou have the same text. That is why the text for the label printout is not defined in the layout set but ina separate text.

Furthermore you can maintain a label type and a label form in the material master. Both fields areused in the condition tables for layout set.

















• Application object (defined in table TTXOB, standard MM07ET): here you can find the text ID (table

TTXID standard 7001), text name and layout set (standard RM07ETIKETT). All data are

maintained in table T159O. We recommend to keep the standard object, text id and text name.

• Label text: report RM07METI to maintain the label text (used for all text elements of the layout set)

• Label types and forms (used in condition tables for labels)

• Number of copies: here you can define which quantity field (e.g. MSEG-MENGE or MSEG-ERFMG) will be used to calculate the number of copies (table T159E). A customer wanted to use

field VM07M-ANZGEB (number of containers in QM), but not possible because it is not an MSEGfield and the program SAPM07DR can only work with DB fields. A modification was proposed inM07DRETI, form ETI _DRUCK (read ANZGEB from table QALS to set field ANZAHL1. Another customer wanted to use field MSEG-WEANZ but it does not work in case of GI (or reversal GIs) inMBxx transactions, see chapter WEANZ above. In MIGO it should work for all goods movementssince note 333860 as we always calculate WEANZ.

Labels and collective slips (output type WEE3):

There is no such thing as a collective label. If you use print version 3 and you have created thecondition records as recommended in Customizing, you will get one output record for WE03 for thefirst item and one WEE3 for each item. You will thus have one collective slip with all items andindividual labels for each item. The content of WEE1, WEE2 and WEE3 is exactly the same, they alluse form routine ETI_DRUCK. If you enter requirement 173 for WEE3 and hope to get one collectivelabel, you will only get labels for the first item with data of the first item.

No labels in MIGO 4.6C after Support Package 15:

You need to set field WEANZ as visible for the movement types used (see note 403003).

To transport label texts, use report RSTXR3TR .

Form routines in SAPM07DR:

ETI_DRUCK (include M07DRETI): here the number of copies is calculated from T159O and the text is

read in perform ETIKETTENTEXT_LESEN. The text element ETIKETT is called (call function‘ WRITE_FORM’ exporting element = 'ETIKETT') in forms WRITE_LINES and WRITE_LAST..

Partner functionsWe only use two partner functions for mails in MM-IM. We do not use any partner functions for slips.

The partner functions are set by the program in MM07MFN0, POSIDIALOGSTRUKTUR_FUELLEN, call

function KOMPBME_FUELLEN. We use the technical partner functions MP for MLGR and DP for MLFH.

Partner function is language-dependent!

In table TPAUM you can find the translation of the partner function in different languages. The English

translation changes from release to release! See OSS note 54000.

Missing part mails

A lot of customers have problem customizing the missing part mails because they not only have tocustomize the output determination but also the missing part check itself.

For detailed information see IMG of missing parts and output determination

The missing part mail is a kind of availability check. We check during a goods receipt if the material ismissing for some MRP requirements in the past. In MRP customizing you can define a time horizon todetermine how far in the past the system has to check the MRP requirements.

In MENGE_PRUEFEN > FEHLTEILE_PRUEFEN we call an MRP function module that gives us a list of

non fulfilled MRP requirements for the material. If a material has non fulfilled requirements, we send a

mail to the MRP controller














If the customer does not get the message ‘Material is a missing part’, the problem will not be a MM-IMbut an MRP problem. Set a breakpoint in FEHLTEILE_PRUEFEN (FM07MEF0), function module

MISSING_PARTS_CHECK (Routine name in 3.0/3.1: MD_FEHLTEILE_WE)

• If you do not get to the breakpoint, it means the missing part is not active (wrong customer setting)

• If you get to the breakpoint but the function module does not export an internal table with the list

of MRP requirements, it means either the material is not a missing part or wrong customer settingin MRP. This is not an MM-IM problem but an MRP problem!!

• If you get a list of MRP requirements from the function module but the customer does not get anymail or gets an empty mail, this is an MM-IM problem (usually wrong customizing of outputdetermination).

If the customer gets a mail for a movement type for which he does not want any or if he hasperformance problems, it is possible to deactivate the missing part checks in table T156S (T156SCfrom 4.6 on) with the checking rule ** (note 102248).








Missing Parts mail: overview

SAPMM07M

MENGE_PRUEFEN

> Fehlteile_pruefen

MISSING_PARTS_CHECK

(MRP program)

-

Table XTFEHLVM07M-XFMAT = X

BUCHEN_NUMMERNVERGABE

> MESSAGING

SAPLV61B

(Output determination)

This is not MM-IM!!

InternaltableXNAST:entry MLFH

SAPOFFICE_AUFRU

External Performs to fillmail text and mail

arameters

MAIL

BUCHEN_AUSFUEHREN

MM07MFT0:

TEXT_FEHLT_FUELLEN

Table XTLINES





Mail text

You can find examples of mail texts in IMG.

Common errors:

Mail variables not replaced in mail:

In the old SAPSpript editor (SE71), the text variables (e.g. MSEG-MATNR) were defined directly in thetext as &MSEG-MATNR&. In the new editor you cannot enter the text variable directly in the editor,youneed to add the text variables through the menue..Make sure the fields you add to the layout setare defined as a variable and not as text in the layout set. In transaction SE71 it should blink when youclick on it.

See also notes 205951 and 213264 (bug in MB_MESSAGE_UPDATE)

Text changes do not appear in mail:

Before 4.6B all mail texts were defined at output type level.

Since 4.6B it is possible to define a mail text at output type level and at condition record level. When

you create a condition, the mail text from the output type is internally copied to the output record. So if you change the mail text at output type level, you need to delete the condition record and recreate it inorder to get the text changes to the condition record.

GR/GI slips for stock transfersUsually the customer wants to have only one GI slip for stock transfers (on the supplying side only),but if he uses individual slips (WA01, WA02), he will get automatically two. In order to get only one, hehas to make the slips dependent from the debit/credit indicator. This is explained in consulting note86725.

If the customer uses a collective slip, he will get only the items for the supplying side, because wemake a check in the program that the item has not been created automatically (MSEG-XAUTO in form

LESEN_WAS). This was implemented with 3.1 in note 32244.

Multiple accounting sheetIf the PO has multiple accounting, we print automatically an accounting sheet together with theindividual slip. The accounting sheet is printed on a separate layout set MB_MFKTO and contains thedetail of the accounting.

• Quantities on the accounting sheet: the quantity is the quantity planned in the purchase order because we cannot decide how to distribute the quantity ourselves. It has to be done by the GRclerk.

• Collective slip: not possible with multiple accounting, we switch automatically to individual slip(since note 15839)

• Layout set MB_MFKTO: customizable since 4.5B only (note 103577 implemented in 4.0BHotpackage 65). Customizing is possible via an entry in table T159N for program M07DRKTO.The entry does not exist in standard in the current releases (4.0B - 4.6C) but will be delivered withthe next release.

The logic to switch to individual slips has not been implemented in MB_CREATE_GOODS_MOVEMENTbefore note 442706. Note 442706 change the behavior according to the dialogue transaction MB01.

Language

Has to be set when calling START_FORM , otherwise termination RV_MESSAGE_UPDATE.

Can be set dynamically by program SAPM07DR from T001W language. Can also be set by customer in condition record.


























Printer determination

See IMG and check list 2 from note 426554.








Program Logic for Developers

Output records for a material document (table NAST)

The output records are stored in table NAST. Table Key:

Field name Field description Field value used in MM-IM

KAPPL Application ‘ME’ (Constant for MM-IM)

OBJKY Object key Is composed of:

- MBLNR Material document number

- MJAHR Material document year

- ZEILE Material document item

KSCHL Output type Examples: WE01, WE02, WE03, WA01, MLGR, MLFH

Automatic output records

Usually output records are generated in the background during a goods movement, if customizing isset correctly. The user does not bother to see which output types will be found.

Technical process (only for ABAP developers):

In SAPMM07M the following routines are processed:

1) In Form-Routine DRUCK_PRUEFEN (MM07MFD0) field MKPF-WEVER is set depending on the print

field (RM07M-XNAPR ) and the default print version (T158-WEVER) or the print version chosen on

the initial screen.

2) The print indicator of the movement type is read from table T156 (T156-KZDRU)

3) In BUCHEN_NUMMERNVERGABE a few routines are processed:

• KOPFDIALOGSTRUKTUR _ FUELLEN: Header data from MKPF (like transaction type VGART,

Version WEVER) are given to the communication structure KOMKBME.

• POSIDIALOGSTRUKTUR _ FUELLEN: Item data from MSEG (e.g. print indicator of movement

type T156-KZDRU, plant, storage location) are given to communication structure KOMPBME.Both communication structures KOMKBME and KOMPBME will be transmitted to the outputdetermination and are used for reading the condition tables.

• MESSAGING: here the actual output determination is processed. The output types that have

been found relevant are stored in internal table XNAST.

4) In BUCHEN _ AUSFUEHREN function module MB_MESSAGE_UPDATE is called in dialog. First it

replaces the mail variables in dialog with function module RV_MESSAGES_MAIL_REPLACE. This is

necessary for goods movements posted with MB_CREATE_GOODS_MOVEMENT because MB_POST_DOCUMENT resets all internal tables ( MB_MOVEMENTS_REFRESH is called) and we need

the internal tables to fill the mail variables (notes 205951 + 213264). Then it sets a PERFORM ON

COMMIT, which itself sets a CALL FUNCTION IN UPDATE TASK. This is necessary to ensure

that data such as batch classification data or QM inspection lot are available for printing.

5) In the update task the output records from internal table XNAST are written in DB table NAST.Table NAST is linked to table MSEG through the object key.

Manual output records

If customizing is not set correctly, it might be necessary to enter the output type manually duringcreation (MB01) or change (MB02) of material document.

Menue: Detail > More functions > Messages/Output (also available as pushbutton from 4.0 on)Technical process when working with the output maintenance full screen:











If the users calls the full screen of output maintenance before posting, the output determination will notbe processed in BUCHEN_NUMMERNVERGABE. It will already be processed before sending the full

screen. That way, it is possible to display the output types that have been found automatically.

NACHRICHTEN_PFLEGE (MM07MFM0)

NACHRICHT_ERZEUGEN

KOPFDIALOGSTRUKTUR_FUELLEN (MKPF -> KOMKBME)

POSIDIALOGSTRUKTUR_FUELLEN (MSEG -> KOMPBME)

MESSAGING (output determination)

RV_MESSAGES_MAINTENANCE : sends the output maintenance full screen (not MM-IM)

In MB01 all output records will be renumbered in BUCHEN_NUMMERNVERGABE and given to the update

task in BUCHEN_AUSFUEHREN through function module MB_MESSAGE_UPDATE.

In MB02 function module MB_MESSAGE_UPDATE is called directly after the output maintenance.

You can recognize manual output records in table NAST with field NAST-MANUE (check with SE16)

The data processing might slightly differ when working with the output maintenancescreen or posting the material document without having a look at the output types as thedata is processed at different times. When working with the output maintenance screen,some application data might not be available. It was a bug in 3.0 for label print (bug fixed).

MIGO

In Release 4.6B and 4.6C we do not have the output maintenance screen. Therefore it is not possibleto enter manual output types. In material document display it is possible to start the automatic outputdetermination with a checkbox ‘Print’ in the header general data. It is also possible to get to the outputfull screen in display mode (pushbutton in item tabstrip. The output determination program does not

support the subscreen technique yet, so it was not possible to have the output maintenance screen asan item tabstrip).

Why is it not possible to maintain output types manually in MIGO?

We assume that a user only has to maintain manual output types because the customizing is not setcorrectly. There is no real justification for having to maintain manual output types.

Deleting output records

Output records are linked to the material document through the object key and are therefore deletedduring the archiving of the material documents.





Output determination processing: Graphical overview

‚3‘

KOMKBME/KOMPBME

SAPMM07M

SAPLV61B

NAST

Update TaskSAPMM07M

(RV_MESSAGES_

UPDATE)

MB90 RSNAST00

Processingtime: ‚4‘

‚2‘

Print program: SAPM07DR

SPOOL

GR/GIslip




Terminology English - German

English German

Access sequence Zugriffsfolge

Condition record Konditionssatz (in condition table and tableNACH)

Condition table Konditionstabelle (e.g. B072)

GR/GI slip Warenbegleitschein, WE-/WA-Schein

Layout set Formular (SAPScript)

Label printout Etikettendruck

Output determination (or message control) Nachrichtenfindung

Output record Nachrichtensatz (table NAST)

Output type Nachrichtenart

Missing part mail Fehlteilemail

Print version (for transaction) Version, Druckversion (T158-WEVER)

Print indicator (for movement type) Druckkennzeichen (T156-KZDRU)

Indicator ‘Print via output control’ (on initialscreen)

Kennzeichen ‘Drucken’ (RM07M-XNAPR)

Partner function Partnerrolle

Requirement Bedingung (transaction VOFM)

Schema (message schema) Schema (ME0001)

output determination in im

Documents