Transferorder based on out bound Delivery

Hi all,
I need to create a LT03 (Transfer Order (TO)) based on the delivery. I am trying to find out BAPI's, and i have a BAPI "L_TO_CREATE_DN"
where i am inputing LGNUM and VBELN, So once i execute this BAPI, i am getting error message like -
2-step picking relevance will be removed since no relevant group
But when i go directly to LT03, i am just getting a warning message and if i press enter again TO is getting created.
So pls let me know to create the TO, If that is not correct BAPI, Pls suggest me the correct BAPI.
Thanks
Senthil

Hi,
Instead of above function module, use follwoing function module sequence to create TO for Delivery.
1. L_TO_SET_SPECIAL - Special Ref as Blank and delivery
2. L_TO_CREATE_INT for creation.
Hope this helps.
Nag

Similar Messages

How movement type is determine in out bound delivery?

Hello,
(1) I want to know, how movement type is determine in out bound delivery (item detail --->Administration tab).
If I want to make a setting of customer return, then where can I assign movement type 451 so that it will appear in OBD?
(iii) Please provide me the path of setting of SD document category ex- J,7 etc (Which appears in T-code OVLP)
Thanks,
MMC

Hello,
M type (Tcode OMJJ) is determine into the Delv doc on the bases of Sch line Cat(Tcode VOV6) maintain in your sales order's item level .
The relevant Sch line Cat is determined into sales order on the bases (tcode VOV5 of
I Cat + MRP type (if any) .
And the I cat is determined into sales order based on (tcode VOV4)
Sales Doc. Type + Item cat.group (determined from material Master) + Item usage (if any) + ItemCat-HgLvItm (if any).
The std sch line cat for Return is 651.
If you want to have 451 as M type for your material then copy std sch line cat DN and maintain 'Z' Sch Line cat with your M Type.
And determine the same to your I Cat for return in return sale order.
Before executing your process cycle have a look/check on copying control config for Return Order to Delv in Tcode VTLA.
Hope this can assist you.
Thanks & Regards
JP

How 2 Copy Header & Line Item Text from Purchase Order 2 Out Bound Delivery

Hi SD Gurus,
I want to copy header and line item text from Purchase Order to Out Bound Delivery (This is required in Stock Transfer Process).
I have been able to do successful config. for copying header and line item text from Sales Order to Outbound Delivery but config. doesn't seems to be same for copying text from PO to OBD.
Is there any way to achieve the same? Can some expert show the way to achieve this.
Thanks in advance.
Warm regards,
Rahul Mishra

Hi Ravikumar thanks for u quick reply.
This is wht is currently coded.
concatenate values to get item text for read text function
   invar3+0(10) = invar1. "PO number
   invar3+10(5) = invar2. "PO line number
   SELECT SINGLE * FROM stxh WHERE tdobject = 'EKPO'
                               AND tdname   = invar3
                               AND tdid     = 'F01'
                               AND tdspras = sy-langu.
   IF sy-subrc = 0.
     invar4 = invar3.
reading the text for the document items.
     CALL FUNCTION 'READ_TEXT'
       EXPORTING
         id       = 'F01'
         language = sy-langu
         name     = invar4
         object   = 'EKPO'
       TABLES
         lines    = it_itab.
I have seen some PO's which have info rec texts in that, which gets pulled by the above code...first thing is its id is F02 which exist in STXH table also there is other text with F01 id, and hence the table it_itab gets both these text hence no pbm.
but i came across a PO which has only one text which is info rec text with id F05 and is not store in stxh and hence doesnot get pulled by read_text fm. How do i change my cod to get this text which should not hamper other PO's as well.
As mentioned in above msgs, this F05 could be retrieved by providing object name as EINE.
anyhelp will be appreciated and rewarded.
thanks

Out bound delivery against STO

Hi
My client requirement is to trace every movement against STO i-e system should track each GR against each GI against STO.
Meaning when we issue a goods against STO system should track against which GI user post GR as in the system there is no standard available to track this activity.
We will see a possibility that the we have posted a outbound delivery against STO and the GOODS ISSUE and similarly do the inbound delivery and then GR against STO this is the only way to track the Goods Receipts against Good Issue.
It is only suggestions kindly correct me if I am wrong and one more help how the system create out bound delivery against STO.
Regards,
Tahir

HI,
Whatever you mention is correct

BAPI for Create out bound delivery

Hi ABAP Gurus ,
we are using following business process.
Create Stock transport Order (Purchasing Document) - > Create Out Bound Delivery.
Now for creating OBD from the Stock Transport Order , we have written a BDC for TCODE VL10I. It runs correctly in dialog work process. But fails in Background Job. Has anybody worked on this ? Any BAPIs , or alternative transactions available for this ?
Please help.
Thanx in advance ........
Regards,
Laxman Nayak.

Thanx Mr Raja,
VL10BATCH doesn't suit our needs . However in the process of trying VL10BATCH , I got one more TCODE VL10X. But this TCODE is again having the same problem as that of VL10i. ie it fails in background job.
Can u pls extend some more help to me Mr Raja?
Thanx in advance .
Regards,
Laxman Nayak.

AFS materials out bound delivery

Hi
could any body let me know how to carry out Out out bound delivery for AFS materials.it is for my inter co stock transfers.
Standard material it is happenung but not for AFS. i cant find AFS grids in AFS data or Picking tab.
what are the settings to be done for this.
waiting for your guidance
Simha

hi,
go to vl01n give the shipping point ,sales orderno then enter.
once we go into the transaction, check the delivered quantity is there.Then select the afs data tab(first one)once we selected
go to afs picking tab and give your picking quantity.
i think it will solve your issues.
regards
muthuraman.d
Edited by: muthuraman d on Dec 14, 2009 4:36 PM

What is meant by in bound and out bound delivery

hai sap sd gurus,
please tell me, wht is meant by in bound and out bound delivery?

>
peruru sreenivas wrote:
> hai sap sd gurus,
> please tell me, wht is meant by in bound and out bound delivery?
Hi Sreeni,
See any delivery that is inbound i.e. bound to come in like Returns from Customer or Delivery from a Vendor to us or any other delivery which is coming to us.....
Similarly any delivery that is outbound i.e. bound to go out like the deliveries we do to customers are Outbound deliveries
Reward if helpful
Regards
Abhishek

Out bound delivery

hi sap gurus
i need your help please help me
i have created stock transport out bound delivery in vl10b
i want see that order where can see that
thanks and regards
srinivas k.

Hi,
You can check the Purchase order history tab in ME23N for that STO.
You will see 2 documents.
1) PGI Document --643 mvt & 49 series
2) Delivery note no--Outbound delivery
rgds
Chidanand

