Userexit in mb1b, mb1c

Hi..
Is there any userexit on mb1c in screen Enter other goods receipts : New Items, i want to find a exit which gets activated when one enters the material.
Does any one have a idea>? I checked on the zuexit and activated break points to each but nothing seems to get activated at this stage.
ANy help is appreciated.
Thanks
Keshi

Hi,
For T. Code M1BC here are the user exits:
                                                                                Transaction Code - MB1C                     Other Goods Receipts
Exit Name           Description
MBCF0011            Read From RESB and RKPF For Print List in MB26
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
MBCFC003            Maintenance of batch master data for goods movements
MBCFC004            Maintenance of batch specifications for goods movements
No of Exits:          9
And for T. Code MB1B here are the User Exits:
Transaction Code - MB1B                     Transfer Posting
Exit Name           Description
MBCF0011            Read From RESB and RKPF For Print List in MB26
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
MBCFC003            Maintenance of batch master data for goods movements
MBCFC004            Maintenance of batch specifications for goods movements
No of Exits:          9
Reward all helpful answers.
Regards,
Varun.

Similar Messages

Creating output type for MB01,MB1B & MB1C for IDOC

Dear Exoerts,
Here scenarion is client using interface at front end.Which provides backup data from SAP.
Can anybody guide to Create output type for transactions MB01,MB1B & MB1C.It is going to use for IDOC creation.Client wants Inventory program at front end system.
Waiting for your reply.

Hi,
Please check below link in this regard. Thanking you.
http://help.sap.com/saphelp_45b/helpdata/en/52/16ac64543311d1891c0000e8322f96/frameset.htm
Edited by: Padmasri Garapati on Nov 30, 2011 3:14 PM

Output type for MB1B & MB1C-IDOC creation

Dear Expert,
I have to make output type for MB1B & MB1C transaction to create IDOC.Can anybody guide path to create Output type for same.

Hi anupmore124,
You can create a new condition type, named as "ZWA1" and you can copied this from WA01.
Once this is copied, change the following data:
1. In partner functions, include:
Medium: 6 - EDI
Funciton: (blank)
You can delete the other partner function(s), if you want that this new output message type can be handled only by EDI (for IDOCs).
2. In the "General data" tab, you need to have selected only:
Access sequence: i.e. 0003 - Trans.Type/Print Vers./Indic.
Check box active "Access to conditions"
The rest of the check box needs to be inactive.
3. In the "Default" tab, define:
Dispatch time: 1 - Send with periodically scheduled job
Transmission medium: 6 - EDI
Then, save the data and now, the IDOC can be created.
Obviously, I presume that you made your customising before in WE20 with the correct IDOC message type, etc.
I hope this help.
Kind regards,
Sandra

Tcode MB1B/MB1C/MB1A

HI,
What is the diffrence between Tcode MB1B/MB1C/MB1A

MB1B - Transfer Posting {may physical (or) logical (not physical) stock transfer of goods}.
MB1C - Initial Uploading for Stock
Initial Entry of Inventory Data
You must carry out an initial entry of stock balances when implementing the SAP System in order to transfer physical warehouse stocks or book inventories from an existing system into the SAP System as book inventories. No physical movements actually take place. The initial entry of stock balances can be carried out for the following three stock types:
·        Unrestricted-use stock
·        Stock in quality inspection
·        Blocked stock
If the stocks are to be transferred from a legacy system, the initial entry of stock balances for large volumes of data is carried out via the Data Transfer Workbench (see MM Goods Movements: Data Transfer Workbench).
You can also carry out the initial entry of stock balances manually.
You use the following movement types to enter an initial entry of stock balances manually:
·        Unrestricted-use stock (561)
·        Stock in quality inspection (563)
·        Blocked stock (565)
The quantity taken over into book inventories is posted to the appropriate stock and increases the total valuated stock of the material.
MB1A - for Goods Issue
Regards,
Anbu

Mb1a/mb1b/mb1c

MB1A-GOODS ISSUE (gi)
MB1B-TRANSFER POSTING (tp)
MB1C-GOODS RECEIPT (gr)

