Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ ME0C (Package) Customizing R/3 Purchasing
IMG Activity
ID | SIMG_OLMEOM1R | Maintain Periodic Invoicing Plan Types |
Transaction Code | S_ALR_87002129 | IMG Activity: SIMG_OLMEOM1R |
Created on | 19981222 | |
Customizing Attributes | SIMG_OLMEOM1R | Maintain Periodic Invoicing Plan Types |
Customizing Activity | SIMG_OLMEOM1R | Maintain Periodic Invoicing Plan Types |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_OLMEOM1R |
In this step, you define the periodic invoicing plan types by specifying the relevant control data for each desired instance.
At the time of purchase order processing - on the basis of certain rules for data determination - the invoicing plan type suggests data such as the duration of an invoicing plan, from which the relevant dates of the plan can be determined.
Among other things, the periodic invoicing plan type includes the following control data:
- Horizon
In the case of periodic invoicing plans, the horizon specifies the last date up until which dates are generally to be set. It is always determined from a rule that can be entered in the invoicing plan type as a default value. This rule takes the current date (=CPU date) as the base date. As a result, the horizon is continually extended into the future as the current date changes over time, which means that the invoicing dates to be set are also dynamically shifted into the future.
- Dialog purchase order
This field allows you to determine whether the invoicing dates are determined and inserted into the invoicing plan automatically, or whether they must be entered manually.
- In advance
Here you determine whether the invoice is to apply retrospectively or in advance - for example, whether a rental payment due on June 15 is to cover the period May 15 to June 15 (retrospective payment) or the period June 15 to July 15 (payment in advance).
Activities
- To create an invoicing plan type, you must enter an alphanumeric key of max. two characters in length, plus a descriptive text.
- Maintain the relevant control data on the detail screen for the invoicing plan type.
Example
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 3 | Nonrequired 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_OLMEOM1R | 0 | HLA0006033 O | |
SIMG | SIMG_OLMEOM1R | 1 | HLA0006041 | Purchase Orders |
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 |
V_MTFPLA | V - View | SM30 | 0000000001 | Maintain Invoicing Plan Types: Periodic Invoices |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |