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

Similar Messages

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

Regarding Goods Reversal & Goods Issue Process for PO

Hi Experts,
           Could you any one tel me what is Goods Reversal and Goods Issue process for PO...
How to create the FM & detailed Procedure Pls?....
Please any one tel me.......
Thanks & Reagards
HB

Hi Hans,
SOURCE : HELP.SAP
Purpose
Inventory Management uses this process in such a way that the goods issue posting is divided into two parts that run in separate systems. Posting the GI document in the supplying plant results in a message to the receiving plant. The receiving plant then performs a complementary posting. The physical goods receipt takes place as usual.
Prerequisites
When using batch processing, the following prerequisites must be fulfilled:
Both the original and target systems have the same batch definition level.
The batch definition level is either the material or the client.
An ALE scenario exists for materials and classes (characteristics).
Unique batch numbers exist cross-system.
Batches can only be changed in their original system when they are not decoupled. From an organizational point of view, this must also lead to the batch status being changeable in a local SAP R/3 system. For example, this is impossible when transfer posting to a new batch and results in further actions, for example, relabeling containers, palettes and so on.
Characteristics
As for the purchase order in a one-system situation, the system should automatically post the material into the stock in transit at the receiving profit center and the corresponding Profit Center Accounting using intra-CC transfer prices at goods issue for the purchase order and the unchecked delivery. This requirement is valid for one-system situations as well as for two-system situations where there is an ALE interface. No internal billing document should be created.
In a two-system case, the receiving profit center should be derived at goods issue from the unchecked delivery. Profit Center Accounting then takes place with
Stock change transfer price to stock
Internal expense to internal sales
Internal clearing account to stock change transfer price.
Account determination in a purchase order for an intra-company-code transaction must be different from account determination in external transactions. Automatic GR/IR account clearing is required in both one-system and two-system situations.
The stock in transit must be visible in the receiving profit center.
The system must send a shipping notification at goods issue in one-system and two-system situations.
You need to create an invoice document for the internal and external trading statistics for cross-boundary deliveries as well as for customs purposes.
GR/GI slips are created.
Process Flow
Goods Issue Posting for Stock Transfers
The delivery triggers the goods issue in the issuing system.
The call contains the stock transport order data known in the delivery, including the PO item and the logical system of the recipient.
The transaction (quantity and value updates) is selected using the movement type:
Movement Type
Function
641
Goods issue with UB logic (Creation of stock in transit at recipient, immediate value posting).
647
As 641, however the goods receipt line (movement type 101) is added automatically, so that the goods receipt is posted at the same time as the goods issue (one-step procedure).
You determine the movement type according to the schedule line category in Sales and Distribution. The goods issue for a cross-system stock transfer must be different from the integrated transaction. This is achieved by adding a new movement type.
You post quantities and values at goods issue in the same way as a goods issue for a sales order. That is to say, the quantity is posted in the supplying plant and the value is adjusted to that of the stock account. The offsetting posting is made to a clearing account. The known data from the delivery is copied to Accounting to balance the account where necessary.
The system creates a message to the appropriate receiving system for all items with reference to a cross-system purchase order. The system does not perform any validity checks on the recipients data before posting begins. Incorrect Customizing results in the update being terminated.
If a goods issue has receiving plants in different logical systems, an IDoc is sent for each system.
In order that the goods receipt is able to use the values on the receiver side, you must add the values used to post the goods movement, in particular the transfer prices, to the IDoc.
The logic for recognizing the profit center switch functions as follows: At goods issue, the system recognizes that the profit center of the issuing plant is different from the profit center of the receiving plant. The system derives the profit center node from the relevant profit center.
Data Transfer
The IDocs sent by the issuing plant trigger the goods issue postings in the receiving plant.
Background Posting in the Receiving System
The goods receipt is posted in the receiving system using the IDoc. The interface receives the data from the goods issue in the supplying plant. The following processes now run at the recipient:
The system finds the update control for the GR part of the posting.
The goods movement is posted with the new movement type.
During valuation of the goods receipt, the system might, where necessary (UB logic), refer to the values (legal value and the value from the parallel valuation type, if you are using the transfer price function) from the IDoc.
The PO history is updated. The PO history is updated with the material document number from the second part of the GI posting. The GI document number is not stored in the supplying plant, because there is no way to display this document.
In two-step procedures the goods receipt is posted to the stock in transit.
Reversal
You can only reverse this goods issue for the PO using the cancellation transaction in SD. You cannot reverse the GI in Inventory Management.
The material document that is automatically created in the receiving system cannot be canceled. This reversal is triggered by the sending system (the actual reversal of the GI document takes place there) and transmits the data, including the reversal movement type, to the receiving system. No actual reversal is posted in the receiving system, because the material document number of the original document does not exist in this system. This scenario is applicable for cases where you use the two-step procedure (with stock in transit).
Distribution of Batch Master Data and Characteristics
The batch information is transported using the message category BATMAS.
When you create a cross-system goods issue, the system creates the corresponding IDoc using the message category BATMAS.
When the delivery arrives in the target system, the batch and all the information is already present in the system.
Changes to the batch data are also distributed using the message category BATMAS.
The batch can be decoupled in the receiving SAP R/3 system. This means that the batch can have a different status in the receiving system than in the original system. By setting an indicator at material level, you decide whether the batch can be decoupled or whether the batch and all its attributes are copied from the original system. "Decoupled" i.e. "locally independent" batches are no longer distributed from its own system.
The batch data does not need to be available before the physical goods receipt takes place. The goods receipt into the stock in transit does not usually refer to the batch unless you are working with batches with assigned active ingredient values.
If the GI cannot be posted for organizational reasons, for example because the goods cannot be loaded onto a truck until 10pm, then you can post the goods into the GR blocked stock. This stock is also non-batch-specific.
In cases where the GI IDoc arrives before the batch IDoc, then the GI IDoc can be subsequently posted by a periodically scheduled report (transaction BD87). A program like this exists in the SAP standard system. In Customizing for MM Inventory Management (activity Copy, Change Movement Types), you should make settings to define that manual creation of batches at goods receipt is not allowed.
Shipping Notification
The shipping notification is required in the receiving system due to its relevance for MRP. In this way, for example, a change in delivery date determined at goods issue is sent to the receiving system using the shipping notification. The shipping notification can also be used when posting the GR batches.
Reward if found helpfull,
Cheers,
Chaitanya.

