IW33 : Good Issue but Cost show in Plan Cost instead of Actual Cost

Hi All,
Would like have your helping hand on below issue.
Warranty Order been done the Good Issue but the cost still planning in plan cost instead of actually cost.
Information as shown below.
Thank you advise in advance.
Trevor Wong.

Abi,
Can you see that there is a difference in the the actual costs reported on the Cost tab (350 RM), and those reported using the Rep Plan/Act button (1100RM).
This is because the Cost tab costs are not correct.
As pointed out by Maheswaran KD above, please run the correction program RIPMCO00 via transaction SE38/SA38, then check the Cost tab data again.
PeteA

Similar Messages

Goods Issues but not invoiced

Hello forum, a question on any Sales/Billing reports people know of for goods that have been goods issued but are awaiting invoicing. We use POD processing and can get some reports but none with a financial value at an item level. We also use tcode VF04 to view pending deliveries to be invoiced but again doesnt show any epxected revenue and so was wondering if there are any other standard reports to give me this information?
Much appreciated
Dan

Through standard TCodes VF04 and VF06, you can generate deliveries that are PGId but not invoiced but value will not flow there. For this, you need to develop a zee tcode considering the tables VBAP (for unit price) and LIPS (for material code and quantity PGId).
thanks
G. Lakshmipathi

Batch not determined in MIGO-Goods Issue for cost center

Hi,
We are using Batch Determination while posting Goods Issue to cost center. However, when we enter * in the batch field system does not propose the batches.
We have done following settngs
Strategy type ME01 which is SAP standard
Batch search procedure - ME0001
Search procedure ME0001 is assigned to movement type 201 in "Allocate IM Search Procedure/Activate Check"
Sort Rule - 01 using charecterstics (ascending)
Class - BATCH_MASTER created
Characterstics - Size, Shape, Color (No table or field are maintained in Addional Data) assigned to this class.
Material is maintained with classification and batch management active.
Master Data - Search Strategy is maintained using t code MBC1 for stratefy type ME01 (Key combination Movement Type/Plant/Material). Selection criteria - Values maintained for characterstics. Sort Rule - 01
Now when we are issuing goods to cost center and enter * in batch field, system is supposed to suggest the batches (material is in stock and batches are available). However, system does not give pop up.
Am I missing something? Where is the batch determination button as system is giving message to use button?
Shekhar

Thank you for the answer.
It gives only one batch and not all the batches. Why it could be?
Shekhar

Good issues to cost center with extra charges 10% from cost

Hiii Guy,
My user would like to charge the cost center 10% from cost when good issues to cost center is perform,
can we do it in sap ?

The scenario is like this,
Only Merchandise Department have the authority to ordering merchandise item from vendor, when other depart required that merchandise item, Merchandise depart will perform GI to that requested cost center.
So Merchandise Depart would like to have extra charge on there extra work.

Goods Issue with cost

Hello
I am trying to make a goods issue to adjust the inventory, but i want to make it with the real cost of the product.
I have just made a formated search to get the cost of the product, the problem is that if i select the last purchase price list, i update this price with the cost, and i dont want to update the last purchase price.
If i choose another list, for example price list 01, this list doesnt get update with the cost?
Thanks
Jacobo

Hi,
The price list in goods issue document is defaulted the 'last purchase
price', and you could manually change it by select from the drop down
list before you add the document.And you could also manually change the info price column.
However the price list and price in the document is only informative. From the testing we could see that the item's cost will always be
used to calculate released stockvalue and create journal postings.
The item cost and last purchase price will not be affected by adding the
goods issue document.
Best Regards
Helen Sun

Hi, problem in goods issue to cost center Error message M7314

