Frieght in consigment process

Hi;
In consingment process, i have maintain price and frieght in consigment inforecord. While transfering the stock from consigment to own,(mvt. type 411K) system is considering(inventorising) frieght part in the accounting accounting doc..
Regards
Manish

Hi,
To settle the delivery costs in consigment you ahve to run MRDC transaction periodically.
regards,
Bharat.

Similar Messages

Consigment process with excise processing

Hello,
I would like to know the complet vendor consigment process with Excise Processing.
Thanks
Manish

Hi,
      Process:
                        Before you can order a material from a vendor or post a goods receipt to consignment stock, you must maintain the consignment price for the vendor in an info record. The price is required for material valuation and accounting purposes.
If you order consignment material from several vendors, the system maintains the consignment stock separately for each vendor, since the individual quantities of the material can have different prices with each vendor.
                     You can order goods from external vendors as vendor consignment goods. You carry the goods in the vendor consignment stock in your site and therefore they remain the property of the external vendor (special stock manager) and do not belong to your valuated stock.also they are not considered for your MRP planning.
This contains the following main functions:
·        You can order goods from an external vendor as consignment goods by setting the Consignment item category manually in the purchase order.
·        You can transfer goods in the consignment stock of your site to other sites. To do this, you post goods manually from the consignment stock to your own stock. This creates a legally binding contract with the external vendor.
           Settlement of the withdrawal is done regularly at an agreed time for eg. quarterly,half yearly...
Activities in Materials Management:
Activity:                     Display Consignment Stocks/ Settle Consignment/Pipeline Liabilities
Transaction Code:       MB54 /    MRKO    Respectively...
Hope it helps you clear the basics of consignment...

Vendor consigment process combined goods issue to cusotmer

Hi, All,
I have some questions on the consignment process.
One Scenario: For the MM consgiment without delivery to customer. I listed some steps with my questions below:
1. Create Consigment info record. Is it necessary?
2. Create consignment purchase order Item category K. Is there any special setting?
3. Goods receipt against PO. What's the movement type here? What's the movement type 201 K and 231 K used for? If 101, is it goods receipt to own stock?
4. No invoice verification done, but settlement is done through MRKO transaction. Is it paid consigment fees to vendor by this t-code? What's the accounting happened?
Two Scenario: For the MM consgiment with delivery to customer. I listed some steps with my questions below:
1. Create Consigment info record. Is it necessary?
2. Create consignment purchase order Item category K. Is there any special setting?
3. Goods receipt against PO. Placed in own inventory with a stock category of K. What's the movement type here? what means stock category K?
4. Create normal sales order.
5. Must remove the K from the inventory before a batch can be selected on the delivery-
a. MB1B- 301 transaction is used to removed the K and to reference the delivery number
b. Depending on if location is inventory managed an LU04 may be necessary to complete the movement off of K .
Why movement type 301 is here?
5. Create delivery and PGI (The quantity is different when you do goods receipt for this material)
6. Invoice to customer
7. Payment for that Purchase Order thrgouth MRKO. The issue is only paid to vendor based on the quantity which sent to customer, not on goods receipt. How it can be achieved?
Three Scenario: Is there any process create MM consgiment with delivery directly to customer? What's the process, movement type and what's the difference?
Thank you very much in advance

Hi,
1. Create Consigment info record. Is it necessary?
           Yes, for consignment process, inofrecord is must, price will be picked only from inforecord, you can't enter price in PO.
2. Create consignment purchase order Item category K. Is there any special setting?
           Item category K is standard for consignment PO.
3. Goods receipt against PO. What's the movement type here? What's the movement type 201 K and 231 K used for? If 101, is it goods receipt to own stock?
Movement type is 101, 201k & 231k is for goods issue.
Its not good's receipt ot own stock, its goods receipt to unrestricted stock with stock indicator as K, later you can take to your own stock through 411k.
4. No invoice verification done, but settlement is done through MRKO transaction. Is it paid consigment fees to vendor by this t-code? What's the accounting happened?
For example If you manage material A of vendor X as consignment stock at a price of $ 10 /piece.
When 100 pieces are withdrawn for consumption, the system makes the following
postings when the withdrawal is settled:
During Withdrawal
Consumption account                               1000 +
Liabilities from consignment stores            1000 -
During Settlement
Liabilities from consignment stores   1000 +
Vendor account                                1000 -
For your scenario 2, follow the same steps as mentioned above and do the goods issue directly from consignment stock.
You can do the settlement to vendor only for the stocks that you consumed.
Regards,
Prabu
Edited by: prabu krishnasamy on Apr 25, 2009 12:13 PM
Edited by: prabu krishnasamy on Apr 25, 2009 12:14 PM

Vendor consigment process

Hi,
I want to know the detail step of customizing and also how to process a consigment PO and how to clear the vendor payment, and initially as in consignment we are giving payment after consuming of material then how to make GR if vendor is under excise register.
regards,
zafar