How Goods Issu happens in the Stock transfer process with outbound delivery

Hi,
Can you please explain me how the goods issue happens in the Stock transfer scenario with outbound delivery?
can we use VL02n for goods issue for single delivery doc(Delivery type-RL).
Can we use the transaction VL23 for collective processing of goods issue for stock transfers.
Thanks

Hi Anil,
->You can use VL02N transaction to do PGI for the outbound delivery in the Stock transfer scenario.
-->But you have mentioned that delivery type is RL -is this returns delivery
Normally NL delivery will be used in STO(Rplenishment
delivery)
-->You can use VL06G transaction for collective PGI
The transaction VL23 for delivery schdule in the back ground
I hope it will help you,
Regards,
Murali.

Goods issue/receipt print out

Hi could any body let me know the print settings for goods issue & receipts and Logistics invoice verification.
i tried with we01 for GRN , wa01 for GI, in nace settings but could not find the result.
pls let me know the settings.especially for sub contract components issue print settings.
regards
Bheemasimha
9900163939

hi bheema,
Configure Automatic Postings
In this step, you enter the system settings for Inventory Management and Invoice Verification transactions for automatic postings to G/L accounts.
You can then check your settings using a simulation function.
Under Further information there is a list of transactions in Materials Management and their definitions.
What are automatic postings?
Postings are made to G/L accounts automatically in the case of Invoice Verification and Inventory Management transactions relevant to Financial and Cost Accounting.
Example:
Posting lines are created in the following accounts in the case of a goods issue for a cost center:
Stock account
Consumption account
How does the system find the relevant accounts?
When entering the goods movement, the user does not have to enter a G/L account, since the R/3 System automatically finds the accounts to which postings are to be made using the following data:
Chart of accounts of the company code
If the user enters a company code or a plant when entering a transaction, the R/3 System determines the chart of accounts which is valid for the company code.
You must define the automatic account determination individually for each chart of accounts.
Valuation grouping code of the valuation area
If the automatic account determination within a chart of accounts is to run differently for certain company codes or plants (valuation areas), assign different valuation grouping codes to these valuation areas.
You must define the automatic account determination individually for every valuation grouping code within a chart of accounts. It applies to all valuation areas which are assigned to this valuation grouping code.
If the user enters a company code or a plant when entering a transaction, the system determines the valuation area and the valuation grouping code.
Transaction/event key (internal processing key)
Posting transactions are predefined for those inventory management and invoice verification transactions relevant to accounting. Posting records, which are generalized in the value string, are assigned to each relevant movement type in inventory management and each transaction in invoice verification. These contain keys for the relevant posting transaction (for example, inventory posting and consumption posting) instead of actual G/L account numbers.
You do not have to define these transaction keys, they are determined automatically from the transaction (invoice verification) or the movement type (inventory management). All you have to do is assign the relevant G/L account to each posting transaction.
Account grouping (only for offsetting entries, consignment liabilities, and price differences)
Since the posting transaction "Offsetting entry for inventory posting" is used for different transactions (for example, goods issue, scrapping, physical inventory), which are assigned to different accounts (for example, consumption account, scrapping, expense/income from inventory differences), it is necessary to divide the posting transaction according to a further key: account grouping code.
An account grouping is assigned to each movement type in inventory management which uses the posting transaction "Offsetting entry for inventory posting".
Under the posting transaction "Offsetting entry for inventory posting", you must assign G/L accounts for every account grouping, that is, assign G/L accounts.
If you wish to post price differences to different price difference accounts in the case of goods receipts for purchase orders, goods receipts for orders, or other movements, you can define different account grouping codes for the transaction key.
Using the account grouping, you can also have different accounts for consignment liabilities and pipeline liabilities.
Valuation class of material or (in case of split valuation) the valuation type
The valuation class allows you to define automatic account determination that is dependent on the material. for example: you post a goods receipt of a raw material to a different stock account than if the goods receipt were for trading goods, even though the user enters the same transaction for both materials.
You can achieve this by assigning different valuation classes to the materials and by assigning different G/L accounts to the posting transaction for every valuation class.
If you do not want to differentiate according to valuation classes you do not have to maintain a valuation class for a transaction.
Requirements
Before you maintain automatic postings, you must obtain the following information:
1. Valuation level (plant or company code)
Establish whether the materials are valuated at plant or at company code level
When valuation is at plant level, the valuation area corresponds to a plant.
When valuation is at company code level, the valuation area corresponds to a company code.
Define valuation level
2. Chart of accounts and valuation grouping code per valuation area
Find out whether the valuation grouping code is active.
Activate split valuation
If it is not active, determine the chart of accounts assigned to each valuation area (via the company code).
If it is active, determine the chart of accounts and the valuation grouping code assigned to each valuation area.
Group valuation areas
You must define a separate account determination process for chart of accounts and each valuation grouping code.
3. Valuation class per material type
If you wish to differentiate the account determination process for specific transactions according to valuation classes, find out which valuation classes are possible for each material type.
Define valuation classes
4. Account grouping for offsetting entries to stock accounts
Under
Define account grouping for movement types , determine for which movement types an account grouping is defined for the transaction/event keys GGB (offsetting entry to stock posting), KON (consignment liabilities) and PRD (price differences).
Default settings
G/L account assignments for the charts of accounts INT and the valuation grouping code 0001 are SAP standard.
Activities
1. Create account keys for each chart of accounts and each valuation grouping code for the individual posting transactions. To do so, proceed as follows:
a) Call up the activity
Configure Automatic Postings .
The R/3 system first checks whether the valuation areas are correctly maintained. If, for example, a plant is not assigned to a company code, a dialog box and an error message appear.
From this box, choose Continue (next entry) to continue the check.
Choose Cancel to end the check.
The configuration menu Automatic postings appears.
b) Choose Goto -> Account assignment.
A list of posting transactions in Materials Management appears. For further details of the individual transactions, see Further information.
The Account determination indicator shows whether automatic account determination is defined for a transaction.
c) Choose a posting transaction.
A box appears for the first posting transaction. Here you can enter a chart of accounts.
You can enter the following data for each transaction:
Rules for account number assignments
With Goto -> Rules you can enter the factors on which the account number assignments depend:
- debit/credit indicator
- general grouping (= account grouping)
- valuation grouping
- valuation class
Posting keys for the posting lines
Normally you do not have to change the posting keys. If you wish to use new posting keys, you have to define them in the Customizing system of Financial Accounting.
Account number assignments
You must assign G/L accounts for each transaction/event key (except KBS). You can assign these accounts manually or copy them from another chart of accounts via Edit -> Copy .
If you want to differentiate posting transactions (e.g. inventory postings) according to valuation classes, you must make an account assignment for each valuation class.
Using the posting transaction "Offsetting entry for inventory posting", you have to make an account assignment for each account grouping
If the transaction PRD (price differences) is also dependent on the account grouping, you must create three account assignments:
- an account assignment without account grouping
- an account assignment with account grouping PRF
- an account assignment with account grouping PRA
If the transaction KON (consignment and pipeline liabilities) is also dependent on the account grouping, you must create two account assignments:
- an account assignment without account grouping (consignment)
- an account assignment with account grouping (pipeline)
d) Save your settings.
2. Then check your settings with the simulation function.
With the simulation function, you can simulate the following:
Inventory Management transactions
Invoice Verification transactions
When you enter a material or valuation class, the R/3 system determines the G/L accounts which are assigned to the corresponding posting transactions. Depending on the configuration, the SAP system checks whether the G/L account exists
In the simulation you can compare the field selection of the movement type with that of the individual accounts and make any corrections.
If you want to print the simulation, choose Simulation -> Report.
To carry out the simulation, proceed as follows:
a) Choose Settings to check the simulation defaults for
- the application area (Invoice Verification or Inventory Management)
- the input mode (material or valuation class)
- account assignment
Instructions
b) Choose Goto -> Simulation.
The screen for entering simulation data appears.
c) Depending on the valuation level, enter a plant or a company code on the screen.
d) When you simulate Inventory Management transactions, goods movements are simulated. The R/3 system suggests the first movement type for simulation. If several movements are possible with this movement type, you can select a line.
When you simulate Invoice Verification transactions, a list appears on the screen of the possible transaction types. Select a line.
e) Then choose Goto -> Account assignments.
A list appears of the posting lines which can be created by the selected transaction. For each posting line, the G/L account for the debit posting as well as the G/L account for the credit posting are displayed.
f) From this screen, choose Goto -> Movement+ to get a list of the posting lines for the next movement type or transaction type.
If you work with valuation classes, choose Goto -> Valuation class+ to receive the simulation for the next valuation class. This function is not possible when simulating with material numbers.
Choose Goto -> Check screen layout to compare the movement type with the G/L accounts determined by the system and make any necessary corrections.
Note
The simulation function does NOT obviate the need for a trial posting!
Further Notes
The following list shows the individual transactions with examples of how they are used:
AG1 - No documentation currently available.
AG2 - No documentation currently available.
AG3 - No documentation currently available.
Expense/revenue from consumption of consignment material (AKO)
This transaction is used in Inventory Management in the case of withdrawals from consignment stock or when consignment stock is transferred to own stock if the material is subject to standard price control and the consignment price differs from the standard price.
Expenditure/income from transfer posting (AUM)
This transaction is used for transfer postings from one material to another if the complete value of the issuing material cannot be posted to the value of the receiving material. This applies both to materials with standard price control and to materials with moving average price control. Price differences can arise for materials with moving average price if stock levels are negative and the stock value becomes unrealistic as a result of the posting. Transaction AUM can be used irrespective of whether the transfer posting involves a transfer between plants. The expenditure/income is added to the receiving material.
Provisions for subsequent (end-of-period rebate) settlement (BO1)
If you use the "subsequent settlement" function with regard to conditions (e.g. for period-end volume-based rebates), provisions for accrued income are set up when goods receipts are recorded against purchase orders if this is defined for the condition type.
Income from subsequent settlement (BO2)
The rebate income generated in the course of "subsequent settlement" (end-of-period rebate settlement) is posted via this transaction.
Income from subsequent settlement after actual settlement (BO3)
If a goods receipt occurs after settlement accounting has been effected for a rebate arrangement, no further provisions for accrued rebate income can be managed by the "subsequent settlement" facility. No postings should be made to the account normally used for such provisions. As an alternative, you can use this transaction to post provisions for accrued rebate income to a separate account in cases such as the one described.
Supplementary entry for stock (BSD)
This account is posted when closing entries are made for a cumulation run. This account is a supplementary account to the stock account; that is, the stock account is added to it to determine the stock value that was calculated via the cumulation. In the process, the various valuation areas (for example, commercial, tax), that are used in the balance sheet are taxed separately.
Change in stock (BSV)
Changes in stocks are posted in Inventory Management at the time goods receipts are recorded or subsequent adjustments made with regard to subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
Stock posting (BSX)
This transaction is used for all postings to stock accounts. Such postings are effected, for example:
In inventory management in the case of goods receipts to own stock and goods issues from own stock
In invoice verification, if price differences occur in connection with incoming invoices for materials valuated at moving average price and there is adequate stock coverage
In order settlement, if the order is assigned to a material with moving average price and the actual costs at the time of settlement vary from the actual costs at the time of goods receipt
Because this transaction is dependent on the valuation class, it is possible to manage materials with different valuation classes in separate stock accounts.
@1A@Caution
Take care to ensure that:
A stock account is not used for any transaction other than BSX
Postings are not made to the account manually
The account is not changed in the productive system before all stock has been booked out of it
Otherwise differences would arise between the total stock value of the material master records and the balance on the stock account.
Revaluation of "other" consumptions (COC)
This transaction/event key is only relevant to Brazil. It is used if a revaluation report is used for company codes in Brazil.
The revaluation report uses the actual prices determined by the material ledger/actual costing to:
Revaluate costs on the basis of actual prices
Post the price differences arising from "other" consumptions (e.g. consumption to cost center) to a collective account
This transaction/event key is needed to post the price differences. The account specified here is posted with the price differences for "other" consumptions.
No documentation currently available.
Small differences, Materials Management (DIF)
This transaction is used in Invoice Verification if you define a tolerance for minor differences and the balance of an invoice does not exceed the tolerance.
Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)
These transactions are used only if
Purchase Account Management is active in the company code.
Note
Due to special legal requirements, this function was developed specially for certain countries (Belgium, Spain, Portugal, France, Italy, and Finland).
Before you use this function, check whether you need to use it in your country.
Freight clearing (FR1), provision for freight charges (FR2), customs duty clearing (FR3), provision for customs duty (FR4)
These transactions are used to post delivery costs (incidental procurement costs) in the case of goods receipts against purchase orders and incoming invoices. Which transaction is used for which delivery costs depends on the condition types defined in the purchase order.
You can also enter your own transactions for delivery costs in condition types.
External service (FRL)
The transaction is used for goods and invoice receipts in connection with subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
External service, delivery costs (FRN)
This transaction is used for delivery costs (incidental costs of procurement) in connection with subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
Offsetting entry for stock posting (GBB)
Offsetting entries for stock postings are used in Inventory Management. They are dependent on the account grouping to which each movement type is assigned. The following account groupings are defined in the standard system:
AUA: for order settlement
AUF: for goods receipts for orders (without account assignment)
and for order settlement if AUA is not maintained
AUI: Subsequent adjustment of actual price from cost center directly
to material (with account assignment)
BSA: for initial entry of stock balances
INV: for expenditure/income from inventory differences
VAX: for goods issues for sales orders without
account assignment object (the account is not a cost element)
VAY: for goods issues for sales orders with
account assignment object (account is a cost element)
VBO: for consumption from stock of material provided to vendor
VBR: for internal goods issues (for example, for cost center)
VKA: for sales order account assignment
(for example, for individual purchase order)
VKP: for project account assignment (for example, for individual PO)
VNG: for scrapping/destruction
VQP: for sample withdrawals without account assignment
VQY: for sample withdrawals with account assignment
ZOB: for goods receipts without purchase orders (mvt type 501)
ZOF: for goods receipts without production orders
(mvt types 521 and 531)
You can also define your own account groupings. If you intend to post goods issues for cost centers (mvt type 201) and goods issues for orders (mvt type 261) to separate consumption accounts, you can assign the account grouping ZZZ to movement type 201 and account grouping YYY to movement type 261.
@1A@Caution
If you use goods receipts without a purchase order in your system (movement type 501), you have to check to which accounts the account groupings are assigned ZOB
If you expect invoices for the goods receipts, and these invoices can only be posted in Accounting, you can enter a clearing account (similar to a GR/IR clearing account though without open item management), which is cleared in Accounting when you post the vendor invoice.
Note that the goods movement is valuated with the valuation price of the material if no external amount has been entered.
As no account assignment has been entered in the standard system, the assigned account is not defined as a cost element. If you assign a cost element, you have to enter an account assignment via the field selection or maintain an automatic account assignment for the cost element.
Purchase order with account assignment (KBS)
You cannot assign this transaction/event key to an account. It means that the account assignment is adopted from the purchase order and is used for the purpose of determining the posting keys for the goods receipt.
Exchange rate differences in the case of open items (KDM)
Exchange rate differences in the case of open items arise when an invoice relating to a purchase order is posted with a different exchange rate to that of the goods receipt and the material cannot be debited or credited due to standard price control or stock undercoverage/shortage.
Differences due to exchange rate rounding, Materials Management (KDR)
An exchange rate rounding difference can arise in the case of an invoice made out in a foreign currency. If a difference arises when the posting lines are translated into local currency (as a result of rounding), the system automatically generates a posting line for this rounding difference.
KDV - No documentation currently available.
Consignment liabilities (KON)
Consignment liabilities arise in the case of withdrawals from consignment stock or from a pipeline or when consignment stock is transferred to own stock.
Depending on the settings for the posting rules for the transaction/event key KON, it is possible to work with or without account modification. If you work with account modification, the following modifications are available in the standard system:
None for consignment liabilities
PIP for pipeline liabilities
Offsetting entry for price differences in cost object hierarchies (KTR)
The contra entry for price difference postings (transaction PRK) arising through settlement via material account determination is carried out with transaction KTR.
LKW - No documentation currently available.
Price differences (PRD)
Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system:
None for goods and invoice receipts against purchase orders
PRF for goods receipts against production orders and
order settlement
PRA for goods issues and other movements
PRU for transfer postings (price differences in the case
of external amounts)
PRK - No documentation currently available.
PRP - No documentation currently available.
PRQ - No documentation currently available.
PRV - No documentation currently available.
PRY - No documentation currently available.
RAP - No documentation currently available.
RKA - No documentation currently available.
Provision for delivery costs (RUE)
Provisions are created for accrued delivery costs if a condition type for provisions is entered in the purchase order. They must be cleared manually at the time of invoice verification.
Taxes in case of transfer posting GI/GR (TXO)
This transaction/event key is only relevant to Brazil (nota fiscal).
Revenue/expense from revaluation (UMB)
This transaction/event key is used both in Inventory Management and in Invoice Verification if the standard price of a material has been changed and a movement or an invoice is posted to the previous period (at the previous price).
Expenditure/income from revaluation (UMD)
This account is the offsetting account for the BSD account. It is posted during the closing entries for the cumulation run of the material ledger and has to be defined for the same valuation areas.
Unplanned delivery costs (UPF)
Unplanned delivery costs are delivery costs (incidental procurement costs) that were not planned in a purchase order (e.g. freight, customs duty). In the SAP posting transaction in Logistics Invoice Verification, instead of distributing these unplanned delivery costs among all invoice items as hitherto, you have the option of posting them to a special account. A separate tax code can be used for this account.
Input tax, Purchasing (VST)
Transaction/event key for tax account determination within the "subsequent settlement" facility for debit-side settlement types. The key is needed in the settlement schema for tax conditions.
Goods issue, revaluation (inflation) (WGI)
This transaction/event key is used if already-posted goods issues have to be revaluated following the determination of a new market price within the framework of inflation handling.
Goods receipt, revaluation (inflation) (WGR)
This transaction/event key is used if already-effected transfer postings have to be revaluated following the determination of a new market price within the framework of inflation handling. This transaction is used for the receiving plant, whereas transaction WGI (goods receipt, revaluation (inflation)) is used for the plant at which the goods are issued.
GR/IR clearing (WRX)
Postings to the GR/IR clearing account occur in the case of goods and invoice receipts against purchase orders. For more on the GR/IR clearing account, refer to the SAP Library (documentation MM Material Valuation).
Caution
You must set the Balances in local currency only indicator for the GR/IR clearing account to enable the open items to be cleared. For more on this topic, see the field documentation.
see the below link also
http://209.85.175.104/search?q=cache:7FJheuTAxiQJ:help.sap.com/bp_afsv1500/CP_AFS_DE/documentation/AFS_Solution_Scope_EN_DE.docprintsettingsforgoodsissue%26receiptsandLogisticsinvoice+verification.&hl=en&ct=clnk&cd=2
thanks
saGAR
REWARD ME IF USEFULL

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...

