SAP OSS Notes

562252 SAP OSS Note - Keine Kontierungsobjekte bei V2-Verbuchung








SAP OSS Note 562252 version 0002 contains details of a know issue related to Keine Kontierungsobjekte bei V2-Verbuchung. This includes any associated symptoms and instructions on how to fix it, see below for full details. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience of this oss note and problem.

...For more information about the SAP support system known as OSS please check out the SAP OSS NOTES SECTION, whih includes how to download & implement them onto your SAP system using transaction code SNOTE.

Note 562252 Details:






When does this problem occur

Es werden periodisch buchende Bewertungsbereiche direkt mitgebucht (V2-verbuchung). Trotz korrektem Kontierungscustomizing wird ein Verbuchungsabbruch mit der Fehlermeldung F5808 "& ist für Sachkonto & & Mußeingabe" oder KI235 "Das Konto & erfordert eine kostenrechnungsrelevante Kontierung" ausgelöst (z.B. für die Kostenstelle).
Der RAPERB2000 bucht die beanstandeten Belege ohne Fehler nach.


Description of problem

APER_POST_DOCUMENT; RLAMBU, ANLZ

Cause of the problem and Pre-requisites

Programmfehler: Die Kontierungsobjekte werden nicht in den direkt mitzubuchenden Beleg transportiert.


Solution instructions

Reparatur gemäß dieses Hinweises:
Legen Sie den Funktionsbaustein APER_GET_ANTS_FROM_DB in der Funktionsgruppe APER an. Die Schnittstelle entnehmen Sie bitte der Korrekturanleitung.
Spielen Sie nun das Coding aus diesem Hinweis ein.

Note 562252 Correction instructions:



NOTE: Only source text changes are displayed here

*$*$----------------------------------------------------------------$*$*
*$ CORRECTION INSTRUCTIONS 0120061532 0000474595 $*
*$ Prerequisite corr. inst. 0120061532 0000410048 Note 0000523750 $*
*$--------------------------------------------------------------------$*
*$ VALID FOR : $*
*$ Software Component EA-APPL SAP R/3 Enterprise PLM, SCM, Financ$*
*$ Release 110 To SAPKGPAA04 $*
*$*$----------------------------------------------------------------$*$*
*&---------------------------------------------------------------------*
*& Object FUNC APER_GET_ANTS_FROM_DB
*& Object header FUGR APER
*&---------------------------------------------------------------------*
*& FUNCTION APER_GET_ANTS_FROM_DB
*&---------------------------------------------------------------------*
...
FUNCTION APER_GET_ANTS_FROM_DB .
*>>>> START OF INSERTION <<<<
*"----------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*" IMPORTING
*" REFERENCE(I_BUKRS) TYPE BUKRS
*" REFERENCE(I_ANLN1) TYPE ANLN1
*" REFERENCE(I_ANLN2) TYPE ANLN2
*" REFERENCE(I_BUDAT) TYPE BUDAT
*" EXPORTING
*" REFERENCE(E_ANTS) TYPE ANTS
*" EXCEPTIONS
*" ASSET_NOT_FOUND
*"----------------------------------------------------------------------

DATA: LS_ANLA TYPE ANLA,
LT_ANLZ TYPE TABLE OF ANLZ.
STATICS: ST_ANTS TYPE TABLE OF ANTS.


* Asset in buffer?
READ TABLE ST_ANTS INTO E_ANTS
WITH KEY BUKRS = I_BUKRS
ANLN1 = I_ANLN1
ANLN2 = I_ANLN2.

* Get asset from database
IF SY-SUBRC <> 0.
LS_ANLA-BUKRS = I_BUKRS.
LS_ANLA-ANLN1 = I_ANLN1.
LS_ANLA-ANLN2 = I_ANLN2.
* Get ANLA data
CALL FUNCTION 'ANLA_READ_SINGLE'
EXPORTING
F_ANLA = LS_ANLA
I_LOCK = SPACE
IMPORTING
F_ANLA = LS_ANLA
EXCEPTIONS
NOT_FOUND = 1
SELBST_GESPERRT = 5
VORHANDEN = 5
OTHERS = 1.

IF SY-SUBRC = 1.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4
RAISING ASSET_NOT_FOUND.
ENDIF.

MOVE-CORRESPONDING LS_ANLA TO E_ANTS.

* Get ANLZ data
CALL FUNCTION 'ANLZ_READ_MULTIPLE_BDATU'
EXPORTING
I_ANLN1 = I_ANLN1
I_ANLN2 = I_ANLN2
I_BUKRS = I_BUKRS
TABLES
T_ANLZ = LT_ANLZ
EXCEPTIONS
OTHERS = 5.

IF SY-SUBRC = 0 AND NOT I_BUDAT IS INITIAL.
CALL FUNCTION 'AMSP_ACCOUNT_ASSIGNMENTS_GET'
EXPORTING
I_BUDAT = I_BUDAT
TABLES
T_ANLZ = LT_ANLZ
CHANGING
C_ANTS = E_ANTS.
ENDIF.