Hi to you all,
I am trying to post a good issue for a material to a cost center but an error message is coming out and says that "stock becomes negative see long text. message no - M7314". the material type was at the begining not valorated (like NLAG material type) but later on it had to be valorated, so the flag was triggered from the basic configuration of material type. if i see the material master record i can noticed that the material has no price neither the amount of stock in the plant, but if i check the stock in any MM report TX like MMBE or MB52 i can see that there is some stock in it. we need to registered the stock issue, any help that you can provide me i´ll appreciate it.
Best regards.
OOOP

When we issue the material to Cost Center then amount (Qty X Value) get debited to that particular cost center,
I think system fails to calculate the amount as there is NO value maintained in material master
this is what I thought
Error Message M7314 is
Short Text
Valuated stock becomes negative: & -> see long text
Diagnosis
When a goods movement or an incoming invoice is entered, the system simulates the update of the valuation data in the material master record. The current simulation indicates that this posting would lead to a negative stock quantity (or a negative sales value) although negative stocks are not allowed for this material.
Procedure
You cannot post this item. Therefore, terminate current processing.
Display the material master record (accounting data).
Check the price, stock value, and stock quantity (also for the previous month, if required).
Proceed
Display the material documents and the accounting documents for the material and check whether the stock quantity is realistic.
Material documents Proceed
Accounting documents Proceed
If the stock value does not correspond to the stock quantity, data inconsistencies may exist.
Please contact SAP Support via SAPNet Frontend as soon as possible.
Support requires the following information from you:
ID and number of this error message (M7 3XX)
Material number and plant
Total stock and its value (see the accounting data in the material master record)

Where do I define the automatic posting of goods issue to Cost Center?

Dear Experts,
I found out that all the raw material consumed each time I do the confirmation of process order via CORK did not post to Cost Center.
Where do I define the automatic posting to Cost Center for Goods issue for consumption?
regards,
Abraham

Hi,
I found out the default movement type has been predefined to 261 (GI for Order, in which it doesn't post to Cost Center). I guess the standard system has a valid reason to set it as 261 instead of 201 (GI for cost center).
As far as I understand, the Process order will accumulate all the costs (direct cost - material, labour and machine hour and also indirect cost) during the confirmation (material is backflushed and fnished goods is auto-GR). And at the end of the period, this process order will be settled its variance if there is (between the total cost credited - based on standard cost of the finished goods and actual total accumulated costs debited).
So, my question is, by right should there be any CO posting being made to Cost Center for material consumption in the above process flow as I checked in the standard system, the material movement for raw material and finished goods have no Cost Center posting at all?
regards,
Abraham

Goods Issue for Cost Center 201 : special stock E not supported

Dear guru ,
I need to run a goods issue(trx.MIGO) for cost center using movement type 201 for a material
in special stock E (with sales order and sales order item).
The system send this message : special stock E not supported.
How can it solved this problem ?
Thanks in advance.

first tranfer stock from Sales Stock to Own stock as follows
Tcode - MB1B / MIGO
Mvt type - 411 E Transfer posting sales order to own
Then issue this own stock to Cost center as follows
Tcode - MB1A / MIGO
Mvt type - 201
hope it helps]
Regards,
Rahul

Creative cloud desktop won't load the "apps" section/shows download error/ have uninstalled & reinstalled/ also completed yosemite os install successfully to see if it was a compatability issue/but still shows download error on apps/ this only occurred af

I have a macbook pro 2010 & extra storage and drive space
I don't know what the link is between the new creative cloud update in january and the loss of my apps & downloading error after that update, to the desktop window?
Before that I hadn't had any trouble with the apps window..all the other parts are syncing and seem fine?
I uninstalled & reinstalled the creative cloud desktop
I installed the yosemite os x to see if the new interface was an issue...all was fine with the yosemite install
I have checked for the answer in the troubleshooting guide
nothing seems to apply at this point...
didn't know if anyone else was having the same difficulty?
Thanks

is this the 'unknown' download error or some other error? attaching a screenshot of the error if it's in english would be helpful.

Closing Date showing 31-12-9999 instead of Actual Date

