Professional Documents
Culture Documents
Trading goods are movable goods intended for commercial exchange. Examples of trading goods
are market goods, consumption goods and durable goods. Trading goods are always bought and
re-sold by your company. The material master record for trading goods therefore always
contains purchasing data and sales data. Trading goods are managed in the SAP System using
the key HAWA.
Trading goods are always procured externally and then sold. A material master record of this
material type can contain purchasing data and sales data.
Example: An electronics shop of HP sells computers manufactured by HP, along with these
computers it also sells mouse, printers, scanners, screens etc. that are NOT manufactured by HP
but are bought and then sold from this electronic shop. This process uses HAWA (goods like
mouse, printers etc. etc.) but it is NOT 3rd party process but trading process.
A car company sell CAR as a Finished Goods (FERT) but it can sell some other accessories like
Audio System, mobile Charger, etc. from other outside vendors a Trading good. These audio
system can be brought by the company and sell as a TAS item category but when these material
have shortage, in that case it can be order from the vendor as a Trading Goods and delivered to
the end customer directly.
Introduction
In third-party order processing, your company does not deliver the items requested by a
customer. Instead, you pass the order along to a third-party vendor who then ships the goods
directly to the customer and bills you . A sales order may consist partly or wholly of third -party
items. Occasionally, you may need to let a vendor deliver items you would normally deliver
yourself. The following graphic shows how a third party business transaction is processed.
Process Flow
The processing of third-party order is controlled via material types.
Page 1 of 40
SAP SD NOTE-10 Third Party Order Processing
Material types define whether a material is produced only internally can be ordered only
from third-party vendors, or whether both are possible.
For example, a material that is defined as a trading good (HAWA) can only be ordered
from a third-party vendor.
However, if you manufacture your own finished products, you may also want, from time
to time, to be able to order the same type of product from other vendors.
Method 2)
Page 2 of 40
SAP SD NOTE-10 Third Party Order Processing
Page 3 of 40
SAP SD NOTE-10 Third Party Order Processing
If, as an exception, you use a third-party material, change the entry TAN to TAS in
the ItCa field when processing the sales document. The item is then processed as third-
party item.
The procurement type should be marked as (X) meaning both types of procurment ( in
house manufacturing and external procurement).
If address data for the ship-to party is changed in the sales order in third -party
business transactions, the changed data will automatically be passed on to purchase
requisition and also to the purchase order ,if one already exists.
In the purchase order, you can display the address data for the ship -to party in the
attributes for the item. You can only change the address data for the ship-to party in
the sales order for third-party business transactions, and not in the purchase order.
Configuration steps:
Page 4 of 40
SAP SD NOTE-10 Third Party Order Processing
Define Schedule Line Categories
Page 5 of 40
SAP SD NOTE-10 Third Party Order Processing
Order type: [NB ]
Purch.requis. Stand.
It is a purchase order type. Ex: Document type NB can be assigned. In individual
purchase order and third party sales order system automatically creates purchase
requisition. So as to create it automatically purchase requisition document type should
be assigned here.
Example
Validity periods and customer purchase order numbers are required entries for both
contracts and scheduling agreements. In this case, the system automatically proposes
the same incompletion procedure for both types of document.
Page 6 of 40
SAP SD NOTE-10 Third Party Order Processing
Billing relevance: [F] = Order related billing doc. Status according to invoice qty.
The value determines what kind of billing document it has to generate for this item.
That is order related billing document or delivery related billing document.
Relevant for order-related billing documents based on the invoice receipt quantity
(third-party business transaction). The system transfers the order into the billing due list
only after the vendor invoice has been received and processed in the purchasing
department. After the receipt of each invoice, a customer invoice is created for the
quantity that appears on the vendor invoice. The order has status "Billed" until the next
vendor invoice is received.
Item category TAS (Third party item) is set up with billing relevance "F" in the standard
system.
You can make the control setting as to whether the invoice receipt quantity or the
goods receipt quantity should be relevant for billing in the copy control for billing on the
item level in the billing quantity field. (In Customizing, choose Sales and Distribution ->
Billing -> Billing documents -> Maintain Copying Control for Billing Documents ->
Copying Control: Delivery to Billing Document -> Item, then select an item category.)
Page 7 of 40
SAP SD NOTE-10 Third Party Order Processing
IMG Sales and Distribution Sales Sales Documents- Sales Document Item
Define Item Category Groups
Page 8 of 40
SAP SD NOTE-10 Third Party Order Processing
Page 9 of 40
SAP SD NOTE-10 Third Party Order Processing
Page 10 of 40
SAP SD NOTE-10 Third Party Order Processing
10. Maintain purchasing area and Maintain Purchasing Area Determination (optional)
NOTE: The requirements for 'Maintain Purchasing Area' and 'Maintain Purchasing Area
Determination' will only be available if your system is configured as an SAP Retail
System. It's not because of different releases which caused it appear/ didn't appear in
the customizing.
Page 11 of 40
SAP SD NOTE-10 Third Party Order Processing
Page 12 of 40
SAP SD NOTE-10 Third Party Order Processing
Page 13 of 40
SAP SD NOTE-10 Third Party Order Processing
Page 14 of 40
SAP SD NOTE-10 Third Party Order Processing
Page 15 of 40
SAP SD NOTE-10 Third Party Order Processing
Page 16 of 40
SAP SD NOTE-10 Third Party Order Processing
Enter the Vendor no. Material no., Purchasing org. and Plant and Create Info Record.
Serves as a source of information for Purchasing. The purchasing info record (also
referred to in abbreviated form as the "info record") contains information on a specific
material and a vendor supplying the material. For example, the vendor's current pricing
is stored in the info record.
Page 17 of 40
SAP SD NOTE-10 Third Party Order Processing
Page 18 of 40
SAP SD NOTE-10 Third Party Order Processing
Page 19 of 40
SAP SD NOTE-10 Third Party Order Processing
Select the Line Item and Click on Menu Goto--> Item--> Schedule Line
Page 20 of 40
SAP SD NOTE-10 Third Party Order Processing
Below is the screen for Schedule Line CS for Third Party Sale and confirm quantity
is “0” since quantity will be deliver by the vendor as available.
After saving sales order with item category TAS the purchase requisition is
automatically created. In order to see the document go to: Environment -> Status
overview and expand data for item, then expand data for purchase requisition as well:
Double click on the requisition number and you will be taken to the purchase requisition
document. The other way is to go to schedule line where you can find the purchase
requisition number.
Page 21 of 40
SAP SD NOTE-10 Third Party Order Processing
If third-party item has more than one schedule line with confirmed quantity > 0, then
purchase requisition is created for each schedule line.
It is wise to have the vendor determined in source of supply at this stage of the process
(i.e. source list)
OR
Page 22 of 40
SAP SD NOTE-10 Third Party Order Processing
Double click on the purchase requisition and verify all the details
The invoice verification with reference to purchase order needs to be created when
invoice from vendor arrives to enterprise (t-code MIRO). The value and, if goods
receipt was done earlier, the quantity are proposed by the system. When the incoming
invoice is posted, following are updated:
Page 23 of 40
SAP SD NOTE-10 Third Party Order Processing
Page 24 of 40
SAP SD NOTE-10 Third Party Order Processing
Page 25 of 40
SAP SD NOTE-10 Third Party Order Processing
The invoice verification with reference to purchase order needs to be created when
invoice from vendor arrives to enterprise (t-code MIRO). The value and, if goods
receipt was done earlier, the quantity are proposed by the system. When the incoming
invoice is posted following are updated:
Page 26 of 40
SAP SD NOTE-10 Third Party Order Processing
Enter the invoice date, amount, and at the item level, change the tax code to I0
(A/P sales tax exempt), and jurisdiction code to IL0000000 and click on
Simulate.
Check the GL accounts.
Once invoice receipt has been entered, the customer can be billed as well (T-CODE
VF01). Since an outbound delivery doesn’t exist for the third party the invoicing will
be order based. In the item category TAS definition, the billing relevance indicator is
set to F by default. That means: relevant for order-related billing document: status
Page 27 of 40
SAP SD NOTE-10 Third Party Order Processing
according to invoice receipt quantity. That is, the system allows invoicing the order
only when vendor’s invoice has been processed in invoice verification.
The customer invoice is created for the quantity specified in the vendor invoice. The
setting in the copy control for the third-party item category from sales document to
billing document specifies that the quantity from the invoice receipt is transferred to
the billing document instead of the order quantity (billing quantity indicator in copy
control is F)
Enter the sales order number and created the billing doc for Customer.
Page 28 of 40
SAP SD NOTE-10 Third Party Order Processing
Page 29 of 40
SAP SD NOTE-10 Third Party Order Processing
NOTE: The requirements for 'Maintain Purchasing Area' and 'Maintain Purchasing Area
Determination' will only be available if your system is configured as an SAP Retail
System. It's not because of different releases which caused it appear/ didn't appear in
the customizing.
Page 30 of 40
SAP SD NOTE-10 Third Party Order Processing
Go to Next screen option
Specify Reconciliation account number [ ] sort key [ ]
Cash management group [A1]
Go to Next screen option
Order currency [INR]
Save and Exit
2 Enter T-Code ME5A in the command bar and hit enter.List of purchase requisitions
screen.
Enter material and plant
Click on the purchase requisition number.
Purchase requisition for the standard third party sales order created.
Double click on PR no to check the source of supply and other details > Back.
3. Enter T-Code ME21N in the command bar and enter. Create purchase order with
respect to PR.
Click on the document overview screen at the top left corner of the screen.
Click on the ‘variants’ icon and Select the purchase requisition and click on
“adopt” icon under the document overview.
Check the purchase Order tabs such invoice etc.. and save the document.
4. Enter MIRO in the command bar to create Invoice verification for vendor.
Enter the company code and hit enter.
Enter the invoice date, amount, and at the item level, change the tax code to I0
(A/P sales tax exempt), and jurisdiction code to IL0000000 and click on Simulate.
Check the GL accounts.
Click on Save/Post
5. Enter VF01 to create billing document for the customer and hit enter.
Overview of the billing items.
Save the billing document
Question: How vendor is determined in third party sale scenario at purchase order
step?
Answer: In the Third party, scenario when the PR is triggered based on the Item
Category, Vendor is determined from the source list (ME01) for the material and plant
combination, which flows into the PR. The Vendor is marked as fixed in the
Source list so that the PR is created automatically.
Page 31 of 40
SAP SD NOTE-10 Third Party Order Processing
Page 32 of 40
SAP SD NOTE-10 Third Party Order Processing
In third-party process the delivery of the goods required by the customer is not done
by sales organization where customer orders. Instead, the request of the goods is
forwarded to an external vendor who sends the material directly to the customer.
SALES ORDER
Third-party process is triggered when the sales order with third-party item is created.
Depending on settings done in customization third-party item categories can be
automatically determined by the system (automatic third-party processing) or they
can be changed from standard item to third-party item category in sales order (manual
third-party processing).
Let’s look deeper into the settings in the system done for automatic and standard
third-party process:
Page 33 of 40
SAP SD NOTE-10 Third Party Order Processing
Create PO Automatic indicator is not marked in TAS. ALES is an item category for
third-party processing where this indicator is marked.
Item category TAS will be determined automatically for standard order (OR) and item
category group BANS (third-party item). Item category group can be found in
material master, Sales: Sales org.2 view.
Page 34 of 40
SAP SD NOTE-10 Third Party Order Processing
Data: Order type = NB, Item Category = 5 and Acct.AssgntCat = X is the data for
Purchase requisition. If it is filled like above the purchasing requisition will be created
automatically as standard purchasing requisition (NB), with item category S and
acc.assign cat X. The mapping of item category (from 5 to S) can be found in IMG:
MM->Purchasing->Define External Representation of item categories. The definition of
account assignment category can be found in IMG: MM->Purchasing->Account
assignment->Maintain acc.***. categories
After saving sales order with item category TAS the purchase requisition is
automatically created. In order to see the document go to: Environment -> Status
overview and expand data for item, then expand data for purchase requisition as well:
Page 35 of 40
SAP SD NOTE-10 Third Party Order Processing
Double click on the requisition number and you will be taken to the purchase requisition
document. The other way is to go to schedule line where you can find the purchase
requisition number.
If third-party item has more than one schedule line with confirmed quantity > 0, then
purchase requisition is created for each schedule line.
It is wise to have the vendor determined in source of supply at this stage of the process
(i.e. source list)
Note: There is also a third-party account assignment category created in the system
and its definition looks as follows:
Page 36 of 40
SAP SD NOTE-10 Third Party Order Processing
As it was written before – the purchase requisition is created automatically when sales
order is saved. It is possible to automatize the next step, the creation of purchase
order, as well. The ALE function is used for that purpose. The indicator for the
automatic creation of purchase order is not set for TAS item category. However, there
is a special item category – ALES which can be used instead in third-party process.
The indicator for the automatic creation of purchase order is marked in ALES by
default.
Page 37 of 40
SAP SD NOTE-10 Third Party Order Processing
At least the document type for the purchase order must be assigned for Sales
organization in customizing under Enterprise structure->Definition->SD-
>Define, copy, delete, check sales organization
If all above prerequisites are set up correctly, purchase order will be created when
sales order is saved. Then, it can be found in document flow in sales order.
GOODS RECEIPT
Since during third-party processing goods are moved directly from the vendor to the
customer, inventory management is not affected by this event. However, if sales
department would like to document and enter delivery to the customer in the system it
is possible depending on settings in customization. If account assignment category 1 is
used in item category definition, goods receipt is not possible, as the goods receipt
indicator is not set for this account assignment cat. If account assignment category X
is used, goods receipt is possible.
The goods receipt posting (t-code migo) would have the following effects:
The goods receipt posting should happen when the vendor reports that outbound
delivery was executed or customer confirms that delivery arrives.
Since no flow of goods occurs in the enterprise, the goods receipt posting results in
updates on value basis.
Page 38 of 40
SAP SD NOTE-10 Third Party Order Processing
INVOICE RECEIPT
The invoice verification with reference to purchase order needs to be created when
invoice from vendor arrives to enterprise (t-code MIRO). The value and, if goods
receipt was done earlier, the quantity are proposed by the system. When the incoming
invoice is posted following are updated:
Once invoice receipt has been entered, the customer can be billed as well (T-CODE
VF01). Since an outbound delivery doesn’t exist for the third-party the invoicing will
be order based. In the item category TAS definition, the billing relevance indicator is
set to F by default. That means: relevant for order-related billing document: status
according to invoice receipt quantity. That is, the system allows invoicing the order
only when vendor’s invoice has been processed in invoice verification.
The customer invoice is created for the quantity specified in the vendor invoice. The
setting in the copy control for the third-party item category from sales document to
billing document specifies that the quantity from the invoice receipt is transferred to
the billing document instead of the order quantity (billing quantity indicator in copy
control is F)
Whenever customer find the damaged or defective goods on third party material we do third party
return process.
The third party return process is, whenever customer return the goods we can create the third party
return order.
when we save the return order system is automatically create purchase requisition, this “PR” based
to we create the return “PO” in this line item we check return in “PO”.
This “PO” will send to the vendor, vendor receive the goods from customer, than vendor rice the
credit memo to company, based on this credit memo we rice the credit memo to the customer.
In third party return item category “TASG” we check return and we specific the
billing relevance is “F”.
Page 39 of 40
SAP SD NOTE-10 Third Party Order Processing
When we creating the third party return order system determine the item category
“TASG” based on item category determination.
VBRK/VBRP : “002”
Positive/ negitve”+”
Page 40 of 40