Do you have any question about this error?
Message type: E = Error
Message class: MM - Messages for material master maintenance and Customizing
Message number: 319
Message text: The entry INFO in screen sequence 21 does not exist
The following entries have not been imported to tables T133E and T133D
in client 000 while the system was upgraded:
Function code <LS>INFO</>
Screen sequence <LS>21</>
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Correct the error and run the program again.
Error message extract from SAP system. Copyright SAP SE.
MM319
- The entry INFO in screen sequence 21 does not exist ?The SAP error message MM319, which states "The entry INFO in screen sequence 21 does not exist," typically occurs in the context of Material Management (MM) when there is an issue with the configuration of screen sequences in the system. This error can arise during various transactions related to material documents, such as goods movements or inventory management.
Cause:
- Missing Configuration: The error usually indicates that the system is trying to access a screen sequence that has not been defined or is incomplete. Specifically, it suggests that the entry for "INFO" in screen sequence 21 is missing.
- Custom Development: If there have been custom developments or modifications to the standard SAP processes, it may lead to inconsistencies in the screen sequences.
- Transport Issues: If the configuration was transported from one system to another (e.g., from development to production), it might not have been transported correctly, leading to missing entries.
Solution:
Check Screen Sequence Configuration:
- Go to the transaction code
OMJJ
(orSPRO
-> Logistics Execution -> Inventory Management -> Goods Movement -> Define Screen Sequences).- Verify that the screen sequence 21 is correctly configured and that the entry for "INFO" exists. If it does not, you may need to create or adjust it.
Review Customizations:
- If there are custom developments, review the code to ensure that it is not referencing a non-existent screen sequence or entry.
- Consult with your ABAP developers if necessary.
Transport Validation:
- If the issue arose after a transport, check the transport logs to ensure that all necessary objects were included and correctly imported.
- If needed, re-transport the configuration or manually adjust the settings in the target system.
SAP Notes:
- Check the SAP Support Portal for any relevant SAP Notes that might address this specific error. There may be patches or updates that resolve known issues related to screen sequences.
Testing:
- After making changes, perform tests to ensure that the error no longer occurs and that the functionality is working as expected.
Related Information:
OMJJ
for screen sequence configuration and SPRO
for accessing the configuration menu.If the problem persists after following these steps, it may be beneficial to consult with SAP support or a qualified SAP consultant for further assistance.
Get instant SAP help. Start your 7-day free trial now.
MM318
Valuation data for material & provided to supplier & does not exist
What causes this issue? The system has tried to read the valuation data for the special stock type <LS>materials provided to supplier</>....
MM317
System error while calling function module &
What causes this issue? The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Syst...
MM320
The data for the user department & does not exist in table &
What causes this issue? Data has already been created for this material for the user department &V1&. However, this data has not been created...
MM321
Copy an existing material type
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.