Ansicht
Dokumentation

SAPF120 - Create Posting Documents from Recurring Documents

SAPF120 - Create Posting Documents from Recurring Documents

RFUMSV00 - Advance Return for Tax on Sales/Purchases   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Description

This program manages the recurring entry original documents created online. It does the following:

  • Selects the recurring entry original documents for which actual accounting documents need to be created.
The recurring entry program selects the recurring entry documents for which the next run date is the same as the date of the settlement period or falls within the interval specified for the settlement period. It does not include recurring entry original documents that are marked for deletion.
  • Creates a batch input session containing the data transferred from recurring entry original documents (which may have been changed or enhanced by the program) to generate the accounting documents and update the recurring entry original documents
  • Marks for deletion those recurring entry original documents for which the next run date determined by the program exceeds the last run date. In the case of an individual run schedule, the program also marks for deletion any recurring entry original documents for which it cannot determine a run date falling after the current run date.

You do not have to make a data backup in case a restart is necessary. The program does not make any changes to the database and can be restarted.

To post the accounting documents and update the recurring entry original documents, you have to process the batch input session created by the recurring entry program. If, during processing of the batch input session, errors occur that prevent the system from creating an accounting document or updating the recurring entry original document, the entire transaction (document creation and the update of the recurring entry original document) is terminated.

The current design of this program does not fully support - or may not support at all - recurring entries or postings in connection with Sales and Distribution, Assets Management, and Cash Management.

Requirements

In the details of a recurring entry original document, you have to specify when each actual accounting document is created from that recurring entry original document. You specify either an interval in months or a run schedule. The run schedule needs to be defined in the system settings in Accounting.

Check whether this prerequisite has been met.

If program SAPF120 has to be updated, your system administrator can do this by running programs SAPF120G and SAPF120R. An update may be necessary if changes have been made to the posting screens.

Program SAPF120R is used as a template for SAPF120. Program SAPF120R is not intended to be executed directly.

Note

If you enter only part of the total run period in the run schedule, you need to enter the additional run dates in the run plan before or once the last date specified in the schedule is reached.

If a recurring entry original document needs to expire after a given period of time, you need to ensure that the last run date in the run plan falls after the last run date in the recurring entry original document. If, in the case of a recurring entry original document with a run plan, the program cannot determine a run date falling after the current run date, the recurring entry original document is marked for deletion. In this case, the program issues a message telling you to check the recurring entry original document or the run plan. You can then correct the dates in the recurring entry original document or its run schedule and reset the deletion indicator in the recurring entry original document. If you want to continue executing this recurring entry original document, you may need to repeat the program run (for creating accounting documents from recurring entry original documents) that issued this warning. If a batch input session was created in the first program run, you need to process it beforehand to avoid duplicate selections.

The system automatically derives date details from the automatically updated date details in the recurring entry original document. This is the case for the value date, for example. If you want to change the dates that are updated automatically for just one recurring entry program run, you need to remember to change the dates back after running the program. If you postpone the next run date, this may cause one or more run dates to be skipped. However, you can also correct this manually.

If you use selection criteria that overlap in two or more batch input sessions, make sure that the next session relating to the same settlement period is not created until after the preceding session has been processed.

Example:

Selection Session 1 Session 2
Company Code 0001 0001
Document Type SA SA
Next Settlement Date
of 0107yyyy 0107yyyy
to 1507yyyy 3107yyyy

If you fail to do this, the program selects recurring entry original documents for the same settlement period multiple times and places the documents of the same name in the batch input sessions. Generally, this does not cause duplicate documents to be posted. However, in some cases, errors occur when sessions are processed later on and an accounting document already exists for the settlement period and respective recurring entry original document. However, if between posting two overlapping sessions you manually bring the new run date forward in the recurring entry original document, it is possible that duplicate documents are posted. The only way to check this is by checking the accounting documents and the number of times the recurring entry original document was executed.

If the Expiring Currencies function is activated, program SAPF120 selects all recurring documents for which the next run date falls in the settlement period. Recurring documents that contain "SAPF121" in the document header text and those with a currency that would be replaced on the run date (corresponding to the date stored for the follow-on process SAPF121) are not processed.

Output

You can use the the following selection criteria to limit the number of recurring entry original documents for settlement:

  • Company Code
  • Document Type
  • Settlement Period
  • Run Schedule

As long as at least one recurring entry original document is selected, the program creates a batch input session. You can enter a name for the batch input session in the appropriate field.

You can also make the following settings for processing the batch input session:

  • You can specify a user name for authorization checks.
  • You can set a lock date for the batch input session if you do not want it to be processed immediately.

The remaining topics of this document explain which data is not taken from recurring documents, which data is changed, and which is updated when data is placed in a batch input session, accounting documents are created, and the recurring entry original documents are updated.

Creating Accounting Documents

  • The number of the recurring entry original document is entered in the document header of the accounting document created.
  • The posting and document date of the accounting documents created are set as the current run date.
  • The posting period is derived from the posting date when the batch input session is processed.
  • Postings that contain terms of payment are assigned the baseline date for due date calculation on the basis of the terms of payment. Postings without terms of payment are assigned the document date as the baseline date.
  • In the case of postings that are part of payment transactions, a value date that you have entered or that the system has assigned is adjusted to the current settlement date. This adjustment is made as follows:
  • If you do not use a run schedule, the system always determines the date on the basis of the difference in days between the first run date (taking into account the day specified for running a recurring entry original document) and the value date in the relevant line item of the recurring entry original document.

  • If you do use a run schedule, the first run date is the value date.

If the value date is the last day of the month, the last day of the month is always used. The different last days of the month are used.
  • In recurring entry original documents that are part of payroll accounting and contain specifications on the payroll period, the system makes an adjustment for the current payroll deadline. It does this using the difference between the first payroll month and year of the recurring entry original document and the settlement period in the relevant line item of the recurring entry original document.
  • Postings in a foreign currency are translated into local currency amounts using the exchange rate stored in the system and valid on the settlement date.
  • If you have explicitly specified an allocation number in the line items of the recurring entry original document, the system copies it. Otherwise, it creates one.
  • With the current version, no data is transferred for the following fields relating to Cash Management and Assets Management:
  • Asset Retirement

  • Asset Transaction Type

  • Asset Value Date

  • Planning Amount in Document Currency

  • Planning Date

Updating Recurring Entry Original Documents

For all recurring entries, the next settlement date of the recurring entry original document is either determined on the basis of the the monthly interval and the run date or taken from the run schedule stored in the recurring entry original document. If, when specifying the month interval and run date, you have manually changed the settlement date so that it does not correspond with the (fixed) run date that either you have chosen or the system has assigned, the next run date is used as the run date again. You can execute recurring entries at the end of each month since the program can adjust for the different number of days in each month.

Examples:

Unchanged Changed
Current Settlement Period 15.03.yyyy 20.03.yyyy
Interval in Months 01 01
Run Date 15 15
Next Run Date Calculated 15.04.yyyy 15.04.yyyy
-----------------------------------------------
Current Settlement Period 31.03.yyyy 02.04.yyyy
Interval in Months 01 01
Run Date 31 31
Next Run Date Calculated 30.04.yyyy 31.05.yyyy

The number of times that the recurring entry original document was run is updated automatically with each posting.

A deletion indicator is set for recurring entry original documents for which the next settlement date determined by the program falls after the last settlement date or for which no date can be determined from the individual run schedule. The last "Next Run Date" is retained.






Addresses (Business Address Services)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 14096 Date: 20240520 Time: 073854     sap01-206 ( 241 ms )