Std SAP Programme , transfer the GR Batch Material to Block Stock.

Hi All ,
Could you please tell , which is the Std SAP Programme , transfer the GR Batch Material to Block Stock. (ECC 6.0)
Thanks & Regards,

such transfers will be made with movements, movement can be created with MIGO transaction or the old transaction MB1B (and several more)
Just goto SE93, enter the transaction code, display the detail and you will find the program name.

Similar Messages

How to transfer material from blocked stock to scrap location

Dear Experts,
Weu2019ve put some of raw material into blocked stock. Now we want to scrap these materials & for that Iu2019m trying to take it to unrestricted stock from blocked stock by MIGO (transfer posting ,Mvt type=343).
But during that system shows an error message that u201CBest before/SLED of batch has been exceededu201D
Due to this Iu2019m not able to scrap the material from blocked stock.
Pls advise what to do .Is there some other way to do it??
Thanks in advance

Hi,
You can directly scrap it from Blocked stock using movement type 555 . Further from the message it is observed that SLED( Self Life Expiration Date ) check is active for this material in material master . Try to scrap it in 555 mvt .
Dhruba
Edited by: Dhruba Charan Behera on May 18, 2011 12:51 PM

Transfer posting from material to material ( for blocked stock)

Dear All,
Whether transfer posting from material to material can be done for blocked stock also? because through 309 movement type i did not find any option, so let me know if there is any option
Regards,
Balakrishna R.V

Dear
Transfer posting of material can't be done if material is in Block Stock.
When block stock is inspected in quality test in inquality inspection stock then it goes to Unrestricted use stock.
finally Transfer posting is possible for unrestricted use stock material.

Withdraw material from blocked stock at subcontractor

Hi
We have Third Party Order process where in materials are directly received to subcontracting vendor stock, when Goods receipt is posted in receving plant.
Due to some error, few stocks have been posted to Blocked stock at Subcontractor.
We would like to transfer the stock to unrestricted stock / scrap the stock from Subcontractor blocked stock.
Kindly let me know your opinion to make transfer posting.
Thanks and Regards
Rajkumar

Dear Yadav,
1.
Firste you wrote:
Due to some error, few stocks have been posted to Blocked stock at Subcontractor.
After that you stated this
It is about restricted stock at subcontractor.
2.
And materials are not subjected to batch management. So we cannot use MSC2N.
So, your first statement was that the material is in "blocked" stock, after that you stated that it is in restricted-use stock. But you also stated that the material is not batch managed.
"Restricted-use" is the status of the batch, so your material should be batch managed if its status is restricted-use.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/a5/63396b43a211d189410000e829fbbd/frameset.htm
As I wrote you can use MB1A +553O if your material is in QI stock, if it is in restricted use you can't. If it is in restricted-use, please use MSC2N to change its status to unrestricted and after that comes MB1A + 551O.
What is the real stock type the stock you are speaking? Who "posted" it to that stock type and how?
Please give EXACT information.
Thanks,
Csaba
Edited by: Csaba Szommer on Feb 10, 2009 10:50 AM

Material at Blocked stock

Hi to All,
How can i unbloked the material, i created PID to adjust inventory 702 but it used awrong movement type 707
can you please help me on how to reverse the block stock what are the transaction code and movement type
Thanks,
Ermin D. Concepcion

Hi Ermin,
You can try movement type 343 to transfer the stock from blocked stock to unrestricted stock
via MB1B or MIGO_TR.
Thanks and regards,
Polly
Edited by: Polly Gan on Apr 26, 2010 9:01 AM

New Tab in WBS Elements & need to pull fields from Std SAP Tab to the New

Hi All,
I would like to create a new TAB in WBS Element & I need to pull fields from Basic data tab,Origanization Tab,Control Tab & user Fields Tab to the New Tab.
Basically my clients wants to see all the fields (based on the requirement) in one TAB.So user will directly go to the Custom Tab & enter the input data & save.
So Kindly guide me how to proced.I tried WBS Layouts ,but am confused.
Any ABAP work is required?or can we do it in PS Configuration itself?
Thanks
Suresh

