GL posting during movement type 107 & 108

Presently system is posting to inventory Gl Account for rejections ,returns and damages from customers during 107 and 108 movement type in MIGO
we want system to post to different GL Account with respect to reason for movement only during Movement type 107 and 108
Edited by: Prabhudev on Nov 8, 2008 9:39 AM

Hi
These are the new movemnt types used for Goods receipt with ref. to Purchase order
107 Mvt recives the Stock as GR Blocked Stock but with Value, An accounting document gets generated
109 Mvt moves the material fro GR Blocked stocked to Unrestricted use stock , No accounting Documents are generated.
108 & 110 are reversal movements ffor 107 & 109
These movments are similar to that of 103 & 105. Which are used for 2 step GR w.r.t PO
In 103 Stock type is GR Blocked stock with out value , no accounting document genareated
105 Stockm is moved from GR blocked to Unrestricted use. accounting document is generated.
hope this helps
Edited by: Manohar Raju on Feb 26, 2008 10:53 AM

Similar Messages

MIRO should not happen for Movement Type 107

Dear All,
We have a peculiar scenario/requirement fulfilled by business and we have done almost all but getting stuck in below area:
We have developed a output type in order to automatically post Mat Doc with Movement Type 107 once the user reverses Material Document with Mvt Type 103, This as per a business requirement. That means when 104 will be done for a Mat Doc with Mvt Type 103, "PO History Tab" will display in following order:
103 > 104 > 107
After 107, user will reverse it with Mvt Type 108 and specific G/L accounts will be hit which will update the "PO History" as:
103 > 104 > 107 > 108
Now issue is we want MIRO to be possible for Mvt Type 108, not for Mvt Type 107 else it will create a vendor liability twice and business will end up paying amount to vendor twice.
How can this be achieved?
Your sound suggestions are most welcome.
Regards
Samier Danish

No replies
Regards
Samier Danish

BDC for MIGO for GR OutBound Delivery( A01 & R05 ) from Movement Type 107 to 109

