BD10 — Send Material Master via ALE IDoc

BD10 generates outbound IDocs of message type MATMAS from current material master data, based on a selection screen (material number, plant, material type, and similar filters) and the active ALE distribution model. It does not itself decide who receives the data; that decision is made by the distribution model maintained separately. The one fact that explains most of the confusion around BD10 is that it is a full-snapshot push, not a change-based mechanism. Every run resends everything matching the selection to every eligible receiver, regardless of whether that receiver already has current data. Consultants used to change-pointer based distribution often expect BD10 to behave like a delta job, then are surprised by duplicate or redundant traffic when it is scheduled on a recurring basis without tight filters.

BD10 is used for manual or one-off distribution of material master data in an ALE landscape: initial load into a newly connected plant or warehouse system, resend after a receiver system was rebuilt or lost data, or ad hoc correction sends for a handful of materials during an incident. It sits upstream of any interface monitoring tool; a consultant reaches for BD10 when the requirement is to push specific materials right now, not to set up ongoing automatic distribution. For continuous synchronization the correct tool is change pointers (triggered automatically on save and flushed by a background job), not repeated manual BD10 runs. In an S/4HANA or BTP integration context, BD10 is typically the fallback used to backfill or repair data on the classic IDoc side while newer API or event-based replication handles steady-state traffic.

In SE16 on EDIDC, filter MESTYP equal to MATMAS, DIRECT equal to 2 for outbound, and CREDAT/CRETIM around the run time to find the IDocs a given BD10 execution produced. Note the DOCNUM values, then look up EDIDS for those document numbers to see the highest status reached (03 or 12 indicates successful dispatch, 29 or 51 indicates a processing error on send or receipt). Cross-check EDID4 for the E1MARAM segment under those same document numbers against MARA-MATNR to confirm exactly which materials were actually selected, since the BD10 selection screen filters silently and does not list skipped materials.

BD10 exists unchanged on S/4HANA as part of the classic ALE/IDoc stack; nothing about its selection screen or underlying logic changed. What changed is the surrounding integration strategy: for real-time or cloud-facing replication of material master data, the preferred approach is API-based or event-driven synchronization through an integration platform rather than scheduled or manual IDoc pushes. There is no Fiori app that replaces BD10 directly; it remains the tool of choice when the requirement is a classic IDoc-based backfill or correction send into an ALE-connected system.

Functional (MM/LE master data or integration team) owns the selection criteria, timing, and business justification for the send. Basis or the interface team owns the distribution model, partner profile, and port configuration, and monitors IDoc status. ABAP is involved only if custom segments or Z-fields require enhancement of the MATMAS structure. A good handover states the material numbers and receiver system involved, the resulting document numbers, and the current EDIDC/EDIDS status for each.

BD64 defines who receives MATMAS and under what filter, and should be the first thing checked when BD10 sends fewer IDocs than expected. WE20 holds the partner profile that BD10 depends on to actually create and dispatch the IDoc; a missing outbound parameter there produces a silent zero-count run. WE05 or the equivalent IDoc list is the monitoring tool to confirm what actually happened after execution. BD21 is the delta alternative to BD10 for ongoing distribution and is worth learning immediately after BD10 to avoid the full-snapshot flooding trap. Analogous send transactions exist for other master data objects, following the same distribution-model-plus-partner-profile pattern.