Validate delivery note number during MIGO

Hi everyone,
Pls. I need to validate the delivery note number during MIGO because I need to avoid duplicates entries.
Thanks for help.

for this you have to find the user exit through which you can validate the delivery note number, but in some scenario it is not feasible as some companies are sending the partial delivery under same delivery note number so if this is not the case then ask the ABAP to find a user exit through which you can validate the delivery note number.
regards,
qsm sap

Similar Messages

MM - User exit to validate delivery note number

Hi everyone,
pls. I need help to find the user exit just to validate the delivery note number during MIGO.
Thanks a lot !
Regards.

>
Himanshu Verma wrote:
> Hi
> Try with BADI: MB_MIGO_BADI Method PAI_HEADER> structure GOHEAD >LFSNR
>
> regards,
> Himanshu
himanshu,
istead of throwing any badi, bapi, enhancement or exit at such a question ... have you ever tried to ask yourself whether you are inventing the wheel again (and for the umptiest time) ... because maybe the solution lies in configuration? how can you come up with a BADI without knowing the process?

Delivery Note Number should not repeat again during MIGO

Hi Friends,
My client has a requirement to validate the Delivery note filed in the MIGO screen, i.e., the system should allow the user to enter a delivery note number once entered already during goods movement through MIGO. Is there any way that this can be done?
Regards
Guru Prasad

Thanks for the reply Ganesh.
Explaination of the requirement:
During goods receipt the user is supposed to enter the delivery challan number of the vendor in the filed "Delivery Note" in MIGO header. If the user by mistake types the same delivery note number again while posting goods reciept for the same vendor in future, the system should throw an error. If there is any user exit or if it can be done through some development kindly suggest the procedure for the same.
I also checked for the standard system messages, but couldn't find any.
Rgds
Guru Prasad

Different Migo posted on the same delivery note number with the same vendor

Hi Experts,
We are facing a peculiar problem while saving migo in the sytem. The system is allowing to post more than one migo with the same delvery note number with the same vendor code in the same financial year. Ideally shystem should give some informative / error messgage during saving one migo. In our company, we capture party invoice number in the delivery note option. Our problem is more promintent if the vendor is non excisable.
How to check this problem.
Regards
GR

Hi,
In Standard SAP, no check is available on "Delivery Note" field for duplicacy. This is only available for "Reference" field in MIRO.
If you want to have a check on "Delivery Note" field in MIGO then go for some ABAP Development using BAdi or Enhancement Spot "MB_MIGO_BADI".

ERS user exit, pass Delivery note(LFSNR) in MIGO to Reference(XBLNR)in MIRO

Hi Experts,
I need to assign Delivery Note(LFSNR) in MIGO, to field Reference(XBLNR) in MIRO. that means "Reference " field must contain the delivery note information instead of Invoice doc number.
how can i use component MRMH0001.where can i use?
i am new to user exits.
please help me. i need logic and steps.
Thanks in advance
Reward points will be given.
Srinu

