Article Directory
Through the introduction of the basic configuration and simple functions of batch derivation, you should have a basic understanding of batch derivation. This article discusses its functions in more depth from the two dimensions of batch derivation type and batch derivation direction.
1. Derived type
Derived types are defined in derived events. There are many standard events here, but only selection events can be performed here, and the acceptance and sending rules of events can be customized.Configuration path: SPRO-Logistics General-Batch Management-Batch Data Derivation-Define Derivation Events. Or execute transaction code: DVC8.
1.1 Static derivation
The receiver's batch will be changed by the sender's batch characteristics according to the transmission settings. As long as the sending batch has characteristics and the receiving batch is created, the characteristics of the receiving batch will be automatically changed. We have shown the effect in the first article, and we will not demonstrate it here. For specific articles, you can refer to the Part1 article derived from the batch. Link: SAP Batch Derivation from Abandonment to Entry Series - Batch Derivation-Part1
1.2 Dynamic Derivation
The batch properties of the receiver will not be changed immediately, and the batch properties of the sender are only used as reference decision values. (In order to prevent the configuration from affecting the effect, it is recommended that the derived event configuration only retain the event of the production order being released).
Looking at the batch, the classification data of the batch did not generate feature values, only corresponding suggestions were generated when the batch was derived. There is no direct update of the properties of the received batches in a static way.
Second, the direction of derivation
According to the different directions of batch attribute derivation, it can be divided into two modes: Pull Derivation and Push Derivation.
Pull Derivation refers to a business scenario in which attributes of multiple component batches are derived into one product batch;
Push Derivation refers to a batch with only one component derived into batches of multiple products.
According to this definition, it can be seen that it is the mapping relationship during batch derivation, mainly to distinguish between many-to-one and 1-to-many derivation relationships.
According to the above definition, it can be seen that the usage scenarios are as follows: Pull Derivation is generally an input of multiple components and only one output. Push Derivation is an input with only one component, and multiple products when it is output.
Push Derivation can be triggered by 100-usage decision, 700-manual derivation, 900-customer-defined event.
Pull Derivation can be triggered by 100-usage decision, 200-production order release, 300-batch record, 400-production order receipt, 700-manual derivation, 900-customer-defined event.
For the two operating modes, you can refer to the SAP standard help document, which contains very detailed examples for reference.
Address: Link: Batch Derivation
also shares a test blog written by others: https://blogs.sap.com/2013/02/18/batch-derivation-overview-with-example/