1 Shaktizshura

Line Assignment Sap Fb02

Purpose 

The purpose of this page is to explain under what circumstances the system allows to change a field in an already posted document in FB02.

What kind of field can never be changed in standard?

1)      The standard system prevents certain field contents from being changed. These include all the fields in the document header except for the reference document number (BKPF-XBLNR) and the document text (BKPF-BKTXT) fields.

The reason behind this system design is to protect critical accounting document data and to avoid fiscal period close problems, e.g., audit control, out of balance situations.

2)      In case NewGL is active, fields which are actively used in NewGL cannot be changed subsequently.  

The reason behind this is following: transaction FB02 only updates the line items of the entry view (BSEG). NewGL cannot be updated because in NewGL an update may involve several processes which do not allow a subsequent change of fields. If these fields were changable, then this would lead to an inconsistency between the entry view and the NewGL view.

3)      Fields that are used in the FI-SL field movement are not usually changeable.

The reason is that Special Ledger is only updated when the document is created. For other components like profit centre accounting or special ledger a subsequent change in an FI document is only local. Special Ledger does not get the information about the change. Thus, in order to avoid inconsistencies between SL and FI those fields are not changeable.

To see whether this is the case, use transaction SE37 to execute the function module G_CHECK_FIELD_USED_IN_GLX in the single test for the affected field. If you receive the export parameter with RC <> 0, it is the case described above. This should be an executive summary of the content and argument being made in the document. Basically a summary (not repeat) of the information you are explaining.

How you can make a field changeable?

The fields in question are not fields of the coding block.

The corresponding field should be maintained correctly in the table TBAER. The table can be maintained in view V_TBAER, calling transaction SM30.

Important:

a) The field should be contained in the table.

b) The rule for the existing case should be correctly defined.

c) The "Field Can Be Changed" indicator should be selected.

What to do if there is an entry for a field in table TBAER but the field cannot be changed (it’s greyed out) in FB02?

1)      Check whether the field is used in Special Ledger: in SE37 execute the function module G_CHECK_FIELD_USED_IN_GLX in the single test for the affected field. If you receive the export parameter with RC <> 0, this field is used in SL.

In this context, see also SAP Note 79760.

2)      Check your customizing in Document Change Rules (transaction OB32).

Some tipical cases: 

a)     Special G/L indicator: if the field which is requested  change in FB02 was posted in a line item with a special G/L indicator within transaction class „A” or „W” (BSEG-UMSKS = A or W), the field can only be changed if a corresponding entry in the table TBAER is maintained (V_TBAER-UMSKS).

The document change rules only have special provisions for transaction types A (down payments) and W (bills of exchange). For all other transaction types the rule for transaction type "blank" is used.

b)     Posting period: if the indicator „Posting period not closed” (V_TBAER-XBUPE) is activated, even if the corresponding field is maintained under the Document Change Rules, it won’t be possible to change the field value in an already posted document if the period (in TA OB52) is closed.

c)      Line item cleared: if the indicator „Line item not cleared” (V_TBAER- XAUSZ) is activated, even if the corresponding field is maintained under the Document Change Rules, it won’t be possible to change the field value in an already posted document if the line item is already cleared. The indicator should be set for all fields which are used for controlling payment transactions or dunning, such as terms of payment, cash discounts, payment methotds and dunning keys.

Related SAP Notes/KBAs 

SAP Note 79760: Certain BSEG fields cannot be changed (FB02)

SAP Note 827413: Changeability of fields in FI documents

Knowledge Base Article 1497601: Document change rule defined in T-code OB32 does not work - field cannot be changed in T-code FB02

Master Data

MD25

Create planning calendar

MD26

Change planning calendar

MD27

Display planning calendar

MDSA

Display BOM explosion number

MDSP

Edit BOM explosion number

MEQ1

Maintain quota file

OPPP

Explode BOM by date

MDUS

Display project assignment

MDUP

Process project assignment

MDL1

Create production lot

MDL2

Change production lot

MDL3

Display production lot

Planning

MD20

Create planning file entry

MD21

Display planning file entry

MDAB

Set up planning file entry in background

MDRE

Check planning file entry

MD01

Total planning online

MDBT

Total planning in background

MD03

Single-item, single-level planning

MD02

Single-item, multi-level planning

MD43

Interactive single-item planning

MD50

Multi-level, make-to-order planning

MD51

Multi-level project planning

MF52

Display planning table

MF50

Change planning table

MF57

Planning table by MRP lists

MF51

Planning table by production list

Evaluations

MD04

Stock/requirements list

MD07

Collective access of stock/requirements lists

MD05

MRP list

MD06

Collective access of MRP lists

MDLD

Print MRP list

MD45

Planning result

MD46

Collective access of planning result

MD44

Planning situation for a material

MD47

Planning situation for a product group

MD48

Cross-plant planning situation

MD4C

Order report

MD09

Pegged requirements

CO46

Order progress

Planned Order

MD11

Create planned order

MD12

Change planned order

MD13

Individual access of planned order

MD16

Collective access of planned orders

MD14

Individual conversion of planned order into purchase requisition

MD15

Collective conversion of planned orders into purchase requisitions

MDUM

Convert planned order into purchase requisition in background

CO40

Convert individual planned order into production order

CO41

Collective conversion of planned orders into production orders

CO48

Partial conversion of planned order into production order

COR7

Individual conversion of planned order into process order

COR7_PC

Collective conversion of planned orders into process orders

COR8

Partial conversion of planned order into process order

MDVP

Collective availability check

MDAC

Execute action for planned order

Leave a Comment

(0 Comments)

Your email address will not be published. Required fields are marked *