Transport request error

[Former Member]

I'm facing a transport request error problem.

I imported a transport request to production system. It ended with error code: 8. But the transport is successful from DEV to QAS system.

The error message is as below:

R3TRTABLZQUO_WF_CONTROL original object cannot be replaced

ZQUO_WF_CONTROL is a Z-table.

There are some information about this issue. They may help to analyze the issue.

1. The transport error object is table zquo_wf_control. This table already exist CRP system previously. Now I add a new field (not key field) in this table.

2. I found this table's Original System is CRP with transaction SE03 in CRP system. But the table's Original System is CRD in CRQ system. And the other Z-table's Original System is CRP in CRP system. For example: table ZIP_ROYALTY.

I confuse why the table's Original System is different between CRQ and CRP. Our CRQ system is coped from CRP system.

I try to change table (zquo_wf_control)'s Original System from CRP to CRQ. After that, I re-transport this request. The transport still fail.

Please help on it. Thanks

[Former Member]

Hi Michelle,

When you transport the request using transaction STMS,

in the popup screen 'import transport request', in tab 'options', you see a list with 'import options'.

Tick the checkboxes 'Overwrite Originals' and 'Overwrite Objects in Unconfirmed Repairs'.

Hope this solves your issue.

Kind regards, Miranda

[Former Member]

Hi Michelle,

When you transport the request using transaction STMS,

in the popup screen 'import transport request', in tab 'options', you see a list with 'import options'.

Tick the checkboxes 'Overwrite Originals' and 'Overwrite Objects in Unconfirmed Repairs'.

Hope this solves your issue.

Kind regards, Miranda

[Former Member]

Dear Botman,

Thanks for your reply. But the issue still exsit although I choosee that two options. But the transport still failed.

[Former Member]

Dear,

This issue has been solved by our basis. She just choosed the option "overwrite original". The request transport is fine. It is a strange case. However, it's so glad that the issue is solved.

Thanks

Michelle

[Former Member]

The issued has been solved.