Create API append in the transaction COMM_ATTRSET

[Former Member]

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.

Regards,

Raju

[Former Member · Accepted solution]

Hello Narayana,

Settypes and attributes are designed to be maintained in the production system,

I guess you are using a transportable package to transport the settype to the production system.

If you select create API append indicator, it should be possible to maintain settypes using API's, you need to enter the transport request number and once released and transported, the settype is transported to the predefined systems.

regards,

Muralidhar Prasad.C

[Former Member · Accepted solution]

Hi Murali

Thanks for the reply..

But my question is what is the reason for the dump when I reprocess the BDoc in the Production system. And why the settype entry in the BDoc is twice?

The dump shows that the exception is raised from the include program SET_RELF41 and in the code

• update buffer

INSERT ls_prrel INTO TABLE gm_prrel.

IF sy-subrc NE 0.

RAISE duplicate_entry.

ENDIF.

DELETE TABLE gm_prrel_delete FROM ls_prrel.

How to solve this?

Regards,

Raju

[Former Member · Accepted solution]

Hi

Is there any configuration issue related to this? Why the settype is added twice to the BDoc? Is this the reason for getting the dump of duplicate entries?

Please send your ideas.

regards,

Raju