!--a11y-->
Purpose
In cross-system flow of goods for materials subject to batch management, the batch data is transmitted at the time of the goods receipt from the source system (supplying system) to the target system (ordering and/or selling system). During the distribution, the system ensures that all batch master data relevant for keeping the batch homogeneous (for example, batch number, batch status, batch specification) is uniform across all the systems.
Data distributed includes:
If changes are made to a distributed batch in the source system, then these changes are transmitted into the target system.

If errors occur during inbound processing, you can use report RBDMANI2 to restart the posting of the relevant IDocs.
Prerequisites
For successful distribution of batch data to take place, the following prerequisites must be fulfilled:

SAP highly recommends choosing material level as the batch definition level. It does not make sense to use the plant level, as the batch number is only uniform when in connection with the plant.
To achieve this, proceed as follows:
For more detailed information, see Customizing for Batch Management under Batch Number Assignment -> Maintain Internal Batch Number Assignment Range / Maintain Number Range for External Assignment of Batch Numbers.
Features
Changing Batch Data
After a batch has been distributed, you can only change the fields in the target system that are not relevant for distribution. To do this, choose Logistics ® Central Functions ® Batch Management ® Batch ® Change.
The following data is not distribution-relevant, and can be changed in any of the systems:
The administrative data are changed automatically in the corresponding systems at distribution:
If you want to change the distribution-relevant attributes of a batch (for example, the batch status) locally (in one system), you can:
Information About Distributing Batches
The system displays information about distribution in the batch master (MSC2N and MSC3N) on the Basic Data 2 tab page.
Decoupling
If you make changes to distribution-relevant data of a batch in a target system, then the batch is decoupled from the source system.
For decoupling to take place, the following prerequisites must be fulfilled:
The authorization object for decoupling is M_MATE_DCP.
After a decoupling has taken place

You can use the user exit EXIT_SAPLVBWC_001 (Enhancement VBWC_DCP) to define which materials and/or which business processes can be decoupled.
Recursivity
In the case of recursivity, i.e. when a system is both the distributing and the receiving system, distribution is stopped in order to prevent a never-ending loop.
Batch Usage
The batch where-used list (Logistics ® Central Functions ® Batch Management ® Batch Usage ® Display) can evaluate the administration records of the distributed batches (indicator: Cross-System Goods Movements). Using RFC, the evaluation of these control records takes place in both directions, that is to say, bottom-up in the receiving system and top-down in the distributing system.
Taking Account of Global and Local Characteristics
Generally speaking, the batch classes and the characteristics assigned to them must be identical in all the systems involved in a transaction. If it is necessary to include additional characteristics in the batch class in one system, then these characteristics must be flagged as Local. Local characteristics can be valuated without decoupling the batch.
To flag a characteristic as Local, you need to make the following settings:
Rules-Based ATP
In the rules-based ATP check, the batch that was entered in the sales order is not considered for transfer, because generally this batch is not valid for the product and/or the location to transfer.
However, you can use the user exit EXIT_/SAPAPO/SAPLATPT_001 (enhancement APOAT001) to define that the batch is passed on to the transfer.