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

Similar Messages

BAPI_GOODSMVT_CREATE is not working for movement type 701 in MIGO

Hi gurus
Can anybody help to track that bapi: BAPI_GOODSMVT_CREATE is not working for movement type 701 for MIGO Transaction.

call this standard BAPI, AND EXECUTE IN SE37
""Local Interface:
*" IMPORTING
*"     VALUE(GOODSMVT_HEADER) LIKE BAPI2017_GM_HEAD_01 STRUCTURE
*"        BAPI2017_GM_HEAD_01
*"     VALUE(GOODSMVT_CODE) LIKE BAPI2017_GM_CODE STRUCTURE
*"        BAPI2017_GM_CODE
*"     VALUE(TESTRUN) LIKE BAPI2017_GM_GEN-TESTRUN DEFAULT SPACE
*"     VALUE(GOODSMVT_REF_EWM) LIKE /SPE/BAPI2017_GM_REF_EWM STRUCTURE
*"        /SPE/BAPI2017_GM_REF_EWM OPTIONAL
*" EXPORTING
*"     VALUE(GOODSMVT_HEADRET) LIKE BAPI2017_GM_HEAD_RET STRUCTURE
*"        BAPI2017_GM_HEAD_RET
*"     VALUE(MATERIALDOCUMENT) TYPE BAPI2017_GM_HEAD_RET-MAT_DOC
*"     VALUE(MATDOCUMENTYEAR) TYPE BAPI2017_GM_HEAD_RET-DOC_YEAR
*" TABLES
*"      GOODSMVT_ITEM STRUCTURE BAPI2017_GM_ITEM_CREATE
*"      GOODSMVT_SERIALNUMBER STRUCTURE BAPI2017_GM_SERIALNUMBER
*"       OPTIONAL
*"      RETURN STRUCTURE BAPIRET2
*"      GOODSMVT_SERV_PART_DATA STRUCTURE
*"        /SPE/BAPI2017_SERVICEPART_DATA OPTIONAL
*"      EXTENSIONIN STRUCTURE BAPIPAREX OPTIONAL
*"      GOODSMVT_ITEM_CWM STRUCTURE /CWM/BAPI2017_GM_ITEM_CREATE
*"       OPTIONAL
call function 'BAPI_GOODSMVT_CREATE'
    exporting
      goodsmvt_header         = goodsmvt_header
      goodsmvt_code           = goodsmvt_code
      testrun                 = testrun
      goodsmvt_ref_ewm        = goodsmvt_ref_ewm
    importing
      goodsmvt_headret        = goodsmvt_headret
      materialdocument        = materialdocument
      matdocumentyear         = matdocumentyear
    tables
      goodsmvt_item           = goodsmvt_item
      goodsmvt_serialnumber   = goodsmvt_serialnumber
      return                  = return
      goodsmvt_serv_part_data = goodsmvt_serv_part_data
      extensionin             = extensionin.
commit work.
hi, rewards point, if this is useful,
regrds
karthikeyan

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

MIGO - GR - Others -- Serial Number Not saved for Movement Type : 561

Hello,
I am trying to post good receipt-other ( for movement type 561) using MIGO transaction. I have specified all required data.
Also depending on the item qty., I entered serial number in serial number tab.
Its creating document successfully. However if I try to display same document using MIGO, serial number is missing.
I tried to debug the code and I realized its not saving serial number itself.
For other movement type its creating document with correct serial number.
If I repeat same process using same data using transaction MB11 its posting successfully and I can see serial number using MIGO transaction as well.
One more thing which I've noticed is when I post document using MIGO, Account assignment details are missing. However with MB11 I can see account assignment data too.
Would be really appreciated if someone can help me on this. I dont know If I'm missing any configuration part here.
Thanks & Rgds,
Nilesh

Any help Experts?
Nilesh

STO delivery should not happen for shelf life expired material

Hai all,
When we are doing PGI for STO-PO. shelf life expired material should not do the delivery.The system should give the error message. but in our system when we do PGI the shelf life expired material is deliverying.
how do we maintain the error message when we doing PGI.
Edited by: hemanth s on Sep 12, 2008 9:37 AM

