《PROCESSINGIERRORSFROMTHEINTERFACEWITHTHE.docx》由会员分享，可在线阅读，更多相关《PROCESSINGIERRORSFROMTHEINTERFACEWITHTHE.docx（36页珍藏版）》请在三一办公上搜索。
1、PROCESSING IDOC ERRORS FROM THE INTERFACE WITH THE PDMTable of contents1. Introduction2. How to handle CHRMAS errors3. How to handle CLSMAS errors4. How to handle ECMMAS errors5. How to handle DOCMAS errors6. How to handle BOMDOC errors7. How to handle ZPDM_MATMAS errors8. How to handle BOMMAT error
2、s9. How to handle CLFMAS errors10. How to handle ECMREV errors11. Setting the deletion indicator for an IDoc12. Serialization errors1. IntroductionThe ERP system receives on a daily basis IDocs from the PDM system. The IDocs can be:IDoc typeDescription of IDoc typeCHRMASClass system: Characteristics
3、 masterCLSMASClass system: Classes masterECMMASEngineering Change ManagementDOCMASMaster documentBOMDOCBOMs: Document structureZPDM_MATMASReduced Material master dataBOMMATBOMs: Material BOMCLFMASClass system: Classification masterECMREVRevision levelThe IDocs have to be processed in the above descr
4、ibed order. This processing order is set in transaction BD44:Select ZGRP_PDM01, and double-click on Assignment of logical messages to serial. Group =Here you can see the sequence numbers for each message type: the message types with highest priorities should be processed first: so first of all we sh
5、ould process the CHRMAS Idocs (having sequence number 1), after then the CLSMAS IDocs (having sequence number 2), and so onRegarding the statuses of the IDocs, the statuses which occur most often are as follows:51Application document not posted (error)53Application document posted (this should be th
6、e final status of the IDoc, if everything was processed successfully)64IDoc ready to be transferred to application (it means that the IDoc was transferred already from PDM to the ERP system, but it wasnt processed yet);66IDoc is waiting for predecessor IDoc (serialization) it means that this message
7、 type is serialized, and this IDoc is waiting for the predecessor IDoc, in order to be processed.68Error - no further processing it means that this IDoc was deleted (it appears in the ERP system, it doesnt disappear, but it has a deletion flag).69IDoc was edited it means that this IDoc was changed m
8、anually (the information contained by one or more segments was changed). It should be processed after this change, in order to have status 53 for the IDoc.The monitoring of the incoming IDocs could be done through the transaction BD87:The following selection is recommended in order to restrict the o
9、verview to only those IDocs coming from PDM which have errors and couldnt be booked automatically in the system:For IDoc Statusvalue ranges from 50 to 52 and from 54 to 70For Message TypeBOMMAT, CHRMAS, CLSMAS, ECMMAS, DOCMAS, BOMDOC, ZPDM_MATMAS, CLFMAS, ECMREVThe dates in the Changed On fields hav
10、e to be maintained according to the specific needs.The selection can be saved and used afterwards:After the selection is made and the Execute button is pressed a screen with the errors appear:Every IDoc error has an error message. Some messages are self-explanatory, like You are not authorized for C
11、hange Document with document type QDO. For the messages which are not that clear the TC SLG1 can be used. This transaction shows a complete error log, giving the user the information needed about the root cause of the error.In the TC SLG1 enter CAPI in the field Object , CAPI_LOG in the field Subobj
12、ect and the IDoc number in the field External ID. Entering the IDoc number will speed up the search for the error log. After pressing the Execute button the error log is displayed:Also you can check the situation of the unprocessed IDocs, using transaction /casww/bd01:Make the desired selection,And
13、press the button Execute:Here you can see the IDocs (according to your selection criteria), and also the error message for each IDoc, in the column “Description”.Also, if you want, you can process the IDocs having the status 51 or 64/66, by selecting the IDoc and pressing the corresponding button (B
14、ook Stat51, or Book Stat 64/66).An other option is, that you can make a variant which can be used in a batch job, in order to be sent to you automatically by e-mail the list of unprocessed IDocs, making the following selection:2. How to handle CHRMAS errorsThe errors which occur most often are prese
15、nted below:It means that this value is used in some Characteristics, so you should check if you still need this value, or not.You can delete this value manually if needed, using transaction CT04:If you decide to delete this value, you can press the button “Delete Value” and Save:If you choose the op
16、tion “Do not check”, it will appear the following message:Press the button “Continue (Enter)”:If you press the button “Yes”, then finally this value will be deleted from the mentioned Characteristic. So it will appear the following message: .After then you can process the corresponding CHRMAS IDoc.B
17、ut please be careful the IDocs with message type CHRMAS are not serialized! It means, that if you process an older IDoc, and in the meantime there were sent other (newer) IDocs from PDM, regarding to the same Characteristic, in this case the information contained by the older IDoc will be overwritte
18、n into your ERP system (so it will not be any more the same data, as it appears in the PDM system).In this case its more correct to delete the old unprocessed IDoc from your ERP system, and to send again from PDM into your system the data contained by it.If you want to resend some CHRMAS IDocs from
19、PDM, you should use in the PDM system the transaction BD91. After you sent these data from PDM, the corresponding IDocs will appear in the PDM system with status 30 (it means that they were not left the PDM system yet). It exists a periodic batch job in PDM, which will send out periodically the IDoc
20、s from PDM, and after then the IDoc will appear in PDM with status 03.Starting with this moment, you can find the corresponding IDoc also in your ERP system, having the status 64. After processing an other periodic batch job in your ERP system, it will import these IDocs periodically, and after then
21、 the IDoc should appear in your system with status 53 (it means that it was processed correctly).Please be aware that the number of the IDocs are different in PDM and in your ERP system. So if you have an IDoc in the PDM system, you will find it in your ERP system having an other IDoc number.3 How t
22、o handle CLSMAS errorsThe error occurred most often is due to the fact, that some characteristics contained by that class dont exist in your system.In this case you should process first of all the CHRMAS IDocs related to the missing characteristic, and after then you can process also the correspondi
23、ng CLSMAS IDocs.An other error which can occur is the following:In this case you should go to transaction CL6K, specify the Class number, the Class Type and the Characteristic which should be deleted (according to the IDoc), and press the button “Execute”:In this case the assignment of the character
24、istic will be deleted from the mentioned Class, and after then you could process your CLSMAS IDoc.But please be careful the IDocs with message type CLSMAS are not serialized! It means, that if you process an older IDoc, and in the meantime there were sent other (newer) IDocs from PDM, regarding to t
25、he same Characteristic, in this case the information contained by the older IDoc will be overwritten into your ERP system (so it will not be any more the same data, as it appears in the PDM system).In this case its more correct to delete the old unprocessed IDoc from your ERP system, and to send aga
26、in from PDM into your system the data contained by it.If you want to resend some CLSMAS IDocs from PDM, you should use in the PDM system the transaction BD92. After you sent these data from PDM, the corresponding IDocs will appear in the PDM system with status 30 (it means that they were not left th
27、e PDM system yet). It exists a periodic batch job in PDM, which will send out periodically the IDocs from PDM, and after then the IDoc will appear in PDM with status 03.Starting with this moment, you can find the corresponding IDoc also in your ERP system, having the status 64. After processing an o
28、ther periodic batch job in your ERP system, it will import these IDocs periodically, and after then the IDoc should appear in your system with status 53 (it means that it was processed correctly).Please be aware that the number of the IDocs are different in PDM and in your ERP system. So if you have
29、 an IDoc in the PDM system, you will find it in your ERP system having an other IDoc number.4 How to handle ECMMAS errorsIn case of the unprocessed ECMMAS IDocs, it can occur the following error message:In this case you can delete the unprocessed IDoc, because the Engineering Change Master contained
30、 by it was imported already into your system.In this case you also should update the counter using transaction BD103, because the ECMMAS IDocs are serialized (for more details about serialization of the IDocs please read the chapter 12).But you can have also other type of errors, please see below:It
31、 means that your IDoc cannot be processed, because the Change Master contained by it was used already in your ERP system at least in one object, and it will lead to a data conflict in case if you make some changes for this Change Master. Probably it was sent an other Change Master from PDM, which st
32、ill was not entered into your system, and in this case you should process first of all the corresponding IDoc for this Change MasterI will present below how to solve this kind of error.The Change number contained by the IDoc (000010195848) is “waiting” for an other change number. We have to find out
33、 what is this Change number (in order to see after then, what happened with the IDoc referring to it). In the error log we see, that its something related to the object M0004623501.Using transaction CC03, we look for our Change number (000010195848):And after then we look for the highlighted object
34、(M0004623501):We found out, that this object is related to the following material BOM: A2C37665200.We look on this material BOM, using transaction CS03:We observe, that starting from 24.10.2021 this BOM will contain an item (at the position 0010): A2C00437000, introduced by this Change Number (10195
35、848). If we check our unprocessed IDoc related to this Change Number, it should change its Valid-From date to 09.11.2011.But if we want to change the Valid-From date of this change number (10195848) to 09.11.2011, we will have a conflict in this BOM, because according to the first line, the material
36、 A2C00436900 should be used starting with 14.07.2021 (according to the Change number 10189890). But the Valid-From date of the second Change number (10195848) will be before this date (it should become 09.11.2011, according to our IDoc).We could check in the PDM system, which are the Valid-From date
37、 for these two Change Masters.We will find out, that the Change Master 10195848 has the Valid-From date 09.11.2011, as it appears also in our IDoc,but the Change Master 10189890 has the Valid-From date 05.10.2011 ! So it doesnt fit the Valid-From date which appears in your ERP system for this Change
38、 Master, which is 14.07.2021.It means that probably it was sent an IDoc also for this Change number (10189890), which was not processed in your ERP system.Using transaction WE09, we can identify which was the IDoc # that was referring to the Change number 10189890:So, on 05.10.2011 it was an IDoc re
39、lated to the change number 10189890, which was deleted (it has status 68).This is the reason that our initial IDoc (13255034) couldnt be processed it was waiting to be processed the IDoc # 13177523 before.Taking in consideration that the IDoc # 13177523 was deleted already (it appears with status 68
40、), in this case we should send again from PDM the Change Master 10189890 (which was initially contained by the IDoc #13177523), and after then our initial IDoc (#13255034) related to the Change Master 10195848 could be processed successfully.If you want to resend some ECMMAS IDocs from PDM, you shou
41、ld use in the PDM system the transaction CC92. After you sent these data from PDM, the corresponding IDocs will appear in the PDM system with status 30 (it means that they were not left the PDM system yet). It exists a periodic batch job in PDM, which will send out periodically the IDocs from PDM, a
42、nd after then the IDoc will appear in PDM with status 03.Starting with this moment, you can find the corresponding IDoc also in your ERP system, having the status 64. After processing an other periodic batch job in your ERP system, it will import these IDocs periodically, and after then the IDoc sho
43、uld appear in your system with status 53 (it means that it was processed correctly).Please be aware that the number of the IDocs are different in PDM and in your ERP system. So if you have an IDoc in the PDM system, you will find it in your ERP system having an other IDoc number.After processing the
44、 IDocs with status 51 (error), then you should process also the IDocs having the status 66 (IDoc is waiting for predecessor IDoc (serialization). For more details about the serialization of the IDocs please have a look on chapter 12.5. How to handle DOCMAS errorsError message Error_while_checking_in
45、_and_storingThe error message in the BD87 TC:Double-click on the IDoc number. The following screen appears:Having the number, type, part and version of the document from the IDoc check in TC CV03N its content:The ERP version of the document:Perform the same check with TC CV03N in the NPP system:Solu
46、tion: Resend the document from the NPP system with the TC ZX81. Book immediately the IDoc in the ERP system and delete the old IDoc.6. How to handle BOMDOC errorsThe error message in the BD87 TC:Enter one of the IDoc numbers in the TC SLG1. The error log is displayed:In TC BD87 double-click on the I
47、Doc number and copy the document details (number, version etc):Check with CV03N in the NPP system if the document is there available:Solution: Resend the document from the NPP system with the TC ZX81. In the ERP system go to TC BD87, select the faulty BOMDOC IDoc and press Process.7. How to handle ZPDM_MATMAS errorsThe error message in the BD87 TC:-