Hi,
I am stuck with a very typical situation need all your expertise and advices for a solution.
We are basically trying to create change the movement type from 107 to 109 through MIGO.
I have made a BDC recording for MIGO ( because we would like to track each delivery specifically under shipment , I know that there is a BAPI which is there to do this but it works fine if we do the shipment with Purchase Order as input which dont want in that manner )
Process:
1. Creating Production Order
2. Creating Purchase Order
3. Creating STO
4. Deliveries
5. PGI for Deliveries
6. Shipment for group of outbound Deliveries
I have created a z program where i am passing shipment number in the selection screen.
Then it would take all the deliveries for that shipment and pass each delivery to MIGO and process it and change the status from 107 to 109.
Interesting part here is, the code works absolutely perfect only from my ID. But when I test from other ID it is not executing, so to check where is the problem I have added mess_tab to the CALL TRANSACTION to capture what message is been populated for my ID comparing with others
Message Captured on Others ID's:
MSGID: 00
MSGNR: 344
MSGV1: SAPLMIGO
MSGV2: 1300
Message Captured on MY ID:
MSGID: MIGO
MSGNR: 012
MSGV1: 5000005802
MSGV2: (empty)
This is the problem this program is executing only on MY ID, rest all ID's it is not processing.
We have cross verified with security and basis regarding any authorization issues but nothing came up.
Please help me what could be the issue ( WHY it is processing successfully for my and WHY NOT for other ID's)
Below is the main code :
CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'                     " Converting Date format to DD/MM/YYYY
     EXPORTING
       DATE_INTERNAL            = sy-datum
     IMPORTING
       DATE_EXTERNAL            = lv_date_external
     EXCEPTIONS
       DATE_INTERNAL_IS_INVALID = 1
       OTHERS                   = 2.
       IF SY-SUBRC <> 0.                                     "#EC NEEDED
* Implement suitable error handling here
       ENDIF.
*   Validating input shipment number with database table VTTP
       SELECT VTTP~TKNUM
              VTTP~TPNUM
              VTTP~VBELN
         FROM VTTP INNER JOIN VTTK
         ON VTTP~TKNUM = VTTK~TKNUM
         INTO TABLE IT_VTTP
         WHERE VTTK~TKNUM = P_TKNUM
           AND VTTK~STDIS = 'X'.
       IF sy-subrc = 0.
*   Validating all deliveries having same Delivery type or not
         SELECT * FROM likp INTO TABLE it_likp FOR ALL ENTRIES IN it_vttp WHERE vbeln = it_vttp-vbeln
                                                                            AND vbtyp = 'J'.
         IF sy-subrc = 0.
           CLEAR lv_lines.
           LOOP AT it_likp INTO wa_likp.
             REFRESH:it_vbfa,BDCDATA.
*   Validating if Delivery Type = 109 (GR already done), or Delivery Type = 107 (must process for GR )
             SELECT * FROM vbfa INTO TABLE it_vbfa WHERE vbelv = wa_likp-vbeln
*                                                AND vbtyp_v = 'J'
                                                     AND bwart = '109'.
             IF sy-subrc = 0.
               lv_flag1 = 'X'.
             ELSE.
               SELECT * FROM vbfa INTO TABLE it_vbfa WHERE vbelv = wa_likp-vbeln
*                                                  AND vbtyp_v = 'J'
                                                       AND bwart = '107'.
               IF sy-subrc NE 0.
                 MESSAGE 'No Deliveries with Movement Type "107" ' TYPE 'I'.
               ELSE.
                 lv_flag2 = 'X'.
                 lv_lines = lv_lines + 1.
** BDC for MIGO
                 perform bdc_dynpro      using 'SAPLMIGO' '0001'.
                 perform bdc_field       using 'BDC_OKCODE'
                                               '=OK_GO'.
                 perform bdc_field       using 'GODYNPRO-ACTION'
                                               'A01'.
                 perform bdc_field       using 'GODYNPRO-REFDOC'
                                               'R05'.
                 perform bdc_field       using 'GODEFAULT_TV-BWART'
                                               '109'.
                 perform bdc_field       using 'BDC_CURSOR'
                                               'GODYNPRO-OUTBOUND_DELIVERY'.
                 perform bdc_field       using 'GODYNPRO-OUTBOUND_DELIVERY'
                                               wa_likp-vbeln. "'80019574'.
                 perform bdc_field       using 'GOHEAD-BLDAT'
                                               lv_date_external. "'04/29/2015'.
                 perform bdc_field       using 'GOHEAD-BUDAT'
                                               lv_date_external. "'04/29/2015'.
                 perform bdc_field       using 'GOHEAD-WEVER'
                                               '1'.
                 perform bdc_dynpro      using 'SAPLMIGO' '0001'.
                 perform bdc_field       using 'BDC_OKCODE'
                                               '=OK_POST1'.
                 perform bdc_field       using 'GODEFAULT_TV-BWART'
                                               '109'.
                 perform bdc_field       using 'GOHEAD-BLDAT'
                                               lv_date_external. "'04/29/2015'.
                 perform bdc_field       using 'GOHEAD-LFSNR'
                                               wa_likp-vbeln. "'0080019574'.
                 perform bdc_field       using 'GOHEAD-BUDAT'
                                               lv_date_external. "'04/29/2015'.
                 perform bdc_field       using 'GOHEAD-WEVER'
                                               '1'.
                 perform bdc_field       using 'GODYNPRO-DETAIL_ZEILE'
                                               '   1'.
                 perform bdc_field       using 'GOITEM-ERFME'
                                               'EA'.
                 perform bdc_field       using 'GOITEM-ERFMG'
                                               '1'.
                 perform bdc_field       using 'GOITEM-LSMNG'
                                               '1'.
                 perform bdc_field       using 'GOITEM-LSMEH'
                                               'EA'.
                 perform bdc_field       using 'GOITEM-MIGO_ELIKZ'
                                               '1'.
                 perform bdc_field       using 'GOITEM-BWART'
                                               '109'.
                 perform bdc_field       using 'GOITEM-LGOBE'
                                               'RX Cross-docking'.
                 perform bdc_field       using 'BDC_CURSOR'
                                               'GODYNPRO-DETAIL_TAKE'.
                 perform bdc_field       using 'GODYNPRO-DETAIL_TAKE'
                                               'X'.
                 PERFORM bdc_dynpro      USING 'SAPLMIGO' '1300'.
                 PERFORM bdc_field       USING 'BDC_CURSOR'
                                               'G_TIP_DONT_SHOW_AGAIN'.
                 PERFORM bdc_field       USING 'BDC_OKCODE'
                                               '=OK_TIP_GO'.
                 PERFORM bdc_field       USING 'G_TIP_DONT_SHOW_AGAIN'
                                               'X'.
*& Avoid unncessary screens to populate while processing background.
                 LV_OPTIONS-DISMODE = 'N'.
                 LV_OPTIONS-UPDMODE = 'S'.
                 LV_OPTIONS-NOBINPT = 'X'.
                 CALL TRANSACTION 'MIGO' USING BDCDATA OPTIONS FROM LV_OPTIONS MESSAGES INTO IT_MESSTAB1 .
                 WAIT UP TO 1 SECONDS.
                 DELETE IT_MESSTAB1 WHERE MSGTYP NE 'E'.
                 IF IT_MESSTAB1[] IS NOT INITIAL.
                   APPEND LINES OF IT_MESSTAB1 TO IT_MESSTAB.
                 ENDIF.
               ENDIF.
             ENDIF.
           ENDLOOP.
         ENDIF.
       ELSE.
         MESSAGE 'Shipment Number does not exists Or not Planned' TYPE 'E'.
       ENDIF.
     ELSE.
       MESSAGE 'Please insert Shipment Number' TYPE 'E'.
     ENDIF.
     IF lv_flag1 = 'X' AND lv_flag2 = 'X'.
       MESSAGE 'This shipment is processed with an inconsistent goods receipt' TYPE 'I'.
     ELSEIF lv_flag1 = 'X'.
       MESSAGE 'Shipment already been processed for these deliveries' TYPE 'I'.
     ELSEIF lv_flag2 = 'X'.
       lv_lines1 = lv_lines.
       CONDENSE lv_lines1 NO-GAPS .
       CONCATENATE lv_lines1 'Goods Receipt are posted for the shipment '
              INTO lv_message SEPARATED BY space.
       MESSAGE lv_message TYPE 'I'.
     ENDIF.
* Display Messages from Message TAB.
     DELETE ADJACENT DUPLICATES FROM IT_MESSTAB.
     DATA:lv_msg TYPE string.
     LOOP AT IT_MESSTAB INTO WA_MESSTAB.
       CALL FUNCTION 'FORMAT_MESSAGE'
         EXPORTING
           ID        = WA_MESSTAB-MSGID
           NO        = WA_MESSTAB-MSGNR
           V1        = WA_MESSTAB-MSGV1
           V2        = WA_MESSTAB-MSGV2
           V3        = WA_MESSTAB-MSGV3
           V4        = WA_MESSTAB-MSGV4
         IMPORTING
           MSG       = lv_msg
         EXCEPTIONS
           NOT_FOUND = 1
           OTHERS    = 2.
       IF sy-subrc <> 0.
* Implement suitable error handling here
       ENDIF.
       WRITE:/ lv_msg.
     ENDLOOP.
*        Start new screen                                              *
   FORM BDC_DYNPRO USING PROGRAM DYNPRO.                 "#EC PF_NO_TYPE
     CLEAR BDCDATA.
     BDCDATA-PROGRAM = PROGRAM.
     BDCDATA-DYNPRO   = DYNPRO.
     BDCDATA-DYNBEGIN = 'X'.
     APPEND BDCDATA.
   ENDFORM.
*        Insert field                                                  *
   FORM BDC_FIELD USING FNAM FVAL.                       "#EC PF_NO_TYPE
     CLEAR BDCDATA.
     BDCDATA-FNAM = FNAM.
     BDCDATA-FVAL = FVAL.
     APPEND BDCDATA.
   ENDFORM.
Thanks,
Srini

Hi Rob,
Thanks for quick reply.
I have checked the NOTE : 304122
But there in the NOTE it says ( " BAPI, BAPI_GOODSMVT_CANCEL, BAPI_GOODSMVT_CREATE, CNTL_ERROR" )
These BAPI's work perfectly for (purchase order as input type), but here out type is ( A01 & R05 ) we are giving DELIVERY NUMBER as input to MIGO.
So for this scenario we cannot use those BAPI's mentioned in the NOTE.
Also as stated earlier in the message interesting part is
"The code works absolutely perfect only from my ID. But when I test from other ID it is not executing. Code is working exactly as expected ONLY to my ID. When i try to execute the same code from another's ID it is not working"
So what do you think might be the issue?

What is the need for movement type 107

Hi Gurus,
In ECC 6.0 i have seen that SAP has introduced 107 for GR Block stock (valuated). Can anyone tell me the business sense for doing so.
What was the exact need for introducing 107
Rgds
Venkat

Hi,
GR Blocked valuatedstock menas , when you do the GR with movement type 107 it will posted under Plant and the value of the goods will be considerd/increased for that Plant. But the stock will be under Blocked Stock..It will not be used all other purpose till you do the transfer psting from Blocked to unresticted.
Thanks,
Kumar Arcot

Transfer posting with Mov Type 311E in MIGO with reference to SC-PO

Hi,
I am working with MTO scenario.
I want to carry out transfer posting of material with movement type 311E against subcontracting Purchase Order which is sale order specific.
However, system does not allow me to do the same. whenever transfer posting, PO & movement type is selected in transaction MIGO, item details entry tabs are displayed blank.
Below steps are being follow:
Scenario is MTO ( special stock subcontracting)
1. Subcontracting PO no. 4500000147 against Sale Order no 61 created.
2. RM code - 61, available stock 100 TO & batch no.0000000127
3. Transfer material to vendor for processing through MIGO ( since it is a special sales order stock, transferring happens from SL 0001- Main Stores to SL VLSC -Virtual storage location) using movement type 311 E
5. Item Data details tabs are blank.---This is the issue / error.
Note: I am restricted to post transfer posting through MIGO-Transfer Posting (will not use MB1B) due to some enhancement of MIGO and interfaces with legacy system.
Please have a look on attachment for SAP screen issue.
Regards
Mohit Jaiswal

Hi Mohit ,
please check below link , you need to perform steps as given
http://help.sap.com/saphelp_470/helpdata/en/4d/2b90b043ad11d189410000e829fbbd/content.htm
also see the sales order subcontracting using the business addon
http://help.sap.com/erp2005_ehp_04/helpdata/en/c7/2587b8dad94c52854ccd28015dceb0/frameset.htm

Error in Transfer posting for movement type 303

Hi Sir,
I am getting following error while doing Transfer posting for movement type 303 thru BAPI_GOODSMVT_CREATE
Error in Function:
Order    not found or not permitted for Goods Movement.
I am passiing all mandatory parameter for it as per BAPI Documentaion in tcode BAPI
Transfer posting
Transfer posting without reference to a reservation
The following fields must be populated:
Material number
Plant
Storage location
Movement type
Movement indicator
Quantity in unit of entry
ISO code unit of measurement for unit of entry
If I am doing manually by MB1B tcode, it is successfully done.......here its not asking any ORDER No...
Please help me .........
Regards,
Krishan

I'm not sure what you're system set up is...   So I'd suggest looking at everything you enter on the screen and then checking to make sure you are passing all the information in the BAPI.
With that said our system does require posting date, and batch. You might check that.   Also check that you've included all the required information in the header.
Did you use the same data when you tried to process the BAPI that you used when you tried to do MB1B manually?

Output Print for MIGO movement type-107.

Hi All kindly help me in resolving the following issues:-
There is the requirement of printing RF Label while saving the GR from PO in movement type-107.
Help me to configure the output type in this case.
How the data flows from MIGO transaction to the ABAP program and finally to the printer ?
How to link the output type to the transaction MIGO and so in movement type-107 ?

Hi,
go to spro-Materials Management-Inventory Management and Physical Inventory-General Settings.
in General Settings print version migo is 2 .execute after Maintain Print Indicator for Goods Receipt Documents check 107 mvt type.
refer the below link
Print material document (WE02) automatic when GR
Regards
Raj.

Different account posting for movement type 412 E ?How?

Account determination for the stock transfer from own stock to sales order stock:
When we transfer the stock from own stock to sales order stock, the amount which gets transferred from own stock to sales order stock is equal to quantity multiplied by the MAP of the item.
We have a scenario where there is a material A having MAP = 10.Quantiy of own stock for A is 100 EA .Now we have got a sales order for A with a quantity of 20 EA for a particular customer .We need sales order stock for this order at a special purchase rate say 8.
Next we have modified the movement type 412 E in such a way that when we transfer the stock from own to sales order stocks it will ask for the amount of the total quantity transferred. When I transfer 20 EA with movement type 412 E it prompts for the amount where we have provided the value 160(=20 X 8). Then save the posting. Accounting entries which happens are as follows:
Dr Stock    A/C u2013 310000       -
160
Cr Stock    A/C - 310000        -
160
In the process it recalculates the MAP of own stock. New MAP = ((100 X 10) u2013 160)/80= 10.5
We do not want the MAP to be effected in this process. We want a posting as below:
                  Dr Stock    A/C u2013 310000       -
160 (for sales order)
                  Cr Stock    A/C - 310000        -
200 ( for own stock)
                  Dr Gain/Loss account -       -
40
In this process the MAP of the own stock remains as 10.But this type of posting does not happen as long as you have own stock available. Is there any way to do the above posting with movement type 412 E . Reversal entry should be possible with movement type 411 E.
Regards,
Feroz Choudhury

Hi,
I am doing the reverse. Transfering Unrestricted stock to Sales Order stock. So it should appear in MBBS.
But in my case for example, if there is a sales order with 3 items, for 2 items posting is as follows:
Inventory account Dr. .....
Inventory account Cr. .....
But for 3rd item,
Cost of Goods Sold (COGS) Dr. .....
Inventory Cr. ....
So in MBBS, only first 2 items appear and not the third one.
Can u tell me what can be the reason for this.
Regards,
Niraj

GL during Mov type 601

Hi SAP Experts,
Need your help please
During PGI Mov type 601 few GL are debited and few are credited and during billing also the same
I) How is the GL determined in both the cases which one will be hitting dr and which one Cr
2) If we need to add one cost duing PGI and the same cost should not be billied to customer how to achive this ??
Please Advice..Thanks in advance for your reply

