Goods Issues has Fund Data

Hi Friends,
      My company want to design for Goods Receive (GR) has Fund data (Fund Management Module). So when I receive goods
from vendor the  system assign Fund data from PR/PO to post FI Document (Financial Accounting ModuleI) but when I issues
goods from Sales (Movement Type 251/252) or Cost Center (Movement Type 201/202) fund data cannot assign to post FI
Document. How should I do that the system has fund data when goods issues. Pls. help me.
Thanks in advance
Pland12

Dear Amit,
-run t-code CO03 for your production order;
-Goto-Documented Goods Movements
all postings are here.
if you need to do the reversal please run t-code CO13
put your oder number, 'tick' the operation/counter you need to reverse and hit 'Save' button
good luck.
p.s.
if you have a mat. document number but don't know which prod. order it belongs to,
just run t-code MB03 , put your mat.doc number and year, hit Enter and look at the 'Order' filed
if it came by the order confirmation there will be an order number.

Similar Messages

  • Why the delivery date is the same date as 'transptn plan date" & loading date' & ' good issue' & GR end date'

    Hi Experts,
    why the delivery date is the same date as ‘transptn plan date” & loading date’ & ‘ good issue’ & GR end date’.
    in shipping tab i can see Planned Deliv. Time  170 Days ... wat could be the reason.
    Many Thanks:
    Raj Kashyap

    Hi Jurgen,,
    Thanks for quick reply!!
    But i didnot find any things like that .. what could be the customizing .. and we are using GATP from APO side.
    \Raj Kashyap

  • Standard Report check whether Goods Issue has been performed for DN

    Hi All,
    My users is having a list of DNs where they would like to check if Post Goods Issue has been performed for them.  I would like to ask is there any standard reports as to check if a Delivery Note has PGI performed?
    I have tried report VL06G but in this report we cannot give the DN No. as the key. 
    Thanks.

    There is no standard reports to check GI by DN number.
    You have to find out the Outbound Number first then check by Outbound number.
    In SE16N, key VBFA table
    Pump in your DN number under "Follow-on doc."
    Under "Prec.doc.categ." select "J".
    with the outboud number, you can proceed to check using above report suggested.
    Alternatively, using same VBFA table. Pump in list of outbound number under "Preceding Doc." and select "Subs.doc.categ." as "R".
    If you can set-up query reports, you can also get all the information directly with the DN Numbers.

  • How to understand post goods issue  has been done?

    how to understand post goods issue  has been done?
    thanks
    Moderator message: please search for information and try finding out yourself before asking.
    locked by: Thomas Zloch on Aug 18, 2010 5:21 PM

    Check for the status in the table. VBUP ( Item level status ) - WBSTA - 'C' , goods movement completed
    VBUK ( At header level ) - WBSTK  If 'C', goods movement completed
    Sujay

  • Goods issue in previous date

    Dear Experts,
    I have a problem with previous period postings.
    We are entering in to production server. Present date is : 01.04.2009.
    Now the open period is 10th of 2008 (January).
    But we are starting the transactions from 01.01.2009 (3rd quarter of 2008)
    when we issue material against to sales order, system not allowing to issue, and throwing an error "material can not be issued in the past date".
    how to solve this problem.
    can any body help me in this.
    regards
    Anand.M

    Now the open period is 10th of 2008 (January).
    But we are starting the transactions from 01.01.2009 (3rd quarter of 2008)
    I dont know what you mean by these statements
    Most propably your MM period would have been closed (MMPV transactions)
    To open the closed MM period can be done MMPI
    But extremely risky and not advisable  production server
    Check with SAP
    Normally today 01.04.2009 you close the period of march 2009 thro MMPV and still will be able to perform backdated goods issue for march only
    SAP standards allow one monthof closed period as grace time
    Regards
    Raja

  • Goods issue in past date

    Hello,
    I notice that i can issue more than the available quantity of a material in past date. The material i issued had 15 PCS at 5/6/2010 and 30 PCS at 11/6/2010. I issued 18 PCS with posting date 6/6/2010. Then i issued the rest but i couldn't issue more than 30 PCS.
    Is this standard SAP functionality or it can be customized  ?
    Thanks in advance.

    Hi,
    Go to MB5B stock on date and check for the available stock on that particular date & same stock you can issue in back date which is restricated to only one month as SAP standard in MM and if you ahve set allow in back date tick then only it will allow.
    If you wish to issue more then the available stock then you ahve to set negative stock tick in configuration which will allow to issue more then the availabe stock.

  • Goods issue has not been posted for delivery

    HI Experts,
    When my user creating the billing he is getting the problemu201Dgoods issue has not been posted for deliveryu201D.
    I investigated and found that in delivery qty for line item 10 (delivery qty is 1 and picking qty is 0) he is not maintained a picking quantity. I asked the user to maintain this. But when he uses the transaction code vl02n he is not able to change the picking quantity from 0 to1 why because the screen is grey mode and one more thing he is not able to cancel the u201CPGIu201D.
    Can any body let me know how to pick a qty in delivery what configuration I have to check .
    Regards,
    Sunina A

    Hello,
    As picking is not activated in the screen, thenyou need to go for a Transfer order Go to VL02N --> subsequent functions --> Create trnasfer order. The system will take you to create transfer order screen (LT03). Save it. Check the delivery whether the pick quantity has been updated ord not? If not then go for confirming the transfer order by transaction LT12. The picking quanity will be picked up. Now proceed with PGI.
    Prase

  • Goods issue in production order using BAPI_PRODORDCONF_CREATE_TT

    Hi All,
    This is regarding goods issue in a production order.We are trying to do this using BAPI_PRODORDCONF_CREATE_TT.
    We have a finished good say FK_PROD_ORD_CONV(with BOM -FKTESTOUT2).we need to do a Goods Issue for this which implies that at reporting point 0001,we need to issue x quantities of BOM FKTESTOUT2 from a particular plant and storage location, and of a particular batch. Therefore, we need to pass the following:
    Production order number
    Plant
    Material (BOM) = FKTESTOUT2
    Movement indicator (which is u2018Fu2019 for goods movement) = u2018Fu2019.
    Movement type = 261(for Goods Issue)
    Storage location of BOM
    Batch
    Operation (Routing point) = 0001
    Entry quantity
    Entry Unit of measure = PC.
    In addition, we need to maintain entries in Link_conf_goodsmov-INDEX_CONFIRM and link_conf_goodsmov-INDEX_GOODSMOV. The value for both would be u20181u2019.
    In the Test program, although I am passing all these values, Goods Issue is not happening. I am not getting any error.The message just says that the production order has been confirmed but when i check for goods Issue,no corresponding data is there.
    After this i am calling fm to commit the work as well.
    Please let me know if I have missed something.

    Good day!
    Do you see you confirmation with CO14 transaction?
    What on movements tab?
    Look at postprocess transaction COGI CO1P.
    Check LINK_CONF_GOODSMOV TABLE with 1,1 record.

  • Problem in Goods Issue using BAPI_PRODORDCONF_CREATE_TT

    Hi All,
    This is regarding goods issue in a production order.We are trying to do this using BAPI_PRODORDCONF_CREATE_TT.
    We have a finished good say FK_PROD_ORD_CONV(with BOM -FKTESTOUT2).we need to do a Goods Issue for this which implies that at reporting point 0001,we need to issue x quantities of BOM  FKTESTOUT2 from a particular plant and storage location, and of a particular batch. Therefore, we need to pass the following:
    Production order number
    Plant
    Material (BOM) = FKTESTOUT2
    Movement indicator (which is u2018Fu2019 for goods movement) = u2018Fu2019.
    Movement type = 261(for Goods Issue)
    Storage location of BOM
    Batch
    Operation (Routing point) = 0001
    Entry quantity
    Entry Unit of measure = PC.
    In addition, we need to maintain entries in Link_conf_goodsmov-INDEX_CONFIRM and link_conf_goodsmov-INDEX_GOODSMOV. The value for both would be u20181u2019.
    In the Test program, although I am passing all these values, Goods Issue is not happening. I am not getting any error.The message just says that the production order has been confirmed but when i check for goods Issue,no corresponding data is there.
    Please let me know if I have missed something.

    Hello.
    Are you calling FM BAPI_TRANSACTION_COMMIT afterwards? If yes, check the content of structure RETURN.
    Regards.
    Valter Oliveira.

  • Internal error (-2014) Goods Issue with Batch Items added through UI

    Hello Experts,
    I've added a button to my Production Order screen labeled 'Issue Components' that is meant to streamline the process, and it works, except when the ProdOrder has Batch controlled items on it. When that happens it returns Internal error (-2014)<br><br>
    I've tried stepping through the code and it doesn't error until the final Add
    Here is my function, Thanks for the Help!<br><br>
    I'm using CitiXSys Inventory Pro and am pulling the items from the Picked table, that's what that sQuery does. It returns correctly. I've also set everything to 'Manual' instead of 'Backflush'<br><br><br>
    <pre>
    Private Sub IssueComponents(ByVal iDocNum As Integer)
            Try
                'Declaring the needed variables'
                Dim oRec As SAPbobsCOM.Recordset
                Dim oGoodsIssue As SAPbobsCOM.Documents
                Dim bIssueLineAdded As Boolean = False, sQuery As String = "", x As Integer = 0, iCode As Long = 0, sErrorMessage As String = ""
                Dim tmpLot As String = ""
                'Instanciating the Goods Issue'
                oGoodsIssue = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oInventoryGenExit)
                'Initialzing the SBO object'
                oRec = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.BoRecordset)
                'Assing the header of the Goods Issue'
                oGoodsIssue.DocDate = Date.Now
                oGoodsIssue.DocDueDate = Date.Now
                'Getting the entire "Manual" components for this production order to issue them'
                sQuery &= "Select PK1.U_DocNo, KI.U_ItemCode, KI.U_BseLnNo, OW.DocEntry, KI.U_Quantity, KI.U_WhsCode, KI2.U_BatSrlNo, KI2.U_LotNo from [OWOR] OW (NOLOCK) INNER JOIN [@ctx_pkin] PK ON OW.DocNum = PK.U_BaseDoc," & vbNewLine
                sQuery &= "[@ctx_PKIN] PK1 (NOLOCK) INNER JOIN [@CTX_KIN1] KI (NOLOCK) ON PK1.U_DocNo = KI.U_DocNo," & vbNewLine
                sQuery &= "[@ctx_KIN1] KI1 (NOLOCK) INNER JOIN [@CTX_KIN2] KI2 (NOLOCK) ON KI1.U_DocNo = KI2.U_DocNo and KI1.U_BseLnNo = KI2.U_BseLnNo" & vbNewLine
                sQuery &= "where OW.DocNum = '" & iDocNum & "' and PK.U_BaseType = 202 and PK1.U_DocNo = PK.U_DocNo and KI1.U_DocNo = PK.U_DocNo and KI1.U_BseLnNo = KI.U_BseLnNo" & vbNewLine
                'Executing the query'
                oRec.DoQuery(sQuery)
                'Looping through the "Manual" components'
                For x = 0 To oRec.RecordCount - 1
                    'Prompting the user'
                    oAppl.StatusBar.SetText("Issuing Components...(" & x + 1 & " of " & oRec.RecordCount & ")", SAPbouiCOM.BoMessageTime.bmt_Long, SAPbouiCOM.BoStatusBarMessageType.smt_Warning)
                    'Adding the previous line if applicable'
                    If bIssueLineAdded Then
                        oGoodsIssue.Lines.Add()
                    End If
                    'Filling the line information'
                    oGoodsIssue.Lines.WarehouseCode = oRec.Fields.Item("U_WhsCode").Value 'dIssueComponents(x).Item("WhsCode")
                    'oGoodsIssue.Lines.TransactionType = SAPbobsCOM.BoTransactionTypeEnum.botrntComplete
                    oGoodsIssue.Lines.BaseEntry = oRec.Fields.Item("DocEntry").Value 'oProductionOrder.AbsoluteEntry
                    oGoodsIssue.Lines.BaseType = 202                                          'Production Order Type'
                    oGoodsIssue.Lines.BaseLine = oRec.Fields.Item("U_BseLnNo").Value 'GetBaseLine(oProductionOrder.AbsoluteEntry, dIssueComponents(x).Item("Component"))
                    'oGoodsIssue.Lines.ItemCode = oRec.Fields.Item("U_ItemCode").Value
                    oGoodsIssue.Lines.Quantity = oRec.Fields.Item("U_Quantity").Value 'Math.Round(oRec.Fields.Item("U_Quantity").Value, 2) 'dIssueComponents(x).Item("PlanQty")
                    'Checking if the item is neither lot or serial controlled item'
                    If oRec.Fields.Item("U_BatSrlNo").Value = "" And oRec.Fields.Item("U_LotNo").Value = "" Then
                        'Nothing controlled item'
                    ElseIf oRec.Fields.Item("U_BatSrlNo").Value <> "" Then
                        'Lot controlled item'
                        tmpLot = oRec.Fields.Item("U_BatSrlNo").Value
                        'oAppl.MessageBox("Lot: " & tmpLot & ", whs: " & oRec.Fields.Item("U_WhsCode").Value & ", qty: " & oRec.Fields.Item("U_Quantity").Value)
                        oGoodsIssue.Lines.BatchNumbers.Add()
                        oGoodsIssue.Lines.BatchNumbers.BatchNumber = oRec.Fields.Item("U_BatSrlNo").Value
                        oGoodsIssue.Lines.BatchNumbers.Quantity = oRec.Fields.Item("U_Quantity").Value 'Math.Round(oRec.Fields.Item("U_Quantity").Value, 2)
                        'Else
                        'Serial controlled item'
                        'oGoodsIssue.Lines.SerialNumbers.SystemSerialNumber = oRec.Fields.Item("").Value
                    End If
                    'Setting the line to be added'
                    bIssueLineAdded = True
                    'Movoing to the next record'
                    oRec.MoveNext()
                Next x
                'Checking if there was any component or not'
                If bIssueLineAdded Then
                    'Adding the Goods Issue'
                    iCode = oGoodsIssue.Add
                    If iCode <> 0 Then
                        oCompany.GetLastError(iCode, sErrorMessage)
                        oAppl.MessageBox("Goods Issue Production Order: " & iDocNum & " didn't get created for the following reason: " & serrormessage)
                    Else
                        oAppl.StatusBar.SetText("Components were issued successfully.", SAPbouiCOM.BoMessageTime.bmt_Short, SAPbouiCOM.BoStatusBarMessageType.smt_Success)
                        'TODO: add to ProdOrder remarks field
                    End If
                End If
            Catch ex As Exception
                oAppl.MessageBox("IssueComponents() " & ex.Message)
                oAppl.StatusBar.SetText("Error in IssueComponenets() : " & ex.Message, SAPbouiCOM.BoMessageTime.bmt_Short, SAPbouiCOM.BoStatusBarMessageType.smt_Error)
            End Try
        End Sub
    </pre>
    Edited by: Rob Daniels on May 30, 2011 10:33 PM

    Please use the latest upgrade of Inventory Pro from CitiXsys.
    If you are using SAP Business One 2007; use Inventory Pro 5.6 series
    For SAP Business One 8.8 and up; use Inventory Pro 6.6.1 and up

  • Regarding Goods Reversal & Goods Issue Process for PO

    Hi Experts,
               Could you any one tel me what is Goods Reversal and Goods Issue process for PO...
    How to create the FM & detailed Procedure Pls?....
    Please any one tel me.......
    Thanks & Reagards
    HB

    Hi Hans,
    SOURCE : HELP.SAP
    Purpose
    Inventory Management uses this process in such a way that the goods issue posting is divided into two parts that run in separate systems. Posting the GI document in the supplying plant results in a message to the receiving plant. The receiving plant then performs a complementary posting. The physical goods receipt takes place as usual.
    Prerequisites
    When using batch processing, the following prerequisites must be fulfilled:
    Both the original and target systems have the same batch definition level.
    The batch definition level is either the material or the client.
    An ALE scenario exists for materials and classes (characteristics).
    Unique batch numbers exist cross-system.
    Batches can only be changed in their original system when they are not decoupled. From an organizational point of view, this must also lead to the batch status being changeable in a local SAP R/3 system. For example, this is impossible when transfer posting to a new batch and results in further actions, for example, relabeling containers, palettes and so on.
    Characteristics
    As for the purchase order in a one-system situation, the system should automatically post the material into the stock in transit at the receiving profit center and the corresponding Profit Center Accounting using intra-CC transfer prices at goods issue for the purchase order and the unchecked delivery. This requirement is valid for one-system situations as well as for two-system situations where there is an ALE interface. No internal billing document should be created.
    In a two-system case, the receiving profit center should be derived at goods issue from the unchecked delivery. Profit Center Accounting then takes place with
    Stock change transfer price to stock
    Internal expense to internal sales
    Internal clearing account to stock change transfer price.
    Account determination in a purchase order for an intra-company-code transaction must be different from account determination in external transactions. Automatic GR/IR account clearing is required in both one-system and two-system situations.
    The stock in transit must be visible in the receiving profit center.
    The system must send a shipping notification at goods issue in one-system and two-system situations.
    You need to create an invoice document for the internal and external trading statistics for cross-boundary deliveries as well as for customs purposes.
    GR/GI slips are created.
    Process Flow
    Goods Issue Posting for Stock Transfers
    The delivery triggers the goods issue in the issuing system.
    The call contains the stock transport order data known in the delivery, including the PO item and the logical system of the recipient.
    The transaction (quantity and value updates) is selected using the movement type:
    Movement Type     
    Function
    641     
    Goods issue with UB logic (Creation of stock in transit at recipient, immediate value posting).
    647     
    As 641, however the goods receipt line (movement type 101) is added automatically, so that the goods receipt is posted at the same time as the goods issue (one-step procedure).
    You determine the movement type according to the schedule line category in Sales and Distribution. The goods issue for a cross-system stock transfer must be different from the integrated transaction. This is achieved by adding a new movement type.
    You post quantities and values at goods issue in the same way as a goods issue for a sales order. That is to say, the quantity is posted in the supplying plant and the value is adjusted to that of the stock account. The offsetting posting is made to a clearing account. The known data from the delivery is copied to Accounting to balance the account where necessary.
    The system creates a message to the appropriate receiving system for all items with reference to a cross-system purchase order. The system does not perform any validity checks on the recipient’s data before posting begins. Incorrect Customizing results in the update being terminated.
    If a goods issue has receiving plants in different logical systems, an IDoc is sent for each system.
    In order that the goods receipt is able to use the values on the receiver side, you must add the values used to post the goods movement, in particular the transfer prices, to the IDoc.
    The logic for recognizing the profit center switch functions as follows: At goods issue, the system recognizes that the profit center of the issuing plant is different from the profit center of the receiving plant. The system derives the profit center node from the relevant profit center.
    Data Transfer
    The IDocs sent by the issuing plant trigger the goods issue postings in the receiving plant.
    Background Posting in the Receiving System
    The goods receipt is posted in the receiving system using the IDoc. The interface receives the data from the goods issue in the supplying plant. The following processes now run at the recipient:
    The system finds the update control for the GR part of the posting.
    The goods movement is posted with the new movement type.
    During valuation of the goods receipt, the system might, where necessary (UB logic), refer to the values (legal value and the value from the parallel valuation type, if you are using the transfer price function) from the IDoc.
    The PO history is updated. The PO history is updated with the material document number from the second part of the GI posting. The GI document number is not stored in the supplying plant, because there is no way to display this document.
    In two-step procedures the goods receipt is posted to the stock in transit.
    Reversal
    You can only reverse this goods issue for the PO using the cancellation transaction in SD. You cannot reverse the GI in Inventory Management.
    The material document that is automatically created in the receiving system cannot be canceled. This reversal is triggered by the sending system (the actual reversal of the GI document takes place there) and transmits the data, including the reversal movement type, to the receiving system. No actual reversal is posted in the receiving system, because the material document number of the original document does not exist in this system. This scenario is applicable for cases where you use the two-step procedure (with stock in transit).
    Distribution of Batch Master Data and Characteristics
    The batch information is transported using the message category BATMAS.
    When you create a cross-system goods issue, the system creates the corresponding IDoc using the message category BATMAS.
    When the delivery arrives in the target system, the batch and all the information is already present in the system.
    Changes to the batch data are also distributed using the message category BATMAS.
    The batch can be decoupled in the receiving SAP R/3 system. This means that the batch can have a different status in the receiving system than in the original system. By setting an indicator at material level, you decide whether the batch can be decoupled or whether the batch and all its attributes are copied from the original system. "Decoupled" i.e. "locally independent" batches are no longer distributed from its own system.
    The batch data does not need to be available before the physical goods receipt takes place. The goods receipt into the stock in transit does not usually refer to the batch unless you are working with batches with assigned active ingredient values.
    If the GI cannot be posted for organizational reasons, for example because the goods cannot be loaded onto a truck until 10pm, then you can post the goods into the GR blocked stock. This stock is also non-batch-specific.
    In cases where the GI IDoc arrives before the batch IDoc, then the GI IDoc can be subsequently posted by a periodically scheduled report (transaction BD87). A program like this exists in the SAP standard system. In Customizing for MM Inventory Management (activity Copy, Change Movement Types), you should make settings to define that manual creation of batches at goods receipt is not allowed.
    Shipping Notification
    The shipping notification is required in the receiving system due to its relevance for MRP. In this way, for example, a change in delivery date determined at goods issue is sent to the receiving system using the shipping notification. The shipping notification can also be used when posting the GR batches.
    Reward if found helpfull,
    Cheers,
    Chaitanya.

  • Value of inventory after Goods Issue, before Goods Receipt for open order

    Dear Experts,
    Raw materials R72 and R82 are required to produce Semifinished Product S10.
    Semifinished product S10 is required to produce Fnished product F20
    On 10th August 2011, I created and release a Process Order for material S10 copying component materials R72 and R82.. Goods issue for component materials R72 and R82 were done for this process order using tcode MIGO (mvt type 261).
    It  takes four to five days to properly blend components R72 and R82 to obtain S10.
    It means Goods Receipt for this process order will be done on 14th or 15th August when this blending has been completed.
    Management suddenly issues a directive that stock take should be carried out in the plant on the 12th August 2011, and my process order is still open and cannot be closed ( or goods receipt cannot be done)  because blending is yet to be completed.
    Please how do I take care of this scenario/situation since Goods Issue has been done already?
    How will the Accountants see or get the correct value of inventory?

    When I run WIP Calculation for my Process Order, what will be the effect ? I mean what accouts are updated by WIP Calculation within a period (not across a perion or  at period end)?
    GI values issued to the Process order will come into WIP GL .( Since your client want to know the stock take should be carried out in the plant on the 12th August 2011- we are doing WIP calculation)
    > After  this WIP Calculation is run,  and say about 2days later, Goods Receipt for this process order is to be posted, what steps am I suppose to carry out?
    After GR Made, Run a WIP calculation again for the order so that The WIP from the GL account will get reduced ,now WIP= (GI value + confirmation ) -(GR Value),
    Check in DEV system before doing in PRD,
    On Month end, do the variance calculation and do the settlement

  • Goods issue in REM process

    hi sir,
    I am new to SAP, so plz guide me.
    in Paper industry this is the actual
    Business Process:
    In  papers industry  they have different varieties of paper production in which they are characterized by the GSM (thickness), sizes  and  grades. These characteristics are not given by customer, they are pre-defined and are fixed i.e based on the available variety of paper that is produced in paper  mill the customer makes the order for sheets or reels(FG). The different customer makes the order for different grades and GSM of paper. In 7th day of  every month they compile the orders in order to get the net quantity of paper quality type  to be produced and based on that the production is done. Remaining materials like pulp, power, steam, water treatment production are continuously takes place without any reference to the FG(paper) to be produced. There is fixed production lines.
    Eg:
    A,B, C are the grades of paper.  If for A-10MT,5MT,15MT are the orders and for B-4MT,2MT similarly for C-15MT,20MT are the orders. Then totally for A-20MT, B-6MT and for C-35MT planned to produce in a month.
    Note: If the customer needs the new variety or changes in the paper variety that is already available then R & D is made on that variety and a new name is given to it.
    Hence, this is Make To Stock  with Repetitive manufacturing process.  Is this process is right??
    As per SAP best practices in repetitive process scenario, there will wont be conversion of planned order to production/process order, based on planned order the production takes place and then we will do the Operative backflushing.
    Here, the client requirement is on what basis the goods issue has to be done for production?? as there will be no production/process orders.

    Hi,
    REM process has been developed by SAP for less complicated scenarios. I mean where product varieties are less and process is less complex.
    That is the reason there is no concept of order. Cost is getting captured on the product cost collector lever rather individual order level(In discrete).
    Goods issue is on planned order which is of PE type (Once order is LA type you can assign the material to planning table. Then it will be PE)
    GI happen through back flush.
    Please refer the above links for better idea.
    Regards,
    Krishnendu.

  • Goods Issue with Purchase Account Management

    Hi,
    in one of our foreign subsidiaries we have to run the MM-Purchase Account Management. These subsidiaries will be delivered by Cross-Company Replenishment deliveries with intercompany-invoicing. Every Goods receipt for such an replenishment delivery will be posted in the receiving subsidiary, besides the normal bookings on the u2018Goods/Invoice Received clearing accountu2019 and u2018Stock accountsu2019, on additional purchasing accounts. Now itu2019s possible that the goods have to be returned to the delivering plant due to any problems. To send back the goods we use again a SD-delivery (triggered also by an MM-IC-Purchase order) and with this SD-delivery we want also to post the goods issue in the subsidiary. But as the goods receipt has been posted on these special additional purchasing accounts, the goods issue has also to be posted on these special additional purchasing accounts (The target is to correct these purchasing accounts to the ammount of the returned goods). But it seems that this is not possible because of the MM-Account determination which doesnu2019t allow to post on these special purchasing accounts with an SD-transaction. Iu2019m no MM-expert but is there any possibility to post on this purchase accounts also when posting a goods issue in SD? If not in standard, are there any User-Exits in the account determination?
    Regards
    Stephan
    Edited by: Stephan Nadler on Aug 12, 2008 1:20 PM

    Hello Dinesh,
    Batch valuation is similar to split valuation. Here is the link on how batch valuation works.
    http://help.sap.com/saphelp_47x200/helpdata/en/25/283db54f7811d18a150000e816ae6e/content.htm
    Please check in sandbox environment before using.
    Hope this helps.
    Regards
    Arif Mansuri

  • Billing in CRM before goods issue in ECC

    Does anyone know if it is possible to create a billing document in CRM before the goods issue has been posted for the delivefry created in ECC? In some cases we need toi have a Pro Forma, before goods issue has been posted.
    Best regards,
    Pascal.

    Couple of things to Clarify here.. There is no such thing as Financial postings in CRM. If you are referring to Billing..CRM can support creation of Debit Memos only and nothing beyond that. So DMs will become your billing document and any other subsequent Accounting entries are dependent on external system like ECC.
    As the other person said, you need to configure the whole 9 yard on Billing in CRM using CRM BEA
    Thanks
    Raj

Maybe you are looking for