MB1A : FI doc for Goods Issue

Hi,
When i enter Goods Issue with Tcode : MB1A betwen 2 plants i have two FI Docs created automatically, i want to know when we maintain the accounts used in these docs.
Please what's the path IMG or Tcode to do that?
Regards.

Hi,
GBB is for Offsetting entry for inventory posting.
U can assign ur GL accounts to that particular valuation class for such material u r making goods issue.
How does the system find the relevant accounts?
When entering the goods movement, the user does not have to enter a G/L account, since the R/3 System automatically finds the accounts to which postings are to be made using the following data:
o Chart of accounts of the company code
If the user enters a company code or a plant when entering a transaction, the R/3 System determines the chart of accounts, which is valid for the company code. You must define the automatic account determination individually for each chart of accounts.
o Valuation grouping code of the valuation area
If the automatic account determination within a chart of accounts is to run differently for certain company codes or plants (valuation areas), assign different valuation grouping codes to these valuation areas.
You must define the automatic account determination individually for every valuation grouping code within a chart of accounts. It applies to all valuation areas which are assigned to this valuation grouping code.
If the user enters a company code or a plant when entering a transaction, the system determines the valuation area and the valuation grouping code.
o Transaction/event key (internal processing key)
Posting transactions are predefined for those inventory management and invoice verification transactions relevant to accounting.
Posting records, which are generalized in the value string, are assigned to each relevant movement type in inventory management and each transaction in invoice verification. These contain keys for the relevant posting transaction (for example, inventory posting and consumption posting) instead of actual G/L account numbers.
You do not have to define these transaction keys, they are determined automatically from the transaction (invoice verification) or the movement type (inventory management). All you have to do is
assign the relevant G/L account to each posting transaction.
o Account grouping (only for offsetting entries, consignment liabilities, and price differences)
Since the posting transaction "Offsetting entry for inventory posting" is used for different transactions (for example, goods issue, scrapping, physical inventory), which are assigned to different accounts (for example, consumption account, scrapping, expense/income from inventory differences), it is necessary to divide the posting transaction according to a further key: account grouping code.
An account grouping is assigned to each movement type in inventory management which uses the posting transaction "Offsetting entry for inventory posting". Under the posting transaction "Offsetting entry for inventory posting", you must assign G/L accounts for every account grouping,
that is, assign G/L accounts.
If you wish to post price differences to different price difference accounts in the case of goods receipts for purchase orders, goods receipts for orders, or other movements, you can define different account grouping codes for the transaction key. Using the account grouping, you can also have different accounts for consignment liabilities and pipeline liabilities.
o Valuation class of material or (in case of split valuation) the valuation type
The valuation class allows you to define automatic account determination that is dependent on the material. for example: you post a goods receipt of a raw material to a different stock account than if the goods receipt were for trading goods, even though the user enters the same transaction for both materials.
You can achieve this by assigning different valuation classes to the materials and by assigning different G/L accounts to the posting transaction for every valuation class. If you do not want to differentiate according to valuation classes you do not have to maintain a valuation class for a transaction.
Offsetting entry for stock posting (GBB)
Offsetting entries for stock postings are used in Inventory
Management. They are dependent on the account grouping to which each
movement type is assigned. The following account groupings are
defined in the standard system:
- AUA: for order settlement
- AUF: for goods receipts for orders (without account
assignment)
and for order settlement if AUA is not maintained
- AUI: Subsequent adjustment of actual price from cost center
directly
to material (with account assignment)
- BSA: for initial entry of stock balances
- INV: for expenditure/income from inventory differences
- VAX: for goods issues for sales orders without
account assignment object (the account is not a cost
element)
- VAY: for goods issues for sales orders with
account assignment object (account is a cost element)
- VBO: for consumption from stock of material provided to
vendor
- VBR: for internal goods issues (for example, for cost
center)
- VKA: for sales order account assignment
(for example, for individual purchase order)
- VKP: for project account assignment (for example, for
individual PO)
- VNG: for scrapping/destruction
- VQP: for sample withdrawals without account assignment
- VQY: for sample withdrawals with account assignment
- ZOB: for goods receipts without purchase orders (mvt type
501)
- ZOF: for goods receipts without production orders
(mvt types 521 and 531)
You can also define your own account groupings. If you intend to
post goods issues for cost centers (mvt type 201) and goods issues
for orders (mvt type 261) to separate consumption accounts, you can
assign the account grouping ZZZ to movement type 201 and account
grouping YYY to movement type 261.
I hope u got the explanation what u wanted.
Assign points if useful
Regards,
Jigar