Hi All,
In the IC while creating Service request transaction in CRM 7.0 closing date is showing as per date rule in the Transaction but when we search the same transaction in the inbox the Closing Date showing as 31-12-9999. We have used standard Date profile in the transaction at both header and Item level.
Any solution for this issue?
Thanks in advance,
Ramesh

Hi Pepe,
Thanks for your quick responce. We have to update the patch level as per SAP Note.
Thanks,
Ramesh

Validation for Cost center for Goods issue against the cost centers

Dear Friends
In my client place we have 6 plants are defined and profit centers are defined for each plant. Hence here each plant is one profit center. Cost centers are defined plant wise.
The requirement is when the goods issued to cost center system should check the cost center is defined against the plant. ( i.e., Cost center def against the Profit Center, and Profit center equal to Plant).
Is there any provision to assign the plant to profit center or vice versa?
Please guide me how to resolve the issue.
Thanks in advance.

Hi
Please check EC01. May be it can help you. But in my view it is not possible.

Good Issue - Cost Center & Activity Code

Hi All,
I've a problem when I creating Good Issue using SDK SAP2007, I set "Cost Center" (CostingCode) dan "Activity Code" (CostingCode2).
When I run the code, and check the result in SBO2007 Good Issue, the "Cost Center" (CostingCode) dan "Activity Code" (CostingCode2) was in the "DistrRule" column not in the "Cost Center code" and "activity code" column, is this normal ? how to insert both data into the right column ?
This is my code:
   Public Function uf_SAP_GoodIssue(ByVal dtTable As DataTable, ByVal p_cardCode As String, ByVal p_Date As Date, ByVal p_priceList As Integer) As String
        Dim lngErr As Long
        Dim strMsg As String = ""
        Dim sboStockOut As SAPbobsCOM.Documents
        sboStockOut = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oInventoryGenExit)
        sboStockOut.DocDueDate = CDate(p_Date)
        sboStockOut.DocDate = CDate(p_Date)
        sboStockOut.PaymentGroupCode = Trim(p_priceList)
        sboStockOut.CardCode = Trim(p_cardCode)
        Dim i As Integer
        For i = 0 To dtTable.Rows.Count - 1
            If i <> 0 Then
                sboStockOut.Lines.Add()
            End If
            sboStockOut.Lines.AccountCode = Trim(dtTable.Rows(i)("AccountCode"))
            sboStockOut.Lines.CostingCode = Trim(dtTable.Rows(i)("CostCenter"))
            sboStockOut.Lines.CostingCode2 = Trim(dtTable.Rows(i)("ActivityCode"))
            'sboStockOut.Lines.CostingCode3 = Trim(dtTable.Rows(i)("PersonnelNo"))
            'sboStockOut.Lines. = Trim(dtTable.Rows(i)("ActivityCode"))
            sboStockOut.Lines.ItemCode = Trim(dtTable.Rows(i)("ItemCode"))
            sboStockOut.Lines.Quantity = CDbl(dtTable.Rows(i)("qty"))
            'sboStockOut.Lines.Price = 500
            sboStockOut.Lines.WarehouseCode = Trim(dtTable.Rows(i)("WarehouseCode"))
        Next
        lngErr = sboStockOut.Add
        If lngErr <> 0 Then
            Call oCompany.GetLastError(lngErr, strMsg)
            Return "Found error:" + Str(lngErr) + "," + strMsg
            'Return "Failed to issue Stock." & lngErr
        Else
            Return "" '"Stock Issued"
        End If
        Call oCompany.GetLastError(lngErr, strMsg)
        If lngErr <> 0 Then
            Return "Found error:" + Str(lngErr) + "," + strMsg
        End If
        Return ""
    End Function
Thx Before
Herfin Jodana

Hi Suraj,
Please check table COBK / COSP (with business transactions RKP1 and RKP2). Hope this may help you.
Best regards,
Dhananjai

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

Re-create billing without reversing goods issue

