SAP OSS Notes

698549 SAP OSS Note - Calling application MM for dynamic exceptions








SAP OSS Note 698549 version 0003 contains details of a know issue related to Calling application MM for dynamic exceptions. 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 698549 Details:






When does this problem occur

Up from release 4.7 for the caller MM for dynamic exceptions was
created to define exceptions valid for the whole logistic process.
In lower releases it was necessary to define the exception for
PO (purchasing); IM (inventory management) and
IV (invoice verification)
From the application itself the caller remains PO, IM or IV.
Therefor itīs necessary to access the exception tables also with
caller MM when itīs called from PO; IM or IV.

Description of problem

Brazil; Nota Fiscal; dynamic exceptions; caller;

Cause of the problem and Pre-requisites

This note is only relevant for Brazil.

Solution instructions

Source code correction.

Note 698549 Correction instructions:



NOTE: Only source text changes are displayed here

*$*$----------------------------------------------------------------$*$*
*$ CORRECTION INSTRUCTIONS 0120031469 0000295460 $*
*$--------------------------------------------------------------------$*
*$ VALID FOR : $*
*$ Software Component SAP_APPL SAP Application $*
*$ Release 500 All Support Package Levels $*
*$*$----------------------------------------------------------------$*$*
*&---------------------------------------------------------------------*
*& Object FUNC J_1BCALCULATE_TAXES
*& Object header FUGR J1BR
*&---------------------------------------------------------------------*
*& FUNCTION J_1BCALCULATE_TAXES
*&---------------------------------------------------------------------*
...
ASSIGN: space TO , "BK99
space TO , "note 370571
space TO ,
space TO ,
space TO ,
space TO ,
space TO ,
space TO ,
space TO .
*>>>> START OF DELETION <<<<<

*>>>> END OF DELETION <<<<<<<
*>>>> START OF INSERTION <<<<
*
data: lv_caller(2) type C. "698549
* set caller to MM for logistic process to "698549
* allow it for the whole process "698549
if cf-caller = 'PO' "698549
or cf-caller = 'IM' "698549
or cf-caller = 'IV'. "698549
lv_caller = 'MM'. "698549
else. "698549
lv_caller = cf-caller. "698549
endif. "698549
*>>>> END OF INSERTION <<<<<<
...
* "BK99
SELECT * FROM j_1btxgruop INTO TABLE i_j_1btxgruop. "BK99
*-- delete not relevant entries---------------------- "BK99
LOOP AT i_j_1btxgruop. "BK99
CHECK i_j_1btxgruop-caller <> space "BK99
*>>>> START OF DELETION <<<<<
AND i_j_1btxgruop-caller <> cf-caller. "BK99
*>>>> END OF DELETION <<<<<<<
*>>>> START OF INSERTION <<<<
AND i_j_1btxgruop-caller <> lv_caller "698549
AND i_j_1btxgruop-caller <> cf-caller. "BK99
*>>>> END OF INSERTION <<<<<<
...
*&---------------------------------------------------------------------*

Effected Objects:


(FUNC) - J_1BCALCULATE_TAXES

(FUNC) - J_1BCALCULATE_TAXES

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 698549 has been released as well as see if the note is valid for your current SAP system landscape.

Check if SAP OSS note 698549 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 698549 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 698549 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)