Views Table (Goods Issue & Goods Receipt)

hi experts,
i need to create a report on goods issue & goods receipt (from inventory module)...i have create a views on sql server to merge the two table IGN1 & IGE1 but to update this report i need to alter the views to update the reports...
How can i do this automatically at crystal report....
Thanks a lot...
john

Hi Jon,
Please post your query in the SAP Business One Reporting & Printing forum
[Reporting and Printing;
Regards,
Rakesh N

Similar Messages

Customisation of goods issue,goods receipt,transfer posting,stock transfer

hi,
how to do customisation of goods issue,goods receipt,tranfer posting and stock transfer.
thanks
katrina

Hi,
You can do customization in following;
SPRO > MM > Inventory Management and Physical Inventory > Goods Issue / Transfer Postings
- Create Storage Location Automatically
- Set Manual Account Assignment
- Define Screen Layout
- Maintain Copy Rules for Reference Documents
- Set Up Dynamic Availability Check
- Generate Physical Inventory Documents for Goods Movements
- Allow Negative Stocks
And SPRO > MM > Inventory Management and Physical Inventory > Goods Receipt
- Set Tolerance Limits
- Create Storage Location Automatically
- Create Purchase Order Automatically
- Set Manual Account Assignment
- Define Screen Layout
- Maintain Copy Rules for Reference Documents
- Set Dynamic Availability Check
- Set "Delivery Completed" Indicator
- Set Missing Parts Check
- For GR-Based IV, Reversal of GR Despite Invoice
- Set Expiration Date Check
- Price Differences for Subcontract Orders at Goods Receipt
- Activate Storage of Incoming Documents

Good Issue & Good Receipt

Hi Members,
I am having a requirement like this,we want to generate Good Issue & Good Receipt Document targeting a Customer or Vendor.
because we use that documents for inter division transactions. can any one help me.
thank you,
saman

Dear Saman,
See the Goods receipts and goods issue only deal with the inventory.
as you already told the you need division wise P& L account to Manage so as per me i think you have to create department as a BP and Post the Goods receipts PO and Delivery document.
You have to create the Division wise warehouse.
it help you to manage your Financial also.
Regrds
MANGESH PAGDHARE

Goods Issue & Goods Receipt

Gurus,
What standard smartform can be assigned in NACE for Goods issue & Goods receipt slip for multiple items

Hi ,
The smartforms program SAPFM07P_SMART can be used for printing goods receipt 'individual' slip using transaction MIGO.
However this program cannot be used for printing goods receipt 'collective' slip.
In order to print collective slips, please use output type WE03. The
processing routine for WE03 selects all items of a material document.In
transaction M708 or in the following customizing:
Materials Management
   -> Inventory Management and Physical Inventory
      -> Output Determination
         -> Maintain Output Determination Procedures
            Activity: Conditions: Procedure.
Please use requirement 173 for WE03 so that a collective slip will only
be printed once for a material document. If you have no requirement for
output type WE03, you will have a collective slip for each item.
Also maintain Version for printing of GR/GI slip as '3' Collective slip
in transaction OMBR for Tcode MIGO.
In the customizing for "Maintain Output Types" or M706 the standard form
is WESCHEINVERS3 should be assigned to the output type WE03 under the
"Processing routines".
Also please refer to the following useful notes for additional
information:
522591 FAQ: IM output determination
426554 Check list for output determination for goods movements
411013 Additional documentation on output determination in MM-IM
Regards,
Jana

Relationship between Goods Issue, Goods Receipt & Invoice Created

Hi Friends !
Facing issue in Prod.
In production, where goods receipt quantity reverts back to 0 in BW after when the invoice is created in SAP. This is after BW was already updated with the correct GR quantity and the delivery complete flag.
Step          DOC_NUM     DOC_ITEM     SCH_LINE    ENT_DATE    PSTNG_DAT COMPL_DEL   GI_QTY     GR_QTY
Initial load          0005051554     000300     1     01/21/2011     00/00/0000              0     0
Change 1 - Goods Issue     0005051554     000300     1     01/21/2011     00/00/0000              0     0
Change 1 - Goods Issue     0005051554     000300     1     02/14/2011     00/00/0000              53     0
Change 2 - Goods Receipt     0005051554     000300     1     02/14/2011     00/00/0000             -53     0
Change 2 - Goods Receipt     0005051554     000300     1     03/08/2011     3/8/2011        X         53     53
Change 3 - Invoice created     0005051554     000300     1     03/08/2011     3/8/2011        X        -53     -53
Change 3 - Invoice created     0005051554     000300     1     03/21/2011     3/21/2011        X         53     0
Issue : Last record change 3 should have GR_QTY = 53.
Please help how Goods Issue, Good Receipt & Invoice are linked together. Also advise what should be the expected result. How to proceed further. Thanks.
With Regards
Rekha

The values for Change 3 are as per standards.
i.e. That is how the system functions.
Ex: Your Order Qty can be 100 & you can Receipt only 50 if you want to.
Now, GR_QTY = 50.
Coming to Invoice, you can invoice even 100 if you want & then receipt the remaining 50.
If you are Invoicing the full PO quantity, Goods Receipt will be 0.
If you see the field Transfer Process or Transaction Key (BWVORG), it would be clear for you.
For PO creation the value is 1.
For a Goods Receipt the value is 2.
For an Invoice Receipt the value is 3.
Record with the different Process Keys, will signify the action taken on the PO.
When you mark 'Delivery Completed', you are telling the system that we do not require more of this particular material.
So, if you have ordered 100 Qty & receipted & invoiced only 50, & then you mark the Delivery Completion, you will not be able to receipt more of that material for this PO.
(It might sound a little confusing. If you can get some help from your MM consultant, it would be great.)

Authoriztion for Goods Issue/Goods Reciept documents

Hi..
I want to authorize the two users who create goods issue/goods reciepts. Each of them should acces only his goods issue/goods reciepts documents
I haver not found Goods issue/Goods reciept document on "Data Ownership Exceptions" window and checked "enabler ownership filteration" as well.
please let me know how to achieve this..
Regards
Akriti

Data Ownership would only apply to marketing documents. However, Goods Issue/Goods Receipt documents are not parts of marketing documents. Therefore, this function is not yet available. You may use SDK, SP or add-on to achieve your goal. Or post a DRQ here:
/community [original link is broken]
Thanks,
Gordon

SAP PP Goods Issue & goods Reciept

Pls tell me the Procedure for Goods Issue & Goods Reciepts, & commonly used movement types in PP

hi these links can be usefull
http://help.sap.com/saphelp_47x200/helpdata/en/4d/2b8e8343ad11d189410000e829fbbd/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/4d/2b8e8343ad11d189410000e829fbbd/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/4d/2b8e8343ad11d189410000e829fbbd/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/4d/2b8e8343ad11d189410000e829fbbd/frameset.htm
-ashok

Goods issue and receipt related problem

hi,
how do I configure goods issue and goods receipt tolerence according to stock in plant.
suppose client want to issue any quantity till the stock level will reach 10 qty.after that no one can issue this material from a perticular plant.same thing applicable for GR also.
plz help me to solve this .
regards
Aniruddha

Hi,
check the "PURCHASING VALUE KEYS".
MM - PURCHASING - PURCHASING VALUE KEYS- NEW ENTRIES - FIX THE LIMITS and assign this with the material in the PURCHASING view of the material master.

Goods Issue & Goods Recipt IDOC

Hi All,
Can somebody tell me any program or Function Module to create an outbound IDOC for googs issue and goods reciept. I need to create the IDOC using a Z program.
Thanks in Advance.
Thanks,
Neha.

If IDOC_OUTPUT_<message_type> function module exists , you can use that too. Else , use MASTER_IDOC_DISTRIBUTE.
Regards,
Deepthi

Goods issue and goods receipt with bar code

hi
i need to do goods issue and goods receipt using bar code
using se 73 i craeted a bar code
iwill print this bar code on external system
after printing same one will be stikked to the respective bins
i need to trigger goods issue and goods recipt by reading
barcode scanner
plz suggest how to achive this
regards
sasikanth
vst

One of the ways of triggering transactions in SAP using external systems is IDOCs
When the barcode scanner scans the barcode of the material, you can trigger the IDOC from that system which will send the material barcode, number of units, goods issue/goods receipt etc to your SAP system. Once that inbound IDOC is received in SAP, SAP will trigger the goods issue or goods receipt based on the kind of transaction.
If you can give the idea of IDOCs to your technical guy, he should be able to enable the solution. You may have to configure an IDOC in your SAP system, using teh standard IDOC type/message types meant for GI/GR
Hope this helps you

How do load system form matrix -Inventory-Goods Issue through SDK UI &DI

While I am accessing system form matrix -Inventory Goods Issue/ Goods Receipt, the matrix object is not accessible.
Error is coming stating "Item 13 is invalid, where 13 is item uid for matrix.
So,How do load system form matrix -Inventory-Goods Issue(FORM 720/-720) through SDK UI &DIAPI.
Form Type: -720
How to get reference of System form matrix object -Inventory-GoodsIssue.
Some thing similar to CopyFrom functionality for -Inventory-Goods Issue.
Currently my client requirement is as follows.
I created a UDF ((U_ILC) Incoming Log Challan) for marketing documents. And, this field is added in the header level of Goods Reciept, Goods Issue documents.
1. Through Inventory->Goods Receipt (ILCNo.10), items are received. Assume, M00001, M00002 are the items received with qty, price, whse, account values.
2. Through Inventory->Goods Issue, item should be issued. In this Goods Issue Form, after entering U_ILC value as 10, pressing Tab, the GoodsIssue matrix should be loaded with the values of GoodsReceipt(IGN1 for U_ILC:10) document i.e. M00001,M00002 along with the same values as in GoodsReceipt of ILC:10.
The code is as follows:
If (( ( pVal.FormType = "-720" or pVal.FormType = 720) And pVal.EventType <> SAPbouiCOM.BoEventTypes.et_FORM_UNLOAD) And (pVal.Before_Action = False)) Then
            '// get the event sending form
            oForm = SBO_Application.Forms.GetFormByTypeAndCount(pVal.FormType, pVal.FormTypeCount)
            If pVal.ItemUID = "U_ILCNo" And pVal.EventType = SAPbouiCOM.BoEventTypes.et_LOST_FOCUS And pVal.Before_Action = False Then
                SBO_Application.MessageBox("ILC No. Lost Focus")
                oMatrix = oForm.Items.Item("13").Specific
                oColumn = oForm.Columns.Item("1")
                oEditItmCode = oColumn.Cells.Item(1).Specific
                oEditItmCode.Value = "07215090x606"
                oItem = oForm.Items.Item("U_ILCNo")
                oEdit = oItem.Specific
                SBO_Application.MessageBox(oEdit.String)
            End If
        End If
3. The code
oMatrix = oForm.Items.Item("13").Specific
is raising error. I have used Event Logger and breakpoints to see where the code is halting.
Help me, how to access the matrix of Goods Receipt/ Goods Issue and load based on the existing data.
Thanks in advance

HI
If your code is in the SBO_Application_ItemEvent then try using this line
oForm = SBO_Application.Forms.Item(strFormUID)
instead of
oForm = SBO_Application.Forms.GetFormByTypeAndCount(pVal.FormType, pVal.FormTypeCount)

Goods receipt Quanity and Goods Issue Quantity tables

Hi experts,
Can u plz let me know in which tables we can find the Goods receipt Quanity and Goods Issue Quantity
if not how to get the values of these, neccessary for open PO report
Thanks in advance.

Hello,
You can get the GR/ GI quantity for a PO from EKBE table.
GR
EKBE-EBELN = EKPO-EBELN
EKBE-EBELP = EKPO-EBELP
EKBE-VGABE = '1'
EKBE-BEWTP = 'E'
GI
EKBE-EBELN = EKPO-EBELN
EKBE-EBELP = EKPO-EBELP
EKBE-VGABE = '6'
EKBE-BEWTP = 'U'
The qty are present in EkBE-MENGE
BR,
Suhas
Edited by: Suhas Saha on Jan 29, 2009 4:52 PM

Last Goods Issue Date & Last Goods Receipt Date

Hi ,
I would like to know in which table (and fields) I can find the "<b>Last Goods Issue Date</b> " & "<b>Last Goods Receipt Date</b>" based on Material Code, Plant and Storage location.I have to prepare a existing stock report for slow moving material.
Thanks.

Hi,
Check table LIKP deliver header and LIPS deliver Item
Regards,
Prashant

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

Last goods receipt, last goods issue and last purchase order

Hi Experts!!
is there any table/info structure where I have the last goods receipt material document number, last goods issue material document number and last purchase order number? I want to extract this information to Business Warehouse.
Best regards

Are you looking for a report similar to MB51?
If you put little more detail, i might be able to help. I don't know much about info structures but i can tell you the SAP tables.
All Movement Details are in the below tables.
MKPF- Material Document Header,
MSEG - Material Document Detail -( you can put your material, plant for selection)
Last PO - you can get it from Info-record (EINE- EBELN, EINE-EBELP).
Thanks,
Shekhar Ramineni

Views Table (Goods Issue & Goods Receipt)

Similar Messages

Maybe you are looking for