Auto goods issue manufatured parts (mvt 281 Q)
hello all
i have approximatley 60 top level parts on my project that are set to be made in house they include thousands of materials under them, purchased and manufactured
once the top level has had all its parts issued and it is booked into stock i wish for it to automatically issue to the project is this possible????
currently backflush is set on the project and i confirm the activity and it issues but this is a task i dont think i need to perform is i
can get the auto issue working
thank you in advance
richard
Edited by: Riche rich on Feb 16, 2012 11:49 AM
You can use Manufacturer Part number functionality of SAP
you need to create manufacturer's part number and then assign it to your internalnumber
in this way you can assign your single internal number to multiple manufacturer (supplier number)
regards
Anish
Similar Messages
-
Auto Goods Issue not taking place
Hii All
I hv Maintained backflush indictor in work center and in MRP2 view it is maintained as Workcenter
decides whether to backfluch .
But the auto goods issue is not taking place when the production order is saved and confirmed.
The stock remains the same ..
Can anybody tell the reason for that
Regds
RakeshHi Rakesh,
what is the control key u have maintained in Routing?
if u r using Control key PP01 - Routing/Ref. op. set - internal proc., then after Production Order confirmation u have to do MB31- Goods Receipt for Order, with movement type 101.
If u r using PP03 Routing - in-house prod. auto. goods rct, then it accepts only single operation in a Routing (or) if u r having say more than one operations in a routing, then u have to give PP03 control key for the last operation.
I think u got it...
revert back if u have doubts.
Thanks & Regards,
Santosh -
Whether it is possible to make auto goods issue below safety stock level
Hi SAP Gurus,
I am implementing MRP for generating stock transfer Planned orders from a Main Mother Plant to different Plants. We have defined a Safety stock level for materials at main Plant level.
There is a auto program available for generating auto goods issue against Purchase orders.
System picks up Qty as long as unrestricted stock exists for the material during auto goods issue.
System dont pick up any Qty below safety stock level (manual goods issue works below safety stock level).
We are defining safety stock to meet sudden requirements and have time for new procurement.
But it should allow us to do auto goods issue below safety stock level.
Whether this is possible and what need to be done ?
Thanks and Regards,
R.Velmurugan.Hi Velmurugan,
I don't think auto GR is a problem from safety stock. Auto Gr can be done by two ways.
1. Control key and assigning the control key in operation(Preferably in last operation)
2. In production scheduling profile you can do it. You have to assign the production scheduling profile in material master work scheduling view.
Regards,
Krishnendu. -
Internal Order through Goods auto Goods Issue
Hi friends
i create PO with acc.*** F and commitment item ,order(Internal oder) .
vendor supplies goods i done GR through 101 . while i done GR goods automatically ISSUE to Internal Order .(contracter)
Po qty 100
GR qty 100
Auto GI to Internal Order (Contracter) - 100
now contracter return some qty - 10 to Company.
how this 10 qty comes to SAP system and in company stockif u reverse or cancel GR thru MIGO; does the system automatically reverse goods issue?
Hi sachin
S. when i reverse in MIGO (101) goods reverse to GI also. but the qty goes to open order stock . i want tht stock comes to in my company stock .
how i ll come -
Goods Issue for Movement Type 281
Hi,
Can anyone suggest me how to use MB_CREATE_GOODS_MOVEMENT to post goods for Mvmt Type 281.
Please give me Sample data as i'm getting errors with data.
Thanks in Advance,
Anjani.Hi Srinivas,
Thanks for the answer. It helped in solving the problem.
thanks,
Anjani. -
Hi
how to take report of sto withou delivery,i created po doc type ub for 6 qty .goods issue given 351 mvt type 1 qty
balance 5qty avl,in me2m i tried select enter material scope of list alv,doc type ub,selection parameters wa351 execute report shows that issue 1qty in 351 mvt type poh/release document as a graphical view. if i double that graphical view then only com issue qty comes, all other things comes good,users to take report in excel sheet,that time showing in excel poh/release document qty not comes,plz suggest,
Regards
SamHi,
You can tell the user to run ME23N AND go to the header and select the status tab and the system will show the history as far as open,delivered and closed.
Or you can run ME2N for the material or MMBE for the material to see the entire history of the material.
Silas -
STO Post goods issue reversal using vl09 not happening.
hi
user has done following cycle
1.ME21N-PO document type UB and Item cat I.
2.VL10B- Outbound delivery
3.VL06G-goods issue using automatic MVT 647 and 101)
4.VF01-Performa Invoice(billing Type JEX)
5.J1IIN- Excise invoice.
In billing base price is missing because of that all duties and net price zero.now user wants to cancel entire cycle. he has done excise cancellation using J1IH. we are not able to reverse billing using VF11, we are not able to PGI reversal using Vl09. it giving error "No dat available for your selection".
Note: is it problem of JEX because we have not assigned cancell billing type and doc pric procedure to JEX?
any solution for the above issue.the optional solution can be as following steps:
1) create the bin manually with ls01n: storage type 904, bin name is the delivery number,
2) reverse with vl09 and a material doc will be created.
3) check the bin stock with ls24, you will see negative stock in 904.
4) create TO to offset this negative qty with lt06 with above mentioned material doc. this TO's source bin is just the one in regular storage type.
5) confirm TO
6) don't forget to delete the bin created in step 1, this is because it is created manually but not dynamic bin that will dissapear automatically.
pls reward if helpful. -
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
9900163939hi 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 -
WM goods issue TO creation and TO confirmation understanding.
Dear all,
i am using WM in context of PP transactions.
my transaction flow is as below
CO01- PRODUCTION ORDER CREATION.
CO15- ORDER CONFIRMATION (AUTO GOODS ISSUE AND GR- SLOC- 00014 wm managed) IM is executing correctly for goods movemnt.
LB12- TO CREATION.
REQURIED help in understanding below scenario.
stock is available in storage bin 500 ea
created TO for both 101 and 261 TR
production order qnty 100 ea
TO created and if viewed stock in LS26 it showing available stock is zero, once i confirm TO remaining stock of 400 is shown.
my query is instead of 0 why it is not showing 400 before confirmation. 500 ea is shown in putaway after confirmation remaining stock is available
is any customizing remaining for same.Hi manish,
pls find below details,
Scrn-1-toce- LS26 Stock available in sloc- 0015 - 49,984
Putaway stock – 100,491
SCRN-2 TR number generated for GR and GI.
TO created with LB12
SCRN-3- .NOW before confirmation TO (LT12)checking goods issue stock it is ‘0’and
entire stock is moved to putaway stock.
Stock available in sloc- 0015 - 0
Increased putaway stock - 150,455.
Due to this next TO is not created for 261 as stock is zero. -
Goods Issue print for Pull list
All,
WHile doing Goods Issue by 201 mvt type one print format is coming .
So we are designing a format for that .
This print is coming thru output type WA03 .
Also while doing pull list (MF60) , one print document is coming .
Business wants a different format for that .
And for both transactions ,output type is WA03 .
How to tackle this situation ?
regardsHello Sandeep,
I think this query is already addressed. Follow the steps in this post, if you still have problem write to this forum.
Goods Issue Print
Hope this helps.
Regards
Arif Mansuri -
Hi
There is another system for order confirmation. When user confirms the order, auto goods issue, confirmation and auto GR , all happens in Sap through IDOC in the background.
Issue :- For one order and one material system has created only 1 line item in IDOC for GI with movement type 261. So no problem. But in the material document, system has generated one more line item for this particular material and has done the goods issue with a different qty. This has happened with this material 2 times wrt same order on 2 different days, same time and with different qty. So total GI qty is more than reqd. I just surprised to see this.
No1 has done manually, all are thru a scheduled background user. same day,same time.
Any1 has experienced such a strange issue?
Thanksif so,
you would check out that particular material and order.
run MM04 and look at last changes first, then look at order and confirmation (focus on details, you may see the reason).
you would also run COGI (just in case for that particular order) and ST22 (if you had any code termination for that time)
good luck! -
Hi,
When i enter Goods Issue with Tcode : MB1A betwen 2 plants i have two FI Docs created automatically, i want to know when we maintain the accounts used in these docs.
Please what's the path IMG or Tcode to do that?
Regards.Hi,
GBB is for Offsetting entry for inventory posting.
U can assign ur GL accounts to that particular valuation class for such material u r making goods issue.
How does the system find the relevant accounts?
When entering the goods movement, the user does not have to enter a G/L account, since the R/3 System automatically finds the accounts to which postings are to be made using the following data:
o Chart of accounts of the company code
If the user enters a company code or a plant when entering a transaction, the R/3 System determines the chart of accounts, which is valid for the company code. You must define the automatic account determination individually for each chart of accounts.
o Valuation grouping code of the valuation area
If the automatic account determination within a chart of accounts is to run differently for certain company codes or plants (valuation areas), assign different valuation grouping codes to these valuation areas.
You must define the automatic account determination individually for every valuation grouping code within a chart of accounts. It applies to all valuation areas which are assigned to this valuation grouping code.
If the user enters a company code or a plant when entering a transaction, the system determines the valuation area and the valuation grouping code.
o Transaction/event key (internal processing key)
Posting transactions are predefined for those inventory management and invoice verification transactions relevant to accounting.
Posting records, which are generalized in the value string, are assigned to each relevant movement type in inventory management and each transaction in invoice verification. These contain keys for the relevant posting transaction (for example, inventory posting and consumption posting) instead of actual G/L account numbers.
You do not have to define these transaction keys, they are determined automatically from the transaction (invoice verification) or the movement type (inventory management). All you have to do is
assign the relevant G/L account to each posting transaction.
o Account grouping (only for offsetting entries, consignment liabilities, and price differences)
Since the posting transaction "Offsetting entry for inventory posting" is used for different transactions (for example, goods issue, scrapping, physical inventory), which are assigned to different accounts (for example, consumption account, scrapping, expense/income from inventory differences), it is necessary to divide the posting transaction according to a further key: account grouping code.
An account grouping is assigned to each movement type in inventory management which uses the posting transaction "Offsetting entry for inventory posting". Under the posting transaction "Offsetting entry for inventory posting", you must assign G/L accounts for every account grouping,
that is, assign G/L accounts.
If you wish to post price differences to different price difference accounts in the case of goods receipts for purchase orders, goods receipts for orders, or other movements, you can define different account grouping codes for the transaction key. Using the account grouping, you can also have different accounts for consignment liabilities and pipeline liabilities.
o Valuation class of material or (in case of split valuation) the valuation type
The valuation class allows you to define automatic account determination that is dependent on the material. for example: you post a goods receipt of a raw material to a different stock account than if the goods receipt were for trading goods, even though the user enters the same transaction for both materials.
You can achieve this by assigning different valuation classes to the materials and by assigning different G/L accounts to the posting transaction for every valuation class. If you do not want to differentiate according to valuation classes you do not have to maintain a valuation class for a transaction.
Offsetting entry for stock posting (GBB)
Offsetting entries for stock postings are used in Inventory
Management. They are dependent on the account grouping to which each
movement type is assigned. The following account groupings are
defined in the standard system:
- AUA: for order settlement
- AUF: for goods receipts for orders (without account
assignment)
and for order settlement if AUA is not maintained
- AUI: Subsequent adjustment of actual price from cost center
directly
to material (with account assignment)
- BSA: for initial entry of stock balances
- INV: for expenditure/income from inventory differences
- VAX: for goods issues for sales orders without
account assignment object (the account is not a cost
element)
- VAY: for goods issues for sales orders with
account assignment object (account is a cost element)
- VBO: for consumption from stock of material provided to
vendor
- VBR: for internal goods issues (for example, for cost
center)
- VKA: for sales order account assignment
(for example, for individual purchase order)
- VKP: for project account assignment (for example, for
individual PO)
- VNG: for scrapping/destruction
- VQP: for sample withdrawals without account assignment
- VQY: for sample withdrawals with account assignment
- ZOB: for goods receipts without purchase orders (mvt type
501)
- ZOF: for goods receipts without production orders
(mvt types 521 and 531)
You can also define your own account groupings. If you intend to
post goods issues for cost centers (mvt type 201) and goods issues
for orders (mvt type 261) to separate consumption accounts, you can
assign the account grouping ZZZ to movement type 201 and account
grouping YYY to movement type 261.
I hope u got the explanation what u wanted.
Assign points if useful
Regards,
Jigar -
Confirmation Resrtiction before GOODS ISSUE
Greetings........
How to restrict the Partial or final confirmation Before issueing Goods To Production order.Dear,
Use backflush indicator in the master the creation (ie.,Material master, routings, workcenter). So that.. u an create order then material auto good issues to order when confirmation and receipts
And also you can control this with Backflushing and Termination if there is any error in Goods Movements with OPK4, so that it will ensure at every time GI will be posted along with the Confrimation.
Or use the Use user exit EXIT_SAPMM07M_001
Please refer this thread.
default quantity of confirmation(co11) should allowed in goods movements mb
Regards,
R.Brahmankar -
Hi Experts,
Is there any function module to perform the automatic goods issue for a particular planned order or prod order?
Client dont want to use any transaction hence they scan the planned order and they want auto goods issue as per BOM planned qty.
Help me out.
Thanks
Regards
TAJUDDINDear,
Then back flush is the best option for auto good issue.
Or try BAPI_GOODSMVT_CREATE
Regards,
R.Brahmankar -
Goods issue against reservation with interchangeable part using MB11/MIGO
Hi
Do anyone know how to make a goods issue against reservation with interchangeable part using MB11/MIGO.
Meaning reservation is made with Part A, goods issue is make with Part B (interchangeable to part A).
Enhancement pack 4 is having some issue with MB1A, we are attempting to do a work around with MB11 / MIGO.
Please assist.
Thanks!!
Regards,
ClariceYou can view report from MB25 ,it will gives you reservation list with reference network number.
Select option in MIIGO as GI > Reservation > Mvt.281. or you can make the entry from MB1A with Mvt .type-281
Regards,
Sandesh Sawant
Maybe you are looking for
-
Hello, So this is annoying me to no end because I just spent $25 to sign up for iTunes Match and so far its wasted my time and given me nothing but a massive headache. This is obviously a major bug on the SERVICE END, not mine. Starting with an empty
-
After having trouble getting back onto my IPAD Mini this afternoon, because I apparently did not have what was required a passcode ?? I was putting in my previously decided on password. I had to use my CHROME machine to communicate with Apple, and b
-
Problem with creating Photo Book
In the past when creating an iPhoto book if I dropped a Portrait photo into a Landscape frame, the frame changed to portrait. This option seems to be turned off now in the new version of iPhoto. I find I need to often change the shape of the frame an
-
hai friends, I am new bw, plz clarify my doubt. In the cube 0SD_C04 there key figures loading date (0loaddatek) and actual goods issue (0act_gi_dtk). But I don't find these kefigures in any infosources (2lis_12_*) then how these fields get updated in
-
Can't install Adobe Air Applications!
Installed Adobe Air without problems - but when I try to install any application it will restart my computer before completing the install. Usually gets to the... "Would you like to install desktop icons etc." then I click 'OK' and it reboots my pc.