Agenda

Introduction Interests

Master Data Installment Plans / Promise to Pay

Transactions Security Deposits

Documents Correspondence
Specific Posting Processes Integration Accounting
Payments and Clarification Invoicing

Payment Run and Transfers Overview Business Rule Framew.

Clearing Control / Ac. Maint. Financial Customer Care

Returns

Dunning
SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 1

1
 Specific Posting Processes

Contents:

Specific Posting Processes

Requests
Write – Off (Temporary Waiver)

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 2

2
 Specific Posting Processes: Unit Objectives

At the conclusion of this unit, you will

be able to:
Reverse documents
Post requests
Create documents from standing requests
Understand the functionality of general
requests
Write-off documents and view resubmission
cases in a clarification list

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 3

3
 Specific Posting Processes: Business Scenario

Your Public Sector Organization wants to post

requests and standing requests for receivables
collected on a periodic basis. Some incoming
revenues have to be written-off and should be
viewed in a clarification list.

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 4

4
 Specific Posting Processes I: Document Reversal

Prerequisites for document reversal

Resetting cleared items -- FP07

Documents can be reversed with the following processes:

Individual documents (not cleared) -- FP08

Mass reversal of documents -- FP08M

Mass reversal of BP, CA, contract

object items -- FP22

Return lot (discussed later in course)

Negative postings can be allowed at document type level:

Always post negatively

Only post negatively for corrections in the same fiscal year

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 5

Various document reversal options are available for specific business requirements:
Reversal of individual documents reverses single documents that are not yet
cleared or may be used to reverse all documents that contain the same document
reference number. You will get a pop-up with all cleared items that need to be reset
to reverse a document. In the pop-up you have got the possibility to reset the
documents.
Resetting of cleared items for individual documents is used to reverse a clearing
document’s effects.
Mass reversal of documents can be used to reverse all of the documents of a
reconciliation key. This may be used to reverse a payment run that was executed
by mistake.
Mass reversal of business partner, contract account, contract object items is used to
reverse all of the documents post against a particular master data object (I.e.
reverse all documents posted against BP Cummings). This program can reset
clearing and reverse documents in just one step.
Return lots are used to reverse payments that have been posted and subsequently
refused by a bank (I.e. account closed or check bounces). This topic will be
discussed in detail later in this course.
PSCD supports the concept of negative postings. A negative posting reduces the
transaction figures for the account posted to in the general ledger. It enables you to show
transaction figures for accounts after an incorrect posting and subsequent correction (for
example, invoice posting and reversal) as if neither the incorrect posting nor the
correction had taken place.
5
 Specific Posting Processes II: Transfer Items (FP40)

Transfer Items
Selection details
Business partner
Contract account
Contract object
Document number
Reference document #

Transfer Posting Target

Business partner
Contract account
Contract object
Details on reverse posting
Posting date
Currency USD
USD
Clearing reason 03
03
Transfer post reason 01
01
Document type 10
10
Reconciliation key

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 6

A transfer posting of receivables or credit is necessary if a business partner assumes the

rights and obligations of another business partner, such as in the case of inheritance.
From time to time it might also be necessary to transfer post receivables or credits between
different contracts or contract accounts of the same business partner. This is the case, for
example, if a customer terminates a contract, but the remaining receivables are to be
collected together with the receivables for the new contract object.
In transfer posting, the transferred items are cleared and a new open item is created of each
item under the transfer posting document number. The new items only differ from the original
items in their origin and posting date. The receivables account, due date, transaction name,
and dunning and interest information remain the same for these items.
You can transfer post the following: single items, all items of a business partner, all items of
a contract account, all items of a contract.
NOTE: You can only transfer post open receivables or credits. Before you transfer post the
items you can check and - if necessary - correct the posting specifications. Then you push
the button “Select Items”, activate the items and save.
In the Transfer of Open Items (menu: Account Transfer Items ), you can define
transactions for the transferred items. The system does not carry out a new account
determination for this, but, for example, you can make the account balance display easier to
read since the transferred items can now be recognized directly from the transaction or the
transaction text.

6
 Request - Overview

Request

Release
Request * Status: released
- Worklist
- Workflow

