SAP Knowledge Base Article - Preview

3730072 - Billing document output via EDI returns error B1128 - 'A message type could not be (uniquely) identified'

Symptom

  • Invoices are stuck without IDoc generated for output type.
  • Error during processing: "A message type could not be (uniquely) identified" (Message no. B1128).


Read more...

Environment

•Sales And Distribution (SD)
•Logistics Execution (LE)
•SAP R/3 •SAP R/3 Enterprise 4.7
•SAP ERP Central Component
•SAP ERP
•SAP Enhancement package for SAP ERP
•SAP Enhancement package for SAP ERP, version for SAP HANA
•SAP S/4HANA
•S/4HANA Cloud Private Edition

Product

SAP ERP Central Component all versions ; SAP ERP all versions ; SAP R/3 all versions ; SAP S/4HANA Cloud Private Edition all versions ; SAP S/4HANA all versions ; SAP enhancement package for SAP ERP all versions ; SAP enhancement package for SAP ERP, version for SAP HANA all versions

Keywords

VF31, RSNAST00, idoc not created, message no. B1128, message type not uniquely identified, edp12, partner profile, ls partner type, message control, sd billing output, invoice output, duplicate entries, we20, ale output, VF01, WE19, WE02, BD87. , KBA , SD-BIL-IV , Processing Billing Documents , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.