-
Vendor invoice created via data management (OCR / Scanner process) and automatic receipt matching
When vendor invoices are imported from data management (with OCR or scanner process), there is no automatic receipt matching.
If the purchase order has already been received and product receipt information is part of pending invoice imported, match status is not automatically updated.
Invoice has to be edited to have match status refreshed.
The idea will have an option (or batch) to automatically match the pending invoice is purchase reception.
-
Workflow reject to be reassigned to previous steps.
Workflow with several approval steps is rejected on last one.
Actual behavior: Workflow will have to be resubmitted by initial user.
Expected result: Workflow should then be reassigned to a selected step (n-1)
-
Accounting distribution to be updated after posting modification
Purchase orders are created. Accounting distribution is then based on inventory posting. (or category posting).
If for any business requirement, posting is modified. all puchase orders created before will not consider this new accounting distribution during invoice validation.
All lines required manual update to see new distribution. It is time consuming.
Periodic process should be implemented in order to update accounting distribution based on some criteria selected by customer.
-
Consolidation period control for modification
When consolidation process is run twice on same period, there is no control or indication that new transactions have been transferred.
Period statut does not work on consolidation company so no blocking can be done.
The idea will be to have some warning or control before process is completed to identify new transactions when process is run several times.
-
Withholding tax payment should consider vendor account from tax authorities
Vendor account is set on Withholding tax authorities. But when withholding tax payment is generated, no transactions is posted on vendor account.
Withholding tax payment should be working as tax payment. Transactions is expected to be posted on vendor account.
-
Conditional VAT in foreign currency - Payment exchange rate gain/loss option
VAT is posted on foreign currency. when payment is done, Conditional VAT is reversed to post final VAT. But Exchange rate can differ and generate exchange rate gain and loss.
There is 2 options to handle conditional VAT payment.
Actual design
Posted VAT is posted at Payment exchange rate.
Exchange rate gain/loss is posted on conditional VAT / gainLoss acount
Options on sales tax code (suggested)
Conditional VAT payment done at invoice rate.
Exchange rate gain/Loss will be on vendor/customer account.
Check SAP design in following website Option is available on conditional VAT
https://help.sap.com/saphelp_sbo900/helpdata/FR/4a/31002ba06b47a29c27cb8beb579ca5/frameset.htmConditional
-
Stock adjustment and financial dimension
Stock adjustment does not consider financial dimension rules set on account structure.
The transaction is based on initial stock transactions that is often set with different financial dimension rules.
As consequence, stock offset account often set with cost account (P&L account) will not follow reporting rules.
Impact for management reporting can be consequent.
-
Intercompany flow is blocked when vendor invoice workflow is activated
Intercompany direct delivery is created with automatic purchase invoice validation.
If workflow is activated on Intercompany purchase company, the Intercompany sales is cannot be posted as ICO purchase invoice is not submitted to workflow.
But purchase invoice workflow cannot be submitted as set for automatic posting.
Workflow should consider Intercompany flow with automatic posting.
Workaround: conditional activation should be added to not consider intercompany.
To work workflow should not be set "as default"
-
Worker relationship to be considered private
in Global address book security access can be set for private information.
Relationships are not considered as private and can be seen by users with access to Global address book.
Relationship can provide family information, name or other personal information that should not be shared and must be private.
Laws have been published in almost all countries to protect individual and their private life.
-
Default description for project elimination and estimation does not exist
Default description for project elimination and estimation does not exist. As consequence there is no voucher text for these transactions. Voucher description provided business information to user but also for audit report that help to understand content.