topic Re: sd in Application Development and Automation Discussions

sd

Former Member — Fri, 25 Jan 2008 06:49:08 GMT

what is allocation, what is depo commercials can any one explain me about this two.

thanks

alka

Re: sd

Former Member — Fri, 25 Jan 2008 06:58:47 GMT

For documentation, please refer below link:

http://help.sap.com/erp2005_ehp_02/helpdata/en/93/744d12546011d1a7020000e829fd11/frameset.htm

http://help.sap.com/saphelp_47x200/helpdata/en/93/744d1f546011d1a7020000e829fd11/content.htm

http://help.sap.com/saphelp_47x200/helpdata/en/93/744d2c546011d1a7020000e829fd11/content.htm

Please see if the following helps:

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).

http://help.sap.com/saphelp_47x200/helpdata/en/93/744d12546011d1a7020000e829fd11/frameset.htm

Regards.

Re: sd

Former Member — Fri, 25 Jan 2008 07:01:51 GMT

Check this link.

http://www.sap-img.com/sap-sd/implement-the-product-allocation-functionality.htm

Also check this thread for Depot sales process

Regards,

Maha

Re: sd

Former Member — Fri, 25 Jan 2008 07:02:22 GMT

In a sense, allocation, assessment and distribution mean the same.

Allocation and distribution are the terms used in BPS / IP and assessment is used in FICO in R/3.

What they do is read the key figures from one object ( say cost center) and post it to another object ( may be one cost centre or several costr centres) based on some logic like no of employees, usuage of a material, etc.

You get more abut these at:

http://help.sap.com/saphelp_47x200/helpdata/en/5b/d2200743c611d182b30000e829fbfe/frameset.htm

http://help.sap.com/saphelp_sem350bw/helpdata/en/05/242537cedf2056e10000009b38f936/frameset.htm

Depo we well configur as delivering plant

Whenever you need to transfer the materials from one plant to another plant belonging to one company or belonging to two company code stock transfer order is raised by the delivering company.

STO:

Transfer of goods from one location to another location,it may be between plants within the same company code or in different company code's plants.

within the company code,bet plants, receiving plant will raise the STO in Supplying/issuing plant-ME21n,

Supplying plant will deliver the goods to receiving plants , then we need to pick n post the Goods Issue-VL02n, nw when we can observe that the STO qtty will be added into receiving plant and reduced in Delievering plant.

Configure Intercompany Stock Transport Order

Material should exist in both the plants (Delivering & Ordering),

Internal customer should be assaigned to the ordering plant ( MM -> Purchasing -> Purchase Order -> Setup stock transport order -> assign the internal customer to the ordering plant and assign the Sales area of the internal customer.

Assign its Sales area to the delivering plant

Assign the document type and Delivery type NB and NLCC

Assign the Supplying plant --> Receiving Plant --> NB

Take the delivering plant and assign the sales area.

Vendor master has to be created and assaign the supply source ( Delivering Plant).

Create a puchase order ME21N ---> Save

Delivery VL10 G ---> Calculation rule (appropriate) --> Assaign the purchase order number here nt. and execute.

Select the Delivery creation line and do the back ground process.

Start the log display and see the delivery document number by the documents button

plzz reward if it is usefull to u in any way