PROCESSINGIERRORSFROMTHEINTERFACEWITHTHE

PROCESSINGIDOCERRORSFROMTHEINTERFACEWITHTHEPDMTableofcontents1.Introduction2.HowtohandleCHRMASerrors3.HowtohandleCLSMASerrors4.HowtohandleECMMASerrors5.HowtohandleDOCMASerrors6.HowtohandleBOMDOCerrors7.HowtohandleZPDM_MATMASerrors8.HowtohandleBOMMATerrors9.HowtohandleCLFMASerrors10.HowtohandleECMREVerrors11.SettingthedeletionindicatorforanIDoc12.Serializationerrors1.IntroductionTheERPsystemreceivesonadailybasisIDocsfromthePDMsystem.TheIDocscanbe:IDoctypeDescriptionofIDoctypeCHRMASClasssystem:CharacteristicsmasterCLSMASClasssystem:ClassesmasterECMMASEngineeringChangeManagementDOCMASMasterdocumentBOMDOCBOMs:DocumentstructureZPDM_MATMASReducedMaterialmasterdataBOMMATBOMs:MaterialBOMCLFMASClasssystem:ClassificationmasterECMREVRevisionlevelTheIDocshavetobeprocessedintheabovedescribedorder.ThisprocessingorderissetintransactionBD44:SelectZGRP_PDM01,anddouble-clickonAssignmentoflogicalmessagestoserial.Group=Hereyoucanseethesequencenumbersforeachmessagetype:themessagetypeswithhighestprioritiesshouldbeprocessedfirst:sofirstofallweshouldprocesstheCHRMASIdocs(havingsequencenumber1),afterthentheCLSMASIDocs(havingsequencenumber2),andsoon…RegardingthestatusesoftheIDocs,thestatuseswhichoccurmostoftenareasfollows:51Applicationdocumentnotposted(error)53Applicationdocumentposted(thisshouldbethefinalstatusoftheIDoc,ifeverythingwasprocessedsuccessfully)64IDocreadytobetransferredtoapplication(itmeansthattheIDocwastransferredalreadyfromPDMtotheERPsystem,butitwasn’tprocessedyet);66IDociswaitingforpredecessorIDoc(serialization)–itmeansthatthismessagetypeisserialized,andthisIDociswaitingforthepredecessorIDoc,inordertobeprocessed.68Error-nofurtherprocessing–itmeansthatthisIDocwasdeleted(itappearsintheERPsystem,itdoesn’tdisappear,butithasadeletionflag).69IDocwasedited–itmeansthatthisIDocwaschangedmanually(theinformationcontainedbyoneormoresegmentswaschanged).Itshouldbeprocessedafterthischange,inordertohavestatus53fortheIDoc.ThemonitoringoftheincomingIDocscouldbedonethroughthetransactionBD87:ThefollowingselectionisrecommendedinordertorestricttheoverviewtoonlythoseIDocscomingfromPDMwhichhaveerrorsandcouldn'tbebookedautomaticallyinthesystem:ForIDocStatusvaluerangesfrom50to52andfrom54to70ForMessageTypeBOMMAT,CHRMAS,CLSMAS,ECMMAS,DOCMAS,BOMDOC,ZPDM_MATMAS,CLFMAS,ECMREVThedatesintheChangedOnfieldshavetobemaintainedaccordingtothespecificneeds.Theselectioncanbesavedandusedafterwards:AftertheselectionismadeandtheExecutebuttonispressedascreenwiththeerrorsappear:EveryIDocerrorhasanerrormessage.Somemessagesareself-explanatory,likeYouarenotauthorizedforChangeDocumentwithdocumenttypeQDO.ForthemessageswhicharenotthatcleartheTCSLG1canbeused.Thistransactionshowsacompleteerrorlog,givingtheusertheinformationneededabouttherootcauseoftheerror.IntheTCSLG1enterCAPIinthefieldObject,CAPI_LOGinthefieldSubobjectandtheIDocnumberinthefieldExternalID.EnteringtheIDocnumberwillspeedupthesearchfortheerrorlog.AfterpressingtheExecutebuttontheerrorlogisdisplayed:AlsoyoucancheckthesituationoftheunprocessedIDocs,usingtransaction/casww/bd01:Makethedesiredselection,AndpressthebuttonExecute:HereyoucanseetheIDocs(accordingtoyourselectioncriteria),andalsotheerrormessageforeachIDoc,inthecolumn“Description”.Also,ifyouwant,youcanprocesstheIDocshavingthestatus51or64/66,byselectingtheIDocandpressingthecorrespondingbutton(BookStat51,orBookStat64/66).Anotheroptionis,thatyoucanmakeavariantwhichcanbeusedinabatchjob,inordertobesenttoyouautomaticallybye-mailthelistofunprocessedIDocs,makingthefollowingselection:2.HowtohandleCHRMASerrorsTheerrorswhichoccurmostoftenarepresentedbelow:ItmeansthatthisvalueisusedinsomeCharacteristics,soyoushouldcheckifyoustillneedthisvalue,ornot.Youcandeletethisvaluemanuallyifneeded,usingtransactionCT04:Ifyoudecidetodeletethisvalue,youcanpressthebutton“DeleteValue”andSave:Ifyouchoosetheoption“Donotcheck”,itwillappearthefollowingmessage:Pressthebutton“Continue(Enter)”:Ifyoupressthebutton“Yes”,thenfinallythisvaluewillbedeletedfromthementionedCharacteristic.Soitwillappearthefollowingmessage:.AfterthenyoucanprocessthecorrespondingCHRMASIDoc.ButpleasebecarefultheIDocswithmessagetypeCHRMASarenotserialized!!Itmeans,thatifyouprocessanolderIDoc,andinthemeantimethereweresentother(newer)IDocsfromPDM,regardingtothesameCharacteristic,inthiscasetheinformationcontainedbytheolderIDocwillbeoverwrittenintoyourERPsystem(soitwillnotbeanymorethesamedata,asitappearsinthePDMsystem).Inthiscaseit’smorecorrecttodeletetheoldunprocessedIDocfromyourERPsystem,andtosendagainfromPDMintoyoursystemthedatacontainedbyit.IfyouwanttoresendsomeCHRMASIDocsfromPDM,youshoulduseinthePDMsystemthetransactionBD91.AfteryousentthesedatafromPDM,thecorrespondingIDocswillappearinthePDMsystemwithstatus30(itmeansthattheywerenotleftthePDMsystemyet).ItexistsaperiodicbatchjobinPDM,whichwillsendoutperiodicallytheIDocsfromPDM,andafterthentheIDocwillappearinPDMwithstatus03.Startingwiththismoment,youcanfindthecorrespondingIDocalsoinyourERPsystem,havingthestatus64.AfterprocessinganotherperiodicbatchjobinyourERPsystem,