Core Configurations

Core Configurations
Parminder
Order Type Configurations
Header Config
Document Category
Transaction Grouping
Leading transaction type
Standard from SAP
Used to write Code & In Functional Specification
Indicator
Sub Category
Or Further classification than category
Block
Blocked
Use Case
For Cutover Purpose Only
Return Order without Reference
Existing order with different number ranges
Not Blocked
Only Automation creation is allowed
Use Case
E Commerce order creation from 3rd party software
Integration with 3rd Party Software
Order Upload
Number Ranges
General Control
Reference Mandatory
Material Entry Type
Used For Catalog Functionality in Retail
Check Division
Match Customer & Product Division and control error
Item Division
If Division need to be taken from Product
Probability
Used In Inquiry & Quotation to Calculate Pipe Line Conversion
For Sales Order Document always 100
Read Info Record
Determines whether the system reads the customer material for the sales document type.
Credit Limit Check
If Credit Check needs to be Done
Only D is allowed in S/4 Hana
Credit Group
For Credit Management Functionality
Check Customer Ref
Warning Control if Same PO/Customer Ref is used for same Sold to party
Also Called Duplication check
Enter PO Number
IF customer Ref number is blank system will propose order number as PO/Customer Ref number
Output Application
Controls Output Determination/ Output Management
Commitment Date
Used In Availability Check - Schedule Line confirmation
Delivery time field is copied from quotation or contract
Order Header
A
Does not commit if delivery time does not exist
B
If delivery time exist confirms as per delivery time or as per first required date
C
Works as B , If sales order is saved again and more favorable commitment exist it will reconfirm
Display Preceding Docs
Provides information of previous document is sales overview tab
Assignment Order Type 01 - General Control - Create Document
Create your custom Order Type
Change Number Ranges & See Impact
See Impact of Reference Mandatory
Explore Check Division & Item Division
Explore Customer Material Info Record Functionality
Check impact of order type tick
Explore Check Customer Ref
Explore Enter PO Number
Explore Doc Type Header Block
Transaction Flow
Screen Seq Grp
Control Screen Sequence Flow of Transaction
How VA51 (Item Proposal) is different form VA01
IF screen sequence need to be changed we need to take help from technical consultant
Technical Detail Information
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/
Display Range
Sub items need to be shown or hide
F code for overview screen
Controls Which Screen Should open once we press enter in VA01
Transaction Group
Controls the types of sales documents you can process with certain system transactions in sales processing
Do not change
Links with table maint.
In completion Procedure
Status Controls that when we create sub seq document like delivery or billing system shows that document is not completed
Example Delivery can be created or not
Assignment
IF IC Dialog box is tick system will not allow to save before completion log is completed
Quotation Message
System Display if quotation exist for sales order you are entering
Outline Agreement Message
System display message if contract exist
Additional indicator to find more contracts if sold to party exist as partner function or part of customer hierarchy
Document Pricing Procedure
Controls Pricing Determination
Message Master Contract
Used in Contract document types
To Control master contract reference
Alternate Document type
System shows options to switch document type while punching order
Product Attribute
BP
MM02
Sales order warning/error
SO Document Type Assignment 2 - Create Document
Change F code for Overview screen and see impact on sales order creation
Create Your own In completion Procedure
Play around with IC Dialog field and show impact
Play around with status group and show impact
Check with In completion log tick and without tick see the impact
Create Quotation & Then sales order and see impact of Quotation Message Config
Create Contract & Then sales order and see impact of Contract Message Config
Maintain Product attributes in material and customer and see impact of config - Mat attribute
Maintain Lead Time In Config and see impact on sales order req del date
Check Impact of Immediate delivery on sales order creation
Check Impact of Delivery Block on sales order creation
Scheduling Agreement
Shipping
Delivery Document type
Auto proposed once delivery is created from sales order
Immediate Delivery
Delivery creation with sales order save
Delivery Block
Can be used for return order
Two step Process
Shipping Conditions
Can be used as default ship condition if not maintained in customer master
By default, the system proposes shipping conditions from the customer master record of the sold-to-party during sales document processing.
The proposal from the customer master record is overwritten by the shipping conditions defined in Customizing for the sales document types.
Used for shipping point determ
Ship Con Ship to party
To check shipping condition from ship to party
Only works if default shipping condition not maintained in order type
Values
Blank
1 . Order type ship condition
2. If order type is blank take from sold to party
3. maintain manually
A
1. From Ship to Party
2. Maintain manually
B
1. From Ship to Party
2. Sold to Party
3. Maintain manually
Billing
Dates Control
Goods Recieving Hours
BP - Main
Contract
Availability Check
Business Transaction
Used for Rule Based ATP
Used to get integration with APO >> GATP
SO Document Type Assignment 3
Create Document - Shipping cond & Shipping point
Create Shipping Point & Assign to your plant
Maintain Shipping type in Order type and customer master - show difference
Determine Shipping Point with Shipping condition
Create Document - Unloading Points
Create Unloading points in Customer Master
Maintain Good recieving hours
Show impact in Sales Order
Create Document
Maintain Propose Delivery Date & Show Impact
Maintain Cust Ref Date & SHow Impact
Maintain Lead time in Days & Show Impact
Item Category Configurations
Generic Info
T code : VOV7
Path
Examples of Item Categories
BOM Header Pricing
BOM Item Pricing
Material Determination Header Pricing
Material Determination Item Pricing
Business Data
Business Data Screen
Item Type
functioning of the line item. i.e. whether the item is normal item (standard item) or Text item or value item or packing item.
Standard or Normal item: - It is the item which is sold to customers.
Text item: - It is the item which consists of some information and which we deliver to customers along with the main product and which we never sell to customer. Ex. - User manual, catalogue, booklet etc.
Value item: - It is an item which consists of certain value and which is delivered to customers and which we never sell to customer. Ex. – Gift voucher etc.
Package item: - It is the item which is used to pack the main item. Ex. – cold drink bottle, Gas cylinder, etc.
Business Item
Check box
This field controls whether to change the business data at item level or not.
If we check this then system will allow changing the business data at item level. If we uncheck this system will not allow to change the business data at item level. The business data at item level will be disabled
Business data is the data, which copies into sales order from sales, shipping, billing Tab‟s of customer master.
The table for business data is [VBKD].
Completion Rule
For inquiry “AFN” completion rule is “A” (item is completed with the first reference).
For quotation “AGN” completion rule is “B” (item is completed after full quantity has been referenced.
For quantity contract “KMN” completion is “C” (item is completed after the target quantity is fully referenced)
For value contract “WKN” completion rule is “E” (item is completed after full target value is referenced).
Completion rule is applicable only between sales document to sales document and completion rule is not applicable between sales documents to delivery document. That is the reason TAN does not have completion rule.
Schedule line allowed
This field controls whether to determine schedule line tab into sales document line item or not.
If we check this then only schedule line tab will be determine into sales document line item.
If we uncheck this then schedule line tab will not be determined.
The below item categories will have schedule line allowed uncheck:- G2N, L2N, KMN, WKN, TATX
Special Stock
Make to order stock “E” (indicator)
TAK item category will have special stock indicator “E”.
This controls while creating sales order, system will consider only sales order stock, and system will not consider unrestricted stock.
IPO - Individual Purchase Order Stock Indicator E
In IPO process when we receive the stock from vendor the stock will be reserved to particular sales order number.
Special stock indicator “E” controls that while doing delivery in IPO process, system will consider sales order stock;
system will not consider unrestricted stock.
Consignment Stock W
KEN – “W”: - This field control that while doing delivery in consignment issue the stock will be reduced from consignment stock.
KRN “W”: - This field controls that while doing return delivery in consignment return the stock will be added to consignment stock.
Item relevant for delivery
This field is only applicable for text item or value item. This field is not applicable for standard item.
If text item and value item is relevant for delivery then check this field.
Billing relevance
This field controls whether item is relevant for billing or not and it also controls whether item is order related billing or delivery related billing.
item categories are not relevant for billing:-
 [AFN, AGN, WKN, KMN, TATX, KLN, KBN, KAN]
Item categories are delivery related billing: - (A)
o [TAN – „A‟, KEN – „A‟, TAB – „A‟, TAK – „A‟, TAQ – „A‟, TAX – „A‟]
item categories are order related billing (C)
o [REN – „B‟, KRN – „B‟, BVN – „B‟, G2N – „C‟ (order related billing status according to target quantity), L2N – „C‟]
Billing Relevance F
The billing relevance for TAS is “F” (order related billing status according to invoice quantity).(MIRO)
Billing relevance “F” controls that while creating invoice to customer in third party process system checks whether MIRO is created or not.
If MIRO is created then only system will allow creating invoice to customer.
Billing relevance “D” (relevant for Proforma invoice)
In free of charge delivery and consignment fill up even though the process is not relevant for billing, in India scenario we have to raise proforma invoice while delivering goods to customer.
For Proforma invoice billing relevance is “D”.
Billing relevance “K”
We use billing relevance “K” if we want to create partial invoice to single delivery
Billing relevance “G”
In third party process we can also use “G” (with shipping notification).(MIGO)
Billing relevance “G” controls that while creating invoice to customer in third party process system checks whether MIGO has been created or not.
If MIGO is created then only system will allow creating invoice to customer.
Returns
Whether item is delivering to customer or coming back from customer.
it controls the accounting entry at the time of invoice.
REN, KRN, G2N and KAN will have return check
Any document types if document categories are “H” or “K” for those item categories we have to check return.
Weight / volume relevant
If we check this system will calculate the weight and determine it into sales document line item.
Billing Block
If we maintain billing block here then it will be applicable to particular line item in the sales document.
Credit active
This field controls whether to update the line item value into credit management or not. If we check this then only the item value will be update in credit management.
Uncheck
AFN REN KMN KBN TAPS AGN KRN KLN KAN TAP BVN WKN G2N TAE TATX
credit active check
TAN TAS TAX TAK TAB L2N TAQ
Pricing
If the item is not relevant for pricing then maintain „Blank‟
TATX, KLN, KBN, KAN, TAE, TAP, TAPS, TAPA
If the item is relevant for pricing then maintain „X‟
AFN, AGN, TAN, BVN, REN, G2N, L2N, KRN, KEN, WKN, KMN, LPN, TAQ, TAX, TAK, TAB, TAS
If the item is relevant for 100% discount then maintain „B‟
TANN
Statistical value
If we maintain this field then the line item value will not have any effect on net value. The line item value will become inactive.
Bus Example
In BOM header pricing system will not determine pricing for components, Because TAE is not relevant for pricing. If management is asking report on component sales then we have to go to item category TAE and maintain pricing “X” and also statistical value “X” then system will determine pricing for component but it does not have any effect on total document value.
Determine cost
This field is a prerequisite to determine cost into sales document. If we check this then only cost will be determine into sales document i.e. „VPRS‟ condition type will be determined into sales document.
General Control
Automatic Batch Determination
Rounding Permitted
Depending on the rounding profile the required order quantity can be rounded in the sales order.
The rounded quantity is used in the availability check.
You can store rounding profiles in the customer-material info record or in the material master.
Order Qty =1
RBA Control
ATP check in APO System
Transaction Flow
Partner Determination procedure for item
Text Determination Procedure
In-completion Procedure
Create PO Automatically
For 3rd Party scenario to create PO automatically
Item Cat Status Group
To update in LIS , not relevant now
Bill of Material Config
Item Category TAC or TAM
TAC = Config at material level
Used in Variant Configuration
Value Contract
Value Contract Material
The system copies the material specified here to the value contract item, if a material has not already been specified by the user for that item.
Contract release control
Determination of Item Category
Item Usage
Maintained in Customer Material Info Record
General Item Cat Group
Item Category Assignment
Create Custom Item Category by copying standard
Create Custom Item Category Group
Determine Item Category
Create Document with impact analysis of below config
In completion Procedure create one for item level
Business Item Configuration - Play around
Completion Rule
Schedule line allowed
Create special stock indicator E & check impact
Billing Relevance
Billing Block
Statistical value
Determine cost
Schedule Line Category Configurations
Path
Delivery Type Configurations
Path
Delivery Type for different processes
Document category
This field controls the functioning of the delivery document.
J= Delivery Standard
System Proposes PGI
T= Return Delivery
System proposes GR
Number Range Control
Order required
This field controls whether any preceding document is required or not to create a delivery document.
LF
Sales Order Required
LO
No Preceding Document Required
Business Case
Free Sample Delivery
Return of Pallets
T code
VL01NO
STO (NL-NLR-NLCC-NCR)
Purchase Order Required
Default Order Type
Considered where Order is not available before delivery i.e. LO
Sudo order type DL is used where reference order is not available
Item Requirement
201
Additional Line items are not allowed
202
Additional Line items are allowed
Storage Location Rule
MALA
MALA rule specifies, storage location should be determined into delivery document based on shipping point + plant + storage condition.
RETA
RETA rule specifies, that storage location should be determined based on shipping point + Situation + storage condition.
Situations are used in retail environment
The situations are entered in the particular environment (allocation tables, cross-docking, logistics documents) in the internal program logic. They cannot be maintained online by the user in logistics documents.
MARE
MARE rule specifies that first check MALA rule, if MALA rule is not maintained then check RETA rule.
Config Path
Subtopic 1
Route Determination
with Check
Manual Route is check as per Route Determination Config
without Check
Manual Route is not check as per config
Delivery Split WH
Activated to split delivery dispatched from different warehouses
Used if WM is activated
Delivery Split Partners
Split if different freight forwarders are there
With this indicator if any two different partners are there system will split delivery document
Delivery Split Criteria
1. Ship to party should be same
2. Shipping point
3. Incoterms
4. Delivery date
5. Route
Assignment
Create Document
Create a Delivery without reference to sales order
Create sales order with two line items with different inco terms and delivery Date & experience Delivery split
Create New Delivery Item Category & New Delivery Type - Determine Delivery item category
Del Type - Check Impact of Req type change from 201 to 202 in delivery Document
Del item category -Remove Picking indicator and see Impact on delivery Document
Maintain storage location determination & check it in delivery document
Assignment Delivery Creation
Subtopic 1
Billing Type Configurations
Copy Control
Type
Order to Order
Order to Delivery
Delivery to Invoice
Order to Invoice
Invoice to Order
Invoice to Invoice
T Codes
[VT] is common in T-code for sales document, delivery, and invoice
A for SD, L for delivery, F for invoice (in T-code first comes target then source
VTAA - Order to Order
Header
Copying Requirements -001
1. Is the reference document complete or not.
2. Is the reference document fully referred or not.
3. Is the currency same in the source and target.
4. Check the validity period of reference customer.
5. Is customer same in reference and target document
6. Is the sales area same or not?
Transfer Header & Partner Data
Complete Reference
If we this system will not allow to select or deselect the items in source document while creating target document.
If we system will not allow to delete the items in target document
Assignment
Copy Control Quotation to sales order type - Create a Document
Create your own sales order type
Create your own quotation type
Check & Uncheck Copy Item Number at header & see Impact
Check impact of complete Ref field
Create sales order from quotation
AI
Complete and Continue