Standing Release
FI-CA-
Request - Worklist
Status: released Debit/Credit
Doc. FI
- Workflow

General Release
Request Status: released Debit/Credit
- Worklist
- Workflow

Incoming
Payment
* Payment Request, Acceptance Request

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 7

Requests can be used to post outgoing and incoming invoices.

If you want to introduce the dual-control principle for requests in your organization, you
can trigger a workflow when an approval is required to create, change or reverse a
request.
As soon as a request is released, a FI-CA document is created. The result is a request-
document and (a) regular FI-CA document(s).
You can choose whether the FI-CA document should be created directly or in a separate
step. To do this, you can use the function “Generate Documents from Requests”.
Requests are classified by the following request classes, which cannot be changed:
Request
Standing Request
General Request
The request category differentiates between acceptance request and payment request.
As of ERP2005 you can now define request categories in Customizing as you wish. You
can select which sign (plus/minus) and which document type the generated documents
should have for each request category and whether a document should be generated for
each request item.
You can go to the list of requests from the request processing transaction where you can
see documents already posted for a request. You can also go to the corresponding
request from a contract accounting document.

7
 Acceptance- and Payment Request

Acceptance-
Acceptance -Req.
Acceptance-Req. One-
One -Screen
One-Screen
Payment-
Payment -Req.
Payment-Req. Transaction
Transaction

Derivation
Derivation of
of FM-
FM -Data
FM-Data -- Worklist
Worklist
Linebased
Linebased entry
entry from
from main/sub
main/sub -- Flexible
Flexible release-
release--
release
transaction
transaction or
or CO-
CO--
CO workflow
workflow
accounts
accounts
SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 8

The transaction for processing requests is an one-screen transaction.

In the upper area of the request, you can choose, if you want to create a new request or if
you want to display an already created request. A request can be created with a template.
You have to tell the system which request category you want use.
In the middle area you can enter the header data of the request, including the data you
can see in the FI-CA document header, such as the document date and the document
type.
In the lower area the request items are entered.
In contrast to creating a FI-CA document, editing a request is line-based. That means,
that in one line you can find the Business Partner data as well as the GL-data. The
assignment between BP-data and GL-data is always unique. Mandatory fields are
company code, business partner, contract account, contract object, main and sub-
transaction, net due date and amount. GL-accounts, FM-Data and CO-Data are derived.
With customer enhancements in Event 6050 it is possible to derive FM-Data from
entered CO-Data. Generally you can create a request for several business partners and
several company codes.
You can create a request template and thereby reduce the amount of entries you have to
make, if you must always enter similar requests. When you create a new request, you can
use this template by calling the function Create Using Template. When you create a
request using a template, you can use existing requests as well as request templates.
Because of this, you cannot create a request with reference to another request.

8
 Standing Request - Overview

Header Data

Document Date 02/15/2008

02/15/2008
Posting Date 02/15/2008
02/15/2008
Document Type DR

Execution Data
Execution Period 001
001
Due date
First Due Date 02/15/2008
02/15/2008 Last Due Date 02/15/2010
02/15/2010
period
No End Date
Due date Special
Frequency monthly Interval 01
01 SpecialDate
Date
frequency
Request Item 02/15/2002 To 02/15/2003
- Adding Dates BPartner Mtrans SubTrans Amount Item Text
Contract
- Excluding Dates BP1 501001234567 4030 0100 100,- Rent

FI-CA-Doc.
BP1 100,-
05/15/2008

06/15/2008
SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 9

Standing requests are an efficient tool, to create PSCD documents on a periodic recurring
basis.
A standing request is a template, which contains all relevant data, to create PSCD
documents periodically.
You can create standing requests for acceptance requests and payment requests.
In the run data you enter the first and the last due date, or you define that there is no end
date.
Additionally you have to insert a frequency (e.g. monthly) and based on the frequency an
interval (02 stands for every two months).
So far, SAP supports the following frequencies:
Daily
Weekly
Monthly
Monthly, on last day
Annually
You can exclude or add special dates by the functionality ‚Special Date‘.

9
 Standing Request – Changes: Versions

BPartner Contract Mtrans SubTrans Amount Item Text

