Skip to Content
Former Member
Nov 12, 2007 at 07:37 AM

Create API append in the transaction COMM_ATTRSET


Hi Friends,

We have implemented the Note <b>602673</b> to Download R/3 ERP Material Sales Status MVKE-VMSTD to CRM.

We have overlooked the point in the Note where it is mentioned that the check box <b>Create API append</b> should be checked while including the settype in the transporting request. We have found this when we read the document again and looked at the menu path Settype/Attributes -> Transport -> Include in Request. We entered our newly created settype here and and we could see that the check box Create API append is not enabled.

The problem is, we are having some BDocs in the intermediate state. When we reprocess them in the Development system they are processed successfully. But when we reprocess the BDoc in the Production system, it gives a dump with the DUPLICATE_ENTRY exception raised.

Our doubt is,

1. Does the enabling of the check box mentioned above will solve the problem?

2. What is the impact when this check box is checked or unchecked?

3. Is there any other reason for this dump? If so how to solve that?

We have found that in the BDoc, we have MNT_SETTYPE table filled with the settypes. In the Development system we have the newly created settype only once, but in the Production system the settype is seen twice. Is this the reason for the dump.

Please revert back with your ideas and solutions. You will be definitely rewarded with points.