GS01/GS02/GS03 Set and transport request

SAP剑客

于 2017-12-01 15:19:04 发布

阅读量1.3k

点赞数 1

分类专栏：程序人生 ABAPer

本文链接：https://blog.csdn.net/zhongguomao/article/details/78687067

版权

程序人生 ABAPer 专栏收录该内容

1331 篇文章

订阅专栏

本文介绍了 SAP SET 工具的基本使用方法及其在不同系统间数据迁移时可能遇到的问题。当从开发环境向生产环境迁移 SET 数据时，可能会覆盖生产环境中的定制设置，导致数据丢失。文章还讨论了如何查看更改历史记录以及默认情况下迁移 SET 数据的风险。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

SAP SET is a very useful tool , allow user to record , save customized setting data. Before we use it , it can be created by Tcode GS01, and we edit and save the customized data using GS02, display it via. GS03.

It is easy to use, we can call function G_SET_GET_ALL_VALUES in ABAP to get data from a SET, especially in FI valid. / subs. Steps, we can use it directly via IN statement as below.

But there is some trouble when we transport a SET to productive system from another system.

As we know, we can edit SET data using GS02 in DEV, QAS, PRD independently, So, there are mostly some difference between DEV and PRD SET data. If we put a SET into transport request in DEV, it indicate that we put the DEV data into the request, and the SET data will be overwritten after we transport this request to PRD, it is dangerous.

more serious, it's difficult to restore PRD SET data, since the last data record is destroyed, if we click the change history, a message popup as follow.

But normally it display the change record fully:

In addition, we must know that transport set is checked by default when transporting a Valid. / Subs. It is a risk if there is a SET used in this Valid. / Subs.