Reg.Purchase order against sale order( E )

Question

Dear Experts
I configured PO against cost centre (K - Cost center and G/L A/c is created) and it is working.But I want to configure against sale order (E).what is the configuration required. Pls advise in details
Thanks
Rajakumar.K

Answer 1

Dear Raja,
Third-party order processing (for direct-to-customer delivery/drop shipment) is triggered when a sales order containing a third-party item is created.
When this occurs, the system automatically generates a purchase requisition item of the category u201Cthird-partyu201D for each delivery schedule line of the sales order item.
This requisition item is converted into a purchase order (PO) item. Depending on the confirmation control key, the quantities/dates in the sales order are confirmed when the PO is created or an order acknowledgment is maintained.
If you create a third-party item without referencing a requisition generated from a sales order, this is not third-party order processing in the foregoing sense: a matching-up of the data between the SD sales order and the purchase order cannot be carried out in such cases!
Sales Order
In the standard system, the sales order item for the third-party process has the item category TAS (this is found automatically if the item category group BANS has been set in the material master, or it can be changed manually). In the standard system, the schedule line category CS is found for the item category TAS. It is specified in Customizing for the schedule line category CS that a purchase requisition (type NB) with the item category '5' (third-party) and account assignment category 'X' is generated.
The number of the requisition that is generated can be displayed via the delivery schedule lines in procurement.
If a PO is generated from this requisition, it can be seen in the document flow for the SD sales order (Environment  Document flow).
Purchase Requisition
The requisition is generated via the function module ME_REQUISITION_EXT. An important characteristic is that the field EBAN-ESTKZ (creation indicator) contains a 'V'. If a third-party requisition is created in dialog mode, this field does not contain the indicator u2018Vu2019 u2013 that is to say, this is not a third-party process in the sense defined. A source determination process is carried out at the time of creation. The purchase order units found during this process are adopted! The account assignment, containing the number, item, and schedule line of the sales order, cannot be changed in the requisition. The account assignment is the u2018pointeru2019 between the requisition and the SD order!! Since Release 4.6, the delivery address cannot be changed either. The address of the goods recipient (ship-to party) from the SD order is adopted as the delivery address (caution: this can be located both at header and item level in the SD order).
There is a requisition item for each delivery schedule line in the sales order!
Purchase Order
Purchase order items generated from the above requisitions contain EKPO-STATU = 'V'. The delivery address comes directly from the sales order (see LMEPOF3T MEPO_ITEM_FILL_ADDR) and cannot be changed. Neither can the account assignment be changed; here too it is the 'pointeru2019 between the PO and the sales order. In the standard system, the account assignment category is 'X', with KZVBR = ' '. Since the account assignment is located at item level, you must not convert several third-party requisitions into a single PO item, otherwise the update of the sales order is liable to fail!
An 'actual' goods receipt does not take place with regard to a third-party item. The 'WEPOS' indicator is not set for the item categories 'S', but can be set manually. The posting of a GR results merely in a value update here. The entry of a vendor invoice can be made dependent on the prior entry of a GR. In the third-party process, this only makes sense if you wish to prevent the customer from receiving an invoice before having received the goods. A goods receipt should be recorded when the vendor reports the outward delivery.
At the time of saving, the document flow and confirmations are updated in the SD order. If problems should arise on the SD side due to changes (e.g. the customer has been blocked), an error message is issued here first!
In the case of third-party items generated without reference to a 'third-party requisition', i.e. the item category u2018Su2019 is merely entered manually, there can be no update between SD order and purchase order. Here, for example, the delivery address is not read from the sales order u2013 it must be entered manually (mandatory field).
Sanjeev