BP1 501001234567 4030 0100 500,- 1st Rate
First Version Run Data – Version 1
First Due Date 02/15/2008
02/15/2008 Last Due Date 02/15/2010
02/15/2010

BPartner Contract Mtrans SubTrans Amount Item Text

BP1 501001234567 4030 0100 100,- Rent
Current Version Run Data – Version 2
First Due Date 03/15/2008
03/15/2008 Last Due Date 02/15/2008
02/15/2008
05/15/2008
05/15/2008

BPartner Contract Mtrans SubTrans Amount Item Text

BP1 501001234567 4030 0100 150,- Adjustment
New current version
Run Data – Version 3
First Due Date 06/15/2008
06/15/2008 Last Due Date 02/15/2010
02/15/2010

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 10

You can change standing requests by creating a new version for a standing request.
The versions can differ by run data and/or accounting data regarding one standing
request.
The due date period in the run data of the different versions must not overlap. In case the
run data of two different versions is overlapping, one version has to be changed.

10
 Standing Request – Creating Documents

Periodic Mass Run

Standing Request FI-CA-Documents

FPDUDC
Req. No. 4711
4711
BPartner BP1
BP1 Due Date incl. 04/15/08
04/15/08
Doc. No. 1100012
1100012
Amount 100,-
100,- From Req. No. 4000
4000
BPartner BP1
BP1
First Due 02/15/08
02/15/08 To Req. No. 5000
5000
Amount 100,-
100,-
Last Due 02/15/10
02/15/10
Due Date 02/15/08
02/15/08

Update History

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 11

Using the transaction Generating Documents from Standing Requests, you can create
PSCD documents on regularly recurring dates.
You can do this by using the mass activity. You can enter a date until which documents
should be created from the standing requests. You can limit the standing requests that
should be included in the processing according to business partner, contract account or
contract. You can also select by standing request number for the processing.

11
 General Request – Business Scenario

Bank Statement
Transactioncode: Direct Debit
Sold-to-Party: TELEKOM
Bankkey: 10020030
Bank Account: 12345
Note to Payee Telekom
Telekom
Connect. 987654
(2) 80,-- 80,-- (1)
---- -----------------
--------- ---- ---- -

Bank

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 12

You use general requests when you expect the same type of revenues or expenditures,
but their amounts are not yet fixed.
For example, you can enter general requests for the revenues using administrative and
usage charges or a general payment request for telephone charges.
The general request simplifies the administrative process because a payment can be
made without there being a concrete payment request in a particular case. You can also
use to represent the participation in debit memo transactions.
You can incorporate a workflow for the approval of general requests.

12
 General request

Allgemeine Anordnung Intern/Extern

Intern/Extern (Customizing)
(Customizing)
Request Number
Request Category Acceptance/Payment
Acceptance/Payment Request
Request

Header data
Posting Date Doc.type Created from
Reference Created at
Status Differentiation
Differentiation of
of documents
documents

Request items
Account Assignm.
BPartner ContractAcc. Contract MTrans. STrans. FM GL/Acc. CO TaxCode Valid to

IfIf Businesspartner
Businesspartner unknown:
unknown: Per
Per line
line unique
unique contract
contract object
object Validation
Validation date
date for
for
Dummy
Dummy BPartner
BPartner general
general request
request

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 13

13
 General Request - Payment

Incoming Payments Account Balance

(View: detailled payment list)
1001 Payment Lot
XYZ 200-
Electronic Bank Statement
Note to Payee Payment on Account
XYZ
Account DocNo. MTrans STrans Amount
Amount 200 1000 1001 0050 0100 200-

Payment Lot

XYZ Payment Document

Doc. Header DocNo. 1001
General Request
BPartnerposition
Doc. Header Doc.No. 0815
Ccode BPartner C.Acc. Contract M/Strans Amount
0001 1234 1000 XYZ 0050/0100 200-
Request Items
GL/Position
Pos. CompCode BPartner Contr.Acc. Contract
CompCode GL/Acc. Amount
1 --- --- --- ---
0001 1234 1000 XYZ 0001 113109 200
2
3 --- --- --- ---
SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 14

