Allocation against outstanding PO

Dear Experts,
I want to know the way i will be able to find the Existance of allocation against Outstanding PO in SAP.
Regards

I find the solution from another thread
Edited by: Samunder Singh on Dec 5, 2008 12:04 PM

Similar Messages

  • Capacity Allocation against Customers

    Hi,
    We have a scenario that we need to allocate capacities to our customers on a monthly basis such that Product A can be made for Customer A and Customer B and the capacity available for it is 4000 units. We need to ensure that Customer A can only place an order of 2000 units and can only place an order of 4000 units if Customer B doesn't place an order for Product A in the given period.
    We are a Make to Order industry and the Sales Order for the month have not been received but capacity for the future needs to be reserved for Product A and Customer A and B.
    Can anyone tell me if its possible and how can it be done?
    Regards,
    Hashim Abbasi

    Hashim,
    There is not a real "capacity allocation against customers" check in SAP ERP.  In SAP, when we refer to 'capacity', we are usually referring to manhours or machinehours.
    However, in your example, where you wish to limit a customer's consumption by units, the standard solution is product allocation.
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/93/744d12546011d1a7020000e829fd11/frameset.htm
    Regards,
    DB49

  • Partial allocation against sale order during allocation run

    Hi Experts..
    How to do allocation run for partial quantity against to the particular AFS sale order while doing allocation run process in J3AT.
    Example :
    I have sale order stock 10 qty. but I want to do allocation run for 5 qty. So that I can make partial delivery for this 5 qty alone. So please suggest me how to do partial allocation run.
    Thanks in advance
    Regds
    Prabakar

    Hi,
    You can try TCode V.00
    This transaction when executed will give you the list of all the sales documents blocked for delivery per sales organization. There are various other criteria which might be useful. This transaction will allow you to edit each sales document.
    If this is not the one that you want, then perhaps you might have to develop one.
    Thanks
    Mukund S

  • Product Allocation against STO

    Hi,
    This is regarding allocation check against stock transport order
    1. As per SAP literature, Receiving plant (WERKS_TO) is available as a characteristic for stock transport orders:
    (http://help.sap.com/saphelp_scm50/helpdata/en/27/31f938a1914358a9df1fcdc2b454ae/content.htm)
    But in the product allocation field catelog, the above field is not present. So how to carry out the allocation check at this level?
    2. What is the key figure to update incoming orders quantity. By default AEMENGE is available. Is the same key figure applicable for STO. If not, what is the key figure to update the incoming order quantity for STO. Where can it be added ?
    Regards,
    RS
    Edited by: sap_apo31 on Jan 4, 2012 11:18 AM

    Hi RS
    1) Receiving Plant can be maintained as a customer with suitable Sales Area. Since customer is available as a characteristic in field catalogue, you can use the same. Alternately, you need to extend the structure (As Michael has advised). This is quite common requirement and your development colleagues will be able to help you.
    2) Key figure will remain AMENGE irrespective of whether it is Sales Order or STO.
    Thanks,
    Prasun

  • MTS material Stock Allocation against Sale Order

    Hi,
    I have a requirment, While creating an sale order for a MTS material the stock from Unrestricted should be allocated to that sale order stock.
    Expecting a solution,
    Thanks and regards,
    Mahi

    Hi Lakshmipathi,
    U r right the scenario is the same as u mentioned. But my requirment is that while creating a sale order for an MTS material the allocated stock should me posted into that sale order stock.  i.e. similar to the stock allocation happening while creating an order for MTO material.
    Hope u can understand my requirment.
    Regards,
    Mahi

  • Demand product allocation against sales target:

    Dear All,
    Here is an interesting sales scenario for you:
    Company gives "high demand product" to their dealers based on their target vs achievement.
    Condition:
    1.A dealer achieves target of 20 cell phones of x-brand in a month, he gets 2 nos of high demand product Z-brand cell phone(not free of charge).
    Eg: 1) ABC dealer has target for 20 nos in a month, and achieved 50% by 20th of that month. Then he is eligible for 1 Z-brand cell phone.
    2) MMM dealer has target for 20 nos in a month, and achieved 100% by month end , he gets 2 nos of z-brand cell phones
    How will we configure it?
    sushil
    [email protected]

    Hi Fab,
    We can connect many production allocatio group to same planning area, but better remove flag direct connection to planning area. During maintenance of PAL procedure and in control conversion conversion factor should be 1 only. 
    In place of removal of above flag we carryout two activity i.e copy data from planning area and copy data to planning area.
    hope process will work fine.
    Regards,
    Veeresh

  • Allocation Management for PO

    Dear Experts,
    I want to know the way i will be able to find the Existance of allocation against Outstanding PO in SAP.
    Regards

    Dear,
    I Have a Sales order XXXXX & Two Purchase orders or Production order XXXX1 & XXXX2 now I want that the Sales Order will be Fullfilled By using Both the Orders in a pre - defined ratio, Please tell me the configuration steps for that.
    Regards
    Samunder Singh

  • Outstanding amount for a Journal Entry

    Dear all
    when we create a journal entry and do a partial outgoing payment based on that Journal entry to a perticular vendor how we an find out how much is outstanding in that journal entry in table level ?????
    Thanks & Regards
    Kanishka

    Hi Kanishka
    In 2005 the system did not cater for partial allocations at journal level. The internal Recon number field woudl only get a number if all the documents in a payment were matched 100%. If just one document at row level in a payment was paid partially, the whole journal would be treated as unmatched. To make it worse, when you open the manual reconciliation function, it displays all these transactions as open, and does not show the partial amounts or full amounts for that payment, thereby allowing you in effect to reconcile "a second time" on the same documents.
    For this reason, you will have to look at VPM2 and see what amounts were allocated against each transaction. The field to look at is SumApplied (Paid to Invoice). Just bear in mind that both invoices and credit notes show a positive value in this field. However, journal debits and credits will show as positive and negative amounts.
    So in summary, for fully paid transactions you can use IntrnMatch from JDT1 but for partial allocations you need to look at VPM2.
    Hope this all makes sense, if not upgrade to 2007. It is worth it even if just for the Internal Reconciliation function that has been added.
    Kind regards
    Peter Juby

  • AFS ARUN goods receipt future allocation

    I'm not able to test a future allocation all the way through for our current setup.
    I allocated an order to future PO and Create an inbound delivery for PO.  At this point /afs/md04 is allocated (R) to stock type 'L'.  When I do the Goods receipt against the Inbound delivery, /afs/md04 remains the same.  I was expecting that the order would be allocated to Batch stock. 
    When I do a good receipt using MIGO against a PO, then it does work correctly - it changes the allocation from PO to batch stock.  When I do a goods receipt using MIGO against an Inbound Delivery or execute Goods receipt using VL32N, it does not - We use VL32N to Goods Receipt.
    Even after doing subsequent allocation against the order requirement using the stanard allocation, I get the message 'no open schedule lines found'.

    Hello Carol,
    might be too late, but is it possible that your stock is (was) stuck in quality inspection?
    KR,
    Peter

  • Issue with Product Allocation Scenario

    I am Trying out Product Allocation in APO (SCM 5.0).
    Relevant setup in SPRO - Product Allocation Object, Group, Procedure, Sequence etc., Planning Object Structure, Planning Area, CVC generation, Connection between Planning Area and Product Allocation object in GATP, assignment in Location Product Master (at Customer Location) Product Allocation Procedure, Check mode, ATP Group has been done in APO.
    After entering data in appropriate keyfigures (Allocated Qty) it shows up under GATP>> Reporting >> Product Allocations >> Time Series per CVC
    Have carried out ATP Simulation to check that for a given product at Customer the Product Allocation against a Required Quantity takes place correctly.
    Now trying to carry out the Product Allocation check by creating a Sales Order in ECC. In that case during the material availability check screen in APO, the product allocation does not show up.
    I believe it is related to master data settings for the product in ECC. My questions are as follows:
    1. In ECC the product exists at the manufacturing plant only (and not at customer as in APO). There in MRP3 tab Strategy Group is maintained. Is this along with Availability Check field responsible for determining the check instruction (combination of check mode + business event) in APO for the Product Allocation check.
    2. If so (which I guess it is) I can see the check instruction picked up in APO while creation of sales order in ECC is different from the check instruction I ran simulation with. How can I ensure the same check instruction is chosen (in which case I believe the availability check result will be same as the ATP Simulation carried out in APO).
    3. In APO I ran simulation for the product at customer location (and maintained the required ATP settings in the product master). In case of Sales Order creation in ECC how does system pick up the Check Mode and Business Event for the product (having Sold-to as customer and Supply Plant as the plant code) and use it in APO.
    4. Any other setting/configuration that is missed causing this behaviour.
    I guess some of the questions is a bit hazy but I would appreciate if someone can outline the Product Allocation Scenario. I am trying out based on Building Block S59 Demand Planning for Product Allocation but of course it does not detail out enough.
    Disclaimer: My knowledge of GATP is almost nil but am exploring.
    Thanks,
    Somnath

    Hi Somnath,
    It will be a pleasure to help you out.
    Firstly I will list out all the steps which I can think of:
    (1) R3-You have moved all the ATP customizing from R3 to APO via ATP integration model.
    (2) APO- goto SPRO>APO>GATP>General Settings>Maintain Check Instructions
    Here go to Check Mode- 041 and Business Event- A and maintain the following settings manually in development and migrate it all the way to Production
    I am assuming here that you want to first do an allocation check and then availability check**
    Product Allocation: Change from NO CHECK to First Check
    Product Check: Change from First Check to Second Check
    This check mode and business event is the most common one which is triggered while placing a sales order
    See the following blog for DETERMINATION OF CHECK MODE
    http://solution-timezone-issue.blogspot.com/
    There might be other check modes( 030, 050) which might also require this change. However you can judge that while placing a sales order and when you go to the availability screen, You have the tab - SCOPE OF CHECK CONTROL where you can see the Check Mode + Business Event
    Following guidelines can be used to modify Check Instrctions after Customizing Import from R/3 –
    1.     Business Event A*  is Sales Order Entry (The main scope of GATP) so define check instructions for all check modes since it is not possible to identify the requirement class that may come over on an order. For Business Event A* if availability check was being done in R3, then define check instructions with Allocation as first step, then Availability check as second step. Else if no availablity check in R3 then define check instructions with no availability and no allocation checks.
    2.     Business Event B* is  normally for deliveries but is also required for Rush Sales Orders. An R/3 configuration showed that 041 is the only requirement class that will come across for this business event. Hence defined only for 041 check mode. For Business Event B* if availability check was being done in R3, then define check instructions with Allocation as first step, then Availability check as second step. Else if no availablity check in R3 then define check instructions with no availability and no allocation checks.
    3.     Business Event 03 required for Inventory Transaction availability check such as MB1C. For such transactions, the APO Product Master Check Mode is used. Hence check instructions for all Check Modes are maintained. For Business Event 03 if availability check was being done in R3, then define check instructions with Availability check as first step. Else if no availablity check in R3 then define check instructions with no availability checks.
    (3) Maintain the Product Alllocation Procedure:
    <b>a-</b> Create a Product Alloc Object -- Example: PAO-001
    In this step, we define the product allocations objects - product allocations are saved per object for a characteristics combination in the product allocation group.
      Product Allocation Procedures can be used to maintain different Product Allocation Objects for different time validity periods.
      Generally Product Allocation Objects are used to model the different ‘reasons’ for the need for allocation – material shortage, capacity constraint, etc.
    <b>b-</b> Product Alloc Group--PAO-1234
    A product allocation group defines a group of characteristics against which allocation checking is done.
       Creating a Product Allocation Group creates a characteristics directory in the APO database and an area in Live Cache where the key figures are maintained.
       If ‘Check Planning Area’ is set to No then allocation and incoming order quantitiy data can be seen in table /SAPAPO/QTTAB. If the ‘Check Planning Area’ is set to Yes then no data is stored in this table and the allocation check is done directly against the data in the Planning area.
       Detials of allocationconsumption by sales orders are maintained in table /SAPAPO/QTVB in APO and in QTVB in R/3.
      If ‘Check Planning Area’ is set to ‘Yes’ and if there are users are in the change mode in the Planning Book, Sales Order Entry can get locked out.
      If ‘Check Planning Area’ is initially set to yes and then deactivated later you will no longer see data in /SAPAPO/AC42.
    Settings:
    Check Planning Area – Yes. The reason being that users are not expected to lock planning books as they would be defaulted into the display mode (through a development object). Also most allocation uploads will be through batch jobs. Setting it to ‘Yes’ reduces one step of moving data between the planning area and the allocation group.
    Check Date - Material Availability Date. Consumption of allocation quantity and checking of available allocation quantities is determined by the check date.
    Time Bucket Profile – Week
    Characteristics – Product Allocation Object (1), Product (2), Plant(3), Customer(4)
    Consumption Period – Bwd Consumption 1  
    Meaning that first the order will consume from current week allocation and then go 1 week backward to consume.
    <b>c-</b> Product Allocation Procedure --- PAO-4567
    Step Sequence:
    <i>Step</i> -
    <i>Step Name-</i> -
    Prod Alloc Group -
    Wild card
    1                      First Step             PAO-1234                     9
    <i>Alloc Procudure</i> - PAO-4567
    <i>Prod Alloc Step</i> -1
    <i>Control</i>
    <i>Valid from -
    Valid to---- -
    Object -
    Active -
    Factor</i>
                            12/31/2037      PAO-001    Check the Box                  1
    <b>d-</b> Maintain Connection to Planning Area (APO) 
    In this step, we maintain the assignment of the planning area to the product allocation group. We must make this assignment because characteristics of the product allocation group have different names from the info objects of the planning area.
      All characteristics of a product allocation group must be assigned to an info object. But multiple info objects can be assigned to one info object. It is not always necessary to assign every info object to a characteristic. It is possible for aggregation and disaggregation (depending on the direction of transfer) to take place with info objects that are not assigned.
    <i>Product Alloc Group -
    Planning Area -
    Version -
    Time Buckets</i>
    PAO-1234                         xxxxx                     000             W
    <i>Characteristic</i>
    KONOB - Prod Alloc Obj
    MATNR --- Material
    WERK -
    Plant
    XXXXX---- Customer
    <i>Key Figures</i>
    Order Qty - AMENGE
    Alloc Qty - KCQTY
    <b>e-</b>  Check the Product Alloc Settings
    This is only a check- Everything should be green and OK .
    (4) You have planned the Characteristic Combination on which you want to do ALLOCATION.
    <b>Create a new POS-</b> Which has your chracateristics as PRODUCT, PLANT,CUSTOMER, Product Alloc Object ( 9AKONOB)
    <b>Planning Area,-</b> Key figures required are Alloc Qty, Order Qty( Sales Order Qty)
    <b>PLannig Book, Data View</b> which has the following characteristics- Product, PLant
    Assuming you are allocating at the following CVC level- Product, PLant,Customer
    Step 1:
    /n/sapapo/MC62-Create Time Series- Basicallly your CVCs -
    Example: Product 1234, Plant INDIA, CUstomer WALKART
    Step 2:
    Move Characteristic Values Combination to Allocation Group (APO) 
    /SAPAPO/ATPQ_PAREA_K
    INput :
    Planning Area: xxxx
    Prod Alloc Group: PAO-1234
    (5) In the INtegration MOdel - Activate the ATP CHECK Integration model for the Plant and material
    THis is the KEY which decides whether availability should be done in R3 or APO
    Material Active in the integration model -- Means Availability( GLOBAL AVAILABILITY: Prod Alloc+Prod Availability) is done in APO
    Material not active in the integration model --- Means Availability Check is done in R3
    (6) APO MASTER DATA SETTINGS:
    Material Master:  On the ATP Tab, Assign Loc Dep Procedure ( Prod Alloc Procedure)
    Location Master: Calendar Tab> Create a shipping time stream calendar
    Additional Info: Please contact your R3-SD people as this involves a lot of understanding and I have not listed all the details here.
    This config shown here is a very basic one which not even 25% of the companies might be using.
    If you have any questions on this part- please see my business card and email me**
    (7) SCHEDULING: This is a major task which determines the route and transit times for calculating the
    Material Availability date
    Goods Issue Date
    Delivery Date
    on the sales order line item- schedule line
    I dont know whether you need info on this**There are many ways of doing this
    a- Configurable Scheduling
    b- COndition records
    c- User Exit
    You can find documentation in SPRO or else let me know*
    For simplicity- Let me take the easiest to create and difficult to maintain master data- Condition Records
    Step1 --Define Field Catalog for Condition Table (APO) 
    /SAPCND/AU01
    Require Plant and Route defined here in the field catalog
    Step 2- Define Condition Table for Scheduling (APO) 
    /SAPCND/AU03
    Create a new table- 901
    901 -  Pick Time based on Route with key as Route
    902- Route Time based on route
    Step 3- Maintain Access for Scheduling (APO) 
    /SAPCND/AU07
    Take the important ones- PICK and TRAN
    I am assuming again as I dont know what kind of Scheduling is maintained on R3 Side. Mostly 80% companies have only two lead times- Pick and Route Transit time.**
    PICK- Select pick and click on accesses > <i>Acno</i>-10-- <i>Table</i>-901
             >> Then save it > and go in again
    Select PICK and click on Fields> A popup will appear > Enter the access sequence as PICK--- Enter the access as 10  and click on the GREEn ARROW and save it
    TRAN- Select TRAN and click on accesses > <i>Acno</i>-10-- <i>Table</i>-902
             >> Then save it > and go in again
    Select TRAN and click on Fields> A popup will appear > Enter the access sequence as TRAN--- Enter the access as 10  and click on the GREEn ARROW and save it
    Now coming to maintaining the Condition records in APO EASY ACCESS
    /SAPCND/AU11
    Create  SCheduling Step for PICK : Enter condition type- PICK
    <i>Enter Route</i>- USCAN --- <i>Duration</i> -24:00 (Hrs)
    Create  SCheduling Step for TRAN: Enter condition type- TRAN
    <i>Enter Route</i>- USCAN --- <i>Duration</i> -48:00 (Hrs)
    Now Let me answer your questions:
    (1) Question 1- <i>In ECC the product exists at the manufacturing plant only (and not at customer as in APO).</i>     
    I did not undertsand what you mean here. As we can create a Material at the following locations in APO( Dist Center(DC), Manu Plant(PL), Cusomter, Vendor, etc)
    For GATP all we need is the material at a PLant location
    STrategy Group on MRP3 tab: This is purely used for determining the CHECK MODE value on APO Product Master.
    When this is blank on R3, the check mode will be blank on APO.
    However SAP recommends Putting in a strategy group value on R3 Material Master
    or
    a default Check MOde value for all those Products who have blank check mode-   041 is the best value * This piece SAP hasnt recommended but I found that there is No harm in anyway and it is MANDATORYfor inventory transactions like GOODS ISSUE otherwise you will get a QUEUE in SYSFAIL **
    Even if this is blank this has no effect on the GLOBAL ATP as the Check mode for a SD transaction is determined as follows
    98% of the SD transactions will generate a CHeck mode of 041 and Business Event- A ***
    Through the item category and the MRP type in the MRP view
    The item category is derived from the item category group in the Sales view of the material master record and from the order type of the sales document. Together with the MRP type in the MRP view of the material master record, the item category determines what requirements type is selected. The advantage of this method is that the selection of the requirements type depends on the business process (such as quotation, sales order, or repair).
    (2) Question 2 - I guess now you must have understood why when you do a simulation in APO, it is taking the Check mode from APO product Master
    and when you do a ATP Check from R3, the check mode(041) is different
    You dont need to ensure that they are the same- It doesnt matter in anyway.
    (3) Question 3- <i>In APO I ran simulation for the product at customer location (and maintained the required ATP settings in the product master).</i>I
    When you run ATP simulation- AC04, you generally run it for the plant as that is the supplying location and not the customer.
    <i>In case of Sales Order creation in ECC how does system pick up the Check Mode and Business Event for the product (having Sold-to as customer and Supply Plant as the plant code) and use it in APO.</i>
    PLease look above for this answer.
    (4) Question 4 - <i>Any other setting/configuration that is missed causing this behaviour.</i>
    To my best knowledge, whatever I could remember I have listed out. However there are some more steps which might be needed.
    Follow all the steps as I have mentioned and whenever you get struck somewhere, shoot me a message and I will help you.
    ONe more pointer here to what you have mentioned
    Relevant setup in SPRO - Product Allocation Object, Group, Procedure, Sequence etc., Planning Object Structure, Planning Area, CVC generation, Connection between Planning Area and Product Allocation object in GATP, assignment in Location Product Master (at Customer Location) Product Allocation Procedure, Check mode, ATP Group has been done in APO.
    After entering data in appropriate keyfigures (Allocated Qty) it shows up under GATP>> Reporting >> Product Allocations >> Time Series per CVC
    <u><i>Have carried out ATP Simulation to check that for a given product at Customer the Product Allocation against a Required Quantity takes place correctly.</i></u>
    Somnath, I believe you might have a wrong picture here. The concept of allocation is  Controlling Supply against huge Demand which is in this case coming from SALES ORDER
    When you place a sales order, the supplying location is your plant and that is where you would like to put in allocation quantities
    Say for example for a material 12345 - You have stock of 100 Qty in Plant KING fo this week and it shows as follows in the planning book
    Customers say are WALKART, GE-FUG, MACROGUN
    The CVCs which we have to create are as follows
    Similar to Demand PLanning**
    Material 12345 -PLant KING-Cust WALKART-Prod Alloc Obj
    Material 12345 -PLant KING-Cust GE-FUG-Prod Alloc Obj
    Material 12345 -PLant KING-Cust MACROGUN-Prod Alloc Obj
    And this is how it appears in the planing book when you go into DETAILS ALL
    You basically enter the Allocation Quantities just as how you enter forecast quantities in DP Book*
                            Wk1   |  WK2     WK3   WK4  WK5
    Alloc Qty                     |
    Material 12345                |
    Plant KING                    |
    Cust WALKART            50    |
    Cust GE-FUG             30    |
    Cust MACROGUN           20    |
    Incoming Order Qty               |
    Material 12345                   |
    Plant KING                       |
    Cust WALKART           <u>50</u>|
    Cust GE-FUG            <u>25</u> |
    Cust MACROGUN          <u>20</u> |
    <u>50</u> : Say the Cust WALKART has ordered 250 for this week, however only the allocated quantity -50 will be confirmed for him and the remaining 200 qty will be confirme at a later week when he is given the allocated amount.
    <u>25</u> :Similarily say this customer GE-FUG has ordered 20 qty. So his remaining allocation is basically 5 which cannot be used by any other customer.
    <u>20</u> : Say this customer MACROGUN has ordered exactly the allocated amount of 20. So his remaining allocation will be 0.
    This is the basic idea of how Allocation Concept is used in GATP.
    Ofcourse you can add the other functionalities like
    Rules Based ATP(LOcation Substitution, Product Substitution)
    Multi ATP( BOM-COmponents)
    Check Aginst Forecast
    Etc Etc
    Like any other module of SAP- this module has much to offer which unfortunately I cannot list here**
    GOOD LUCK and let me know If you need additional help.
    Regards
    KUMAR AYYAGARI
    Message was edited by:
            Kumar P Ayyagari

  • Allocation vs assessment/distribution

    Hi,
    1 May I know what is the difference between allocation VS assessment/distribution?
    I may think that allocation is ONLY from cost center to another cost center?
    assessment/distribution is ONLY to another cost element?
    2 what tcode to use for allocation and assessment/distribution?
    Please advise.
    thanks
    rgds

    Hi,
    To me it is not general, I have to understand that before I can start doing.
    I really hope I can get advice of the difference between
    allocation VS assessment / distribution.
    I would like to know if there is any difference of allocation against assessment or allocation against distribution.
    hope can get advice.
    thanks
    rgds

  • PGA Allocation on Windows/Linux

    As linux is a process based architecture. Each client connection is treated as a separate
    process on linux as compared to windows where client connection are implemented as threads within a single process.
    Thread base model has limitations on 32-bit systems because all the threads share the same 3GB address space for SGA, PGA and other memory.
    A PGA is created by oracle whenever a server process is started.
    On windows PGA and SGA are created under oracle process and all threads share the same 3GB address space for SGA, PGA then how does a PGA is allocated against a singles session (which is treated as a separate process) on Linux. Does it come out of same 3GB address space as on windows.

    [email protected] wrote:
    As linux is a process based architecture. Each client connection is treated as a separate
    process on linux as compared to windows where client connection are implemented as threads within a single process.
    Thread base model has limitations on 32-bit systems because all the threads share the same 3GB address space for SGA, PGA and other memory.
    A PGA is created by oracle whenever a server process is started.
    On windows PGA and SGA are created under oracle process and all threads share the same 3GB address space for SGA, PGA then how does a PGA is allocated against a singles session (which is treated as a separate process) on Linux. Does it come out of same 3GB address space as on windows.Yes it is part of the 3GB address space.

  • 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

  • Availability Check with ATP Logic  or  Against Planning-reg

    hi gurus,
    what is the difference between
    Availability Check with ATP Logic
           or         
    Against Planning
    means can we have two types of check?
    how can we do against planning?
    rajendra

    Hi Prasad,
    I think it would not possible to maintain to procedures at the same time for single material.
    availability check against ATP is  allowcation of material based on certain rules like which we set under basic functions - AC.
    In this process you cant allocate the stock for specific customer.
    In case of AC against planning you can allocate each and every material along with qty to specific customers.
    Please see the configuration required for planning.
    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).
    Reward if helpful.
    Regards
    Raj

  • Link between delivery line item and sales order item schedule line.

    Hello friends,
    This is a continuation of my earlier query - for which I got half the solution, and this is the remaining problem.
    I want to know: from delivery document line item, how to link it to sales order line item's schedule line (when there are multiple schedule lines with identical quantities).
    Thanks for your help.
    - Chetan

    This is the code which i used for the same purpose and its working.
    Hope this will help you too....
    ****it_itab  is my final internal table.
    *Internal table for manupulating the Delivery balance when
    *its used in more than one schedule line
    TYPES: BEGIN OF ty_new,
           vbeln TYPE vbep-vbeln," so no
           posnr TYPE vbep-posnr," so line no
           etenr TYPE vbep-etenr," schedule line
           delno TYPE lips-vbeln,"delivery no
           delposnr TYPE lips-posnr,"del item no
           totval TYPE vbep-wmeng," total del wise value
           val   TYPE vbep-wmeng," del wise used value
           sdval TYPE vbep-wmeng,"schedule wise  del used value
           sdtotval TYPE vbep-wmeng," total Schedule value
         END OF ty_new.
    DATA:it_new TYPE ty_new OCCURS 0,
         wa_new TYPE ty_new.
    DATA: it_vbepvb TYPE TABLE OF vbepvb,
            wa_vbepvb LIKE LINE OF it_vbepvb,
            fvbfa TYPE TABLE OF vbfa,
            fvbup TYPE TABLE OF vbup,
            fvbap TYPE TABLE OF vbapvb.
      LOOP AT it_vbak INTO wa_vbak.
        LOOP AT it_vbap INTO wa_vbap
                WHERE vbeln = wa_vbak-vbeln.
      SELECT * FROM   vbfa INTO TABLE fvbfa WHERE vbelv = wa_vbap-vbeln
                                             AND  posnv = wa_vbap-posnr.
      SELECT * FROM   vbup INTO TABLE  fvbup WHERE vbeln = wa_vbap-vbeln
                                             AND  posnr = wa_vbap-posnr.
      SELECT * FROM   vbap INTO TABLE fvbap WHERE vbeln = wa_vbap-vbeln
                                             AND  posnr = wa_vbap-posnr.
      SELECT * FROM   vbep INTO TABLE it_vbepvb WHERE vbeln = wa_vbap-vbeln
                                             AND  posnr = wa_vbap-posnr.
      CALL FUNCTION 'RV_SCHEDULE_CHECK_DELIVERIES'
        EXPORTING
          fbeleg                        = wa_vbap-vbeln
          fposnr                        = wa_vbap-posnr
      FVERRECHNUNG                  = ' '
      FS073_ALT                     = ' '
      IF_NO_SORT                    = ' '
        TABLES
       fvbfa                         = fvbfa
       fvbup                         = fvbup
       fxvbep                        = it_vbepvb
      FVBLB                        =
        fvbap                        = fvbap
    EXCEPTIONS
      FEHLER_BEI_LESEN_FVBUP        = 1
      FEHLER_BEI_LESEN_FXVBEP       = 2
      OTHERS                        = 3
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      SORT it_vbepvb BY vbeln posnr edatu.
      LOOP AT it_vbepvb INTO wa_vbepvb
                    WHERE vbeln = wa_vbap-vbeln
                      AND posnr = wa_vbap-posnr.
        to write data of schedule line with no delivery
        MOVE wa_vbepvb-olfmng_flt TO wa_itab-openqty.
        IF  wa_vbepvb-bmeng EQ wa_itab-openqty.
          CLEAR wa_itab.
          PERFORM schedule_data.  "schedule line based data to be displayed
          MOVE: wa_vbap-lgort TO wa_itab-lgort.
          MOVE: wa_vbepvb-etenr TO wa_itab-etenr,
                wa_vbepvb-bmeng TO wa_itab-kwmeng,
                wa_vbepvb-olfmng_flt TO wa_itab-openqty.
          APPEND wa_itab TO it_itab .
          CLEAR wa_itab.
        ENDIF.
        LOOP AT it_vbfa INTO wa_vbfa WHERE vbelv = wa_vbepvb-vbeln
                                            AND  posnv = wa_vbepvb-posnr.
          READ TABLE it_likp INTO wa_likp WITH KEY vbeln = wa_vbfa-vbeln.
          CHECK wa_likp-bldat >= wa_vbepvb-edatu.
    check the Delivery doc date with the schedule line confirmed date
          CLEAR: delbal, deltot,wa_new.
          LOOP AT it_new INTO wa_new WHERE vbeln = wa_vbepvb-vbeln
                                         AND       posnr = wa_vbepvb-posnr
                                         AND       etenr = wa_vbepvb-etenr.
            deltot = deltot  +  wa_new-sdval.
          ENDLOOP.
          delbal = wa_new-sdtotval - deltot.
          CHECK sy-subrc <> 0 OR delbal GT 0.
          MOVE wa_vbepvb-olfmng_flt TO wa_itab-openqty.
          CHECK  wa_vbepvb-bmeng NE wa_itab-openqty.
    ****To check whether this delivery is already fully allocated against
    any other schedule.
    LOOP AT it_lips INTO wa_lips WHERE  vbeln = wa_vbfa-vbeln
                                           AND posnr = wa_vbfa-posnn.
            MOVE: wa_likp-bolnr TO wa_itab-vesname.
            MOVE: wa_likp-vbeln TO wa_itab-delno.
            MOVE: wa_likp-wadat TO wa_itab-wadat.
            MOVE: wa_likp-anzpk TO wa_itab-anzpk.
            MOVE: wa_likp-lddat TO wa_itab-lddat.
            MOVE: wa_likp-ernam TO wa_itab-ernam.
    ******end of code added by IVL1 on sep 27 2007 #3618
            PERFORM schedule_data.
            IF wa_lips-umvkz <> 0.
              tempquant = wa_lips-umvkn / wa_lips-umvkz.
            ELSE.
              tempquant = wa_lips-umvkn. "delivery qty
            ENDIF.
            tempquant = tempquant * wa_vbfa-rfmng.
    ***New logic added to get delivery qty schedule wise****
            MOVE: wa_vbepvb-etenr TO wa_itab-etenr,
                  wa_vbepvb-bmeng TO wa_itab-kwmeng,
                  wa_vbepvb-olfmng_flt TO wa_itab-openqty. "jo
    **if delivery qty is less than or equal to schedule line qty******
            IF tempquant LE  wa_vbepvb-bmeng.
              wa_itab-delqty =  tempquant.
              LOOP AT it_new INTO wa_new  WHERE  vbeln = wa_vbepvb-vbeln
                                         AND     posnr = wa_vbepvb-posnr
                                         AND     etenr = wa_vbepvb-etenr
                                         AND     delno  = wa_lips-vbeln
                                         AND     delposnr = wa_lips-posnr.
                MOVE-CORRESPONDING  wa_itab TO wa_new.
                wa_new-delposnr = wa_lips-posnr.
                wa_new-val = tempquant.
                wa_new-totval = tempquant.
                wa_new-sdval  = tempquant.
                wa_new-sdtotval = wa_vbepvb-bmeng.
                MODIFY TABLE it_new FROM wa_new .
                IF NOT sy-subrc IS INITIAL.
                  APPEND wa_new  TO it_new.
                ENDIF.
              ENDLOOP.
              IF sy-subrc <> 0.
                MOVE-CORRESPONDING  wa_itab TO wa_new.
                wa_new-delposnr = wa_lips-posnr.
                wa_new-val = tempquant.
                wa_new-totval = tempquant.
                wa_new-sdval  = tempquant.
                wa_new-sdtotval = wa_vbepvb-bmeng.
                APPEND wa_new TO it_new.
              ENDIF.
             wa_itab-delqty =  tempquant.
             CLEAR tempquant.
            ELSE.
        lips qty > so schedule lineqty
              CLEAR deltol.
              LOOP AT it_new INTO wa_new WHERE    vbeln = wa_vbepvb-vbeln
                                          AND      posnr = wa_vbepvb-posnr
                                         AND     etenr = wa_vbepvb-etenr
                                          AND     delno  = wa_lips-vbeln
                                          AND    delposnr = wa_lips-posnr.
                deltol = deltol  + wa_new-val.
              ENDLOOP.
              LOOP AT it_new INTO wa_new  WHERE    vbeln = wa_vbepvb-vbeln
                                          AND      posnr = wa_vbepvb-posnr
                                          AND     delno  = wa_lips-vbeln
                                          AND    delposnr = wa_lips-posnr.
                MOVE-CORRESPONDING  wa_itab TO wa_new.
                wa_new-val = wa_new-totval - deltol.
                wa_itab-delqty =  wa_new-val.
                wa_new-delposnr = wa_lips-posnr.
                wa_new-totval = tempquant.
                wa_new-sdval  = wa_new-val.
                wa_new-sdtotval = wa_vbepvb-bmeng.
                MODIFY TABLE it_new FROM wa_new .
                IF NOT sy-subrc IS INITIAL.
                  APPEND wa_new  TO it_new.
                ENDIF.
              ENDLOOP.
              IF  sy-subrc <> 0.
                MOVE-CORRESPONDING  wa_itab TO wa_new.
                wa_itab-delqty =  wa_vbepvb-bmeng.
                wa_new-delposnr = wa_lips-posnr.
                wa_new-val =  wa_vbepvb-bmeng.
                wa_new-totval = tempquant.
                wa_new-sdval  = wa_vbepvb-bmeng.
                wa_new-sdtotval = wa_vbepvb-bmeng.
                APPEND wa_new  TO it_new.
              ENDIF.
            ENDIF.
            IF NOT wa_lips-lgort IS INITIAL.
              MOVE: wa_lips-lgort TO wa_itab-lgort.
            ELSE.
              MOVE: wa_vbap-lgort TO wa_itab-lgort.
            ENDIF.
            APPEND wa_itab TO it_itab .
            CLEAR wa_itab.
          ENDLOOP. 
        ENDLOOP.
        CLEAR wa_vbepvb.
      ENDLOOP.
        ENDLOOP.
        CLEAR wa_vbak.
      ENDLOOP.

Maybe you are looking for

  • How to build a https, simply, but detailled way

    HI there! It took tones of hour trying to setup a https connexion and finally, it still not work. I went to tones of forums and try all the tricks written, nothing worked. Most of the time it is not clear. Most of the time it changed nothing. YOU are

  • In Colloboration rooms where in KM are Past Meetings stored

    Where are Past Meetings stored within KM (I need to know the path to see where they are stored)?  I have not been able to find them.  Past Meetings are where you type in your meeting session minutes.   Please let me know where within the KM content t

  • Spry Data in Accordion in Tabs

    Hi I have been able to get xml spry data to work in an accordion and I have been able to get an accordion to work in tabs but I cannot get the data to work in an accordion that is in a tab -- the accordion panels do not collapse. I have a sample test

  • Comparing headerlines of internal tables

    Hi abapers, I have 2 internal table IT1 & IT2 with header line. In a loop i take values of IT1, one by one, to its header line and compare it with the header line of IT2. How can i compare header lines of two internal table? Explanation with a exampl

  • Error in Portal Favourites

    Hello,      I am facing some problem in Portal Favourites on client 280. It Says Error during Knowledge Management Startup. And it shows a runtime error. I am totally blank in this area. Any help will be appreciated.