Logic for finding transfer order creation date for a given delivery??

Hi,
I am trying to find a logic for connecting the table LTAK which has ERDAT as the T.O. creation date with LIKP/ LIPS table.
Can you please help me with this information.
Regards,
Peeyoosh.

Hi,
Go to LTAP to get the transfer order number based on delivery ltap-vbeln. Then got to ltak to get the Creation date.
Hope it helps
Vinod.

Similar Messages

Upload data for Tcode LT06(Transfer order creation) using BDC -very urgent

hi experts,
I got stucked up in writing a BDC for the Tcode LT06(Transfer order creation using wearhouse number) in MM module,
the problem is like this, when i go to the tcode LT06 , it will ask for material doucument,mat. docu. year and wearhouse number, iam entering the inputs and then press enter, as soon as i press enter it takes me to the second screen where i will be selecting the item and then click on the button called 'Generate TO item'
here the problem arises, as soon as i click the button iam getting a standard SAP error message(No Destination Storage Bin found in storage type 'IMP'). Due to this errror iam not able populate the batch input data on the screen, suggest me a proper solution. rewards will given if solution found useful.
Kishore K

Hi ,
I have done the same in Background with BDC and TR Number for Multiple Materials ,
Can u please explain the scenario, so then I would be able to try for solution ?
Warm Regards.

Error Handling for Background/Update Tasks (Transfer Order creation) - How?

Hi,
I have a standard process for creating a Transfer Order and 2 user-exits that I have implemented.
The user exits are used to transfer information during Transfer Order creation.
However, the user-exits also check data in table TVARV and other. As such, error handling needs to be implemented, since the T.O. might or might not go through, depending on data validation and related.
However, the user-exits are implemented during creation, which is an update task that runs in the background. This makes it impossible to output any information or error messages.
What else can be done in regards to outputting a message, since the user will need to see some sort of message that the process failed, that the T.O. didnu2019t confirm? Can an SAP inbox message be created and how?
Please help.
Thank You,
John

Hi,
Please check the following link for all the function modules and user exits on TOs.
http://help.sap.com/saphelp_erp2005/helpdata/EN/c6/f83a294afa11d182b90000e829fbfe/content.htm
Reward points if it was helpful.
Regards
Abhishek
Edited by: Abhishek Raj on May 29, 2008 10:20 AM

No Automatic Transfer order creation upon usage decision for 553 mtype

Scenario: We have quality and warehouse management active. Goods receipt is done against a purchase order. Stock comes into 902 storage type under stock category u201CQu201D. From 902 storage type, Goods issue to scrapping under quality( using IM movement type 553 ) is done using QA11. Normally, once GI to scrap under quality is done at IM level, WM movement type 551 gets triggered automatically in the background which creates a transfer order to move stock from 902 to 999 storage type under u201CQu201D stock category.
Problem: System unable to find storage bin for storage type 902 Q.
In our system, automatic TO creation from TR isnu2019t happening once the usage decision for 553 movement type happens. The TO creation process couldnu2019t recognize the stock which is available as u201CQu201D. It throws an error message u201Csource storage bin could not be foundu201D at the time of TO creation from TR. Putaway strategy for the physical storage types is FIXED BIN, MIXED STOCK ALLOWED and ADDITION TO EXISTING STOCK. 902 storage type has ADDITION TO EXISITNG STOCK and MIXED STOCK as a putaway strategy.
We have already activated auto TO creation settings at WM-IM reference movement types interface configuration.
Is there any setting missing at QM-WM interface?
Can someone please tell us a methodology to activate this transfer order creation process (WM mtype 551) for 553 IM mtype ?
Thanks in advance. Please reply.
Regards
Preetinder Singh
Phone: 404-468-8422

Hello,
I do not understand your scenario , u are saying are posting inspection lot to non WM storage location and again saying system can not find bin automatically.
"A transfer requirement (movement type 311 / destination u201C921 Transferu201D) is created after the inspection lot posting (QA11) but the auto-creation functionality is not possible since the u201CSystem cannot find source storage binu201D.
How can this auto-creation of a transfer order be realized since it is possible to create the transfer order manually via LB11 (entering source u201C902u201D / storage bin u201CPurchase Order no.u201D)?
The system cannot find the storage bin automatically.
Thank you in advance!"
Please let me know are u using quality interim storage area. If you clear material from quality and want material to go to bin then it should be warehouse managed storage location.
Regards,
Prashant