Hi,
Consignment Stock means your Vendor stores there material in your company premises.When ever you want you can use it as per your requirement. Unless you consumed, It is regarded as non -valuated stock. PO can be created with item category K( ME21N)
The steps are:
1. Consigment info record(ME11),
2.Souce List(ME01)
3.PO with item category K( ME21N)
4.GR WRT to PO (stock will be shown as material provided by Vendor)
5.Consuption Posting (Creates Invoice automatically)
6.Invoice Verification in MRKO.
7.Payment to vendor(F-53)
The account entries in GR,GI and IR are as follow;
A.Goods Receipt:
No Accounting Documents
B.Goods Issues:
Consumption A/C: DR,
Consignment(Liability Account ) Payable: CR,
C.Consignment Settlement:
Consignment (Liability Account )Payable: DR,
Vendor Account A/C: CR
For more check the link:
http://help.sap.com/saphelp_erp2005/helpdata/en/4d/2b8ec943ad11d189410000e829fbbd/frameset.htm
Regards,
Biju K

Movement Types in Consignment Processing ?

Hello SAPains,
What are the movement types used in Consigment Processing ?
ie - CF, CI, CP & CONR .
Please write back, Points will be awarded.
Thank you.

hi,
In consignment orders you are allowing the stock to sit in your customer location. Once he informs that he used the stock you will invoice him. If he returns the stock you will accept the stock to take it back.
It is defined in 4 steps.
1. Consignment fill up:
Sales document type is KB
Item category KBN
shedule line category E1
In this step, you are not invoicing the customer. document flow is sales order -
delivery item category. It will not be relevent for billing and pricing because you are not charging money for these goods in this step.
In schedule line category, you will set movement type 631 & set for availability check and TOR.
2. Consignment Issue.
Once the customer informed you that he used all the goods or partial goods then you will create consignment issue for used goods.
Sales document: KE
Item category: KEN
shedule line category: C0 or C1
Here you are invoicing the customer(because he used the goods). you are assigning the delivery documnt and billing document to the sales document.
In item category, you are setting relevent for billing, pricing, special stock.
In schedule line category, your setting is 633 movement type, relevent for availability check & TOR.
3. Consignment Return:
Customer found that some goods are damaged or he not able to sold the goods he want to send it back. that you are creating this document.
Sales document type: KR
Item category: KRN
Shedule line category: D0
You will assign delivery document and billing to sales document. you will create return order, return delivery, return billing.
Your setting item category relevent for billing, returns, pricing, special stock.
Your setting schedule line item category: 634 movement type, NO availability NO TOR.
4. Consignment Pick up:
Even if you create the consignment return the goods are not come to direct to your plant. For that you need to create consignment pick up. here the owner ship is not changing so you do not need to create billing.
Assign retrun delivery to sales document type.
Sales document: KA
Item category: KAN
schedule line category: F0 & F1
Your setting item category relevent for returns. any shedule line category relevent for 632 movement type, MRP, availability check, delivery
Regards,
Murali

Help me on tthese issues

Hai Friends,
<b>1)
Kindly help me toughest tickets in SD with clear explanation....
i lost many interviews because of this ....
2)
kindly through customization on pricing
3)
what is significance of account assignment grp in SD?
4)can we have credit mangement only at order level or only at delivery level?
5)toughest GAP analysis u faced in implementaion
6) generally how many types of pricing scenarios will be there in normal implamentaion?
Mail me at [email protected]
</b>
i reward suitably***
Thanks a lot in Advance
Venkat

