I am using a PBET Update profile, are there any constraints ?
You should run FM_DLOI only in exceptional cases when no other solution is found. Executing FM_DLOI and then reposting with FMN3N, FMN4N, FMN5N, FMNSDN etc. will result in a collection of FMIOI table entries. Therefore you will loose the track of change history. The totals will be corrected but the chronological change information will no longer be available.
FMIOI records with amount types 0100, 0150 will be collected in a single 0100; all 0200 as a single 0200. There will be no reassignment records (amount types 0600/0650) because the system will rebuild utilizing the most recent Account assignment data.
I am using a NON-PBET Profile, are there any constraints ?
In those cases, the 0100 and 0200 will still be collected and rebuilt after using the corresponding transaction for subsequent posting (FMN3N, FMN4N...). Rebuild will take place based on date setup for FM Posting Date: Posting/document date, due date, or delivery date (update profile settings).
Can I rebuild Trips deleted with FM_DLOI ?
Report RPR_CORRECT_COMMITMENT is available and can be used as follows:
Using flag 'Post Explicit Trips subsequently', you can rebuild trips in status:
'Open' or 'Completed'
What is the effect of FM_DLOI on carried forward documents?
If you do not select Do not delete documents in FYC, the Fiscal Year Change information will get lost and commitment carryforward will need to be reexecuted.
How to deal with documents documents originated in external systems ?
Deletion of documents coming from external systems (different logical systems) like SRM (Supplier Relationship Management) or Trips, will cause inconsistencies and should not be performed. Reconstruction will not work because source tables are only available in the external system. Therefore deletion of those documents with FM_DLOI is never recommended. Instead, reconstruction should be triggered from the external system (for example by making a change to the original document).
This is also applicable to transaction FMMC (Close Open items) that should not be used on any document originated in an external system.
For SRM customers:
- Instead of using FMMC, SRM provides /SAPPSSRM/CLOSEOUT for closing commitment
- For reposting an SRM Shopping Cart (FM Value type 50 ), you should use /SAPPSSRM/SC_COMMIT_REPOST
- For reposting an SRM Purchase Order (FM Value type 51), you should use /SAPPSSRM/MCN
After an upgrade to EHP4 or above, from a release older than EHP4, FM_DLOI is not working anymore with certain documents, why?
As of EHP4, new checks have been introduced in FM_DLOI , in a way that documents belonging to other logical systems will be protected against deletion. See information in question 5
Note: With note 2190393, deletion of FM data of SRM Purchase Orders is possible
I am using BW, does FM_DLOI update BW ?
Yes, the records to be deleted will be transferred to the BW delta queue.