Collective goods issue

Hi
Any collective goods issue for production order is there in standard SAP?
I checked in MB1A, there i can enter only 5 production order using with reference to production order. Beyond that no option was there.
So any option is there. pls.

Hi,
You can do it by T.code MB26.
Regards,
Dhaval

Similar Messages

Collective goods issue in production

Hello All,
We want to do a collective goods issue in production. Is there a chance in SAP that we can do a goods issue by supply area or MRP controller. We don't want to enter manually the group of production orders in MB1A or don't want to do backflush. Is there any way, please advice.

Dear,
In standard SAP are we issue the good In MB1A (261 Mov type) with reference to order and which having the reservation.
The dependent requirements are planned as per BOM explosion. Item materials are issued against header material to complete header material production.
Goods issue takes place against the production order at the start of the header material prod order.
But MB26 will allow you to issue for serval orders,
Hope clear to you.
Regards,
R.Brahmankar

Goods Issue Print

All,
1.For MB1A (201 Mvt type ) , how to set the print put while saving ?
Can anyone help me regarding this .?
2.Please tell me whether I have to use WA01 or WA03 ?
3. Wat is the difference between WA01 and WA03 ?
regards

Hi
1. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WA01, WA02 and WA03, set the dispatch time as 4. If it is 4, it is printed immediately on saving MIGO. If it is 3, you have to print it using MB90.
2.a. WA01 means Tr type WA and version 1: This is used for printing Individual Goods Issue slips i.e. 1 GI slip for each item of the MIGO.
b. WA02 means Tr type WA and version 2: This is used for printing Individual Goods Issue slips wth Inspection texts if any i.e. 1 GI slip for each item of the MIGO.
c. WA03 means Tr type WA and version 3: This is used for printing Collective Goods Issue slips i.e. 1 GI slip for all items of the MIGO.
Hope this clarifies. If it still does not work, pls check the following settings:
1. Maintain the Printer Name in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
2. Ensure that in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Item Print Indicator, 1 stands for Matl Doc print out
3. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Print Version, maintain Print Version 2 for MIGO_GI and MB1A
4. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Maintain Pr indicator for GI docs, for mvt type 201 maintain Print indicator as 1.
5. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WA01, WA02 and WA03, ensure the foll:
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Tr medium is 1
b. Print Parameter is 7
6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Pr Det by Pl/StoLoc, maintain the Output device for all your Plants and Sto Locations for WA01, WA02 and WA03.
7. Go to MN21, for Tr Type WA, Print Version 3, maintain Print Item as 1.
Now the settings are ready for Printing GR doc
8. While doing MIGO, ensure that in General Tab, you get "3 Collective Slip" beside the Print Indicator and you tick mark the field.
9. Now depending on the setting in 5a, the Matl doc is printed. If it is 3, you have to print it using MB90. If it is 4, it is printed immediately.
Hope this clarifies.
Thanks

Goods Issue VL06G

Hi Gurus,
I have an issue regarding goods issue posting.
I mean I want to try the collective goods issue posting through VL06G using the Shipment number.
If I do that all the deliveries in the shipment should get Post goods issued. When I give the Shipment number, it says No Deliveries can be found.
But when I check in customization it's taking one the pre-configured SAP Standard variants which have the statuses given earlier and they are completely masked cannot be changed. I think those pre-configured varaints are erring me out.
If anybody have used VL06G to post goods Issue using the Shipment number, Please let me know.
Thank you,
Sharath Marripelli.

Hi Nikhil,
It's working now. May be the Shipments in the deliveries are not setup coreectly.
Now it's working fine.
Nikhil, one quick questions.
I am trying to setup CMR1 bill of lading output type.
It's erring me out saying that
"Shipment 0000001412 contains no legs relevant for printing"
I have been through OSS NOTE: 136345.
checked all, everything is setup right.
My shipment determines "Direct Leg" everytime, its' default.
But I donno where to make these legs relevant for printing.
Please let me know, if the issue is familiar.
Thank you,
Sharath Marripelli.

