SAP Note Nr. 2596 28.03.

2019 Page 1
________________________________________________________________________

Number 2596
Version 21

Processor
Processing Status new
Implement. Status Cannot be implemented

Language EN
Short Text SAPDFKA6: New fields in fast entry screens

Component FI Financial Accounting

________________________________________________________________________

Long Text

Symptom

Key word: FAKP

Program : SAPDFKA6
Customer wants to use new fields in the list of possible fields whilst
generating screen templates for fast entry screens.

Other terms

Reason and Prerequisites

Fields are missing in the SAP standard system, or customer has added new
fields.

Solution

This note is in generally valid for all programs which use the method
for generating screens for fast entry. The individual screens ar
e: Program Applic. Description Reference screen
-------- --------- ------------------------- -------------
SAPLF040 PRPOS FI: Preliminary posting SAPVF040/1002
SAPLFICP ICPOS FI: External documents SAPVFICP/1001
SAPLFKMT KMPOS FI: Acct assignment models SAPVFKMT/1001,1002
SAPLFRAD AVIP FI: Payment advice notes SAPVFRAD/1001
SAPMF05A RE/GU FI: Inv/cr.memo fast entry SAPVF05A/1001
SAPMF05A SAKOP FI: G/L account fast entry SAPVF05A/1002
SAPMF40K KNTAZ FI: Acct statement (man.) SAPVF40K/1002,1003
SAPMF40S SCHKR FI: Check deposit trans. SAPVF40S/1002,1003
SAPMKAUF ORC CO: Internal orders SAPVKAUF/3000
SAPMKMA1 COMA1 CO: Cost center master SAPVKMA1/1200

If you want to insert characteristic fields for profitability segments

in entry screens, refer to Note 331370.

This is a modification which can be carried out as follows (using

SAPMF05A and tables BSEG/SAPOS as an example):
Use SE51 to add the new BSEG-NNNNN field for "G/L account items ->
Screen templates"
on screen SAPVF05A/1002 (Releases 2.1*)
on screen ZZZVF05A/1002 (all following releases)
SAP Note Nr. 2596 28.03.2019 Page 2
________________________________________________________________________
1. Put the input field (BSEG-NNNNN),
the key word (BSEG-NNNNN),
and the column heading (*BSEG-NNNNN) on the screen.
Be sure that you only pick these fields out of the dictionary
(Goto -> Dict./program fields)
2. The field attributes (in particular the modification groups) are to
be filled according to the requirements of the underlying appli
cation (this is application-specific).
The field 'Ok Code' must have the field name 'OK CODE'; if not,
maintenance is terminated with error message F4308 in routine FLDTAB_F
UELLEN.
3. In the flow logic, a line like
FIELD BSEG-NNNNN.
should be added.
4. Generate the screen.

For "Vendor inv./crdt memo -> Screen templates" (Transaction FB10), use
SE11 to add the new "NNNNN" field in the SAPOS structure. Save
and activate SAPOS.
Then use SE51 to add the new SAPOS-NNNNN field on screen
SAPVF05A/1001 (Releases 2.1*)
on screen ZZZVF05A/1001 (all following releases)
1. Put the input field (SAPOS-NNNNN),
the key word (SAPOS-NNNNN),
and the column heading (*SAPOS-NNNNN) on the screen.
Be sure that you only pick these fields out of the dictionary
(Goto -> Dict./program fields) 2. In the flow logic, a line like
FIELD SAPOS-NNNNN.
should be added.
3. Generate the screen.
4. Note: for vendor inv./credit memo fast entry it is only possible to
define variants with two or more lines as of Release 3.0A.
Therefore, it is not possible to insert the item text (SGTXT), which has
a length of 50 bytes, prior to Release 3.0A. It is not possib
le to define fields with a reduced length.
Simplification as of Release 3.1H:
For the applications SAKOP, inv./credit memo, PRPOS and KMPOS, you can
use program RGUCBFIP to change the model screens with regard to
the fields that have been included in the coding block using OXK3.
General note:
You have to check whether there are modules to check the input for the
new field and whether they are processed during fast entry. It
may be necessary to add or to include such a check module. You should
also check whether a blank entry representing the "OK CODE" appe
ars in the field list, before generating the screen. If a blank is
there, enter the field name "OK CODE" in its place.

If you want to add an SAP standard field, then send a development

request to SAP so that this field can be included in the standard li
st in future releases. Do not include any SAP Standard fields in your
ZZZ* screen without having first spoken with an experienced cons
ultant. Some SAP Standard fields are not on the standard template
screens (with good reason), since the required flow logic cannot be
copied into the screen template (for example, BSEG-DMBTR, BSEG-ANBWA).
It only makes sense to add such fields to the template screens
that can be assigned to accounts using the standard transactions without
fast entry (e.g. not: BSEG-VBELN since this field is not avai
lable in the ordinary document entry either).
SAP Note Nr. 2596 28.03.2019 Page 3
________________________________________________________________________

If the screen on which the new field should be put does not yet exist,
it has to be created (using SE51). A corresponding module pool
(SAPVF05A) does not exist - it may have to be created (SE38, create,
complete required fields only).

CAUTION, please note:

Do not include fields to the user-defined screen ZZZ* which already
exist in the SAP template screen. In particular, SAP warns against
copying the SAP screen as screen ZZZ*. Otherwise, duplicate entries may
occur in the list of possible fields in Transaction FAKP.

________________________________________________________________________

Valid Releases

________________________________________________________________________

Links to Support Packages

Software Component Release Package Name

________________________________________________________________________
________________________________________________________________________