Hi,
GL Debiting at the time of PGI: COGS account is fetching from T Code OBYC, Offsetting entry for stock posting (GBB), 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)
GL Crediting at the time of PGI: Inventory Account is fetching from T Code OBYC, Stock posting (BSX).
GL Crediting at the time of Billing: Revenue account is fetching from T code VKOA.
If you need same value at the time of PGI and billing, Please maintain the cost value in condition record of the customer.
Thanks and Regards
Binoj M D

Changing GL acc posting for movement type

Dear all,
I want to change the GL account posting for the new movement type copied from 101. and also the offsetting entry posting. please give the steps for the same?
regards,
prash

Hi
Please try out in T.Code : OBYC
Enter Valuation modifier
Enter Valuation Class
Enter Credit & Debit G/l account
Thanks & Regards,
Mani

Sales Returns Stock posting using movement type 651

Hi Experts,
I want to upload the sales returns stock using movement type 651. Because, our existing company code 'xxxx' has been changed to 'zzzz' and all the stocks, balances and so on has been uploaded and carry forwarded to new company code 'zzzz'.
Now, I stuck with the customer/sales returns stock. Also, I know that there is no accounting effects with the movement type 651 i.e., blocked stock stored in customer rejection storage location.
I have tried lot but I didn't get the solution for the same.
Kindly share some ideas to upload the sales returns stock.
Anandkumar KS

