|
24.07.2008 Page 1 of 2
Note 29708 - Entry of account assignment fields in FB02, FBD2
Note Language: English Version: 8 Validity: Valid from 14.01.2002
Summary
Symptom
For document updates (Transaction FB02) and updates of recurring documents
(Transaction FBD2), the customer-defined fields that were entered in the
system as the result of a source code enhancement are not ready for input.
Question: what can be done to make these fields ready for input?
More Terms
Account assignment block, section of code, additional account assignments,
OXK3
Cause and Prerequisites
Entries in Tables TBAER and TCOBX are missing.
Solution
Add entries to tables TBAER and TCOBX to meet your requirements (in
Transaction SM31).
The required entries are shown below in the example of additional account
assignment ZZTEST.
1. Entry in table TBAER (= document change rules)
AcTyp I Trans. type I Field name I CoCd I Field name
---------+-------------+---------------+----------+-------------------
-
S I I COBL-ZZTEST I I Coding Block Test
(Enter COBL-<field_name> as field name, not BSEG-<field_name>)
2. Entry in table TCOBX (= COBL: assignment of field attributes)
Fieldname I Program I Scrn no. I Gr1 I Gr2 I Gr3 I Gr4
------------+----------+----------+-----+-----+-----+-----
ZZTEST I SAPMF05L I 0300 I I I 001 I
(Enter the field name without "COBL-"; with Gr3, enter number 001.)
The changes of the field contents in Transactions FB02 and FBD2 are logged
in change documents for SAP standard fields.
To activate writing of change documents for customer-specific fields, set
the indicator 'Change document' in Transaction SE11 for the data elements
of the fields and activate the data elements.
As of Release 4.5A, this indicator is set automatically for fields that are
transferred to the coding block in light mode.
Header Data
 |
|
Вход
Регистрация
FAQ пользователя
Поиск
