Goods & Invoice Receipts

Hi guys, I am still a newbie in SAP and I have a few questions regarding this matter which I hope you pros can help me out with.
With regards to the posting of goods receipt, does the system automatically update the delivery status of the PO and increase inventory levels for you? Are the goods then free to be used? Also after creating the goods receipt, we also create an invoice receipt right? What happens after creating the invoice? will accrued liabilities be reduced and accoutns payable created? And is the invoice amount deducted from your bank account?
Really appreciate all your help here!!!

HI,
With regards to the posting of goods receipt, does the system automatically update the delivery status of the PO and increase inventory levels for you?
Yes ,check Po historytab in PO you will get material document and in MMBE check your stock you will get stock .
Are the goods then free to be used?
If you have stock type unrestricted in MIGO then its free to be used.if it is blocked or quality stock then no ,you have to pass this stock in unrestricted
Also after creating the goods receipt, we also create an invoice receipt right?
Yes
check following link
[http://help.sap.com/saphelp_40b/helpdata/en/a8/b9921c452b11d189430000e829fbbd/content.htm]
[http://help.sap.com/saphelp_46c/helpdata/en/4f/71e70a448011d189f00000e81ddfac/content.htm]
Regards
Kailas Ugale

Similar Messages

Goods/invoice receipt clearing account

Hi,
We have open item of GL account 2010001(goods receipt/invoice receipt clearing) by FBL3N, PO:4700009743 have 0.13 outstanding which unable to be auto clear
Check our PO history for PO:4700009743 qty 50pc, under ME2N GR and IR is matching
Qty in PO
GR # 124 posting dt 27/4/10 41pc
GR # 123 posting dt 9/4/10 9pc
IR-L # 213 posting dt 25/10/11 -2pc
IR-L # 214 posting dt 25/10/11 2pc
IR-L # 211 posting dt 21/9/11 -2pc
IR-L # 212 posting dt 21/9/11 2pc
IR-L # 210 posting dt 23/12/10 -2pc
IR-L # 209 posting dt 25/06/10 41pc
IR-L # 208 posting dt 3/6/10 9pc
IR-L # 207 posting dt 3/6/10 2pc
Check at MIRO when we enter PO:4700009743, system showed 2 pc GR outstanding for invoice.
How to clear the GL account. Pls. advise.
Thanks in advance.

Yes, since there is quantity difference, please use MR11 to perform the clearing if there is no expected LIV

SRM PO error-Account assignment cannot be changed after goods/invoice receipt

Hi,
The SRM PO throws account assignment error in system (SRM7.2).
Scenario: Shopping cart is created and SRM PO is sent to backend system and GR is also posted.The purchaser is now trying to change any data like,value,currency etc and the system throws account assignment error.
The issue is system throws account assignment error for any change in other parameters but actually nothing is changed in account assignement part.This error is the backend error but not sure what can be done to stop this error.
Need guidance from experts whomever came across this type of issue.
Thank you
swathi

Hi,
We started experiencing the ME 458 error last year when SAP introduced some new edits in BAPI_PO_CHANGE.
It's triggered when the SRM account assignment (CO and FM) fields do not match the ERP PO account fields.
SRM function B470_ACCSERV_CHECKACCASSIGNMT calls ERP function BBP4X_CODINGBLOCK_CHECK_47A.
In our case this only happened for material POs, services do not have this problem.
There are numerous OSS notes out there for this problem, some are for MM and others for SRM.
Hope this helps.
Jerry

2LIS _02_SCL Invoice receipt quantity for services

Hi,
When you use service-based invoice verification (EKPO-LEBRE)
the extractor 2lis_02_scl
do not extract the good Invoice receipt quantity for each purchase order.
The field 2lis_02_ITM-AKTWE give the good GR Quantity for services but do
not ectract the good Invoice receipt quantity.
Is there any standard solution to extract properly the invoice receipt quantity
for services using line item extractor?
Thanks for your help.

Hi,
can you see that, your line item struc. has got this fields avialbe..if not check your
DS and try to keep this field into your structure from LBWE..
If you don't find in DS with std. struc. provided with LBWE, you would suppose to
enhance the DS to accommodate this field into your struc. and write a select
query on EKPO/EKKO wherever this field value is avialble for each PO and update
in your result through your user exit..
Hope it helps..if useful pls. assign points..
Cheers,
Pattan.

Configuration change from MM invoice receipt to MM goods receipt

Dear sapient
At present i have configured
Spro-
Public Sector Management-Funds Management Government-Actual and Commitment Update/Integration-General Settings-Make Other Settings
MM invoice receipt
Now as per our client requirement i have to change the configuration from MM invoice receipt to MM goods receipt.
will it create any problem if i will configure and move it to production client.
Presently budget control available during the time of PR,PO & MIRO now as per client budget control should be on PR,PO & MIGO not in MIRO.
ECC EHP6 version
Using BCS & Payment budget.
Thanks & regards
Soraj

Hi,
My question was whether you follow your budget up to payment itself, i.e. is it important for you to know budgetary-wise if the invoice was paid. In FM these values will be registered with '57' value type. If the answer is positive, then you cannot base your FM update only on GR: it has to be IR or IR/GR. Otherwise, you can base your FM update on GR.
Your second point is not clear: what do you mean by making 'payment to commitment budget'?
Regards,
Eli

2LIS_02_SCL / Getting both Posting dates of goods receipt & invoice receipt at the same time

Hi,
I have created a DSO based on the schedule lines standard extractor 2LIS_02_SCL.
The keys of this DSO are PO Number, PO Item and Schedule Line number.
I have succeed to get some key figures like PO Quantity, GR Quantity and Invoice Receipt Quantity according to the Process Key value.
Furthermore, I'd like to get too the goods receipt date (Process Key = 02,12,22).
In order to do that I wrote a small routine in the transformation rule for my target field which fill it only if the process key is 02, 12 or 22.
The problem is that it doesn't work well because of the invoice records in my source package...
Indeed when there is an invoice in my PSA for a schedule line, my target field (GR date char) is empty (for these schedule lines, last record is Invoice Receipt type). So it means my transformation rule works but is overwritten by an blank value when there is a process key 03,13 or 23 (invoice Receipt type).
Do you have a idea to solve my issue ?
Thank you very much

Hi.
You have to write start or end routines for this scenario, not the field level routine since it gets overwrite with last record values....
overall logic is:
Collect GR date per PO Num, PO Item and PO SCH. Lin num..like you have internal table with PO number, PO Item and PO Sch line number and GR date. First you have to go through source_package or result_package and fill up that temporary internal table
And than again go through source_package or result_package and READ that temporary table and fill GR date for all records of same PO sch. lines ..hope this resolves the issue.
I would prefer end routine if you have posting date in DSO or target structure
this is little bit complex, so you need ABAP skills....

Problem with the Posting Date of Goods Receipt or Invoice Receipt for PO

Hi All,
I am working on 2LIS_02_SCL - Purchasing Data (Schedule Line Level),
For our report, we should get the scheduled PO quantity,actual PO qty, Scheduled date and actual date in the report.
we are getting all these fields from the above extractor...
For a PO which is opened (Delivery Completion indicator not set) - we where getting all field as in ECC(ME23N)
But for a PO which is finished(Delivery completion indicator is set) - we where are getting actual GR qty,planned qty,planned or scheduled date at schedule line level.But we are not getting the Posting Date of Goods Receipt or Invoice Receipt for PO from history EKBE for all the schedule line.
ex:
for open PO
PO num         item num   schedule line    Planned date   actual date difference actual qty planned qty difference
450002432   10                        1              01/10/2011    02/10/2011       1 day          100             100             0
                                                 2              02/10/2011    04/10/2011       2 days        200             400            200
                                                 3              03/10/2011    07/10/2011       4 days         300            300              0
For the same PO when it is Finished or completed(Delivery completion indicator is set)
PO num         item num   schedule line    Planned date   actual date difference actual qty planned qty difference
450002432   10                        1              01/10/2011    07/10/2011       6 day          100             100             0
                                                 2              02/10/2011    07/10/2011       5 days        200             400            200
                                                                03/10/2011    07/10/2011       4 days         300            300              0
for all the schedule line its displaying the last posting date(i think its taking from EKKO table)
Is there any possibility to get that posting date history ....

You can have multiple receipts against a PO schedule line, but this extractor is not meant to go to that level of granularity. Please try to use 2lis_02_sgr instead which provides goods receipts per PO schedule line.

2lis_02_scl or 2lis_02_itm - goods receipt/invoice receipt number

Hi Gurus,
there is a field:
BUDAT - Posting date of goods receipt/invoice receipt for purchase order; Table: EKKO/EKBE
in 2lis_02_scl and 2lis_02_itm Data Sources.
As I can see, for every Purchase Order Item I get three records:
- one record for the last Invoice Receipt (with Posting date of invoice receipt in BUDAT field)
- one record for the last Goods Receipt (with Posting date of goods receipt in BUDAT field)
- one record for something else.
Do I understand it well? What is the third record?
I would to get Material Document Number, that is, Invoice Receipt Number for the first record and Goods Receipt number for the second one. How can I make it?
Regards,
Dorota

you should be able to use Movement Type field to differentiate between Invoice or Good Reciept.
Regards,
Gaurav

MIRO Invoice Receipting Workflow Solution for unreceipted Goods / Services

Hi
We wish to improve the flow of Invoice Receipting (MIRO).
Problem:
Invoices are receipted centrally at head office
Goods/Service Receipts are performed on location at site
Some Invoices are received from the Vendor before site has goods/service receipted the item.
Current configuration prevents invoice being entered when no goods receipt.
Ideally, the sites would receipt on time, but as a solution we are considering two options. I would appreciate any thoughts on whether is possible as well as guidance on implementing a solution.
OPTION A. - With Parking
1. When Head Office cannot post invoice (due to unreceipted goods/service), user parks the invoice.
2. This sends a workflow email to the site that invoice has been parked.
3. Head Office attaches a scanned image of the invoice to the parked document, so the site can review.
4. Site enters Goods/Service Receipt.
5. Work flow is triggered back to head office that a goods receipt was performed against a PO that has a parked invoice
6. Head Office posted parked invoice.
OPTION B - Without Parking
1. Configuration is changed so that Invoice Receipt can be performed when no goods/service receipt.
2. Invoice is posted and blocked for payment.
3. This sends a workflow email to the site that invoice has been blocked for payment.
4. Head Office attaches a scanned image of the invoice to the parked document, so the site can review.
5. Site enters Goods/Service Receipt.
6. Work flow is triggered back to head office that a goods receipt was performed against a PO that has a blocked invoice.
7. Head Office unblocks invoice.
Many thanks
Adrian

Hi Adrian,
Option B is very much feasible by developing the workflow for users.
OPTION B - Without Parking
1. Configuration is changed so that Invoice Receipt can be performed when no goods/service receipt.
2. Invoice is posted and blocked for payment.
3. This sends a workflow email to the site that invoice has been blocked for payment.
4. Head Office attaches a scanned image of the invoice to the parked document, so the site can review.
5. Site enters Goods/Service Receipt.
6. Work flow is triggered back to head office that a goods receipt was performed against a PO that has a blocked invoice.
7. Head Office unblocks invoice.
IF GR based IV is removed, Invoice can be done before GR. Having a GR based IV tick in PO (Mandatory) would ensure IV is raised only after the quantity is delivered.
I doubt if Scanning of invoice copy is possible in the MM system, but it would be feasible via Document Management in SAP.
Alternatively, you can have Idoc based creation for Invoice based on GR quantity.

Good receipt - invoice receipt

Hi gurus,
Do you know if exist a table that contain the link good receipt document - invoice receipt document?
If not, do you know the way to link this documents?
Thanks in advance
Regards

Hi Raffaele,
You will need to make an inner join on RSEG and MSEG tables with ref with EKPO to get your link between the GR doc. and the IR doc. with ref. to the PO.
Regards
Keshav

I want to have only display of Goods receipt and Invoice receipt indicator

I want to have only display of Goods receipt and Invoice receipt indicator in Purchase Requisition for only category D. Is it possible.? Pls help.

Hi balaji,
we cannot change the setting of item category.
in the customizing we maintain the links between the item category and account assignmnet category.
these changes has to be done only in the account assignmnet category.
by following this link
IMG...>MM...>Purchasing...>Account Assignment...>Maintain Account Assignment Categories
Hope it wud have answered ur question
Reward if useful
Aasif

LO DataSource for Goods receipt and Invoice receipt

Hi all
In LBWE, under Purchasing there are few DataSources available for Goods receipt and Invoice receipt. Is there any DataSource for both Goods receipt and Invoice receipt. What are the DataSources available for Goods receipt and Invoice receipt. Please clarify the difference.
Thanks.
Zak.

Try to use the PROCESSKEY standard infoobject (BWVORG in R3/ECC) to discriminate the good receipt from the invoice one...
An other option is create a custom generic data source with a view on EKBE table and use the EKBE-VGABE field to discrimate them.
Regards.

TOA01 Entries - Invoice Receipt vs. Goods Receipt

Using transaction MIR4 - I bring up an invoice receipt. I go to GOS and create an store business document attachment. Based on our config, SAP creates an entry into table TOA01 for BUS2081. For the follow-on accounting document SAP automatically creates the same attachment, but does not create an entry in TOA01 for BKPF.
For Goods receipt - I go to MB03 and create the same business document attachment using GOS. Entry for BUS2017 (based on config) is created in TOA01, but the attachment is not automatically created for the accounting document. I create this manually and entry is made in TOA01 for BKPF.
What is the invoice procedure doing that the goods receipt procedure is not doing? Is the accounting document for the invoice receipt linked somewhere else besides TOA01 or does it somehow know to look at the BUS2081 entry in TOA01? Can goods receipt also behave the same way - that is not create another entry in TOA01 (the BKPF entry), but look at the BUS2017 entry?

Just to follow up on the question : Can anyone tell me if the reason MIR4 stored business document also shows on the follow-on FB03 document is because it is related to some kind of config or GOS just knows that the documents are related by looking at the AWKEY etc...
I'm trying to mirror MB03 and FB03 the same way. Want to create a stored business document on MB03 and have FB03 contain the same business document attachment, without creating a BKPF entry into table TOA01.
Justing trying to fiure out if something is missing in config or if we will have to change SAP code, etc..
Thanks for anything you might can offer.

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

Invoice Receipt Warning Message Appear After Upgrade from 4.6C to ECC6

Hi Gurus,
We do upgrade from 4.6C to ECC6. And we do Invoice Verification base on Delivery (Vendor delivery number), in our business process there more than one Purchase Order has same Vendor Delivery Number while GR executed. But only one Purchase order related to Invoice verification, others PO are Free PO (no need Invoice Verification).
The problem is:
In SAP 4.6C, while execute Invoice base on Delivery (Vendor delivery), system automatic select only PO with Delivery (vendor) which related/allow invoice receipt.
In SAP ECC6, while execute Invoice base on Delivery (vendor delivery), all PO selected. So than there are warning messages appear (warning pop screen) for those PO not allow invoice Receipt (message M8035: PO item XXXXX does not allow invoice receipt), and at the end PO which allow Invoice receipt then appear for further Invoice Receipt process.
At overall, the final result SAP 4.6C and SAP ECC6 is same (only PO which allowed Invoice Receipt will processed further).
The Question are:
1. Why in ECC6 appear warning message, while in 4.6C no warning message ? Is there config to ignoring the warning message. I've try to maintain system message for M8035 (t-code: OMRM) to ignoring the pop screen, but can not created.
2. How do we make warning message dissapear (no need warning message), because if the PO's has hundred items so user need to click enter hundred times.
Thanks in advance.
Regards,
Tri Wicaksono

Hi,
could you please check whether the flag "GR-based IV" is set in the purchase orders?
If GR based-IV is ticked, then this pop-up cannot be suppressed.
If you would like to post the invoice first then GR-based IV should not be checked, otherwise this pop-up will always appear. I am afraid that this behaviour is standard.
Please, be aware that this feature is only available if you set in the Purchase Order item the 'GR-based IV' indicator:
   If the GR-IV flag is not set in the PO, then the system does not
   differentiate individual goods receipts. Please see the <f1> help
   for the field "GR-IV" in the PO item detail. Since the individual
   receipts are not differentiated, an invoice is not tied per se to
   an individual receipt and a goods receipt can be reversed despite
   an invoice receipt.
With the GR-IV flag set on in a PO, you can specify which goods
   receipt is being invoiced in an IR and which goods receipt is being
   reversed in a return. It is this correlation between goods receipts
   and invoices that enables you to specify for GR-IV PO's whether an
   item can be returned despite an invoice.
Please refer to the note :457511 Question 10.
Best regards
Erika

Goods & Invoice Receipts

Similar Messages

Maybe you are looking for