Hi Venkat,
PRICING SD:
PRICING:
Pricing is the combination of creating correct pricing procedure that map the business needs & processes, such as correct pricing & discounting, & keeping to the legal requirements placed on the business, such as adhering to the tax laws of the country.
SPRO- IMG- SD- Basic Functions- Pricing- Pricing Control
Create Condition Table: V/03, V/04, V/05
Define Access Sequence: V/07
Define Condition Types: V/06
Define & Assign Pricing Procedure
Maintain Pricing Procedure: V/08
Define CuPP: OVKP
Define DoPP: OVKI. The DoPP indicator is used to determine pricing in conjunction with the sales area & CuPP.
Assign DoPP to Order Types & Billing Types: OVKJ & OVTP
Define Pricing Procedure Determination: OVKK
Create Condition Table: V/03, 04, 05
Put the most general field for e.g., Sales Orgn in the highest position & the most specific field in the lowest. After organizational fields, place fields from doc header before those that come from item level (customer comes before material).
Sales Orgn, Distbn Channel, Div, Cust, Mat: Customer Specific Price
Sales Orgn, Distbn Channel, Div, Price List Type, Mat: Price List
Sales Orgn, Distbn Channel, Div, Mat: Material Price.
Maintain Access Sequence: V/07
Go to new entries, define 4-digit acc seq. Select acc seq, go to Accesses and place the cond tables and check exclusive indicator (which determines that if a cond record is successfully found, the system will stop searching further). Select each cond table and go to Fields.
There are some cond types for which you do not create cond records (header discounts that you can only enter manually). These cond types do not require an access sequence.
Define Condition Type: V/06
They are used in the pricing procedure to define how the cond is going to perform, such as either a %tage or a fixed amount. The cond type can be automatic or it can allow manual changes. Copy the required cond type and rename. Then assign acc seq to cond type.
If you use different calculation types for what are otherwise the same conditions (for e.g., %tage, as fixed amt, qty dependent), you do not have to define different cond types in customizing. You can set different calculation type when maintaining cond records.
Functionality of Condition Types:
Access Sequence
Condition Class: surcharge & discounts or prices
Plus/Minus: -ve, +ve or both
Calculation Type: fixed amt, %tage, qty, wt, voln
Rounding rule: commercial, round up and round down
Group Cond
Manual Entry: whether manual or automatic entry has priority
Header Cond: after entering the header cond type click on the button activate. The cond amt of the header conditon is copied as it is to all the line items in the doc.
Item Cond
Amount/ Percent: check & u can change the amount or % for the cond type during data processing
Delete: check & the cond record may be deleted from the doc.
Value: check & the value of the cond type can be changed during data processing
Calculation Type: check & the cal type can be changed during doc processing
Valid from & to
Scale Basis: determines how the system interprets a pricing scale in a cond, for e.g., the scale can be based on qty, wt, voln
Check Value: indicates whether the scale rates must be entered in ascending or descending order.
Define and Assign Pricing Procedure: V/08
A pricing proc consists of a lists of cond types in a defined order, such as price less discount plus tax. Go to new entries, define 6-digit pricing proc with descp. Select the 6-digit pricing proc and go to Control Data, you will be faced with an empty structure.
Step: the no that determines the sequence no of a cond type with in a procedure
Counter: second mini step with in an actual step
Conditon type: specify the cond type
From & To: if you specify the ref steps in these fields, the cond values of the 2 steps specified and steps in between are totaled
Manual:
Mandatory: whether a cond type is mandatory when system carries out pricing
Statistical: the value represented in this step will not alter the overall value
Print: which cond types should be printed on a doc (order confirmation, invoices)
Subtotal: controls whether & in which fields the cond amts or subtotals are stored
Requirement: for a cond type to be executed in the sales doc the requirement specified here must be satisfied. (It is a gateway)
Alternative Calculation Type: alternative formula to the formula in the std system that determines the cond. In the std SAP system for the cust expected price EDI1, the alt cal type is 9, which means it contains a routine with a logic which states that the difference between the customer expected price & the net value is zero.
Alternative Cond Base Value: alternative formula for determining the cond basis (amt to which the discount or surcharge in a scale refers)
Account Key: this field enables the system to post the sales value to different G/L accounts. ERL: sales revenues, ERS: sales deductions, ERF: freight revenue.
Accruals: this is exclusively for rebate cond types BO01 & BO02. Key, which identifies various types of G/L accounts for accrual postings.
TAX: MWST
Tax is calculated on the following parameters:
Plant
Ship to party region
Customer tax classification
Material tax classification
Pricing Procedure Determination: OVKK: Determination Rule
Before one can proceed with the determination rule, one needs to maintain the CuPP & DoPP. One needs to assign a single character alphanumeric key with a short descp. Then assign the DoPP to the sales doc types. This will ensure that for e.g., all sales orders created using order type OR, which has been assigned a DoPP of 1, will all use the same pricing proc if created in the same sales area & with the same CuPP. In some instances, you may not want to have the same pricing proc for a sales doc, as you may want in a billing doc. For this reason, you may allocate a different DoPP to a billing doc.
Do not forget to assign the CuPP indicator to your CMD in the Sales Screen
Sales Orgn + Distbn + Division + CuPP indicator + DoPP indicator = Pricing Procedure
To Create own Sales Doc Types:
SPRO- IMG- Sales Doc- Sales Doc Header-
Define sales doc types: VOV8. Copy std order type& rename
Assign Sales area to Sales Doc Types:
Combine sales orgn
Combine Distbn channel
Combine division
Assign sales order types to permitted sales area
To create Price List Types:
SPRO- IMG- SD- Basic Functions- Pricing- Maintain Price Relevant Master Data:
Define price list category for customers: OVSI: assign to CMD sales area screen in price list type field, in sales tab page in pricing and statistics section.
Define pricing group for customers: OVSL: assign to CMD sales area screen in price group field, in sales tab page in pricing and statistics section.
Define material group: OVSJ: assign to sales orgn 2 view of MMR in Mat Pricing Group Field.
2 digits character key with description
Cond Type Description Cond Class Calculation Type
BO01 Group rebate Exp reimbursement Percentage
BO02 Mat rebate Exp reimbursement Qty (fixed)
BO03 Cust rebate Exp reimbursement Percentage
BO04 Hierarchy rebate Exp reimbursement Percentage
BO05 Hierarchy rebate / Mat Exp reimbursement Percentage
BO06 Sales Independent Rebate Exp reimbursement Fixed amount
EDI1 Cust Expected Price Prices Quantity
HB00 Discount (value) Discount / Surcharge Fixed amount
HD00 Freight Discount / Surcharge Gross weight
K004 Material Discount / Surcharge Qty / absolute
K005 Customer / Material Discount / Surcharge Qty / absolute
K007 Customer discount Discount / Surcharge Percentage
K020 Price group Discount / Surcharge Percentage
K029 Material Pricing Group Discount / Surcharge Absolute discount by wt
K030 Customer/ Mat Group Discount / Surcharge Percentage
K031 Price Grp/ Mat Pr Group Discount / Surcharge Percentage
K032 Price Grp/ Material Discount / Surcharge Quantity / absolute
KF00 Freight Discount / Surcharge Gross weight
NRAB Free Goods Discount / Surcharge Quantity
PI01 Inter company price Prices Quantity (fixed)
PI02 Inter company % Prices Percentage
RB00 Discount / value Discount / Surcharge Fixed amount
PR00 Price Prices Quantity
VPRS Cost Prices Quantity
RL00 Factoring Discount Discount / Surcharge Percentage
MW15 Factoring Discount Tax Taxes Percentage
SKT0 Cash discount
Customer Specific Price: sales orgn, distbn, division, customer & material
Price List Price: sales orgn, distbn, division, price list type & material
Material Price: sales orgn, distbn, division & material
Customer discount: sales orgn, distbn, division & customer
Customer material discount: sales orgn, distbn, division, customer & material or sales orgn, distbn, customer & material.
Material discount: sales orgn, distbn, division & material or sales orgn, distbn & mat.
Condition Records:
Condition records allow you to store & retrieve pricing data in the system. Pricing elements are generally managed at the sales orgn & distbn channel level. There fore you always have to specify organizational level when creating cond records. In the case of cond records for price groups, freight charges, & cust specific prices & discounts you must also enter the division. As a result, you can create conditions according to product groups with these price elements.
Pricing Elements in Sales Order:
Price: the basis of pricing during sales order processing is the gross price of the mat. The system selects the most specific record- the cust specific price. If it does not exist, the system looks for price list type. If it also does not exist then system takes the basic material price. You can define price list types by customer groups (wholesale or retail) or by currency (price lists for each foreign country dealt with)
Surcharge & Discounts:
Freight Costs: you can create cond record either based on: the first part of the inco term (for e.g. FOB) or on the combination of part 1 & 2 (for e.g. FOB & Boston). There are 2 predefined freight conditions
o KF00: applies to each item in a sales doc.
o HD00: applies to entire document.
Sales Taxes:
Prerequisites for Automatic Pricing:
Necessary data must be maintained in MMR & CMD:
Material Master Data: the price related fields can be found in sales orgn 1 & 2.
Tax Classification
Price Material: you can specify another material as ref for pricing info
Material Group: defines a group of materials for which you want to apply the same cond record.
Cash Discount: whether or not mat qualifies for cash discount
Customer Master Data: the price related fields appear on sales data screen.
CuPP: specify the pricing proc for a customer
Price List: Allow you to apply a mat price in a particular currency to a group of customers e.g. wholesale customers.
Price Group: price group lets you apply a discount to a particular group of customers.
Tax Classification: billing tab page.
HEADER & ITEM CONDITIONS:
The standard system includes cond types that you can apply at only the header level, the header conditions. Cond types that you can only use for items are called item conditions. There are some cond types that can be used at both header & item level:
RA01: percent from gross
RB00: absolute discount
RD00: weight discount
Header Conditions: you cannot create cond records for it; it is entered manually in order processing. Automatic pricing does not take place for them.
HA00: percent discount
HB00: absolute discount
HD00: freight
HM00: order value
Item Conditions: in the std SAP most cond types are defined as item conditions:
K004: mat discount
K005: cust/ mat discount
K007: cust discount
PR01: mat price
KF00: freight
Distribution between Header & Item:
Header conditions apply to all items in the doc & are automatically distributed to all the items. It can be either percentage or an absolute amount.
If you enter a header cond that is based on a percentage (e.g., a dis of 2% ) the system automatically applies this percentage to all the items in the doc.
If the header cond is an absolute amount, there are 2 ways in which the system can distribute the amount among the items in the doc:
Distributed proportionally among the items
Amount entered at header level is duplicated for each item.
You control the distribution of absolute header condition in the Group Price Field per cond type.
HB00: header discount distributed as percentage because it is marked as a header cond & group condition. The system distributes the amt proportionally among the various items, in this case according to the value of the items. The distribution of an absolute header cond need not be based on value. For e.g. you can specify in customizing for sales that the distribution is based on weight & volume of the different items. You can specify the basis of distribution in the Alternative Cond Base Value field in the pricing screen.
RB00: assigns the header discount to each item identically, because it is only marked as header condition.
Pricing Procedure:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
Condition Table:
Condition records are always created using a specific key.
Use tables for help in defining the structure of condition record keys.
The most important fields used in pricing at header and item level are available in the standard system.
 The key fields of a condition table must appear at the start of the table, in other words, non-key fields must not appear between any two key fields.