Out bound delivery for STO

Hi
In stock transfer order in delivery tab part Del/Item tab it is mentioned "B" means it will create only one outbound delivery for sto. if stock is not available it will create deliver y with quantity 0.
But for 1 sto it has created 3 out bound deliveries.
Why it is happened?
Thanks,
Kiran

Hi
To check the possible reasons of splitting, see these notes:
SAP Note 166397 - Delivery split according to customer field ZUKRL
SAP Note 546668 - FAQ: Delivery split when creating deliveries
I hope this helps you
Regards
Eduardo

Print Preview of Out bound delivery is not available in VL71

Hi Experts,
             I have created Outbound delivery with VL10B (against Purchase Order) and also set up output parameter in VL02N (Extra->elivery output -> Header)
             Now I want to take Print out of this Outbound delivey in VL71 , I cant even see the Print preview. I have already maintained Output type , Access sequence and condition table in SPRO . I have also maintained condition record also (with delivery type and Shipping point).
              Any help on this

Check if output triggered successfully in delivery.
If yes, then please use indicator "Processing Mode" appropiately on the main selection screen of VL71.
If not, please see the error and try to resolve it.
Also check from main screen of VL02n where you enter delivery no, don't go inside the delivery screen, from main screen itself,
Outbound delivery> Issue Delivery output
Hope it helps
Regards
Anand Misra

I doc for transfer oder creration for out bound delivery

Hi
I am using idoc basic type WMTOID01 and message type WMTORD. when i am trying to create TO for delivery. the idoc is creating and TO ia also creating but, this is not linking to delivery. I am using mov type 601 and requirement type PICK and doc type L sales document. destination storage type 916 but when u see the TO i am not getting the delivery number is not appearing in TO and if you see the document flow in delivery the TO which is created is not appearing in document flow. please help to get the solution.

Hi,
The TO is basically created with refernce to warehouse number, plant and the delivery no.When you are creating the IDOC please ensure that the delivery number, warehouse number and the plant is entered in the IDOC.
Because in your case system is creating the TO but not with reference to the delivery which you have earlier created
Regards
Mano

