Duplicate GR's in MIGO

Hi All,
How to stop duplicate GR's while doing GR in MIGO.
Kindly suggest.
Regards,
Thiru

Hi,
Follow the simple procedure as described below,it will helps you to stops wrong creation of GRs by users in system.
1 ) Do the MIGO posting by 103 (GR into blocked stck ) . Provide the authorization to stores officer
2) Authorize for Final release of GR to Logistics Incharge ,they will post the Release GR Block stock with Mvt .type-105 which is nothing but the Actual GR Posting.
Hope this will be helpful to you.
Thanks & Regards,
Sandesh Sawant

Similar Messages

User exit needed (Problem related to duplicate batch entry in Migo(GR))

Dear all,
              I need a help from you.we facing problem in Goods receipt in MIGO.
where we want to apply a check on batch which has already been assigned to a raw material in MIGO .we are using manual
batch entry .we don't want to make duplicate entry of same batch
against any material.
I tried to find out the user exit for that but i have not succeed .
what is solution to
avoid duplicate batch entry.

Transaction Code - MIGO                     Goods Movement
Exit Name           Description
MBCF0002            Customer function exit: Segment text in material doc. item
MBCF0005            Material document item for goods receipt/issue slip
MBCF0006            Customer function for WBS element
MBCF0007            Customer function exit: Updating a reservation
MBCF0009            Filling the storage location field
MBCF0010            Customer exit: Create reservation BAPI_RESERVATION_CREATE1
MBCF0011            Read from RESB and RKPF for print list in MB26
MB_CF001            Customer Function Exit in the Case of Updating a Mat. Doc.
No of Exits:          8
USER EXIT
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.sap-img.com/ab038.htm
http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
Rewards if useful.........
Minal

Check duplicate asset number during MIGO

Hi MM/Abap Gurus ,
What user exit can be used to check duplicate asset number during GR. E.g: I have a PO with same asset number for item line 1 and 2. What user exit can be used to set warning msg if duplicate asset number exits during MIGO. Please advise if there any user exit can be used for my requirement?
Thanks
Mitra

Hi Puspha,
Actually, the scenarios as below:
1. PO created with 1 line item with Acc Assign Cat = A and multiple account assignment. Therefore, under the account assignment tab there are duplicate asset number inputted.
2. Hence, when do GR, the system should prompt warning message " Duplicate asset number exists".
Above are the requirement. I need any user exit that I can use in MIGO, where there is checking on duplicate asset number or during the sving of MIGO, I could inforce a logic on the checking.
Your help appreciated.
Thanks

Duplicate tab appearing in MIGO

Hi ,
I am implementing BAdi for the first time. In T code MIGO i want to add a tab in item details. I have used the BAdi MB_MIGO_BADI.
I have followed some thread. In SE 19 edit implementation field i have selected classic BAdi field ( give name zmigo) and under this view in create implementation i have choose the new BAdi radio button ( give MB_MIGO_BADI ).
when i am going for create implementation its one pop up appearing with the fiedl enhancement implementation. After saving it in a package one appears as a pop up with fields BAdi implementation ( new zname given) , Implementation class ( zclass name), BAdi definition ( selected MB_MIGO_BADI ) and then i proceed with creating a empty class. In that class under the method IF_EX_MB_MIGO_BADI~PBO_DETAIL i am calling a sunscreen of my program.
Now the problem I am facing is that in MIGO now instead of one two tab are coming that is one duplicate tab is appearing. Can any one suggest me why this is happening.
Also as i am new to this, it will be very helpful if any one give me idea about the details process i.e. what are parameter to select and edit at the time of creating any implementation and why.
Thanks & Regards,
Monishankar C

Hi,
First can you check the number of active implementatations for the BADI MB_MIGO_BADI, as it is a multiple implementations allowed .
Then inmethod PBO_DETAIL the below part of code is must:
This check is obligatory, otherwise the program flow is incorrect
(If there would be more than one implementation of BAdI MB_MIGO_BADI,
only one subscreen would be displayed).
CHECK I_CLASS_ID = GF_CLASS_ID.
In the above code GF_CALSS_ID is the unique identifier for your implementation.
if still the same problem persists can you share the code you have used in method PBO_DETAIL.
You can refer to the SAP example code also .
Regards,
Deepak.