FM or BAPI for Transfer Order creation in eWM

Hello ALL,
Please provide any FM or BAPI for Transfer Order creation in eWM. i know how to create transfer order in ERP.I tried to find out a FM or BAPI in SCM eWM but failes to get one.
Kindly help.
BR,
Anil..

Hi,
Try using FM WS_LM_TRANSFER_ORDER_CREATE.
I hope this is available in ur system
Thanks

Sales order creation - data stored in which tables for customer

Hi experts,
During sales order creation, data entered during sales process is stored in various related tables. Can anyone list the tables where data is stored for customers?
Thank you

Dear Manisha
Once you saved the sale order,
- all header datas are stored in VBAK
- all item level datas are stored in VBAP
- schedule line confirmation in VBEP
- all condition types and values are stored in KONV / KONP
- Partner functions in VBPA
- Delivery related fields like Shipping Point, Delivery Date, Goods Issue etc., are all in VEPVG
thanks
G. Lakshmipathi

Production declaration based on order creation date in R/3

Hi,
Can we do the production declaaration in R/3 (mfbf) for PPDS planned orders sent to R/3 from APO based on order creation date?
This is because we need to differentiate between SNP and PPDS planned orders in R/3.
As there is no differentition in SNP and PPDS orders in R/3, while production decalration,
it's not possible that only PPDS orders will get consumed (in mfbf).
SO can we do production declaration based on order creation date instead of order number?
Please share the information.
Thanks,
Vinayak

Hello Santosh
Production versions are selected on the standard system according to the basic finish date, however, you can change the standard system behavior with the implementation of the following note:
351773 - Selection of production versions for planned order
Alternatively, you may use BAdI MD_MODIFY_PRODVERS to create your own logic to select the production versions.
BR
Caetano

How to fetch post goods issue date and sales order creation date

Hi All,
How to find out the difference between SD Sales Order Item Creation Date and final Post goods issue Date. I would like to know how to fetch those dates and what is the relationship between the tables from which i will get the dates.
Please let me know the solution .
Thanks in advance.

Hi,
Sales order creation date is when u raise a sales order in favor of the customer using VA01.......using ATP logic system purposes the material availability date....
after saving ur sales order...when u raise the Delivery using VL01n w.r.t to OR...than u have to perform picking ....In the picking Tab...specify the amount to be picked than press Post Good Issue....means the goods left the company premises ..
You can the fetch the values using tables- Use T code SE12 or SE16
Vbak-----order header
Vbap-----order item
Vbek-----order schedule line
Likp-----Delivery header
Lips----Delivery item

IDOC generation at time to transfer order creation.

What are the config steps involved for idoc generation at the time of transfer order creation?
please advise.
Edited by: avi on Dec 25, 2008 5:31 AM

Hello,
TO creation with respect to Picking perspective:
Lean WM --> output type WMTA can be used to create TO automatically can be created (you can go to NACE transaction and check the settings of WMTA)
From MM WM perspective i think it is PUTAWAY concept, if Purchase order -->Inbound delivery will be created with ref. to inbound delivery TO (putaway) can be created.
Link for IDoc maintenance:
IMG>LE>WM>Interfaces>external systems-->configure wm
link for Automatic TO creation:
IMG>LE>WM>Interfaces>inventory management-->Activate Automatic TO creation
Mahesh
Edited by: Mahesh on Jan 2, 2009 11:19 PM

User exit at Transfer order creation

i have a user exit named MWMTO001.
it has been given like this will trigger at the end of the transfer order creation (Update task). wt i have done here is i activated the user-exit and when i try to create the TO its not getting stopped over the user-exit and here i didn't understand wt is mean by update task.
regards,
Mahesh.G

Hi,
How is it solved?
I'm facing same problem, would you please advise?
Regards

Sales order Creation date

Hi All,
I see that the sales order creation date in VBAK is suppose 2009.06.16 and in VA03 if i see th document flow the date is 2009.06.15. and quatation date is also 2009.06.15.
Which date is the correct Sales order date.If va03 one is correct what is the source table of this date?
PLease commnet .
Thanks in advance,
Swati

Hi ,
Let me know in which field you are looking into in VBAK table
Please let me know if you still need any help.
Thanks and regards,
Rajeshwar.