Hi,
In Inventory management there is a which helps you "Set expiration Date Check". This allows you to make sure that the shelf life of the material is checked before delivery.
In Material master, you would need to enter relevant information in the "Plant Data/Stor. 1" tab page (Min remaining shelf life, total shelf life). Also in IMG settings, you need to activate the check for both Plant and movement type. The path is as follows:
IMG Settings > Material Management > Inventory Management and Physical Inventory > Goods Receipt > Set Expiration Date Check. TCode: OMJ5
Cheers.
Edited by: Sowmya Mohan on Sep 15, 2008 8:43 AM

What is d BAPI for reversal of Good Receipt Note(GRN) for movement type 102

Hi ABAPers,
I have got requirement like this , I have done Goods Receipt Note (GRN) based on Purchse order Number using '.BAPI_GOODSMVT_CREATE' with 101 movement type.
But now my requirement is reversal of good receipt note(GRN) based on Material Document Number (or) Purchase Order Number with 102 movement type. what is the bapi name i need to use. and i need to give reason for the reversal of GRN.
please tell me the field name for reason in bapi.
i have searched in the net, but i could not get proper answer to this isse.
Highly appriciate who gives answer as early as possible. I need to complete this task EOD. please give replies.
Thanks & Regards,
Vinay Kumar.

Hi,
If your material document has specific movement type i.e. 101, if you cancel document using BAPI_GOODSMVT_CANCEL, it automatically picks associated movement type 102 defined in customizing setting, you don't need to pass 102 explicitly while cancelling.
I have not seen reason code in this bapi, but it is required to pass reason code then you may try transaction code MBST using BDC.
Thanks,
Ashok Veer

Profit Center not updated for mov type 511

When we are doing the goods receipt through transaction MIGO with mov
type 511 (Receipt of delivery without charge) as 2nd line item along with
mov. Type 101 as first line item, profit center document is not getting
updated for 2nd line item (GLPCA-MSL), but for 1st line item (mov type
101) profit center getting updated.
If we are doing the GR with movement type 511 alone, profit center
(GLPCA-MSL) updated correctly.

hi,
As per your error i might understand.
please check for second line item Item okay is marked or not.
if its 511 then please check whether Pricing control in MA-master whether its a Moving average or Standard price.
as you said for singular 511 profit center gettng updated then you can very well compare to GR's.
Regards,
Ninad Kshirsagar

Some key figure are not update for movement type 101

Dear All,
I have done load for Inventory and now i am finding that for some material the with movement type 101 the key figures are not getting populated, for these materials the values in characteristics is getting populated fine.
I have loaded the data according to stranded procedure in "How to Load...."
I have checked the values of material in R3 and it is there.
Example of the record::
Material    Plant Movement type Calender Day    quanity Base Unit
10101      01       350                     01.02.2006     20             KG
10101        01       101                     05.07.2006                      KG
10101         01      101                      10.07.2006                      KG
The Quantity is not appearing in second and third record.

Hi,
Please check whether you have set ''Rule groups'' at transfermation level . There you can set the conditions like materials having movement type X can be updated to one Key Figure and material having movement type Y can be updated to another Key figure.
Please check whether you have set this option at transfermation level.
For example, may be in your case materials from different plants are updating to different key figure.
Thanks,
Edited by: kavitha nagandla on Feb 17, 2010 7:19 AM

Classification Data (SLED) not Updated for Movement Type 561

Dear All,
I have noticed that after uploading the opening stock with movement type 561, the Classification data (Date of manufacture & Shelf Life expiry date) which was captured in MB1C is not updated in the batch master in Classification Tab.
Is this standard SAP behaviour for 561 movement type? Or is there any config is missing?
Please advise.
Regards,
Suresh.

Hi Suresh,
For your question I understand that while uploading the initial balances, system didn't ask you for the Manufacturing date or total shelf life date. Following is the solution:
You have to maintain "Check SLExpir.date" and "Classif.batches" indicators for the movement type 561 or any movement type you required. This customization can be perform through SPRO>>MM>>IM>>Goods Mvt. and mvt. No.
Also activate SLED at plant level in customization.
Regards
SAK

Inspection lot not created for movement type 101 O

