Inventory management senerios difference

Hi expert,
I am refering to the comman documents available for implementing inventory, as i am new to the inverntory, and have to propose the fesibility of implementing the inventory part,
i dont have the functional deep knowlege about the inventory,
In the document it says about the non cummulative senerio and the snap shot with cummulative,
i am not able to catch up with the terms used in explaining the use of senerious,
So can any one tell me,
1) Dose it depend on the implemantation process been handled by the functional consultant for customising the inventory in the ECC system for opting for the senerio's of implementing inventory management on BW side, ?
or it is entirly dependent on the performance base and the advantages and disadvantages ?
2) As it is a fresh implementation and we have lack of resources also, i am the only one, i want to avoid all the complex situatuion which could consume time, basically the coding part, etc,
I want to make it as simple as possible with following the neccessary steps to be taken as mentioned in documents,
So can anyone sujjest on that too ?
Thanks
Daljeet Singh Nagi

hi
1.
Processes in the area of Inventory Management address the recording and tracking of materials on a quantity and value basis. This includes planning, entry, and documentation of stock movements such as goods receipts, goods issues, physical stock transfers, and transfer postings as well as the performance of physical inventory (stocktaking).
Warehouse Management Processes cover warehouse-internal movements and storage of materials.
2.
SAP Warehouse Management allows you to manage your material flow, using advanced putaway and picking strategies. In the standard system, these strategies for putaway include random putaway (next empty bin), bulk storage, fixed bin, or addition to stock. The picking strategies include standard strategies first-in first-out (FIFO), last-in first-out (LIFO), picking by shelf life expiration date (SLED), or partial quantities first. For customer-specific strategies, solutions can be self-defined in user exits.
3.
While Inventory Management manages the stocks by quantity and value, the Warehouse Management component reflects the special structure of a warehouse, and monitors the allocation of the storage bins and any transfer transactions in the warehouse.
Reward points if helpful