Condition table: The definition of the key of the condition record.
Access Sequence:
The access sequence determines the sequence in which the condition records for a condition type are found and read.
 An access sequence (search strategy) is defined for each condition type (with the exception of header and manual only condition types) in the pricing procedure.
This search strategy defines the sequence in which the system reads the condition records for a condition type.
Each access performed during the access sequence is made using a condition table.
A condition table is a combination of fields, which form the key for a condition record.
You can make an access dependent on certain requirements.
You can define prices, discounts, and surcharges at various levels.
Each level is defined by a combination of fields or by a field in a condition table.
Using the access sequence, you can define the sequence of the different levels.
The system attempts to determine the condition records in the sequence specified.
 Within each access of an access sequence, you can specify the specific document field (source field) with which an access is carried out.
Examples:
> Material or pricing material?
> Document currency or local currency?
> Sold-to party or ship-to party?
Make accesses dependent on requirements to avoid unnecessary accesses. This reduces the system load.
Access sequence: A search strategy to locate the proper condition record.
Condition Types:
The condition type determines the category of a condition and how it is used.
The calculation type and the scale base type can be controlled for each condition type.
For Example: Scale for Condition Type PROO
1 pieces 800 uni
10 pieces 750 uni
100 pieces 700 uni
Possible scale base types Possible calculation types
Value Percentage from an initial value Fixed amount
Quantity Amount per unit of measure
Weight Amount per unit of weight
Volumes Amount per unit of volume
Time period Quantity per unit of time
Each condition type can be set as an automatic surcharge, discount or either.
Condition Type in Pricing Procedure can be set as Manual, Mandatory or Statistical, as per requirement.
Condition types: A calculation or formula used for a component of pricing.
A condition type is a representation in the system of some aspect of your daily pricing activities. For example, you can define a different condition type for each kind of price, discount or surcharge that occurs in your business transactions.
Example of a Condition Type price pr00, discountk007,frieght kf00
A condition table defines the combination of fields (the key) that identifies an individual condition record. A condition record is how the system stores the specific condition data that you enter in the system as condition records. For example, when you enter the price for a product or a special discount for a good customer, you create individual condition records.
An access sequence is a search strategy that the system uses to find valid data for a particular condition type. It determines the sequence in which the system searches for data. The access sequence consists of one or more accesses. The sequence of the accesses establishes which condition records have priority over others. The accesses tell the system where to look first, second, and so on, until it finds a valid condition record. You specify an access sequence for each condition type for which you create condition records.
The primary job of a pricing procedure is to define a group of condition types in a particular sequence. The pricing procedure also determines:
Which sub-totals appear during pricing
To what extent pricing can be processed manually
Which method the system uses to calculate percentage discounts and surcharges
Which requirements for a particular condition type must be fulfilled before the system takes the condition into account
pricing procedure dirctly link to fi through the acount keys link to gl accounts
Pricing Procedure:
Pricing procedure: A sequential list of condition types and subtotals.
All condition types permitted in pricing are contained in the pricing procedure.
You determine how the system is to use conditions by specifying requirements for each condition.
The sequence in which the system accesses conditions in the business document is also determined here.
 The reference level provides a method to specify a different basis for the condition type calculation and for grouping conditions for subtotals.