APPEND E_ANTS TO ST_ANTS.
ENDIF.
*>>>> END OF INSERTION <<<<<<
...
*&---------------------------------------------------------------------*
*&---------------------------------------------------------------------*
*& Object FUNC APER_POST_DOCUMENT
*& Object header FUGR APER
*&---------------------------------------------------------------------*
*& FUNCTION APER_POST_DOCUMENT
*&---------------------------------------------------------------------*
...
READ TABLE IT_ANTS INTO LS_ANTS
WITH KEY BUKRS = LS_ANEK-BUKRS
ANLN1 = LS_ANEK-ANLN1
ANLN2 = LS_ANEK-ANLN2.
IF SY-SUBRC <> 0.
*>>>> START OF DELETION <<<<<
SELECT SINGLE KTOGR FROM ANLA INTO LS_RLAMBU-KTOGR
WHERE BUKRS = LS_ANEK-BUKRS AND
ANLN1 = LS_ANEK-ANLN1 AND
ANLN2 = LS_ANEK-ANLN2.
IF SY-SUBRC <> 0.
* write error-message in Syslog
CALL FUNCTION 'APER_CREATE_SYSLOG_ENTRY'
EXPORTING
I_MSGID = 'AA'
I_MSGTY = 'E'
I_MSGNO = '001'
I_MSGV1 = LS_ANEK-ANLN1
I_MSGV2 = LS_ANEK-ANLN2
I_MSGV3 = LS_ANEK-BUKRS
I_MSGV4 = SPACE.
EXIT. "leave ANEPI and process next ANEK
ENDIF.

ELSE. "Read ANTS
LS_RLAMBU-KTOGR = LS_ANTS-KTOGR.
*>>>> END OF DELETION <<<<<<<
*>>>> START OF INSERTION <<<<
CALL FUNCTION 'APER_GET_ANTS_FROM_DB' "<0562252
EXPORTING
I_BUKRS = LS_ANEK-BUKRS
I_ANLN1 = LS_ANEK-ANLN1
I_ANLN2 = LS_ANEK-ANLN2
I_BUDAT = LS_ANEK-BUDAT
IMPORTING
E_ANTS = LS_ANTS
EXCEPTIONS
ASSET_NOT_FOUND = 1.

IF SY-SUBRC <> 0.
* write error-message in Syslog
CALL FUNCTION 'APER_CREATE_SYSLOG_ENTRY'
EXPORTING
I_MSGID = SY-MSGID
I_MSGTY = SY-MSGTY
I_MSGNO = SY-MSGNO
I_MSGV1 = SY-MSGV1
I_MSGV2 = SY-MSGV2
I_MSGV3 = SY-MSGV3
I_MSGV4 = SY-MSGV3.
EXIT. "leave ANEPI and process next ANEK
ENDIF.
*>>>> END OF INSERTION <<<<<<
...
LS_ACCHD-TCODE = CON_TCODE_ASKBND. "RAPERB2000 direkt buchen
CONCATENATE 'RAPERB:' LS_ANEPI-AFABE '/' SY-DATUM+0(4)
SY-DATUM+4(2) SY-DATUM+6(2) '-' SY-UZEIT
INTO LS_ACCHD-BKTXT.
MOVE LS_ACCIT-BLART TO LS_RLAMBU-BLART.
*>>>> START OF INSERTION <<<<
MOVE-CORRESPONDING LS_ANTS TO LS_RLAMBU. "<0562252
*>>>> END OF INSERTION <<<<<<
...
*&---------------------------------------------------------------------*

Effected Objects:


(FUNC) - APER_GET_ANTS_FROM_DB
(FUNC) - APER_POST_DOCUMENT

(FUNC) - APER_GET_ANTS_FROM_DB
(FUNC) - APER_POST_DOCUMENT

Solution instructions


Please import the corrections attached to this OSS note into your SAP system using SNOTE.

You can also view the full details of this OSS note and download it to your SAP system ready for implementation using transaction code SNOTE. Once it has been downloaded you can read the full details, check out any installation instructions including manual changes and see if there are any pre-requisites.

You can also check if a new version of note 562252 has been released as well as see if the note is valid for your current SAP system landscape.

Check if SAP OSS note 562252 has already been downloaded and is valid


To check if this note has already been download, what status it has and if it is valid for your system first execute t-code SNOTE and click on the SAP Note Browser icon
Icon used to execute SAP Note Browser report within SNOTE

From here you can just enter the note number 562252 and press execute. If the note already exists it's details will be displayed. See here for full step by step instructions on how to check if an SAP note has been downloaded and is valid for your system.



If note 562252 does not exist on your system you will receive the message "Unable to find SAP Note that meets specified criteria"
Icon used to execute SAP Note Browser report within SNOTE

If this is the case you will need to download the note to you SAP system also using transaction SNOTE. For further details see Download note using SNOTE. Even if it does exist you may still want to check if you have downloaded the latest version of the note.

Alternatively you can find full details of this note on the SAP service market place(SNumber / Service market place login will be required)