User exit MB_CF001 in MIGO
Folks,
I am using the user exit MB_CF001 to get the data from XMSEG table and send it to an external system. I was asked to call an RFC function module in this user exit to send the XMSEG data to an external system but the user exit documentation clearly says not to use RFC function call in this user exit.
I also heard that I can do this by using the idocs that get posted after MIGO is done. Could anyone give me step by step procedure how to do this as I am new to IDOCS.
Points will be rewarded for best answers.
Thanks,
Alok
Dear Alok,
Below is a documentation about IDOCs. Hope it will be useful to you.
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
Important links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
>SAP ALE & IDOC
Steps to configuration(Basis)
>>1. Create Logical System (LS) for each applicable ALE-enabled client
>>2. Link client to Logical System on the respective servers
>>3. Create background user, to be used by ALE(with authorizaton for ALE postings)
>>4. Create RFC Destinations(SM59)
>>5. Ports in Idoc processing(WE21)
>>6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
>Steps to customize a new IDoc
>>1. Define IDoc Segment (WE31)
>>2. Convert Segments into an IDoc type (WE30)
>>3. Create a Message Type (WE81)
>>4. Create valid Combination of Message & IDoc type(WE82)
>>5. Define Processing Code(WE41 for OUT / WE42 for IN)
>>6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Best Regards,
Rajesh.
Please reward points if found helpful.
Similar Messages
-
USER EXIT MB_CF001 NOT GETTING TRIGGERED
Hi All,
I am using EXIT_SAPLMBMB_001(MB_CF001)
I want it to be triggered after the document has been saved but its not trigeering..
How can I find out the reason???
Regards
ShilpaHi,
have you checked documentation for that enhancement? That function module is not called after goods movement creation.
The user exit MB_CF001 includes a function module that is called up
immediately before the COMMIT WORK when a goods movement is posted.
How do you test that FM? Some function modules from user exits are called in UPDATE TASK so they just ignore break points. In this case you can use the following trick. You need to enter an infinite loop into your user exit. Then you can connect to this program via transaction SM50 (Program/Session -> Program -> Debugging).
Cheers -
User exit/BADI for MIGO Batch numbers
Hi All,
I want to find a user exit which will give the oldest batch number (MCHA-LWDET) of semi-finished product during the goods receipts of the finished prodocut in MIGO.
Could you please give me any hints to find out the user exit for this.
Regards,
Sekhar DHi,
Check these User exits... for MIGO
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.
Check thse BADI's.. for MIGO
Badi Name
ARC_MM_EBAN_CHECK
ARC_MM_EBAN_WRITE
ARC_MM_EINA_WRITE
ARC_MM_INVBEL_WRITE
ARC_MM_MATBEL_CHECK
ARC_MM_MATBEL_WRITE
MB_CHECK_LINE_BADI
MB_CIN_MM07MFB7
MB_CIN_MM07MFB7_QTY
MB_DOCUMENT_BADI
MB_DOCUMENT_BADI_SAP
MB_DOCUMENT_BADI_SAP
MB_DOC_BADI_INTERNAL
MB_DOC_BADI_INTERNAL
MB_ME_CSGMT_BADI_SAP RTFASH:
MB_MIGO_BADI
MB_MIGO_ITEM_BADI
MB_PHYSINV_INTERNAL MB_PHYSINV_INTERNAL BAdI Implementation
MB_RESERVATION_SCR DFPS: Field in the Reservation
MB_RESERVATION_UPCHD DFPS: Reservation
Regards,
Raghu
Edited by: Raghavendra Rao G on Aug 27, 2009 5:50 PM -
User exit/Badi in MIGO after save
hi all
I am trying to find a user-exit/BAdi in tcode MIGO.
This one should be called after saving the MIGO document.
Using this i want to put control over auto TO creation for some specific plants and storage locations.
Important thing is I am using version 4.6C.Hi,
Please try the last one. This may suit.
For "Automatic TO creation (background processing)", the following user exits are available:
MWMTOAU1 Selection of requirements for automatic creation of orders.
MWMTOAU2 Reference number assignment.
MWMTOAU3 Selection of posting change notices for automatic creation of transfer orders.
Thanks and Regards
Guru -
BADi/User Exit in J1IEX/MIGO
Hi.,
While capturing excise invoice in MIGO, iI wanna to make excise material type NONCENVATABLE as default for those items which has JMIP (Inventorized duty) in Purchase Order.If the material is maintained as Raw/asset/consumable/tools & if JMIP condition is maintained for that material in PO,then while capturing excise invoice in MIGO,it should take the excise material type as NONCENVATABLE.
Are there any Badi/User Exits for this?
Please guide on this issue
Thanks & Regards,\Check with function module "J_1IEX_DETERMINE_CHAPTER_ID" & "J_1IEX_FILL_EXCISE_ITEMS"..
-
Hi to all
I need do it, a enhancement by the transaction MIGO, just when the document is saved.
Somebody knows, an enhacement in particular ??
Thank by their aid.
regards
DarioHi,
Assuming this is your requirement..
Store the MKPF & MSEG details in a Z table...when the material document is created..
Solution
1)
Create a function module Z_ADD_ZTABLE..Which should be remote enabled..
Give the parameter..
You can select on MKPF and MSEG with the material document number that has been just posted...The values are available in XMKPF-MBLNR..
Example.
SELECT SINGLE * FROM MKPF WHERE MBLNR = XMKPF-MBLNR.
****The return code will be zero..Means the record is available in the database.
2)
IN the BADI MB_DOCUMENT_BADI or in the USER EXIT...
CALL the function module in BACKGROUND TASK..
Example
CALL FUNCTION 'Z_ADD_ZTABLE' IN BACKGROUND TASK
Exporting
Hope this is clear..
Thanks,
Naren -
HI all,
My requirement Is to POst another transaction at migo.
lets say after transaction 909, i have to create another material doc using
BAPI_GOODSMVT_CREATE..
Is there a User exit or Badi which is safe to use?...
i am currently using
EXIT_SAPMM07M_001 but there are times that locks entries are not
yet removed from the first movement type(909).
or any other approach with my requirement..?Hi,
Steps to achieve..
1) Create a FM in se37 with the "Remote enabled module" radio button enabled in the attributes tab..
Do all your functionality in this Function module..
2)
In the exit EXIT_SAPLMBMB_001..
Call the FM that you created above in BACKGROUND TASK..
CALL FUNCTION 'Z_POST_NEW_DOCUMENT'
IN BACKGROUND TASK
This will work...
Thanks,
Naren -
MM User Exit : MB_CF001
Can anyone please tell me when do this user exit break.
The enhancement MB_CF001 includes a function module that is called up immediately before the COMMIT WORK when a goods movement is posted.
All the material document data is passed on to this function module from the following tables:
o MKPF (Material document header)
o MSEG (Material document items)
o VM07M (Update data)
This data can be passed on to other programs.
Note
The enhancement does not write any data to the material document, that is, it is not possible to change material document data before the update posting takes place.
If the enhancement MB_CF001 (component: Function module EXIT_SAPLMBMB_001with Include ZXMBCU01) is implemented incorrectly, an inconsistency may occur between documents and stocks as well as between material documents and accounting documents. Such inconsistencies can be caused by the following elements in the user exit, for example:
o COMMIT WORK
o Remote function call (CALL FUNCTION .. DESTINATION)
o Separate updates on the document or stock tables (for example, an
update on table MBEW, MARD, MSEG)
o Unlocking data (for example, through DEQUEUE_ALL)
The enhancement MB_CF001 is called in the update function module MB_POST_DOCUMENT. If a COMMIT WORK or a Remote Function Call is set in the enhancement, a complete ROLL BACK is not possible in the case of an update termination, since data has already been written until the COMMIT
or the remote function call in the database. Consequently, an asynchronous status (for example, a material document without accounting document), which can only be repaired with considerable effort, may be the result.
The enhancement MB_CF001 is not suited for customer-specific updates on the stock tables, because such updates can destroy the standard inventory update if they are not programmed incrementally (see Note 6899), or if they do not take the material blocks into account.
Unlocking data (for example, using DEQUEUE_ALL) is also very important, as the data to be updated is no longer protected against external updates, and inconsistencies can result from parallel updates.
Before you activate an enhancement, check thoroughly that the user exit does not contain high priority source code positions.
If data inconsistencies have already occurred in your system, inconsistencies that can be traced back to the user exits, remove the high priority source code positions immediately before they cause further
inconsistencies. -
hola, necesito un user exit para desplegar un mensaje cuando se hace un traslado por la transacción MB1B y no el material no tiene costo, estoy tratando de usar la ampliación MB_CF001 y no me perimite desplegar mensajes via abap
gracias y saludos
DayanaAssuming that you are speaking Portuguese, please post your queries here: /community [original link is broken]
For Spanish: /community [original link is broken]
pk -
hi all,
plz solve my problem.
how to find a badi for tcode migo ?
wher to write code?
can any bodysuggest me?
thanks
sachhidanandaHi Sachhidananda,
MIGO belongs to MB Package
These are the BAdI's for MB package.
MB_CHECK_LINE_BADI..............BAdI: Check Line Before Copying to the Blocking Tables
MB_CIN_LMBMBU04...................posting of gr
MB_CIN_MM07MFB7...................BAdI for India Version exit in include MM07MFB7
MB_CIN_MM07MFB7_QTY...........Proposal of quantity from Excise invoice in GR
MB_DOCUMENT_BADI................ BAdIs when Creating a Material Document
MB_DOCUMENT_UPDATE ..........BADI when updating material document: MSEG and MKPF
MB_MIGO_BADI .........................BAdI in MIGO for External Detail Subscreens
MB_MIGO_ITEM_BADI ................BAdI in MIGO for Changing Item Data
MB_RESERVATION_BADI............MB21/MB22: Check and Complete Dialog Data
After finding the appropriate BAdI u need to Implement the BAdI in SE19 Tcode.
In SE19 , give the Implementation name and click on create pushbutton then u get a popup Definition Name. Give the Definition Name and click on Enter (Continue).
Here u can see all the Methods in Interface Tab.
U need to select the Appropriate METHOD and in that METHOD u need to write the Code.
For Example
Best regards,
raam -
IS there any user exit when finish MIGO?
Hi,
I want change the material price when post goods using Migo,I find several exit,but It locked the material,I can't change material during this time,is there any exit after posing goods, or is it possible to call another program after migo?
Thanks in advance.
LanceDear Lance,
Do you already check for : ZXMBCU01-ZXMBCU03
Also in IMG path : MM>Inventory management and PI>Maintain customer exits and Business add-ins.
Regards,
w1n -
Hello Experts
i am having a requirement where in i will have to perform certain validations before posting PO and material document (MIGO). If these validations fail, PO or Material document should not be posted.
i managed to find certain BADI and user-exits (MB_CF001 and MB_DOCUMENT_BADI) typically for MIGO but when tested they use to get triggered once these doucment numbers are generated.
what i am looking at is cancel the process by giving the hard-error.
thanks in advance.
regards
rajeevHi,
<b>User exits for MIGO:</b>
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
MBCFC003 Maintenance of batch master data for goods movements
MBCFC004 Maintenance of batch specifications for goods movements
MB_CF001 Customer Function Exit in the Case of Updating a Mat. Doc.
<b>User eits for PO:</b>
These are the User exit for CO01 ( Create PO)
CCOWB001 Customer exit for modifying menu entries
COIB0001 Customer Exit for As-Built Assignment Tool
COZF0001 Change purchase req. for externally processed operation
COZF0002 Change purchase req. for externally procured component
PPCO0001 Application development: PP orders
PPCO0002 Check exit for setting delete mark / deletion indicator
PPCO0003 Check exit for order changes from sales order
PPCO0004 Sort and processing exit: Mass processing orders
PPCO0005 Storage location/backflushing when order is created
PPCO0006 Enhancement to specify defaults for fields in order header
PPCO0007 Exit when saving production order
PPCO0008 Enhancement in the adding and changing of components
PPCO0009 Enhancement in goods movements for prod. process order
PPCO0010 Enhancement in make-to-order production - Unit of measure
PPCO0012 Production Order: Display/Change Order Header Data
PPCO0013 Change priorities of selection crit. for batch determination
PPCO0015 Additional check for document links from BOMs
PPCO0016 Additional check for document links from master data
PPCO0017 Additional check for online processing of document links
PPCO0018 Check for changes to production order header
PPCO0019 Checks for changes to order operations
PPCO0021 Release Control for Automatic Batch Determination
PPCO0022 Determination of Production Memo
PPCO0023 Checks Changes to Order Components
STATTEXT Modification exit for formatting
I am giving you the list of all user exits available for ME21N:
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
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requisn.
M06E0004 Changes to communication structure for release purch. doc.
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., preview)
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
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
For your purpose you can probably try MM06E005. Or you can also try BADI ME_PROCESS_PO_CUST.
You can also check this BADI available for PO:
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
ME_BAPI_PR_CHANGE_01 BAdI: Enjoy BAPIs for Purchase Requisitions (Method Chan
ME_BAPI_PR_CHANGE_02 BAdI: Enjoy BAPIs for Purchase Requisitions (Method Chan
ME_BAPI_PR_CREATE_01 BAdI: Enjoy BAPIs for Purchase Requisitions
ME_BAPI_PR_CREATE_02 BAdI: Enjoy BAPIs for Purchase Requisitions (Method Crea
ME_BSART_DET Change document type for automatically generated POs
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standa
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Cust
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Custom
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PURCHDOC_POSTED Purchasing Document Posted
ME_RELEASE_CREATE BAdI: Release Creation for Sched. Agreemnts with Rel. Do
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_REQ_POSTED Purchase Requisition Posted
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Orde
SMOD_MRFLB001 Control Items for Contract Release Order
Transaction codes for BADI are:
SE18 - Business Add-ins(BADIs): Definition transaction
SE19 - Business Add-ins(BADIs): Implementation transaction
SE24 - Class Builder
Link for all user exits in SAP:
http://www.easymarketplace.de/userexit.php
Pls reward helpful points.
Regards,
Ameet -
Hi,
I have added code in the user exit MB_CF001 for the transcation code MIGO.
I put a break-point in it (hard coded),
I have activated in SMOD and CMOD also.
But when i run MIGO and POST (click on post button on application tool bar) it is not posting, while clicking on SAVE also it is not stopping.
Please tell me when the user exit will be encountered.
regards,
Prabhu.
Points assured.sorry.
regrads,
Prabhu -
User exit for MIGO Posting Date
Dear all,
My Client want requirement is : Posting date of GRN should be after last posting date of goods issue
i.e. GI 261 1st june
GI Reverse 262 2nd june
again GI 261 28 may ( as 2 posting perod are open )
then user should be able to do GRN on or after 28th may
For this user exit please suggest me any FM or logic
my current logic is allowing to post GRN after 1st june i.e. latest GI date but that is not matching client requirement
Please suggest
Regards,
IshwarHi,
Enhancement for MIGO ,you can try these user exit
MB_CF001--> Customer Function Exit in the Case of Updating a Mat. Doc.
MBCF0002 --> Customer function exit: Segment text in material doc. item
MBCF0005 --> Material document item for goods receipt/issue slip
MBCF0007 -->Customer function exit: Updating a reservation
In BADI,you can refer these
MB_CIN_LMBMBU04--> posting of gr
.In MKPF table having data (posting date of goods issue) BUDAT-field name,tell the conditions as per your requirement to ABAPer,they can implement the enhancement as per your requirement...
I hope,it will help you
<=<< Sharing Knowledge is a way to Innovative >>=>
By,
Yoga -
Hi All,
Please let me know which user exits / badi for MIGO which is effective at SAVE time (only for GRN) with using PO.
Best Answer Best Points....
Thanks In AdvanceEnhancement/ Business Add-in Description
Enhancement
MB_CF001 Customer Function Exit in the Case of Updating a Mat. Doc.
MBCF0011 Read from RESB and RKPF for print list in MB26
MBCF0010 Customer exit: Create reservation BAPI_RESERVATION_CREATE1
MBCF0009 Filling the storage location field
MBCF0007 Customer function exit: Updating a reservation
MBCF0006 Customer function for WBS element
MBCF0005 Material document item for goods receipt/issue slip
MBCF0002 Customer function exit: Segment text in material doc. item
Business Add-in
MB_RESERVATION_BADI MB21/MB22: Check and Complete Dialog Data
MB_QUAN_CHECK_BADI BAdI: Item Data at Time of Quantity Check
MB_PHYSINV_INTERNAL Connection: Core Inventory and Retail AddOn
MB_MIGO_ITEM_BADI BAdI in MIGO for Changing Item Data
MB_MIGO_BADI BAdI in MIGO for External Detail Subscreens
MB_DOC_BADI_INTERNAL BAdIs when Creating a Material Document (SAP Internal)
MB_DOCUMENT_UPDATE BADI when updating material document: MSEG and MKPF
MB_DOCUMENT_BADI BAdIs when Creating a Material Document
MB_CIN_MM07MFB7_QTY Proposal of quantity from Excise invoice in GR
MB_CIN_MM07MFB7 BAdI for India Version exit in include MM07MFB7
MB_CIN_LMBMBU04 posting of gr
MB_CHECK_LINE_BADI BAdI: Check Line Before Copying to the Blocking Tables
ARC_MM_MATBEL_WRITE Check Add-On-Specific Data for MM_MATBEL
ARC_MM_MATBEL_CHECK Check Add-On-Specific Criteria for MM_MATBEL
Regards.
Maybe you are looking for
-
Nano seen in windows, not in itunes
I got a iPod nano about 2 weeks ago and after fixing my computer so that the USB port would work i installed the software so i could download the music. Before that i installed the software on another computer and it worked fine. I had downloaded itu
-
Powerbook wont startup and have no install disks
My powerbook G4 starts up installs lots of extensions until it announces that it is "waiting for Apple file service" and then stops. I am fairly sure that I didnt get any install disks when i bought it (long time ago now) because all the software was
-
How to include link with parameter in marketing emails?
Hi, my client wants to send out personalized marketing emails to customers with a link back to the BC site that have a parameter on the end that passes the customer's email address the message was sent to. Then the landing page can parse that email o
-
Parrot Hands-free kit and 6300
Having a bit of trouble with my new Parrot PMK5800 hands-free kit and my 6300. I can connect to the 2 together, but the Parrot asks for a voice tag from the 6300 for hands free dialling. I cannot seem to be able to transfer this. Have tried most thin
-
Fcpx trial can't read my card EX3
I download the fcpx trial, i try to read a EX3 card and doesn't work... and to try to resolve this problem when I look to download content format I didn't can find them???? Do you have any sugestion to resolve it... thank you very much