Output Determination in Inventory Management (IM) Content •
Content
•
1. About this document
•
2. Genera in!ormation
•
". Output records !or a materia document (tabe #A$%)
•
&. 'rint version !or transaction (%1*+,-,)
•
. /ied 0'rint0 (MM*3#A')
•
4. 'rint indicator !or movement type (%14*56D7)
•
. Output type (+,18 M9/:...)
•
. Message schema (M,1)
•
;. Condition tabe
•
1. Condition records
•
11. Access se
•
12. 9ayout sets ($A'$cript)
•
1". Coective sips
•
1&. e
•
1. #umber o! G=GI sips (M$,G*+,A#6)
•
14. 9abes
•
1. 'artner !unctions
•
1. Missing part mais
•
1;. Mai te>t
•
2. G=GI sips !or stoc? trans!ers
•
21. Mutipe accounting sheet
•
22. 9anguage
•
2". 'rinter determination
•
2&. %roube*$hooting guide !or non*deveopers
•
2. %roube*$hooting guide @ith debugging
•
24. %erminoogy
•
2. $A' #otes
1. About this document %his document describes the output determination in Inventory Management. •
Chapter " deas @ith the program ogic and is intended to deveopers.
•
Chapters & to 2" describe the singe eements o! output determination. $ome are purey MM*IM8 others are genera output determination concepts. %he chapters may be used as re!erence @hen deaing @ith a specia part o! the output determination. %hey contain genera e>panations as @e as technica descriptions. Chapters 2&=2 concentrate on troubleshooting. %he !irst part gives a ist o! important brea?points and chec?s. %he
•
second part is organied in the maBor symptoms that arise @hen deaing @ith issues about output determination in MM*IM area. Chapter 24 contains a ist o! a output determination terms in German and ,ngish.
•
2. Genera in!ormation %he output determination (aso caed message contro) generates output records (messages) !or a materia document. %he messages can be G=GI sips (e.g. output type +,1)8 mais (output type M9/: !or missing part mais) or even @or?!o@ events (not in standard but can be customied by customer). %he output determination program is a centra !unctionaity outside MM*IM. It is aso used by MM*'78 $D etc. C$$ component !or the centra program (i! bug is not due to caing appication i?e MM*IM) CA-GTF-BS-MC 'rincipe %he appication using the output determination provides the output determination program @ith appication data (i?e pant8 storage ocation) through communication structures (MM*IM communication structures 5OM5M, !or header data and
5OM'M, !or item data). %he output determination program uses these appication data to determine * @ith the hep o! e>tremey !e>ibe and compe> tabes * @hether an output type is reevant or not. I! an output type can be !ound !or the given criteria (appication data)8 an output record @i be generated. /or more in!ormation about Customiing o! Output determination see IMG.
". Output records !or a materia document (tabe #A$%) %he output records are stored in tabe #A$%. %abe 5ey Field name
Field description
Field value used in MM-IM
KAPPL
Application
'ME' (Constant for MM-IM)
OBJKY
Object e!
Is co"pose# of$ - MBL%& Material #oc"ent n"ber - MJA& Material #oc"ent !ear - EILE Material #oc"ent ite"
K*CL
Otpt t!pe
E+a"ples$ ,E./ ,E0/ ,E1/ ,A./ ML2&/ ML3
Automatic output records 7suay output records are generated in the bac?ground during a goods movement8 i! customiing is set correcty. %he user does not bother to see @hich output types @i be !ound. %echnica process (ony !or AA' deveopers) In $A'MMM the !oo@ing routines are proc essed 1.
In /orm*outine DRC!"#R$F$% &MM'(MFD') !ied M!#F-*$+$R is set depending on the print !ied (MM*3#A') and the de!aut print version (%1*+,-,) or the print version chosen on the initia screen.
2.
%he print indicat or o! the m ov em ent t ype is read !rom t abe %14 &T,.-!/DR)
".
In BC0$%"%MM$R%+$RGAB$ a !e@ routines are processed
•
!1#FDIA21GSTR!TR"F$22$%3 :eader data !rom M5'/ (i?e transaction type -GA%8 -ersion
+,-,) are given to the communication structure 5OM5M,. •
#1SIDIA21GSTR!TR"F$22$%3 Item data !rom M$,G (e.g. print indicator o! movement type
%14*56D78 pant8 storage ocation) are given to communication structure 5OM'M,. oth communication structures 5OM5M, and 5OM'M, @i be transmitted to the output determination and are used !or reading the condition tabes. •
M$SSAGI%G3 here the actua output determination is processed. %he output types that have been !ound
reevant are stored in interna tabe 3#A$%. &.
In BC0$%"ASF$0R$% !unction modue MB"M$SSAG$"#DAT$ is caed in diaog. /irst it repaces the mai variabes in diaog @ith !unction modueR+"M$SSAG$S"MAI2"R$#2AC$. %his is necessary !or goods movements posted @ith MB"CR$AT$"G11DS"M1+$M$%T because MB"#1ST"D1CM$%T resets a interna tabes (MB"M1+$M$%TS"R$FR$S0 is caed) and @e need the interna tabes to !i the mai variabes (notes 2;1 E 21"24&).
%hen it sets a #$RF1RM 1% C1MMIT8 @hich itse! sets aCA22 F%CTI1% I% #DAT$ TAS! . %his is necessary to ensure that data such as batch cassi!ication data or FM inspection ot are avaiabe !or printing. .
In the update tas? the output records !rom interna tabe 3#A$% are @ritten in D tabe #A$%. %abe #A$% is in?ed to tabe M$,G through the obBect ?ey. Manua output records I! customiing is not set correcty8 it might be necessary to enter the output type manuay during creation (M1) or change (M2) o! materia document. Menue Detail 4 More 5unctions 4 Messages61utput (aso avaiabe as pushbutton !rom &. on) Technical process 7hen 7or8ing 7ith the output maintenance 5ull screen3
I! the users cas the !u screen o! output maintenance be!ore posting8 the output determination @i not be processed in BC0$%"%MM$R%+$RGAB$9 It @i aready be processed be!ore sending the !u screen. %hat @ay8 it is possibe to dispay the output types that have been !ound automaticay. %AC0RIC0T$%"#F2$G$ &MM'(MFM') %AC0RIC0T"$R/$G
%$•
•
!1#FDIA21GSTR!TR"F$22$% &M!#F -4 !1M!BM$)
•
#1SIDIA21GSTR!TR"F$22$% &MS$G -4 !1M#BM$)
•
M$SSAGI%G (output determination) R+"M$SSAG$S"MAI%T$%A%C$3 sends the output maintenance !u screen (not MM*IM)
•
In M1 a output records @i be renumbered in BC0$%"%MM$R%+$RGAB$ and given to the update tas? in BC0$%"ASF$0R$% through !unction modue MB"M$SSAG$"#DAT$. In M2 !unction modue MB"M$SSAG$"#DAT$ is caed directy a!ter the output maintenance. ou can recognie manua output records in tabe #A$% @ith !ied %AST-MA%$ (chec? @ith $,14) MIG1
In eease &.4 and &.4C @e do not have the output maintenance screen. %here!ore it is not possibe to enter manua output types. In materia document dispay it is possibe to start the automatic output determination @ith a chec?bo> 0'rint0 in the header genera data. It is aso possibe to get to the output !u screen in dispay mode. *h: is it not possible to maintain output t:pes manuall: in MIG1;
+e assume that a user ony has to maintain manua output types because the customiing is not set correcty. %here is no rea Busti!ication !or having to maintain manua output types. Deeting output records Output records are in?ed to the materia document through the obBect ?ey and are there!ore deeted during the archiving o! the materia documents. Output determination processing overvie@
&. 'rint version !or transaction (%1*+,-,) adio buttons on initia screen o! M1
%here are " print versions (0108 0208 0"0). %he description o! the print versions (individua sip8 coective sip) is ony correct i! the customiing is set as $A' recommends. I! the customer creates a condition record !or an individua sip @ith the version " (coective sip)8 he @i get an individua sip @hen the users chooses radio button 0coective sip0. De!aut*-ersion &T,<-*$+$R)3 determines @hich print version is set on initia screen o! transaction. I! !ied 0'rint0 is not set8 the version @i be ceared. %hat @ay the system @i not !ind any condition record and @i not print any sip. MB"CR$AT$"G11DS"M1+$M$%T
ecause MHC,A%, @or?s @ithout initia screen8 @e a@ays use de!aut version !or transaction !rom %1. I! printing @ith MHC,A%, does not @or?8 chec? that the IM5'/ transaction has a print version in %1. In case o! goods receipt !or purchase orders @ith mutipe account assignments8 the de!aut version o! %1 in ony used i! 010 or 020. In case o! coective sips8 the version is changed to 010 a!ter appication o! note &&24 in order to be consistent @ith the diaogue (transaction M1). MIG1
In transaction MIGO the print version is avaiabe since note "1&"&.
. /ied 0'rint0 (MM*3#A') Chec? bo> on initia screen and header data screen o! M1. Is set !rom user parameter #D 3. 3 has to be @ritten in capita etters8 other@ise basis error 2 0pease enter vaid vaue0 on initia screen. +ith this !ied it is possibe to deactivate the printing o! G=GI sips (but not to deactivate mais) %echnicay the !ied is used in /orm routine DRC!"#R$F$% &MM'(MFD') to reset the print version &M!#F*$+$R)9 %hat @ay a output types @or?ing @ith the print version are deactivated. Caution3 deactivation o5 output determination not possible =
+ith the !ied 0'rint0 it is not possibe to deactiv ate the output determination competey. %he output determination is a@ays processed8 even i! !ied 0'rint0 is not set8 because it sti might be necessary to generate some mais. %he output determination can ony be deactivated t hrough coding modi!ication. Caution3 5ield >#rint> onl: 7or8s 5o r condition tables 7ith version =
I! the customer uses o@n condition tabes @ithout the version8 the !ied 0'rint0 @i have no e!!ect. %he system @i !ind a condition record and @i print a sip. ,>pained in note 2&. Setting o5 5ield >#rint> and user name in MB" CR$AT$"G11DS"M1+$M$%T
ecause MHC,A%,HGOOD$HMO-,M,#% @or?s @ithout initia screen8 !ied 0'rint0 is set e>cusiv ey !rom the parameter ID #D o! a user record. It is possibe to give MHC,A%,HGOOD$HMO-,M,#% a user name !or print in !ied IM!#F#R"S%AM (i! initia8 the system @or?s @ith IM!#F-S%AM9 I! IM!#F-S%AM is initia8 the system @or?s @ith $*
7#AM,). %he vaue o! parameter #D is read directy !rom the user data (tabe 7$) and not through G$T #ARAM$T$R %DR 8 because the user might @or? paraey @ith M11 and there change the parameter #D !rom !ied
MM*3#A'. I! printing @ith MHC,A%,HGOOD$HMO-,M,#% does not @or?8 chec? the user has parameter #D 3. $eecting or deseecting #D does not react i?e a seection O#=O// in a transaction i! you use a A'I. %he parameter and the A'I are in t@o di!!erent memories. %he A'I cannot then recognie that the parameter has been deseected. MIG1
%he !ied sti e>ists as header data (!ied G10$AD-?%A#R on header tabstrip 0Genera0).
4. 'rint indicator !or movement type (%14*56D7) ecause most movement types do not need a speci!ic G=GI sip8 @e do not use the movement type directy in the condition tabes. Instead @e use the print indicator !rom tabe %14. •
Most movement types have print indicator 010 (norma G=GI sip).
•
Mvt 122 has print indicator 020 to distinguish a return deivery sip !rom a G sip.
•
Mvt &1 has print indicator 0"0 because it needs a specia condition tabe @ith debit=credit indicator ($:56G) so that ony one ine is printed and not the automatic ine.
•
Mvt 1 has print indicator 040 (&.) because it is possibe to create 1M ines in M1. M1 prints normay a G sip @ith 'O data (mvt 11 uses output type +,1)8 but mvt 1 needs a G sip @ithout 'O data (output type +A1). As both mvt types use the same condition tabe8 it @as necessary t o distinguish them @ith the print indicator.
. Output type (+,18 M9/:...) %he output type determines @hat ?ind o! output (sip8 mai8 @or?!o@ event) is generated. Output types !or G=GI sips are directy in?ed to a $A'$cript ayout set and to a read routine in tabe %#A'. Individua sips and coective sips have di!!erent output types because they use di!!erent ayout sets and have di!!erent read routines. /urthermore the output type has a printer parameter (8 ;8 78 3) that is used !or the printer determination. /or more in!ormation see IMG. Common errors •
Customer has assigned the @rong program to an output type in tabe %#A'. /or e>ampe he @ants to have 'O data on the sip but uses the routine !or other goods receipt
•
Customer has entered an o@n read program in %#A' that does not @or?. A@ays chec? tabe %#A' @hen anaysing an output type issue.
. Message schema (M,1) A schema gathers a output types that have to be chec?ed by the output determination. In Inventory Management @e use ony one schema >M$''',>. %he schema is a program constant and cannot be changed by the customer. %he customer can add his o@n output types to our standard schema. %he output determination program oops over a output types that are de!ined in the schema and tries to !ind a condition record !or that output type in the corresponding condition tabe. In the schema it is possibe to de!ine a reampe8 coective sips need re
;. Condition tabe A condition tabe contains the criteria that are reevant !or an output type. Our norma condition tabe is 2 !or norma G=GI sips (can be dispayed @ith $,14). %abe ?ey •
5A''9 Appication (a@ays 0M,0)
•
-GA% %ransaction type (+,8 +A8 +) !rom %1. #ever use +O because @e do not print sips !or M&. %he transaction type cannot be changed by the customer.
•
+,-, 'rint version !rom %1 (1 and 2 !or individua sip8 " !or coective sip)
•
56D7 'rint indicator !or movement type (18 28 "8 4) Mais and mvt &1 have their o@n condition tabes. Customer may create an o@n condition tabe but $A' doesn0t recommend it. %e7 5ield in 5ield catalog
A customer may create a condition tabe @ith a !ieds that are contained in our !ied cataog. %he !ied cataog is de!ines in tabe 5OM5 and is !itered ! or each appication in tabe %41/. It is !ied by our communication structures 5OM5M, and 5OM'M,. Customer may add and !i ne@ !ieds as @e have user*e>its !or a communication structures8 but they have to add the !ieds to t he appication !ied cataog (tabe %41/8 can be maintained @ith transaction #AC,)
1. Condition records Condition records are entries in c ondition tabes. ,>ampe tabe 2 (appication a@ays 0M,0) +GART
*$+$R
!/DR
1utput t:pe
,E
.
.
,E. (se# for .. in#i4i#al slip)
,A
.
.
,A. (se# for 0. in#i4i#al slip)
,A
1
.
,A1 (se# for 0. collecti4e slip)
In IMG you can !ind a ist o! condition records that have to be created by the customer i! he @ants to use the standard settings. Common error Create a condition record @ith transaction type +A and output type +,J. %hat @ay he gets a G sip @it h empty 'O data. A@ays chec? in the condition tabe 2 (@ith $,14) i! the condition records have been created as described in IMG and i! customer output types are used. It gives you a hint i! customer has understood the output determination and uses o@n output types. ou can aso chec? @hich output types he uses as a ot o! customers ony create condition records !or the output types they use. %o transportation o5 output records3
Output records are master data @ith automatic numbering. +hen you create a condition record in Customiing (transaction M#21)8 the system c reates an entry in tabe 2 @ith a condition number (e.g. &11). %he condition number re!ers to the
master data in tabe #AC: (@ith ?ey &11). It is not possibe to transport the condition records because t he record &11 might aready e>ist in the target system and re!er to another condition tabe than 2. I! you have transported a condition record manuay (transport o! 2 entry or #AC: entry)8 you have an inconsistency in tabe #AC: @hich can cause M#21 to abort. %he transported entries need to be deeted @ith a correction program and re*created manuay @ith M#21. %his is not a hotine probem as this is a @rong customer transport.
11. Access se
12. 9ayout sets ($A'$cript) ou can !ind the ayout set used !or an output type in tabe %#A'. Our st andard ayout sets begin @ith + ,$C:,I#J8 +A$C:,I#J. +e recommend the customer to copy our standard ayout set (6...) i! he needs additiona !ieds. Our read routines in tabe %#A' !i a M5'/8 M$,G and 'O data !ieds. %he customer does not need an o@n read program i! he uses !ieds !rom these tabes. I! he needs o@n !orm routines (e.g. to read the batch cassi!ication data)8 he can impement an e>it*routine directy in the ayout set (using = ',/OM as $A'script command). %ransaction $,18 ayout set e.g. +,$C:,I#-,$1 !or output type +,1 Connection bet7een te@t element o5 la:out set and print program
A ayout set has @indo@s (e.g. MAI#) and a @indo@ has te>t eements (e.g. +19GMA%8 +1-,MA%). A te>t eement represent a !e@ ines that @i be printed together (e.g. + 19GMA% !or item in!ormation in c ase o! 'O @ithout account assignment8 +1-,MA% !or item in!ormation in case o! 'O @ith account assignment). %he print programs (e.g. $A'MD8 !orm ,#%H+,1) cas the !oo@ing !unction modues to @or? @ith the ayout set •
1#$%"F1RM3 to open the ayout set and give the printer data
•
START"F1RM3 to give the anguage
•
*RIT$"F1RM (e.g. ,3'O%I#G ,9,M,#% 0+19GMA%0 to print a particuar te>t eement.
•
C1%TR12"F1RM3 e.g. to start a ne@ page8 a ne@ @indo@
•
C21S$"F1RM to cose the ayout set and be abe to open a ne@ one. %@o O',#H/OMs @ithout a
C9O$,H/OM update t ermination in -HM,$$AG,$H7'DA%,. ecause the te>t eements are caed by the program (in ca !untion +I%,H/OM e>porting eement ...) the customer may copy a ayout set but sti has to ma?e sure that the te>t eements caed by program sti e>ist in his ayout set. +hen a te>t eement is caed8 a !ieds to be printed shoud have aready been read by the program. As @e read a data (i?e M5'/8 M$,G8 ,5'O) be!ore caing te>t eements in standard8 there is practicay no ris? that a !ied is empty @hen the
te>t eement is being processed. As @e !i the compete @or? area !or M$,G8 ,5'O etc. the customer may add any !ied !rom these tabes in a te>t eement. Ony te>t eement !or the @indo@ 5O'/ (header data) have a deayed process (not during +I%,H/OM but a!ter the @hoe page has been processed. /or that reason8 it @as necessary to store the @or? area in 0od0 !ieds in the routines :,9'DA%A1 and :,9'DA%A2 in $A'MD. /or the customer it means that you cannot add an M$,G !ied in t he @indo@ 5O'/ because you @i a@ays get the data !rom the ne>t item and not !rom the current item.
1". Coective sips +e have " coective sips +,"8 +A"8 +9" (used !or &1). A coective sip contains a items o! a materia document. It @oud be ogica to have a coective sip at materia document eve but @e do ony output determination at item eve. %hat is @hy @e create a coective sip !or item 1. Common customer errors Collective slip printed 5or all items3
A coective sip is printed !or a items. $oution customer has deeted the re
In a coective sip it is not possibe to add an M$,G !ied to the header data because you @i a@ays have the data o! the ast item. ou can ony add an item !ied in the te>t eement processing the item data.
1&. eampe8 coective sips need re
I! an output type has a reecution o! a re
1. #umber o! G=GI sips (M$,G*+,A#6)
7sed ony !or individua sips because it depends on materia. Output types +,18 +,28 +/18 +/2. %he idea is to print a number o! sips that corresponds to number o! paets deivered. I! a materia a@ays has a !i>ed
In the print program there are ony t@o ?ind o! output types @or?ing @ith !ied +,A#6 Individua G sips +,1 and + ,2 in !orm ,#%H+,1 and ,#%H+,2 @e per!orm t he sip printing as
•
many times as indicated in +,A#6. %he !ied is not active in a coective sip as it is an item in!ormation. I! item 1 says 1 sips and item 2 says & sips8 ho@ many coective sips shoud @e print It does not ma?e sense in a coective sip. 9abes !ied M$,G*+,A#6 can be used !or the determination o! the number o! copies (tabe %1;, see beo@)
•
!or a goods movements in MIGO since note """4. In M>> transactions8 it @or?s ony !or goods receipts as +,A#6 is not !ied !or goods issues.
14. 9abes %here is an o@n customiing step !or setting abe printout. %he idea is that you have a ayout set @ith te>t eement ,%I5,%%. %he system determines the number o! abes to be printed !rom the item t eements (caed by +I%,H/OM). In each te>t eement you have the same te>t. %hat is @hy the te>t !or the abe printout is not de!ined in the ayout set but in a separate te>t. /urthermore you can maintain a abe type and a abe !orm in the materia master. oth !ieds are used in the condition tabes !or ayout set. Appication obBect (de!ined in tabe %%3O8 standard MM'($T) here you can !ind the te>t ID (tabe %%3ID
•
standard ('',) te>t name and ayout set (standard RM'($TI!$TT). A data are maintained in tabe T,1. +e recommend to ?eep the standard obBect8 te>t id and te>t name. •
9abe te>t report RM'(M$TI to maintain the abe te>t (used !or a te>t eements o! the ayout set)
•
9abe types and !orms (used in condition tabes !or abes)
•
%umber o5 copies here you can de!ine @hich
cacuate the number o! copies (tabe T,$). A customer @anted to use !ied -MM*A#6G, (number o! containers in FM)8 but not possibe because it is not an M$,G !ied and the program $A'MD can ony @or? @ith D !ieds. A modi!ication @as proposed in MD,%I8 !orm ,%IHD7C5 (read A#6G, !rom tabe FA9$ to set !ied A#6A:91. Another customer @anted to use !ied M$,G*+,A#6 but it does not @or? in case o! GI (or reversa GIs) in M>> transactions8 see chapter +,A#6 above. In MIGO it shoud @or? !or a goods movements since note """4 as @e a@ays cacuate +,A#6. 2abels and collective slips &output t:pe *$$E)3
%here is no such thing as a coective abe. I! you use print version " and you have created the condition records as recommended in Customiing8 you @i get one output record !or + ," !or the !irst item and one +,," !or each item. ou
@i thus have one coective sip @ith a items and individua abes !or each item. %he content o! +,,18 +,,2 and +,," is e>acty the same8 they a use !orm routine ,%IHD7C5. I! you enter rets8 use report $%3"%. Form routines in $A'MD $TI"DRC! (incude MD,%I) here the number o! copies is cacuated !rom %1;O and the te>t is read in
per!orm $TI!$TT$%T$?T"2$S$%. %he te>t eement ,%I5,%% is caed (ca !unction>*RIT$"F1RM> e@porting element >$TI!$TT>) in !orms *RIT$"2I%$S and *RIT$"2AST..
1. 'artner !unctions +e ony use t@o partner !unctions !or mais in MM*IM. +e do not use any partner !unctions !or sips. %he partner !unctions are set by the program in MM'(MF%' #1SIDIA21GSTR!TR"F$22$%8 ca !unction !1M#BM$"F$22$%. +e use the technica partner !unctions M' !or M9G and D' !or M9/:. 'artner !unction is anguage*dependentN In tabe T#AM you can !ind the transation o! the partner !unction in di!!erent anguages.
1. Missing part mais A ot o! customers have probem customiing the missing part mais because they not ony have to customie the output determination but aso the missing part chec? itse!. /or detaied in!ormation see IMG o! missing parts and output determination %he missing part mai is a ?ind o! avaiabiity chec?. +e chec? during a goods receipt i! the materia is missing !or some M' re
I! you get to the brea?point but the !unction modue does not e>port an interna tabe @ith the ist o! M' re
•
I! you get a ist o! M' re
1;. Mai te>t ou can !ind e>ampes o! mai te>ts in IMG. Common errors Mail variables not replaced in mail3
In the od $A'$pript editor ($,1)8 t he te>t variabes (e.g. M$,G*MA%#) @ere de!ined directy in t he te>t as M$,G* MA%#. In the ne@ editor you cannot enter t he te>t variabe directy in the editor8 youneed to add the te>t variabes t hrough
the menue..Ma?e sure the !ieds you add to the ayout set are de!ined as a variabe and not as te>t in the ayout set. In transaction $,1 it shoud bin? @hen you cic? on it. $ee aso notes 2;1 and 21"24& (bug in MHM,$$AG,H7'DA%,) Te@t changes do not appear in mail3
e!ore &.4 a mai te>ts @ere de!ined at output type eve. $ince &.4 it is possibe to de!ine a mai te>t at output type eve and at condition record eve. +hen you create a condition8 the mai te>t !rom the output type is internay copied to the output record. $o i! you change the mai te>t at output type eve8 you need to deete the condition record and recreate it in order to get the te>t changes to the condition record.
2. G=GI sips !or stoc? trans!ers 7suay the customer @ants to have ony one GI sip !or stoc? trans!ers (on the suppying side ony)8 but i! he uses individua sips (+A18 +A2)8 he @i get automaticay t@o. In order to get ony one8 he has to ma?e the sips dependent !rom the debit=credit indicator. %his is e>pained in consuting note 42. In the customer uses a coective sip8 he @i get ony the items !or the suppying side8 because @e ma?e a chec? in the program that the item has not been created automaticay (M$,G*3A7%O in !orm 9,$,#H+A$).
21. Mutipe accounting sheet I! the 'O has mutipe accounting8 @e print automaticay an accounting sheet together @ith the individua sip. %he accounting sheet is printed on a separate ayout set MHM/5%O and contains the detai o! the accounting. •
Fuantities on the accounting sheet the
•
Coective sip not possibe @ith mutipe accounting8 @e s@itch automaticay to individua sip (since note 1";)
•
9ayout set MHM/5%O customiabe since &. ony. Customiing is possibe via an entry in tabe %1;# !or program MD5%O.
22. 9anguage :as to be set @hen caing START"F1RM8 other@ise termination R+"M$SSAG$"#DAT$. Can be set dynamicay by program $A'MD !rom %1+ anguage. Can aso be set by customer in condition record.
2". 'rinter determination $ee IMG and chec? ist 2 !rom note &24&.
2&. %roube*$hooting guide !or non*deveopers
ear in mind that the maBority o! printing probems are attributabe to incorrect Customiing or to the use o! user*de!ined deveopments. 'robems @hich arise as a resut cannot be deat @ith by $upport. I! you re
note &24& chec? ists !or output determination and printer determination !or goods movements
•
note &244& chec? ist !or missing part mais
2. %roube*$hooting guide @ith debugging 7se this troubeshooting guide ony i! your are !amiiar @ith AA' programming and debugging. Important chec8s3
•
Do :ou use o7n condition tables; Chec? 1) Customiing MM*IM LOutput Determination L Output types note access
se>. I! a customer uses o@n condition tabes and the system cannot !ind any output record or !inds too many o! them8 this is a consuting probem. •
Do :ou use o7n print program; Chec? in Customiing MM*IM L Output Determination L Assign !orms and
programs (or $,14 tabe %#A'). outines i?e ,#%H6,1 or program 6MMD are not s tandard. It might e>pain that a #A$% record @i not be printed or has @rong data. Important programs3 •
SA#2+.,B3 output determination program
•
SA#M'(DR3 print program (reads a data per $,9,C% on database and cas $A'$cript ayout set.
Important Form-Routines 5or brea8points3
•
MM'(MFD' DRC!"#R$F$%3
the version &M!#F-*$+$R) is set depending on !ied RM'(M-?%A#R and de!aut version in %1. /ied MM*3#A' itse! is set on !irst screen (diaog) or !rom parameter #D (MHC,A%,). •
MM'(MF%' !1#FDIA21GSTR!TR"F$22$% and #1SIDIA21GSTR!TR"F$22
%$communication structures 5OM5M, and 5OM'M, are given to the output determination inter!ace. %here you can chec? the version (M5'/*+,-,)8 the print indicator (%14*56D7) and the transaction t ype (M5'/*-GA%) •
MB"CR$AT$"G11DS"M1+$M$%T3
the user given in IM5'/*'H7#AM, or IM5'/*7$#AM is used !or reading parameter #D in DRC!"#R$F$% and is used !or the printer determination in 9-41/'8#RI%T$R"#ARAM$T$R"2$S$% •
2+.,BF'% %AC0RIC0T$%STATS"SC0R$IB
%$the output determination program oops over a output types and tries to !ind a condition record. I! a condition record is !ound (IF ?!%M0 %$ S#AC$)8 an entry is added to interna tabe 3#A$%.
2+.,BF'# #RI%T$R"#ARAM$T$R"2$S
%$•
%he printer is !ound in tabes %#AD and %#AD; (CAS$ I%D$?9 *0$% >(>9 *0$% >>)9 MM'(MFB BC0$%"ASF$0R$% CA22 F%CTI1% R+"M$SSAG$S"G$T
•
can be used to chec? the interna tabe 3#A$% Bust be!ore posting (be!ore commit @or?) SA#M'(DR Form $%TR"999
•
the data is read !rom the database (using $,9,C% J) by the print program. %he print routine aso cas the ayout set and the te>t eements that have to be printed. MM'(MFT' !or mais ony
•
reads the data and !is mai te>t. $et parameter !or mai processing (ca transaction) Tips3
•
,ven i! an output record !rom #A$% has been printed immediatey in the update tas?8 it is possibe to repeat the output @ith M; and debug the print program in diaog.
•
It is not possibe to debug the print program $A'MD during the posting o! a materia document as it is processed in the update tas?. I! an update termination -HM,$$AG,H7'DA%, occurs during the creation o! a materia document8 change the processing time & (immediatey) to ". %hat @ay the materia document @i be posted @ithout update termination and you @i be abe to debug $A'MD in diaog using M;. 9ist o! symptoms *!"pto" .
%o otpt recor# create# for "aterial #oc"ent
*!"pto" 0
2&52I slip is printe# on 6ron7 printer
*!"pto" 1
8p#ate ter"ination in &9:ME**A2E:8P;A
*!"pto" =
,ron7 #ata is printe# on 2&52I slip
*!"pto" >
%o "ail ML3
*!"pto" ?
Mail ML3 is sent 6it@ot te+t or to 6ron7 recipient or cannot be processe# 6it@ CO?
*!"pto"
2&52I slip is printe# alt@o7@ fiel# 'Print' is not set (note 0>=>)
S:mptom ,3 nothing gets
printed
S:mptom 3 *rong
printer
S:mptom E3 pdate termination R+"M$SSAG$"#DAT$9
Can happen i! O',#H/OM @ithout C9O$,H/OM or i! anguage is not set.
S:mptom 3 *rong data printed on GR6GI slip
S:mptom 3 %o mail M2F0
S:mptom .3 Mail M2F0 is sent 7ithout te@t or to 7rong partner or cannot be processed 7ith C1'.s
S:mptom (3 GR6GI slip is printed although 5ield >#rint> is not set ¬e '')
Can happen i! customer uses o@n condition tabes @ithout print version.
24. %erminoogy
2. $A' #otes 1;"2 'artner !unc !or vendor=cust. in inventory mangment 2"24 /ied 0Created by0 (,#AM) is not !ied 2& G=issue sip athough indicator 0'rint0 not set "1 Document type MMID,9#%O cannot be customied &244& Missing part mai chec?ist !or goods movements &24& Output determination chec?ist !or goods movements
22;1 /AF IM output determination &111" Additiona documentation on output determination in MM*IM