Configuration:
Project System>Structures>Operative Structures>Work Breakdown Structure (WBS)>User Interface Settings>Layout of WBS Element Detail Screens>Define Layout of WBS Element
Detail Screens
Do do something as below:
Project Profile:000CAP1
Act Cat:*
Tab Page ID: TAB01
Tab page Title:Basic Data
ICON_HEADER
Details Screen 1: 2 (WBS Element Basic Data)
Details Screen 1: 5 (WBS elements, organization)
Details Screen 1: 8 (WBS Element: User Fields)
Regards
Sreenivas

How to see the material document for Blocked stock

Hello Experts
I having some blocked stock in plant X , How to see the material document for this stock.
Thanks in Advance
Prashanth.v
Edited by: prashanth.venkategowda on Aug 11, 2010 7:38 PM

which material documents do you want to see?
Material documents can be found and displayed in MB51 transaction.
in MMBE you can put the cursor onto your stock line and then choose from menu Environment > material documents and SAP will list all relevant material documents.
block stock status is not a selection criteria, material number, plant storage location, batch number are selection criterias.
if you want only documents to block stock, then you need to select by movement type, e.g. 343 and 344 are movements that change status from unrestricted to blocked or vica versa.

Transfer the Postings from One G/L Account to the Other

Hi,
I had some postings under one G/L Account. I want to transfer the Open items from this account to the Newly created G/L Account(Open Item Management check box is selected). Please let me know how to do this.
Thanks

Hi Kedar,
There is no standard functionality available in SAP to transfer the open items from one GL to another.
You need to create the new GL with correct settings and pass a manual JV using Tcode F-02.
Thanks,
Srinu

Is there any statement to transfer the data from unix server to another

Hi All,
Is there any statement or function module avaliable in sap to transfer the data from one unix server to another unix server apart from FTP(file transfer protocol).?
My requirement : I need to fetch the data from one unix server to another sap server. i have a option of FTP but i need to transfer the unix data to another server internal table.
I need to move the unix data to another sap sevrver internal table
Regards
Raja

not sure what your exact requirement is, but
if both servers are in the same system group, you could potentially just mount the unix directory from the source machine to the target with nfs mount or something.
if not, you could consider remote function call. create a remotable function module on the source machine to read the data into an internal table, and call that function module from the target machine. this requires creating entries in the RFCDES table (i think via SM59?). on the target machine, you would call function y_whatever destination xyz, where xyz is the RFCDES you set up. it works great.
dave

Archiving batch- material used in inspection lot error

Hai,
I am trying to archive a batch, but I do receive the below message:
u201CMaterial is used in Inspection Lotu201D. Message number W4123.
Prior to this I archived the existing Inspection Lot using u2018QM_CONTROLu2019. The status on the inspection lot is now ARCH. There are no other open inspection lots for this material/batch.
I ran MM_SPSTOCK to archive the associated batch number. But still I get message "Material is used in Inspection Lot".
Note We are not using Long term Inspection.. We are in ECC 6.
Did anyone has this same issue before?
Thank you in advance!
Sonali

Sonali
Just check the existing batch & Material combination - that particular material -recurring inspection09 is selected or anyone of the batch & Material is QI stock.
Thanks
Sami

MM Stock transfer from blocked stock between plants

Dear friends ,
Could I transfer material from Blocked stock between plants but in Blocked stock ?
I not found this movement types in ECC.
best regards,
Ale

It is not possible to move blocked stock between plants.
You have to transfer the stock into unrestricted- then you can move it to the other plant- then again a transfer posting into blocked stock.

Stock Transfer using Two Step (QI & Block stock)

Hi All ,
Is it possible to receive material QI / Blocked stock of receiving plant ??
Another query is ... can I transfer QI / Block stock of supplying plant to another plant ??
I have a business case where I have to transfer QI stock from one plant to another Plant using two step.
Regards/
Suresh