FM for Deleting out bound delivery

Hai All,
Can Any one say FM for deleting outbound delivery with example.
Thanks,
Regards,
Ekadevi.S

Hi
Use the below mentioned Exit :
EXIT_SAPLCOMK_010
This basically validates for the changes in order component overview.
Use your condition after the EXIT to delete the components.

Simulation of out bound delivery docs in r3

Hi all,
I ran /SAPSLL/DS_I_SD0B_R3 this morning and when I ran in simulation - all docs shows status of released / checked. However, I then ran w/o the simulation box checked and when I reran the report again in simulation, all the docs still appear. Thought they should all be removed from the report? Why is this happening
regards

Hi,
The report checks in table /SAPSLL/OBJIDX for SD0B orders, re-transfers them and set an 'X' in the table /SAPSLL/OBJIDX when the documents have been successfully re-transferred. You should execute report /SAPSLL/OBJIDX_REORG_R3 - that's for the recovery index. This will remove all orders in the table marked with an 'X'. Afterwards you should retry your simulation.
Regards,
Oliver
Edited by: Oliver Rheinen on Apr 18, 2008 4:52 PM

Inbound and out bound

hi all
can anybody give ,when we do inbound and outbound delivery
regards
bhavani

Hi
Inbound delivery
The significant advantage of depicting the goods receipt process through the inbound delivery function is that the company can execute many processes in advance, even before the actual goods receipt posting takes place. In this case, all the necessary information is available beforehand as notification of the inbound delivery will be released ahead of time by the supplier.
The inbound delivery describes exactly which materials or pallets can be received on what date and at what time.
The following functions are available with the goods receipt process for inbound deliveries:
Material availabiltiy status for MRP run
Batch information
The batch split that is already possible for outbound deliveries is also available for inbound deliveries, since batches are often first identified in the inbound delivery.
Inventory management of packaging materials
Goods receipt for inbound deliveries
Determination of goods receiving point
Outbound delivery:
Outbound delivery is similar to Inbound delivery.Before Goods issue to Customer against Sales order, Out bound delivery ill be created contains all the information like shipping-planning information , Quantity etc.Based on this document, picking and packing will be done.after all the required processes completed, then Post goods issue will be done.
Outbound delivery supports all shipping activities including picking, packing, transportation and goods issue. During the outbound delivery process, shipping-planning information is recorded, status of shipping activities is monitored and data accumulated during shipping processing is documented. When the outbound delivery is created, the shipping activities, such as picking or delivery scheduling, are initiated, and data that is generated during shipping processing is included in the delivery.
Process:
Inbound Delivery:
PO -> Inbound delivery -> GR
Outbound delivery
Sales order-> Outbound delivery - > goods issue
Regards
Ramakrishna

Out bound IDOC creation

Hi experts,
I am given a task to create an out bound IDOC which would be input to TIBCO, which must be triggered every time Good issue transaction is completed by either VT02N or VL02N transaction up pressing SAVE.
IDOC is to have fields from Customize tables apart from standard SAP tables, so was asked to create an own IDOC ( eg: Z--Idoc).
Please tell me how to create the idoc, and also the method to trigger it and how to populate the IDOC ( program etc).
Use full inputs would be promtly rewarded.
Regards,
Ram.