Duplicate delivery note in MIGO to be restricted

Hi,
In case we enter the duplicate delivery note from the same vendor in the same physical/financial year, should get error/warning message.
Please suggest.
Thanks in advance,
njs

Hi
Use MBCF0002 Customer function exit: Segment text in material doc. item
EXIT_SAPMM07M_001 to give ur coding for duplicate delivery note entry and chk.
Field name i_mkpf-xblnr for delivery note number
Reg
Raja

Duplicate entry at migo

hi expert
AT migo level when i enter delievery note and header text system is accepting duplicate values i.e values which are already entered , but at Miro level system does not allow duplicate values,we have done configuration at MIro so i want system should also stop me when i entered duplicate values at migo level.Please help me in this issue
Regards
Edited by: usmfarhan on Dec 19, 2008 7:20 AM

Hi
The said requirement is well addressed if the material is excisable. Ie; In customizing we can say one gr per excise invoice and the system checks this duplication.
Whereas in MIGO without excise this is not available in STD SAP.
Try enhancement MBCF0002 and component EXIT_SAPMM07M_001 and check for the same. I have used this to check for the posting date of MIGO w.r.t PO.
Reg
Raja

Duplicate GR Posting Control With Respect to MIGO Filed Delivery Note

Hi Team,
Is there any possiblity to check / control GR Posting with respect to the same PO and same delivery note reference.
I have a PO 1000001 with line item 10 with qty 100. I did a MIGO with respect to this PO for 50 qty with delivery note ref DC-53.
When i try to do MIGO with the same PO and same delivery note DC-53 for the balance 50 quantiy,
System should intimate me as warning / error..
How can we acheive this by standard SAP. If not possible by standard SAP wats the alternate.
Vijay

HI Vijay,
It is possible to check warning / error message display of the MIGO bottom of the screen through ABAP delveloper with enhancement (Validation).
After enhancement, MIGO posting is not allow to duplicate DC Ref.no. and also double entry of the same DC ref.no.
Hope, it is useful for you.
Regards,
K.Rajendran.

Duplicate Batch number creation during MIGO wrt PO

Dear al SAP
We have activated batch management at material level and set external number range. During MIGO say for the first line item, I have entered external batch number as 123. If I give the same batch number for the second line item of the same material code, system should throw an error message.
Pls explain in detail SPRO setting required for this.

In Logistics General -> Batch Management -> Creation of New Batches -> Define Batch Creation for Goods Movements select the option "E" Manual and check against external number range

Error during MIGO

Dear all,
while doing MIGO for the PO i am getting following error
"Check table 169P: entry PICT does not exist
Message no. M7001"
In table 169P the entry PICT is missing..
PICT is my compnay code.
Also in GR Excise tab " BED,SED, AED for excise item is zero. "
But in PO in INVOICE tab against tax code system is showing the correct values of BED.
wHERE Should i check for same.
Best Regards,
Venu

Hi,
Go to SPRO > MM > Logistics Invoice Verification > Incoming Invoice > Here configure following
- Tax Treatment in Invoice Reduction
- Maintain Default Values for Tax Codes
- Configure How Exchange Rate Differences Are Treated
- Configure How Unplanned Delivery Costs Are Posted
- Edit PO Supplement Text in Invoice Verification
- Activate Direct Posting to G/L Accounts and Material Accounts
- Set Check for Duplicate Invoices
And then check Table T169P, it will have aal the parameters mainatined for Invoice verification for compnay code. Then do MIRO.
Aslo go to OBCL and mainatin input tax code of Zero % for compnay code.

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?

Avoid duplicate batch (batch managment)

dear all,
We are facing problem related to batch managment .we are using manual batch entry .we don't want to make duplicate entry of same batch (which have already assign to material) against any material.what is solution to avoid duplicate batch entry.
can u tell me the settings and any user exit in which we can avoid the duplicate batch.
regards