hi
Overview
R/3 provides three "customization spots" that allow you to enhance FI/CO features without modifying the standard code. Although often collectively referred to as "user exits," two of the three have different names. SAP Enhancements are used to expand the standard functionality within SAP. Enhancements use function modules and are called from the standard SAP code. Each module in the system has a set of delivered enhancements that help companies expand the standard functionality where they need it. Enhancements were new in release 3.0.
The Open FI Interfaces or Business Transaction Events are also used to expand the standard functionality within SAP. These events are defined in the IMG. Business Transaction Events were new in release 4.0. They are not available for all modules and are not called on all integrated transactions into FI as of release 4.5B. This will change with each release and should be retested.
The older User Exits in FI/CO are "Z" programs that are defined in table T80D for client-dependent user exits, and in table T80I for client-independent user exits. These are also used to expand the standard functionality within the FI/CO modules. These User Exits have been available since the early releases of SAP. All of these FI/CO User Exits are listed in this document in the Configuring User Exits (Older). The list is included because these User Exits are not a part of the Enhancements or Business Transaction Events and do not have an Info System for searching.
Benefits
Standard SAP functionality can be enhanced without modification to the standard code.
Upgrades do not erase the functionality and it does not have to be re-transported or re-entered into the system. The enhancements should be thoroughly tested when upgrading to ensure the system will still work as implemented.
Configuring SAP Enhancements
Basic Steps in Configuring an Enhancement
Find the appropriate Enhancement.
Enter the ABAP code in the "Z" program within the function module.
Create a project.
Add the Enhancement to the project.
Activate the project.
Example Business Scenario for Enhancements
Company A has a requirement to validate all customer master records created with a U.S. address. The U.S. entity reports on the industry field on the customer master. This is only a U.S. requirement and should not be required for the other countries, so the field status would not work. To accomplish this requirement, Company A will need to set up an Enhancement for the customer master transaction. The necessary steps are detailed below with screenprints. This example was configured in a 4.6C system.
to find the suitable exit for ur requirements check the following program
Hi
Find the available exits with the following program:::
*& Report ZFINDUSEREXIT
report zfinduserexit.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
select single * from tadir where pgmid = 'R3TR'
and object = 'PROG'
and obj_name = tstc-pgmna.
move : tadir-devclass to v_devclass.
if sy-subrc ne 0.
select single * from trdir where name = tstc-pgmna.
if trdir-subc eq 'F'.
select single * from tfdir where pname = tstc-pgmna.
select single * from enlfdir where funcname =
tfdir-funcname.
select single * from tadir where pgmid = 'R3TR'
and object = 'FUGR'
and obj_name eq enlfdir-area.
move : tadir-devclass to v_devclass.
endif.
endif.
select * from tadir into table jtab
where pgmid = 'R3TR'
and object = 'SMOD'
and devclass = v_devclass.
select single * from tstct where sprsl eq sy-langu and
tcode eq p_tcode.
format color col_positive intensified off.
write:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
skip.
if not jtab[] is initial.
write:/(95) sy-uline.
format color col_heading intensified on.
write:/1 sy-vline,
2 'Exit Name',
21 sy-vline ,
22 'Description',
95 sy-vline.
write:/(95) sy-uline.
loop at jtab.
select single * from modsapt
where sprsl = sy-langu and
name = jtab-obj_name.
format color col_normal intensified off.
write:/1 sy-vline,
2 jtab-obj_name hotspot on,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
endloop.
write:/(95) sy-uline.
describe table jtab.
skip.
format color col_total intensified on.
write:/ 'No of Exits:' , sy-tfill.
else.
format color col_negative intensified on.
write:/(95) 'No User Exit exists'.
endif.
else.
format color col_negative intensified on.
write:/(95) 'Transaction Code Does Not Exist'.
endif.
at line-selection.
get cursor field field1.
check field1(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
write the code in the right form and check by keeping a break point
HI
To search for a badi, go to se 24 display class cl_exithandler.
double click on method get_instance, get a break point on case statement.
execute and start the required transaction in new session.
look for variable exit_name. It would show the available badi's.
also check the following links
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.planetsap.com/userexit_main_page.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
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
Please do reward if useful
Regards
Dinesh

Delivery Note NUmber

When i try to post MIGO i am getting the following error message:
Check the Delivery Note Number
Message no. ZMM01000
Please help me to solve this issue
Thanks & Regards,
Pioneer

HI
Is it that you are not filling in the delivery note number which sems it is mandatory from your message ro is it required that you have to fill in a particular pattern, just check this out. Refer your old GRN documents for MIGO and analyse how they have been carryign out if not successful you can go for de_bugging to find out the reason as this is a custom designed message developed by the client.
Regards

MBXA and delivery note number.

Hi,
if a delivery note has been created with a mistake what do I do?
The material document is being reversed but when printing a delivery note for another material
system saves with a new delivery note number instead of the previous.
Best regards

hi,
spro --> materials management --> inventory mangement and physical inventory --> Number range assignment -->
under this path you can maintain number ranges for accounting documents and material documents.
1. accounting documents (OMBA)
2. Material documents (OMBT)
3. Reservations ( OMC2)
4. GR/IR slip numbers. ( OMC1)
hope this may help you,
Regards,
Srinivas

How to fetch delivery note fiedl from MIGO

Hi,
how to fetch delivery note field from MIGO.
Regards
Mave

see it is not the exact field.
Regards
Mave

Report: Acc doc with delivery note number

Hi,
Is there any report where we can have the accountting document number and the corresponding
delivery note number?
I can understand, the delivery note should be ideally put in the reference field of the MIRO screen. But in our scenario it is not mandatory. So there are cases where the reference field and the actual delivery note of GR differ.
So the need is for a report of the accounting document and the actual delivery not (which we can in the MIRO screen item level)
Please guide...
Regards,

Hi ,
Try with Table RBKP incase of Logistics Invoice Verification.
You may also try with BKPF for Conventional Invoice Verification.
Regards
Ramesh Ch

Supplier delivery note number

Hi,
I'd need to extract, using SQVI, the supplier delivery note number starting from part number and/or supplier and display the main information (supplier, supplier delivery note number, part number, posting date, supplier delivery note date, quantity). Which are the right tables to use?
Thank you in advance!

Hello,
By part number I assume you mean material? Or do you mean MPN?
In case its just material:
Inner join of MSEG, M_MEBEX and MSEG should provide you all the details you require:
1) Material - on the selection screen - MSEG - MATNR
2) Supplier - on the selection screen - MSEG - LIFNR
3) Supplier Delv note - M_MEBEX - XBLNR
4) Posting Date: MSEG - BUDAT_MKPF
5) Document Date / Supplier Note date - MKPF- BLDAT
6) Delv note quantity - MSEG - LSMNG

