Re-Allocation Process

Hi all
Please provide me the Re-Allocation / Allocation process in IS-retail...
Thanks
Karamjit Singh
9899022368

Hello Karamjit,
what exactly do you want to do? This is not clear from your question. Do you have a specific situation that you want to resolve?
Regards,
Smitha

Similar Messages

Actual Template Allocation - Process Order Handling

Hi all
Could somebody give me some input to an issue I am facing.
I am working on a best practice baseline for Chemicals and have setup a Template to allocate overheads to materials. The allocation is fixed no matter the lot size of the process order.
At month end when running the closing process I use the transaction CPTD to allocate the actual template overhead to each process order.
However this transaction picks up and re-allocates overhead to process orders already confirmed, delivered and settled.
This is of course not what I expected as these orders have been fully completed, so I am thinking that I am missing step in closing down the process orders correctly.
Is there a status on the process order that will cause that order to be excluded from the CPTD, or am I missing some configuration?
Thank you in advance
/Thorben Hald
2C change A/S
Denmark

Hi
I am using environment 9 yes.
My formula is very simple:
On Object I have:
SenderCostCenter = '130570' AND
SenderActivityType = 'LABORA'
And then I have simply put "1" in Plan Quantity and Actual Quantity.
So what it does is it allocates the unit cost of the combination of cost center 130570 and act. type LABORA one time to each material/order no matter lot size.
Should I perhaps have put "1" into the Plan Fix and Actual Fix instead?
Thanks

GL Reporting /FSG report/Allocation process SLOW

Team,
My users are experiencing slowness during running reports.
Oracle 10.2.0.3
Ebs 11i(11.5.10.2 CU2)
RHEL 4.4
10 years of data
Please advice what need to looks.

No, a different row order is being used in this report. I have created several different row orders to use with this report and the results are the same.

Help on Crossjoin Syntax Please on ASO Allocation

Hi,
Tyring to run an ASO Allocation via MaxL. I always have trouble with syntax on CrossJoins for some reason. When I run the below I get an error:
ERROR - 1260052 - Syntax error in input MDX query on line 1 at token ')' .
ERROR - 1241192 - Allocation terminated with Essbase error 1260052 in AMOUNT.
execute allocation process on database appname.dbname with
pov
"Crossjoin(Descendants([Total Year],[Year].levels(0)),
Crossjoin(Descendants([YearTotal],[Period].levels(0)),
Crossjoin(Descendants([Version],[Version].levels(0)),
Crossjoin(Descendants([Total Product],[Product].levels(0)),
Descendants([Total Employee],[Employee].levels(0)) ))))"
amount "([NET INCOME/(LOSS)],[Actual])"
target "([OH_Per_Unit],[AllocAct])"
range "Descendants([Total Entity],[Entity].levels(0))"
basis "([Funded Units],[Actual])"
share;
logout;

This is something which I've done
execute allocation process on database smp.smp with
pov 'Crossjoin(Crossjoin(Crossjoin(Crossjoin(Crossjoin(Crossjoin(Crossjoin({Descendants([AC_10000], [Accounts].Levels(0))},{&ActualMonth}),{&ActualYear}),{Descendants([Input Currency], [Currency].Levels(0))}),{Descendants([no entity], [Entity].Levels(0))}),{Descendants([Country Code], [Country Code].Levels(0))}),{Descendants([cost center], [Cost Center].Levels(0))}),{Descendants([Source], [Source].Levels(0))})'
amount '([PRTOT], [Actual], [All Clients], [Act_Tot], [Final])'
target ""
range 'Crossjoin(Crossjoin(Crossjoin(Crossjoin({Descendants([Working], [Version].Levels(0))},{Descendants([Plan], [Scenario].Levels(0))}),{Descendants([100-10], [Product].Levels(0))}),{Descendants([cl_cola], [Client].Levels(0))}),{Descendants([act_12121], [Activity].Levels(0))})'
spread;You cannot paste your code, calc manager provides a GUI version of allocate command where you can just type in your members.
Regards
Celvin
http://www.orahyplabs.com
Please mark the responses as helpful/correct if applicable
Edited by: Celvin Kattookaran on Apr 11, 2013 2:16 PM

