SAP ABAP IMG Activity SIMG_OLPR_ODP5 (Residence Time of the DIP Source)
Hierarchy
BBPCRM (Software Component) BBPCRM
   CRM (Application Component) Customer Relationship Management
     CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       CNPC (Package) R/3 Customizing PP Project Management
IMG Activity
ID SIMG_OLPR_ODP5 Residence Time of the DIP Source  
Transaction Code S_AL0_96000866   (empty) 
Created on 20020208    
Customizing Attributes SIMG_OLPR_ODP5   Residence Time of the DIP Source 
Customizing Activity SIMG_OLPR_ODP5   Residence Time of the DIP Source 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_OLPR_ODP5    

Use

Resource-related billing determines the original expenditure from the source data always and determines the open expenditure by comparing the document flow for the billed expenditure. The original expenditure is not stored additionally, but rather remains alone in the sources.

If the source data is totally or partially archived, the system displays an original expenditure of 0 for resource-related billing. If the source data has already been billed, credit memo items are created, because the billed expenditure is greater than the original expenditure.

In the SAP Standard System this situation can appear if you bill based on actual cost line items or statistical key figures, and then archive them using the archiving object CO_ITEM.

In this IMG activity you can prevent this effect from happening by creating residence times for DIP sources. You can archive all sources you specified, which are older than the residence times. This is possible for sources of the standard as well as for your own sources.

For the standard sources "Actual Cost Line Items" or the statistical key figures, you can prevent the table COEP from growing too large and improve the overall performance of your system.

Note that in some cases the existing open expenditures can no longer be billed for archived source data.

Requirements

Standard settings

Activities

You can stipulate the residence times depending upon the source, controlling area, and object type. The system identifies the residence time in billing periods.

You can make the following settings:

  • Source:

    You can use then same sources as those used in the DIP Profile. Specifying the source is obligatory.

  • Object type:

    Entering the object type is optional. If you do not specify an object type, the residence time for all object types is valid. The following values are valid for the object type:

    AUF Order

    NPL Network

    PSP WBS Element

    VBP Sales document item

  • Controlling area:

    Specifying the controlling area is optional. If you do not specify a controlling area, the residence time for all controlling areas is valid.

  • Residence time:

    The residence time is specified as the number of billing periods. Specifying this value is obligatory.

If you specify data for the two optional parameters "controlling area" and "object type", the object type is evaluated before the controlling area.

Example

You specified the following values in the table:

Source        Object type        Controlling area        Residence periods

001                        12

001                001        24

001        NPL                36

001        NPL        002        48

In this case the residence time for networks in the controlling area 0002 has 48 periods and in all other controlling areas 36 periods. The following is valid for all other object types:

In controlling area 0001 the residence time has 24 periods, otherwise 12 periods. The values are valid for the source 0001 only ('Actual cost line items').

Evaluating Residence Times

The system evaluates residence times as soon as billed expenditures for a billing period in the document flow exist, but for which no original expenditure using the corresponding source was determined. If the billed expenditures are older than the number of residence periods, the original expenditure is set equal to the total of billed and rejected expenditures. If the expenditures are younger than the number of residence periods, or of the system cannot determine a valid entry in the residence times, the original expenditure is 0 and the expenditures are suggested as credit memos for billing.

When you archive the CO line items with the archiving object CO_ITEM the residence times are evaluated as well. The archiving program makes sure that CO line items are archived only after the specified residence times for the sources "actual cost line items" and "statistical key figures of line items" have expired. (This is not valid for plan line items.) Note that the archiving object CO_ITEM does not differentiate between actual costs and statistical key figures when taking residence times into account. If a residence time is specified for both sources, the larger of both residence times is used for actual costs, as well as statistical key figures. If only one residence time is specified for one of the two sources, it is used for both sources. The residence times specified here work with the residence times for the archiving object CO_ITEM (transaction and table ARCU_COIT1) in a way so that in doubt, the lesser number of line items is archived. To avoid confusion, you should keep the residence times specified for both tables synchronous.

Business Attributes
ASAP Roadmap ID 105   Define functions and processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_OLPR_ODP5 0 HLA0100702 Revenues and Earnings 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
AD01SRCARC S - Table (with text table) ODP5  
History
Last changed by/on SAP  20020208 
SAP Release Created in 470