Getting error after adding new fields in 2LIS_03_BF.

[Former Member]

Hi Experts.

I have include three new fields in the extractor 2LIS_03_BF using the LBWE to edit the structure MC03BF0 and drag this fields from the Pool are to the Selection area. After a lot of work, to understand that I have to clear the MCEX queue I had success to include these new fields.

Once this job was done, the next step was to release the request to QAS and PRD. But, after send to QAS I tried to test the extractor via RSA3, but I got a DUMP error: CONNE_IMPORT_WRONG_COMP_TYPE

After reading the dump, it seems that the Structure of the extractor was changed, but the ABAP code behind the scenes do not reflect this modification.

By the message:

When importing the object "MC03BF0_TAB", the component no. 64 in the

dataset has a different type from the corresponding component

of the target object in the program "SAPLMCEX".

I note that the component no. 64 is the exact place that the new fields included starts..so the abap found diferent types of dataset..

Does anyone know how to solve this issue?

It's necessary to delete al the queues in QAS and reinit all the stock?

Best Regards,

Thiago

[Former Member]

Thank you guys. I'll consider this informations to go ahead. Yesterday I cleared all this setup tables in QAS and transport the same requests again. Now there is no DUMP in QAS.

Also I found a document in SAP: "Transport Management for Enhanced LO DataSource. I'll initialize the extractor again, activate the delta and than try to include one more field in the extractor and send to QAS following this guide.

Later I post the result.

Thanks!

[Former Member]

So I'll have to reinit all the datas in PRD? Delete the infocube 0IC_C03, do the init delta again....?

[Former Member]

If you need historical data for these newly added fields then you have to reload everything(re-Init and delta) or

Perform selective deletion in Cube and do full repair.

If you don't need historical data for new fields.. then you need not to delete the data from the cube

[Former Member]

Hi Thiago,

Try these options.

1) See if Basis can back out the transport. Then run v3, execute delta 2x and reimport the transport.

2) If basis can't back out the transport. Back out the changes in Dev and import the structure in original state. Then run v3, execute delta 2x and reimport the transport. Redo changes and import.

Before you import the transport into your Production Environment, make sure you do the following:

• Setup quit time so no transactions are posting that generate MM docs.

• Run V3 update

• Unschedule V3 job

• Do a delta pull from BI 2x

• Import Transport

• Reschedule V3 job

As Srinivas states, if you want history for these new fields, you will have to load the setup tables or populate it via code loading into DSO/Cube.

Regards,

Dae Jin

[Former Member]

Yes, you have to delete the Queues across the landscape before transport... The way you have done in development should be done in Qual and Prod