Storage Location Determination

Referreing to the Question asked by Deepak
Mat 'ABC' is stored in plant 'PLA' in two different storage locations 'STR1' and 'STR2'. On creating a SO which storage location, will it pick and why??

Hi Deepak,
Let me explain you first how the storage location is determined

Storage location is determined at the delivery document by storage location rules viz MALA, RETA or MARE
The most commonly used one is MALA.
One rule is defined against a Delivery type (ref: check in TC : 0VLK - Delivery type LF)
MALA is determined as below:
STORAGE LOCATION = SHIPPING POINT + PLANT + STORAGE CONDITION
RETA = PLANT + SITUATION + STORAGE CONDITION
MARE = MALA then RETA (First MALA will be applicable failing to find this rule, system will trace for RETA)
Check which rule is applied to the delivery type.
So if MALA is used for storage location determination then based on the parameters defined for shipping point, plant and storage condition system will pick the storage location.
We set Storage location determination under Shipping -->Picking-->Determine Picking Location-->Assign Picking Locations
But COPY CONTROL also plays its role in copying the storage location in the delivery document if it is created w.r.t. the SO. (Ref: TC: VTLA under Item data one routine is defined viz. “101”)
Please have look at the below portion of “Routine 101”
IF CVBAP-LGORT NE SPACE. (LGORT = Storage location)
LIPS-LGORT = CVBAP-LGORT.
ENDIF
IF NOT CVBAP-CHARG IS INITIAL.
LIPS-CHARG = CVBAP-CHARG.
ENDIF.
Coming back to your question, above portion of SAP standard routine 101, explains us if in a SO, storage location is blank, storage location will be picked determining the rule e.g. MALA, and if SO has a value for storage location then LIPS-LGORT = CVBAP-LGORT. (LIPS is delivery at item level and VBAP is SO at item level)
* SO = Sales Order

Routine "2" : Requiremnt colum in Pricing Procedure

Hey Deepak...Here's your answer

Requirement: Denoted by numbers and maintained in VOFM, this is a condition required for a particular condition type.
E.g. PR00: req. 2 i.e. item relevant for pricing or not.
* Pricing is turned on in item category configuration

FORM KOBED_002.
SY-SUBRC = 4.
IF KOMP-KPOSN NE 0 (KOMP- Pricing Communication Item KPOSN -Condition item no. in SO)
CHECK: KOMP-PRSFD CA 'BX'. (PRSFD - PRSFD Carry out pricing)
CHECK: KOMP-KZNEP = SPACE. (KZNEP -Condition exclusion indicator)
ENDIF
SY-SUBRC = 0.
ENDFORM.
* Prestep
FORM KOBEV_002.
SY-SUBRC = 0.
ENDFORM.
For techi’s above program is self explanatory
Explanation:
The above routine “2” is included under Req column in Pricing Procedure. It means that system would first check whether the item category attached for an item in that condition item number in SO is relevant for pricing or not.
If the Item category is pricing relevant only then system will go to VK11 and fetch the price. On the contrary if req. column does not contain 2 as routine against a condition type system will not consider this parameter and would directly jump to VK11.
This routine improves system performance
Note: If an item category marked as NOT relevant for pricing system will not fetch price in the Sales order even if the condition records for the condition types are maintained.

Please let me know in the form of comments should you have any query.

Support Environment

Following are the four major things in support environment, issues fall in the form of tickets.

• Taking Ownership of the call coming in the form of ticket
• Resolving a call
• How to reassign a logged call to the next support level
• Interaction with the next Level support.

Please post your questions here

Hi Guyz n gals,

Pl post your questions in SAP SD in the form of comments under this subtitle and I'll get back with an answer as a different post asap.

Faraz

Master Data and Transaction Data

whats the difference between Master Data and Transaction Data