Posting of Goods Issue for a Delivery (Different movement types)

Hello SD Experts,
We have this process wherein we use Deliveries w/o reference. There's a customization in place for this process, the movement type is determined through the item category of the material.
Given this scenario, my question is if it is possible to process the goods issue of a delivery with multiple item which require different movement types (diffrent items and item categories thus it have different movement types)?
Thank you for your kind consideration.

Hello,
Yes, you can.
As you know LO is std delv doc for delv w/o reference.
And I cat determination for that LO delv doc are
Delv Type __ I Cat Group __ Usage __ High I Cat __ Def I Cat __ Man I Cat __ Man I Cat
LO _____________________TEXT ______________ DLTX
LO ________DIEN____________________________ DLX _______DLX
LO ________LEER___________________________ DLN
LO ________LEER________________DLNG_______DLNZ
LO ________LEIS_____________________________DLX_______DLX
LO________ NLAG____________________________ DLX
LO________NORM____________________________DLN
LO________NORM________CHSP_______________DLN
LO________NORM________CHSP____KLN________KLN
LO________NORM________CHSP____TANN______TANN
LO________NORM________PACK_______________DLN________DLX________DLP
LO________VERP____________________________DLN
LO________VERP_________PACK_______________HUPM______DLN
LO ________VOLL____________________________ DLNG
LO ________ WERT____________________________ DLW
Corresponding maintain movement type in Schedule line cat (Tcode VOV6) & determination that in TCode VOV5.
If you want diff movement type then create your own 'Z' Sch line cat with you desired Movement type (Tcode VOV6) and determine the Sch line Cat accordingly in TCoDe VOV5.
Thanks & Regards
JP

