Process efficiency: transfer of stock between 2 sites

I'm looking for some input/experience concerning the comparison of user workload "in minutes" for WM Transfer of Stock between (2 storage types) (process in 2 steps: step1: transfer "issue"- Step2: validation of transfer) and Shipping between 2 SAP plants in the same company code based on MM SA - SD SA + Goods receipt.
Thanks

Hi Umesh,
It would be a business decision i suppose. If those 5 nos. are lost / damaged in transit & needs to be scrapped, then the ownership needs to be decided first. If it lies with the sender, then reverse the 5 nos. (MB1B mvt is 314) & then proceed with your scrapping or if it lies with the receiver then receive the 5 nos & then proceed with the scrapping.
Posting in system is one aspect, but a clear business rule is the key factor. So discuss with your materials mgmt personnel to define the process flow.
Hope the above helps.
Regards,
Vivek

Similar Messages

Transfer of stock between the storage types in WM

Hi Gurus,
can any one tell me the proceedure how to transfer a material in warehouse between the storage types.
For example if i have a stock of 100 Nos.ina warehouse of storage type 916 (Goods issue for Deliveries) Ineed to transfer this stock to my permanent bin Storage type of 001.
Sunil

Hi
Use LT01 & create Tansfer order (TO), Input material ,plant,storage location.
Provide the required inputs like Source & destination storage type,storage section & Bin numbers.
Finally confirm the TO, it will be done.
Regards,
Ravindran

Transfer blocked stock between plants.

Hi everyone !
Pls. I need to transfer blocked stock from plant A to plant B.
The point is stock must be blocked in plant A and then I have to transfer to plant B, but stock must always be blocked just to avoid the selling process.
Thanks a lot for help !
Regards.

if you want do it with SD deliveries, then the answer is: not possible
but pure MM movements........
By changing the field selection for movement type 325 you can open the field 'receiving plant'. this will then allow a plant to plant movement of blocked stock. Whether you should do it or not is of course up to you.
I doupt that it is possible to do a 2-step movement for blocked or QI stock, because the 303 post the quantity to transfer stock. And transfer stock has no sub categories like QI or blocked. It is on the same level.
There is an OSS note 448761, it is for another transaction, but it might help you a bit to understand.
amongst other things following is said:
There are not two-step movement types for blocked stock since no stock in transit, quality inspection exists .
Edited by: Jürgen L. on Jun 10, 2009 9:46 PM

Transfer consignment stock between special stock partners

Dear Friends,
we have a scenario wherein i have two special stock parnter defined for the consignment stock processing. i want to transfer some material from one stock partner to another stock partner.
can someone help regarding this scenario.

Dear rahul patil
To reduce special stock for a particular sold to party, you can use MB1A / 291W so that it will ask for customer code, where you need to define the sold to party. Similarly to add stock, you can use MB1A / 292W. But b4 doing this, check in development and get concurrence with your FI people also for accounting implications.
thanks
G. Lakshmipathi

Transfer of stock between two storage locations within a plant in two steps

Hi,
We have a plant 6400 & we have two storage locations 6401 & 6402. Each storage location belongs to a department which are located at some distance from one another.
The material to be moved from one storage location to another using a truck.
For the above mentioned process can we have the following process
(1) In first posting the material is issue from the storage location to a transit
(2) In second posting the material from the transit is received into the storage location
I am looking for a feature that is possible between two plants, can we have a similar feature available within a plant.
Warm regards,
Umesh

Hi Umesh,
It would be a business decision i suppose. If those 5 nos. are lost / damaged in transit & needs to be scrapped, then the ownership needs to be decided first. If it lies with the sender, then reverse the 5 nos. (MB1B mvt is 314) & then proceed with your scrapping or if it lies with the receiver then receive the 5 nos & then proceed with the scrapping.
Posting in system is one aspect, but a clear business rule is the key factor. So discuss with your materials mgmt personnel to define the process flow.
Hope the above helps.
Regards,
Vivek

Transfer Special Stock between Plants

We would like to transfer a special stock assigned to a sales order from one plant to another plant with delivery documents. We doesn't want to use the transaction MB1B with the code movement 301E which does the transfer in one step without devlivery document. We would prefer to use the STO procedure but we doesn't know how to assign the special stock to the stock transfer order. Is there any solution?
Thanks.
Edited by: Couny Christophe on Aug 18, 2011 3:58 PM

it is possible see OSS note 92231
643 : Goods issue for a cross-company-code stock transport order via Shipping
645 : Goods issue for a cross-company-code stock transport order in one step via Shipping
With these two movement types, you can work with both valuated and nonvaluated sales order stock (E).

Transfer project/ SO stock between 2 storage locations of same plant

HI,
We have a requirement in which the we have to transfer project/sales order stock between 2 storage locations of the same plant.

Transfer between storage location.
   311 Q - Project Stock
   311 E - Sales Order Stock
Transfer between storage location to own stock
   411 Q - Project stock to own
   411 E - Sales Order to own

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.

Differences between stock transfer, transfer posting, stock transport order

