Ansicht
Dokumentation

FVVI_RESUBMIT - Define Rules for Resubmission

ROGBILLS - Synchronize billing plans   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

When processing the Real Estate general contract, you can enter rules governing when the contract should appear for resubmission. For more information, refer to the application documentation.

SAP provides five sample resubmission rules:

1. S01: Resubmission on start date

The contract is resubmitted once on the start date specified in the rule.

1. E01: &1 Months before contract end

The contract receives a resubmission date a given number of months (specified in application) before the end of the contract (for fixed-term contracts).

1. R01: As of date &1 every &2 months

The contract receives dates for periodic resubmission: starting on a date you specify, and recurring at the interval of months specified.

1. R02: &1 Months/&2 days before renewal
2. R03: &1 Months/&2 days before notification of renewal

Depending on the data in the date overview, the contract receives one or more resubmission dates. R02 calculates the dates based on the 'New End' date; R03, on the other hand, calculates from the notification date. You can also specify if the system should consider renewal dates on which an action was already taken.

Example:R02/R03, each with 1 month and 0 days

End of rental is initially set for December 31, 2002. The contract can be renewed automatically, without notification being required, for another 6 months. There is also an option allowing renewal of the contract by 1, 2 and 4 years (in that order), with 3 months notification. You have not yet taken advantage of any renewal dates.

Based on the settings for renewal, the following date overview for renewal results:

New	Notification	Resubmission	Resubmission
End	Date	R02	R03
06/30/2003	12/31/2002	05/31/2003	11/30/2002
12/31/2003	09/30/2002	11/30/2003	08/31/2002
12/31/2005	09/30/2003	11/30/2005	08/31/2003
12/31/2009	09/30/2005	11/30/2009	08/31/2005

11/30/2009

11/30/2009

In order to define your own additional resubmission rules, follow this procedure:

1. Step 1: Specify rules
1. Choose New Entries on the level of the resubmission rules.

Enter a key beginning with Y or Z, and a helpful description of the rule with a variable.

Example:

You want the resubmission to take place a certain number of months after the start of the contract. You want the user to be able to enter the number of months for the rule later in the master data dialog. Enter this description for the rule: "Resubmission &1 months after contract start." &1 is a placeholder for the value that the user enters in the application.

1. Choose the Parameter for resubmission activity for the rule and then choose New Entries.

Specify a parameter category and the description. For the example described in point 1, you would choose "Months" for the parameter category.

1. Step 2: Program logic for the rules

In order to be able to use the new resubmission rule, you have to:

• Program your own logic in a function module and

• Save the execution of the function module by activating the user exits in BTE

Proceed as follows:

• In the Customizing activity in step 2, choose: Program logic for the rules. This takes you to transaction FIBF, where you can maintain Business Transaction Events (BTE).

• First you should find out what the interface of the function module you have to program needs to look like. To do this, choose Environment -> Infosystem (Processes). Enter 00708010 as the process interface, and execute the report. The row "00708010 User-defined resubmission" appears in the list. Use the pushbuttons to access the documentation and the sample function module.

• Copy the sample function module (to customer name range) and program your own logic for the resubmission in this copy. You can find example rules in function group FVRS03.

• Activate the BTE as described in (Business Transaction Events).

11/30/2009

BAL_S_LOG - Application Log: Log header data   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 6328 Date: 20240523 Time: 220235     sap01-206 ( 101 ms )