The pricing procedure can contain any number of subtotals between gross and net price.
You can mark a condition type in the pricing procedure as being:
--> a mandatory condition
--> a manually entered condition
--> for statistical purposes only
Pricing Procedure Determination & Overview:
In this example, an order for 120 pieces of a material is created. The system must determine the price automatically.
First, the relevant pricing procedure is determined based on the sales area, customer, and sales document type.
The system reads the condition type of the first step. It determines the assigned access sequence for this condition type.
 The system reads the access sequence. The sequence of condition tables represents the search strategy for finding the relevant condition record.
Each condition table represents one access which can be made for a condition record with the specified key.
The system searches for valid condition records with the key specified by the condition table (accesses).
 If the first access does not find a valid condition record, then the system searches for the next access using the next condition table.
 Once the system finds a valid condition record for an access, it reads the condition record and copies the value that corresponds to the scale into the sales document.
The whole process is repeated for each condition type until the system has finished the entire pricing procedure.
Pricing Configuration:
The condition table contains the keys that can be used for creating dependent condition records.
You can add your own condition tables using table numbers 501 through 999.
An access sequence is composed of one or more condition tables.
After creating the access sequence, it is assigned to a condition type.
 You can also create your own condition types. You determine the characteristics of each condition type, for example, whether it is for surcharges or discounts and whether it should be dependent on values or quantities.
