Link between sales order-delivery-invoices

Hi all,
I need to display an order , the delivery that is based on the order , the invoice based on this delivery...
I need to find a link property between them ...
Plz help...
Ola

The links between the documents are held at the item line level. 
The BaseEntry property, BaseLine property, and BaseType property are used to link from one document to another. On your invoice these would contain pointers to the delivery it was based on, on the delivery these would contain pointers to the sales order.
BaseType contains a BoObjectTypes reference (eg. Sales Order = 17) to let you know what type of document the line was based on.
BaseEntry contains the document key to the originating document.
BaseLine indicates which line number on the original document the current line was based on.
John.

Similar Messages

  • Link between sales order to Credit management

    Where can we link between sales order to Credit management?

    HI Gopala rao.,
                       In VOV8 sales document type there is <b>credit limit & Credit group</b> Where we asign the credit mage,ment data to Order
    The configuration part of credit managemnt is
    CREDIT MANAGEMENT:
    A credit limit may be a customer’s credit limit, which is the permitted limit of value of open items, such as invoices not yet paid, plus the value of open sales orders.
    The credit limit is the total combined value of the following documents:
    Net value of sales order
    Open Sales order: order created, but not delivered
    Open deliveries: delivered, but not invoiced
    Open billing doc: value of billing doc, which has not yet been forwarded to accounting
    Open items: forwarded to accounting, but not settled.
    Types of Credit Check
    • Simple Credit Check
    • Automatic Credit Check
    o Static
    o Dynamic
    Simple Credit Check:
    SPRO- IMG- SD- Basic Functions- Credit Mgmt/ Risk Mgmt- Simple Credit Check- Assign Credit Check to Doc Types.
    • Based on sales doc types
    • It will check all the above-mentioned docs & if the credit limit exceeds, the system responds in the way defined by you in the configuration menu.
    • Cannot differentiate according to customer
    3 ways to Control the Simple Credit Check:
    A: warning
    B: error message: the doc cannot be saved
    C: warning message with delivery block: the doc can be saved but is automatically blocked for delivery.
    Automatic Credit Check:
    This credit mgmt control is maintained by using the automatic credit control functionality. The automatic credit control divides the sales doc types, the delivery doc types, & goods issue into specific credit groups. It also uses the customer’s risk category as assigned to the CMD of the payer & assigns an outcome proc to the combination of the above 2 objects, i.e. the credit group & customer risk category along with the credit control area. The definition of customer’s risk category is carried out in the fin accounting module.
    A customer’s risk category is a grouping category that controls the credit check when automatic credit control takes place. Thus one can assign high-risk customers to risk category for e.g. A01, medium risk to B01 and low risk to C01.
    Automatic credit check divides customers in to 3 categories:
    • High-risk customers,
    • Low risk customers &
    • Medium risk customers.
    A credit check &#61614;can only occur at 3 places: Credit Group
    Sales order: for high risk customers
    Delivery: for medium risk customers
    Goods Issue: for low risk customers
    Credit Control Area (CCA): highest organizational element in credit management. A credit control area is an organizational unit that is comprised of one or more company codes. A company code can have no more than one credit control area. Defined by FI.
    Menu Path to create Credit Control Area: OB45: FI people.
    SPRO- IMG- Enterprise Stru- Definition- Fin Accounting- Define Credit Control Area
    Credit Control Area Description
    0001 Credit control area 0001
    1000 Credit control area Europe
    Menu Path to Assign Company Code to Credit Control Area: OB38: FI people.
    SPRO- IMG- Ent Stru- Assignment- Fin Accounting- Assign Comp Code to CCA
    • It is possible to assign Credit Control Area to a Sales Area. This is more specific assignment than the assignment to Company Code.
    Company code Company name City Credit Control Area Over write CCA
    Menu Path for Defining Risk Categories: OB01: FI people
    SPRO- IMG- Fin Accounting- Account Receivables & Payables- Credit Mgmt- Credit Control Account- Define Risk Categories.
    Risk Category CCA Name
    001 4500 Low risk
    002 4500 Medium risk
    003 4500 High risk
    Menu Path for defining Credit Groups: OVA6
    SPRO- IMG- SD- Basic Function- Credit Mgmt/ Risk Mgmt- Credit Mgmt:
    • Define Credit Groups: OVA6
    • Assign Credit Groups to Sales Doc’s & Delivery Doc’s
    o Credit Limit check for Order Types: OVAK
    o Credit Limit check for Delivery Types: OVAD
    • Define Automatic Credit Control: OVA8
    Define Credit Croups: OVA6
    One merely creates a credit group for each differentiation in the doc type. You enter the credit groups when you configure the sales doc types for credit management & define the automatic credit check. The following credit groups are contained in the standard R/3 system:
    • 01: credit group for sales order
    • 02: credit group for delivery
    • 03: credit group for goods issue
    CG (Credit Group) Doc Credit Group
    01 Credit group for sales order
    02 Credit group for delivery
    03 Credit group for goods issue
    Assign Sales Documents & Delivery Documents:
    Sales Doc Type Descp Check Credit Credit Group
    OR Std Order D 01
    Delivery Type Descp Del Credit Group GI Credit Group
    LF Delivery 02 03
    Define for each sales doc type whether a credit check should be carried out. Enter ‘D’ if an automatic credit check should be carried out.
    Specify a Credit Group
    Specify a Credit Group for the Delivery Type for which you want to carry out a credit check
    Specify a Goods Issue Credit Group for the Delivery Type for which a credit check is to be carried out for goods issue.
    SIMPLE CREDIT CHECK CANNOT BE ASSIGNED TO DOCUMENTS.
    Define Automatic Credit Control:
    One can now assign settings to the combination of the Credit Control Area, the Customer Risk Category & the Credit Group.
    CCA Risk Cat Credit Group Credit Control
    4500 001 01 Low risk sales orders
    4500 001 02 Low risk deliveries
    4500 001 03 Low risk goods issue
    4500 002 01 Medium risk sales orders
    4500 002 02 Medium risk deliveries
    4500 002 03 Medium risk goods issue
    4500 003 01 High risk sales orders
    4500 003 02 High risk deliveries
    4500 003 03 High risk goods issue
    Select line item and go to details, you can decide whether to do Static or Dynamic Credit Check. Credit Horizon can also assigned here. Additional function checks can be performed here:
    • A credit check when the maximum document value is exceeded.
    • A credit check when changing critical fields.
    The risk category assignment occurs in the same place as the customer’s credit limit, which is the customers credit management screen. That is, the risk category is assigned to the customer by the Finance in transaction code FD32.
    The customer credit master record is divided in to 5 views:
    • Overview Screen: gives an overview of credit settings in relation to the customer, including his credit limit, credit exposure, the %tage of credit limit used, his payment data & his risk category.
    • Address: view gives the customers address details as they appear in CMD
    • Central Data: is a view that shows the total credit limit the customer can receive across all credit control areas as well as the maximum limit he can receive in one credit control area.
    • Status: view shows the customer’s actual individual details according to particular CCA being investigated. This includes his credit limit, percentage used, credit exposure, risk category, whether he is blocked due to credit or not.
    • Payment history: view displays the payments made by the customer for a particular credit control area where a comp code is assigned.
    Static Credit Check Dynamic Credit Check
    Net Doc Value Net Doc Value
    Open Order Open Order
    Open Delivery Open Delivery
    Open Billing Open Billing
    Open Item Open Item
    Compares the total combined values of the above-mentioned documents to credit limit. Plus credit horizon. Compares the values of the following documents to credit limit + credit horizon.
    Credit horizon has an attached time period that states that the system is not to include sales orders in the total of outstanding items created after that specified period i.e. for the purpose of evaluating credit, you want the system to ignore all open orders that are due for delivery after the horizon date. Maintained for low & medium risk customers.
    Update Groups
    Basically it is a info structure where system stores all the data about credit limit. The credit relevant data is updated in a info structure, where it is accessed & updated. Thus each automatic credit control must be assigned an update group.
    • Update Group 000012
    • Update Group 000015: delivery & billing
    • Update Group 000018: sales order, delivery & billing.
    Update group 000012, updates at:
    • Sales doc: increased order value
    • Delivery: decreased order value & increased delivery value
    • Billing: decreased delivery value & increased billing amount
    • Invoice: decreased billing amount & increased open item value.
    Release Blocked Sales Order/ Deliveries:
    • VKM3: sales order
    • VKM5: delivery
    • VKM4: both
    One can see the offending document. Note on the right hand side, the ‘Status Field’. This shows the check, the doc failed. If this field is empty, the doc did not fail a credit check, even though it may be in the list of SD documents that are “required to be released”.
    To release the doc, one indicates the doc to be released and then clicks on the ‘Release Button’. The result is the offending doc entry, highlighted green. One then proceeds to save, after which you are informed the doc number has been released.
    • Net value with sub total ‘A’, in pricing proc, will be the basis for credit limit.
    REWARD if helpfull
    Thanks & Regards
    Narayana
    Message was edited by:
            manam narayana

  • Tracking Sales Order/Delivery/Invoice Status

    Hi Experts,
    I have a requirement where i need to track the status of the Sales Order/ Delivery/ Invoice without any customized program for achieving this.
    Is there any way we can track the status of the above said Sales Documents without writing a program for it?
    Kindly share your expertise on the same.
    Thanks in advance.
    Regards,
    Keerthi

    Hi,
    Use FM 'SD_DOCUMENT_FLOW_GET'.
    pass sales order no. & item no(optional)
    and you will get all flow documants for that sales order i.e. delivery, GI,invoice details along with all details including status.
    hope this will be useful for you.
    Regards
    Edited by: Vishal Chavan on Jul 9, 2009 8:23 AM

  • Regarding creating a LOOSE LINK between Sales Order and Vehicle

    Hi,
    Does anyone has any idea on how to establish a LOOSE LINK between Sales Order and Vehicle using BAPI_VEHICLE_CREATE or any other Function module.
    Any help will be highly appreciated and rewarded.
    Kind Regards,
    Tanuja

    Dear Kumar,
    Strategy - 40
    Consumption of PIR (not Redution)
    1) the first point in strategy in 40 is, incoming sales order consumes PIR
    2 )both sales order and PIR takes place in MRP planning run
    2) this is where it is in mostly used in many indutries
    just a small example how this strategy works
    1) creat PIR for ur FERT- 100Nos
    2) check in MD04- u will get PIR (VSF) as 100
    3) now creat sales order for 120 for same month
    4 )run MRP for that particular FERT
    5) check the result in MD04, here ur PIR gets vanishied and an plan order will be generated for 120 Nos.
    Regards
    kumar
    Edited by: kumar kumar on Jul 22, 2009 8:29 AM

  • Link between Sales order and Credit master sheet

    Hi,
    Plz explain the link between sales order and credit master sheet.
    Thanks and regards
    CSR

    Hi,
    Credit master is related to Customer.
    Credit limit will be assigned to a customer by using the T.Code FD32.
    Credit control area will be assigned to a customer.
    You can the credit control area for a customer in the table "KNVV".
    Goto the T.Code "FD32".Enter your customer number and credit control area.Select the status tab.
    Here you can maintain the credit limit.If you leave blank means the limit is 0.00.
    Next thing is goto the T.Code "OVAK".
    Select your sales order.Maintain the "Credit limit check" for your order type.
    Goto the T.Code "OVA8".Select your valid combination.Here,you can activate either the static or dynamic credit limit checks.
    If you create the sales order by using the customer,initially the system will check for the credit limit.If it is 0.00 and credit check functionality is activatd in the above specified T.Codes,then creditcheck will happen and order will be blocked for releasing of credit by using the T.Code "VKM3".Authorised persons have to release this credit block.Suppose,you have maintained this credit limit as "1000Rs/-" and you are creating the order of value "550Rs/-",then your order will not be blocked even though the credit check functionality is activated for your order type.
    In this way,sales order is in turn related to credit master.
    Regards,
    Krishna.

  • Link Between Sales Order Type and Customer/Material Exclusion

    Hi,
    Any one know the  Link Between Sales Order Type  and Customer/Material exclusion tables (Transaction: VB03 ) ?

    Hello,
    For Tcode VB03 you can check KOTG001 for Customer/Material.
    Thanks &Regards,
    Abhijit

  • Linking between Sales order data and Biling condition

    Hi Bwers,
    Currently we are geneating a report with Sales order Item level (2lis_11_VAITM) information and Biling conditions(2lis_13_VDKON). We have respective DSO for both datasources (Sales order DSO and Biling Condition DSO). We have to pull both information into a report.
    We have sales order number (0DOC_NUM) in Sales DSO and Biling document number (0BILL_NUMber) in Biling DSO. And we found Sales order Number (0BILL_NUM_0DOC_NUMB) as an navigational attribute for Biling DSO.
    We are trying to extract Billing condition type and Billing condition value from Billing DSO.
    Now the question's are:
    1. Can I use Sales order number as linking field for Both DSO' or not. Though It is an Navigational attribute for Biling document number in Biling DSO.
    2. Is the Sales order number and Billing Document number both are same or not. What is the linking field between sales order info to Biling info.
    2. How to bring Sales order info and Biling info into a report through Infoset. If infoset which link should I use bring both info into a report.
    3. Or Multiprovider is the right one.
    3. Please let me know if any other linking fields are existed between these two datasources other than Sales order.
    All the helpful answers are awareded with full points.
    Regards,
    Venkat

    1. Can I use Sales order number as linking field for Both DSO' or not. Though It is an Navigational attribute for Biling document number in Biling DSO.
    - yes you can link, Navigation attrbute does not matter
    2. Is the Sales order number and Billing Document number both are same or not. What is the linking field between sales order info to Biling info.
    --one sales order number may correspond to different billing number including the one which shares the same number.
    2. How to bring Sales order info and Biling info into a report through Infoset. If infoset which link should I use bring both info into a report.
    -- Multiprovider is the best option while dealing with such cases.
    3. Or Multiprovider is the right one.
    --yes.
    3. Please let me know if any other linking fields are existed between these two datasources other than Sales order.
    there may be possibilty of other fields also like Profit center, Controling area etc depending upon your project requirment

  • Linking Between Sales Order And Purchase ORder

    Dear Gurus,
      How to link the Sales Order Number and Purchase Order Number. I know the Sales Order Number and I need the tables from which I can know the Purchase Order Numbers for that Sales Order Number.
    Points will be awarded.
    Thanks,
    Ravi

    Hi,
    Goto Table Mseg-kdauf is sales order no.
    get mseg-ebeln is purchase order.
    Or u can do the following code.
    from sales order no VBELN get VBFA-VBELV.
    SELECT SINGLE vbeln  FROM  likp
             INTO l_delno
             WHERE  vbeln   = vbfa-vbelv.
    SELECT SINGLE ebeln
               INTO l_sono
               FROM ekbe
               WHERE  belnr = l_delno    
               AND   bewtp = 'L' .  
    L_DELNO IS PURCHASE ORDER.
    If it is helpfull pls reward it.
    Regards
    Srimanta

  • Link between sales order and purchase order

    plz explain the link between the sales order and purchase request

    Hi Javed,
    Their are 2 scenario for this.
    1) You create a sales order and the system automatically creates a PR and then you convert to PO.This is third party sales.In PO account assignment the sales order number is directly copied to the PR And PO.
    2) You create a PO wrt to SO .The goods received will be reserved for that SO. third party PO Vendor will directly deliver the goods to customer.The delivery address is copied from sales order.
    Techincally
    EKKN table you have sales order and Item fields (VBELN and POSNR)
    using these fields search for the deliveries in LIPS table
    EKKN-VBELN = LIPS-VGBEL and
    EKKN-POSNR = LIPS-VGPOS
    Edited by: Raj on Jun 19, 2008 6:58 PM

  • Maximum Line items in Sales order/ Delivery/ Invoice

    Hi guru's
    Maximum line items(SAP Standard) in the sales document/ Delivery Document / Invoice?
    Thanks and Regards
    Srinivas Kapuganti

    Dear Srinivas
    Why you want in sale order and delivery to restrict the number of line items and it will have no impact.
    For Billing, you can achieve this.  Go to IMG path -- Billing -> Billing Docs -> Country specific features --> Maintain Maximum Number of Billing Items.  There select your sales organization and maintain the number of line items to flow in your billing document. 
    thanks
    G. Lakshmipathi

  • Enabling the Local time stamp on Sales Order, Delivery, invoice & PO

    Hi SAP experts,
    I need the valuable inputs for the following requirement- the user ( India based)want to see the local time stamp on transactions VA01(Sales Order), VL01N(Delivery) and VF01(Sales Invoice), ME21N(PO). The system is currently fetching the Malaysian time on these.(invoice and delivery).
    A small info about the issue: As India is 2.5 hrs behind Malaysian time so at 9:30 pm India time system date changes to the next day for us and any invoice done after 9:30 pm is showing next day's date. Also the time reflected on the Invoice is Malysian time which should be actually the local time. As per user, it is a non compliance on regulatory front.
    To simulate the issue we have created an invoice on 3rd Jan at 4:01PM Indian Std time but the time reflected on the invoice is 18:31 which is MY time.
    Also provide help in where to see the time settings for these sales documents?
    I am new to the SAP, All the valuable suggestions are highly appreciated.

    Dear All,
    With the help of security team, we tried to change the Personal time Zone ( of the user) maintained in SU01-Defaults tab to INDIA , but did not get the expected results. THE SYSTEM TIME ZONE JUST MAINTAINED BELOW PERSONAL FIELD IS SHOWING UTC+8.
    After the change , the invoice created at India time is reflecting +2.5 hrs ahead time.
    Pls Suggest , how to acheive this. Any example ecenario can help a lot.
    Thanks a lot in advance for the support.

  • API to create a link between Sales order and Requisition

    We are upgrade 11i to R12. We have a custom drop ship process. We have a original SO and through the sales order we create a Reqisition. We send the requisition details to the factory and the factory sends us a flat file with the quantity shipped and dates. There might be multiple lines for each requisition received. We will add the details to the SO and update the Requision with the flat file details for the SO shipment. But We will have to create a link between the SO and the requisition. Is there an API to do the linking between a SO and A requisition line?

    I created a SO and a requisition
    declare
    p_rsv inv_reservation_global.mtl_reservation_rec_type;
    p_dummy_sn inv_reservation_global.serial_number_tbl_type;
    x_msg_count NUMBER;
    x_msg_data VARCHAR2(240);
    x_rsv_id NUMBER;
    x_dummy_sn inv_reservation_global.serial_number_tbl_type;
    x_status VARCHAR2(1);
    x_qty NUMBER;
    l_inventory_item_id number;
    l_source_header_id number;
    l_reservation_qty number;
    l_error_message VARCHAR2(300);
    l_order_number NUMBER;
    begin
    fnd_global.APPS_Initialize(1131,50654,660);
    p_rsv.reservation_id := NULL;
    p_rsv.requirement_date := to_date('30-JUN-2012','DD-MON-YYYY');
    p_rsv.organization_id := 88; ---ship_from_org_id
    p_rsv.inventory_item_id := 147001; --inventory_item_id
    p_rsv.demand_source_type_id := inv_reservation_global.g_source_type_oe;
    p_rsv.demand_source_name := NULL;-------'SALES ORDER';
    p_rsv.demand_source_header_id := 27005; --- sales order header id
    p_rsv.demand_source_line_id := 29010; --- sales order line id
    p_rsv.primary_uom_code := 'EA';
    p_rsv.primary_uom_id := NULL;
    p_rsv.reservation_uom_code := 'EA';
    p_rsv.reservation_uom_id := NULL;
    p_rsv.reservation_quantity := 200;
    p_rsv.primary_reservation_quantity := 200;
    ----p_rsv.supply_source_type_id := inv_reservation_global.g_source_type_internal_req;
    p_rsv.supply_source_type_id :=inv_reservation_global.g_source_type_inv;
    p_rsv.supply_source_header_id :=18001; -- requisition header id
    p_rsv.supply_source_line_id :=12172; -- requisition line id
    p_rsv.supply_source_name := NULL;
    p_rsv.supply_source_line_detail := NULL;
    p_rsv.autodetail_group_id := NULL;
    p_rsv.external_source_code := NULL;
    p_rsv.external_source_line_id := NULL;
    p_rsv.supply_source_line_detail := NULL;
    p_rsv.revision := NULL;
    p_rsv.subinventory_code := NULL;
    p_rsv.subinventory_id := NULL;
    p_rsv.locator_id := NULL;
    p_rsv.lot_number := NULL;
    p_rsv.lot_number_id := NULL;
    p_rsv.pick_slip_number := NULL;
    p_rsv.lpn_id := NULL;
    p_rsv.attribute_category := NULL;
    p_rsv.ship_ready_flag := NULL;
    p_rsv.demand_source_delivery := NULL;
    p_rsv.attribute1 := NULL;
    p_rsv.attribute2 := NULL;
    p_rsv.attribute3 := NULL;
    p_rsv.attribute4 := NULL;
    p_rsv.attribute5 := NULL;
    p_rsv.attribute6 := NULL;
    p_rsv.attribute7 := NULL;
    p_rsv.attribute8 := NULL;
    p_rsv.attribute9 := NULL;
    p_rsv.attribute10 := NULL;
    p_rsv.attribute11 := NULL;
    p_rsv.attribute12 := NULL;
    p_rsv.attribute13 := NULL;
    p_rsv.attribute14 := NULL;
    p_rsv.attribute15 := NULL;
    inv_reservation_pub.create_reservation
    p_api_version_number => 1.0
    , x_return_status => x_status
    , x_msg_count => x_msg_count
    , x_msg_data => x_msg_data
    , p_rsv_rec => p_rsv
    , p_serial_number => p_dummy_sn
    , x_serial_number => x_dummy_sn
    , x_quantity_reserved => x_qty
    , x_reservation_id => x_rsv_id
    IF x_status='S' THEN --- HARD RESERVATION IS DONE SUCCESFULLY ---
    dbms_output.put_line('reservation succesful');
    dbms_output.put_line('reservation id: || x_rsv_id');
    ELSE
    if(nvl(x_msg_count,0) = 0) then
    dbms_output.put_line('no message return');
    else
    for I in 1..x_msg_count LOOP
    l_error_message := fnd_msg_pub.get(I, 'F');
    end LOOP;
    end if;
    --- HARD RESERVATION API fails ---
    dbms_output.put_line('Reservation API Error Message: '||l_error_message);
    END IF;
    EXCEPTION
    WHEN OTHERS THEN ------------------ In case of any pl/sql error
    l_error_message := SQLERRM;
    dbms_output.put_line('Plsql Error Message: '||l_error_message);
    END;
    but i am getting an error
    "Reservation API Error Message: INV_RSV_DS_SO"
    I am stuck and no idea how to fix this. Any help is appreciated.
    Edited by: 901524 on May 23, 2012 1:26 PM

  • Steps for SFS: Sales Order, Delivery, Invoice

    Hello,
    Can anyone provide me the complete steps for SFS for SAP ERP system?
    Regards,
    Ahmed

    Dear Ahmed,
    Do You mean Sales Flow Structure (SFS) in SD Module?
    If So,
    Enquiry                       VA11
    Quotation                      VA21
    Sales Order          VA01
    Delivery                       VL01N
    Invoicing                        VF01
    Best Regards,
    Amit
    Note: Also refer -
    [SAP SD Processing|http://www.sap-basis-abap.com/sd/sap-sd-processing-flow.htm]
    Have you searched in to Search Forum, before posting?

  • Crystal report link between sales order and picklist

    Hi,
    Good day!
    I am making a picklist document using crysal report. My requirement is to show the sales order number, cardcode, cardname, itemcode, released qty in the picklist. the tables i linked in crystal are the ff:
    RDR1.DocEntry linked to ORDR.DocEntry and ORDR.DocNum linked to PKL1.OrderEntry.
    I have a sales order with 2 items and then I processed picklist for it. When I run the report, my problem is that it shows the items twice.
    Scenario:
    Sales Order 1:
    Item A   2
    Item B   1
    When I run the report, it's like this:
    Item A 2
    Item A 1
    Item B 2
    Item B 1
    I'd already tried adjusting the links but still can't get it.
    Please help me.
    Thanks so much.
    SIncerely,
    Jackilou

    Hi,
    could you please describe how you solve this issue?
    Thank you very much!
    Regards,
    Tobias

  • Link Between Sales Order - Internal Requisition - Internal Sale Order

    Hi Expert,
    I tried writing the query to find the supply and demand details in ASCP Planning.
    In our scenario we created a sales order '5110416.AT PROJECT.ORDER ENTRY(6.1)' and launch the plan. It has created the plan order and after releasing it has created the internal requisition and then Internal sales order. But the supply sales order number is not populated in order_number column of msc_supplies.
    Please help me if I am missing some thing. Just for your info I have run the plan again and then also its not updated. Below is the query which I have written. This is very critical for me. Please advice.
    SELECT
    MS.ORDER_NUMBER,MS.ORDER_TYPE,MS.ORDER_LINE_NUMBER,MD.SALES_ORDER_LINE_ID,MD.ORDER_NUMBER
    FROM
    MSC_SUPPLIES MS,
    MSC_FULL_PEGGING MFP,
    MSC_DEMANDS MD
    WHERE 1=1
    AND MS.TRANSACTION_ID=MFP.TRANSACTION_ID
    AND MD.DEMAND_ID=MFP.DEMAND_ID
    AND MD.ORDER_NUMBER='5110416.AT PROJECT.ORDER ENTRY(6.1)'
    Thanks in advance.
    Regards
    RV

    Hi Suraj,
    In MSC Supplies Order_Number column contains the information for Planned Order, but not the Sales order. This same planned order number, once released from planning workbench, would be become the Work Order number of Purchase Req number, depending on the item make/buy code.
    However, if you would like to see the supply created for the particular SO, then you also need to create a join for MSC_Sales_orders table in your query. Sales orders after collection are stored in this table. Once the plan is run, relevant SO come into MSC_Demands with origination_type = 30
    Hope this answers your question.
    Regards,
    Kanishk Maheshwari.

Maybe you are looking for