ASO Allocation Maxl error

Syntax error in input mdx query on line 1 token ","
Allocation terminated with essbase error 1260052 in POV
execute allocation process on database ASOALLOC.ALLOCAT with
pov "crossjoin([Year].[FY10],
crossjoin([period].[Jan],
crossjoin([account].[a111],
([Entity],[Entity].levels(0)))))"
amount "([account].[a111]"
target ""
range "{[Entity].[e222]}"
spread;
Edited by: mb021059 on Oct 13, 2010 5:13 AM
Edited by: mb021059 on Oct 13, 2010 6:53 AM
Edited by: mb021059 on Oct 13, 2010 7:00 AM

I really don't understand what you are trying to do (may be because you are in 11 version{allocation in ASO cube sounds kool).
but I can tell you the syntax error you are getting at first line.
change it to:
"crossjoin([Year].[FY10],crossjoin([period].[Jan],crossjoin([account].[a111],[Entity].levels(0))))"
Thanks,
Jeeth
Edited by: Jithendra on Oct 14, 2010 5:20 PM

BPC 7.5 NW -- Allocation Issue -- Good Illustration

Hi all,
I've been struggling with a fundamental issue with the way the Allocation process works on the Netweaver platform. But, this might be an easy way to illustrate the problem.
This data is typical representative what has been loaded to a test area for 2007.APR:
ACCOUNTGL     CO_CODE      FUNC_AREA              COSTCENTER      2007.APR
A54442000     N001                     S413201                CC01000                           -
A54442000     N001                     S413264                     CC01004                  97,436
A54442000     N001                     S413264                     CC01027                    9,588
A54443000     N001                     S413266                     CC01004                         33
The basic goal of the allocation is to distribute in some of those GL Accounts and Costcenters to other company codes/subsidiaries. These are mostly general-purpose services accounts, such as legal services that are provided by the parent, etc.
The problem is that after the allocation is run, the amounts in ACCOUNTGL, COSTCENTER, and FUNC_AREA are spread to essentially all base-level members and not just the ones that had data initially, this (A.) generates so many records as to almost render allocations unusable, and (B.) duplicates a lot of data. Here's a sample of after the allocation is run:
                   CC01000 CC01004 CC01027
S101011             6,256.31 6,256.31      6,256.31
S101021          6,256.31 6,256.31      6,256.31
S101031          6,256.31      6,256.31      6,256.31
S104001          6,256.31      6,256.31      6,256.31
As you can see above, all the cost centers got an allocation of about 6% of the total (which is the correct value), but it should have been in proportion to what they had originally. Meanwhile the FUNC_AREA/S-Accounts all got this value written to them as well.
Beyond the How-To Guides, does anyone have any specific pointers on how the allocation engine works on the NW platform? It seems to behave a bit differently than on Microsoft.
Thanks,
Garrett

