User Exit available for basic inbound idoc type MBGMCR01 in SAP R/3

HI,
We are looking for the User Exit for BsicIdoc MBGMCR01.
When we create confirmation in EBP, this idoc gets triggered from EBP to R/3 to create goods receipt material document.
Regards,
Nikhil.B

Hi
<b>Please go through the following links, for all the required details -> </b>
GRN IDOC Transfer to ERP - MBGMCR01 ( 2 IDOCS created)
Re: GR IDOC Number
Re: Confirmation screen field to be mapped to backend field
Re: Delete goods confirmation in SRM3.0
Re: Not able to change confirmation date
Confirmation against Backend PO for SRM@ERP2005
Re: SRM Confirmation # in R/3
Re: Goods Confirmation not transferred to backend!!
Hope this will definitely help.
Regards
- Atul

Similar Messages

User exit / BADI for the MATQM01 IDOC type?

Hello,
I am working on a Material Master conversion that will need to include the Material Inspection Setup. Using BD10 to send the material 'In Full' generates these MATQM01 IDOCs successfully. As part of this conversion I need to map some old plants to new plants.
Is there a user exit or BADI within the MATQM process that I can use to accomplish this?
The BADI/Exits for BD10 do not access the MATQM data. There are no exits listed for QL11 which is the standalone code for creating MATQM idocs.
Any help would be appreciated!
John

Thank you guys for the replies. I will try the Rules and Filters approach to implement the logic I require. If the logic is too complex then I will go with the z-copy of QL11.
Thanks!

BADI / USER-EXITS available for Txn. QE01

Hi Experts,
Could anyone please suggest appropriate BADIu2019s and user-exists available for Txn. QE01 to send the status change.
Our requirement is to send a mail notification to the user when all the result recording status of the inspection characteristics turn to 'complete'
In Tx QE01 the inspection results are recorded for each inspection characteristics.When results recorded for all the characteristics the user will close the insp. characteristic and the status will change to 'complete' then needs a mail notification so that user decision (UD) can be performed for the inspection lot.UD (Txn QA11) will be performing after result recording.
Any suggestion will be appreciated.
Thanx and Regards

Hi ,
Please check below BADI and User exits .
Bus. add-in name     Description
QE_RESULT_VALUATION   "Valuation of Single Values
QE_SAVE              "Save Results
QEEM_SUBSCREEN_5000   "EE: BAdI Subscreen for Display of Data on Screen 5000
QM_IDI_INSPPOINT     "Changing of Inspection Point Processing in IDI and BAPIs
QM_INPUT_PROCEDURE   "Input Processing
Exit name     Description
QEEM0003     "User exit: add. functions after valuating insp. characs
QEEM0004     "User exit: add. functions after valuation of partial samples
QEEM0006     "User exit: add. functions after closing inspection characs
QEEM0007     "User exit: add. functions after completing partial samples
QEEM0011     "User exit: add. functions before valuating insp. characs
QEEM0012     "User exit: add. functions before valuating partial samples
QEEM0015     "User exit: add. functions after entering individual results
QEEM0020     "User exit: additional functions after entering the inspector
QEEM0021     "User exit: additional functions for user key +US1
QEEM0022     "User exit: additional functions for user key +US2
QEEM0023     "User exit: additional functions for user key +US3
QEEM0024     "User exit: additional functions for user key +US4
QEEM0029     "User-Exit for Characteristic Overview Subscreen
QEEM0030     "User-Exit for Subscreen: Characteristic Single Screen
QEEM0031     "User-Exit for Table Structure with External Numbers
QEEM0032     "Presentation of the characteristic text in the logon lang.
QEEV0003     "Determination of order type for print
QIST0002     "Generating MATERIAL_DATA for QM STI Interface
QIST0003     "Generating VENDOR_DATA for QM STI Interface
QIST0004     "Generating CHARACTERISTIC_HEADER for QM STI Interface
QIST0005     "Generating CHARACTERISTIC_QUANTITATIVE for QM STI
QIST0007     "Generating SAMPLE_HEADER for QM STI Interface
QIST0008     "Generating RESULTS_ADDITIONAL_DATA for QM STI
QIST0009     "Generating RESULTS_QUANTITATIVE for QM STI Interface
QIST0010     "Generating REPORT_HEADER for QM STI Interface
QIST0011     "Generating METHOD_DATA for QM STI Interface

Segment E1IDBW1 is missing for the inbound idoc type PAYEXT

