- #Sap movement type and transaction key relationship update#
- #Sap movement type and transaction key relationship full#
POSIDIALOGSTRUKTUR_FUELLEN (MSEG -> KOMPBME).KOPFDIALOGSTRUKTUR_FUELLEN (MKPF -> KOMKBME).That way, it is possible to display the output types that have been found automatically.
#Sap movement type and transaction key relationship full#
It will already be processed before sending the full screen. If the users calls the full screen of output maintenance before posting, the output determination will not be processed in BUCHEN_NUMMERNVERGABE. Technical process when working with the output maintenance full screen: Menue: Detail > More functions > Messages/Output (also available as pushbutton from 4.0 on) Manual output records If customizing is not set correctly, it might be necessary to enter the output type manually during creation (MB01) or change (MB02) of material document. Table NAST is linked to table MSEG through the object key.
#Sap movement type and transaction key relationship update#
In the update task the output records from internal table XNAST are written in DB table NAST.This is necessary to ensure that data such as batch classification data or QM inspection lot are available for printing. Then it sets a PERFORM ON COMMIT, which itself sets a CALL FUNCTION IN UPDATE TASK. 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). First it replaces the mail variables in dialog with function module RV_MESSAGES_MAIL_REPLACE. In BUCHEN_AUSFUEHREN function module MB_MESSAGE_UPDATE is called in dialog.The output types that have been found relevant are stored in internal table XNAST. MESSAGING: here the actual output determination is processed.Both communication structures KOMKBME and KOMPBME will be transmitted to the output determination and are used for reading the condition tables. print indicator of movement type T156-KZDRU, plant, storage location) are given to communication structure KOMPBME. POSIDIALOGSTRUKTUR_FUELLEN: Item data from MSEG (e.g.KOPFDIALOGSTRUKTUR_FUELLEN: Header data from MKPF (like transaction type VGART, Version WEVER) are given to the communication structure KOMKBME.In BUCHEN_NUMMERNVERGABE a few routines are processed:.The print indicator of the movement type is read from table T156 (T156-KZDRU).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.Technical process (only for ABAP developers): In SAPMM07M the following routines are processed: The user does not bother to see which output types will be found. Table Key:Įxamples: WE01, WE02, WE03, WA01, MLGR, MLFHĪutomatic output records Usually output records are generated in the background during a goods movement, if customizing is set correctly. The output records are stored in table NAST. Output records for a material document (table NAST) If an output type can be found for the given criteria (application data), an output record will be generated.įor more information about Customizing of Output determination see IMG. 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. Principle: The application using the output determination provides the output determination program with application data (like plant, storage location) through communication structures (MM-IM: communication structures KOMKBME for header data and KOMPBME for item data). CSS component for the central program (if bug is not due to calling application like MM-IM): CA-GTF-BS-MC The output determination program is a central functionality outside MM-IM. output type WE01), mails (output type MLFH for missing part mails) or even workflow events (not in standard but can be customized by customer). The output determination (also called message control) generates output records (messages) for a material document. Chapter 26 contains a list of all output determination terms in German and English.The second part is organized in the major symptoms that arise when dealing with issues about output determination in MM-IM area. The first part gives a list of important breakpoints and checks. Chapters 24/25 concentrate on troubleshooting.They contain general explanations as well as technical descriptions. The chapters may be used as reference when dealing with a special part of the output determination. Some are purely MM-IM, others are general output determination concepts. Chapters 4 to 23 describe the single elements of output determination.Chapter 3 deals with the program logic and is intended to developers.This document describes the output determination in Inventory Management.
0 kommentar(er)
