FI: EHP7 Issues After Upgrade

FI: EHP7 Issues After Upgrade

MIRO Small Difference (Rounding off)

Gabriel India Limited, MIRO / Auto MIRO/FB60 Prepared by: Anil Vishwakarma,
Serial Number: 2015/09/EHP7/FI/DN/001 Document Revision Date: 29.09.2015
Contents
1. Error after SAP upgrade to EHP7 .................................................................................................. 1
2. Error Analysis: ................................................................................................................................ 1
2.1 MIRO Rounding off Issue raised to SAP ....................................................................................... 2
3. Solution .......................................................................................................................................... 3
3.1 Define the user exit Z_FI_MIRO .................................................................................................... 3
3.1.1 Draw back Z_FI_MIRO user exit ............................................................................................... 3
3.2 Define OKB9 at higher level with Valuation Area .......................................................................... 3
4. Configuration Change .................................................................................................................... 4
4.1 Configuration for Valuation Area .................................................................................................... 4
4.2 Define CO-Substitution .................................................................................................................. 5
4.3 Check Client Specific user exit GCX2 transaction code ................................................................ 7
4.4 Routine UOKB9 Code .................................................................................................................... 8
5. Operating Procedure .................................................................................................................... 10
8 Conclusion. .................................................................................................................................. 10
Request Number.
Request No
1. ECDK916708 FI-AV-23.09.2015 CO Object Error Configuration

2. ECDK916706 PRAMOD-SD-23.09.15 CO OBJECT ASSIGNMENT ERROR
3. ECDK916728 PRAMOD-SD-23.09.15 CO OBJECT ASSIGNMENT ERROR1 – COMMIT
4. ECDK916730 PRAMOD-SD-23.09.15 CO OBJECT ASSIGNMENT ERROR1 – 1 WAIT
5. ECDK916732 FI-AV-29.09.2015 OKB9 Assignment on Valuation Area
6. ECDK916734 PRAMOD-SD-23.09.15 CO OBJECT ASSIGNMENT ERROR1 COMMENT
7. ECDK916736 FI-AV-29.09.2015 Substitution for MIRO UOKB9
8. ECDK916742 FI-AV-29.09.2015 OKB9 Valuation Area Mnt for After Market
9. ECDK916744 FI-AA-29.09.2015 Valuation Area for 2000 AM
Gabriel India Limited, MIRO / Auto MIRO/FB60 Prepared by: Anil Vishwakarma
1. Error after SAP upgrade to EHP7

Error while posting MIRO, system generates additional line for small difference, for this line
item cost center and profit center is not being captured, those it is defined in OKB9, maintained
in level 3 in cost element 463116.
Error: Account 463116 requires an assignment to a CO object

Error “balancing field profit center line item 012 not filled (773946 / 2015)
2. Error Analysis:
This issue occurred after SAP upgradation from EHP 4 to EHP7, in EHP4 system was running fine, the
profit center is being defined correctly for the cost element 463116,
We have tried to resolve the above error by doing the configuration in OKB9, we have tried all the
configuration option available in OKB9, but error is not resolved by doing configuration change.
Old Configuration in OKB9
Change Configuration in OKB9
Page No. 1
SAP Response
2.1 MIRO Rounding off Issue raised to SAP
Please check your settings in transaction OKB9.Attached note 32654 explains why the system takes
the account assignment at a higher level for automatically generated lines like small differences. You
should maintain an entry in OKB9 at a higher level than valuation level (or profit center, or business
area). OKB9 is used whenever there is an account assignment to a cost element. This particular
problem with the system not being able to use the 'detailed' OKB9 assignment happens when the
system creates an automatically generated line in a document. This is driven by the transaction key
and is then linked to OKB9 by the G/L account defined for the transaction key. The most common
transaction keys that are used in auto-generated lines are 'DIF' (small diff) and 'KDR' (exchange rate). I
have also attached note 409520 for more information.
With Kind Regards,
Adam Kavanagh,
MM Support Engineer,
Global Support – Logistics
SAP has suggested