Posting multiple goods issues against the same delivery

Hello gurus,
We are a fashion apparel company using ECC 6.0 and would like to know if it is possible to post mutliple goods issues against the same delivery?
I will explain the business requirement.
- We create a stock transport order to deliver 400 units of merchandise to on or our retail stores (STO is created and processed to a delivery).
- This information is passed down to our warehouse management system (which is not SAP)
- Our warehouse management system has the ability to split a delivery into multiple shipment when needed. For example, our warehouse may only be able to complete 250 units for our morning shipment and will therefore pick, pack and post this. This will feed back into SAP and process a 641 movement so that the units now show as "in transit". This is needed so that our stores can process the ASN and move the units into their inventory when they receive the merchandise later that day.
- During the afternoon, our warehouse will process the remaining 150 units and will ship this to our store later in the evening or next day.
Currently, we are not able to process another goods issue against a delivery as we close out the delivery during the first goods issue. We would prefer not to have to generate a new delivery for our DC and let them continue to process against the same delivery, but we are unsure how to configure this.
Any help or guideance would be extremely appreciated
Thanks in advance

Hi RJ,
First of all sorry to write such a lengthy reply,In one line if i want to summerize then it is not possible with standard SAP however we can achieve this by writing some piece of code in both the system
AS - IS
               Business process
          From business process point of view you are right that once the pick & pack is in process it is not advisable to create a new delivery document for balance quantity and share the same with WMS as then they have to create a new document in WMS and start picking based on that rather then the old delivery document number. if i am in your position then i can give a thought like this