Hi,
As a rule cross-plant stock transfers is done only through unrestricted-used stock only.
BR,
Krishna

No New Batch number creation at the time of Material Transfer Movement(309)

We are upgarding from 4.6C to ECC6.0. We have an issue in regards with the material movement type 309. At the time of creating the material tranfer using the same material as issuer and receiver, the same plant and storage location ( this process is used by the business to diferentiate batches).
In 4.6C a new batch number is created automatically when 309 movement is posted; stock and characteristics transfered are allocated at the new batch created automatically.
The same case in ECC6.0 does not create a new batch as done in 4.6C. We have looked for any SAP note or forum discussion without success.
If anybody has an answer for this issue, let us know.

As a matter of fact these configuration has been checked before, additionally we compare configuration at 4.6C and ECC6.0 and it is the same but the new batch creation (for this specific case) is working at 4.6C, not at ECC6.0.

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

Transistion in SAP to know The Stock For List Of Material

Dear Sir,
Is there any transistion in SAP.
To know the stock for list of material.
For Ex=
I want to know the stock for below material in one shot
1) A
2) B
3) C
4) D
Pls solve my problem soon
Thanks & Regards
Ajay Pareek

Hi Ajay,
Following are the some of Useful T.Codes for the stock Report.
LT51 Maintain Preallocated Stock
LVASE Exit stock from Work Center
LX02 Stock list
LX23 Stock comparison IM - WM
LX27 Stock levels by shelf life exp.date
MB52 List of Warehouse Stocks on Hand
MB53 Display Plant Stock Availability
MB54 Consignment Stocks
MB5B Stocks for Posting Date
MB5K Stock Consistency Check
MB5L List of Stock Values: Balances
MB5OA Display Valuated GR Blocked Stock
MB5T Stock in transit CC
MB5TD Stock in Transit on Key Date
MB5W List of Stock Values
MBBS Display valuated special stock
MBLB Stocks at Subcontractor
MBSF Release Blocked Stock via Mat. Doc.
MBW1 Special stocks via WWW
MC.1 INVCO: Plant Anal. Selection: Stock
MC.5 INVCO: SLoc Anal. Selection, Stock
MC.9 INVCO: Material Anal.Selection,Stock
MC.D INVCO: MRP Cntrllr.Anal.Sel. Stock
MC.H INVCO: Business Area Anal.Sel. Stock
MC.L INVCO: Mat.Group Analysis Sel. Stock
MC.P INVCO: Division Analysis Sel. Stock
MC.T INVCO: Mat.Type Anal.Selection Stock
MC48 INVCO: Anal. of Current Stock Values
MC49 INVCO: Mean Stock Values
MC50 INVCO: Analysis of Dead Stock
MC8M Read Opening Stocks
MCB) INVCO: Long-Term Stock Selection
MCC4 Set Up INVCO Info Structs.from Stock
MCH: RIS: STRPS/Mvmts + Stock - Selection
MCKJ Selection version tree: Stock
MCKR User-spec. sel. vers. tree: Stock
MCNB BW: Initialize Stock Balances
MCSK Call Standard Analyses of Stocks
MD04 Display Stock/Requirements Situation
ME27 Create Stock Transport Order
ME2O SC Stock Monitoring (Vendor)
MF65 Stock Transfer for Reservation
MI35 Batch Input: Post Zero Stock Balance
MILL_ Cutting Stock Transfer
MIQ1 Batch Input: PhInvDoc. Project Stock
MM73 Special Stocks: Preparation
MM74 Archive Special Stocks
MM75 Display Archive of Special Stocks
MMBE Stock Overview
MMBE_ Stock Overview
MMCL Stock Overview by Characteristic
Or you can refer the thread [stock overview;, search there are several threads already available regarding this.
Regards,
Shyamal

Std SAP Programme , transfer the GR Batch Material to Block Stock.

Similar Messages

Maybe you are looking for