IHi experts,
In VOV8 we use both Order related billing & Delivery related billing. We always encounter problem when we need to amend
the Condition values in VK12 that system looks for reversing the Goods issue , then can change the price manually or thru
the new condition amounts that was changed in Vk12.
Isu2019t possible to NOT TO reverse the Goods issue but instead amend the pricing in the SO & create the invoice again. Just with
cancelling the invoice.
We do not want to go thru the hurdle of cancelling the goods issue, but just cancel the invoice amend the sales price & re-create the billing.
Please advice the setting to do this.
Thanks,
Pri

Dear Arijeet
Fortunately, the settings in VTLA exactly matches with what you have indicated. So we can conclude that the control is not in VTLA.
So let us move to other settings as under:-
My VOV8 settings are
SD document categ.::::::C
Item division:::::::::::X
Read info record::::::::X
Probability:::::::::::::100
Outpur application::::::V1
Screen sequence grp:::::AU
Incomp.proced.::::::::::11
Transaction group:::::::0
Display Range:::::::::::UALL
FCode for overv.scr:::::UER1
ProdAttr.messages:::::::A
Incomplet.messages::::::X
CndType line items:::::::EK02
Billing Plan type::::::::blank
Paymt.guarant.proc.::::::01
paymt card plan type:::::03
Checking group:::::::::::01
Propose deliv.date::::::::X
My Item Category settings are
Completion Rule:::::::::::B
Billing Relevance:::::::::A
Pricing:::::::::::::::::::X
Business Item:::::::::::::X
Sched.Line Allowed::::::::X
Wght/Vol.Relevant:::::::::X
Determine Cost::::::::::::X
Incompletion Proced.::::::20
PartnerDetermProced:::::::N
TextDetermProcedure:::::::01
Item Cat.Stats.Group::::::1
Screen Seq.Grp::::::::::::N
thanks
G. Lakshmipathi

COPA document not generated when Post Goods Issue is reversed.

Hello Friends,
WE uses Stock Transport Order in two steps for transfering Stock from one plant to another. We have defined a Condition type FRB1 to capture the Freight cost involved in the stock transfer.
When the Post goods issue is done for the Stock Transport Order. following Accounting documents are generated.
Accounting
Profit Center
COPA
Spec. Purpose Ledger
Controlling Document
Material Ledger document.
But When the Post goods issue is reversed through transaction code VL09 all the above documents are generated except for COPA document. Though in controlling document it shows the object type hit is REO i.e profitability Analysis
For further information we have mapped cost element (600150) with Value field in PA transfer structure (Direct assignment from FI and MM. Movement type used for PGI are 641 & 642.
Thank you

Dear Colleagues
I thank all those who put in thier time and efforts for possible solution for my problem. But I could resolve this issue with help from SAP.
Basically in costing based COPA the system does not post the cost of goods sold to COPA during goods issue but it is done at the time of posting the invoice since the system wants to see the revenues and the COGS values together.
Since the system posts the COGS into COPA at the time of invoice posting, you will appreciate that if this is also done during goods
issue then you will have duplicate entries in your COPA (i.e. the COGS will be doubled).
If in transaction VL01N/VL02N a costing-based line item would be posted, the costs would be double in CO-PA (the billing and goods issue). For this reason, no costing based line items will be created in the standard R/3 system for transaction VL01N/VL02N.
If for some reason you still wish to post the COGS to COPA during goods issue you have to do the same thro a modification of the system.In your case you have applied note 214381 for the same. Please note here that movement type '641' is used as an example. For other movement types you will need to code accordingly.
as per note 337488 point 2. the changes of note 214381 were not required in our case. Therefore we reverted these changes in LKEIIF01 and added the relevant coding for movement type 642 in function COPA_DOCUMENT_CHECK as per note 337488 point 2.
Looking forward for your continued support
Regards
Umesh Gothankar

IW33 : Good Issue but Cost show in Plan Cost instead of Actual Cost

Similar Messages

Maybe you are looking for