e.g.
Delivery                                                  - 100 Unit
Shipment confirmation from WMS            -   60 Unit
Change in delievry quanity / Pick qty        -   60 Unit
Invoice from SAP                                    -   60 Unit
Second confirmation from WMS                          -   40 Unit
Change in the existing delivery quantity                -   Now here we have two option either
1) Change the delivery quantity / Pick qty to (60+40) =100 or
2) Remove the 60 and update 40 as delivery and pick quantity
Pros & Cons
if you will select option 1 then furhter invoice will happen for 100 unit which is incorrect as physically you are shipping only 40 unit
if you are selecting option 2 then the document flow is incorrect as you don't have history(in SAP) for the 60 unit which was shipped earlier
Solution ::
so in my opinion the best option is to create a seperate delivery document (store the old delviery number in one of the field of the new delivery and pass the same to custom segment of the IDoc) transmit the IDoc to WMS write the validation logic in WMS
Find the record with old deliver number in the WMS system, check the status whether it is active or inactive
if it is acitive Validate the Material + qty with the WMS record(Material + balance quantity) if both are same then pass the new deliery number to custom field of the WMS table
At the time of confirming back to the SAP, Write a piece of code in SAP that if the incoming idoc custom field(new delivery number) field is populated then ignore the orignal document number and post the document using the new delivery document number
Hope this help