Hi hema,
in our scenario user manually enter batch of raw material in MIGO when we do good recipte in MIGO againts purchase order we enter batch manually.but we need that a batch which has already assign to raw material can not be assign again .if user enter the previous batch then system gives a error that batch has already exist.
may be u know the prob

BADI for MIGO update - Data not getting saved in table sometimes

Hi,
This is regarding automatic update of material document number to our Z Table for Gate entry in MM.
Steps for Generating GR throu2019 MIGO:-
1) the user has to key in the gate entry number and plant,
2) then after giving i/p values the user has to click the save button,
3) MIGO number is generated by the system which is updated in gate entry header table.
For updating the MIGO number BADI is used . But some time the system is not updating the GR number in gate entry header table.
Can we use COMMIT WORK statement in BADI? Hope its not advisable to use it.
What else can we do if data is not getting stored in table while updating throu2019 BADI?
Inside the Method : IF_EX_MB_MIGO_BADI~POST_DOCUMENT the below code is written,
Instead Of Updating The Gate Entry Item Table Now
Update The Gate Entry Header Table. Update The
Value Of The Field MBLNR With Current Document Number
Generated Updating the header table ZMM_GATE_ENTRY
    SELECT SINGLE *
      FROM ZMM_GATE_ENTRY
      INTO WA_ZMM_GATE_ENTRY
     WHERE GATEENTRYNO EQ GS_EXDATA_HEADER-GATEENTRYNO
       AND WERKS       EQ GS_EXDATA_HEADER-WERKS
       AND GYEAR       EQ GS_EXDATA_HEADER-ENTRY_DATE+0(4).
Check To Ensure That Once A Gate Entry Number
Is Associated With A GR It Cannot Be Reused
    IF WA_ZMM_GATE_ENTRY-GR_NUMBER IS INITIAL.
      WA_ZMM_GATE_ENTRY-REFERENCE = GS_EXDATA_HEADER-REFERENCE.
      WA_ZMM_GATE_ENTRY-REFWERKS = GS_EXDATA_HEADER-WERKS.
      WA_ZMM_GATE_ENTRY-GR_NUMBER = IS_MKPF-MBLNR.
      WA_ZMM_GATE_ENTRY-GR_YEAR   = IS_MKPF-MJAHR.
MODIFY ZMM_GATE_ENTRY FROM WA_ZMM_GATE_ENTRY .u201Dupdating the workarea
u201CThe above modify stmt updates data sometimes and does not updates the data sometimes
    ELSE.
      MESSAGE E901(ZMM) WITH GS_EXDATA_HEADER-GATEENTRYNO WA_ZMM_GATE_ENTRY-GR_NUMBER.
    ENDIF.
Plz suggest some soln?
Regards,
P.S.Chitra

Hi,
This is regarding automatic update of material document number to our Z Table for Gate entry in MM.
Steps for Generating GR throu2019 MIGO:-
1) the user has to key in the gate entry number and plant,
2) then after giving i/p values the user has to click the save button,
3) MIGO number is generated by the system which is updated in gate entry header table.
For updating the MIGO number BADI is used . But some time the system is not updating the GR number in gate entry header table.
Can we use COMMIT WORK statement in BADI? Hope its not advisable to use it.
What else can we do if data is not getting stored in table while updating throu2019 BADI?
Inside the Method : IF_EX_MB_MIGO_BADI~POST_DOCUMENT the below code is written,
MODIFY ZMM_GATE_ENTRY FROM WA_ZMM_GATE_ENTRY .u201Dupdating the workarea
u201CThe above modify stmt in code updates data sometimes and does not updates the data sometimes
Moderator message: duplicate post locked.
Edited by: Thomas Zloch on Aug 10, 2010 11:33 AM

Duplicate IR-L document.

Hi
We are in SAP 4.7. Once the Invoive verification document is posted for all the items for a PO with MIGO system is allowing to post one more document for the same PO. We have checked check duplicate invoice in teh vendor master which should prevent posting duplicate Invoice during MIRO. Is there any SAP notes to be implimented in our system to prevent duplicate invoice. or please suggest the User exit where we can code to prevent duplicate invoice during MIRO.
Regards
Jai