Similar Messages

  • Difference between inventory management and warehouse management

    can any body tell me the difference between inventory management and warehouse management i need atleast five differences

    hi
    1.
    Processes in the area of Inventory Management address the recording and tracking of materials on a quantity and value basis. This includes planning, entry, and documentation of stock movements such as goods receipts, goods issues, physical stock transfers, and transfer postings as well as the performance of physical inventory (stocktaking).
    Warehouse Management Processes cover warehouse-internal movements and storage of materials.
    2.
    SAP Warehouse Management allows you to manage your material flow, using advanced putaway and picking strategies. In the standard system, these strategies for putaway include random putaway (next empty bin), bulk storage, fixed bin, or addition to stock. The picking strategies include standard strategies first-in first-out (FIFO), last-in first-out (LIFO), picking by shelf life expiration date (SLED), or partial quantities first. For customer-specific strategies, solutions can be self-defined in user exits.
    3.
    While Inventory Management manages the stocks by quantity and value, the Warehouse Management component reflects the special structure of a warehouse, and monitors the allocation of the storage bins and any transfer transactions in the warehouse.
    Reward points if helpful

  • Inventory Management differences between 3.5 and 7 versions doubt

    Hi
    We plan to upgrade BW system from version 3.5 to version 7 next year.
    And we plan to initiate Inventory Management in BW (Cube 0IC_C03).
    It is good idea to start Inventory Management before upgrade?
    OR the better idea is wait befor upgrade?
    THX for your opinion.
    Adam

    look at the current content if that meets the requirement then why to wait till upgrade. During upgarde it is your call whether to move objects to BW7 (content) and data flow. Even if you want to move to BW7 data flow, you could easily migrate.
    Why should you wait for those many months if currents objects meet your reporting needs.
    Also, I am not sure whether SAP has made any changes to Inventory content so that you could get anything better with new content post upgrade.
    Regards
    Vikash

  • Stock Valuation - Inventory Management Cube

    Dear Sap Gurus,
    We have implemented the Inventory Management Cube in BW.
    Quantities are correct, but we have difference on the stock valuation.
    For some material stock value are correct, for some other they are not correct.
    A saw a lot of OSS notes and how to on this subject, I am trying to solve this issue using these documents, but based on your experience could you explain me how you solved this issue ????
    Thanks,

    Hi
    Did you follow the correct steps?
    Initialisation of BX data in the first step.(Loading of Opening Stock)
    Then The request in which the opening stock was loaded must always be
    compressed with a marker update
    Init load of BF And UM in the second step
    The request in which the historical material documents were contained
    must always be compressed without a marker update and
    Successive delta uploads must always be compressed with marker
    updates
    Check this whether you have done this or not.
    Because of missing the steps here also would give you wrong values,
    Regards
    Ram

  • HU without inventory management and message L3778 in storage type 999

    Hi experts,
    Need suggestion on the process to add inventory of an HU with status 'HU without inventory Management'. This issue has occurred out of the below scenario:
    1. our warehouse is HU & WM managed.
    2. We have a transfer order for a delivery document requesting to pick up 100 cases of MAT1 which is assigned to HU1.
    3. While confirming the transfer order user has confirmed difference for the full quantity of 100 because the SU/HU was not found in the bin.
    4. The system has set the status of HU as 'HU without inventory Management'. The HU is empty.
    5. system has moved the stock from the bin to difference storage type 999.
    Now user has found the stock for this HU and he wants to post the stock back into the bin. system does not allow to move the stock back to bin using LT01 as we get error message 'L3 778'.
    What will be the best practice to get the stock back into the bin and post the stock into the same old HU.
    Is there a process wherein we can post this stock to another bin and repack into the old HU?
    Thanks,
    Harish

    Thanks Manish on the hint. I was able to transfer stock to partner location and then bring back to original Storage type/Bin. Below steps was used to fixed the issue:
    1. Initiate a transfer of stock from WM/HU Sloc where the IM stock resides into Sloc 9099. An outbound delivery is created during this process.
    2. Create a transfer order with reference to delivery and pick the stock from 999 storage type.
    3. Create a Pick HU using LH01 and assign the HU on the pallet to the transfer order.
    4. Confirm the transfer order using LT12.
    5. Perform PGI for the delivery.
    6. Use HUMO to display the HU and then you can transfer the stock back to WM/HU location using the storage location transfer option available on the HUMO screen(EDIT à change HU posting à Storage location)
    7. Perform Bin to bin transfer to move the SU from 921 storage type to putaway the HU/SU back to the destined Storage type/Bin.
    Best Regards,
    Harish

  • Serial Numbers in Inventory Management – Warehouse Managed storage location

    Serial Numbers in Inventory Management u2013 Warehouse managed storage locations
    We want to run inventory cycle at the warehouse for materials. These materials are u2018serial numberedu2019 in the material master. During the initial entry (say GR) of the materials, systems prompt for the serial numbers. At this point, system offers option of assignments of serial numbers automatically.
    While running an inventory cycle for warehouse u2013 and posting difference at WM level (LI01), system is throwing error as u201Cmaintain serial number for totol quantityu201D. System does not promt me to enter the serial number for the materials (count) which are found excess/shortage duing the inventory cycle.
    Is there any configuration where this scenario can be managed; system should prompt us to enter serial number while posting differenes at WM level (LI20).
    The inventory cycle is -
    1.     Create Physical Inventory Documents - LI01N
    2.     Activate Physical Inventory Document -      LI02N
    3.     Enter Count -     LI11N
    4.     Post Differences at WM level -     LI20
    5.     Post Differences at IM level(If Differences are posted at WM ) -     LI21

    Curious to know: The WM Inventory transaction - LI11N - (where we enter physical count. )
    1. Compared to MI04 - IM Inventory Transaction: where a pop-up window asks for serial number of the material.
    2. We expect a similar pop-up at LI11N transaction- where the system should ask serial numbers.
    Q.1 How can we achieve this?
    Q.2 Will this be a standard SAP practice?  (if we do customizing to get serial nos. pop-up window at LI11N)
    thanks,

  • Inventory management with SnapShots

    Hi
    I've got this document, "How to handle inventory management scenarios in BW".
    It's generally very clear, no problem to understand the standard solution (0IC_C03, non-cumulatives).
    But I really didn't understand the explanation about Snapshot on the monthly positions.
    So I ask someone to explain how does the concept work.
    Example:
    The document refers to material movements in 01.2004 and 03.2004.
    Question 1:
    What are the values posted to the DSO and to the InfoCube after initial load (after the first load of datasources BX and BF/UM) ???
    Will we have registers to 01.2004, 02.2004, 03.2004 and 12.9999, both in the DSO and in the InfoCube ?
    How does month 12.9999 work?
    Question 2:
    What are the values posted to the DSO and to the InfoCube after the second BF load?
    Let's suppose 2 movements in 04.2004 and 2 movements in 05.2004.
    Will we add registers to 04.2004 and 05.2004 both in the DSO and in the Cube?
    Thanks in advance.
    Cesar Menezes

    Hi Cesar,
    Not sure if this could be helpful.. but still sharing..
    http://www.biportal.org/discussion_forum?mode=MessageList&eid=350671
    As even I want to understand differences between 2 methods.. Snapshot and 0IC_C03 (non cumulative)
    Could you find any leads?
    Regards, Vittali

  • About archiving BW Inventory Management cubes

    Hi everyone!
    I would like to know what a marker in Inventory Management (BW) is. This question comes from the following: I need to archive a IM cube, and it presents the following option:
    Stocks:
    Only transactions
    Transactions and Markers
    I don't know what a marker is, so I'm kinda lost here...
    Any help would be greatly appreciated (and rewarded, ofc!).
    Best Regards,
    Luís.

    Hi,
    Marker is fairly simple, you will get the details also on help.sap.com with more detailed explanation.
    In a brief here is what i can tell you :
    1. The marker is set on a specific date and the value of the inventory KF( NON CUMULATIVE KF) the value on that particular date is stored in the cube.
    2. Since Inventory is working on the non cumulative method the difference is calculated since DAY 1. but with Marker the difference is calculated from the day of marker.
    Hence it helps in retrieving faster results.
    Let me know if you want more information.
    Regards,
    Den

  • Regarding inventory management

    Hi,
    I have documnet How To Handle Inventory Management Scenarios in BW
    Version 1.3 – January 2005.
    But it gives the details about 3.5 version. If i want to implemnet in 7.0 what all i need?
    also i w2as trying to find the 'No marker update' option and all in 7.0 but coudnt find the same. Is thr so much difference in implementing INVENTORY in 7.0
    *Please help.

    Hi Jino,
    Briefly,
    a) Single Step transfer: -
    this comes in STO, while transfer material between plants.
    if you tick the indicator as one step in config,
    Generally, when you do the PGI for material from supply plant to receiving plant, goods issue document will generate in Issuing plant.
    Similarly goods receipt (GR)document  generate in receiving plant.
    in One step procedure, GR will create automatically in background after you do PGI.
    where as in Two Step Plant Transfer. AFter PGI, you have to create GR-MIGO also.
    Hope it clears.  Try and let me know

  • How to handle inventory management scenario

    Hi All,
    In How to handle inventory management scenario whitepaper, I fail to understand the basic difference between 'Inventory Management with non-cumulative Key Figures' and 'Inventory Management with Snapshots'. Can anyone please explain me the basic difference.
    Thanks
    PB

    Hi Loic
    Can u please see if all the steps listed below are OK.
    While setting up  the IM Scenario
    I have jotted down the steps with valuable inputs from you  and paper 'How to Hanlde IM scenarios'
    Please find the steps below. Kindly review them and let me know in case I have got anything wrong or missed out on anything.
    1. Transfer Business Content Datasources 2LIS_03_BX , 2LIS_03_BF, AND 2LIS_03_UM in RSA5.
    2. Go to Transaction LBWE, Activate Datasources 2LIS_03_BF, AND 2LIS_03_UM.
    3. Go to Transaction MCB_ select SAP BW usage 'Standard' Radio button.
    4. Save it.
    5. Go to Transaction MCNB, enter name of run ‘Stock_init’. Enter Termination date in future. Enter Datasource as 2LIS_03_BX.
    6. Execute the initialisation.
    7. Entries can be found in SETUP Table MC03BFSETUP & MC03BFSETUP.
    8. Run SETUP for 2LIS_03_BF, AND 2LIS_03_UM using TCodes OLI1BW and OLIZBW respectively.
    9. Run the extraction for 2LIS_03_BX in BW.
    10. Compress the request with ‘No Marker Update’ NOT SET i.e. unticked or unchecked.
    11. Run the extraction for 2LIS_03_BF in BW.
    12. Compress the request with ‘No Marker Update’ SET i.e. ticked or checked.
    13. Run the extraction for 2LIS_03_UM in BW.
    14. Compress the request with ‘No Marker Update’ SET i.e. ticked or checked.
    Steps 1 and 2 shall be executed in Development and transported to production and step 3 onward should be carried out in Production itself with Posting Block.
    Thanks in advance.
    Regards
    PB

  • Inventory Management Loading clarification - loading BX , BF and UM

    Hi,
    I want to load inventory management from scratch.
    I have ready lots of documents from this site related to this but still unsure.
    In SAP document, It says that BX should be compressed with NO MARKER UPDATE and  while BF and UM should be compressed with NO MARKER Update box checked.
    I also read some where that
    BX and UM should be compressed with No marker update not selected while only BF should be compressed with marker update box checked.
    which is the correct version or whats the difference between these two.
    thanks

    Hi Vaidya,
    Inventory calculate all non cumulative values based on a reference +/- delta principle.
    The reference is called the marker.
    Answer to the question when should I do a marker update?
    Initially, for first load to BW, if R/3 system has gone live earlier, each material would have some stock value in the plant. But if BW has to load only deltas , then it should have this initial stock figures.
    So we do a statsitcal run for BX. This statistical run.. consider intial stock of R/3 when it went live + incoming material movement documents - outgoiong material movements and loads BX.
    So after this load in BW, we compress the request in BW to create our marker to say 100PCS for material A in plant A as on 31.03.2009.
    Now if you are interested in seeing on what were material movements(incoming/outgoing)  for 01.02.2009 in BW, you would have to load BF to BW.
    So you rean intialization for BF and loaded BF in BW.
    But this movement of material A on 01.02.2009 was considered in getting our marker value when we did BX load. This is because in our statistical run for BX we had calculated = R/3 initail stock + incoming movements - outgoing movements until 31.03.2009. So if we consider this historical movement for marker uppdae again our marker would become incorrect.
    So when we load BF until 31.03.2009(initialization run) we do not update the marker. So we compress the marker without update.
    From 31.03.2009 onward when you load detlas to BW for BF and UM every day, you would like to update the marker to keep it current as of date.
    ie say material A moved out on 01.04.2009 - 20 pcs.
    say material A moved in on 03.04.2009 - 40 pcs.
    So on 4th when you load delta and update the marker , the marker value would be - 100 - 20 + 40 =120.
    You update the marker because business is most often interested to see stock of previous or two to three days before. If the marker is updated then it has to check fewer records to get the delta to goe the the stock figure then.
    Thus, for all future delta loads you would compress with marker update.
    Hope this helps,
    Best regards,
    Sunmit.

  • Inventory Management 0IC_C03 customizations

    Dear Experts,
    I have a task in hand to implement Inventory Management in SAP BW 3.5. Now, this is the first time that we will be implementing anything related to Logistics and I havenu2019t done so earlier in my support projects. I have got 10 hrs of downtime.
    I need to fetch the report for both Trading as of now.
    The fields needed in the report by the customer are:
    Plant
    Plant Description
    S. Loc.
    S.Loc. Description
      Opening Stock Qty,
      Opening Stock Value,
    Receipts against PO Qty,
            Value,
    Receipt against STO  Qty,
            Value,
    Receipt against return SO  Qty,
         Value,
    All Other Receipts  Qty,
          Value,
    RevaluationValue,
    Miro Differences,
    Issue against SO  Qty,
          Value,
    Issue against STO Qty,
            Value,
    All Other Issues Qty,
          Value,
      Closing Stock Qty,
               Value,
    Book Inv Qty,
    Physical Inv Count.
    I am planning to define these as Zkey-figures and write routines in update rules based on processing keys to capture each qty and value separately.
    My questions are:
    1) What are the fields from above that can be pulled from standard BI Content Reports (if possible, please specify which report)? OR fields (or combination of fields) that are already in the cube?
    2) For every above field, customer has given standard movement types.
    For ex: for Receipts against PO = Mov Types 101,105,123,162 (Doc Type IN/IM)
                for Receipt against STO = Mov Types 351, 352 (Doc Type UB)
    But when brought in BI, all routines are based on processing keys (BW Transaction key). Where can I find mapping of each processing key to the corresponding movement type?
    If you know which processing key can be used for above fields, please let me know.
    3) What are the other fields that need to be considered in routines. If possible please specify field wise.
    4) Should I extend the 0IC_C03 with these new custome KFs creating a new zcube or should I add only required fields in zcube.
    If I follow the latter, will there be any impact on standard BF/UM runs as in If I load till PSA and from PSA I follow my customized update rules terminating into my customized cube?
    Thanks friends.

    BJ,
    My questions are:
    1) What are the fields from above that can be pulled from standard BI Content Reports (if possible, please specify which report)? OR fields (or combination of fields) that are already in the cube?
    ~ You will get fields from the Cube only.
    2) For every above field, customer has given standard movement types.
    For ex: for Receipts against PO = Mov Types 101,105,123,162 (Doc Type IN/IM)
    for Receipt against STO = Mov Types 351, 352 (Doc Type UB)
    ~ Check this Table in Source system for BW Keys : TMCLVBW
    But when brought in BI, all routines are based on processing keys (BW Transaction key). Where can I find mapping of each processing key to the corresponding movement type?
    If you know which processing key can be used for above fields, please let me know.
    Check this table
    3) What are the other fields that need to be considered in routines. If possible please specify field wise.
    That depends upon your requirement in the report or Check the standard Dcoument for Inv management in SDN search.
    you will get lot of help.
    4) Should I extend the 0IC_C03 with these new custome KFs creating a new zcube or should I add only required fields in zcube.
    If I follow the latter, will there be any impact on standard BF/UM runs as in If I load till PSA and from PSA I follow my customized update rules terminating into my customized cube?
    ~Best Practice and even SAP Recommends Make a ZCUBE and then enhance or customize to fullfill your rek.
    No impact follow IM steps for BW.
    Make sure you keep these things in Mind:
    There are 3 SAP delivered transactional data sources for stock management.
    2LIS_03_BX : Always needed to carry the initialization of the stocks.
    2LIS_03_BF :  Initialize this in source if you need historical data else an empty init can be done for this to load only future delta records. If the Source system is new then no need to do an initialization. 
    2LIS_03_UM : Only needed if revaluations are carried out in Source. This data source is helpful if adjustment in material prices is done time to time otherwise it wonu2019t extract any data.
    2.  Check list for source system. Needs to be carried out before initialization of the above 3 data sources .
    A.   Table TBE11 : Maintain Entry u2018NDIu2019 with text u2018New Dimension Integrationu2019 and activate the flag(Note 315880)
    B.   Table TPS01 : Entry should be as below(Note 315880)
    PROCS u2013 01010001
    INTERFACE  - SAMPLE_PROCESS_01010001
    TEXT1 u2013 NDI Exits Active
    C.   Table TPS31 : Entry should be as below(Note 315880)
    PROCS u2013 01010001
    APPLK  - NDI
    FUNCT u2013 NDI_SET_EXISTS_ACTIVE
    D.   Tcode u2013   MCB_  
    In most cases you need to set the industry sector as u2018standardu2019. For more info please see Note 353042
    E.    Tcode u2013  BF11
    Set the indicator to active for the Business warehouse application entry. This entry may needs to be transported to the production system. (Note 315880)
    3.  After running the setup data, check the data for the fields BWVORG, BWAPPLNM, MENGE. If no data available in these fields then some setting mentioned in the above checklist are missing in R/3. Correct the issue and rerun the setup data.
    4.  Data staging with DSO for BX extractor is not allowed. Data should directly load from extractor to Cube only once. Choose the extraction mode as u2018Initial Non-cumulative for Non-cumulative valuesu2019 in the DTP.
    5.  DSO is possible for BF. If you are creating a standard DSO then choose the fields MJAHR,BWCOUNTER,MBLNR,ZEILE as key fields. Some of these fields wonu2019t be available in the standard data source but the data source can be enhanced using LO Cockpit (LBWE) to add these fields. In addition to these other fields depending upon the DSO structure is also possible.
    Note  417703 gives more info on this.
    6.  Point-5 is valid for UM also. The Key fields could be a combination of MJAHR,MBLNR,ZEILE,BUKRS  fields. Note 581778 
    7.  Data load to the cube should follow the below process
    A.      Load the BX data. Compress the request with stock marker(uncheck the marker option).
    B.      Load the BF and UM init data. Compress the loads without the stock maker(Check the marker option).
    C.      The future delta loads from BF and UM should be compressed with Stock marker(uncheck the marker option).
    8.  If in future the cube needs to be deleted due to some issues then the load process should also be carried out as above. (only init of BF and UM should be loaded first and then the deltas should be processed)
    9.  To check the data consistency of a Non cumulative cube the standard program SAP_REFPOINT_COMPLETE can be used. To check the compression status of the cube the table RSDCUBE can be refered. Before the compression of BX request, the u2018REFUPDATEu2019 field should be blank and after the compression the value should become u2018Xu2019. Check Note 643687 for more info.
    10. After BX data load to cube the data wonu2019t be visible by LISTCUBE. Only after compression the data can be seen by running a query on the Non cumulative cube.
    ~AK

  • Inventory Management 0MM_IM_BX, 0MM_IM_BF, 0MM_IM_UM, 0MM_IM_STOCK

    Hello Everybody,
    does anyone has experience or knowledge with the new datasources 0MM_IM_BX, 0MM_IM_BF, 0MM_IM_UM, 0MM_IM_STOCK for inventory Management?
    What are the differences to datasources 2LIS_03_BX, 2LIS_03_BF, 2LIS_03_UM?
    How works the initialization of this datasources?
    Is there also a How to paper available, or is also the How to paper of the old datasources valid for the new ones
    Thanks
    Constantin

    Hi Bhavin,
    my Basic Approach was the 'how to handle inventory Management scenarios' document from 2005, which gave me an Overall Impression. next Thing was to simply check the meta data Details of the info sources before the inventory cube 0IC_C03 and compare that stuff to the meta data Details of the corresponding new 0MM- data sources. It has been no surprise to me that they go together pretty well.
    So what we find provided from the activation of Business Content looks like this:
    As mentioned in my earlier post I created a custom copy of the 0IC_C03 cube to leave the Content as it is. Then i copied the transformations from info source to cube to link the info sources to the new custom cube. For the inventory initialization path (*BX) I have connected the data source directly to the info source before the cube.
    For the movements (*BF) and revaluations (*UX) i have created DSOs (where I have used the info source as template. You have to check for the correct key fields in the DSO!). The DSOs then required transformations to connect their data sources.
    Now the full custom view on my development Looks like this:
    Please bear in mind that you Need to activate the MM_ANALYTICS Switch using Transactions SFW2/SFW5 in your ERP source System before you can do a Delta load.
    I hope this has given you more clarity and Detail to get along with it.
    Cheers, Harald

  • MM-Based inventory management & Replenishment -based Inventory Management

    Hi,
    Can any one through me some light on the difference between "MM-Based inventory management" & "Replenishment -based Inventory Management" in IS-Retail.
    Is it something related to planning, If so what is the difference.
    Thanks in Advance,
    Shakthi Rajkumar.

    Hi
    In retail scenario the replenishment can happen in two ways
    (1) From DC to Stores
    (2) Directly from vendor to Distribution center.
    However the above two scenarios follow the following push / pull strategy to replenish the material.
    Case 1 : From DC to Stores
    How the push occurs ?
    Store orders/sales orders
    Automatic store orders/sales orders from different POS system
    Auto replenishment
    How the pull occurs ?
    Allocation of merchandise purchased
    Case 2 : Directly from vendor to Distribution center.
    How the push occurs?
    Reorder point planning
    Forecast based planning
    Time phased planning
    How the pull occurs?
    Allocation
    Manual purchase orders
    Hope this clarifies your doubts how the replenishment happens in retail scenario
    Reward if useful
    Regards
    edwin

  • Database design (ERD )for Inventory Management System

    Dear All,
    I am going to develop a simple Inventory Management System software using C# .NET for my learning. After searching different forums, many people have suggested to first create a database design for the software. I want a database design, in short, an ERD
    diagram for simple Inventory Management System which shows proper entities(tables), attributes and relationship between entities.
    It would be highly helpful for me as I am newbie to C# and databases.
    Thanks,
    momersaleem

    Dear Rebecca,
    Thanks for you suggestions.
    As I am going to develop IMS for learning purposes so I think I wouldn't need to go in detail regarding Customer name and addresses. However, I am still thinking of adding country attribute in customers' table which I think will be helpful to sort out customers.
    What's the difference between a purchase and an order?  They're usually the same thing, which doesn't mean you're
    wrong, but what are you picturing here? Purchase entity will be used to keep record of purchases you made and an order entity will be used to keep record of orders that cutomers placed.
    Pricing:
    Any order system needs to manage two very distinct bits of data that are easy to confuse. The price in the Product entity is the current
    price. The price in the Order entity is the selling
    price. Not at all the same thing--current price is almost certainly going to change over time. Selling price won't.
    Does it mean that I'll change the price attribute for product to current_price and add selling_price to order table which will help to keep record of price at the time of order?
    Why did you include a quantity field in the Products table? Is it meant to represent stock on hand?
    Yes you are right. It represents stock in hand.
    Could you please recheck the entities relationships as I am not confirmed whether these are correct or not?
    Thanks,
    momersaleem

Maybe you are looking for