Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Write-offs
Internal
Baohua Feng
March 01, 2016
Agenda
Overview
System Demo
Documentation
Features:
You can write off open items completely, or partially in transaction Write Off Items (FP04).
The written off items are cleared and a write-off document is created.
Write-off History
Val: Valid for manual write-off (Write off or Mass Write-off or both )
CO account Assignment:
2 = derived from the write-off main and sub transaction from posting area R001*
*Posting Area R001 - Acct Assignment Data to main and sub transactions
Key fields :
Company code
GL account of the write off item
Write off reason
Division
Account Determination ID
Main transaction
Subtransaction
Function fields:
G/L account for expenses from write-offs.
G/L account for write-off revenues.
Selection of :
Business partner
Contract account
Contract
Document number
Reference Document
IS-PS
specific
IS-U
specific
The function module called at event 5010 enables you to specify company-
specific check rules. It’s called in process after selection of open items from
database. It comes directly before actual selection of the items to be written off.
Depending on the authorization of a user they can write off with or without
check rules:
Special authorization for activity 020 of the authorization object FI-CA Special
Function (technical name F_KK_SOND)
* FQAUTH can be used to check the predefined processing functions with authorization protection (F_KK_SOND)
BAPI:
BAPI_CTRACDOCUMENT_WRITEOFF
5006 Check data or get defaults on selection screen for the transaction Write Off Items (FP04)
5010 Specify company-specific check rules ( is not used when flag ‚do not use write-off rules‘ is set. )
5030 Additional Account Assignment such as cost centre, profit centre or business area (see also
Posting area 1052)
5040 Enables you to realize closing actions after the write-off was processed
5512 Write-off workflow:decides whether the write-off you have entered has to be approved
General Selection:
You can use GPART and VKONT as selection criteria or the preselection.
To maintain preselected data, you can use transaction FPSELP.
Via preselection, you have much more possibilities to specify criteria (e.g.
surname) for your mass run.
Preselection used
Direct selection
Addtional Selection:
Posting Parameters:
You can see via Menu also in simulation mode, to which accounts the postings will be done
Next slide
It’s also possible to write-off the downpayments
Example
Document 4711 was posted 360 days ago with the amount EUR 1000.
There is a write-off variant VARI with the following settings:
Days after Sequential Automatic From these settings, the system derives the following procedure:
Amount Log
Due Date Number W/O 1. The document is older than 50 and 100 days. The system therefore
50 1 500 X
checks all four entries, but firstly the items with the highest number of
days after due date and the smallest amount.
100 1 500 X 2. The system checks line 2 first. The amount of EUR 1000 is more than
EUR 500 and, therefore, does not qualify.
100 2 1000 X X 3. The system then checks line 3. The amount of EUR 1000 is within the
range up to EUR 1000 and therefore qualifies for the write-off.
100 3 5000 X
4. The system writes off the item automatically and makes a note in the log.
VC_TFK090:
VC_TFK090:
Subroutine:
• document_lines_create
• gl_lines_create
• document_post
Due to historical reason, FP04 (Manual Write-off) and FP04M(Mass Write-off) are
still complete different.
FP04 FP04M
Function Group FKA1 FKA8
Main FM FKK_WRITEOFF FKK_SAMPLE_1730
OPK Created writeoff_fkkopk_create gl_lines_create
……
Challenge
It means that all corrections are needed to be considered if it applies to
both transactions and if yes, it has to be done seperately.
Background:
Runtime error with SAPSQL_ARRAY_INSERT_DUPREC is reported for FP04M
Explanation:
The problem happened when the collective bill accounts are involved and the
parallel processing is scheduled for FP04M.
When the process writes off an item which is contained in a collective bill, the
corresponding statistical collective item is partially written off as well. As the
collective bill 'contains' postings from many different contract accounts,
it may happen that several processes of the mass activity are trying to partially clear
the same open position of the collective bill at the same time.
Such competitive update on the same collective bill account
document during parallel processing of the write-off will lead to runtime error.
See Wiki-Page
https://wiki.wdf.sap.corp/wiki/display/imsfica/Write+Off
http://help.sap.com/erp2005_ehp_07/helpdata/en/62/e7c5536a51204be10000000a174cb4/frameset.htm
2068654 - WriteOff Approval: Unexpected error messages e.g. >0 012 or >0
476 prevent postings or too many sub-items written off
Contact information:
Baohua Feng
mailto: Baohua.feng@sap.com