Dear Experts,
First of all, sorry for late reply.
I tried using the movement type 655, but i can't able to post the stock.
Is there any other way to post the stock in customer rejection storage location with the movement type 655?
Also, it should not create any Accounting Document while posting the stock.
Please advice me in this issue.
Anandkumar KS

Two Step Posting in Movement Type 201 and 309

Hi Experts,
Our copmany wants to use movement type (T-code MB1A) 201 and (MB1B) 309 in two way posting, like 313/315 like some body create the document and then somebody apporves the document then finance entry takes place.
How can we map the same in the system, please suggest, its most urgent.
Regards
Ishu

201 Goods issue for a cost center
The goods can only be withdrawn from unrestricted-use stock.
Possible special stock indicators:
K: Goods withdrawal from consignment stock
P: Goods withdrawal from the pipeline
If you have withdrawals from consignment stock and from pipeline, payables to suppliers ensue.
309 Transfer posting material to material
The quantity is posted from unrestricted-use stock of the issuing material into unrestricted-use stock in the receiving material.
Prerequisite: both materials have the same stockkeeping unit.
Possible special stock indicators:
E, O, Q, V, W
I think it is not possible in Standard System

Revesal of document posted with movement type 654

I have created one outbound delivery using tcode VL01NO (Create outbound del without order reference). In PGI material qty was issued using movement type 654. Now, I need to reverse this document i.e. reversal of movement type 654, but system is not allowing the same.
Pl help on this
regards,

