consolut - /SAPAPO/FOT_CALCULATE_PRODCH - Function module with Split algorithm

/SAPAPO/FOT_CALCULATE_PRODCH - Function module with Split algorithm

BAL_S_LOG - Application Log: Log header data CPI1466 during Backup
This documentation is copyright by SAP AG.

Functionality

Algorithm for calculating Order quantities, confirmation quantities, and GM/ACT data transfer quantities during the FOT action "Product Change"

Change the final product of an order.

There are three ways to Change the product of an order,-- distinguished from the field LS_FOTMOD-WIPMOVE in the subroutine: PRODCH_SOFT_MAPPING.

HARD Product Change:,,No WIP allowed at a RP that does not have a mapping.
Soft UP :,,WIP from non-mapped RPs is added to the earlier mapped RP: The mapping for non-mapped RPs is added to accomplish this task.
Soft DOWN:,,WIP from non-mapped RPs is added to the succeeding mapped RP: The mapping for non-mapped RPs is added to accomplish this task.

DIFFERENT UNITS OF MEASURE HANDLING:

This function module takes care of the unit of measure changes between the orders, as well as the reporting point quantities in the order in the following manner:

The Source order header unit is used as the base unit of measure (BASEUNIT) in the order.

All the quantities in the order are converted to the base unit before calculations. The unit ofmeasure conversion must be defined in the original order's material master or in the configuration.If configuration also has the conversion factor defined for the two units in question, then the material master conversion factor will be over-written by the one defined in the configuration.

If the target order header unit is different from the parent order header unit, the conversion factor defined in the two material masters must be same, otherwise the transaction will abort.

If there are different units of measure used in the target order reporting points, their conversionfactor to the source order header unit must be defined either in the original order material master, or the configuration.

All the quantities are calculated after converting the quantities in baseunit, and then the calculated quantities are converted back to their respective units of measures.

The information of the Original (source) order and Resulting (target) orders is sent in the table CT_ORDERS.

CT_ORDERS has nested RP (reporting point) structure CT_ORDERS-RP_TAB

RP_TAB has nested:

GM (Goods Movement) for particular RP

ACT (Activity / resource utilization) for a particular RP

CT_ORDERS-MAIN_ORDER = 'X' identifies the Source order (Original )

CT_ORDERS-MAIN_ORDER = ' ' identifies the target order (resulting)

CT_ORDERS-ORD_STATUS = Determines the level of the transaction

Example

One order's final product is changed and the new order structure is different, so the algorithm determineswhich quantities from which reporting point go to which new reporting point based on the mapping information provided in the mapping table.

Scenario example:

Mapping Table
FR--TO
A1--B1
A2--B4
A3--B4
A4--B4
A5--B7
Original order	Resulting Order
ORDER_A		ORDER_B
RP	WIP	RP	WIP
A1	15	B1	15
A2	10	B2	0
A3	10	B3	0
A4	10	B4	30
A5	25	B5	0
	B6	0
	B7	25

Note:

The Components and Resources attached to particular reporting points will also be transferred to the resulting order based on the mapping table information.