SAP Note

Header Data

Symptom

The Expense screen of resource related billing shows items already billed as negative items and additionally as positive items. This subsequently creates a credit memo request as well as a debit memo request. After applying changes to your DIP-profile you see, that items already billed are credited and billed again. After changes of characteristics values for a dynamic item - also possible via user-exit, items already billed are credited and billed again. When entering a value in field "Posting date to" in the entry screen for a DIP run, that is earlier than one from a prior DIP run, items already billed are credited and billed again. Why does this happen -> see solution.

Other Terms

DP90, DP91, DP95, DP96, DP97, ODP1, AD01DLI, AD01DLIEF, AD01DLISF, document flow

Reason and Prerequisites

Missing information about the technical background.

Solution

During the creation of the debit/credit memo request a so called document flow for resource related billing is written. This document flow is the relation between the source record and the dynamic item and the debit memo request. The document flow also contains a "Posting to" date, which is used to identify the time range up to which source records were taken for creating dynamic items. Source records can be identified as belonging to a certain debit memo request item by their set of characteristics values - and of course their posting to date. If this set of characteristics values changes during an ongoing billing process, the connection between the debit/credit memo request item and the orginal expense (source record) is lost. The same is for changed 'posting date to'. This would lead to inconsistencies in the document flow, if the document flow would not be updated. For instance cancellations would not be possible or be inconsistant. The change of characteristic values can occur as well from changes in the DIP-profile as from changes in indicating a characteristic value in a user-exit. To get back to a consistent situation, the system in this case cancels all already existing dynamic items and re-bills them. That can lead to an enourmous amount of credit memo request lines and corresponding debit memo request lines. But only this can make sure, that the relation between source, dynamic item and billing request item is there and unique and cancellations do not make any problems. If an earlier "Posting to" date is used for a later DIP run for the same objects, than the one that was used in the prior DIP run, the correction is slightly different. In this case, the system has to cancel all dynamic items belonging to source records in_the_time_range_between_the_earlier_used_and_now_used "Posting to" date. This is necessary, as already billed items from source records later than the actual "Posting to" date must not be taken into account for the actual DIP run, and therefore the already existing document flow for these source records has to be cancelled.

    698230 - DIP-Process: Expense items credited and debited  

Version   5     Validity: 02.07.2007 - active   Language   English (Master)

Released On 02.07.2007 12:22:36

Release Status Released for Customer

Component PS-REV-ACT Actual Revenues and Forecast

CS-BS Fakturierung und Abrechnung

CS-BS-BI Billing

PS-REV Erlöse und Ergebnis

SD-BIL Billing

SD-BIL-IV Fakturabearbeitung

SD-BIL-IV-SM Aufwandsbezogene Fakturierung

Priority Recommendations / Additional Info

Category Consulting

Other Components

As the behaviour described in the 'symptom' area may come up because of two different reasons, two solution paths are available. Two general recommendations should be kept in mind:

It is strongly recommended not to apply changes to DIP-profiles used in an ongoing billing process.

It is strongly recommended only to use increasing dates for the "Posting to" date of DIP runs using the same objects.

First solution path - for changed characteristics values:

There are now several possibilities to deal with the situation:

1. Recommended: Let the old objects fade out with the old DIP-profile and start new objects with the new DIP-profile.

2. If you really need to have the change immediately, you can use the following solution, which consists of four steps:

a) For the old objects: Restrict the source not to select old records - for instance by posting date.

b) Let the material determination not find dynamic items for the old items.

c) Set the flag 'DI with material' in the usage view of the DIP-profile.

d) If possible, start even though new objects with a new DIP-profile without the additional restrictions to the source and the flag 'DI with material' in the usage view of the DIP-profile not set ... - so to say with a 'normal' DIP-profile.

                       Caution: You will get problems cancelling items from before the change date! Please use this possibility only, if you are aware of this and sure, that you will not cancel items from the time before the change.

Second solution path - for decreasing 'posting to' dates:

Please see note 557159.

Validity

This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (2)

557159   DP90: Entry of 'Posting date to' leads to incorrect value

545095   FAQ 2: billing/accrual/quot./results analysis

545095   FAQ 2: billing/accrual/quot./results analysis

557159   DP90: Entry of 'Posting date to' leads to incorrect value