Note 0000409520 Goods invoice receipt default account assignment ignored.pdf
Note 0000032654 Automatic account assignment at higher level.pdf
Page No. 2
Sapnote_000003265 Sapnote_000040952
4 - Automatic account
0_Goods
assignment
invoice
at high
receipt
level.pdf
Default account assignment ignored.pdf
3. Solution
To eliminate the error we have decided to go with the Enhancement to derive cost center and
profit center plant wise for the small difference line generated in MIRO
3.1 Define the user exit Z_FI_MIRO

We have dined the user exist Z_FI_MIRO written in program ZRGGBS00. The logic
written as
 Commit the MIRO data in BSEG table
 Derive the profit center from WRX key from BSEG table
 Seek the Profit Center from OKB9 where the profit center is equal to profit
center maintained against WRX key,
 Pick the Cost Center against the profit center in OKB9
 Change the profit center and cost center in BSEG line item against the DIF key
3.1.1 Draw back Z_FI_MIRO user exit

 We have to put the WAIT statement for 2 seconds, so the MIRO booking is
delayed by 2 seconds for each document
 It is corrected for Entry View not for the Accounting view, so the profit center
and cost centers mismatch in both the views
 We have to define Default Account Assignment cost center in Cost element
463116,
 While reversing the MIRO system posts the small difference value in default
cost center and demine the profit center accordingly. That means the reversal is
done in HO profit center because default cost center is define from HO.
[Note: the above solution is not feasible and recommended due the inconsistency in cost
center & profit center determination at all stages of transaction posting and reversal]
3.2 Define OKB9 at higher level with Valuation Area
 Configuration for Valuation Area (OKB9)

o Maintain Valuation Area and Cost Center for Plants & After Market
 Define CO-Substitution (OKC9)

 Check Client Specific user exit GCX2 transaction code
 Modify Program RGGBS000 with code
Page No. 3
4. Configuration Change
4.1 Configuration for Valuation Area
To rectify the error following activity to be performed
1. Go to OKB9 transaction code

2. Select Cost element 463116
3. Change Account Assignment Setting to 1 Valuation area is mandatory
4. Double Click on Detail per business area/valuation area
5. Maintain Valuation Area and Cost Center
6. Save
Execute Transaction Code OKB9
Select Cost element 463116 and Change Account Assignment to 1
Maintain Valuation Area and Cost Center
Page No. 4
4.2 Define CO-Substitution
Substitution checks whether a particular input values satisfy one or more user-defined conditions, if
the given condition satisfied, the values are automatically replaced by other value.
Standard settings
The following call up points are defined in the standard SAP for Controlling:
 0001 - Document row : Used for all CO-relevant postings in external accounting as well as for
manual postings in CO.
Transaction code
Click on New Entry
 Choose the "New entries" function.

 Enter the controlling area in which the substitution is to be executed.
 Enter a call-up point.
 Select Active
 Save
Page No. 5
Choose "Environment -> Substitution".

Enter a name and a call up point for the substitution
Change the data as per requirement or given in below screen - Prerequisite.
You can choose "Exit only" or database fields.
"Exit only" ensures that all fields allowed for substitution are available only in this USER-EXIT. UOKB9
Page No. 6
4.3 Check Client Specific user exit GCX2 transaction code
Here we need to check assigned program for the Application Area GBLS. We need to
some change in Program, First copy from Existing program RGGBS000 to ZRGGBS000.
Change in Z Program as below-
Page No. 7
Note : see below changes are based on organization structure here you need to determine which field
you can enter to get Cost center, if you are using Business area so OKB9 can be determine by Business
area .
We have made OKB9 account assignment as per Valuation Area, but here system does not determine
profit center and Valuation Area for auto generated line item,
Our Business Place and Section Code is equal to Plant (Valuation Area)
4.4 Routine UOKB9 Code

* Form UOKB9
FORM UOKB9 .
IF COBL-WERKS is INITIAL AND COBL-BWKEY is INITIAL.

