SAP® Documentation

Single view

/SAPAPO/CL_EOGL_ROUNDING_EXMPL - Example Implementation: /SAPAPO/EOGL_ROUNDING

PERFORM Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

This class represents an implementation example for BAdI /SAPAPO/EOGL_ROUNDING.

This function is based on characteristics that contain the number of delivered lengths in the case of requirements, or the number of expected lengths in the case of receipts. This is just one possible solution.

When posting deliveries or goods receipts in ERP, the valuations of the characteristics must be adjusted accordingly. It is thus possible to round the quantities correctly in the methods described here.

Caution

Note that using characteristics in this manner has the following disadvantages:

(In this example, the characteristic posted_demand_lengths is used and adjusted after each delivery.)

  • If you create a receipt for the requirement, the receipt gets the same valuation of characteristic posted_demand_lengths.
  • If the characteristic valuation changes for the requirement, the receipt no longer matches. To avoid this, the requirement must have suitable selection criteria for the characteristic (for example, 0 to number of desired lengths).
  • The lot-sizing procedures Fixed, Periodic and Multiple-Output-Planning cannot be used because these procedures group the requirements according to characteristic valuations to create lots for identical products. The posted_demand_lengths characteristic would distort this grouping and cause many groups.
  • If planned orders are created for in-house production, the characteristic is transferred to the independent requirements of the components and causes the same problems as at the higher level. However, this is even more problematic because the automatically generated selection criteria would go from 5 to 5 if the valuation at that point in time was 5. The propagation of the characteristic could be avoided if a different class is used for the components that does not contain this characteristic.

Due to these disadvantages, we recommend that you consult with Solution Management regarding the usability of this example. In addition to using characteristics, another possible solution would be to use a customer-specific table.

Relationships

Example

Notes

Further information






General Material Data   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 2759 Date: 20190626 Time: 215303     sap01-206 ( 60 ms )

Our Service

Looking for Support? Questions?

The

Consolut

Callback-Service

Leave us your contact details and we will call you back. Panels marked with * are mandatory.