Hi,
MB1A ( Goods Issue) :
Term used in inventory management to describe a reduction in warehouse stock due, for instance, to a withdrawal of stock or the delivery of goods to a customer.
MB1B (Trnasfer of Posting) :
Generic term covering both physical transfers of stock and changes that affect book records only (that is, which do not involve a physical movement), such as changes in the identification or classification of stocks.
Examples are:
Stock transfer within a plant or between plants
Release from quality inspection
Transfer of consignment stock to the company's own stock.
MB1C (Goods Receipt) :
Term from the field of inventory management denoting a physical inward movement of goods or materials.
The SAP System differentiates between the following kinds of goods receipt:
Goods receipt with reference to a purchase order
Goods receipt with reference to a production order
Other goods receipts (without reference).
Prase

Additional Items via Enhancement on MB1A / MB1B / MB1C - Update of Accounting Documents

Hello all!
Please, I'm in need of help from community.
I am working on a Project For México. It's a doubt that has arisen from a functional request.
They want that we create a development that might check the materials inserted on MB1A / MB1B and MB1C transaction.
If these materials meet with the functional requirements, then new materials must be inserted at this same document, correcting it.
We already have searched for User-Exits, BADIs and Enhancement-Points, and our position at the moment is that we already achieved to input the material into the material document, but those new lines aren't been recognized on subsequent Accounting Documents, that are created after the material document and that can be viewed on MB03 transaction, into the material document.
Anyone has any clue if it's possible to modify Material Documents through Enhancements/BADIs/Exits, adding new lines of materials (XMSEG), and grant the subsequent creation of accounting documents?
Thanks in advance!
Some Points that we already tried, but without success:
EXITs : MB_CF001, MBCF0002 and MBCF0005
BADIS: MB_MIGO_ITEM_BADI, MB_MIGO_BADI, MB_CHECK_LINE_BADI, MB_DOCUMENT_BADI_SAP, MB_DOCUMENT_BADI
Enhancements in following programs: MM07MFJ1 and MM07MFB9_BUCHEN_NUMMERNVERGABE

Hello Srilakshmi,
Thank you for the response, but unfortunately the BADIs you've mentioned don't allow me to modify Material Data tables, such as MSEG and VM07M.
MB_DOC_BADI_INTERNAL is only for SAP use, and MB_DOCUMENT_UPDATE parameters are Importing only.
Regards.
Thiago

Auto Update MB1* transactions

Hi All,
I would like to Update transactions MB1A,MB1B,MB1C through Flat file.
I appreciate if any one let me know the relevent IDOc/RFC ( I got WMMBID02 Idoc from SDN )
and configurations in R3 to Update transaction.
I have configured connection between XI and R3.
regards,
Ramesh.

Hi Ramesh,
Usually we dont update the transactions directly from PI. We usually send to SAP using RFC or IDOC and from there we post it and while posting if we need to use any user exits we will use them and post it.
For your transactions you can use the idoc WMMBID02 or you can also use RFC BAPI_GOODSMVT_CREATE. You need to check all the fields required which are used to post. If you dont have all the fields then you can also create a zrfc or extend the idoc to support your requirement. or Call the RFC INBOUND_IDOC_PROCESS with IDOC_CONTROL and IDOC_DATA. The structure in the field sdata in the IDOC_DATA are e1mbxyh and e1mbxyi. So in PI it will be like File - PI - IDOC or File - PI - RFC scenario. To find any user exits are there for this transaction you can do the steps mentioned in this thread:
Userexit for extended idoc for std. idoc WMMBID02 for T.Code MB1A & MB1B
> and configurations in R3 to Update transaction.
The corresponding functional consultant will help you in detail for your client requirements. Some configuration you can see here:
http://sap.rfgen.com/docs/PR/PR%20Component%20Scrap.pdf
http://www.sapstudymaterials.com/2007/12/accounting-fico-journal-of-mm-goods_09.html
Regards,
---Satish

Vendor field should not display when GI is done in MB1A?

Hi guys ,
i have a report programe here i am pulling all the material data and purhasing order info in the background using the BADIO MB_DOCUMENT BADI. here i am writing my logic. this BADI is triggering once material Documnet is created in MIGO MB1A,MB1B,MB1C . when i am trying to excute the MIGO tranasaction all the data shoulb be displayed . when I am trying to excute MB1A Here i dont need one field like Vendor Number ? can any one please help me on these ?
Thanks In Advance.

