Skip to Content
avatar image
Former Member

Purchase order triggering Sales order

I have a business scenario where the sales process happens between two internal companies. Company 'A' (ordering company) creates PO on Company 'B' (Supplying company). Company B inturn creates the Sales order, delivery, ships and bills to Company B. Here we require the automatic trigger of Sales order in Company B whenever a PO is saved in Company 'A'. Kindly suggest whether we can handles this requirements through any standard configuration process (similar to the one in Third Party process where the Sales order upon saving triggers Purchase Requisition in MM)

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Sep 07, 2010 at 10:07 PM

    Hi Rahul,

    You have two options

    A) Folllow 3rd party process

    1. Configure the S.L Categories in company A to create PR automatically.

    2. Schedule a batch job to create PO over to Company B.

    3. This PO should send O/B Idoc to Compnay B.

    4. I/B idoc should create SO automatically in Company B.

    B) Follow B2B process.

    1. You line item requirement type should trigger a Req class which is relevant for B2B.

    2. i believe it should create B2B PO

    3. PO Should have O/B idoc from company A to company B, You should have I/B idoc to I/B idoc to create SO in Company B.

    This is the outline flow and not contain all the config steps involved in ALE layer.

    Thank you


    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 07, 2010 at 07:00 PM


    Can you explain why you don't want to use intercompany stock transfer order?

    There you also go through purchasing part and SD for sales. There are some reasons why PO-SO is better option (like eg. no ship-to/sold-to concept for iSTO process) but on the other hand there is no standard way to automatically generate SO from PO document.

    For our customer we created some complex chains, involving automatic generation of multiple documents (eg. PO generates 2 other SOs and POs because goods need to flow through multiple companies).

    But it was based on custom solutions using BAPIs to create sales order.

    For your case one of the options would be to trigger an output from PO document which would call a BAPI to create SO document. Naturally some of the elements for SO should be determined within output logic, such as sales area etc.


    Dominik Modrzejewski

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 17, 2010 at 03:03 PM

    Hi Rahul,

    I am doing exactly similar interface at the moment. Where we can created SO wrt to PO using ALE IDOC.

    We have two plants where these plants relates each other as customer and vendor.

    Customer A orders via PO triggers NEU output and process code ME10, idoc "orders05" and messge "orders".

    Against this incoming idoc gets generated which creates SO.

    Process code ORDE, idoc type ORDERS05 and message "orders".

    You may also need to define data in VOE2 transaction for automatic determination of customer and vendor while generating idocs.

    Even in customer and vendor master u need to maintain the fields where it says customer no at vendor side and vice versa.

    Come back if this won"t suffice.

    Best regards,


    Add comment
    10|10000 characters needed characters exceeded