Sl.
no Determination Object Rules for determination
1 Sales document Sales Area
+ Document Type
2 Item category Document type
determination for Sales + Item category Group
document + Usage
+ High level Item Category
3 Schedule line category Item category of the corresponding item
determination + MRP type of the Material
4 Delivery document Delivery document default type attached to Sales document type
determination
5 Item category Copy form Sales document
determination for or
Delivery document Delivery Document type
+ Item category Group
+ Usage
+ High level Item Category
6 Shipping Determination Delivery Plant
+ Shipping condition (Customer Master - Sold-to Party)
+ Loading group(Matrial Master)
7 Route determination Departure zone of the shipping pt(Customizing)
+ shipping condition(SP)
+ Transport group(MM)
+ Transportation zone of the Ship to party(General Data)
8 Storage location Shipping point
determination + Delivery plant
+ storage condition
9 Picking determination On bases of MALA rule
Delivery Plant
+ Loading Group
+ Storage condition(MM)
(storage rule also assignment to Delivery type)
10 Packing determination Package usage
11 POD This object use for confirmation of delivery, based on which billing document
can create
12 Billing document Sales document type is maintained as default type
determination For Billing plan, Billing Type maintain under Billing Plan Type of Maintain Date
Category for Billing Plan Type
13 Account determination Chart of Accounts
+ Sales Org
+ Customer Account grp (Customer Master - Payer)
+ Material Account grp (Material Master)
+ Account key
[Link] Determination Object Rules for determination
14 Business area Plant/Valutaion Area
determination OR
Sales area
OR
Item division + Plant
15 Company code Sales organization uniquely attached to Company code
determination
16 Partner determination At -Account group level, sales document header level, item level, sales
document delivery level, Shipment level, Billing document level and item level
17 Delivery Plant The system will determine Plant details at following in given sequence
determination Customer - Material info record
From customer master Ship-to Party
From Material Master
18 Output determination Output determination at Sales document level, Delivery level, Billing level
19 Price determination Pricing procedure
Sales Area
+ Document Pricing Procedure indicator from Sale/Billing Document type
+ Pricing Pricing Procedure indicator from Customer Master (Sold-to Party)
20 Text determination 1)Customer Material Information Record
2) Customer Master (General text, Accounting text, Sales text)
3) Material master text (Sales text or PO text)
21 Warehouse Ware house number
determination + Plant
+ Storage location
22 Lean Warehouse Lean ware house activate,
determination Plant
+ Storage Location
+ Ware house number
23 Tax determination Destination Country of Ship-to Party
+ Departure Country of Shipping Point
+ Tax Classification for Customer from Customer Master
+ Tax Classification for Material Master
24 Routing determination Shipping point
+ Delivery plant
+ Loading condition
+ Shipping condition
25 Material determination Create condition record
Maintain Customer Material record
26 Product substitute Create condition record
27 Product Exclusion Create condition record(Not to sale any particular product)
28 Product listing Create condition record (Sale of one particular product)
[Link] Determination Object Rules for determination
29 Credit check Credit check at Sales document level OR at Delivery OR at Good issue Risk
group at Sales document level and Risk category from Customer Master, Item
category credit check should be activate
30 Incomplete log Incomplete log assign to Status group, which is assign to Sales document,
Item category or Schedule line level
31 Rebate condition setup customer master billing info checked, Sales organization activate, Billing
document activate
SAP HANA (high-performance analytic appliance) is an application that uses in-memory database technology
that allows the processing of massive amounts of real-time data in a short time with an enriching user
experience using FIORI apps.
Status tables VBUK and VBUP have been eliminated and the new status fields have been added to:
VBAK and VBAP for sales order header and item
LIKP and LIPS for delivery document header and item
VBRK for billing document header
No status fields are present for billing items.
Advantages:
Reduced memory footprint : Since fewer tables are involved this means reduction of redundant data and
simplified document flow.
Now if we need to query the order table on the basis of document status we can simply do so by 1 single query
on VBAK table instead of join on VBAK and VBUK.
Third Party process –
Creating a Third-Party Item Manually
If you do not use SD, you can plan a third-party business transaction using a purchase requisition. To enter a
purchase requisition with a third-party item manually, proceed as follows:
1. Enter the item category s and an account category (for example, x - all account assignments). When you
press ENTER, the account assignment screen is displayed.
2. Enter the account assignment data (for example, the number of the G/L account). Which account
assignment data you have to maintain depends on the account assignment category.
3. Save the purchase requisition.