Om Day1&2
Om Day1&2
Om Day1&2
Responsibility: 06_resp1
Location Setups
06_loc1
Organization -> to create Operating Unit
Nvaigate to sys admin:
Organization id : 7941
4) Transaction Types – Create order and line level transaction types. Every
TT is governed by a Work Flow for order processing. We will begin with
the following three TTs.
a) 02_line_order_tt1
b) 02_line_return_tt2
c) 02_order_mixed_tt3. Assign tt1 and tt2 into tt3 with workflows.
Transaction
i) Header
a) Mixed (Order & Return)
b) Order
c) Return
ii) Line
a) Order
b) Return
Lines:
Headers:
Purchasing-> advanced pricing -> price list-> price list set up.-> enter price lists
After open the form verify whether pricing transaction order or not.
Save.
Click Bangalore Warehouse -> details -> click shipto -> details
Click apply.
Go to sales Order screen to see the customer
Below screen you are able to see the order number. It is coming from document
sequence.
After create Document we could able to see the line items form in sales order
screen.
For seeing the item we need to do below steps.
Notes:
Profile setup:
- System options
- Ivo
Detailed setups:
- Price list
- T.T
- W.H
- Sales person
- Payment Terms
- Profile class
- Customer
OM ACTIVITIES:
Go to sys Admin
Purchasing -> advanced purchasing -> price list -> price list setup
Define the price for item:
8) Item on a Sales order – Pre-requisites:
Item Attribute Customer order enabled must be ticked
IVO must be set to 06_imo1 under nav Setup-System Parameters-Values
Setup-System Parameters-Values
Check whether IVO is pointing to proper IMO.
Basic Pricing :
Pricing Event:
Price for all items, Item Category and Item Numbers, UOM Conversion and
Exclusive price
Modifiers
Modifier Event By Default – Unrestricted
Gets applied on all Customers
and Sales Orders.
Purchasing -> Advanced pricing -> Price List -> Price List setup
Price for Item Category :
UOM -> DZ is not defined. To resolve above issue we need to set enable Primary UOM
in price list window at line level. See the below screen shot.
Above screen shot Line 3 & 4 are having same Precedence number.
When we Compare the UOM of line 3 & 4 , It will take exclusive value(DZ) not
converted value(Ea).
PRICE BREAKERS:
Scenario:
Qty Price
Value from -> 0 – 10 - 10
10 – 20 - 8
20 - 30 - 6
Save.
If Qty between 0 to 10 then Price -> Rs.10
If Qty more than 30 then we will get error cz the item Qty is not defined.
Price Break Header – Range – Unit price
Scenario:
0 – 50K – No transaction – 0
50K – 60k – 10% -1000
60K – 1 LAC – 20% - 8000
------------
9000
-------------
Save.
Qty Price
Value from -> 0 – 10 - 10
10 – 20 - 8
20 - 30 - 6
Calculation:
Note : Absent ranges it will be 0 prices in the price list Under price break type -> Range.
15 – 10 and 5
10 -10
5 -8
---
EP- 18
--
UP = 18/15 = 1.2
0 -10 = Price :10
How to automatically default the line type in sales order line window?
Save.
Go to Sales Order Screen
Note : You are able to see the line type automatically. (Order TT)
Discount Modifies
Note: Take a item line with normal details (ex: Unit Price)
Modfier no change 1
level -> Line
Modifier Type -> discount
Automatic -> enabled
Pricing phase -> LLA
Product attri -> item number
Product attri Value -> my item 02%
Volume TYPE-> item quantity
Break type -> point
Operator -> between
UOM -> Ea
Value from : 5
Valure to : 9999
Application method – Percent
Value : 10
Save.
Note: Pricing will pick value from price list engine. But Modifier controls the value of
discount.
Modifier depends on the below three condition:
1) Customer – In modifier window we attached the customer.
2) Item – we attached the item in modifier window at product attr value.
3) Quantity - we attached the item in modifier window, depends upon value from
and value to.
Note: Folder -> save as -> public mean all OU will see our folder.
Note: After entered the order line we should press save then only we are able to see the
discount price. Cz modifier will start trigger at commit level.
Freeze Price:
Default value:
In sales order screen -> Line -> Pricing tab-> Calculate price flag -> Calculate Price
But for this one we need to change Calculate price flag -> Freeze Price
Once freeze the amt it will not apply the modifier (Any discount)
Now you are able to see the amount is not changing after giving commit also.
Coupon Issue
Scenario:
1) 1000 item2-> confirm purchase -> booked -> he will get coupon (Next sale only
coupon eligible)
2) coupon > will get 10% -> but condition, we need to purchase more than 200 then
only we can use this
3) coupon.
Open modfier
Qual context->customer
Qual context->customer
Attr -> cust name
Value from -> my cust name.
Ok.
Modfier no change -> 02_coup_dis
level -> Line
Modifier Type -> discount
Automatic -> enabled
Pricing phase -> LLA
Product attri -> item number
Product attri Value -> my item 02%
Volume quan-> item AMOUNT
Break type -> point
Operator -> between
UOM -> Ea
Value from : 200
Valure to : 99999
Application method – Percent
Value : 10
Open Sales Orders -> Line items -> Book Order -> then only it will provide coupon ->
continue. In header status is Booked.
Actions -> view Adjustments -> Ensure coupon issued or not.
Encashing :
Action -> promotion/ Pricing Attributes.
Coupons tab -> C+L -> ensure our coupons is not coming.
In Modifiers form -> click the discount modifier -> Line qualifiers -> ensure population
of coupons.
End date is null-> when you encash the amount end date will come
Line items -> Less than 200 accept the order but coupon not valid.
Item Upgrade
Click new
Generic relarionship is is two items related to from items and type.
From item -> 02_100ml
To_item -> 02_150ml
Type-> promotional type.
MODIFIER name-> 1
level -> line
Modifier Type -> item upgrade
Automatic -> enabled
Pricing phase -> LLA
Product attri -> item number
Product attri Value -> 100 ml item
Volume quan-> item quantity
Break type -> point
Operator -> between
UOM -> Ea
Value from : 3
Valure to : 99999
2 100 ml + 3 150 ml shampoos and if u ask for Keyboard u will get 75%
discount.
Goto Modifiers.
MODIFIER name-> 2
level -> line
Modifier Type -> other item desc
Automatic -> enabled
Pricing phase -> ALA
Product attri -> item number
Product attri Value -> 100 ml item
Volume quan-> item quantity
Break type -> point
Operator -> between
UOM -> Ea
Value from : 2
Valure to : 99999
Get
Sales Order
Line
100 ml (2) +150 ml (3) + Keyboard (1) -> will get 75% discount for keyboard.
Don’t for got to end date the modifier number 2.
Scenario:
If you buy 3 100ml shampoo, you will get 2 150 ml shampoo free.
MODIFIER name-> 3
level -> line
Modifier Type -> Promotional goods
Automatic -> enabled
Pricing phase -> ALA
Product attri -> item number
Product attri Value -> 100 ml item
Volume quan-> item quantity
Break type -> point
Operator -> between
UOM -> Ea
Value from : 3
Valure to : 99999
Get
Chek for Break type -> Recurring. -> It is used to bring every 3 shampoo you will get
free 1 150 shampoo. Ex: 10 100 ml shampoo 3 150 shmpoo.
Buy one Get one free:
MODIFIER name-> 3
level -> line
Modifier Type -> Promotional
Automatic -> enabled
Pricing phase -> ALA
Product attri -> item number
Product attri Value -> 100 ml item
Volume quan-> item quantity
Break type -> point
Operator -> between
UOM -> Ea
Value from : 2
Valure to : 99999
Get
Deactivate modifier.
Modifier
Line Level:
MODIFIER name-> 1
level -> line
Modifier Type -> Frieght/special
Automatic -> enabled
Pricing phase -> ALA
Product attri -> item number
Product attri Value -> 100 ml item
Volume quan-> item quantity
Break type -> point
Operator -> between
UOM -> Ea
Value from : 0
Valure to : 2
Click Discounts/charges :
Line Level:
Give >2 then you could able to see the Charges in Order Level.
Order Level:
MODIFIER name-> 1
level -> Order
Modifier Type -> Frieght/special
Automatic -> enabled
Pricing phase -> ALA
Discount charges:
Charge_name -> Transaportation charges
Application_method -> Lumpsum
Value -> 2.34
Defaulting Rules
Scenario:
Validation Groups:
Precedence
20 Always
21 02_cust1
Sequence
Defaulting Rules
Precedence
Sequence
10 System variable
Default _valus -> sysdate + 2
Tool -> Generate…
Scenario:
Try to Update the price list after order booked status.
C+F11
Entity->Order Header
Update -> Cust _po not allowed and applies -> fulfillment
Condition
Scenario:
After booked status if you change the request you are able to see the version.
101
Sope-> Any
Validation -> Order Line
Record set -> Line
Validation Template -> Booked
Sales order
Change the request_date and that time it will show version and ask the reason
Actions-> Version history and -> compare
Scheduling/Reservation
Scheduling:
Scheduling Engine
Book Event Scheduling ( ATP Not Applicable)
Event
Scheduled Scheduled
Ship Date Arrival Date
SSD = RD
SAD = SSD + ( ILTT) Inter Location
Transit Times between Our Ware House
and Customer’s location
Booked.
Reservation:
Inventory -> Tansactions -> Miscellenous -> Transactions
Open Periods
Create Subinventory:
Subinventeries
Query tt3.
Sales Order
Create line for reservation and line type.
lined Qty and Qty reserved.