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 type Description of IDoc typeCHRMAS Class system: Characteristi
3、cs masterCLSMAS Class system: Classes masterECMMAS Engineering Change ManagementDOCMAS Master documentBOMDOC BOMs: Document structureZPDM_MATMAS Reduced Material master dataBOMMAT BOMs: Material BOMCLFMAS Class system: Classification masterECMREV Revision levelThe IDocs have to be processed in the a
4、bove described 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
5、 all we should 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:51 Application document not posted (error)53 Application document posted (this
6、should be the final status of the IDoc, if everything was processed successfully)64 IDoc 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);66 IDoc is waiting for predecessor IDoc (serialization) it means tha
7、t this message type is serialized, and this IDoc is waiting for the predecessor IDoc, in order to be processed.68 Error - 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).69 IDoc was edited it means that this ID
8、oc was changed manually (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 t
9、o restrict the overview to only those IDocs coming from PDM which have errors and couldnt be booked automatically in the system:For IDoc Status value ranges from 50 to 52 and from 54 to 70For Message Type BOMMAT, CHRMAS, CLSMAS, ECMMAS, DOCMAS, BOMDOC, ZPDM_MATMAS, CLFMAS, ECMREVThe dates in the Cha
10、nged On fields have 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 n
11、ot authorized for Change 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_L
12、OG in the field “Subobject“ 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
13、the desired selection,And 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 t
14、he corresponding button (Book 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
15、occur most often are presented 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
16、 Save:If you choose the option “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 c
17、orresponding CHRMAS IDoc.But 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 old
18、er 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 again from PDM into your system the data contained by it.If you want to rese
19、nd some CHRMAS IDocs from 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
20、 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 other periodic batch job in your ERP system, it will import these IDocs pe
21、riodically, 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 an IDoc in the PDM system, you will find it in your ERP system having an
22、 other IDoc number.3 How to 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 pr
23、ocess also the corresponding 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 a
24、ssignment of the characteristic 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) IDoc
25、s from PDM, regarding to the 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 E
26、RP system, and to send again 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
27、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, 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
28、 64. After processing an other 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
29、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.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 Engineeri
30、ng Change Master contained 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 e
31、rrors, please see below:It 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
32、 Master from PDM, which still 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 n
33、umber. We have to find out 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 f
34、or the highlighted object (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
35、 this Change Number (10195848). 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 th
36、e first line, the material 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, whi
37、ch are the Valid-From date 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
38、ERP system for this Change 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
39、.10.2011 it was an IDoc related 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
40、(it appears with status 68), 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 ECMMA
41、S IDocs from PDM, you should 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 periodic
42、ally 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 other periodic batch job in your ERP system, it will import these IDocs periodically, a
43、nd 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 an IDoc in the PDM system, you will find it in your ERP system having an other IDoc n
44、umber.After processing the 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 messa
45、ge “Error_while_checking_in_and_storing“The 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
46、CV03N in the NPP system:Solution: 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
47、 TC BD87 double-click on the IDoc 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 pr
48、ess “Process“.7. How to handle ZPDM_MATMAS errorsThe error message in the BD87 TC:could be related to some settings which dont correspond with the initial settings in Material Master.The problem occurred most often is related to the unit of measure: the unit of measure for the material does not matc
49、h the unit of measure defined in Material Master.In this case you can correct the IDoc segment manually:- Check the unit of measure defined in the Material Master for that material, and change it on the corresponding IDoc segment (using transaction WE02):After editing the IDoc, it will appear with status 69. After processing it again, it should appear with status 53.But please be careful the IDocs with message type ZPDM_MATMAS are not serialized! It means, that if you process an older IDoc, and in the meantime there were sent other (newer) IDocs from PDM, re