movement 654 is already the reversal to movement 653.
A reversal movement type does not have a reversal movement type.
you may need to create a new schedule line category in VOV6 to create a new outbound del without order reference with a 653 as movement

Storage location is not updated after posting GR with Mvt type 107(Valuated GR blocked stock)

Hi experts,
Before posting GR through Movement type 107 (valuated GR blocked stock) we can see the storage location field in MIGO screen and able to enter value into this field. But after posting GR when we retrieve the material document we are finding that the field (storage location) is blank, i.e. it's not updated at all. When we check the stock in MMBE we find that no quantity is updated for valuated GR blocked stock.
We want the storage location to be updated while posting GR with 107 Mvt type.
Any idea Please?
Points assured.
Thanks
Amitava

SAP describes it in help.sap.com: Since the material is not to be added to the inventory yet, do not enter a storage location.
If you require a storage location, then I assume that your design does not match with the design of SAP, you are using a function to solve a gap which is not foreseen by SAP for this case.
Especially the 107 is usually representing stock which is still in transfer but you are already the legal owner and have to show the value of those goods in your books.

Return (122) for 107/109 Mov Type

Hello,
After research in SDN forum I didn't get any confirmation on my question. I can I not perform a return to vendor with 122 for movement type 107/109? Effectively is not in OMJJ, but shouldn't be a standard behavior allowed?
Iu2019m able to do it for 101 and 103.
Thanks in advance.
Tania

Hello,
Thanks for your answer but we cannot use 103 and 107 and I will explain way:
We can use CIF or FOB.
In CIF you should use 103/107 because the financial posting is only performed at the 107 when the responsibility of the purchase and transportation is from the vendor/freight forwarder (FF) side until you receive the materials at the final destination.
In FOB is different, we need to use 107/109 because the responsibility of the vendor finish when he deliver the materials at the customs in the origin country. Then FF ship the goods until the final destination. With this incoterm the purchase need to be recognized in financial side and the invoice can be posted to vendor before 109 is confirmed.
So we are not able to change our procedure regarding each movement type choose, because need financial reflection. What I do not understand is why I cannot return materials to 109 with 122.
Thanks in advance.
Best regards.

GL posting during movement type 107 & 108

Similar Messages

Maybe you are looking for