The condition types are combined in the required sequence in the pricing procedure.
Finally, you need to maintain the procedure determination table for the pricing program.
The pricing procedure is determined according to:
>> Sales area
>> Customer pricing procedure field in the customer master
>> Document pricing procedure field in the sales document type.
Account Assignment Group in SD:
I Plays a vitol Role in SD --> Customer Master Record --> Sales General Data
Billing Tab.
Account assignment group for this customer
The account assignment group to which the system automatically posts the sales document.
Use
The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.
Procedure
The system automatically proposes the account assignment group from the customer master record of the payer. You can change the default value in the sales document or the billing document.
It also Plays a vitol Role in Material Master --> Sales Organisation Data 2 View.
Account assignment group for this material
Group of materials with the same accounting requirements.
Use
Used by the system when creating an accounting document from a billing document to determine the revenue or sales deduction account.
We can Set Credit Managment at Either Sales Order Level or Delivery Level.
GAP ANALYSIS
Gap means small cracks. In SAP world or in Information Technology world, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be."
Gap Analysis is undertaken as a means of bridging that space. Actual Gap Analysis is time consuming and it plays vital role in Business Blueprint [AS IS Process] stage.
A through Gap Analysis will identify the gaps between how the business operates and its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and auctioned,
1. GAP must be closed and customized software can be developed
2. GAP must be closed but software cannot be written therefore a workaround is required
3. GAP does not need to be closed.
A point worth mentioning here is that at time people confuse between user-exits and Gap Analysis. User exits are standard gate ways provided by SAP to exit the standard code and we can write our own code with the help of ABAP workbench, its not new functionality which we are trying to build in sap but its slight enhancement within the same code.
Gap analysis is start point of Realization and once business Blueprint is finished we have to find the realization of sap system for client requirement and there will be certain gaps when compared to system fit. Those gaps can be closed either by re-engineering of business process to fit with SAP or we have to use USER exits in case of small deviations or complete enhancements with the help of ABAP to fit with the SAP system.
The Gaps can differ from company to company. Most commonly, however, missing functionality is industry-specific.
Examples:
1. MGM Studios and Lycos sometime back worked with SAP to develop its new intellectual property management and media advertising management functionality, respectively.
2. A leading Oral care product company wanted the promotion of free-goods where they wanted 'Buy one get 2 different products free'.
A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can and can't do. For each gap there will be one of three outcomes which must be recorded and actioned.GAPs must be closed and therefore customized software can be developed to close the gap. In some cases GAP must be closed but software cannot be written therefore a workaround is required in other words a business process change is recommended to the client.
In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications (ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
Actual gap analysis is time consuming and it plays vital role in blue print stage.
Pricing Scenarios :
There are Client Specific:
Ex:- If the Client is Dealing with Domestic and Exports we have to Maintain the Both and having the Consigment Process we have to do the Consignment Pricing etc.,
Hope this Clairfies your Doubts and Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Intercompany STO Consignment Return

Hi gurus,
I am giving support to a company with Intercompany consigment process. The process works but I am meeting a problem with the return process . If a click on the flag return item, the shipping tab of the position dissppears so I cannot create the delivery. Please if anyone knows let me know!!
Some details:
Order type NB,
Stock type K
I have customized the:
delivery determination
returns from plant to plant
All master data is correct cause the process is working (only the return are not working)
Thanks in advance!
Mikel

I have never heart of an Intercompany STO Consignment process.
However, you usually create a consignment fillup to get the material to your customer (still owned by you)
when the customer uses this material, you create a consignment issue.
if any unused material shall be returned, then this is not a return, it is called consignment pickup, this process starts as well in SD.
A consignment return would only ocur after a goods issue was done, a return will then return the material into consignment stock at customer location.
About which return are you talking? the pickup or the real return?

Automatic Part 1 and excise capturing while trans. stock from cong.to Own

Hello;
While transfering the consigment stock to Own (Movement tye :411K) , i would like to update part 1 and capture excise invoice, but excise tab dosent appear in MIGO(Transfer posting).
Can any body help me how to automate this excise activity in consigement process
Rgerads
Manish

Hi;
I wanted to know the excise process(Part 1&2 ) in case of consigement process
Rgerads
Manish

Roles in Project preparation phase ?

hii
Some body explain me on their real time exeperiance of 1st phase implementation.??
What will be the major roles and reponsibilities of MM consultant in 1st and second phase ???
How we should do the AS-IS study in client place ????
Some body explain me in depth and detailed of their own experiance in implementation project.
And additionally ,as MM consultant where we shlould not be lack of knowledge for any implementationss??
Thanks

In project preparation phase, all the details of the projects are set, who will be the project manager from implementors side and from client side, then the whole team is selected of both sides, some times there are interviews of consultants as well from the client, where client desides which consultants they want for there implementation.
Then usually sign up of the project is done and sometimes presentation on every module is given as well if sign up and project start has big difference in dates.
Then in blueprint phase, for AS-IS, you MM consultant and powerusers from client sit down and you jott down all the current settings of the client, here its decides and researched how there current system is configured, and what necessary settings are required for SAP i.e. how many plants, how many purchase organisations,groups, how many material groups, what number ranges master record will follow, how many document types for PR,PO,contract, which additional processes are required i.e. Framework order, source lists, which type of mrp, subcontract, consigment process etc.
Once you get all the data in AS-IS, you create blueprint based on this information which will contain every info, i.e. how many plants will be created, what numbers, how many storage locations with names and numbers for each plant, how many purchase organisation with details, purchase groups, document types of prs, pos, with number ranges, release strategy, and total process flow in this documentation and what can and what cant be configured in SAP, thus the TO BE stage. Here client views your document and if there are any reservations they are pointed out, if any deletion addition is needed to the document they are notified to the consultants, necessary changes are made to the blueprint and this up/down in changes keeps on going, until the blueprint is signed.
Same above described process happens for all other modules as well, and once all module blueprints are signed, then begins the realization phase. Usually the blueprint phase in 6 months implementation last for 2 months.
Edited by: Afshad Irani on Aug 30, 2010 3:55 PM

Timing of Confirmation from Consignee to Company during Consignment Issue

Hi, The consignment process is something where the company keeps his stocks at consignee place with full ownership (consignment fill-up). When the consignee sells the stock then the consignee informs the company and company invoices the consignee (consignment issue). Now my question is what happens if the consignee sells the item and informs the company (owner) after sometime ? e.g. if consignee sells an items and informs the company after say 1 year, then by this time the consignee might have earned some interest on the sold items for year and after 1 year it pays the amount to the company (owner). So the consignee profits more (one through higher selling price and second by informing and paying the amount to the company after sometime). To prevent this, is there any stock checking carried out from company side to the consignee ? Or does any other sort of process take place to prevent this ? Thanks.

Hi there,
In consigment process, stock is maintained as consignment special stock. When a consignment fillup happens, stock will still be under the pocession of the company but under consignment special spock.
If you see the item catg KEN (consignment issue item) in VOV7, you will find that there is a special stock indicator W. When you raise a consignment issue order KE, basing on the item catg determination, automatically KEN will be proposed. So when you PGI a KEN item, stock will automatically deducted from consignment special stock. When the stock in consignment special stock reduces, it means that a consignment issue has happened.
Also KEN item catg is relevant for billing. So when you PGI a KEN item, automatically system do pricing & will generate billing. (Note that for consignment fillup item KBN, there is no pricing or billing relevance).
Basing on these settings, when a consignment issue happens, there is no need for some1 to inform the company. Even though the stock is there at a different location, consignment stock visibility is available in SAP.
Hope this clarifies.
Regards,
Sivanand

Exception /BOBF/CX_FRW_FATAL while executing /SCMTMS/TEND_CONT_PROCESS (Process Frieght quotations and overde Freight RFQs).

Hi Experts,
I am getting a dump when executing /SCMTMS/TEND_CONT_PROCESS (Process Frieght quotations and overde Freight RFQs).
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                     /BOBF/CX_FRW_FATAL
ABAP Program         /BOBF/CL_FRW==================CP
Application Component AP-RC-BOF-RNT
HOW TO CORRECT THE ERRORS-
"UNCAUGHT_EXCEPTION" "/BOBF/CX_FRW_FATAL"
"/BOBF/CL_FRW==================CP" or "/BOBF/CL_FRW==================CM00Z"
"SET_APPLICATION_ERROR"
i really dont know why this dump is coming. I checked the "SET_APPLICATION_ERROR" method.
==> RAISE EXCEPTION TYPE /bobf/cx_frw_fatal
       EXPORTING
       textid           = /bobf/cx_frw_fatal=>sc_application_error
       previous         = io_exception
       mv_bo_name       = mo_conf->ms_obj-bo_name
       mv_proxy_bo_name = mo_conf->ms_obj-bo_esr_name
       application_information = lv_application_information.
Can anyone tell me the possible reason for this dump?
Thanks.
Regards,
Meenakshi

Back Flushing Vendor consigment Material in process order

Dear Experts,
I have a question Regarding Vendor consignment back flushing
while i am doing order confirmation system not proposing vendor name and in good movement tab
may i know what configuration or master data setup is missing
My requirment is i need to back flush vendor consginment material automatically
currently i need to manually choose the vendor while confiming the order
Thanks in advance
Rgrds
Raj

Dear Experts,
I manage to use stock determination group for back flushing consignment material
it works fine system automatically picking up vendor as we do not have multiple vendors
now i have new issue
for instance
i have a RAW material A used in a Product A when i do confirmation system can able to do back flush with movement type 261 K
i am using same RAW material A used in product B and when i do confirmation system give me a error
as below
Pipeline/consignment movement posted without value
Message no. M7234Diagnosis
The system has determined a consignment/pipeline price of 0.00.
Possible reasons:
The system could not find any valid condition for the posting date in the consignment/pipeline info record.
A price of 0.00 was defined in the info record.
System Response
Depending on how the system is configured, the message can be either a warning or an error message.
A withdrawal from this consignment stock or from the pipeline will not create vendor liabilities. For materials with moving average price control, withdrawals are posted without value. For materials with standard price control, a price difference posting is carried out.
The message is also issued when materials are received into consignment stock, as the system must check whether a consignment price of zero is required.
Procedure
If you have authorization, check whether the conditions or the price has been defined correctly in the info record, if necessary. If there is a condition with a price other than zero, check whether the posting date of the movement lies within the condition's validity period.
Proceed
just wonder does any one have this issue
so strange i can issue to product A and not product B
Please help me if you have any problem
Rgrds
Raj

Best Practice for sugar refinery process

hello, my company need to deploy a new business concerning raw sugar refinery.
so we need to analyze the business requirements and propose a process for refinery management .
step 1: arrival of goods in docks
step 2: raw sugar need to be charged in our stock ( quantity and value ) but is not our property
step 3: goods need to be delivered to our plant ( we pay the transport as service for our business partner )
step 4: goods need to be verified ( for quality and quantity ) and accepted by operators
step 5: goods are processed in a refinery plant, we need to verify timing, costs, quantity and human resources employed ( for costs remittance and transfer )
step 6: sugar is delivered to other industrial plants, warehouse and finally sold ( but is not our property ), for us it's like a refinery service.
step 7: we need to trace production lot from raw sugar arrival to the docks up to step 6 .
step 8: inventory and maintenance costs need to be traced because our profit is a part of this refinery service reduced by costs incurred
any suggestions to find the right best practice ?
I'm not a skilled BPS, I was looking for oil refinery but is not the same process, so.. what can i look for?
TNks

Hi Kumar,
In order to have Consigment in SAP u need to have master data such as material master, vendor master and purchase inforecord of consignment type. U have to enter the item category k when u enter PO. The goods receipt post in vendor consignment stock will be non valuated.
1. The intial steps starts with raising purchase order for the consignment item
2. The vendor recieves the purchase order.
3. GR happens for the consignment material.
4. Stocks are recieved and placed under consignment stock.
5. When ever we issue to prodn or if we transfer post(using mov 411) from consignment to own stock then liability occurs.
6. Finally comes the settlement using mrko. You settle the amount for the goods which was consumed during a specific period.
regards
Anand.C

Return to vendors- robust process considering all scenarios

Gurus,
i am redesigning return to vendor process. Our FI team is facing problems in creation of credit memos. they have not done so far and hence there is lot of amount pending from vendors to us. now, they want to be involved in this process a lot.
its workign good for logistics and MM guys.
howver i want to design a process which is best for that perticualr scenarios.
rt now we create return PO whenver we return to vendors.
i got to know FI team can review from Me2l tcode and decide to raise or not.
here are my questions after some R& D of mine reg this.
1a) how can FI team know they have returns. they keep monitoring tcodes?
1) what is teh best return to vendor process when invoice has been done for initial PO.
just reverse MIGO and MIRO?
2) what is the best practise when there is no invoice yet.
3) how to read ME2L and decide whether we need to create crediot memo?
are all quantities less than zero are returns?
4) FI team wants to add additional costs like, frieght, storage, hence they r creating ret PO. can thsi be done even by just doign MIGO or some other conditions setting.
5 ) do we always get to know what original PO is ? based on batch?
6) once a ret PO is created can it be changed for extra costs from FI after its been picked and shipped? ( during Me2L step)
i have no proobs in creatign ret PO as process is workign for other teams and moreover no need to attach PO, however need to know what approach to take when. especially invoiced/ not invoiced... extraa costs/ no extra costs and original PO known/ not known, so that best process can be in place.
regards
Kavana

