Deriving the Production Date in Orders – Example (SAP Library

Deriving the Production Date in Orders – Example

Deriving Production Date and Expiration Date - Example

In this example, in the first derivation (highlighted red on the screen), the system determines the production date of batch B from the minimum production dates of batches D and G. Afterwards, the system uses this production date and the expiration date from the material master data for B to calculate the shelf life expiration date for B.

This derivation is executed in the event process order. The production dates for D and G have already been maintained at this point.

In the second derivation (green), both dates are transferred from batch B to batch A. This derivation takes place in a further order.

This graphic is explained in the accompanying text

Activities

Customizing

To assign the standard search procedures BDR001 for receiver search and BDS001 for sender search to the derivation event process order, choose Batch Derivation ® Condition Technique ® Assign Search Procedures to Derivation Events.

When the system subsequently searches for a receiver condition record during derivation, it uses the search procedure BDR001, and therefore searches:

Using the material number of the batch that is currently being processed
Then, using the material type

When it looks for a sender condition record using search procedure BDS001, it searches:

Using the material number of the component batch and the material number of the batch that is currently being processed
Then, using only the material number of the component batch

That means that when checking in the first derivation whether D is a sender batch, the system would search for a condition record:

Using material number_D + material number_B

Then, using only material number_D as a key

Maintaining Condition Records

Create two receiver condition records for the strategy type BDR1 and key combination receiver material number using Create (receiver condition type): Fast Entry

Key = material number_A

On the Detail screen, maintain the attributes HSDAT and VFDAT.

The following rules are defined for the attributes:

Attribute HSDAT	Attribute VFDAT
Sender field empty = Error	Sender field empty = Error
Selection rule = Minimum	Selection rule = Minimum
Levels in BWU List = 2	Levels in BWU List = 2

Key = material number_B

On the Detail screen, maintain the attribute HSDAT that is to be received.

The following rules are defined for the attribute:

Attribute HSDAT

Sender field empty = Error

Selection rule = Minimum

Create three sender condition records for the strategy type BDS1 using Create (sender condition type): Fast Entry.

Two of those sender condition records are created with the key combination sender material number:

Key	Attribute
Material number_D	HSDAT
Material number_G	HSDAT

A third sender condition record is created with the key combination receiver material number + sender material number.

Key	Attribute
Material number_B \| Material number_A	HSDAT

Note

If this record was created with the key combination sender material number, it would already send to itself in the first derivation.

In order to restrict this condition record to the second derivation, the material number of the receiver batch is also used as key to the condition record.

Order Maintenance

A manufacturing order is created in order to produce batch B. After batch B in the display has been booked in for goods receipt, the derivation is performed after each save of the order.

During the derivation for batch B, the system finds the second receiver condition record, as described above. This condition record specifies that the production date should be derived.

Note

Special functionality when deriving the production date:

If the shelf life data is maintained in the material master, the expiration date will be calculated.

To derive the production date for batch B, the system searches for sender batches in the extended batch where-used list of batch B. During this search, the system uses condition technique to look for a sender condition record for each of the batches from the extended batch where-used list.

Note

The extended batch where-used list is not only based on posted goods movements but also on expected goods movements.

The condition technique finds condition records for batches D and G.

The system uses the contents of both HSDAT fields to determine the minimum, and checks that none of the sender fields was empty. If the production date is successfully derived, and if the shelf life data is maintained for batch B, then the system also calculates the shelf life expiration date.

A dialog box informs the user that a derivation has been carried out.

(In Customizing for Batch Management under Derivation of Batch Data ® Define Derivation Events, you define whether a dialog box appears.)

You can display the result of the derivation in detail.

The derivation is saved along with the order, unless the user does not save the order.

Changes are only made to batch B if the derivation is successful, or has ended with a warning. If an error has occurred, for example because a sender field was empty, then batch B is not changed, but the derivation is saved.

In a similar way, the expiration date and the production date are transferred from batch B to batch A in the order that produces batch A. In this derivation, the batch where-used list is only evaluated down to the second level. Therefore, batches D and G will not send again in this derivation.