COBL-WERKS = bseg-bupla.
COBL-BWKEY = bseg-bupla.
ENDIF.
DATA:
LD_KOSTL LIKE COBL-KOSTL,
LD_AUFNR LIKE COBL-AUFNR,
LD_PRCTR LIKE COBL-PRCTR,
LD_PAOBJNR LIKE COBL-PAOBJNR.
CHECK COBK-VRGNG = 'COIN'.
CHECK NOT COBL-HKONT IS INITIAL.

CALL FUNCTION 'RK_KSTAR_READ'
EXPORTING
DATUM = COBK-BUDAT
KOKRS = COBK-KOKRS
KSTAR = COBL-HKONT
IMPORTING
V_CSKB = CSKBV
EXCEPTIONS
KSTAR_NOT_FOUND = 1.
CHECK SY-SUBRC = 0.
Page No. 8
CALL FUNCTION 'K_ACCOUNT_ASSIGNMENT_GET'
EXPORTING
BUKRS = COBL-BUKRS
WERKS = COBL-WERKS
BWKEY = COBL-BWKEY
GSBER = COBL-GSBER
KSTAR = COBL-HKONT
I_COBL = COBL
IMPORTING
KOSTL = LD_KOSTL
AUFNR = LD_AUFNR
PRCTR = LD_PRCTR
E_PAOBJNR = LD_PAOBJNR.
IF COBL-KOSTL IS INITIAL "*!

AND NOT LD_KOSTL IS INITIAL.
COBL-KOSTL = LD_KOSTL.
ENDIF.
IF COBL-AUFNR IS INITIAL "*!

AND NOT LD_AUFNR IS INITIAL.
COBL-AUFNR = LD_AUFNR.
ENDIF.
IF COBL-PRCTR IS INITIAL "*!

AND NOT LD_PRCTR IS INITIAL.
COBL-PRCTR = LD_PRCTR.
ENDIF.
IF COBL-PAOBJNR IS INITIAL "*!

AND NOT LD_PAOBJNR IS INITIAL.
COBL-PAOBJNR = LD_PAOBJNR.
ENDIF.
ENDFORM. "UOKB9
*&-----------------------------------------------------------------------------------------------------------------------------------------------*
Page No. 9
5. Operating Procedure
No Change in Operating Procedure
8 Conclusion.
Solution provided with Enhancement is not worked for this scenario, we have
implemented the standard process which is also recommended by SAP.
Page No. 10

Uploaded by

Uploaded by

FI: EHP7 Issues After Upgrade

MIRO Small Difference (Rounding off)

1. ECDK916708 FI-AV-23.09.2015 CO Object Error Configuration

1. Error after SAP upgrade to EHP7

Error: Account 463116 requires an assignment to a CO object

Old Configuration in OKB9

Change Configuration in OKB9

2.1 MIRO Rounding off Issue raised to SAP

SAP has suggested

3.1 Define the user exit Z_FI_MIRO

3.1.1 Draw back Z_FI_MIRO user exit

3.2 Define OKB9 at higher level with Valuation Area

 Configuration for Valuation Area (OKB9)

 Define CO-Substitution (OKC9)

1. Go to OKB9 transaction code

Execute Transaction Code OKB9

Select Cost element 463116 and Change Account Assignment to 1

Maintain Valuation Area and Cost Center

4.2 Define CO-Substitution

Click on New Entry

 Choose the "New entries" function.

Choose "Environment -> Substitution".

Change the data as per requirement or given in below screen - Prerequisite.

You can choose "Exit only" or database fields.

4.3 Check Client Specific user exit GCX2 transaction code

Change in Z Program as below-

4.4 Routine UOKB9 Code

IF COBL-WERKS is INITIAL AND COBL-BWKEY is INITIAL.

CHECK COBK-VRGNG = 'COIN'.

CHECK NOT COBL-HKONT IS INITIAL.

CALL FUNCTION 'K_ACCOUNT_ASSIGNMENT_GET'

IF COBL-KOSTL IS INITIAL "*!

IF COBL-AUFNR IS INITIAL "*!

IF COBL-PRCTR IS INITIAL "*!

IF COBL-PAOBJNR IS INITIAL "*!

You might also like