In the case of incoming or outgoing payments using electronic account statement or cash
desk, the system recognizes that the payment is made due to a general request.
The payment is first posted as a payment on account as a payment without debits.
So that the system can recognize that the payment is due to a general request, it saves
the combination main transaction 0050 / sub transaction 0100 as soon as a payment can
be assigned to a general request.
The system determines the main and sub transaction that were actually saved in the
payment document from the IMG activity Assign External Transactions.
For the master data the system transfers the account assignments from the general
request in this process.
You can set whether the system should assign the general requests using the contract
object or the classification key for incoming and outgoing payments.

14
 General Request – Creating invoices

Periodic Mass Run

General Request
OGRM3
Req.No. 4711
4711
BPartner GP1
GP1 GP1
GP1
Contract XYZ
XYZ From Req.No. 4000
4000
(2) 200,- 200,- (1)
To Req. No. 5000
5000

Update History

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 15

If you want to generate debit entries for payments made on general requests, select the
function Generate Documents for General Requests.
The system automatically clears the contract accounting documents with the payments
according to the Customizing settings.
You can list all relevant documents in order to check the funds consumption on general
requests.

15
 Worklist: Approve Requests

Selection
Clerk Mode
Administrator Mode
FKKORDA
Resubmission Cases

In Process by me
In Process by other user
Resolved Worklist: approve requests
Locked resubmission by me
Status Status Name Request No. Amount User Resub. Date
Approved
Rejected In process 2424 1000.00 TRAINING 08/15/2010
Cancelled
Deleted

New
Resubmission
Date Clarify Lock Set Clar. Case for Change
Unlock Resubmission Status/User
Approve
Reject

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 16

You can approve requests by using the workflow or by using a worklist.

You define which classes and categories of requests should be approved through a
worklist in Customizing.
Event 5510 was enhanced for a customer-specific differentiation between approval by
worklist or by workflow. You can also suppress the entry of an approval reason for event
5510 when starting the workflow.

16
 Requests: Special Features

Print requests – correspondence type 0039

Enter notes (copied into the documents)
Set payment, dunning, interest and clearing blocks (copied
into the documents)
Create one document for each request item
Enter tax code containing several tax rates
Enter a classification key in request items
Display requests in account balance
Approve requests not only with workflow, but also with a
worklist
Use BAPIs to process requests

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 17

For requests, standing requests and general requests…

You can print requests. All header data on the request and all request items with additional
information on the business partners and contract accounts are available for the printout of a
request. All execution dates and special dates are also available for the printout of standing
requests.
You can enter notes for requests. If you generate documents from requests, the notes are
copied over into the notes on the documents.
You can set payment/dunning/ interest and clearing blocks for request items that are copied
into the documents when the documents are generated. You can enter a block reason and
validity period for each request item and block.
If you create requests with lots of lines and in some circumstances several business partners
and contract accounts, this can cause quite a number of documents that can no longer be
represented clearly. For this reason, you can generate documents from requests for each
request item. You define the corresponding specifications for requests for each request
category in Customizing.
You can also enter requests with a tax code that contains several tax rates. The calculated tax
amount that is displayed in the request item is determined from the total of amount of the
individual tax rates.
You can enter the new field Classification Key in the request items if you have activated the
standard enhancement for the classification key. As the classification key is a header field of
the document you can only enter different classification keys in a request if you generate
documents for each request item.
By defining corresponding function modules for events 1203, 1209 and 1211 you can display
requests in account balance. SAP provides function modules FKK_EVENT_1203_REQUEST,
FKK_EVENT_1209_REQUEST and FKK_EVENT_12011_REQUEST for this that you can
define for the events mentioned or use as templates for your own function modules .
Until now you could only approve requests through workflow. You can also approve requests
using a worklist. You define which classes and categories of requests should be approved
through a worklist in Customizing. Event 5510 was enhanced for a customer-specific
differentiation between approval by worklist or by workflow. You can also suppress the entry of
an approval reason for event 5510 when starting
17 the workflow.
 Requests: BAPIs

BAPI_REQUEST_ADDLINEITEMS BAPI: add line items in request

BAPI_REQUEST_ADDPERIODS BAPI: add periods in request