Dear all,
. We are creating a PO (ME21N) indicating in the view u201CDelivery addressu201D the same vendor than the PO and the flag u201CSubcontracting vendoru201D
. The material has in MM02 the inspection type 0130 Receiving Insp. from External Processing.
. There is QM plan with the Usage 53 GR external process.
. When we do MIGO 101 u201CSpecial Stock Indicatoru201D O Parts prov. Vendor. The system doesnot create an inspection lot.
But in MMBE the stock appears in u201CStock Provided to Vendoru201D u201Cquality stocku201D. The customer wants to control that stock in u201CQuality inspection:
Can somebody help me?
regards
shilpa

SPRO - QM - Quality inspection - Inspection lot creation - inspection of goods movement - Deactivate Quality Inspection for a Movement Type
Check in this setting, whether QM is deactivated for 101 and special stock O

Without QM module, for materials is in Quality, Miro should not happen

Hi All
without QM module,
After GRN the material is going to quality inspection.
For such Purchase Orders, I want to restrict the invoice verification process.
system should give error message.
Regards
M S K

Hi,
Through QM module you can block the invoice for payment but you can't stop the posting.
Do the settings in SPRO > Quality Management > QM in logistics > QM in procurement > Define delivery block, here block invoice option is there.
But in standard SAP, you can't control the Invoice posting through QM.

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?

Cross Company MIRO Transaction - BSEG-TXGRP Not Valued for Account Type "S"

I am working with the ABAP group to create tax reports for audits and sales tax charged by vendor. I am basically wanting a line item report of all purchases along with any tax applied to each line. Therefore, I am, for the most part, using tables BKPF, BSEG, and BSET. For our US transactions, we have one company paying the invoice on behalf of all other US companies. Essentially, every transaction is a cross-company transaction. The problem is I am having a hard time tying BSEG to BSET by line item. For FB60 transactions, I can tie BSEG-TXGRP to BSET-TXGRP; however, for MIRO transactions, BSEG-TXGRP is not valued for Account Type "S" (GL Accounts). Any ideas? I could not find a note to capture this issue. There was a note, but it was with regard to Account Types "D" and "K" I believe, vendor and customer accounts.
Any help would be greatly appreciated.
Thanks,
Deanna

So,
Did you ever resolve this. I have the EXACT problem right now. Inter-co. MIRO documents only getting TAXGRP popuplated for Original Co. Document (not cross-co. document).
Thanks,
- Tim

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.

I keep getting this message and PSCC will not open:Unable to start your subscription for Adobe Photoshop CC. I keep trying again with no results. I am on automatic pay system. This should not happen.

I keep getting this message and PSCC will not open:Unable to start your subscription for Adobe Photoshop CC. I keep trying again with no results. I am on automatic pay system. This should not happen.
I had it open a few minutes ago. Closed it and went to reopen to no avail. How can I open and continue to work?

Does your Cloud subscription properly show on your account page?
If you have more than one email, are you sure you are using the correct Adobe ID?
https://www.adobe.com/account.html for subscriptions on your Adobe page
If yes
Some general information for a Cloud subscription
Cloud programs do not use serial numbers... you log in to your paid Cloud account to download & install & activate... you MAY need to log out of the Cloud and restart your computer and log back in to the Cloud for things to work
Log out of your Cloud account... Restart your computer... Log in to your paid Cloud account
-Sign in help http://helpx.adobe.com/x-productkb/policy-pricing/account-password-sign-faq.html
-http://helpx.adobe.com/creative-cloud/kb/sign-in-out-creative-cloud-desktop-app.html
-http://helpx.adobe.com/x-productkb/policy-pricing/activation-network-issues.html
-http://helpx.adobe.com/creative-suite/kb/trial--1-launch.html
-ID help https://helpx.adobe.com/contact.html?step=ZNA_id-signing_stillNeedHelp
If no
This is an open forum, not Adobe support... you need Adobe staff to help
Adobe contact information - http://helpx.adobe.com/contact.html
-Select your product and what you need help with
-Click on the blue box "Still need help? Contact us"

MIRO should not happen for Movement Type 107

Similar Messages

Maybe you are looking for