Workflows for Supplier Invoices – “not starting” Issue(with Chinese translation)
Customer Issue Description:
Supplier invoice items can not be forwarded to approvers after 2002CE upgrade, when customers create supplier invoices and choose “Save as Completed”, for the approvers they do not see any invoice items in their “My Inbox” to be approved.
Or for blocked invoices, the release approvers can not see invoice items in “My Inbox”, not able to release blocked invoices.
Analysis to determine whether this is caused by 2002CE upgrade, then the attached workaround is applied:
Via transaction SCU3 in the customer’s test system for T169WF02, if it is the case like the sample as below:
And in “Manage Your Solution” under Configure Your Solution -> Sourcing and Procurement -> Invoice Processing -> Incoming Invoice -> Activate Flexible Workflow for Supplier invoices (SSCUI 101098):
The values in T169WF02 were changed with the upgrade to 2002CE in the Q-system, the workflows were deactivated via the upgrade.
The configuration file of IMG T169WF02 was updated from both “X” selections to blank for 1802CE release, without NUR indicator (the indicator was dropped during restructuring from moving one building block to a new building block) for the IMG in solution builder plus the values have been changed during 1802CE, the blanks replaced the original “X”s.
As a consequence, the workflows are deactivated.
The customizing in the test and productive systems needs to be set up. There is a customizing in the app “Manage Your Solution”:
Configure Your Solution -> Sourcing and Procurement -> Invoice Processing -> Incoming Invoice -> Activate Flexible Workflow for Supplier invoices, to determined whether the flexible workflows for supplier invoices should start or not.
1. Steps in test system: As this setting cannot be maintained in the productive system, please activate the setting of both “Payment Block” and “Release Completed Invoice” (must comply with the Old setting of customer’s before 2002CE upgrade, check via transaction SCU3 in the customer’s test system for T169WF02 like screenshot above, usually only the first and second “X”s needed), and transport from the test system to productive system.
Then the workflows for invoices can be triggered.
2. After the configuration above arrive in productive system, then execute steps regarding invoices have created in the past days：
2.1 For which are currently not subject to the workflow for parked and completed invoices, please firstly choose “Edit” and choose “Park” those invoices, afterwards choose “Edit” and choose “Save as Completed”. With the two steps the workflow will start for those invoices.
2.2 For which are currently not subject to the workflow of blocked invoices (e.g EDI invoices), the editing is not allowed, please reverse the supplier invoices and reprocess the invoices as usual again to start the blocked invoice workflow.
The detailed invoice reverse steps, you may refer to sample series steps including “Reverse Supplier Invoice”, “Clear GR/IR” and “Cancel Journal Entry” like below:
2.2.1 Reverse Supplier Invoice
2.2.2 Clear GR/IR
2.2.3 Cancel Journal Entry
2.2.4 After you finish the steps above, you can reprocess the invoices as usual again to trigger the blocked invoice workflow.
分析确定该问题是否由 2002 CE 升级导致，并应用以下解决方案：
使用客户测试系统中的事务SCU3 查看 T169WF02，如果情况如下所示：
并且 配置您的解决方案-> Sourcing and Procurement -> Invoice Processing -> Incoming Invoice -> 激活供应商发票的灵活工作流（标识 101098）界面如下所示：
T169WF02 中的值已在质量系统中升级到 2002CE，工作流在升级中被取消激活。
升级后，IMG T169WF02的配置文件从1802CE中的两个“X”选项变为空白, 且IMG解决方案没有NUR 标识 (标识从一个构件块移至新构件块期间被删除），并且值在 1802CE期间已经被更改，空白替代了原值“X”。
配置您的解决方案-> Sourcing and Procurement -> Invoice Processing -> Incoming Invoice -> 激活供应商发票的灵活工作流，确定供应商发票的灵活工作流是否启动。
1. 测试系统中的步骤： 由于此设置无法在生产系统中维护，请激活“付款冻结” 和 “审批已完成发票”的设置（必须符合 2002CE 升级之前客户的旧设置。并如上文截图所示，使用客户测试系统的SCU3 查看 T169WF02，通常只需要第一和第二个“X”），并从测试系统传输到生产系统。
2.2.2 清算 GR/IR清科账目
Thanks for this Nora 🙂
Thanks Nora and this will help a lot for customers from China.
Thank you for Sharing!
thanks for sharing
Hi Nora, thanks so much for updating the Chinese version.
thanks for sharing. the Chinese version is quite useful.