SPAU & SPDD

部署运行你感兴趣的模型镜像

SAP Help Reference: http://help.sap.com/saphelp_nw04/helpdata/EN/c8/61ec66e33611d1954b0000e82de14a/frameset.htm


Describe SPAU and SPDD.

When you apply a package, a large number  of objects are changed.

If you have applied any OSS notes to objects in your system, the hot package may overwrite these objects. 

SPDD is used to identify dictionary objects 

and

SPAU (repository objects), will identify any objects where the hot package is overwriting changes you have made through OSS notes. 

You must check all objects identified in SPAU and decide whether you need to reapply the OSS note or reset the code to the original SAP Code. 

If, for instance, you are applying hot package 34, SPAU identifies an object where you have applied an OSS note.  You must check the OSSs note and see if SAP have fixed that note in a hot package. 

If the OSS note has been fixed in hot package 34, then you should reset the object to its original source code.  This means that there is no repair flag set against this object again and it is now SAP standard code. 

If, however, the object is not fixed until hot package 38, or there is no fix available you have to reapply the OSS note, otherwise users will encounter the problems they had before the note was applied.

You must transport all reapplied notes and Reset to SAP Standard objects after you apply your hot package to your QAS and PRD systems.

-->When using Reset to original, the active version on the database is confirmed as the new original version.

What objects will come in SPAU and SPDD?

All the objects which are modified, after tansporting to the current system, will be listed in SPAU and SPDD. SPDD contains the list of all modified Data Dictionary objects, like tables, dataelements, domains,view...etc. The rest of all the modified repository objects will be listed in SPAU. 

What happens to the modifications done in the older version when we upgrade the version? (with Modification assistant and w/o)

After the initial upgrade happens, we have to do adjustments from SPAU/SPDD to maintain or reset the changes. That is, from the list of objects in SPAU/SPDD, you have to either carry forward the changes to the new version, by choosing the option ADOPT CHANGES (available on right click) or RESET TO ORIGINAL (available on right click).

Will they come in these transactions?

Yes, they will be listed in these transactions, after the BASIS updgrade activity. 

And what if we apply some patches(Notes) to the system? What is the impact of these patches to the SPAU transaction?
Patches will be supported by the version upgrade. In case of notes, we have to verify whether these notes are supported by the new version (you can go into http://www.service.sap.com/notes to verify this. Also, we have to analyze whther the code in the note is already incorporated in the new version. In this case you can ignore the chanes choosing RESET TO ORIGINAL option.

 

Cite from: http://www.sap-img.com/bc018.htm

您可能感兴趣的与本文相关的镜像

Stable-Diffusion-3.5

Stable-Diffusion-3.5

图片生成
Stable-Diffusion

Stable Diffusion 3.5 (SD 3.5) 是由 Stability AI 推出的新一代文本到图像生成模型,相比 3.0 版本,它提升了图像质量、运行速度和硬件效率

<think>嗯,用户遇到了LFACIF5D隐式增强时的错误“Object stillin upgrademode.Finish theupgrade first”。我需要先理解这个错误的原因。根据经验,这种错误通常与系统升级未完成有关。可能是在升级过程中,某些对象被锁定或标记为需要进一步处理,导致无法进行隐式增强。首先,我应该检查系统升级状态。用户可能执行了升级但未完成后续步骤,比如运行必要的后处理程序或事务。常见的需要运行的事务包括SPAUSPDD或SMU_PGUID。此外,数据库相关的升级步骤也可能未完成,比如执行mysql_upgrade或类似的工具,特别是如果系统使用MySQL的话。引用中提到在升级MySQL时遇到分区表的问题,可能需要执行特定的ALTER TABLE语句,这可能与数据库对象的状态有关联,但用户的问题更可能是在SAP系统中出现的。接下来,可能需要检查对象状态。使用SE80或SE24查看LFACIF5D对象的状态,确认是否处于“upgrade”模式。如果是,可能需要手动标记为完成。但要注意权限问题,可能需要BASIS团队协助。 另外,隐式增强的兼容性也是一个考虑因素。升级后,原有的隐式增强可能不兼容新版本,需要调整。使用SAAB或增强模式工具检查是否有冲突,并重新实施增强。日志分析也很重要。检查ST22中的ABAPdumps或系统日志,可能有更详细的错误信息。同时,查看升级日志,确认是否有未完成的步骤。 如果以上步骤无法解决,可能需要联系SAP支持,提供详细日志和错误信息,寻求进一步的帮助。用户可能需要执行特定的修复程序或应用补丁。 最后,确保所有步骤都按照升级指南正确执行,没有遗漏的后处理任务。有时候,系统升级需要多个阶段完成,特别是在复杂的ERP环境中。</think>### LFACIF5D隐式增强错误解决方案 #### 错误原因分析 该错误通常发生在以下场景: 1. **系统升级未完成**:对象仍处于升级锁定状态,无法执行增强操作[^1] 2. **隐式增强兼容性冲突**:升级后新旧版本代码不兼容 3. **数据库对象未同步**:表结构变更未完全应用 #### 分步解决方案 1. **确认系统升级状态** - 执行事务代码`SPAU`检查未处理的修改请求 - 运行`SMU_PGUID`确认升级后处理完成状态 - 检查数据库升级工具输出(如`mysql_upgrade`)是否包含未完成操作[^1] 2. **强制完成升级模式** ```abap * 在调试模式下执行 SET PARAMETER ID 'UPG_MODE' FIELD ''. CALL FUNCTION 'ENQUEUE_EO_FINS_UPG' EXPORTING mode_trkorr = 'X'. ``` 3. **重置对象状态** - 使用事务代码`SE80`定位LFACIF5D对象 - 右键选择"Reset Modification State" - 执行`SYSTEM->MODIFICATION->Release Modifications` 4. **重建隐式增强点** ```abap * 在增强点实现代码中添加版本检查 IF cl_enh_tool_root=>get_tool( )->is_upgrade_active( ) = abap_false. " 原有增强逻辑 ENDIF. ``` #### 注意事项 1. 操作前务必创建系统快照 2. 需要BASIS团队权限执行核心对象修改 3. 若涉及数据库分区表,需检查`ALTER TABLE`语句是否完整执行[^1]
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值