Is there any User Exit or BADI- Where LTAP-WDATU is as change parameter ,So during or after Transfer order creation GR date would be as per given logic not as current date

Dear All,
There is a requirement in which when the material (Not batch managed) is getting return from Non WM managed storage location to WM managed storage location than at the time of creating transfer order or after creation of transfer order would like to change LTAP-WDATU (GR date) automatically , So here i am unable to find the right user exit or BADI in which i can write the logic for same. Below is full description of the requirement.
Here we are following Removal strategy "FIFO" while picking the material (Not batch managed) from WM managed storage location (WMS1) & transferring to Non WM managed storage location (ODS) ( than from there it use to go to Production) , at certain times partial quantity use to come back from Non WM managed storage location (ODS) to WM managed storage location (WMS1) and while doing putaway of the same "GR date" use to change which was not the actual when the material 1st time comes to WM managed storage location (WMS1) (before getting transfer to Non WM managed storage location). So here i want the user exit or BADI in which i can write my logic so that GR date ( LTAP-WDATU) would automatically change while creating transfer order or after creation of transfer order as per the "GR date" of same material which last moved from WM managed Storage location (WMS1) to Non WM managed storage location(ODS) because as per FIFO material dated before that would not be exist in the warehouse.
Below is the flow of the material while transferring to production & returning from production.
WMS1 ( WM managed warehouse ) --> ODS ( Non WM managed warehouse) --> Production At the time of issue to production
Production --> ODS ( Non WM managed warehouse) --> WMS1 ( WM managed warehouse ) At the time of return from production
I hope i m clear on my requirement.
Thanks in advance.

1. You have to get a key from SAP to modify the two includes in which the user exits are present.
2. You have to enter statement 'INCLUDE z**. ' in both user exits in the MV45* includes. Then save and activate the MV45** includes.
3. You have to figure out the code that carries out the functionality described in your specifications.
3. Write the code in includes Z** .
4. Now the code written by you will be executed when you run the relevant SD transaction
Message was edited by: Sudhir Bhate

Strategy for selecting Storage Unit for Transfer Order Creation

Hi ppl,
I need to understand what strategy is used by SAP to determine the storage unit while creating a transfer order for delivery using transaction LT03.
It seems that the system selects the SU randomly, but, in the backend, there should be some strategy.
Please let me know how to find this.
Regards.

Hi,
Check the storage type indicator assignment value in the stock removal field in the material master Warehouse management1 tab.
Then go to SPRO->Logistics Execution ->Warehouse management->Strategies -> stock removal startegies. Check the stock removal strategies for the warehouse and storage type (from material master) data. From this data you can understand the details on system proposals.
Regards

Transfer order creation Any User-Exit for item ?

Hi all,
Im working with transfer order. What Id like is to apply to the TO item my own fields.
Is there a possibility to overwrite some of the fields of the LTAP segment at transfer order item creation, using any enhancement (User-exit, ) ?
Transaction used to create TO is LT43.
Ive try to use MWMTO001( but it doesnt work, only for specific data (z table)).
Ive also try MWMTO008 ( doesnt work for that )
Fields I want to overwrite are VLTYP(Source storage type), VLPLA(Source Storage Bin), VPTYP, VLQNR.
Hope someone can help mePlease ?

Hi Erwan,
give MWMTO004(EXIT_SAPLL03A_005) a try. It's a different event/time in document creation, but looks good comparing your fields you want to change.
It's of course not only 'overwriting' VLTYP, VLPLA, ... but implementation of own / additional removal strategy. Might be more complicated, but sounds better for whole process.
Regards,
Christian

User or SAP exit for Batch Status during Transfer Order creation

Hi All,
I would like to know if there's an user-exit or a SAP-exit available with which we could evaluate the status of a batch during the creation of a Transfer Order.
When a production order is created, the system creates automatically a transfer requirement with all the components needed for the production. This TR (Transfer requirement) is then converted into a TO (transfer order) with transaction LT04. Here, we want to control that the status of the batches is not restricted. Otherwise, the user shall not be able to save the TO.
Thanks in advance, I appreciate your feedback!
SS

