You are on page 1of 3

SAP creates a purchase requisition (P/R) for this line item, which

then converts it
into a purchase order following the regular procurement process.
The purchase
order is released and is sent to the vendor, and the vendor supplies
the goods to the
customer and sends you an invoice for the goods delivered. You
post the invoice
receipt (I/R) against the purchase order via transaction code MIRO.
This I/R then
updates the VPRS cost and sales order billing status for the line
item (I/R done
billing due), and the billing document is created for the delivered
quantities as per
the normal billing process.
To support the third-party processing, standard SAP comes with
item category TAS
and schedule line category CS. Schedule line category CS contains
the defaults for
the purchase requisition type, item category, and account
assignment and thus is
responsible for triggering the P/R for the order line items. You can
have one or more
line items in the purchase requisition, depending upon how many
schedule lines
exist in your third-party line item in the sales order. So, a one-line
item with two
schedule lines means two individual line items in the purchase
requisition.
Item category TAS comes with billing relevancy F, which means that
the billing for
the order item will be possible only when the I/R for the purchase
order is posted.
The indicator F also controls the billing status for the sales order,
because the billing
status remains not due for billing until you post the invoice receipt.
This way,
you bill multiple invoices to the customer based on the I/R
quantities. Each I/R
updates the invoicing status only for the quantity received by the
I/R. If you dont

want to wait for the I/R posting for billing your customer, you can
set up the billing
relevancy for your third-party item category as B (relevant for orderrelated billing
on the basis of the order quantity). In this case, the customer will be
billed for the
entire order quantity irrespective of the I/R processing.
You can configure SAP to do manual as well as automatic third-party
order processing.
If you normally fulfill the customer order from your own stocks and
require
case-to-case procurement only for a particular product via thirdparty processing,
you can follow the manual process. In manual processing, you
change the item category
on the overview screen of the sales order to TAS, which then
triggers the purchase
requisition process. If you have a particular product that is always
procured
via a third party, you can set up an automatic process also. In an
automatic process,
you assign the item category group BANS on the Sales Data2 tab of
the material
master. In standard SAP, under item category determination rules,
BANS is linked
to item category TAS, and therefore when you create an order with
a material having
BANS, SAP automatically determines the item category as TAS.
When you create a third-party order, SAP takes into account the
lead times for
automatic delivery scheduling for the third-party line item in the
sales order. This
means that the time required by the vendor to deliver the goods
and also the time
taken by your purchasing department for processing the purchase
order together
impact the schedule line confirmation date for the corresponding
third-party line
item in the order.
When you create a purchase order using the purchase request
corresponding to the

third-party order line, SAP automatically updates the purchase order


number in
the document flow of the sales order. Any changes in the delivery
dates or quantity
thereafter in the purchase order automatically updates the
confirmed quantity and
confirmation date in the corresponding schedule line on the thirdparty sales order,
but the reverse way is not allowed. Any changes in the quantity or
date in the sales
order does not change the purchase order quantity or delivery
dates. It is therefore
always suggested to make changes in the purchase order and not in
the sales order.
If you want to copy any text from the sales order to the purchase
order, enter that
into the text field PO text at the sales order item level because this
gets copied over
to the purchase order item text field during the third-party
processing

You might also like