Instead of <?for-each:G_CF_SUB_SEG_VALUE?>
use
<?for-each:G_CF_SUB_SEG_VALUE[TOTAL_CUST_AMT!=0 or TOTAL_CUST_B0!=0 or TOTAL_CUST_B2!=0 or TOTAL_CUST_B3!=0 or TOTAL_CUST_B4!=0 or TOTAL_CUST_B5!=0 or TOTAL_CUST_B6!=0]?>

Unit of measure EA allows transactions in decimals ? Is EA indivisible?

Unit of measure EA allows transactions in decimals ? Is EA indivisible?
There are two scenarios. While creating a Bill of material - based on the configuration (see below) if you enter a quantity with decimals for a part number for which the Basic UOM is EA the system displays a message "Unit of measure EA does not support decimal places" THIS IS GOOD AS EXPECTED
While transacting using MB1B, MB1C, MB1A, MFBF, MIGO or other transactions the system DOES NOT check and it is currently allowing us to post with decimals (1.25, 1.312) for part number for which the unit of measure is EA.
Was not EA supposed to be an indivisible unit of measure? why is the warning message getting activated while creating or changing a BOM and why not while transacting stock?
We have configured EA in the CUNI transaction as follows:
Int. meas. unit      EA
Commercial           EA              each
Technical            EA              each
Decimal places
float. point exp.
ISO code             EA
                                      Primary code
Numerator            1
Denominator          1
Exponent             0
Additive constant    0.000000       X Commercial meas.unit
Decimal pl. rounding                 Value-based commt
Unit of meas.family

you cannot restrict this behaviour with CUNI customizing, you can only check and stop this in a user exit.
SAP inventory managment allows and stores 3 decimals for any unit of measure. You can only define how it will show the value to the users and how it will round the decimals if it calculates the conversion. But if you enter manually with decimals, then SAP will not round this.
please read OSS Note 931971 - Decimal places in stocks and stock postings
and
Note 77525 - Quantity unit conversion in inventory management

Can we get our own defined Goods Receipt doc type in the [OMBT] tranx?

Hi Friends,
We copied and defined new goods receipt document types for our internal purpose to define new number ranges for each document type?
Actually we have two types of Goods receipts which are identified by different number ranges.
So we defined two Goods receipts document types which are not appearing in the OMBT transaction code to assign new number ranges.Is there any settings to do this to appear in this transaction.
Can we have different number ranges for these two different goods receipts?
Thanks in advance...
Regards.....KB

Hi
In whcih transaction were you able to create a new GR document type.
I am not sure what doucment type you have created.
Document types similar to WE , WA, WI cannot be created.( Not accounting document types)
These document types are attached to the Transaction such as MIGO, MB1A, MB1B, MB1C.
You cannot have two different number ranges based on document types in Goods receipt transactions.
Thanks & Regards
Kishore

BAPI's in ECC 6.0

Hi,
What are the corresponding BAPI's for these transaction in ECC 6.0
MB1B
MB1C
VA01
F-02
F-30
Regards,
Karthik.k

Hi.
I know 2 of them.
F-02: BAPI_ACC_GL_POSTING_POST, BAPI_ACC_DOCUMENT_POST
F-30: POSTING_INTERFACE_CLEARING

Problem in Migo BAdi

Hi All...
I have written a BDC for MIGO for Transfer Posting (A08) , with Reference Document (R10)-Others and Movement Type 911.
First I go into the Tcode MIGO and set these parameters and come back.
Then I run the BDC , it runs properly.
But once I change these parameters one or all of them, the BDC does not run properly. It says that movement type does not exist.
While in my BDC , I have assigned the above parameters .So it should run properly for these parameters, but it still shows the error.
Can anyone please suggest me a solution .
Thanks in advance.
Sangeet.