Goods issue asking for currency

The local and system currency of the DB is in AUD.
When processing a Goods Issue for items that have been purchased in EURO, SAO is asking for a currency / exchange rate in EURO before processing the transaction.
Both the purchases and inventory accounts (inventory offset a/c) are both set up in AUD.
Please assist.

Hi Julie,
Thanks for the reply - this answers my question.
The last purchase price is active in the Goods Issue screen, and the product was last purchased in Euro.
If we change the price list to our supplier with no price, price list, the item can be added without reference to an exchange rate.
Cheers Lisa

Can not "post goods issue" against Vendor Return PO.

Hello Friends,
**I have a problem During the "Vendor Return Through Purchase Order" Process.I crated a PO with return flag set.**
**Then 1) Created a outbound delivery against purchase order (VL10B)**
2) Created a Billing (VF01)**
3) Next is VL02N - While doing the "post goods issue" where i got following error message "Update control of movement type is incorrect (entry 161 X X _ L)"**
Its shows setting related to Mvt 161 to update .I check allowed transaction with respect to 161....VL02N is there .....But don't understand what change needed in "Update control /WM movement type is needed.....Pls suggest any solution........Thanx**
Regards
Sachin
*Error Messafe -
Update control of movement type is incorrect (entry 161 X X _ L)
Message no. M7226
Diagnosis
The system could not find entry 161 X X _ L in any of the movement type control tables.
Procedure
Cancel current processing.
Contact your system administrator.
Action to be taken by the system administrator
Check in Customizing for Inventory Management under Copy, Change Movement Types whether the entry is contained in the Update control view for the movement type.
If the entry is missing, proceed as follows:
For standard movement types, this means that the given process is not supported using the present data combination. Do not create any entries without prior arrangement with your SAP consultant. Otherwise, incorrect postings may result.
For customer-defined movement types (beginning with 9, X, Y, or Z), this may mean that they have not been fully defined. Delete the movement type and re-create it by copying a standard movement type.