Validate the delivery note i tcode MIGO

Hi Experts,
In MIGO Tcode ---> Delivery Note is taking the same number at any number of times for the same Purchase Order .
But Excise Invoice if u enter the same it will rise the error message .
like that i want to validate the Delivery Note , IF we enter second time it has to rise the error message .
plz guide me on this.
Regards,
Hari.

Hi,
I think what you want to do is to restrict users fro entering the same delievry number multiple times, check exit MBCF0002 here in the importing parameter I_MKPF you should get the current delievery number using this you should be able to keep a check for the same.
Regards,
Himanshu

Excise invoice not capturing during migo?

when I tried to capture the excise invoice during Migo. I am unable to select the capture only option. it is automatically selecting "refer only excise invoice"? how to solve this problem.

Dear,
I think you have not maintain Excise data
T.code
J1ID - Excise rate maintenance
Maintain Chapter Id,
Maintain Mateial & Chapter id combination.
CENVET Determination (If material is CENVETABLE)
Vendor Excise Detail
Excise Tax Rate.
Hope above will useful.
GOPAN.

Make to Order 543 E is not picking during MIGO.

Dear Friends,
I am trying to perform Goods receipt against a Subconctracting PO, in a MTO scenario. The components are linked to Sales ORDER (Special Stock u2013 E). I have maintained u20190u2032 in the Individual / Coll requirements field in the MRP 4 view of the component.
So after creation of PO(Subcon), I am trying to perform MIGO u2013 without issuing components to vendor as 541/E movement type for componenets is not allowed in standard.
While performing MIGO I am getting the error no stock available with vendor, the system is trying to trigger 543/O movement type whereas I am expecting 543/E to be triggered for the components.
Can anyone sujjest if there is a way by which the MIGO should trigger 543/E during MIGO.
MM Consultant, needs help regarding
Regards,
Veeran

Hi,
So after creation of PO(Subcon), I am trying to perform MIGO u2013 without issuing components to vendor as 541/E movement type for componenets is not allowed in standard.
you are correct special stock can not issue to vendor directly
so you have to transfer this stock to own stock first through 411E movement type then issue component to vendor through 541
then receive stock by 101 O
Regards
Kailas Ugale

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

Make Delivery note mandatory in MIGO

Hi Friends,
                          My client want to make mandatory for Delivery note field in the Goods reciept in MIGO. can you please explain how to do this?

Hi K.Prasanna,
Gothrough the following setting ,
SPRO-->Materials Management -->Inventory management > Settings for Enjoy Transactions> Field selection for MIGO
                                         Input           Required       Disappear        Hide          HILI
Delivery Note                                            X
Then try to Create GRN.......
Thanks and regards.
R.Ramanarao

Validate delivery note number during MIGO

Similar Messages

Maybe you are looking for