Hello,
the above segment is missing in the inbound idoc - basic type pexr2002.
I have checked in TC-we30 and its available there.
but still the idoc is getting generated without this segment.
can someone suggest.
thanks
Arun

Hi All,
I have a similar query to that of Penny. We are able to get the standard IDOC to generate with segment E1IDBW1. It contains the standard fields INPWEEMP, INPWTXT1, INPWTXT2. However, we have a requirement to manipulate the standard contents of these fields. We wanted to use user exit EXIT_SAPLIEDP_002 to do this.
I have maintained user exit EXIT_SAPLIEDP_002 but when we enter this on creation of the IDOC the segment E1IDBW1 does not seem to be available in table EDIDD_TABLE for manipulation. Can you advise please if (1) you were able to get E1IDBW1 available to edit in exit EXIT_SAPLIEDP_002 and (2) were you able to manipulate the contents of INPWTXT1, INPWTXT2 etc?
We have done the following steps:
- BTE 2441 is available on our release
- house bank has been setup as an In House Cash Center which allows E1IDBW1 to be generated
- entry has been maintained in table FEDICUS with Message Type = PAYEXT, BasicType = PEXR2002, Extension = Blank, Seg Type = E1IDBW1
- code maintained in ZXF08U04
The system enters ZXF08U04 but E1IDBW1 is not available there for manipulation.
Can you advise what we might be missing please?
Thanks and regards
Mike

User Exit required for restricting 1 vauation type in ME51N

Hi Experts,
I want to restrict that during the creation of PR i can only create the PR for materials for same valuation type. If there are 10 material then that should be of same valuation type.
Please suggests.

Hello,
While creation of PR, System will check Material is split valued or not.... if yes then ask you enter split valution.
This is not possible in Std SAP. this is only possible through enhancement. What is the business requirement?
Because if i want to create One PR for 5 Raw materials and 5 FINISHED goods, then here system will create PR for any of the 5 materials., so this is not feasible.
Regards
Mahesh Naik.

Inbound Idoc type for posting Non-PO Invoice

Hi,
I am looking for an inbound Idoc type to post Non-PO Invoice. The Idoc types INVOIC01 and INVOIC02 helps me to post the invoice with reference to PO. But I am looking for the Idoc type to post the invoices without reference to PO i.e., For example to post the transaction FB60 (Enter vendor invoice without ref to purchase order).
with regards,
suresh

Hello Deep,
I know it might be quite late for you for this answer, nevertheless I will write that, because there are lots of question like yours. bapi_incominginvoice_park is also a suitable bapi for you. All you need to do is call it this way:
data: headerdata like bapi_incinv_create_header value is initial,
        table_item type table of bapi_incinv_create_item,
        gl_account like bapi_incinv_create_gl_account,
        table_gl type table of bapi_incinv_create_gl_account.
* fill headerdata and table_gl, leaving table_item empty
CALL FUNCTION 'BAPI_INCOMINGINVOICE_PARK'
    EXPORTING
      HEADERDATA                = HEADERDATA
*   ADDRESSDATA               =
    IMPORTING
      INVOICEDOCNUMBER          = lv_docnr
      FISCALYEAR                = lv_year
    TABLES
      ITEMDATA                  = table_item
*      ACCOUNTINGDATA            = table_acc
      GLACCOUNTDATA             = table_gl
*   MATERIALDATA              =
*      TAXDATA                   = table_tax
*   WITHTAXDATA               =
*   VENDORITEMSPLITDATA       =
      RETURN                    = lt_return.
This works perfectly for me, creating a mir7 document without refering to a PO. The trick here is to fulfill the glaccountingdata importing table while leaving itemdata empty.

To find out appropriate user exit/ badi for transaction VT01n

Hi,
   I have the following requirement.
Cass shipment type (VTTK-ADD03) field needs to be required and should be automatically populated upon creation of the shipment document. The rules for populating the value (SO, ST, PO and RA) are as follows:
If any of the orders on the shipment are customer order types, then the CASS shipment type should be a SO,
If all of the orders are STO orders, then the Cass shipment type should be "ST",
If all of the orders are PO orders, then the Cass shipment type should be "PO" , and
If all of the orders are customer return orders, then the Cass shipment type should be "RA".
I have to find out proper user exit / badi to do this.I have tried with many userexit but it won't work.
   Thanking in advance to give your suggestion in order to resolve it.
With regards,
Ajit.