Look at [Note 504936 - Batch input compatibility of new transactions|https://service.sap.com/sap/support/notes/504936]
With release 4.6B, SAP has delivered new enjoy transactions. Examples
are transactions MIGO, MEPO, VL01N, VL02N. These transactions are not
supported for batch input processing. For details please read notes
304122,381630 457925 and 491875.
or [Note 304122 - MIGO: Batch input and CATT not supported|https://service.sap.com/sap/support/notes/304122]
Reason and Prerequisites
The new goods movement transaction MIGO is not intended for use with batch input and CATT.
The reason for this is that batch input and CATT are based on the screen technique, the Enjoy transactions like MIGO (single screen transactions) work more and more with the control technique. Batch input and controls are not compatible.
Solution
There are two alternatives:
Use the following BAPIs to post goods movements in the background:
      Object name: GoodsMovement
      Object type: US2017
      Method:       Cancel (cancel goods movement)
                    CreateFromData (post goods movement)
The old goods movement transactions (MB01, MB0A, MB1A, MB1B, MB1C, MB31) are still supported. These transactions support batch input and CATT.
(BAPI refers to function module BAPI_GOODSMVT_CREATE)
Regards

Inspection lot number ranges skipping

My inspection lot number ranges are skipping, those are std number ranges like 01 origin, 04 origin etc, what could be the reason for that.
Inspn lots are getting generated and I took UD also. But certain numbers in the range got skipped.
Eg:- Incoming inspn lot 010000000041 then it comes 010000000045
Lot numbers 01/42, 01/43, 01/44 does not exist in sytem.
Please suggest a way out
Thanks
Vineeth
Edited by: vineeth varghese on Jul 18, 2008 11:31 AM

Craig,
But expert suggestion says, not to switch off buffer thru SNRO as it may affect fuctionality as you said early in this discussion.
But I believe, this is to be relooked by SAP as number range skipping is not good (My case its skipping 5-7 numbers at a time). But I am not convinced with the reply from SAP also.
Anyway thanks to you craig for your advice.
SAP Note on this matter for reference of all. Thanks
================================
Note: 62077
Summary
Symptom
Gaps (jumps) occur when allocating internal numbers.
The status of the number range interval does not match the number that was last assigned.
The number assignment does not reflect the insert sequence.
IMPORTANT: Read Notes 504875 and 678501.
Other terms
Document number, number range, number range object, buffering, current number level, trip number assignment, number interval, CO document, CO actual posting, inspection lot, material document, physical inventory document, production order number, planned order number, process order number, maintenance order number
FB01, VF01, KO88, KE21, KE11, FD01, FK01, XK01, XDN1, MB01, MB0A, MB11, MB1A, MB1B, MB1C, MB31, KANK, KB11, KB13, KB14, KB41, KB43, KB44, KB21, KB23, KB24, KB31, KB33, KB34, KB51, KB53, KB54, PR01, PR02, PR03, PR04, PR05, XD01, VD01, MK01, SNUM, SM56, SNRO, VL01, VL02, CO01, CO40, CO41, VA01, MR1M, MIRO
Reason and Prerequisites
A large number of number range objects are buffered. When the system buffers a number range object, it does not update numbers individually in the database but reserves a preset group of numbers (depending on the number range object) in the database the first time a number is requested, and makes these numbers available to the application server in question. The following numbers can then be taken directly from the application server buffer. New numbers are not used in the database until the application server buffer has been used up.
The effects described under "Symptom" are a direct consequence of this:
If an application server is shut down, the numbers that are left in the buffer (that is, that are not yet assigned) are lost. As a result, there are gaps in the number assignment.
The status of the number range interval reflects the next free number that has not yet been transferred to an application server for intermediate buffering. The current number level therefore does not display the number of the "next" object.
The current number level (for each server) can be displayed using Transaction SM56. Call transaction SM56 and choose the menu 'Goto' -> 'Entries'. In the dialog box, enter the client, the affected number range object (for example, RK_BELEG) and possibly the required subobject (corresponds to the controlling area for the object RK_BELEG).
If you use several application servers, the numerical sequence will not reflect the (chronological) insert sequence because the numbers are buffered separately on the individual hosts.
Buffering the number range objects has a positive effect on performance, because the system no longer has to access the database (number range table NRIV) for each posting. Furthermore, a serialization of this table (database locking) is prevented to a large extent so that posting procedures can be carried out in parallel.
Solution
Since number range buffering does not cause any expressly assured qualities to be lost, no correction is required.
If you still require continuous allocation, you can deactivate the number range buffering specifically for individual objects.
Proceed as follows:
- Start Transaction SNRO and enter the affected object.
- Choose 'Change'.
- Deactivate buffering: Choose 'Edit' -> 'Set Up Buffering' -> 'No Buffering'.
- If you want to change the buffer size only, enter the corresponding value in the field 'No. of numbers in buffer'.
- Save the changes.
Please note that this change is a modification. The modification is overwritten as soon as the affected number range object is redelivered - in other words, you must check the change manually each time you import a release.
In particular, read Note 678501, bearing in mind that changing the buffering type - if not explicitly recommended by SAP - constitutes a modification. For other possible solutions, refer to the following notes:
179224, 599157 and 840901.
For the the following number range objects, gaps may cause users to have doubts since they are 'expecting' a sequential numbering:
Area CO:
- RK_BELEG   (CO Document)
CAUTION: Note that the problems described in Notes 20965 and 29030 may occur if you deactivate buffering.
- COPA_IST (Document number in actual posting)
- COPA_PLAN (Document number in planned posting)
- COPA_OBJ   (Profitability segment number)
Area FI:
- DEBITOR    (Customer master data)
- KREDITOR   (Vendor master data)
Area HR:
- RP_REINR (Trip numbers)
Area PM, PP, PS
- AUFTRAG    (Order number, production, process, maintenance order, network number)
- QMEL_NR    (Number range - message)
Area MM:
- MATBELEG   (Material documents)
- MATERIALNR (Material master)
Area QM:
- QLOSE      (Inspection lots in QM)
- QMEL_NR    (Number range - message)
- QMERK      (Confirmation number)
- QMERKMALE (Master inspection characteristics in QSS)
- QMERKRUECK (Confirmation number of an inspection characteristic in QM results processing)
- QMETHODEN (Inspection methods in QM)
- ROUTING_Q (Number ranges for inspection plans)
- QCONTROLCH (Quality control chart)
Area Workflow:
- EDIDOC     (IDocs)
Number range buffering can be activated or deactivated at any time.
Number range objects that have to be continuous due to legal specifications (for example, RF_BELEG, RV_BELEG), or due to a corresponding application logic must not be buffered using the buffering type 'Main memory buffering'. See also Notes 37844 (for RF_BELEG) and 23835 (for RV_BELEG).
Header Data
Release Status: Released for Customer
Released on: 10.07.2007 12:57:00
Priority: Recommendations/additional info
Category: Consulting
Primary Component: BC-SRV-NUM Number Range Management
Secondary Components: CA-GTF General Application Functions
BC-SRV-ASF-UOM Unit Management
CO Controlling
CO-OM-CCA Cost Center Accounting
CO-OM-CCA-A Master Data
CO-PA Profitability Analysis
FI Financial Accounting
FI-AP Accounts Payable
FI-AR Accounts Receivable
FI-GL General Ledger Accounting
FI-TV Business Trip Management
LO-MD-MM Material Master
MM Materials Management
MM-IM Inventory Management
MM-IM-PI Physical Inventory
PM Plant Maintenance
PP Production Planning and Control
QM Quality Management
QM-PT Quality Planning
QM-QN Quality Notifications
Edited by: viny on Jul 23, 2008 9:18 AM

Reason for Movements for selected movement type in MB1A/B/C

All,
When a user goes to MB1A, MB1B, MB1C and selects a movement type is there a way to show only the reasons for movements for that selected movement type?
Currenlty, when the users clicks F4 or wants to view the options available for reasons for movements, it shows them EVERYONE movement type and its associated reason for movement. The list is HUGE. So, I want to know to shorten the list to show only the applicable ones for the movement type the user has selected.
I know the user can enter the movement type and the list gets filtered but this is a manual step the user must perform. Is there any way the system can restrict the reasons for movements based off the Movement Type already selected by the user?
Please let me know how to show only those reason codes for the selected movement type in transactions MB1A, MB1B, and MB1C.
Thanks for your help in advance!

To shorten the list you can select the movemnt types the user requirs and make his/her personal list so when he.she do f4 onlt personal list will be displaed.
U can create personal list by doing the F4 and put cursor on movement type and below will be icon to add into personal list.after selecting all the movement types. close the window and adain do f4 u will only see the entries of u r personal list.

Missing orders in SAP-Gap in number assignment

Hi All,
We are facing a situation where there is a gap in assignment of order numbers. We do not have any trace of any failed updates in ST22,SM13 etc. Does this mean that we missed only a "number" and not an order? Is there any other transactions that can give some information on this? Do we have any documentation from SAP that talks of a similar isssue?

<b>This is report I used for FI = RFBNUM00</b>
<b>FYI</b>
OSS note # 62077
Symptom
Gaps (jumps) occur when allocating internal numbers.
The status of the number range does not match the number last assigned.
The number assignment does not match the insert sequence.
Additional key words
Document number, Number range, Number range object, Buffering, Current number level, Trip number assignment, Number interval, CO document, CO actual posting, Inspection lot, Material document, Physical inventory document, Production order number, Planned order number, Process order number, Maintenance order number
FB01 VF01 KO88 KE21 KE11 FD01 FK01 XK01 XDN1 MB01 MB0A MB11 MB1A MB1B MB1C MB31 KANK KB11 KB13 KB14 KB41 KB43 KB44 KB21 KB23 KB24 KB31 KB33 KB34 KB51 KB53 KB54 PR01 PR02 PR03 PR04 PR05 XD01 VD01 MK01 SNUM SM56 SNRO VL01 VL02 CO01 CO40 CO41 VA01 MR1M MIRO
Cause and prerequisites
A large number of number range objects are buffered. When buffering a number range object, numbers are not updated individually in the database, rather, the first time a number is requested, a preset group of numbers are reserved in the database (depending on the number range object) numbers and these are made available to the application server in question. The following numbers can then be taken directly from the application server buffer. If the application server buffer is exhausted, new numbers are generated in the database.
The effects described under "Symptom" then result:
If an application server is shut down, the numbers that were left in the buffer (that is, that are not yet assigned) are lost. As a result, there are gaps in the number assignment.
The status of the number range interval reflects the next free number that was not yet transferred to an application server for intermediate buffering. The current number level does not therefore display the number of the "next" object.
The current number level (per server) can be displayed with Transaction SM56. Start Transaction SM56 and branch into the menu 'Goto' -> 'Entries'. In the dialog box, enter the client, the affected number range object (for example, RK_BELEG) and possibly the required subobject (corresponds to the controlling area for the object RK_BELEG).
If several application servers are used, the chronological insert sequence is not determined by the numerical sequence on the individual hosts, due to the separate buffering on the various servers.
Buffering the number range objects has a positive effect on the performance as no database access (on the number range table NRIV) is required for every posting. Furthermore, a serialization of this table (database blocking) is prevented to a large extent so that posting procedures can be carried out in parallel.
Solution
As the number range buffering does not lose any guaranteed attributes, a correction is not required.
If you still require a continuous allocation, you can deactivate the number range buffering deliberately for individual objects.
Proceed as follows:
- Start transaction SNRO and enter the affected object
- Press the 'Change' pushbutton
- Deactivate buffering: Menu 'Edit' -> 'Set buffering' -> 'No   buffering'
- If you only want to change the buffer size, please enter the   corresponding value in the field 'No. of numbers in buffer'
- Save the changes
Please note that this change is a modification. The modification is overwritten as soon as the affected number range object is redelivered - that is, you must check the change manually after every import of a maintenance level.
For the the following number range objects, gaps may cause user insecurity as a sequential numbering is 'expected':
Area CO:
- RK_BELEG   (CO Document)
Caution: Note that the problems described in notes 20965 and 29030 can occur if you deactivate the buffering.
- COPA_IST   (Document number during actual posting)
- COPA_PLAN (Document number with planned posting)
- COPA_OBJ   (Business segment number)
Area FI:
- DEBITOR    (Customer master data)
- KREDITOR   (Vendor master record data)
Area HR:
- RP_REINR   (Trip numbers)
Area PM, PP, PS
- AUFTRAG    (Order number, Production, Process, Maintenance order
number, network number.)
- QMEL_NR    (Number range message)
Area MM:
- MATBELEG   (Material documents)
- MATERIALNR (Material master)
Area QM:
- QLOSE      (Inspection lots in QM)
- QMEL_NR    (Number range message)
- QMERK      (Completion confirmation number)
- QMERKMALE (Master inspection characteristics in QSS)
- QMERKRUECK (Completion confirmation number of an inspection
             characteristic in QM results processing)
- QMETHODEN (Inspection methods in QM)
- ROUTING_Q (Number ranges for inspection plans)
- QCONTROLCH (Control chart)
Area Workflow:
- EDIDOC     (IDocs)
Number range buffering can be activated or deactivated at any time.
Number range objects that must be continuous due to legal specifications (for example RF_BELEG, RV_BELEG), or due to a corresponding application logic must not be buffered with the buffering type 'Main memory buffering'. Please see also notes 37844 (for RF_BELEG) and 23835 (for RV_BELEG).
Source code corrections
Thanks
SK

Userexit in mb1b, mb1c

Similar Messages

Maybe you are looking for