Is it necessary to transport /SAPAPO/TS_SELKO Table entries to target systems

[Former Member]

Dear Scn mates

I am curious about /SAPAPO/TS_SELKO table entries in APO.

Is it necessary to transport table /SAPAPO/TS_SELKO entries to further ( taget) system .

If yes then how will we transport to avoid duplicate entries of the table.

I tried in our community old posts but ended with no luck.

Could some one please help me to understand this.

Thanks in advance for your help..

Cheers

K M R

[Former Member · Accepted solution]

Hi KMR

Your selection related data is saved in two table SELKO (Header Level) and SELPO (Details level), therefore transporting only SELKO table will cause some negative impacts and therefore please don't do this.

Standared way of importing the selection is

"You list down the selection IDs which you need to transport from one system to another and add them in transport by using T code - /n/SAPAPO/TSOBJ-> Click on Transport Selections"

System will always create GUID for each selection (its available in SELKO), if you create selection with same description in your quality and production individually, GUID in this case will be different and system always read GUID while reading selection in background job therefore before moving selection in Production system, please compare the description and GUID data whether its matching in both systems.if its matching then only you transport that selection ID. if description is matching but not GUID, it means that selection created individually in the system and not moved via TR in past.

In case if you need any further details, please let me know.

regards,

Sachin

[Former Member]

Thank you so much Sachin . It's worthy info.

Cheers

K M R