Hi Garrett,
It would be helpful if you could provide the allocation script that resulted in this data. Then maybe we can recommend changes that will help you or better understand what you are attempting. I realize you have shared your scripts in other threads, but it would be best to get the script and the example data together in one place.
It seems clear that you don't want the value duplicated across the accounts, but you can probably control that in your allocation script. Further, it should be possible to allocated based on existing data by using a USING/TOTAL factor, but Gersh has indicated that there might be a problem here, and possibly a BPC bug.
Regarding differences between NW and MS allocations, yes, the statement behaves differently in the two systems. The biggest difference is that the NW version allocation functionality only works for disaggregation, not for driver-based allocations. What that means is that in the NW version, if you have multiple members in the WHAT= section, the values in these members will be added up and allocated out to all the members in the WHERE= section. I believe this differs from the behavior in the MS version which would run the allocation separately if lists of members were provided in the WHAT and WHERE sections.
If you want to do a driver-based model in the NW version, you will need to use MDX or WHEN/IS/*REC statements, but in this case it seems you are trying to distribute overhead costs to subsidiaries, which is a disaggregation activity and should be possible using NW version allocations.
Ethan

Allocation Question -- Selecting Non-zero Dimension Members?

Hi experts,
(BPC 7.5 NW) During an Allocation process, if you have a dimension, such as COSTCENTER for which only some members have data (in my case, about 400 of 700), which is not the driver dimension and you'd like to have the Allocation write back to those same members, while leaving the blank ones blank, is there some special process?
In this example, you can see it selecting the CC's which are <> NO_COSTCENTER, but USING the Allocation rate, which as a stat account is stored in NO_COSTCENTER.
So, it all works, except that the logic function writes a percentage to all three CC's specified in the *XDIM_MEMBERSET, even if there were initially values in only one or two. Is there any way to have it write only to the ones that were initially populated/non-zero?
===================================================================================
*XDIM_MEMBERSET ACCOUNTGL=A54442000,A54443000,A59989000,ALLOC_0702
*XDIM_MEMBERSET COSTCENTER=CC01000,CC01004,CC01027,NO_COSTCENTER
*XDIM_MEMBERSET CATEGORY=ACTUAL
*XDIM_MEMBERSET CO_CODE=C001
*XDIM_MEMBERSET TIME=2007.APR
*RUNALLOCATION
*FACTOR=USING
*DIM COSTCENTER WHAT<->NO_COSTCENTER; WHERE<->NO_COSTCENTER; USING=NO_COSTCENTER
*DIM ACCOUNTGL WHAT=A54442000,A54443000; WHERE=A59989000; USING=ALLOC_0702
*ENDALLOCATION
*COMMIT
Edited by: Garrett Tedeman on Nov 4, 2010 6:59 PM
Edited by: Garrett Tedeman on Nov 4, 2010 7:24 PM
Update -- Just discovered that the "AMOUNT" keyword, which was used on the MS version, will not validate on BPC 7.5 NW.

Hi Garrett,
I'm not sure I understood what is the problem here: is it that allocation overrides some existing values on those Cost centers and Account A59989000 or you just don't like those records with zeroes?
If it's the last one, that just run light optimization and check that zero elimination is turned on. It will delete your records with zeros.
If it's the first one, that common practice is to use additional Dimension (DATASRC for example) and populate it with some value for all Cost centers from which you taking data (INPUT for example); than include it in allocation with WHAT = INPUT. You have to define additional member in that dimension (RESLT for example) and put WHERE = RESLT in allocation. By using this technique you achieve at least two benefits:you don't override existing values and you can run allocation as many times as you want without deleting results of previous allocations. You don't have to use that dimension in your reports and data will be just summarized across that Dimension.
Please let me know if you had something different in mind.
Regards,
Gersh

Move In Standard Workflow (ISUACBMOVEIN) : Automatic Owner Allocation Proc.

Hello Experts,
In the automatic owner allocation process, when we move out the tenant the owner is supposed to automatically move in with the pre-configured offset. In my case the workflow was not being triggerred so we defined the the linkage of the events (tcode: SWETYPV). After doing this we got an exception
"Object MOVEINDOC method MOVEINOFOWNERCREATENODIALOG cannot be executed" with error EQ067 (Check the reference for move-in document &1).
When I see the standard workflow I see that it analyses Contract Account and verifies what category it belongs to Residential or not and splits it into two paths one for Residential and one for non residential. Then it passes through "template Movein Doc for". Here it provides a Move in Doc Reference as 000000004712 for non residential and 000000004711 for residential customers in a container operation.
This is where the problem is. These donot exist in Move in / move out tables. So how do I approach now
1) Is there any standard reference document already present in SAP system which can be configured?
2) Do I have to copy the standard workflow and edit the template to give different reference document numbers?
Or is there any other way to solve this issue?
I really appreciate all the help i am getting from this forum so far.
Thanks a lot.
Vinay.

Hi Vinjay,
we are using different method to create a owner move-in MOVEINDOC->MDTMOVEINOWNER which doesn't required the reference.
However, for your answer, you should check out these SAP help:
http://help.sap.com/saphelp_rc10/helpdata/en/43/a7b39d823017b5e10000000a1553f6/content.htm
http://help.sap.com/saphelp_rc10/helpdata/en/43/a24f89794e274ee10000000a422035/content.htm
Regards,
Chaiphon

OPM Process Execution and OPM Standard Costing for Poultry Business

I have a business requirement from the client at their Poultry Processing plant where the client feels that the OPM Execution steps are too cumbersome until closing the batches. The client wants to maintain minimum number of batches in Production: one for Primary, one for Secondary and one for Further Processing, rather than having multiple batches based on different formulas. There are 3 main types of processing which can be briefly described as follows:
A.) Primary Processing:
Live Birds (Ingredient) become Whole Dressed Chicken with Neck, without Neck, Liver, Heart, etc... (40 Finished Products)
e.g. Live Birds (Broiler) -> Whole Dressed Chicken with/without neck, Whole Dressed Chicken with/without neck, etc.
B.) Secondary Processing:
Only one type of Whole Dressed Chicken (from Primary Processing) become Chicken Cuts (80 Finished Products).
e.g.[Scenario B1] Whole Dressed Chicken (Broiler) -> Drumsticks, Thighs, Wings, Breasts, Backbone, etc.
[Scenario B2] Breasts -> Filets and Deboned Breasts (2 FGs)
[Scenario B3] Thighs -> Thighs in Plain Bag
Please note that the Whole Dressed Chicken is also sold as a Finished Good as well as an Ingredient for the Secondary Processing.
C.) Further Processing:
Chicken Cuts become 40 Finished Products
e.g Filets -> Chicken Nuggets, Chicken Fries, etc...
The client is using Standard Costing method for its OPM Financials and all the finished products (160 Products in all) are having different production cost. Please note that 1 kg of Chicken Wings is not equal to 1 Kg of Chicken Thighs. Different body parts have different costs. In order to alleviate the maintenance of multiple batches per day on the production floor, the client wishes to have minimum batches. We therefore would wish if you can confirm the below approach to be correct?
a.) OPM Process Execution:
==========================
EITHER should I (Option 1):
a.) Create ONLY 3 Formulas for Primary, Secondary and Further Processing . The 3 Formulas will have all the processing line Finished Products grouped together (as per the scenarios explained above). Formula for Primary and Secondary Processing can also combined together, reducing it to only 2 batches to maintain per day.
b.) Can set any Quantity Values for the Ingredient, Product and By-Product in the Formula details with ANY Cost Allocation (amounting to a total of '1') in the Products section
c.) Set the Validity Rules as 'PRODUCTION' for the 3 Recipes
d.) Complete the steps defined in the 'OPM Cost Management' (as described below)
e.) Create the 2 or 3 batches and record the appropriate quantities at the end of the day before closing the batches
OR should I (Option 2):
a.) Create MULTIPLE Formulas (above 100 formulas) for Primary, Secondary and Further Processing based on the different products processed.
b.) Can set any Quantity Values for the Ingredient, Product and By-Product in the Formula details with ANY Cost Allocation (amounting to a total of '1') in the Products section
c.) Set the Validity Rules as 'PRODUCTION' for the 3 Recipes
d.) Complete the steps defined in the 'OPM Cost Management' (as described below)
e.) Create the MULTIPLE batches and record the appropriate quantities at the end of the day before closing the batches.
b.) OPM Cost Management:
========================
Whether (Option 1 or Option 2) selected, the below needs to be set for OPM Costing:
a.) Define multiple formulas (above 100), as in Option 2.
b.) Set the Quantity value to be '1' for the Ingredient, Product and By-Product in the Formula details with the appropriate Cost Allocation in the Products section
c.) Set the Validity Rules as 'COSTING' and 'PRODUCTION' for each Recipe
d.) Run Cost Rollup at least once so that the products can have an item cost per unit
As per me, for the purpose of Costing, it would be imperative to have multiple batches (created one time only) with appropriate Cost Allocation in the Formulas and the ‘Recipe Use’ in the Validity Rules should be set as ‘COSTING’. Then, setting Profile Option 'GMF: Use Only Costing Validity Rules for Cost Rollup' to 'Yes'. In this way, we are sure that the different products in the formula with correct Cost Allocation will have their Item Cost calculated after performing the Cost Rollup. AND, for the purpose of operations, we can only one combined formula of Live Birds (as Ingredients) to yield -> All FGs for Primary and Secondary Processing with Cuts. But, this time, the ‘Recipe Use’ in the Validity Rules of the Recipe should be set as ‘PRODUCTION’.
I want to confirm which approach (Option 1 or Option 2) is more appropriate in terms of Operations and confirm that the above proposed steps are correct with no circular reference (as certain finished products are also used as ingredients for another product in the Secondary Processing)?
Thanks and regards
Raveesh Nobeen
[email protected]
Edited by: user12189219 on Jan 20, 2010 3:48 PM

Hi Raveesh
I am implementing OPM R12 in Poultry Processing business, I think option 1 (Create 3 formulas/recipes/batches) is more appropriate. In my case we are using actual costing (Moving Average) as a costing method.
I have set the profile option GMF: Cost Allocation Factor Calculation to be "Dynamic" to calculate the batch cost allocations as a ratio of actual quantity of each product produced to the total production batch output quantity and I have used OPM Financial Cost Allocation process to allocate GL expenses on different products based on Fixed percentage % according to product "value" where Filets has a return more than wings.
Can you please share your knowledge in this business area and confirm to what extend my approach is correct ??
Thank you and best regards
Mamdouh Ragab

ASO Allocation EXCLUDERANGE syntax question

am developing an allocation script and need to be able to exclude certain members identified by UDAs from the allocation. When I try to use the UDA function in the excludedrange specification I cannot find a solution to the requirement to have the excluded range statement in double quotes as well as the UDA value. Script is as follows:
execute allocation process on database app.db with
pov "Crossjoin({[Final]},
Crossjoin({[b701]},
Crossjoin({[c21001]},
Crossjoin({[i000]},
Crossjoin({[All Reports]},
Crossjoin({[All Channels]},{[a41510]})
amount "[PD08]"
amountcontext "([l0999],[Act],[2013])"
target "([Alloc],[PD08],[2013])"
range "Attribute([Status_Open])"
excludedrange "UDA([Location], "Exclude_Alloc_1")"
spread
Can anyone suggest an escape character combination that might work ?
Thanks,
Gavin

I really don't understand what you are trying to do (may be because you are in 11 version{allocation in ASO cube sounds kool).
but I can tell you the syntax error you are getting at first line.
change it to:
"crossjoin([Year].[FY10],crossjoin([period].[Jan],crossjoin([account].[a111],[Entity].levels(0))))"
Thanks,
Jeeth
Edited by: Jithendra on Oct 14, 2010 5:20 PM

Error while running Actual Cost Process.

Hi,
Currently i am trying to implement Actual Costing with calculation type as (PMAC). when i run the actual cost process it is showing the error below.
Errors:
Warning: Cannot find the previous cost period record.
Warning: Total allocated GL expense amount on item MN1-004 is zero or negative.
Do please help me in Using Gl Expense allocation process like what are the steps involved and how system will allocate the cost to items.
Thanks
Amit

For the currency you are converting to: XXX
INPUTCURRENCY dimension must have XXX as a member with "REPORTING" property set to "Y"
and
RPTCURRENCY dimension must have XXX as a member with "REPORTING" property set to "Y" and "CURRENCY_TYPE" property set to "R"
It needs to be in both dimensions with the right properties. INPUTCURRENCY is the currency dimension in the RATE cube, RPTCURRENCY is the currency dimension in the financial or consolidations cube.

Resource Breakdown structure role in Project Cost Allocation.

Dear Experts,
What is the role of resource breakdown structure while running project cost allocations? Is it possible that targets in the allocation process gets the cost allocated to the resources in RBS which is same for source as well as target projects?

Hi
The resource breakdown structure (RBS) is used in the system to summarize the amounts from the lowest level leaf to the grouping / parent levels.
You can use a summarized amount of certain node on the RBS, per your source project, as the source amount that will be allocated.
On the target projects the allocation transactions are created as expenditure items. Those expenditure items will be on target project and task, using the expenditure type and expenditure organization you have setup for the allocation rule.
Dina

Essbase ASO Allocation

Hi, all,
I am writing an ASO allocation script, which is working now. However, I wonder whether there is any way to easily have some mathematics operations on some of the fields. For example, in the following allocation script, how can i use the negative figures of the amount to allocated out? For example, "([East],[Total_Expenses])" is a positive 1000. However, I would like to have the negative 1000 (e.g. -1000) to be allocated amount?
execute allocation process on database DemoASO.Basic with
pov "Crossjoin(Descendants([Year],[Year].levels(0)),
Crossjoin(Descendants([Product],[Product].levels(0)),
Descendants([Scenario],[Scenario].levels(0))))"
amount "([East],[Total_Expenses])"
target ""
range "CrossJoin({[Sales],[Cost_of_Goods_Sold]},
Descendants([South],[Market].levels(0)))"
spread;
Is there a easy way to do such amount calculation in the ASO allocation script? Or I have to created additional members in outline to do such reversal of the sign?
Appreciate any suggestions/ideas?
Thanks a lot

Major caveat - I haven't used the function - but have you looked at the Technical Reference?
http://docs.oracle.com/cd/E17236_01/epm.1112/esb_tech_ref/maxl_execalloc.html
http://docs.oracle.com/cd/E17236_01/epm.1112/esb_tech_ref/maxl_alloc_numeric.html
The example there says that 'amount' is a numeric expression, i.e. you don't just have to list a member or tuple there. It looks like you can use an arithmetic expression, but if you do all members must be from the same dimension - so your {[East], [Total_Expenses]} might be problematic. But that's obviously a sample rather than your actual use case.

ISU Property Owner Allocation - History of owners

Hi All,
I am working on owner allocation process. Just wanted to check if a history of the ownership allocation would be stored in SAP system?
I have checked EPROP, EPROPH tables but could't find if system stores the history anywhere.
Also please confirm the process of reversing owner allocation. Will this reverse the allocation from new owner to previous owner. If yes, system should have stored the history of ownership.
I have tried to reverse a property ownership. Later when I tried to edit / display the same property, system throws a message as "property reversed, no more changes possible ". Does it mean, once a property is reversed, it is of no use!! Can't we further edit the same property?
As far as I understand, ES54 transaction for reversal of owner allocation should work in case of incorrectly created property, but later the property can be edited with correct owner. But the error message triggered by system would not allow us to reuse the property.
Appreciate your input.
Thanks,
Somu

Hi Somasekhar,
The owner allocation history is not stored in a single table. Instead, you have to create a join of the relevant fields from the tables EANL, EPROP and EPROPH. Please go through the attached image.
Note: Also add the field for reversal indication from table EPROP into the join
About your question regarding owner allocation reversal. A reversal will not allocate the old owner back into a premise/ installation. Instead, when a property is reversed, we have to manually assign the old owners for all the premises/ installations contained in that property
Regards
Ullas

How is the product allocation work?

How is the product allocation works? (material master: Basic Data 1,) where is the place to maintain the parameters?
point will given

Product Allocation
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).
Regards
Jitesh

Re-Allocation Process

Similar Messages

Maybe you are looking for