Hi all,
           what is the differences between stock transfer, transfer posting, stock transport order
cheers
bandhan

Hi Bandhan Roy
Stock transfer:
            stock has been moved from one location to another. Here there is a physical movement must occured.
Transfer posting:
           here may be or may not be physical movement is occured. but here the stock type is changed. transfer posting should affect the characteristci of a stock.
Stock transfer order:
            We have to do transfer the stock through order is called stock transfer order...
regards,
sathes

Transfer of Goods between Center (2 Steps MM-SD)

Hi Friends;
I have a little problem to which I have done several tests and did not have much success to complete the activities related to the transfer of goods between centers using the procedure I describe below:
- ME21N -> Creation of Purchase for transfer using the category UB (Stock Transport Order);
- VL10B -> Process documents for Shipping (using Purchase Order);
- VL02N -> To Process Delivery (Picking and deposit);
- J1B3N -> Issue of the tax document (invoice);
- MB0A -> Entry of Goods to Purchase Order;
The problem is that when I am doing the PO (First part of the process) I notify the PO type, in the field I meet the supplier center provider, I meet the item and the center of will receipt the goods. After all information completed on the screens of Purchase Order (ME21N) the system displays the following message.
u201CNot possible to determine shipping data for material 9999999u201D
u201CMessage no. 06280u201D
As this is the beginning all of process, I am not able to continue. I already made several checks which I will describe below, and still am not successful in completing the process.
u2022     The material is already expanded to the Center Supplier and Receiver;
u2022     The material is already expanded to SD View, with the sales organization, distribution channel and sector of activity properly;
u2022     Customer (center) already expanded to the Organization of Sales and Channel Distribution properly;
u2022     On the table is expanded KNVV you both for the organization's sales center provider for the center as recepitor;
u2022     On IMG:
    o     It was the assign of the sales organization of the center (Materials Management -> Purchasing -> Purchase Order -> Set up
        Transport Order -> Define Shipping Data for Plants);
    o     It was assigned to the Shipping Points (Logistics Execution -> Shipping -> Basic Shipping Functions-> Shipping points and
        Good Receiving Point Determination -> Assign shipping Point). Therefore the u201CShipping Conditionsu201D is properly linking to
        Custumer Data Master and Loading Group is properly to Goods Master Data.
Even with all these settings made, I am not having success in the process of creating of PO and start the procedure for transfer of material between centers and so I ask the help of colleagues to help me find what is still missing or set up in process that can make it flow.
Beforehand, Thanks a lot.
Vinicius

Hi ,
GOTO IMG -> MM->PURCHASING ->Purchase Order ->Set up Stock Transport Order->Define Shipping Data for Plants-
here for both receiving and supplying plant give the same sales org , distridution channel and division .
And in receiving plant maintain the customer no .
And one more thing do the PO as document type NB (standard order ) , then maintain delivery type NLCC against NB in customizing (GOTO IMG -> MM->PURCHASING ->Purchase Order ->Set up Stock Transport Order ->Assign Delivery Type and Checking Rule )
Regards,
Anupam
Edited by: Anupam Halder on Jul 28, 2009 7:07 PM

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

Issue in WM enabled with HU (Transfer of stock frm Quality to Unrestricted)

Hi,
We've a scenario in such a way of both WM with HU engagged together.
Transfer of a Material from Quality to unrestricted stock type using transfer posting.
1. in MB1B using mvt 321, stock of Matl A with qty 20 has been transferd from Quality to unrestricted.
2. Due to HU mapped, an OBD for posting change had been created.
3. wrt OBD, matl get packed,(as per packing instruction) which is identified with the HU no.
4. Subsequently a TO had been created and confirmed.
as of this stage the stock view in IM & WM is as follows:
IM
Unres   -
    nil
Quality ---      20
Due to effect of PCN, TO has been created to transfer the stock catogry within the same bin
WM
Bin 1 (Q)    20      ---            922 (Q)       20
922          20     ---           Bin 1            20
5. Then as per the process of completion PGI has to occur so as to nullifying the the -ve stock in 922 storage type
so the stock levels will be
IM
Unres --- 20
Quality --- nil
WM
Bin 1              20
Issue case :
A mannual TO has been created moving the stock from Bin 1 to 922 , without doing step 5 (i.e w/o completion of PGI).
This lead my stock figs as
IM
Unres    -
nil
Quality -
20
WM
922(Q)              20
This also causes storage unit status as " To be Picked". leads to stuck up to proceed further.
We also tried to do mannual TO to transfer the stock from 922 to BIn 1. Due to unavailabilty of the stock system throws error as -ve stock is not possible for 922 Storage type..
Seeking experts to help out this issue if possibly w/o any customising settings.
Regards,
Prasanna
Edited by: prasanna govindarajan on Sep 22, 2010 2:55 PM