Hi this code will enable you to find the user exit for any transaction . Just give the transaction as input
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).
   call transaction 'SMOD' and skip first   screen.
*---End of Program
Just for your information the User exits available for VT01n are
MV56AINI            Initialization of transaction control for transportation
V56AFCCH            Shipment processing: Check function code allowed
V56AGTAR            User Exit for Filtering Shipping Unit Calculation
V56ARCHV            Customer-spec. checks for archiving shipments
V56ATKTX            Change the number of lines for text input in shipment
V56BMOD             Transportation processing: Field modification
V56DISTZ            Shipment Processing: Determine Distance
V56FCOPY            Shipment processing: Copy delivery data
V56FSTAT            Shipment processing: Activities when setting a status
V56L0001            Status of Shipments for a Delivery
V56LDELI            Read Delivery Data for Shipment Processing
V56LOCID            Shipment Processing: Determine Location Identification
V56MVT04            Extensions for Collective Processing of Shipments
V56SLDET            Shipment processing: Leg determination
V56TDLIF            Filter Delivery Items for Shipment
V56UCHCH            Shipment processing: Check whether changes were made
V56UCHCO            Check shipments are complete
V56UDLUP            Obsolete as of 4.6C: Delivery Update on Delivery Routines
V56UNUMB            Shipment number allocation
V56USTAT            User-individual definition of transportation planning status
V56USVDO            Update new objects for transport
V56USVDP            Preparation for updating new objects for transport?
Award points if helpful..
Thanks

Correct user exit need for vl32n - post goods receipt.

Sorry this is not the correct forum . SO please don't look in to this
For vl32n , upon "Post goods receipt" button click, I was writing code in "mv50afz1" ...Basically in the "mv50afz1" program, I am clearing the value of batch(charg) and the same batch value I am assigning to vendor batch(am doing by moving xlips-charg value to xlips-lichn).
But the thing is my logic should be written in one of the userexit before this user exit( Why because SAP generates one batch on it's own and assigns that to batch if it the batch field in vl32n is space - If batch field is not space SAP's generated batch won't be assigned - So I need to make the batch value space in vl32n upon click of "Post goods receipt" button to allow assignment of SAP's batch).
So could you please suggest me is there any user exit available for this ?
THANKS.
Edited by: sam kumar on May 8, 2009 7:22 PM

I am sorry this i snot the correct forum.

User exit/BADI for delivery creation in VL10B

Hi,
Is there any exits available for restricting the document type while the deliveries are selected/processed using VL10B/VL10G - delivery creation in background.
Scenario is when deliveries are created for STO's,thedelivery is to be created for a selected document types(EKKO - BSART).Other types of document types have to be ignored when the delivery is created in background.
Regards
Deepak

Check this exit.
BADI LE_SHP_DELIVERY_PROC
Method IF_EX_LE_SHP_DELIVERY_PROC~DELIVERY_FINAL_CHECK

User Exit MIGO for Purchase Orders

I need to check a purchase order during the Migo process.
I tried the User Exit EXIT_SAPLEINR_001, but the break-point has no effect. The user- exit is useful for schedule agrmts but it seems that there is a different handling.
Do you have an idea where I can check the MIGO date?

hi alexander,
this program will display all the user exits available for any specified Tcode.
when u execute this code...... it will ask for tcode..... u enter any tcode.... it will display all available exits for specified tcode.....
i hope this may help u...... all the best....
report y_user_exit .
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).
call transaction 'SMOD' and skip first screen.
reward me if it is useful..............
with regards.....

How to block the status mail for an inbound Idoc to a specific user

Hi,
I have to stop sending the error status mail to a specific user depenidng on Partner Type. This will trigger when an inbound Idoc contains status error(message type INVOIC &ORDRSP).This user needs other mails which are getting triggered with the same Idoc for the same partner. Basically, the requirement is to block only the status mail for that user. The statndard task for this is TS70008125 and it uses the agent determination rule 30000001 (Idoc Administrator).in WE46, this task is assigned to process code EDIR. I have copied the task to a custom task and changed the agent determination rule. I would like to know how will I configure this task so that this custom task will trigger for the status error, without altering other workflows for the same message type & the partner type. Or is there any other way to block the mail?
Thanks,
Santosh

Hi,
I have done the required coding to exclude the specific agent from the rule,copied the task and its ready. My question is how do I map this custom task to a particular partner type, for the message type INVOIC in WE20? (The message type used for the inbound Idoc is INVOIC). I checked the Partner profile in WE20. Most of the process code is using function module as the processing type.
Thanks,
Santosh

