SAP OSS Note 351755 version 0003 contains details of a know issue related to Lockbox IDOC MICR update session error . 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 351755 Details:
When does this problem occur
Processing of the lockbox data from IDOC delivery creates a MICR update
session. The processing of the MICR update session must be don
e with manual intervention because the country of the bank details to
insert is not filled in the batch session.
Cause of the problem and Pre-requisites
Oversight
Solution instructions
The country of the MICR details is determined from country assignment of
the company code of the lockbox. The IDOC delivery fills the
company code of the Lockbox data for processing in field FEBKO-BUKRS.
This is the company code of the configuration table t049a which
has been rendered from the origin and destination values.
See attached code correction
Description of problem
FINSTA LOCKBX KNBNK-BANKS MICR
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 351755 has been released as well as see if the note is valid for your current SAP system landscape.
Check if SAP OSS note 351755 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
From here you can just enter the note number 351755 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 351755 does not exist on your system you will receive the message "Unable to find SAP Note that meets specified criteria"
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)