Pull Derivation (1 Receiver, n Sender)
Purpose
The derivation is triggered from a transaction that affects the product. Here, data from various senders can be collected, cumulated, and calculated. Within a derivation according to the pull principle, there can only be one receiver, but there can be several senders (example usage: pick and pack for pharmaceutical products).
Prerequisites
For more information, see
Prerequisites for Batch Derivation.Features
Range of the Derivation
You can derive the following fields:
In order that the field and characteristic values can be successfully transferred, the master fields and the characteristics of the batches involved in the derivation must be identical.
Data that cannot be displayed using these fields with regards to having the same names (for example, different characteristics), but which should still be transferred, can be integrated into the derivation using the Business Add-In Derivation (method SENDER_VALUES_CHANGE). This gives you more flexibility when constructing the type and range of the data to be derived, depending on the information required.
For more information, see Customizing for Batch Management under Derivation of Batch Data ® Business Add-In: Derivation.
You specify the fields and characteristic values that to derive in the condition records.
Derivation Rules for Receiver Batches
When maintaining receiver condition records, you can specify whether, during a derivation, you want to allow sender attributes without content, or overwriting of already filled receiver attributes.
The system also offers several rules for the attributes, which enable an automatic, rule-based derivation where there are conflicting sender values.
You can maintain receiver condition records by choosing:
Derivation Events
A pull derivation can be triggered at the following events:
When you make the usage decision, the derivation is triggered in the background.
The event "usage decision" does not include the
Automatic Usage Decision
After you have released the process/production order, you can trigger the derivation by choosing 
on the Goods Receipt tab page. If a header batch exists, the derivation occurs automatically.
When you create or change a version, a derivation is triggered automatically.
When you post the production order, the derivation is triggered in the background.
A derivation is also triggered when you post a goods receipt for a run schedule header.
You perform a manual derivation by choosing Logistics ® Central Functions ® Batch Management ® Batch Derivation ® Manual Derivation.
For more information, see
You can use this derivation event if you do not want to run the derivation as for one of the standard events. To do this, you can, for example, call the derivation in a suitable user exit.
You maintain the required derivation events in Customizing for Batch Management under Derivation of Batch Data ® Define Derivation Events.
See also:
Deriving the Production Date in Orders - Example