Collective Invoice - Actual Goods Issue date

Hi Friends,
Collective invoice topic has been discussed many times but I didn't find exact solution to solve my issue.
From sap help and few other threads it is learnt that Billing type, Billing date, Payer, Billing unit, Terms of payment, Incoterms, Letter of credit should be same to have collective invoice. During my tests it is understood that apart from those Actual Goods Issue date (Post Goods Issue) date should be same to have collective invoice for different sales orders/deliveries. In my tests SAP didn't consider Billing date but it did consider Actual GI date. In other words, even the billing date and other requirements are same invoice split happend due to different Actual GI date. However collective invoice created even though the billing date is different but Actual GI date is same.
My user creates one sales order and one delivery for a customer once in a week (so 4 orders/deliveries in a month) and creates Invoice by end of the month with collective invoice. So based on the above tests I can ask the user to create sales orders, deliveries every week but perform Post Goods Issue month end and then create invoice so that collective invoice can be done. But the issue is they want to do the Post Goods Issue every week because the stock levels should reduce on weekly basis. So how can we create collective invoice even though the Post Goods Issue is done weekly (so Actual GI date will be different)
Any idea? Please let me know if further information required.
Thank you

Hi,
You may consider writing a routine under copying requirements so that invoice is not split even if the Actual GI date is different.
Consider the following [thread|Collective billing; for more info.
Regards,
Amit

EXIT or BADI for Post Goods Issue

Hello Experts,
I need help in finding a USER EXIT, or BADI to change the contents of MSEG at PGI moment in VL02N.
I'm using version 4.6c.
When I click at Post Goods Issue, I need to insert the customer number at MSEG for certain documents that the standard does not use this field.
Can anyone PLEASE help?
Will reward points!
Thanks a lot and regards,
Fernanda

Hi
Enhancement/ Business Add-in            Description
Enhancement
V02V0004
User Exit for Staging Area Determination (Item)
V02V0003
User exit for gate + artl staging area determination (headr)
V02V0002
User exit for storage location determination
V02V0001
Sales area determination for stock transport order
VMDE0004
Shipping Interface: Message SDPACK (Packing, Inbound)
VMDE0003
Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0002
Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0001
Shipping Interface: Error Handling - Inbound IDoc
V53W0001
User exits for creating picking waves
V53C0002
W&S: RWE enhancement - shipping material type/time slot
V53C0001
Rough workload calculation in time per item
V50S0001
User Exits for Delivery Processing
V50R0004
Calculation of Stock for POs for Shipping Due Date List
V50R0002
Collective processing for delivery creation
V50R0001
Collective processing for delivery creation
V50Q0001
Delivery Monitor: User Exits for Filling Display Fields
V50PSTAT
Delivery: Item Status Calculation
Business Add-in
DELIVERY_PUBLISH
Announcement of delivery data during database update
If it is helpful rewards points
Regards
Pratap.M

Goods Issue error - batches not defined for delivery item

Hi,
We are getting a Goods Issue error u201CThe batches are not defined for delivery item 000010u201D.   We are only getting this error for a material that is being shipped against a particular third party sales scheduling agreement. We went live in 2007 and we had no issues, but when we had to create a new Sched Agreement this year, for third party sales, we started to get this error. However, if we re-activate the old scheduling agreement we do not get the error. We have a batch job that executes the following steps:
1.     VL06IG (collective goods receipt)
2.     VL10 (collective delivery)
3.     VL06O (collective GI)
We have compared the 2 scheduling agreements and see no difference. We are assuming it has something to do with how the scheduling agreement was setup, but are not sure. Any suggestions on how to correct this problem would be much appreciated.
Thanks in advance,
Helen

Dear Murali,
The material has not changed at all. I'm not sure what you mean by maintaining batches while receipt of the material.
If I re-open the old scheduling agreement, we do not get the error message. However, as soon as we use the new SD scheduling agreement, we get the error. We are using the same material master on both scheduling agreements.
Thanks,
Helen

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

Post Goods Issue (VL06O) - taking more time approximate 30 to 45 minutes

Dear Sir,
While doing post goods issue against delivery document system is taking lots of time, this issue is very very urgent can any one resolved or provide suitable solution for solving this issue.
We creates every day approximate 160 sales order / delivery and goods issue against the same by using transaction code VL06O system is taking more time for PGI.
Kindly provide suitable solution for the same.
Regards,
Vijay Sanguri

Hi
See Note 113048 - Collective note on delivery monitor and search notes related with performance.
Do a trace with tcode ST05 (look for help from a basis consultant) and search the bottleneck. Search possible sources of performance problems in userexits, enhancements and so on.
I hope this helps you
Regards
Eduardo

Change Moving Average Price when Post Goods issue posted from VL02N

Hi all,
Please help me to find USER EXIT / BADI or Enhancement to change Price - MSEG-DMBTR
when Post Goods Issue posted from transaction VL02N.
Thanks in advance,
Mila.

Hi,
Check these Enhancemnts...
Exit Name           Description
V02V0001            Sales area determination for stock transport order
V02V0002            User exit for storage location determination
V02V0003            User exit for gate + matl staging area determination (headr)
V02V0004            User Exit for Staging Area Determination (Item)
V50PSTAT            Delivery: Item Status Calculation
V50Q0001            Delivery Monitor: User Exits for Filling Display Fields
V50R0001            Collective processing for delivery creation
V50R0002            Collective processing for delivery creation
V50R0004            Calculation of Stock for POs for Shipping Due Date List
V50S0001            User Exits for Delivery Processing
V53C0001            Rough workload calculation in time per item
V53C0002            W&S: RWE enhancement - shipping material type/time slot
V53W0001            User exits for creating picking waves
VMDE0001            Shipping Interface: Error Handling - Inbound IDoc
VMDE0002            Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003            Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004            Shipping Interface: Message SDPACK (Packing, Inbound)
Badi Name            Description
DELIVERY_ADDR_SAP    Determine Time-Dependent Delivery Address in Delivery
DELIVERY_PUBLISH     Returns BAdI Implementation: Automatic GR Posting T 2
DELIVERY_PUBLISH     Updating of Delivery in Purchase Order
DELIVERY_PUBLISH     AIP: Delivery Confirmation for Sales Order
Regards
Raghu

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

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

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

BADIs used in VL01n transaction ( for post Goods issue)

Hi,
The requirement I have is to substitute the transaction type field (BSEG-BEWAR)based on the mapping to movement types.
The first step, in case of a Goods issue is to look into table LIPS, field BWART to get the movement type. However, since the outbound delivery has not been created, I cannot query this table on the basis of VBELN.
Is there any BADI which will help me get the value BWART(movement type)?
Any help/documentation will be greatly appreciated.

Hi,
VL01N has one BAdi called "DELIVERY_PUBLISH".
Why don't you use User exit for solving your problem?
Following are the user exits availble for the transaction:
V53W0001 User exits for creating picking waves
V53C0002 W&S: RWE enhancement - shipping material type/time slot
V53C0001 Rough workload calculation in time per item
V50S0001 User Exits for Delivery Processing
V50R0004 Calculation of Stock for POs for Shipping Due Date List
V50R0002 Collective processing for delivery creation
V50R0001 Collective processing for delivery creation
V50Q0001 Delivery Monitor: User Exits for Filling Display Fields
V50PSTAT Delivery: Item Status Calculation
V02V0004 User Exit for Staging Area Determination (Item)
V02V0003 User exit for gate + matl staging area determination (headr)
V02V0002 User exit for storage location determination
V02V0001 Sales area determination for stock transport order
VMDE0004 Shipping Interface: Message SDPACK (Packing, Inbound)
VMDE0003 Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0002 Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0001 Shipping Interface: Error Handling - Inbound IDoc
Regards,
Dharitree

Goods issue availability check

Dear All,
we are facing one problem in SAP.
My scenerio is i am procurring one Raw Material say Eg - RM1 - 100 kg Batch No - ABC01 on 12.08.2010 so my stock will be availble only 12.08.2010 only, but when i am doing goods issue to order / cost centre same RM1 Batch ABC01 01 .08.2010 system allowing me to post the stock. Actually on that day 01.08.2010 there is no stock in this material/batch .
I want system should not allow me to if stock is not available on that day. how to do this one
Regards,
s.sakthivel

Dear ,
If the stock is not avilable ( Check in MMBE) , When you trigger MIGO with by marking OK and posting dates in 01.08.2010 , hit the Check Button , it should promt you with the following messeage : Deficit of SL Unrestricted-use XX EA : SAMPLE 001 0001 " like this .It means , there is insuffiecent stock .It will not allow you to carry out Goods Issue against PO as long as there is insuffiecent stock .
1.As per your problem i believe you have activated the negative stocks in plant and all storge location.
It can done by de-activating the negative stocks in Inventory management.
Check in the transaction code for this OMJ1.
Follow the IMG path SPRO->MM->Inventory Management->Goods Issue / Transfer Postings->Allow Negative Stocks.Un-checked if you have marked it .
2.Did you keep Individual and Collective Indicator -2 in MRP4 view .
3.Try User exit : User Exit for MIGO (goods receipt and goods issue)
User Exit for After SAVE in MIGO..
Regards
JH

Reversal or cancellation of a Goods Issue document (transaction VL09) ,

Hi Experts,
I am trying to look for a user exit that will be triggered after user confirm the reversal or cancellation of a Goods Issue document (transaction VL09).
I want to put validation while cancelling document if movement type is 101 it should not cancelled.
any solution please reply.
Thanks & Regards,
Yogesh

Check this thread ..
User Exit During Goods Issue Cancellation/Reversal
Transaction Code - VL09 Cancel Goods Issue for Delivery Note
Exit Name Description
V02V0001 Sales area determination for stock transport order
V02V0002 User exit for storage location determination
V02V0003 User exit for gate + matl staging area determination (headr)
V02V0004 User Exit for Staging Area Determination (Item)
V50PSTAT Delivery: Item Status Calculation
V50Q0001 Delivery Monitor: User Exits for Filling Display Fields
V50R0001 Collective processing for delivery creation
V50R0002 Collective processing for delivery creation
V50R0004 Calculation of Stock for POs for Shipping Due Date List
V50S0001 User Exits for Delivery Processing
V53C0001 Rough workload calculation in time per item
V53C0002 W&S: RWE enhancement - shipping material type/time slot
V53W0001 User exits for creating picking waves
VMDE0001 Shipping Interface: Error Handling - Inbound IDoc
VMDE0002 Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003 Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004 Shipping Interface: Message SDPACK (Packing, Inbound)
USER EXIT
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.sap-img.com/ab038.htm
http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
Rewards if useful.

Goods issue print program

Hi friends
Can someone tell me what is the print program for smartforms /SMB40/MMGI3_A and /SMB40/MMGI3_L? I'm trying to print goods issue slips(collective) using transaction code MIGO and application ME .we are on ECC 6
Helpful answers will be rewarded with point.
Thanks a lot
-Nash

hi john,
to know the print program name u just do like this,
go to T.code samrtforms,
provide your smartfrom name ex:SMB40/MMGI3_L,
display,
at the menu select environment tab,
it shows function module name,
copy that and go to T.code se37,
there u can paste your smartfroms function module,
and slelect where used list at the tool bar,
in the pop up enable programs check box alone,
and enter,
now you can see the driver program for that smartforms.
regards,
seshu.

Collective goods issue

Similar Messages

Maybe you are looking for