SAP OSS Notes
2056968 SAP OSS Note - OKEI codes: length 4
SAP OSS Note 2056968 version 0001 contains details of a know issue related to OKEI codes: length 4 . 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 2056968 Details:
When does this problem occur
You cannot maintaine the new 4-digit codes that were added to OKEI
according to the order of Rosstandart No 1101-##.
The length of OKEI codes in SAP system shall be extended.
Cause of the problem and Pre-requisites
Legal change
Prerequisite Note: 1784853
Solution instructions
Install the support package mentioned in the section "Support Packages"
of this note or perform the attached manual steps.
Description of problem
J_3RJ_UOM_CONV
------------------------------------------------------------------------
|Manual Activity |
------------------------------------------------------------------------
|VALID FOR |
|Software Component SAP_APPL SAP Application |
| Release 600 SAPKH60001 - SAPKH60026 |
| Release 602 Until SAPKH60216 |
| Release 603 Until SAPKH60315 |
| Release 604 SAPKH60401 - SAPKH60416 |
| Release 605 Until SAPKH60513 |
| Release 606 SAPKH60601 - SAPKH60613 |
| Release 616 Until SAPKH61608 |
| Release 617 SAPKH61701 - SAPKH61705 |
------------------------------------------------------------------------
RESET N1
- SE11: Update domain OKEI:
No. Characters: 4
Output length: 4
Save and activate.
- SE11: Update view J_3RJ_UOM:
Go on menu: Utilities -> Table Maintenance Generator, press Change.
Check the reason: "Field attribute subset changed", press Continue.
Check Overview screen '1', press continue.
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 2056968 has been released as well as see if the note is valid for your current SAP system landscape.
Check if SAP OSS note 2056968 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 2056968 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 2056968 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)