Output determination in IM

March 28, 2018 | Author: YOYONOVITCH | Category: Page Layout, Ibm Db2, Parameter (Computer Programming), Input/Output, Troubleshooting
Share
Report this link


Comments



Description

Output Determinationin Inventory Management SAP Online Help 20.11.01 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 the express 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 software components 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 Software Incorporated. ® ® ® TM are registered trademarks of Informix ® 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, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies. Output Determination in Inventory Management (MM-IM) 2 SAP Online Help 20.11.01 Icons Icon Meaning Caution Example Note Recommendation Syntax Output Determination in Inventory Management (MM-IM) 3 ............................................................................ 28 Program Logic for Developers .......................................................................SAP Online Help 20....................................................... 30 Output determination processing: Graphical overview ....................................... 21 Access sequence ...................................................................................................................................................................................................................................................................................................................... 20 Condition records .................................................... 22 Number of GR/GI slips (MSEG-WEANZ)....................................................................................................................................................................................................................................................................................................................................................................................................... 8 Elements of Output Determination................... 31 Terminology English ............................................................................................................................................................................................................................................... 23 Labels .......................................................................... 18 Print version for transaction (T158-WEVER) ......................................................................................................................... 29 Deleting output records ................................................ 5 General information ............. 20 Condition table ..................................................... 29 Manual output records .............................................. 24 Mail text ........................................................................................................................................ 29 Output records for a material document (table NAST).................................................................................................................................................. 19 Message schema (ME0001) ................................................ 6 Troubleshooting guide with debugging ............................................................................................................................................................................................................................................ 21 Layout sets (SAPScript) .................... 27 GR/GI slips for stock transfers ..................................................................... 7 List of symptoms....................German ................................................................................................................................................................................... 32 Output Determination in Inventory Management (MM-IM) 4 ................................................)......................... 27 Multiple accounting sheet................................................................................................ 18 Print indicator for movement type (T156-KZDRU) ............................................................................................. 21 Collective slips................................................................................................................................ 19 Output type (WE01........................................................................................................................................ 22 Requirements ................................................................................ 18 Field ‘Print’ (RM07M-XNAPR) ................................................... 27 Printer determination .......................... 27 Language............................................................................... MLFH............................................................... 24 Missing part mails......................................................................................................................................................... 5 Troubleshooting Guide for Non-Developers ...................................................................................................................................... 23 Partner functions ..................................................................................11..................................................... 29 Automatic output records.................................................01 Table of Contents About this document ......... The messages can be GR/GI slips (e. mails (output type MLFH for missing part mails) or even workflow events (not in standard but can be customized by customer).German contains a list of all output determination terms in English and German. General information The output determination (also called message control) generates output records (messages) for a material document. The second part is organized in the major symptoms that arise when dealing with OSS messages about output determination in MM-IM.g. • The section Trouble-Shooting guide for non-developers concentrates on troubleshooting and is mainly intended for non-developers. The output determination program is a central functionality outside MM-IM. storage location) through communication structures (MM-IM: communication structures KOMKBME for header data and KOMPBME for item data). SD etc. • The section Elements of Output Determination describes the single elements of output determination. It is also used by MM-PUR. non-developers can read it. • The section Program logic for Developers deals with the program logic and is mainly intended for developers. If an output type can be found for the given criteria (application data). others are general output determination concepts. output type WE01). For more information about Customizing of Output determination see Implementation Guide. However.01 About this document This document describes the output determination in Inventory Management. Some are purely MM-IM. It contains general explanations as well as technical descriptions. The first part gives a list of important breakpoints and checks. • The last section Terminology English .11. too. The output determination program uses these application data to determine – with the help of extremely flexible and complex tables – whether an output type is relevant or not. an output record will be generated. Output Determination in Inventory Management (MM-IM) 5 .SAP Online Help 20. 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 with application data (like plant. This section may be used as reference when dealing with a special part of the output determination. 11.SAP Online Help 20.01 Troubleshooting Guide for Non-Developers Bear in mind that the majority of printing problems are attributable to incorrect Customizing or to the use of user-defined developments. In SAP Service Marketplace (OSS) you will find two notes that will help you checking the output determination 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 Output Determination in Inventory Management (MM-IM) 6 . Before you enter a message in SAP Service Marketplace (OSS) for SAP Support. If you require help with troubleshooting. Problems which arise as a result cannot be dealt with by SAP Support. make sure that there are no errors in Customizing or a user-defined development is not involved. you can call our Remote Consulting Service. Important Form-Routines for breakpoints: • MM07MFD0. it is possible to repeat the output with MB90 and debug the print program in dialog. If a condition record is found (IF XKNUMH NE SPACE). Field RM07M-XNAPR itself is set on first screen (dialog) or from parameter NDR (MB_CREATE_GOODS_MOVEMENT). Output Determination in Inventory Management (MM-IM) 7 . an entry is added to internal table XNAST. PRINTER_PARAMETER_LESEN • LV61BF0N. If a customer uses own condition tables and the system cannot find any output record or finds too many of them. • Does the customer use own print program? Check in Customizing MM-IM > Output Determination > Assign forms and programs (or SE16 table TNAPR). DRUCK_PRUEFEN: the version (MKPF-WEVER) is set depending on field RM07M-XNAPR and default version in T158. CALL FUNCTION RV_MESSAGES_GET can be used to check the internal table XNAST just before posting (before commit work) • SAPM07DR. Set parameter for mail processing (call transaction) • Even if an output record from NAST has been printed immediately in the update task. Customer range is 5xx.01 Troubleshooting guide with debugging Use this troubleshooting guide only if your are familiar with ABAP programming and debugging. the data is read from the database (using SELECT *) by the print program. Important programs: • SAPLV61B: output determination program • SAPM07DR: print program (reads all data per SELECT on database and calls SAPScript layout set. There you can check the version (MKPF-WEVER). Check 2: Access sequence: check condition table. WHEN ‘9’). WHEN ‘7’.. Routines like ENTRY_ZE01 or program ZM07MDR are not standard. • MM07MFB9. • MM07MFN0. BUCHEN_AUSFUEHREN. It might explain that a NAST record will not be printed or has wrong data. PRINTER_PARAMETER_LESEN The printer is found in tables TNAD7 and TNAD9 (CASE INDEX. The print routine also calls the layout set and the text elements that have to be printed. • LV61BF0P. • MM07MFT0 for mails only reads the data and fills mail text. Ask to change back to standard and see if the bug still occurs before you go on troubleshooting. 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. Form ENTRY_.SAP Online Help 20.. this is a consulting problem. Important checks: • Does the customer use own condition tables? Check 1: Customizing MM-IM >Output Determination > Output types: note access sequence.11. Standard tables range from 070 to 079. NACHRICHTENSTATUS_SCHREIBEN the output determination program loops over all output types and tries to find a condition record. KOPFDIALOGSTRUKTUR_FUELLEN and POSIDIALOGSTRUKTUR_FUELLEN communication structures KOMKBME and KOMPBME are given to the output determination interface. 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) Output Determination in Inventory Management (MM-IM) 8 .01 It is not possible to debug the print program SAPM07DR during the posting of a material document as it is processed in the update task.SAP Online Help • 20. That way the material document will be posted without update termination and you will be able to debug SAPM07DR in dialog using MB90. change the processing time 4 (immediately) to 3. If an update termination RV_MESSAGE_UPDATE occurs during the creation of a material document.11. go to go to 1 Output record generated in NAST? MB03. 8b Cust. POSIDIALOGSTRUKTUR_FUELLEN. If no. 7 IF NOT XMBWL IS INITIAL. KOPFDIALOGSTRUKTUR_FUELLEN 7 3 4 Cust.11.g. 9 8a/8c Print parameter T156-KZDRU 7 Mvt type has print indicator? (customizing of movement types Condition records found.g. 6 6 Correct user is set? Breakpoint: MB_CREATE_GOODS_MOVEMENT: fields IMKPF-PR_UNAME or IMKPF-UNAME.SAP Online Help 20. DRUCK_PRUEFEN 7 5 5a Parameter NDR is set? (MB01) Check in user data.g. print indicator..g. check 1) Access sequence for output type? (e. WE01 In customizing of output determination. output or SE16 table NAST with Objkey =MBLNR* (example 0050013456*) 15 2 Breakpoint: MM07MFN0. The user is set by the caller of MB_CREATE_GOODS_MOVEMENT. transaction type) 4) SE16 for condition table (e. 4 Field ‘Print’ is set ?(RM07M-XNAPR) Breakpoint: MM07MFD0. DRUCK_PRUEFEN. DRUCK_PRUEFEN. Check if user has parameter NDR=X (user data). B072): check if entries match the data given in KOPFDIALOGSTRUKTUR and POSIDIALOGSTRUKTUR_FUELLEN 8b Program finds the condition record? Breakpoint in LV61BF0N. 0003) 2) Condition table for access sequence? (072) 3) Key fields for condition table (e. Version MKPF-WEVER 2 Version is set? (MKPF-WEVER) (or SE16 table MKPF if document was posted) 3 Default version for transaction? (T158-WEVER) SE16. parameter NDR 7 User 5b Parameter NDR is set? (MB_CREATE_GOODS_MOV EMENT) Breakpoint: MM07MFD0. 8 Cust. 7 User SE16 table T156 or breakpoint in MM07MFN0. NACHRICHTENSTATUS_SCHREIBEN. XNAST entries 8a Condition record exists for the output type that should be printed? Ask the customer which output type he wants to print (or send mail).. item detail. Output Determination in Inventory Management (MM-IM) 9 . T158 or breakpoint in MM07MFD0. version.01 Symptom 1: Nothing gets printed Step Question Check answer in. Can be set in customizing. Check if the correct user is set (step 6). E. If yes. 9 Printer determination set correctly? See symptom 2 step 5c 10 Cust. > Assign forms/programs (or SE16. parameters for printer (read IMG) or breakpoint in M07DRSON. Output Determination in Inventory Management (MM-IM) 17 10 . output 18 16 16 Output record appears in MB90? MB90 o. 10 Condition records are kept until COMMIT? BP in :MM07MFB9. BUCHEN_AUSFUEHREN. check table KOMT1.If yes. If output type not in KOMT1.SAP Online Help 20. (loop at KOMT1) 8c Output type in schema? Same breakpoint.k.01 IF XKNUMH NE SPACE.11. • 3 = print with MB90 • 2 = print with RSNAST00 Cust. table TNAPR). ask him to change to std Modifi 20 cation 20 Text in spool but no immediate print? Check printer determination. OPEN_FORM. Only 3 and 4 can be processed with MB90 18 Output can be repeated with MB90 Try MB90 19 19 Customer uses own print program? Check Cust. Check processing time • 4 = during posting of material document. 17 17 Condition record has correct processing time? MN22 for output type. item detail. check structure ITCPO. 15 RV_MESSAGES_GET (check XNAST) 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. check customizing schema 9 Cust. CALL FUNCTION RV_MESSAGES_GET. communication or If yes.SAP Online Help 20. check structure ITCPO. If goods receipt for PO with assignment. If no. POSIDIALOGSTRUKTUR. POSIDIALOGSTRUKTUR. item detail. OPEN_FORM. PRINTER_PARAMETER_LESEN.k. 6 Printer is found before posting? Breakpoint in MM07MFB9. Output Determination in Inventory Management (MM-IM) 11 . Cust. Check XNAST 7 Printer is changed by printing program? Check print program with SE16 table TNAPR (see symptom 3 steps 1 and 2). Check parameter ID ND9 (user group) in user data. display condition record for output type (check also if customer has created own condition table with user) Custo 4 mizing 4 Printer from printer parameter? Customizing output types 5 5a Printer parameter 7 (TNAD7)? Check SE16 TNAD7 against KOMPBME in MM07MFN0. output. an entry with storage location blank is necessary. Standard program: breakpoint in M07DRSON. an entry with storage location blank is necessary 5b Printer parameter 9 (TNAD9)? Check SE16 TNAD9 against KOMPBME in MM07MFN0. WHEN ‘9’.? 3 3 Printer from condition record MN23.. 5c Entry for printer determination is found by program? Breakpoint in LV61BF0P. User name is set in MM07MFD0. WHEN ‘7’. go to go to SE16 table NAST with Objkey =MBLNR* (example 0050013456*) field LDEST 2 Printer entered manually in MB01? Ask customer or check field NAST-MANUE o. If goods receipt for PO with assignment.11. CASE INDEX. BUCHEN_AUSFUEHREN. DRUCK_PRUEFEN and send to SAPLV61B in KOPFDIALOGSTRUKTUR. Cust. 1 Check printer in NAST MB03.01 Symptom 2: Wrong printer Step Question Check answer in.. SAP Online Help 20.. Solution: set time to 3 (print with MB90) so that the customer is able to post the material document without termination and you are able to debug in dialog with SE16.11. ENTRY_WE01 for output type WE01) 3 Where does the termination occurs? Debug in SAPM07DR (if time set to 3) Output Determination in Inventory Management (MM-IM) If yes. 1 Condition record set to print immediately in update task? (Processing time = 4) 2 MN22: check condition record for output type. 2 Output type printed with standard program? SE16 table TNAPR (e..g.01 Symptom 3: Update termination RV_MESSAGE_UPDATE. SAPM07DR. Can happen if OPEN_FORM without CLOSE_FORM or if language is not set. If no. go to go to 3 2 Modif cation 12 . Step Question Check answer in. .g.g. SAPM07DR. go to go to 1 Output type printed with standard program and with standard layout set? SE16 table TNAPR (e. Be careful that for a field for window KOPF (only collective slips) has to be saved in helpdata1 and helpdata2 because of the delayed process.. check text elements of windows the layout set? (especially MAIN) 3 SE71 3 Data read by the program? Debug in routine ENTRY_. MSEG) is filled correctly when SAPscript element is called by WRITE_FORM..SAP Online Help 20. 4 Bug or modifi cation 4 Text element is processed by print program? Same breakpoint as step 3.01 Symptom 4: Wrong data printed on GR/GI slip Step Question Check answer in.. Set watchpoint at call function ‘WRITE_FORM’. If no. If yes. ENTRY_WE01 and layout set WESCHEINVERS1 for output type WE01) 2 Modifi cation 2 Wanted field has been added in SE71. Check the text elements called by WRITE_FORM against text elements in layout set Output Determination in Inventory Management (MM-IM) Bug or modifi cation 13 .11.. Make sure the table is read by program and the work area (e. .SAP Online Help 20. MN22 for MLFH 7 Cust.0/3. check customizing schema 9 Cust.11. Condition record found by program? Breakpoint in LV61BF0N. IF XKNUMH NE SPACE (loop at KOMT1) 9 8 8 Output type in schema? Same breakpoint. 3 Is the material a missing part according to MRP? Breakpoint in FEHLTEILE_PRUEFEN (FM07MEF0). If no. CALL FUNCTION until commit? RV_MESSAGES_GET. customizing is not set correctly. check table KOMT1. If it is empty. material document? output 5 Output record processed by standard program? SE16 table TNAPR 6 Condition record exists for MLFH 7 5 6 Cust. function module MISSING_PARTS_CHECK (Routine name in 3. If yes. NACHRICHTENSTATUS_SCHREIBEN. Check XNAST Standard: program: RSNASTSO. 9 Condition record kept in XNAST Breakpoint in MM07MFB9. If the program stops at one of the checks. item detail. BUCHEN_AUSFUEHREN. 3 Cust. it means either material is not a missing part or MRP customizing is not set correctly.. 4 Send OSS to MRP 4 Output record MLFH created for SE16 table NAST or MB03. go to 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 customizing set correctly? Set a breakpoint at the beginning of FEHLTEILE_PRUEFEN (FM07MEF0). If output type not in KOMT1. routine SAPOFFICE_AUFRUF Output Determination in Inventory Management (MM-IM) 14 .1: MD_FEHLTEILE_WE) Check internal XTFEHL.01 Symptom 5: No mail MLFH Step Question Check answer in. English version differs. 8 Partner function set correctly? SE16 table NAST: partner should be DP (technical name) 9 Cust. POSIDIALOGSTRUKTUR_FUELLEN Cust. MN22 for MLFH. An external application might delete our text memory by calling the COMMIT_TEXT without specifying an application Bug or modifi cation 6 Mail sent to wrong recipient 5 Check recipient name MB03. item data.11.01 Symptom 6: Mail MLFH is sent without text or to wrong partner or cannot be processed with CO06s Step Question/Problem Check answer in... check communication. Press F4 on partner role to find correct partner name (German version: DP.1: MD_FEHLTEILE_WE) Check field VM07M-DUSER. 3 Text routine is processed? Breakpoint in MM07MFT0. output or SE16 table NAST 6 6 Recipient defined directly in condition record for MLFH (symptom: mail always sent to same recipient) MN22 for MLFH.SAP Online Help 20. output record? Check parameters against IMG of condition Output Determination in Inventory Management (MM-IM) ?? 12 15 . TEXT_FEHLT_FUELLEN 4 1 4 Text is processed in step 3 but deleted before posting Breakpoint in function module COMMIT_TEXT. 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 in MB03. 2 Output type MLFH has processing routine for text? Customizing output types: text routine TEXT_FEHLT_FUELLEN 3 Cust. communication. function module MISSING_PARTS_CHECK (Routine name in 3. 10 Partner exists as Sapoffice user? This part does not belong to MM-IM anymore. Read also IMG for an example of text Cust. or UserExit Debug single steps in the function modules until function module KOMPBME_FILL. 1 MLFH is sent to recipient but has no text Customizing output types: check if one line 2 of text has been maintained for MLFH. 8 Cust. Debugging possible in RSNASTSO.0/3. If no. go to go to Check coding 1 Mail without text 0 Notes 205951 + 213264 And note 212682. If yes. item detail. No partner should be defined there as recipient is determined dynamically from MRP controller Custo 7 mizing 7 MRP controller has mail partner? Breakpoint in FEHLTEILE_PRUEFEN (FM07MEF0). output. Can be set in customizing. usually PS) 9 Partner role correctly given to communication structure? Breakpoint: MM07MFN0. 14 Parameter Ids set correctly? Breakpoint MM07MFT0. TEXT_PARAMETER 15 15 Text routine processed? Breakpoint MM07MFT0. communication.SAP Online Help 20.11. TEXT_FEHLT_ FUELLEN (Parameter Ids are set there) 3 Output Determination in Inventory Management (MM-IM) 16 . Parameter routine 13 is TEXT_PARAMETER in SAPMM07M Cust. 13 Condition record has a call transaction and parameter names? MN22 for MLFH. Check transaction and parameters according to IMG 14 Cust.01 records 12 Parameter routine set correctly for output type? Customizing output types. 0003) on detail screen • Access sequence: check condition table (e. go to Note 20545 0: consult ing 2 issue 2 Field ‘Print’ set internally? Breakpoint : MM07MFN0. See steps 2 to 6 of symptom 1 for debugging Modific ation? Output Determination in Inventory Management (MM-IM) If no. go to 17 .11. Step Question Check answer in. 072) and fields: ‘Print version’ (WEVER) is missing If yes..SAP Online Help 20.g. 1 Output type has an own condition table ? Customizing MM-IM: • Output types: check access sequence (e.g.01 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.. KOPFDIALOGSTRUKTUR_FUELLEN: field MKPF-WEVER is set? 3 3 Check why MKPF-WEVER is set although field ‘Print’ initial. In case of goods receipt for purchase orders with multiple account assignments.11. even if field ‘Print’ is not set. 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). In case of collective slips. check that the IMKPF transaction has a print version in T158. the version will be cleared. the field ‘Print’ will have no effect. otherwise basis error 00002 ‘please enter valid value’ on initial screen. Field ‘Print’ (RM07M-XNAPR) Check box on initial screen and header data screen of MB01. the default version of T158 in only used if ‘1’ or ‘2’. That way all output types working with the print version are deactivated.01 Elements of Output Determination Print version for transaction (T158-WEVER) Radio buttons on initial screen of MB01 There are 3 print versions (‘1’. The output determination is always processed. Default-Version (T158-WEVER): determines which print version is set on initial screen of transaction. If printing with MB_CREATE_GOODS_MOVEMENT does not work. because it still might be necessary to generate some mails. Is set from user parameter NDR = X. ‘3’). Explained in note 205450. MB_CREATE_GOODS_MOVEMENT Because MB_CREATE_GOODS_MOVEMENT works without initial screen. 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 system will find a condition record and will print a slip.SAP Online Help 20. MIGO In transaction MIGO the print version is available since note 315434. Output Determination in Inventory Management (MM-IM) 18 . we always use default version for transaction from T158. The output determination can only be deactivated through coding modification. ‘2’. If field ‘Print’ is not set. If the customer creates a condition record for an individual slip with the version 3 (collective slip). The description of the print versions (individual slip. the version is changed to ‘1’ after application of note 442706 in order to be consistent with the dialogue (transaction MB01). Field ‘Print’ only works for condition tables with version ! If the customer uses own condition tables without the version. he will get an individual slip when the users chooses radio button ‘collective slip’. X has to be written in capital letters. collective slip) is only correct if the customizing is set as SAP recommends. That way the system will not find any condition record and will not print any slip. • Mvt 501 has print indicator ‘6’ (4. The reason is that we did not refresh the function group SAPLV61B after posting.0) because it is possible to create 501M lines in MB01. If IMKPF-USNAM is initial. As both mvt types use the same condition table. The BAPI cannot then recognize that the parameter has been deselected. X) that is used for the printer determination. field ‘Print’ is set exclusively from the parameter ID NDR of a user record. • Mvt 122 has print indicator ‘2’ to distinguish a return delivery slip from a GR slip.01 Setting of field ‘Print’ and user name in MB_CREATE_GOODS_MOVEMENT Because MB_CREATE_GOODS_MOVEMENT works without initial screen. MIGO The field still exists as header data (field GOHEAD-XNAPR on header tabstrip ‘General’). Always check table TNAPR when analysing an output type for an OSS message. MB01 prints normally a GR slip with PO data (mvt 101 uses output type WE01). workflow event) is generated. the system works with SY-UNAME). Common errors: • Customer has assigned the wrong program to an output type in table TNAPR. For example he wants 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).) The output type determines what kind of output (slip.11. then create a new one without leaving MIGO and display it. Output type (WE01... U. 9. It is possible to give MB_CREATE_GOODS_MOVEMENT a user name for print in field IMKPF-PR_USNAM (if initial. the system works with IMKPF-USNAM.SAP Online Help 20. Furthermore the output type has a printer parameter (7. mail. Individual slips and collective slips have different output types because they use different layout sets and have different read routines. Output Determination in Inventory Management (MM-IM) 19 . • Most movement types have print indicator ‘1’ (normal GR/GI 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. MLFH. the second document might have no field ‘Print’ (= no NAST entries). Instead we use the print indicator from table T156. we do not use the movement type directly in the condition tables. but mvt 501 needs a GR slip without PO data (output type WA01). The value of parameter NDR is read directly from the user data (table USR05) and not through GET PARAMETER NDR. check the user has parameter NDR = X. The parameter and the BAPI are in two different memories. it was necessary to distinguish them with the print indicator. Output types for GR/GI slips are directly linked to a SAPScript layout set and to a read routine in table TNAPR. MIGO bug repaired with note 354033 / 357346: if you create a material document with field ‘Print’ set to X. Selecting or deselecting NDR does not react like a selection ON/OFF in a transaction if you use a BAPI. then display a material document. Print indicator for movement type (T156-KZDRU) Because most movement types do not need a specific GR/GI slip. If printing with MB_CREATE_GOODS_MOVEMENT does not work. For more information see IMG. because the user might work parallely with MB11 and there change the parameter NDR from field RM07M-XNAPR. collective slips need requirement 173 so that they will be printed for the first line only. 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). he has to take UNAME in field catalog of application ME (transaction NACE). In Inventory Management we use only one schema ‘ME0001’.01 Message schema (ME0001) A schema gathers all output types that have to be checked by the output determination. 3. • WEVER Print version from T158 (1 and 2 for individual slip.SAP Online Help 20. If customer wants to create his own condition table with user name. UNAME (in structure KOMKBME) is filled but is not in our field catalog. This is the responsibility of the consultant only. This is a pure consulting issue. WA. but they have to add the fields to the application field catalog (table T681F. The system behaves correctly. Customer may create an own condition table but we do not recommend it. The output determination program loops over all output types that are defined in the schema and tries to find a condition record for that output type in the corresponding condition table. but ERNAM is not filled with the user name (MKPF-USNAM) in our communication structure. Condition table A condition table contains the criteria that are relevant for an output type. The field catalog is defines in table KOMK and is filtered for each application in table T681F. 2. Our normal condition table is B072 for normal GR/GI slips (can be displayed with SE16). Never use WO because we do not print slips for MB04. The customer can add his own output types to our standard schema.0. For that purpose the Form routine KOBED_173 (in SAPLV61B) is processed. the user can be used in the printer determination with 4. Customer may add and fill new fields as we have user-exits for all communication structures. In the schema it is possible to define a requirement (Bedingung) for an output type.11. 6) Application (always ‘ME’) Mails and mvt 541 have their own condition tables. For example. Solution: In most cases the customer does not need the user in a condition table. Table key: • KAPPL • VGART Transaction type (WE. New field in field catalog A customer may create a condition table with all fields that are contained in our field catalog. The schema is a program constant and cannot be changed by the customer. so it never worked. Output Determination in Inventory Management (MM-IM) 20 . 3 for collective slip) • KZDRU Print indicator for movement type (1. It is filled by our communication structures KOMKBME and KOMPBME. The transaction type cannot be changed by the customer. WR) from T158. (This is described in IMG). Field ERNAM is used for mail MLGR and is filled with the user of purchase order. We recommend the customer to copy our standard layout set (Z. The transported entries need to be deleted with a correction program and re-created manually with MN21.g.g. 4711). In the output type you enter an access sequence (e. 0003).g. It is not possible to transport the condition records because the record 4711 might already exist in the target system and refer to another condition table than B072. W1VERBRMAT). MAIN) and a window has text elements (e. The customer does not need an own read program if he uses fields from these tables. The access sequence contains the condition table that will be checked for the output type. That way he gets a GR slip with empty PO data. Common error: Create a condition record with transaction type WA and output type WE*. WESCHEINVERS1 for output type WE01 Connection between text element of layout set and print program A layout set has windows (e. If you have transported a condition record manually (transport of B072 entry or NACH entry). Theoretically it is possible to assign several condition tables to an access sequence (used in MMPUR) but we do not need it in MM-IM. Layout sets (SAPScript) You can find the layout set used for an output type in table TNAPR. MSEG and PO data fields..01 Condition records Condition records are entries in condition tables. This is not a hotline problem as this is a wrong customer transport. layout set: e.g. You can also check which output types he uses as a lot of customers only create condition records for the output types they use.) if he needs additional fields. W1LGMAT for item information in case of PO without account assignment. Example: table B072 (application: always ‘ME’) VGART WEVER KZDRU Output type WE 1 1 WE01 (used for 101 individual slip) WA 1 1 WA01 (used for 201 individual slip) WA 3 1 WA03 (used for 201 collective slip) In IMG you can find a list of condition records that have to be created by the customer if he wants to use the standard settings. you have an inconsistency in table NACH which can cause MN21 to abort. Always check in the condition table B072 (with SE16) if the condition records have been created as described in IMG and if customer output types are used. W1LGMAT. the system creates an entry in table B072 with a condition number (e. Transaction: SE71. It gives you a hint if customer has understood the output determination and uses own output types. he can implement an exit-routine directly in the layout set (using /: PERFORM as SAPscript command). No transportation of output records: Output records are master data with automatic numbering.g. WASCHEIN*.g. Our read routines in table TNAPR fill all MKPF. Output Determination in Inventory Management (MM-IM) 21 . Access sequence The access sequence is the link between output type and condition table. The condition number refers to the master data in table NACH (with key 4711).g. W1VERBRMAT for item information in case of PO with account assignment). So you will always find a 1:1 relationship between condition table and access sequence. A text element represent a few lines that will be printed together (e. If he needs own form routines (e. to read the batch classification data).. When you create a condition record in Customizing (transaction MN21). Our standard layout sets begin with WESCHEIN*.SAP Online Help 20.11. form ENTRY_WE01) calls the following function modules to work 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. EKPO etc. Output Determination in Inventory Management (MM-IM) 22 . 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 always have the data of the last item. EXPORTING ELEMENT = ‘W1LGMAT’ to print a particular text element. Common customer errors: Collective slip printed for all items: A collective slip is printed for all items. A collective slip contains all items of a material document. WLB3 in the schema.g. It might a problem if the customer deletes item 0001 before posting. to start a new page. You can only add an item field in the text element processing the item data. it was necessary to store the work area in ‘old’ fields in the routines HELPDATA1 and HELPDATA2 in SAPM07DR.. As we fill the complete work area for MSEG. For example. Only text element for the window KOPF (header data) have a delayed process (not during WRITE_FORM but after the whole page has been processed. WA03. They can be maintained with transaction VOFM (also accessible in Customizing). For that reason. If a condition record is found for an output type but the requirement is not fulfilled. a new window • CLOSE_FORM to close the layout set and be able to open a new one.) the customer may copy a layout set but still has to make sure that the text elements called by program still exist in his layout set. For the customer it means that you cannot add an MSEG field in the window KOPF because you will always get the data from the next item and not from the current item. 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 . • CONTROL_FORM: e. That is why we create a collective slip for item 0001.g. It would be logical to have a collective slip at material document level but we do only output determination at item level. For that purpose the Form routine KOBED_173 (in SAPLV61B) is processed. No solution for MB01. there is practically no risk that a field is empty when the text element is being processed. We use requirements for collective slips and mails. Bug is solved in MIGO only. Requirements are assigned to an output type in the schema table. Solution: customer has deleted the requirement 173 for WE03.SAP Online Help 20. Collective slips We have 3 collective slips: WE03. 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. the customer may add any field from these tables in a text element. all fields to be printed should have already been read by the program. When a text element is called. See also common error for collective slips. SAPM07DR. collective slips need requirement 173 so that they will be printed for the first line only. the output type will not be generated. EKPO) before calling text elements in standard.. WA03. As we read all data (like MKPF.11.01 The print programs (e. WLB3 (used for 541). You can find the coding of a requirement either with SE80 for program SAPLV61B or with VOFM.g. MSEG. The field is not active in a collective slip as it is an item information. it works only for goods receipts as WEANZ is not filled for goods issues. how many collective slips should we print? It does not make sense in a collective slip. That is why the text for the label printout is not defined in the layout set but in a separate text.SAP Online Help 20. In each text element you have the same text. but the field is not filled if you create the items on the detail screen.6C? We implemented the entry field in MIGO with note 333860. It is only filled per chance on the list screen.. The Number of GR/GI slip is active for goods receipts only in the old MBxx transactions. you can maintain it in the material master (quantity GR slips on storage location view). do not forget to reset the return code (SY-SUBRC = 0) if the requirement is fulfilled. However in 4. The technical reason is that the program SAPLV61B checks the return code (SY-SUBRC = 0) after the execution of a requirement.11. Output Determination in Inventory Management (MM-IM) 23 . Set in program SAPM07DR. MIGO: Here WEANZ is processed for all goods movements.(Include M07DRAUS). • Labels: field MSEG-WEANZ can be used for the determination of the number of copies (table T159E see below) for all goods movements in MIGO since note 333860. It will be proposed in MB01. Both fields are used in the condition tables for layout set. WEANZ should not be used for GI.6C it is necessary to set the field as visible in MIGO customizing (note 403003). The idea is that you have a layout set with text element ETIKETT. Output types: WE01. If you use your own requirements. it might happen that the output record will not generated. but in the print programs it is only implemented in the GR slips WE01 and WE02. It is never read in case of goods issue! A customer tried to print labels on the base of field WEANZ during goods issue. Note 432947. The system determines the number of labels to be printed from the item quantity and prints the same quantity of text elements (called by WRITE_FORM).6B/4. WE02. So if a return code was set (SY-SUBRC <> 0) before a requirement. Number of GR/GI slips (MSEG-WEANZ) Used only for individual slips because it depends on material. The idea is to print a number of slips that corresponds to number of pallets delivered. If a material always has a fixed quantity by pallet. In MBxx transactions. WEANZ is recalculated when the quantity is distributed among storage locations. WF01. 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 the slip printing as many times as indicated in WEANZ. Forms AUSGABE_WE01. Labels There is an own customizing step for setting label printout.01 No print if empty requirement: If an output type has a requirement that is not used. If item 1 says 10 slips and item 2 says 4 slips. WF02. Solution: remove the requirement from the output type if the requirement is empty or always set SYSUBRC = 0 in the requirement. the system considers that the requirement gives a return code and thus is not fulfilled. AUSGABE_WE02 etc. Furthermore you can maintain a label type and a label form in the material master. “Number of GR/GI slip” in MIGO 4. .01 • Application object (defined in table TTXOB. We use the technical partner functions MP for MLGR and DP for MLFH.11. The partner functions are set by the program in MM07MFN0. If you use print version 3 and you have created the condition records as recommended in Customizing. MSEG-MENGE or MSEGERFMG) will be used to calculate the number of copies (table T159E). The content of WEE1. use report RSTXR3TR. Partner functions We only use two partner functions for mails in MM-IM. We check during a goods receipt if the material is missing for some MRP requirements in the past.g. Another customer wanted to use field MSEG-WEANZ but it does not work in case of GI (or reversal GIs) in MBxx transactions. For detailed information see IMG of missing parts and output determination The missing part mail is a kind of availability check. You will thus have one collective slip with all items and individual labels for each item. but not possible because it is not an MSEG field and the program SAPM07DR can only work with DB fields. they all use form routine ETI_DRUCK. In MRP customizing you can define a time horizon to determine how far in the past the system has to check the MRP requirements. you will only get labels for the first item with data of the first item.SAP Online Help 20. No labels in MIGO 4. WEE2 and WEE3 is exactly the same. you will get one output record for WE03 for the first item and one WEE3 for each item. In MIGO it should work for all goods movements since note 333860 as we always calculate WEANZ. Missing part mails A lot of customers have problem customizing the missing part mails because they not only have to customize the output determination but also the missing part check itself. If you enter requirement 173 for WEE3 and hope to get one collective label. standard MM07ET): here you can find the text ID (table TTXID standard 7001). A modification was proposed in M07DRETI. In MENGE_PRUEFEN > FEHLTEILE_PRUEFEN we call an MRP function module that gives us a list of non fulfilled MRP requirements for the material. 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. call function KOMPBME_FUELLEN. form ETI_DRUCK (read ANZGEB from table QALS to set field ANZAHL1.6C after Support Package 15: You need to set field WEANZ as visible for the movement types used (see note 403003). we send a mail to the MRP controller Output Determination in Inventory Management (MM-IM) 24 . All data are maintained in table T159O. A customer wanted to use field VM07M-ANZGEB (number of containers in QM). Labels and collective slips (output type WEE3): There is no such thing as a collective label. Partner function is language-dependent! In table TPAUM you can find the translation of the partner function in different languages. see chapter WEANZ above. If a material has non fulfilled requirements. The text element ETIKETT is called (call function ‘WRITE_FORM’ exporting element = 'ETIKETT') in forms WRITE_LINES and WRITE_LAST. To transport label texts. We recommend to keep the standard object. text name and layout set (standard RM07ETIKETT). The English translation changes from release to release! See OSS note 54000. We do not use any partner functions for slips. • 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. text id and text name. POSIDIALOGSTRUKTUR_FUELLEN. 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 any mail or gets an empty mail. the problem will not be a MM-IM but an MRP problem.01 If the customer does not get the message ‘Material is a missing part’. 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.6 on) with the checking rule ** (note 102248). If the customer gets a mail for a movement type for which he does not want any or if he has performance problems.SAP Online Help 20. it means either the material is not a missing part or wrong customer setting in MRP.1: MD_FEHLTEILE_WE) • If you do not get to the breakpoint. Output Determination in Inventory Management (MM-IM) 25 . Set a breakpoint in FEHLTEILE_PRUEFEN (FM07MEF0). this is an MM-IM problem (usually wrong customizing of output determination). function module MISSING_PARTS_CHECK (Routine name in 3.11. it is possible to deactivate the missing part checks in table T156S (T156SC from 4.0/3. SAP Online Help 20.11.01 Missing Parts mail: overview SAPMM07M MENGE_PRUEFEN MISSING_PARTS_CHECK > Fehlteile_pruefen (MRP program) This is not MM-IM!! VM07M-XFMAT = X Table XTFEHL BUCHEN_NUMMERNVERGABE > MESSAGING SAPLV61B (Output determination) This is not MM-IM!! BUCHEN_AUSFUEHREN Internal table XNAST: entry MLFH SAPOFFICE_AUFRU F MM07MFT0: External Performs to fill mail text and mail parameters TEXT_FEHLT_FUELLEN Table XTLINES Output Determination in Inventory Management (MM-IM) MAIL 26 . otherwise termination RV_MESSAGE_UPDATE.11. Multiple accounting sheet If the PO has multiple accounting. the mail text from the output type is internally copied to the output record.6C) but will be delivered with the next release.5B only (note 103577 implemented in 4. we switch automatically to individual slip (since note 15839) • Layout set MB_MFKTO: customizable since 4. See also notes 205951 and 213264 (bug in MB_MESSAGE_UPDATE) Text changes do not appear in mail: Before 4. In transaction SE71 it should blink when you click on it. you need to delete the condition record and recreate it in order to get the text changes to the condition record. • Collective slip: not possible with multiple accounting.0B . he has to make the slips dependent from the debit/credit indicator. If the customer uses a collective slip. • 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. This was implemented with 3. The logic to switch to individual slips has not been implemented in MB_CREATE_GOODS_MOVEMENT before note 442706. he will get automatically two. Customizing is possible via an entry in table T159N for program M07DRKTO. we print automatically an accounting sheet together with the individual slip. It has to be done by the GR clerk.6B it is possible to define a mail text at output type level and at condition record level. Can be set dynamically by program SAPM07DR from T001W language. The accounting sheet is printed on a separate layout set MB_MFKTO and contains the detail of the accounting. he will get only the items for the supplying side. This is explained in consulting note 86725. In order to get only one.Make sure the fields you add to the layout set are defined as a variable and not as text in the layout set. youneed to add the text variables through the menue.0B Hotpackage 65).4. but if he uses individual slips (WA01.01 Mail text You can find examples of mail texts in IMG. Language Has to be set when calling START_FORM. So if you change the mail text at output type level. In the new editor you cannot enter the text variable directly in the editor.SAP Online Help 20. Common errors: Mail variables not replaced in mail: In the old SAPSpript editor (SE71).6B all mail texts were defined at output type level. the text variables (e. Since 4. GR/GI slips for stock transfers Usually the customer wants to have only one GI slip for stock transfers (on the supplying side only). because we make a check in the program that the item has not been created automatically (MSEG-XAUTO in form LESEN_WAS).g. When you create a condition. WA02). The entry does not exist in standard in the current releases (4. MSEG-MATNR) were defined directly in the text as &MSEG-MATNR&.. Note 442706 change the behavior according to the dialogue transaction MB01. Can also be set by customer in condition record. Output Determination in Inventory Management (MM-IM) 27 .1 in note 32244. Output Determination in Inventory Management (MM-IM) 28 .11.SAP Online Help 20.01 Printer determination See IMG and check list 2 from note 426554. 5) In the update task the output records from internal table XNAST are written in DB table NAST.SAP Online Help 20.g.0 on) Technical process when working with the output maintenance full screen: Output Determination in Inventory Management (MM-IM) 29 . Table NAST is linked to table MSEG through the object key. it might be necessary to enter the output type manually during creation (MB01) or change (MB02) of material document. which itself sets a CALL FUNCTION IN UPDATE TASK. The user does not bother to see which output types will be found. First it replaces the mail variables in dialog with function module RV_MESSAGES_MAIL_REPLACE. print indicator of movement type T156-KZDRU. plant. 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). 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. 4) In BUCHEN_AUSFUEHREN function module MB_MESSAGE_UPDATE is called in dialog. • POSIDIALOGSTRUKTUR_FUELLEN: Item data from MSEG (e. WA01. Manual output records If customizing is not set correctly. Both communication structures KOMKBME and KOMPBME will be transmitted to the output determination and are used for reading the condition tables. Then it sets a PERFORM ON COMMIT. WE03.01 Program Logic for Developers Output records for a material document (table NAST) The output records are stored in table NAST.11. 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. WE02. The output types that have been found relevant are stored in internal table XNAST. MLFH Automatic output records Usually output records are generated in the background during a goods movement. Menue: Detail > More functions > Messages/Output (also available as pushbutton from 4. • MESSAGING: here the actual output determination is processed. if customizing is set correctly. 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: KSCHL Output type - MBLNR Material document number - MJAHR Material document year - ZEILE Material document item Examples: WE01. storage location) are given to communication structure KOMPBME. MLGR. This is necessary to ensure that data such as batch classification data or QM inspection lot are available for printing. Version WEVER) are given to the communication structure KOMKBME. In MB02 function module MB_MESSAGE_UPDATE is called directly after the output maintenance.01 If the users calls the full screen of output maintenance before posting. In material document display it is possible to start the automatic output determination with a checkbox ‘Print’ in the header general data. the output determination will not be processed in BUCHEN_NUMMERNVERGABE.6B and 4. MIGO In Release 4. Deleting output records Output records are linked to the material document through the object key and are therefore deleted during the archiving of the material documents. It was a bug in 3. Output Determination in Inventory Management (MM-IM) 30 .6C we do not have the output maintenance screen. so it was not possible to have the output maintenance screen as an item tabstrip). 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.0 for label print (bug fixed). When working with the output maintenance screen. There is no real justification for having to maintain manual output types. It will already be processed before sending the full screen. That way. Therefore it is not possible to enter manual output types.11. 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 maintenance screen or posting the material document without having a look at the output types as the data is processed at different times. some application data might not be available. 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 set correctly. It is also possible to get to the output full screen in display mode (pushbutton in item tabstrip.SAP Online Help 20. The output determination program does not support the subscreen technique yet. 11.SAP Online Help 20.01 Output determination processing: Graphical overview SAPMM07M KOMKBME/KOMPBME SAPLV61B NAST Processing time: ‚4‘ ‚2‘ ‚3‘ Update Task SAPMM07M (RV_MESSAGES_ UPDATE) MB90 RSNAST00 Print program: SAPM07DR SPOOL GR/GI slip Output Determination in Inventory Management (MM-IM) 31 . 01 Terminology English . B072) GR/GI slip Warenbegleitschein. Druckversion (T158-WEVER) Print indicator (for movement type) Druckkennzeichen (T156-KZDRU) Indicator ‘Print via output control’ (on initial screen) Kennzeichen ‘Drucken’ (RM07M-XNAPR) Partner function Partnerrolle Requirement Bedingung (transaction VOFM) Schema (message schema) Schema (ME0001) Output Determination in Inventory Management (MM-IM) 32 .SAP Online Help 20.German English German Access sequence Zugriffsfolge Condition record Konditionssatz (in condition table and table NACH) Condition table Konditionstabelle (e.11. 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.g.
Copyright © 2024 DOKUMEN.SITE Inc.