Kontakt

Ansicht
Dokumentation

SF1080 and SF1081 (Changed) ( RELNPSM_603_FMFG_SF108X )

SF1080 and SF1081 (Changed) ( RELNPSM_603_FMFG_SF108X )

BAL_S_LOG - Application Log: Log header data   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

SF1080 and SF1081 (Changed)

Use

As of SAP ECC 6.0, Enterprise Extension Public Sector Management (EA-PS 603), Enhancement Package 3, the Federal Government solution includes changes to the SF1080 and SF1081 reporting process. An agency can use these reports to provide Treasury with cash movement information between one agency and another (SF1081) and movements between one appropriation and another (SF1080). This report is used in the absence of the automated IPAC (Interagency Payment and Collections) reports/files.

There are several components in the SF1080 and SF1081 process:

  • Create the SF1080/SF1081 output documents (transaction F110)
  • Reverse SF1080/SF1081 confirmed payment document (transaction FMFG_SF108_REV
  • Creation of the SF1080/SF1081 output documents (transaction F110)
  • SF1080/SF1081 processing involves the following payment methods:

  • Outgoing SF1081

  • Outgoing SF1080

  • Incoming SF1081

  • Incoming SF1080

Accounts Payable or Accounts Receivable invoices are posted in the system with their applicable payment method. The invoices have been paid through the payment program and the generated payment documents have check numbers assigned to them. In addition to the check number, the payment program produces SF1080 and SF1081 output documents, which have the relevant check number printed on the top right-hand corner. The SF1080/SF1081 forms are given to the partner/reciprocating government entity for approval.
If another copy of the SF1080/SF1081 is required, transaction FMFG_SF108_REPRNT can be used to print out the document(s). This transaction calls program SAPFPAYM_SCHEDULE and you must enter the payment run date and payment run ID in the run time parameters.
Use this transaction (rather than the standard FI reversal transactions) if the payment document needs to be cancelled prior to confirmation. It calls transaction FCH8 "Cancel Check Payment" and voids the check on the payment document, resets the clearing, and reverses the payment document. The invoice is marked as 'open' and can be included in subsequent payment runs.
If the partner agency approves the SF1080/SF1081, the confirmation process can be performed. Transaction FMFG_SF108_CONFRM is run (this transaction calls SAP standard transaction FCHR "Online Cashed Checks"). The FCHR "Online Cashed Checks" function is equivalent to the US Federal Confirmation. The confirmation process clears the DIT line item on the Payment Document and mark the check as "cashed" in PAYR. The clearing document posts to the FBT GL Account. The FBT GL Account is retrieved from the SAP Bank Account (also known as the Account ID). This results in an FI clearing posting of DR Disbursement In Transit (DIT) / CR Fund Balance With Treasury (FBT).
  • Reversal of SF1080/SF1081 confirmed payment document (transaction FMFG_SF108_REV)
Run this transaction to reverse the confirmed payment. The transaction calls program RFFMFG_SF108_REV, and you then have the following options:
- Reverse the clearing document only
The clearing/confirmation document is reset and reversed and the 'check encashment date' (BANCD) and the 'paid' indicator (XBANC) are deleted from PAYR table. The payment document is open and the check attached to it remains intact and uncashed. The payment document can be confirmed again.
- Reverse the clearing document and the payment document
In addition to the clearing/confirmation document being reset and reversed, the check is marked "void" and the payment document is reset and reversed. The invoices are open and ready to be paid again through the payment program.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

  • Define House Banks and Bank Accounts (transaction FI12). The FBT GL Account is stored on the Bank Account. In most cases, one bank account is sufficient for the SF1080 and SF1081. This GL account will be used during the SF1080/SF1081 confirmation process (which is using the standard SAP online cash check clearing program).
  • Payment Methods per Country for Payment Transactions
To segregate check lots and cash flow direction, four payment methods are required for the SF1080/SF1081 processing. They are:
  • Outgoing SF1081

  • Outgoing SF1080

  • Incoming SF1081

  • Incoming SF1080

For the SF1080/SF1081 payment methods, a single payment per invoice is recommended. This means that each invoice has its own payment document when it is paid using the payment program. Attach each payment method to a Payment Medium Form. For the SF1081 the PDF form is RFFMFG_SF1081_PDF and for the SF1080, the PDF form is RFFMFG_SF1080_PDF.
For the SF1080/SF1081 payment methods, assign the house bank and account ID (bank account) to a "bank subaccount" (GL account that represents the DIT account). This is the GL account to which postings are made when the payment run is processed.
Configure two check lots for each bank account ID - one for SF1080 and one for SF1081. Each check lot should be assigned to its respective payment method (one for SF1080 and one for SF1081). The check number generated using the F110 payment program is printed on the SF1080/SF1081 output forms; it is a 'pseudo' check number, used for identification purposes only.
The SF1080 / SF1081 reversal program (RFFMFG_SF108_REV) has a run time parameter for the 'void' reason code. When the program is executed if the second option is selected to "reverse / reset both clearing and payment documents", the check is marked void and the payment document is reversed. Note that, once the payment is reset and reversed, the voided check is attached to both the payment document and its reversal.
  • Create Payment Medium Format Variant (transaction OBPM4)
SAP supplies two Payment Medium Formats: SF1080_US_FEDERAL and SF1081_US_FEDERAL. The Payment Medium Format tells the payment program which PDF output form to use.
  • Payment Medium Format SF1081_US_FEDERAL is linked to PDF output form RFFMFG_SF1081_PDF

  • Payment Medium Format SF1080_US_FEDERAL is linked to PDF output form RFFMFG_SF1080_PDF

Each Payment Medium Format format must be assigned a variant (transaction OBPM4). The variant provides run time parameters for print the program SAPFPAYM. This print program creates the PDF output for SF1080 and SF1081. Each format is linked to an SAP supplied function module (see below).
Background Information
Each supplied Payment Medium Format is assigned to a Business Transaction Event (in particular, event number 30 which is called for each record). The function modules build the content of the SF1080 / SF1081 forms and place the data into internally defined structures. The data/structures flow through to the print workbench (using the application form) and then to the PDF output. Below is a list of each Payment Medium Format and its associated function module:
  • Payment Medium Format SF1081_US_FEDERAL is linked to function module FI_PAYMEDIUM_1081_FG_PDF_30

  • Payment Medium Format SF1080_US_FEDERAL is linked to function module FI_PAYMEDIUM_1080_FG_PDF_30

SAP supplies the following Print Workbench components:

  • Two form classes - called FM_1080 and FM_1081

  • Two PDF forms - called RFFMFG_SF1081_PDF and RFFMFG_SF1080_PDF

The form classes are linked to the PDF Forms by means of an application form. The implementation team must create two application forms - one for the SF1080 and one for the SF1081. This is done in Customizing by choosing Cross Application Components -> General Application Functions -> Print Workbench -> Define Application Forms (transaction EFRM)

When creating each Application Form, identify the form class, the form type as 'PDF' and the name of the PDF form, as follows

  • Application Form SF1080 - Form Class FM_1080 and PDF form RFFMFG_SF1080_PDF
  • Application Form SF1081 - Form Class FM_1081 and PDF form RFFMFG_SF1081_PDF

Implementation of BAdI to determine the Application Form and default printer (IMG Activity PWB_EFG_PRINT_PARAM) takes place in Customizing. Choose Cross Application Components -> General Application Functions -> Print Workbench -> BAdI: Override Default Print Parameters

The enhancement in this BAdI is called EFG_PRINT_PARAMS. The implementing interface is called IF_EX_EFG_PRINTPARAMS. The method where the code should be placed is called IF_EX_EFG_PRINTPARAMS~CHANGE_IN_PRINT_EXPANDED

Further Information






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 12463 Date: 20240523 Time: 055129     sap01-206 ( 198 ms )