Multi-level Packaging in Delivery

Before creating the packaging material you have to go to: 

IMG-Logistics Execution-Shipping -Packing.

• Define packaging material types- it can be anything like boxes crates, etc. in this you have to maintain the output determination procedure, output type, plant determination, packaging material category, generate delivery items, number assignment. you can copy from standard also.

• Then go to define material group for packaging materials - here you maintain the four digit code and the description. Actually, this group is nothing but similar products which require similar packing products. For Ex. Nokia Phones all types they are basically packed first into a polythene bag. So here nokia phones can become a material group for packaging materials and polythene bag can become the packaging material type which can include different sizes and types of polythene bags.

• Define Allowed Packaging Materials - Here you assign the shipping group for packaging materials to the packaging material type. This is related to your material master data of the packaging material which you create.

• Now go to MM01 to create a packaging material. use material type as Packaging material then inside the system will take the item category group as VERP. Then in the Basic Data1 screen you have the material group for packaging material (MGPM). Select the proper one. Now in the Sales:General/ Plant screen you have to maintain data regarding the packaging. you select the MGPM same as the basic data 1 screen, then select the packaging material type, the allowed pkh weight, allowed pkg volume. This is important because if the weight of your finished item is 2 KG and in the allowed pkg weight you enter only 1.5 KG, then while you carry out the packing process in delivery, the system will give you error," packaging weight exceeded." The assignment in the IMG creen for Define allowed packaging materials should be same as u mention in the material master. Then save your material master for packaging material.

• VA01 create the order, save it.

• VL01N enter shipping point, go to edit - pack- you will face a screen with 2 parts. In the top part you select your packaging material in which you want to pack your finished item, enter the system will assign a number to that material. Now select the Material in the top part and the finished one in the lower part and click on the Icon Pack. Here one thing has to be taken care of. Suppose if you want to pack only one finished item in one packaging material, then in the lower part of the screen you have a field for partial quantity here you change it to 1. system will prompt quantity changed. now you select the material in the top part and the one in the lower part and click on the PER PART. QTY ICON. In this way the system will pack only one finished item in a single packaging material. Packing is done go back, select the picking and do the PGI. save the delivery and create the invoice.

• HANDLING UNITS. (Used for Multi level packing) Basically handling units come into picture when you want to carry out multi level packing. suppose you want to pack Nokia phone first into a polythene bag, then this polythene bag is again packed in to box. like that. then this box will become a handling unit. For this go to : 

IMG - Logistics General - Handling Unit Management - Basics. 

First create all your packing materials using MM01 and type as packaging material. Maintain all the assignments in IMG in Logistics General.

In basics you do the same thing as you did in the packing in logistics execution. like you create the packaging material type, then MGPM and their assignment.

Then go to External Identification - and maintain the number ranges for the handling units that you want and assign the same to your packaging material type.

Now that you have done everything, create the order, save it, in VL01N, enter shipping point, go to edit - pack - do the same thing as i have told you in the step no. 6 (above). now after doing select the PACK HUs TAB . NOW IN THIS SCREEN IN THE TOP PART YOU WILL SEE THE ALREADY PACKED MATERIAL. In that same part again select your next packaging material that is BOX. enter the system will assign the number to the BOX.

Now select the material which you have just entered and the materials which were already packed in the lower part of the screen and click on the ICON PACK.

In the same way again in the top part of the screen you select your next level packaging material and press enter. the system will assign a number to it. now select the material you have just entered and the previously packed material in the lower part of the screen and click on the icon PACK.

In this way you can carry out multilevel packing. just take care of the allowed packing weight and the number of units you have to pack in the next packaging material.

Implement the Product Allocation Functionality

Configuration Overview; Allocation Specific Usage 