Dear Venkat,
There is a tick mark in post to inspection stock indicator thereafter inspection lot tab in qa32 or qa11 is not activated.
Secondly, this is a stock item.
Thirdly, No PS module is implemented in my client
I think the user has posted the stock through MB1C with Movt.Type 503 into quality stock.At the time of this posting the 05 inspection type is not activated in QM view of Material Master thatswhy system does not created any inspection lot for this.
After some days,with out stock posting from inspection stock to unrestricted stock,he has activated 05 inspection stock for the first time.
Pl.suggest any possible solution .
Prashant

Very imp stock transfer and stock transport order

hi folks,
please explain me in detail the difference between stock transfer and stock transport order.
regards,meena

Hi:
Stock Transfer is the physical movement of material from one location to another location,stock transport order is one way of doing the stok transfer.
Stock can be transfer between plant to plant,company code to company code,storage location to storage location.
However there are different procedures for stock transfers:
1.Stock Transfer using one step procedure: Here Goods issue and Goods receipts happens in single step.
2.Stock Transfer using Two stage procedure:The two-step procedure allows you to monitor the stocks in transit. After the goods issue is posted at the issuing point, the stock appears "in stock transfer" at the receiving point and is managed as such in the system.
3.Stock Transport Order:
This is transfer of material from one plant to other plant or co.code to co.code via SD route.
Here a.receiving plant raise the stock transport order on issuing plant.
       b. Issiuing plant creates the outbounmd delivery against STO and PGI.IF it is in India,then excise
           invoice creation.
       c. Receiving plant post the goods receipt against outbound delivery and post the excise ivoice.
       d. Invoice verification.
The main advantage of Stock Transport order is you have a more control because you can have purchasing document behind itand you can check the PO history which would gives all the details for Delivery as well GR documents.
However ftor STO via SD you need to configure the set up stock transport order in MM>Purchasing>Purchase Order-->Set Up Stock Transoport order.
Also on a data maintanace side you need to maintain the custmor and vendor relations.
Hope this would helps you.
Cheers
Rahul
Awards plz.if helpful.

Importing keywords from stock photography sites

We purchase a lot of images from stock photography sites, such as Shutterstock and iStockphoto.
We have been using a software called QPict to catalogue the images. QPict is no longer supported.
We'd like to shift to Lightroom or possibly Bridge. Is there a way to automatically import the images along with their keywords from those sites?
In QPict, I've had to find an image, go to the site, copy out the keywords and paste along the image in the catalog. Very tedious process, especially that QPict had limitations as to the number of keywords per image that you could import. Took forever just to catalogue a few dozen photos. We have thousands.
Any help would be greatly appreciated. For the life of me, I cannot find any help in Google or any forums I've visited.
Thank you in advance.

Hi
I try to give you few brief answers.
1) I have almost 1000 keywords (including synonyms) and I don't have problems. But at least some previous versions of Lightroom were unusable with controlled vocabularity keyword set which contains something like 11000 keywords. I haven't recently heard any comments about large quantity of keywords. So someone with more experience should comment on that.
2) You can import keyword hierarchy to Lightroom from text file. File should have keywords in tab intented hierarchy, with one keyword in line. If I recollect correctly the file should be in UTF-8 character set (this is important if you have some non ascii characters in keywords). Synonyms are marked with {} and keywords that are not exported with [].
3) Synonyms are written as keywords when images are exported. As far as I know current search tool does not support synonyms (yes, this is weird).
Hope this helps at least a bit.
Jukka,
Finland

Suddenly slow transfer of files between computers over LAN

All, I have the following: HP Desktop, XP Pro, SP3, with Maxtor external HD Dell Laptop, VISTA Business, SP2 Both 32 bit Both running Norton Internet Security 2011, including firewall Linksys WRT54GL router V1.1, connected to DSL The external HD is configured to share over the network. I use it to move files between the twp computers, and to access the Internet. It has been working fine for about 3 years. Everything is still working, except that the speed of transfer, either direction, between the laptop and the external HD has dropped to nearly zero. Files that used to take a minute or so to transfer now literally take hours, and depending on the software, may time out. The problem is not so much the speed over the network, but that the data is only sent in short bursts, with long, many seconds, delays between. As the file progresses, the process gets worse. Typically, it takes as long to send the last 10 % as the first 90%. In the past, the data was sent in a continuous stream. The access between the laptop and the Internet is still fine. I am in a rural area, and have verified that there is no other WiFi to interfere. Using my backup program, I have rolled both my computers back to a time when everything was working. The problem still exists. That seems to point to the router. I have flashed the most recent firmware and reconfigured, but not help. Google turns up lots of hits, but nothing that fits this. Any suggestions on what to do next? For now, I am just swapping the USB drive physically. Alan

Try to reset the router and reconfigure it.
Press and hold the reset button on the router for 30 seconds. Release the reset button and wait for 30 seconds. Power cycle the router and reconfigure it.
Change the MTU size to 1365. Save the settings.
Go to Wireless tab and click on Advanced wireless settings. Change the Beacon Interval to 75, RTS and fragmentation threshold to 2304. Save the settings. Power cycle the router and see if that helps you.
Disable or turn OFF the firewall or Anti-virus software on your computer.

Process efficiency: transfer of stock between 2 sites

Similar Messages

Maybe you are looking for