Hi Jaichandra
Clarify whether the second document you are posting has the following same as the original one
Vendor
Currency
Company code
Gross invoice amount
Reference document number
Invoice doc. date
If there is slight difference (for ex. "," or ".") The system will allow the second document
Check whether the error message is set as error or just warning, if warning user may not have ignored.
Also If you are uploading the batch file then you need to check if there is any error message in SM38
Regards
Deepak

Problem in Set Check for Duplicate Invoices

Hi,
I have did all the required setting s for check duplicate invoice , but when i do miro , its not giving any error or warning msge.. i did all the config as per blw link..
FYI- in migo, i have entered the 3434 as a invoice ref # in delveriy note column and while doing miro , i have entered 3434 in ref column and give the 3434 as a dlvery note # in item tab .. but its not giving any error?
Pls guide, where the mistake has gone wrongly??
Problem in Set Check for Duplicate Invoices
Edited by: UJ on May 15, 2009 1:45 PM

Hello,
Hope you have done all the required configurations for the checking of double invoice and ticked the vendor for the double invoice checking in vendor master record.
You have to understand the way the system does the double invoice check.
As per the configuration, if the system identifies an invoice for a vendor whose double invoice check is activated, at the time of MIRO, system will update a separate table.
So system will check for the double invoice entry among the invoices entered after making the tick in the vendor master.
i meant to say that, if you are introducing this double invoice check in between the transactions, the check will be valid only for the invoices entered after the activation of double invoice check.
Regards

OSS Note for MIGO "Update terminate (SAPSQL_ARRAY_INSERT_DUPREC)"

Dear all
I am facing problem during MIGO GR reference Others, MVT 561.
Upon clicing Button: Save, I face 2 types of errors intermittently
1. Material document is saved and generated but when comes to displayed, it will say "Document 4900496xxx does not exist in calendar year 2009" And I check in Table: MKPF and it does not exist at all
2. I am not able to save it and face this termination error:
The ABAP/4 Open SQL array insert results in duplicate database record
What happened?
Error in ABAP application program.
The current ABAP program "SAPLGLIU" had to be terminated because one
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and adminis
termination messages, especially those beyond their normal deletion"
I have done my investigation and the number range uder FBN1 for this MVT 561 under this Company Code and Year has been maintained.
Can anyone advise me the OSS note to solve it? I cannot find a direct OSS note on it to solve this.
Thanks.
Edited by: Daimos on Oct 26, 2009 7:58 AM

Sorry Jurgen
I have posted so many material documents using MIGO to test it out and try to update my OMBT there so many times until I lost track what is the current number range when I wrote my question here.
I have read that thread you posted regarding the ST22 analysis [Solution from Jurgen|Document does not exist after creation of PO; . I exported them to HTML and did a detail checking, and I find out it is FI GL there did not update the number range properly which in turns cause my GR to have problems.
Below is my analysis and learning to share with others:
1. Ask the ABAPER to find out which record value the system trying to insert. Copy down this number.
2. Check the OMBT value of Current Number.
3. Then use the MFPK Table to search the latest Number Range.
4. Try to check if the record value trying to insert already exists in Current Number. Normally, it will exist and that is why
    system prompt "insert duplication".
5. Then check if the record value trying to insert already exists in MFPK Number. Normally, it will exists it will exist and that is
    why system prompt "insert duplication". (There can be situation that the Current Number is lower than the MFPK Number,
    but it rarely happen).
6. Replace the Current Number to be the Next Number of MKPF largest Number. Save and it should work.
7. If it is not work, please create a material which is non valuated and perform GR, if GR can be done and we can display
    material doc, it means the error is caused by the FI GL number range error.
8. There can be other issues such as activation of user exits and other.
Jurgen, I got one more question to ask you. I have tried to replace the current number with the largest number of MKPF without + 1. It can solve my problem.
But I wonder why SAP Notes and you suggest us to replace Current Number with largest MKPF value PLUS 1?
Please advise.
Thanks.
Edited by: Daimos on Nov 2, 2009 8:41 AM

Duplicate GR's in MIGO

Similar Messages

Maybe you are looking for