BAPI_REQUEST_ADDSPECIALDATES BAPI: add special dates in request

BAPI_REQUEST_CHANGE BAPI: change request

BAPI_REQUEST_CREATE BAPI: create request

BAPI_REQUEST_DELETE BAPI: delete request

BAPI_REQUEST_DELETEPERIODS BAPI: delete periods in request

BAPI_REQUEST_DELLINEITEMS BAPI: delete line items in request

BAPI_REQUEST_DELSPECIALDATES BAPI: delete special periods in request

BAPI_REQUEST_EASYCREATE BAPI: create request with template

BAPI_REQUEST_GETDETAIL BAPI: read request

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 18

18
 Customizing
IMG

Request Class Request Category Number Range

Request Payment Request 01

Request Category Doc. Type

Payment Request KR

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 19

In Customizing you have to define a number range per request class and request
category.
Furthermore you have to configure a document type per request category, which can be
used as default value.
For general requests a new IMG activity has been added to Customizing of Contract
Accounting.
You can find this IMG activity under Define Specifications for Clearing Documents for
General Requests.
You can define specifications for clearing documents here.
If you want the system to clear the contract accounting documents automatically with the
payments, you have to select the relevant field in the IMG activity Define Basic Settings
for Document Creation.
As of release ERP 2005 you can define request categories in Customizing as you wish.
You can select which sign (plus/minus) and which document type the generated
documents should have for each request category and whether a document should be
generated for each request item.

19
 Write-Off (FP04)

Selection Details Total/Partial Contract Account

BPartner BP1
BP1 Write-off
Contract Acc. RITEOFF
RITEOFF W.
W. Riteoff
Riteoff
Contract (1)100,-- 80,-- (2)
W/o
Document No.
Resubmission date
Reference

Specifications for Write-Off FI GL-Accounts

Posting Date 04/15/2008
04/15/2008
Clearing Reason 04
04 Write-Off Write-off items/ Property
Property Tax
Tax
Write-Off Reason 02
02 Waiver Write-off Mass run 100,-- (1)
Resub. Date

Write
Write -- Off
Off
Account
(2) 80,--
Determination
Note

IMG
Events : P730, P731
SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 20

It is possible to write-off debit or credit items within PSCD.

Special revenue and expense accounts for write-off postings can be defined in
customizing. Depending on the write-off reason you can define, that for the write-off the
same account assignment is used as in the written off document.
If you want to waive partial amounts of open receivables due, you assign the partial amount
to be written off in the transaction “Write Off Items” (FP04).
You have to explicitly permit partial write-offs. To do this, set the indicator PW/O (Permit
Partial Write-Off) in the Implementation Guide for PSCD under Business Transactions
Write-Offs Define Write-Off Reasons.
To limit temporary waivers, you can enter a resubmission date on the selection screen. You
can define that the resubmission date in the transaction “Write-Off Items” appears as a
required field.
In the transaction Write Off Items, you can enter notes for a write-off document created.
Extras Notes Enter Notes.
After writing off, you can print the information of the write-off document and the written off
items. The data of the write-off document, the cleared items and the data entered during
the write off with additional information on the business partner is available for this. You
generate and print the write-off data using the events P730: Print Write-Off Data and P731:
Generate Write-Off Data. Correspondence type P034 Write-Off Data is used and uses the
form class FMCA_WRITEOFF_DOC. SAP provides the sample form
FMCA_WRITEOFF_DOC_SAMPLE_SF.
Transaction FPZW “Adjust Receivables” allows you to write off a percentage of an item.
20
 Writing-off Open Items: Customizing Defaults
IMG

Maintain clearing specifications and default values

Function
Check level 04
04 Contract
Currency USD
USD
Default values that can be
Clearing reason 04
04 Clearing
overridden at time of execution
Document type 92
92

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 21