Exit Name Description
MWM2S001 Exit to Determine 2-Step Picking Characteristic
MWMBAP01 Enhancement for BAPI WarehouseTransOrder.GetDetail
MWMBAP02 Enhancement for BAPI WarehouseStock.GetDetail
MWMD0001 Transfer order print via RLVSDR40
MWMD0002 Transfer order print as multiple process with RLKOMM40
MWMIDI07 Enhancement for Output WMPIHU (Create Pick-HU) Inbound
MWMIDO11 Enhancement for message WMTORD: TO with several items
MWMIDO12 Enhancement for Output WMPIHU (Pick-HUs) Outbound
MWMIDO13 Extension for WMMBXY (subsequent tasks after goods movement)
MWMPP001 Enhancement WM/PP Interface (automatic TR generation)
MWMRF001 RF: Influence Display of material description
MWMRF100 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0100)
MWMRF101 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0101)
MWMRF102 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0102)
MWMRF104 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0104)
MWMRF105 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0105)
MWMRF106 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0106)
MWMRF107 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0107)
MWMRF108 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0108)
MWMRF151 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0151)
MWMRF152 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0152)
MWMRF153 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0153)
MWMRF170 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0170)
MWMRF202 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0202)
MWMRF203 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0203)
MWMRF204 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0204)
MWMRF205 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0205)
MWMRF212 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0212)
MWMRF213 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0213)
MWMRF221 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0221)
MWMRF302 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0302)
MWMRF303 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0303)
MWMRF304 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0304)
MWMRF305 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0305)
MWMRF312 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0312)
MWMRF313 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0313)
MWMRF321 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0321)
MWMRF400 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0400)
MWMRF402 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0402)
MWMRF403 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0403)
MWMRF404 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0404)
MWMRF405 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0405)
MWMRF406 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0406)
MWMRF410 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0410)
MWMRF411 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0411
MWMRF412 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0412)
MWMRF502 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0502)
MWMRF503 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0503)
MWMRF504 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0504)
MWMRF505 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0505)
MWMRF600 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0600)
MWMRF601 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0601)
MWMRF630 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0630)
MWMRF631 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0631)
MWMRF632 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0632)
MWMRF633 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0633)
MWMRF634 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0634)
MWMRF650 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0650)
MWMRF651 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0651)
MWMRF700 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0700)
MWMRF701 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0701)
MWMRF702 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0700)
MWMRF703 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0703)
MWMRF704 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0704)
MWMRF705 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0705)
MWMRF760 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0760)
MWMRF761 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0761)
MWMRF762 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0762)
MWMRF763 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0763)
MWMRF764 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0764)
MWMRF765 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0765)
MWMRF766 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0766)
MWMRF767 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0767)
MWMRF768 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0768)
MWMRF769 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0769)
MWMRF777 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0777)
MWMRF800 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0800)
MWMRF801 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0801)
MWMRF802 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0802)
MWMRF803 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0803)
MWMRF804 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0804)
MWMRF805 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0805)
MWMRF806 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0806)
MWMRF807 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0807)
MWMRF888 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0888)
MWMRF889 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0202)
MWMRF998 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0998)
MWMRF999 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0999)
MWMRFCOD Enhancement for function codedisabling
MWMRFDLV select delivery by user criteria
MWMRFPRT Enhancement for printing
MWMRFSSG user exit for sorting TOs in RF system-guided transaction
MWMRFUP Customer defined general purpose pushbutton called from scr.
MWMRP001 Cust. Exit for Fixed Bin Replenish.: Delivery Item Selection
MWMRP002 Cust. Exit for Fixed Bin Replenishment: TR Quantity Distr.
MWMRP003 Customer Exit for Replenishment using RLLNACH1
MWMRP004 User Exit for Replenishment using RLLNACH4
MWMTO001 Enhancements for end of transfer order generation
MWMTO010 Exit: Calculation of Total Planned TO Processing Time
MWMTO011 Correction of Planned Processing Time for TO Item
Hi,
MWMTO012 Correction of Sorting and Split Transfer Order
MWMTO013 Stock Removal for Sev. Storage Types as in Stringent FIFO
MWMTOAU3 Separate selection of posting changes for autom.TO creation
MWMTR001 Exits at the end of transfer rqmnt creation (IM,PP interf.)
No of Exits: 104
USER EXIT
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.sap-img.com/ab038.htm
http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
USER EXIT
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
Regards,
Raj.

Logic for finding transfer order creation date for a given delivery??

Similar Messages

Maybe you are looking for