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

/SAPAPO/FOT_CALCULATE_SPLIT - Function module with Split algorithm

Vendor Master (General Section) General Data in Customer Master
This documentation is copyright by SAP AG.

Functionality

Split One order into several orders.

There are three ways to Split an order,-- distinguished from the field LS_FOTMOD-WIPMOVE in the subroutine: SPLIT_SOFT_MAPPING.

HARD split:,,No WIP allowed at a RP which does not have a mapping.
Soft UP :,,If SPLIT quantity from a reporting point is greater than the WIP available at that RP, theextra WIP from next non-mapped RPs is added to this RP: The mapping for non-mapped RPs is added to accomplish this task.
Soft DOWN:,,If SPLIT quantity from a reporting point is greater than the WIP available at that RP, theextra WIP from previous non-mapped RPs is added to this 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 parent order header quantity 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 child order header unit is different from the parent order header unit (different material), 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 child order reporting points, their conversionfactor to the parent order header unit must be defined either in the parent 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 WIP transfer quantities (WIPQUANT in CT_MAP) may also have a different unit than the parentorder header unit, but the same restriction applies here as well: the conversion factor must be defined either in the parent material master or the configuration.

The information of the Original (parent) order and Resulting (child) 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 Parent order (Original / Main resulting)

CT_ORDERS-MAIN_ORDER = ' ' identifies the Child orders (resulting)

CT_ORDERS-ORD_STATUS = Determines the level of the transaction

Example

Scenario example:

Mapping Table		Parent Order
FR--TO	WIPQUANT		RP	WIP
A1--B1	18		A1	18
A2--B1	10		A2	17
A2--C2	4		A3	55
A3--B4	5
A3--C3	18

Child order1		Child Order2		New Parent Order
ORDER_B		ORDER_C		ORDER_A
RP	WIP	RP	WIP	RP	WIP
B1	28	C1		A1	0
B2		C2	4	A2	3
B3		C3	18	A3	32
B4	5

Note:

The Components and Resources attached to particular reporting points will also be transferred to theChild orders based on the mapping table information and the quantities proportionately. The WIP transferquantities in the mapping table are used to calculate the proportional GM/ACT quantities at reportingpoints. If the algorithm determines that some of the GR quantity is also to be transferred to child orders, the GR transfer quantity is used to calculate the GM/ACT transfer quantities.