Hi Antony,
Thanx for reply.
1) I had assign delivery Type (RL -Returns Purchase order) to my document type. Assingnment of delivery type thru
spro>MM->purchasing>purchase order->set up stock transport order--->assign delivery type and checking rule....
2) MvT - 161----If i modify 161 wrt to GR Returns what modification is needed ? ......
3) VOV6 - I had checked it ,maintain it, but that is not relavant in my case....
4) During PGI system pick 161 as defalult MvT.....can we change it t0 122 ? but how...??
still the problem is there......
Sachin

About goods issue from vendor consignment stock

Hi, I meet some issue needs your help!
The outbound delivery needs to post goods issue from vendor consigment stock directly. then how to choose which vendor's
stock for this delivery base on the actual process?
thanks
Best Regards,
Rory

Hi
In R3 it is not possible
If say material X is 100 units lies in your premises the vendor consignment stocks (the vendor property lying in your premises ) and out of that 100 units if you are making a sales order and then a goods issue means it is not possible
To sell that material you need to make it your own stock ( that is transfer from vendor consignment to your own ) as good as buying that stocks and then sell it
But the same scenario is possible in IS retail
For this iS retail server is reqd
In Retail you can play with vendor consignment stocks as much as possible without making our own stocks
You can search SAP library regarding the settings of the same
http://help.sap.com/erp2005_ehp_04/helpdata/en/c6/af3c415e5dde2be10000000a1550b0/frameset.htm
Regards
Raja

Goods issue from vendor consignment stock with freight charge

Hi Experts,
I have a typical scenario for GI from consignment stock with freight charge.
The consigment price is agreed of the material is agreed between the vendor and the client. The vendor buy the material and use the company/client shipment.The client carry the vendor material in their shipping. The fright charges was not included in the consignment price. Presently they accumulated the vendor frieght charge in a separate account.
When the user raise a reservation and goods issue was done from consignment stock Info record price of material for the consignment + 8% of the price of material should be charge to the user.
And the 8% of info record price of the consignment material should be posted to freight recovery account.
So there is no balance between the freight charges account and the freight recovery account.
Can you suggest who we can mapped this process?
Regards
DP

Hi DP,
As SAP doesn't Support Delivery cost settlement with the consignment process to seprate G/L ( Similar to accruals ), you need to go for Z development which while posting MRKO will be executed with refernce to PO & Issue Document Posting the freight Value to Appropriate fright G/L .
Regards
Manish
Edited by: Manish Kumar on Nov 3, 2010 12:06 PM

Goods issue in third party process

Hi All,
I have done third party process. But I am not clear for goods issue to the customer.
We will place goods at customer premises at the time of goods receipt with purchase order reference. In this flow will place goods to customer place directly. Why should I go once again goods issue to customer and which document reference can I do.
Thanks
Nagi

Hi
In Third party scinerio their is no need to issue stock to customer or vendor,
In system when we do GR stock is consumed that momvent, after GR quantity is not update.
Regards
Chandrajit Patil

Goods issue to vendor

Dear all
How to send the material to vendor without PO.Which movement type?
& how to get this material back to our stock?
Thanks

Hi,
Two option: -
1) Follow Subcontract purchase order process
2) Create service order for service changes of material.
Issue material to vendor with MIGO >> Good Issue >> Other.
Here you can issue material to vendor.
Then at the time of back material from vendor you can create material document with MB11 and take reference of 501: - Transfer posting without purchase order movement type.
Regards,
Mahesh Wagh

Vendor consigment process combined goods issue to cusotmer

Similar Messages

Maybe you are looking for