Do you have any question about this error?
Message type: E = Error
Message class: J1B_NFE - Message class for NF-e
Message number: 344
Message text: Movement type could not be determined using delivery type
When processing the data from the incoming XML sent by <ZK>SAP
BusinessObjects Nota Fiscal Eletr(nica</>, your SAP system tried to
determine the correct goods movement type for the items in the nota
fiscal. However, the relevant settings are missing in your Customizing.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check that the correct Customizing settings have been made for this
Incoming NF-e process in the <LS>Assign Delivery Type to Incoming NF-e
Process</> Customizing activity in the Customizing for <LS>Incoming NF-e
Automation</> under <LS>Cross-Application Components</> -> <LS>General
Application Functions</> -> <LS>Nota Fiscal</> -> <LS>Electronic Notas
Fiscais (NF-e)</>.
Error message extract from SAP system. Copyright SAP SE.
J1B_NFE344
- Movement type could not be determined using delivery type ?The SAP error message J1B_NFE344, which states "Movement type could not be determined using delivery type," typically occurs in the context of Brazil's Nota Fiscal (NF-e) process. This error indicates that the system is unable to determine the appropriate movement type for a given delivery type during the processing of a Nota Fiscal.
Causes:
Configuration Issues: The movement type may not be properly configured in the system for the specific delivery type being used. This can happen if the necessary settings in the customizing (SPRO) are not correctly defined.
Missing Entries: There may be missing entries in the configuration tables that link delivery types to movement types. This can occur if the system has not been set up to recognize the specific combination of delivery type and movement type.
Incorrect Delivery Type: The delivery type being used may not be valid for the transaction or may not have an associated movement type defined in the system.
Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the required configuration settings.
Solutions:
Check Configuration:
- Go to the SAP customizing transaction (SPRO) and navigate to the relevant configuration for delivery types and movement types.
- Ensure that the delivery type in question is correctly linked to a movement type in the configuration settings.
Maintain Movement Type:
- Use transaction code
OMJJ
to maintain movement types. Check if the movement type is defined for the delivery type you are using.- If it is missing, you may need to create or modify the entry to ensure that the system can determine the movement type.
Review Delivery Type:
- Verify that the delivery type being used is correct and appropriate for the transaction. If necessary, consult with your logistics or supply chain team to confirm the correct delivery type.
Check User Authorizations:
- Ensure that the user has the necessary authorizations to perform the transaction and access the relevant configuration settings.
Consult Documentation:
- Review SAP documentation or notes related to Nota Fiscal and movement types for any specific requirements or updates that may affect your configuration.
Testing:
- After making changes, perform a test transaction to ensure that the error is resolved and that the movement type is now being determined correctly.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
J1B_NFE343
Error in BAdI implementation; no data returned
What causes this issue? The logic in your implementation of the <ZK>Conversions for Incoming NF-e Automation</> Business Add-In (BAdI) di...
J1B_NFE342
Error in BAdI implement.; items in NF-e &1 do not match delivery items
What causes this issue? The logic in your implementation of the <ZK>Conversions for Incoming NF-e Automation</> Business Add-In (BAdI) ha...
J1B_NFE345
Expected &1 tax rate is &2 but tax rate in XML is &3
What causes this issue? You have tried to run an invoice or NF-e simulation in <LS>SAP BusinessObjects Nota Fiscal Electr(nica</>. During...
J1B_NFE346
&1 tax not available in XML for purchase order item &2 &3 xml pos. &4
What causes this issue? You have tried to run an invoice or NF-e simulation in <LS>SAP BusinessObjects Nota Fiscal Electr(nica</>. During...
Click on this link to search all SAP messages.