When customizing default specifications for writing-off items, you define at what ‘check
level’ write-off rules are to apply; the possible levels are at document, business partner,
contract account. For example, if charge-off rules are defined to apply at check level
‘contract account’ then rules will be applied to each contract account individually.
Other customizing areas within the IMG for write-offs include defining allowable charge-off
reasons and automatic G/L account determination (definition of the revenue and expense
accounts to be posted to when executing charge-off function).
The above displayed defaults are set for posting areas 1052 and 1053 (mass processing)
that are relevant for write-offs. For mass processing the default clearing reason should be
‘14’.
As of release ERP 2005, you can also perform write-offs in external systems. You can
activate the function in posting area 0124. If you perform write-offs in an external system,
line items that are posted in PSCD via this external system are forwarded to the relevant
external system via the Outbound Interface for Business Partner Items. The SAP system
(PSCD) denotes the items to be written off with the clearing restriction T. This means that
these items cannot be cleared by other business transactions. The tax calculation takes
place in the external system. The data determined for the calculation of the write-off
document is posted in the SAP system (PSCD) again via the Bill Line Item Interface. The
pre-selected items that are to be written off are cleared and the clearing restriction T is
deleted.

21
 Writing-off account determination: Customizing

Application area P Public Administration

Posting area P030 Additional Specifications for Write-offs and Mass Write-offs

Account determination

Write-off reason Doc. type CO acct.assign. Resubm. date FM acct.assign. from Transf. G/L acct
AB DG 1 x x
P2 DG 1 x
P3 DT 1 x
P4 DG 1
P5 DG 2 x
P6 DG 2 x
CO account assignment : FM account assignment :
„ „ = GL account cost type „ „ = Derivation from account determination of writte-off doc.
1 = Item to be written off (inheritance) X = Inheritance from item to be written-off
2 = Account assignment determination

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 22

In posting area P030 you must define the derivation of CO account assignment data and
FM account assignments separately as of Release ERP 2005. The field “FM Account
Assignments from” has been introduced for this where you can define whether the
derivation should occur from the account determination or from the items to be written off.
In posting area P030 you can define that the CO account assignments from the items to
be written off are inherited. This setting replaces the derivation of CO account
assignments from the account determination of the item to be written off.
Furthermore you can define that the G/L account of the write-off document is derived with
event 5030 from the date of the open item and that the specification from posting area
0120 is overwritten. The standard function module defined with event 5030 has been
enhanced accordingly.

22
 Petty Amount Limits in Write-off Run

Dunning Dunning Account Main Sub Curr. Under- Over- No Future

Level Proc. ID Trans. Trans payment payment Due Date
01 4010 0100 USD 10,00 10,00
01 4030 0100 USD 5,00 10,00

VK1
VK1
(1)100,-- 96,-- (2)

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 23

In order to avoid non-financial enforced collection procedures, an organization can

dispense with entitlements under a certain amount limit. In the write-off run you could
previously enter an amount limit under Additional Selection within which the program
wrote off items.
You can also define separate petty amount limits for over-and underpayments in
Customizing of contract accounts receivables and payable. This prevents items which
have an open amount above or below the legal petty amount limit stipulated for the public
sector being written off by mistake during a mass write-off.
In addition, now different revenue types with different petty amount limits can be written
off in the same write-off run.

23
 Write-off History

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 24

The Public Sector Write-Off History lists the individual documents which were written off
and entered in the write-off history using the function Write Off Items.
Data of the written off document, write-off document and the resubmission is displayed in
addition to the information from the write-off history.
If you have defined a separate write-off reason for waivers, you can use the write-off
history to generate a waiver directory.

24
 Resubmission Lot for Write-Offs

Selection
Clerk Mode
Administrator Mode
FMCADLOT
Resubmission Cases

In Process by me
Worklist: Resubmission Write-Off
In Process by other user
Resolved Status Status Name Doc. No. Amount Write-Off Reas. Resub. Date
Set to Resubmission In process 4711 80,- Temp. Waiver 08/15/2008
Reversed
No Resubmission

New
Resubmission
Date Clarify Lock Set Clar. Case for Change
Unlock Resubmission Status/User
No
Resubmission
Reversing

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 25

Resubmission cases can be processed further when the resubmission date has been
reached, by using the transaction Resubmission Write-Off.
There you can reverse the write-off document and then resubmit it.

25
 Exercise

Unit: 05 - Specific Posting Processes

Topic: Document Processing

SAP AG 2008, Public Sector Collections and Disbursements / Specific Posting Processes / 26

26