oss note 0042615

8/9/2019 Oss Note 0042615

http://slidepdf.com/reader/full/oss-note-0042615 1/4

22.04.2007 of 4

SAP Note Number 42615 - Substitution in FI

Note Language: English Version: 27 Validity: Valid from 28.01.2002

Summary

SymptomA substitution has been defined but nothing is substituted when posting.

More TermsSubstitution exit, user exit, GGB1, OBBH, FB01, MR01, MR1M,

PERFORM_PARAMETER_TOO_SHORT, MRHR, MRHG, MR21, MIRO

Cause and PrerequisitesNote:

If you use a substitution exit, make sure that only fields are replaced and

that no side effects occur. For example, you must not trigger any error

message, since this would interfere with the SAP program control. You haveto issue your error messages in validation. In substitution and validation,

error messages of category W, I are always only generated for the manual

entry in FI and for the invoice verification MR01. For postings from other

application components (for example, from SD (VF01) or from the logistics

invoice verification (MR1M)), error messages of category W, I are ignored.

Possible causes are:

1. The requirement specified as a prerequisite has not been met for the

posting.

2. The substitution was not activated in Customizing (Transaction OBBH)or it is not activated for batch input.

3. Not all the values are available yet for callup point 1 and 2 for the

substitution or validation in Transactions MR01, MRHR, MRHG, MR21,

etc. (all with program SAPFMM08R). You should therefore use callup

point 3 for the validation in these transactions. The values for

callup point 1 and 2 are already available in the logisitics invoice

verification (MR1M).

4. A substitution for reversal postings (FB08, F.80) was defined. No

substitution for callup point 1 - 3 takes place in FI for reversals,

because the reversal document must resemble the document to be posted

(except the exchanged debits and credits).

5. An attempt was made to use a substitution exit to substitute a field

which has not been released for substitution. When defining a

substitution, you will find the fields that can be substituted under

the "Extras -> Fields for substitution" menu option.

6. A customer-defined field ZFELD was included in table BSEG. Such fields

are not substituted during postings (from other modules) via the FI/CO

interface. You must enhance the coding block so that ZFELD is

substituted.

The substitution callup points available with Release 3.0 are primarilyintended not as an input help, but above all to allow costumer-specific

fields to be supplied with values without program modifications. So that,

8/9/2019 Oss Note 0042615


22.04.2007 of 4


if possible, all values for standard fields are available here, the

substitution callup point is only after the checks in the standard system.

After the substitution no further check is carried out. Only those standard

fields are released for substitution which meet the following requirements:

1. Values are not critical for further processing and are not validated

against other tables.

2. Substitution is carried out for all documents that are posted.

Therefore only relatively few fields can be substituted for callup points 1

(document header) and 2 (line item). At callup point 3 (complete document),

no field has currently been released since substitution is not possible for

all transactions by which documents are posted (for example MR1M, VF01,

MB01 or all postings via the FI/CO interface).

Please also refer to Note 386896.

Fields of the coding block can be set at callup point 1 via the

substitution in CO (Transaction OKC9).

SolutionYou can carry out a substitution for some fields. If invalid values are

substituted in this case, you may receive the wrong function or error

messages in standard programs. However, these errors are not particularly

critical. You can currently release the following fields for substitution:

BSEG-FIPOS, BSEG-HBKID, BSEG-MSCHL, BSEG-MANSP, BSEG-MADAT, BSEG-MANST,

BSEG-MABER, BSEG-RSTGR, BSEG-ZLSPR

Formally, this is a modification. Therefore, you can also change entries in

the table via SAP transports with a release upgrade (refer to Note

0391309).

If you release fields other than the ones listed for substitution, then you

must take responsibility for all the consequences!

Important: At callup point 2 (BOOLCLASS = 009) NO fields must be released

for substitution from the document header. Otherwise, the system generates

a short dump (PERFORM_PARAMETER_TOO_SHORT).

In addition to accounts and amounts, the following fields, for example, are

critical and must not be substituted:

GSBER: this could lead to inconsistencies with modules AM, CO and

MM, since the business area is also used in these modules.

To make, for example, the BSEG-MABER field substitutable for callup point2, proceed as follows:

1. Table entry in GB01

With an ABAP/4 program, change the entry:

BOOLCLASS CLASSTYPE BCLTAB BCLFIELD BEXCLUDE

009 S BSEG MABER X

in table GB01 to the entry:

BOOLCLASS CLASSTYPE BCLTAB BCLFIELD BEXCLUDE

009 S BSEG MABER

That is, the BEXCLUDE field must be set to space. There is no view for

maintaining GB01.

8/9/2019 Oss Note 0042615


8/9/2019 Oss Note 0042615


22.04.2007 of 4


Number Short Text

881202 FM derivation tool: Derivation of foreign acct assignments

720881 KALC: Terms of payment missing in FI document

687972 Substitution for the LZB in France

638886 SAP Cons: Consoldatn transctn on customer/vendor line items

582950 Business area not transferred to line items

513891 BUC: Field VBUND not filled with loan postings

436046 CO interface: Error KC051 (Entry in COKA-Buffer not found)

413956 Complete document / matrix validation, -substitution

391309 GB01 Boolean class 015: FI subst. for call-up point 3

386896 Substitution for call-up point 3 ('Complete document')

380239 GB01 Booln clss 009:fld BSEG-PARGB nt rlsd fr sbstn

331202 Required field check for automatically genrtd clearing items

301077 User exits for the interface to accounting

210224 Substitution of the functional area in IS-PS 46.1

206574 Miro:F5A068 itm txt is requird entry fld for a/c XY189447 Line by line validation for callup point FI-3

154918 "USING","TABLES" or "CHANGING" expctd aft. "FOUND"

148741 Accrual/deferral postings without trading partner

123218 Validation/substitutn BSEG-VBUND FI callup point 2

99483 Syntax error: 'B_SUBRES-xxx' is already declared

97557 Substitution in FI for change document

95516 Problems with matrix validations/substitutions

89571 Substitution of coding block fields in FI

82105 Maintenance of V_GB01C not possible

76872 Substitutions in FI at callup point 368506 Invoice verification: wrong substitution/validation

20637 Inserting Fields in Validations and Substitutions

Attributes

Attribute Value

weitere Komponenten MM-IV

oss note 0042615

Documents