Inbound Idoc type for Usage Decision QA11

Dear SAP Gurus,
Would like to find out if there is any inbound idoc type to perform Usage Decision (transaction QA11).
Will reward points for any kind of help. Thank you.
regards,
Ju Lee

Hi,
There is no standard Inbound Idoc for UD. But there is BAPI available for same "BAPI_INSPLOT_SETUSAGEDECISION".

Can anyone give me user exit name for create/update purchase order partners

Hello guys
Can anyone gives me user exit name for create/update purchase order partners?
Requirement is to insert/update partner when SC flag is checked while creating/updating purchase order (ME22N / ME21N) by using user exit.

hi,
check these exits.
Transaction Code - ME21N                    Create Purchase Order
Enhancement/ Business Add-in            Description
Enhancement
MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
MM06E001                                User exits for EDI inbound and outbound purchasing documents
MM06E003                                Number range and document number
MM06E004                                Control import data screens in purchase order
MM06E005                                Customer fields in purchasing document
MM06E007                                Change document for requisitions upon conversion into PO
MM06E008                                Monitoring of contr. target value in case of release orders
MM06E009                                Relevant texts for "Texts exist" indicator
MM06E010                                Field selection for vendor address
MMAL0001                                ALE source list distribution: Outbound processing
MMAL0002                                ALE source list distribution: Inbound processing
MMAL0003                                ALE purcasing info record distribution: Outbound processing
MMAL0004                                ALE purchasing info record distribution: Inbound processing
MMDA0001                                Default delivery addresses
MMFAB001                                User exit for generation of release order
MRFLB001                                Control Items for Contract Release Order
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
AMPL0001                                User subscreen for additional data on AMPL
LMEDR001                                Enhancements to print program
LMELA002                                Adopt batch no. from shipping notification when posting a GR
LMELA010                                Inbound shipping notification: Transfer item data from IDOC
LMEQR001                                User exit for source determination
LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001                                Customer-Specific Source Determination in Retail
M06B0001                                Role determination for purchase requisition release
M06B0002                                Changes to comm. structure for purchase requisition release
MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
MEETA001                                Define schedule line type (backlog, immed. req., preview)
ME590001                                Grouping of requsitions for PO split in ME59
M06E0005                                Role determination for release of purchasing documents
M06E0004                                Changes to communication structure for release purch. doc.
M06B0005                                Changes to comm. structure for overall release of requisn.
M06B0004                                Number range and document number
M06B0003                                Number range and document number

User exit/ badi for fb02 transaction

Hi,
what are the appropriate user exit/ badi for fb02 transaction for a disabling(graying out) a
payment block field for particular users..?
Regards,
Avi

Following are the exits available for FB02
F050S001            FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment
F050S002            FIDCC1: Change IDoc/do not send
F050S003            FIDCC2: Change IDoc/do not send
F050S004            FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
F050S005            FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document
F050S006            FI Outgoing IDoc: Reset Clearing in FI Document
F050S007            FIDCCH Outbound: Influence on IDoc for Document Change
F180A001            Balance Sheet Adjustment
FARC0002            Additional Checks for Archiving MM Vendor Master Data
FEDI0001            Function Exits for EDI in FI
RFAVIS01            Customer Exit for Changing Payment Advice Segment Text
RFEPOS00            Line item display: Checking of selection conditions
RFKORIEX            Automatic correspondence
SAPLF051            Workflow for FI (pre-capture, release for payment)

BADI/User Exit suggestion - for determining Partner in PO header

Hi All,
I want to be able to automatically populate and determine a manual partner function within the header of a purchase order creation.
Example, when PO is allocated against account assignment 'P' then go to the WBS element assigned and retrieve the specific partner number for partner function type XX. Then populate this into the relevant header partner function of the PO.
Any ideas of which BADI/User exit could be used in ME21N?
Thanks
Steve

Hi Steve
Before going to search the UserExit/BADI, please remember your account assignment will be at item level and the partner will be at Header level.If you have number of line items with different account asssginments or different WBS elements under account assignment P, it is difficult to determine the partner functional at Header level.Please think on how can you build logic? There are number of BADI/Exits available for Purchase order.
Regards
Ramakrishna

User Exit available for basic inbound idoc type MBGMCR01 in SAP R/3

Similar Messages

Maybe you are looking for