cancel
Showing results for 
Search instead for 
Did you mean: 

Error in EEWB after extending existing Extension

Former Member
0 Kudos

Dear Sap gurus;

yesterday we added a new customer field (zzcategory_id) for business transaction (complaints) in an existing extension XXXX.

We did this using the wizard, where in the step ''Define Fields'' we added this new field, also indicated that it was relevant for header level.

Anyway...we created a New transport request for this regeneration, e.g.

CRTK900301.

The generation really took us a while (I think about 1/2 hour) and somehow the generation process suddenly also created new tasks under another 'not released transport request CRTK900201 for example).

Now the status of the Extension = 'Extension Objects Generated' Version 6.

the Extension object has a red colour.

The task added for this extension is:

CRM_BTX_ADD_NEW_FIELDS and has status:" Processed with Errors".

<b>when checking the log for this taks, I get the following:</b>

No task for editing objects can be determined

Message no. TK599

Diagnosis

One or more objects could not be checked for editing because no suitable task was found.

"CRTK900101" was defined as proposed request. This request is not valid for editing the specified objects.

Procedure

Check the request. If necessary, define another request.

<b>However</b>, this transport request CRTK900101 was already released on 28.08.2007 and the extension of the existing Extension only was done yesterday.

The second error message we get for this Task in the log =

"deleting of existing BAdI Implementation "ZEEW_CUSTOMER_H02" failed".

any clues what went wrong, and better...how we should solve this?

thanks for a quick response

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

OK,

the problem is solved.

cause of the error:

We only made a transport request during usage of the wizard to change the existing extension when adding the new field. (on the level of the extension).

However, on the level of the Project, the old 'initial Customizing and workbench' requests were still mentioned.

You can change this by selecting your project (double-click) and next right-mouse click on the project and choosing: "transport requests".

There we entered the workbench request that was created during the change of the extension + we also created a new customizing requests and assigned it to the project. Afterwards we could generate the Extension again succesfully.

cheers

davy

Former Member
0 Kudos

OK,

the problem is solved.

<b><u>cause of the error:</u></b>

We only made a transport request during usage of the wizard to change the existing extension when adding the new field. (on the level of the extension).

<b>However,</b> on the level of the Project, the old 'initial Customizing and workbench' requests were still mentioned.

You can change this by selecting your project (double-click) and next right-mouse click on the project and choosing: "transport requests".

There we entered the workbench request that was created during the change of the extension + we also created a new customizing requests and assigned it to the project. Afterwards we could generate the Extension again succesfully.

cheers

davy