Skip to Content

Table Entry manual collection in Transport Request

Hi All

Environment- BW 7.4 with ECC-6 EHP7

As part of project activity we are using data source 2LIS_02_SRV..

Activation is done as per instructions in thread Datasource for Services Procurement

Datasource is loading records successfully in Dev Environment,Post transport to QA Datasource is not loading any records

Post analysis understood that TMCEXACT table entries(as shown below) for Extract structure is missing

Could you suggest how to manually collect below Table entry in a Transport request,so this can be transported across environments

I did gave a try using SM30/SE16 but no luck as change/transport options are disabled

Thanks

Bose

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Oct 28, 2015 at 08:02 AM

    Hi Bose,

    Did you check those missing table entries from TMCEXACT table in your source (Dev) system? have you maintained them manually in Dev?

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 28, 2015 at 08:17 AM
    R3TRTABU

    TMCEXACT

    and specify your keys

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 28, 2015 at 08:28 AM

    hi Bose,

    Normally we won't transport tables.

    At Dev system reactivate your data source and recollect into new transport.

    later release transport and check at target system.

    if not rectified your table entries then you can collect table thru SE11 or SE16N.

    From menu options you can collect table into new transport request. Find option like - Goto --> object direct entry from menu options.


    Thanks

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 28, 2015 at 09:21 AM

    Hi Bose,

    Goto table entry --> select the table entry and from the menu --> "Table Entry" -->Transport Entries.

    It will prompt for a transport request --> Only that particular entry will be collected into the transport request.

    Once the transport is migrated to QA environments you can find that entry.

    Regards

    KP


    1.PNG (6.4 kB)
    Add comment
    10|10000 characters needed characters exceeded