Hi
Creation of Custom IDOc type and message Type
First Create Partner Profile(WE20 Tcode) and Port Definition in WE19 Tcodes.
take the Basis help to create them.
1.First create segments in WE31 Tcode with the required dataelements
2.Create the Basic Idoc Type in WE30
release the Segments and IDOC type.
3.Create Message type in We81
4.Assign the message type to IDOC type in WE82 T code
5.Create the process code in We41 (for Outbound) WE42 (for Inbound)
6.Create A fun module in SE37 starting with ZIDOC_OUTPUT_.. by copying some Inbound (for Inbound) Outbound Fun module
7.Create Workflow setting if needed ..
8. Assign the fun module to Idoc Type, Message Type and WF object (if it is there0
9.Define setting for fun module in BD51
10.In BD51 Define the settings for Fun module..
10.Assign the Processs Code to Fun mod`ule
Outbound Interface
PROCESS DIAGRAM for Outbound Interface
1. Analyse Hierarchy Levels
2. Create New segment
3. Create New IDoc Type
4. Create New Message Type
5. Link Message with IDoc Type
6. Create an entry in EDP13 via transactions WE20 and BD64
7. Populate the Custom IDoc via ABAP Program
7b Error Handling
7c. Send Status Email
8. Test the Population of the Custom IDoc
Step 1 Analyse Hierarchy Levels:
Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
Navigate to transaction code WEDI
Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
Step 2 Create a new segment:
via wedi : Development - IDOC Segments or Transaction code WE31.
Enter segment name and click on Create.
? The name of the segment type must start with Z1 , and have a maximum of eight characters.
Enter description and enter the relevant field names and data elements.
? The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.
Save the segment and enter Person Responsible and Processing Person .
Go to Edit and Set Release.
Repeat this procedure for each new Segment in the IDOC.
Step 3 Create a new IDOC Type
via wedi Development - IDOC Types or Transaction WE30.
Enter segment name (starting with Z), click on Basic Type and then Create.
Create as new, enter Person Responsible and Processing Person and enter description.
On Create Basic Type screen decide where segments should be inserted and go to Edit/Create Segment.
Complete relevant fields in the Maintain Attributes screen:
From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a Child.
When IDOC created return to initial screen. Go to Edit and Set Release.
Go to Transaction WE60 to view the IDoc Type you have created.
Step 4 Create new Message Type
via wedi Development - Message Types or Transaction WE81.
Display/Change and click on New Entries
Create a new Message Type and Save.
Step 5 Link Message Type to IDOC Type
via wedi Development - IDOC Type/Message or Transaction WE82.
Display/Change and then click on New Entries.
Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
Step 6 Create an entry in EDP13 via transactions WE20 and BD64.
The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
WE20 Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
BD64 Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to Environment on Menu and click on Generate Partner Profiles and generate (not save) profile.
Step 7 Populate the custom IDOC via ABAP Program
See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
- PERFORM populate_Control_structure USING c_mestyp
c_SEGMENT_type1.
The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
- PERFORM transfer_Parent_data_to_seg.
The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
- PERFORM master_idoc_distribute.
NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
The ALE Layer handles the sending of the IDOC to the receiving system.
Error Handling (see Step 7b).
Commit work.
Project Specific
Step 7b Error Handling Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
Declare a structure of type MCMAILOBJ for sending instructions.
Enter values for the internal table based on structure MCMAILOBJ
For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module MC_SEND_MAIL.
Enter values in the following parameters: -
MS_MAIL_SENDMODE = B (Batch Mode)
MS_MAIL_TITLE = 'Mail Title'
MS_MAIL_DESCRIPTION = Error description (e.g. MATNR not given)
MS_MAIL_RECEIVER = Name of Receiver (To be determined)
MS_MAIL_EXPRESS = E (Express Delivery)
MS_MAIL_DLINAME = Leave Blank
MS_MAIL_LANGU = 'E' (Language)
MS_MAIL_FUNKOBJ_NAME = Leave Blank
TABLES
MS_MAIL_CONT = I_MCMAILOBJ
Note:
It has to be determined separately for each interface how these errors and mail notifications are to be grouped dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
Step 7c Send status mail
Append to table I_MCMAILOBJ details of the time the interface was processed, how many Idocs were created and how many of these produced a status of 03.
Select the user to receive the mail from ZINT_RECEIVER, using the name of the program as a key (SY-CPROG).
Use function Module MC_SEND_MAIL to send a mail to the user containing the contents of I_MCMAILOBJ at the end of the interface processing.
Step 8 Test the population of the custom IDOC
via wedi IDoc - Display IDoc or Transaction WE02.
Enter your message type and execute.
Status should be green, double click on one of the Idocs you have created to view its contents.
If a problem has occurred click on Status which will give you a description of the error.
Drop down Data Records arrow and this should list the data in the IDoc in the correct hierarchical structure.
Click on each individual segment and view the content to check that the correct data has been read.
If you have UNIX access by using AL11 you can view the file that you have created.
Note:
For some interfaces it may be valid to send an empty file to SAP. This empty file is converted to the custom IDOC format expected by SAP. This custom IDOC will contain dummy information. In the inbound processing code, if the dummy information is identified then the processing of the IDOC is considered to be complete and the IDOC should then be assigned a successfully processed status of 53, even though it has not been processed at all.
Regards
Anji

Transferorder based on out bound Delivery

Similar Messages

Maybe you are looking for