we worked out a process.. thanks

Frieght vendor payment in STO..?

Hi all
Can anybody explain me about the , Frieght Payment for frieght vendor in STO process.
There is no invoice verification process in STO, but how can i pay the amount to frieght vendor.
Pls explain me with example with T.Codes
Thanks
sap-mm

Hi,
Go to SPRO > MM > Purchasing > Conditions > Define Price Determination Process > Define Schema Determination > Determine Schema for Stock Transport Orders > Here assign Calculation Schema "RM2000" i.e. Stock Transfer Document to the combination of Schema Group Purchase Organization, STO Document Type and Supplying Plant.
Also check Pricing Procedure "RM2000" in M/08.
In M/06 for Condition types;
FRB1     Freight / Value
FRC1     Freight/Quantity (S)
Maintain following;
Cond. class   A Discount or surcharge
Calculat.type B / C Fixed amount / Quantity (B for FRB1 and C for FRC1)
Cond.category B Delivery costs
Now at the bottom, you will get option as "Vendor in GR", here input "2" i.e. Entry always possible
Now in STO (ME21N), maintain values for condition types and select and then click on the "Details" button to enter the Vendor Code.
And SAVE STO.
Now after Outbound Delivery > PGI > GR
Do LIV for the STO, by selecting "Planned Delivery Cost" option and do necessary postings.

Frieght in consigment process

Similar Messages

Maybe you are looking for