topic Re: Error in include when trasnporting from DEV to QAS (please help) in Application Development and Automation Discussions

Error in include when trasnporting from DEV to QAS (please help)

Ananovaes — Tue, 19 Dec 2023 14:13:26 GMT

Hello, I'm geeting the following error when trying to transport a workbench request from DEV to QAS. Could someone please help?

I have seen people trying to mention include transportation prior to the original class. I don't know how to do this or even if it's the solution.error.png

Re: Error in include when trasnporting from DEV to QAS (please help)

Sandra_Rossi — Tue, 19 Dec 2023 15:09:28 GMT

===CO means the include of the protected section of the class.

The error INCLUDE ===CO not found may happen if you only transport LIMU CLSD, LIMU CPUB, etc. (but not LIMU CPRO = include ===CO)

The implementation missing for method means that the definition part was transported (LIMU C...) but not the method itself (LIMU METH).

The solution is to transport the whole class R3TR CLAS <class name> = all LIMU parts.

Re: Error in include when trasnporting from DEV to QAS (please help)

RaymondGiuseppi — Tue, 19 Dec 2023 15:12:41 GMT

Seems you import a method or other subobject before importing the whole class (include ending with CO should be 'Protected Section' source include)

In Development, execute SE38 on the include name, click on display object list to get the class name and list of methods, etc.
With SE24, SE80, SE01 or SE03 create a transport request with the whole classes (R3TR CLASS ZCL_SD_PICKING, ZCL_ZSDOD_PICKING_V2_DPC_EXT?)
Browse table PROGDIR with Name class + * as name to get list of all includes of the class

Re: Error in include when trasnporting from DEV to QAS (please help)

matt — Tue, 19 Dec 2023 15:24:03 GMT

You've forgotten to hide the names of the classes in a couple of places in your screen shot...

Re: Error in include when trasnporting from DEV to QAS (please help)

Sandra_Rossi — Tue, 19 Dec 2023 19:27:53 GMT

Please show the images instead of hyperlinks, in order to have both the text and the image in one place. It's even more useful when there are several images, it avoids the pain to open and close each of them separately and repeatedly.