VT01N Config Steps
VT01N Config Steps
VT01N Config Steps
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).
Sales order type used for third-party – OR (standard order)
Item category for third-party – TAS
Schedule line category for third-party – CS
Let’s look deeper into the settings in the system done for automatic and standard third-party process:
ITEM CATEGORY TAS:
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.
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:
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)
The purchase requisition needs to be converted into purchase order in MM (t-code me21n). The purchase
order document type is NB (standard order), item category S, that must be assigned to account. Thus
account assignment category needs to be given. In this example it is X (automatically taken during
conversion from purchase requisition, as it was defined in item category CS).
The definition of acct assignment category can be found in IMG: MM->Purchasing->Account assignment-
>Maintain acc.***. categories:
Note: There is also a third-party account assignment category created in the system and its definition
looks as follows:
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.
Prerequisites for the automatic creation of purchase order are as follows:
The indicator automatic purchase order needs to be marked in item category definition (item
category ALES has it by default)
Unique source of supply needs to exist for third-party item
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.
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)
THIRD-PARTY SALES
Introduction
In third-party sales the company transfers the sales order to an external vendor. This vendor delivers the goods directly to
the customer and invoices the company. The customer receives an invoice from the company’s sales office.
Maintain:
In Sales: General/Plant:
Process flow
Sold to Party,
Ship to party
Customer PO no. &
Matl. No. (Third party material)
Ordered Qty.
A screen with the following details will get created.
Then click on the continue button
Pick the Schedule lines.
A screen will be displayed with Delivery date, Rounded qty. and Confirmed qty.
Note: Before saving the sales doc. Purchase requisition no. will not get created
Save the Sales Order.
On saving the sales order, purchase requisition is generate in the back ground.
To know the purchase requisition number, either go schedule line tab in item level of the sales order and check in
procurement tab or go sales order in status overview.
Step: 3 Adopt Purchase Requisition into Purchase Order or create PO with reference to
PR
Use TCode: ME21N
Keep the standard order (Which you have defined in the Document type)
Enter the purch. Org.
Purch. Group. and Company code
Enter the Purchase Requisition no.
After Entering the Details, Press Enter Button
A screen as appears with all the details like Matl. Po. Qty, Deliv. Date, Net price Curr etc.
Then Save the PO.
Hence PO is created
Step: 3 Release the PO. Number. (Based on release stategy in PO type used)
TCode: ME29N
Now Release the Order.
On release it will give following message
"Purchase Order no. xxxxxxxxx changed"
We assign plant of other company code to designated sales area (distribution channel for inter-
company sales) of our company code, and we can use standard SAP inter-company pricing for
the same. Here we can specify any special prices applicable via condition types IV01 & IV02.
There are condition types PI01/02 which serve as reference condition types for IV01/02.
IV01 & IV02 are used with subtotal 9 (gross value) and routine 22 (inter-company billing) as
shown below.
Now, we will look at two company codes 1002 & 3000. Go to IMG–>Sales & Distribution –>
Billing –> Intercompany Billing
First, we define order types for inter-company billing. Specify IV (standard billing document
type) in required sales document type inVOV8.
or IMG–>Sales & Distribution –> Billing –> Intercompany Billing –> Define order types for inter-
company billing
Here, I have assigned 2010 plant (company code 3000) to sales area 3031/71/00(company code
3000) for internal costing.
I have created a customer id (XD01) in 1002 and assigned the same to the sales organization of
1002. This customer id will be payer & represent 1002 for inter-company billing of plant. IMG–
>Sales & Distribution –> Billing –> IntercompanyBilling –> Define internal customer number by
sales org
Customer places an order on company code 1002. 1002 decides to deliver from plant 2010
belonging to company code (3000). I have created normal sales order and saved. Inventory
postings for the delivery are in plant 2010 & company code 3000. Further, two billing
documents are generated with reference to the same delivery document. Document flow is as
under:
First billing document created in company code 1002 and payer is customer.
Create second invoice with reference to the same delivery document number. This second
invoice is the inter-company billing document created in company code 3000 and here payer is
the first company (1002 here) for sales area 3031/71/00. Price (IV01) will be active for inter-co
bill where as PR00 will be active for customer bill.
Related accounting documents & excise documents can be generated as per pricing procedure
with reference to respective billing documents.