1.Allocation Procedure (OV1Z) The product allocation procedure is the parent of the entire allocation process. All materials that are to be included in the allocation scheme are required to have an allocation procedure assigned to it in the material master. In addition, as of release 4.0, it is in the procedure that the method of allocation is defined. The user has the opportunity to set an indicator to identify their choice of two different methods (discrete and cumulative allocation) to evaluate the quantities to be considered for product allocation. 

2.Allocation Object (OV2Z) The allocation object is the root level of the allocation process where actual data is entered and planned in LIS. The object allows the user to further break down a procedure into smaller parts for future validation of components comprising a specific material 

3.Allocation Hierarchy Mapping (OV3Z) Primarily, this transaction permits the assignment of an allocation procedure to an LIS information structure. Secondly, a character is assigned to the information structure to permit collective planning. Finally, the user can assign a step level to the procedure and information structure to sequence the order in which allocation quantities are checked. This functionality allows the user the opportunity to check product allocation against several product allocation scenarios, before the required quantity is confirmed 

4.Define Consumption Periods (OV5Z) The allocation consumption periods functionality is only valid if the allocation method flag has been set (OV1Z). If you have de-selected the method field, this functionality is not available. The consumption window indicates the number of past and future periods to be used in the allocation check. 

5.Control Product Allocation (OV4Z) In order for the allocation process to function properly, allocation control records are created primarily to map allocation procedure steps to their corresponding objects so that the allocation data records can be located for validation. Secondly, validity periods must be established to indicate when the allocation control records are active. Finally, the user has the option of establishing a conversion factor per allocation control record to accommodate BOM listings of constrained materials 

6.Activate Allocation for Requirement Class (OVZ0) In order to turn on allocation in the standard order processing functionality, the requirements class must have a flag indicating that allocation is relevant. 

7.Activate Allocation for Schedule Line Category (OVZ8) In order to turn on allocation in the standard order processing functionality, the schedule line must have a flag indicating that allocation is relevant 

8.Create Planning Hierarchy (MC61) In order to adequately establish allocation quantities, the user must initially determine the level at which the allocation is to take place and the aggregation factor of the allocation quantities. In this step, the levels for the collective allocation search procedure are also identified. 

9.Generate Masking Character (OV7Z) Upon completion of the level determination for the planning hierarchy, the collective allocation masking character must be generated to allow aggregation indicators to be established. This transaction simply reads the hierarchy established in the planning table and then generates a collective mask character for each level of the hierarchy 

10.Modify Planning Hierarchy (MC62) This step is a repeat of MC61 where the initial hierarchy was established. In order to complete the hierarchical set up, the collective allocation (mask character) hierarchy must now be maintained with the appropriate aggregation factors 

11.Allocation Procedure Assignment to Material Master (MM02) At the root level of the allocation process are the materials. Each material that is to be considered in allocation scenario must be mapped to an allocation procedure. In order entry, then, when a material is entered with a valid allocation procedure in the material master, the allocation data is verified prior to confirming the line item ordered 

12.List of Suitable Structures (OV9Z) This report is used to identify potential LIS information structures that can be used in the product allocation process. This report simply reads through the data dictionary and selects all the active information structures that contain the field product allocation object (KONOB) as the first field. This data can then be utilized in the mapping transaction (OV3Z) to link the allocation procedure step to an information structure (previous step).

Customer Hierarchy

All the customizing is in SD/Master Data/Bussiness Partner/Customers/Customers hierarchy 

1) Define hierarchy type: just put and ID and a name to the new hierarchy. 

2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this informacition, in the order, you obtain the bussiness partner for each partner function. 

3) Assign acount groups: you indicate which accounts groups are allowed for being part or your hierarchy. 

4) Assign sales areas: symple you indicate wich sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas). 

5) Assigning hierarchy type for pricing: you indicate which classes of documentos uses hierarchy in pricing determination. 

It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount. 

Customer hierarchy setup, firstly decide the hierarchy type to be used. 

The standard is type A. 

You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right? 

Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy. 

You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level. 

You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area. 

All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy 

You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all customers. If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy