Link delivery to outbound Idoc

Dear Experts,
I am need to link a delivery to an outbound Idoc, I am using function module BINARY_RELATION_CREATE to create the link and I can see the link has been created in the delivery but it showing as Incoming Idoc instead of Outgoing.
I am using relationship type IDC1 in the FM and have tried using others and have failed miserably, could anybody help me??
code
 wa_rolea-objkey = doc_number.
 wa_rolea-objtype = 'IDOC'.
 wa_rolea-logsys = wa_logsys. <-- From FM D_OBJECT_TYPE_DETERMINE using document type (VBTYP)
 wa_roleb-objkey = delivery_number.
 wa_roleb-objtype = wa_objtype. <-- From FM OWN_LOGICAL_SYSTEM_GET
 wa_roleb-logsys = wa_logsys. <-- From FM D_OBJECT_TYPE_DETERMINE using document type (VBTYP)
 call function 'BINARY_RELATION_CREATE'
 exporting
 obj_rolea = wa_rolea
 obj_roleb = wa_roleb
 relationtype = 'IDC1'

Hi,
try to use value "LIKP" for variable wa_roleb-objtype.
BUS2015 = Inbound delivery
LIKP = Outobound delivery
Regards

Similar Messages

Error in the content of Delivery output ASN outbound IDOC

Hi,
I created an Delivery order for an SO and processed to PGI.
Then the ASN Outbound idoc is triggered successfully!
But when i checked the content of this ASN Outbound IDOC, i found some data were not populated into the IDOC from the Delivery order...
So i should debug which program to determine the problem???
I dont know which one is the right one for me to debug the problem:
1) debug the output FM for this IDOC
We19(entering the error IDOC)-->Test outbound
2)VL02N>Delivery output>Enter the output type>Then swiching on the debugging mode>Enter to debug???
For above 2, which one is the one who retrive the DO content into the output IDOC???
Thanks very much!!!!!
Message was edited by:
Hoo Laa
Message was edited by:
Hoo Laa

Hi,
If i am right, there should be an output type that is trigerring this IDOC from the delivery ---right.
Can you please check the delivery and let me know....
At Extras - Delivery output - Header level...
Regards,
Syed Nasir

Duplicate outbound Idoc created for outbound delivery

Hi Gurus,
We use decentralised whse system for goods movement.
For couple of outbound deliveries there are double idocs created (messge type SHP_OBDLV_SAVE_REPLICA).
I have no idea how the duplication taken plcae. Any body come accross this kind of issue .
Please help to reslove the issue .
Thanks in advance

Hi,
There is nothing in message control tab for outbound parameter(we20) and even there are multiple changes in delivery.
What we do is as soon as the delivery is created . Z trnx is executed which changes the dec whse status A(Relevent ) to B (distribution) simulteneously outbound Idoc is created and delivery details send to whse.
Normally there will be one outbound idoc per delivery , but in this case there are 2 (duplicate)

Generating outbound idoc - During Oubound delivery deletion using VL02(N).

Hi All,
There is a requirement for me to send an outbound idoc from SAP System, when a outbound delivery is deleted in SAP system using transaction VL02N. The functionality is to achieve the same using message control/output control.
When an item of the delivery is deleted then the idoc is getting generated correctly.
But when the outbound delivery itself is being deleted no idoc is getting generated in fact the output determination itself is not taking place.
Could anyone please give me some inputs on this.

Hi,
Could anyone please reply to my query. Points will be definitely awarded. Thanks in advance.
Goutham.

Stop generating delivery IDOC output (outbound IDOC) if goods issued!

How to stop generating delivery IDOC output (outbound IDOC) if the delivery has been goods issued?! Any user exit or BADI for this?!
Thanks

We take a routine in output requirement! it's done!

Nace config for DESADV type Outbound IDOC of type 856 at Delivery level

Hi All,
My requirment is to trigger Outbound IDOC of type 856 at delivery level & not at shippment level & one line per ASN.
How can I configure this in NACE?
Thanks in Advance.

Hi Raj,
For example, you can use the ASN0 output condition as a SAP standard. please go to NACE t-code and select the V2 for shipping and
go into the ASN0 output type configuration. in the that sceen;
1)give access sequence regarding of your requirment, for general data.
2)in the default values tab, Dispatch time can be 4= send immediately (when saving the application), transmission medium should be A Distribution (ALE) and partne function SH.
3 go in to the processing routines for the output type and Programcan be configured as RSNASTED, Form Routine as ALE_PROCESSING. But these are SAP Standard and they are changing your requirements with the ABAP tricks.
After the output type configuration, go in to the output condition from nace t-code same. And create condition for ASN0 output type. when creating your conditions regarding of your acces sequence, you should Dispatch time can be 4= send immediately (when saving the application), transmission medium should be A Distribution (ALE) and partne function SH like output type configuration,too.
I hope these will very useful to meet your requirements. But additionally, you should also contact with a ABAPER for the program and routines.
Regards,

Outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON

Hi Friends
I am trying to pack outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON.
But IDOC has error Specification of destination HU missing.
Could you please help us to resolve the issue to Pack the outbound delivery with the IDOC.
Thanks
SR

HI Ian Kehoe
Sorry for delay in reply
Thanks you very much
I solved that problem .
Could you please advice test data for IDOC DELVRY06 packing hierarchy (multi level packing) to pack SAP outbound delivery.
Thanks
Ravi

How to create Inbound Delivery using SHPMNT03 Idoc details...

Hi,
I need to create Inbound delivery using idoc SHPMNT03 details. I am getting all the data required to create Inbound delivery is from this idoc. for that I need to create a custom function module.
I tried with FM IDOC_INPUT_DESADV1. But it is for only if you use DELVRY03.
I haven't (yet) found a way to create automatically an inbound delivery when you post the goods issue from the outbound delivery.
Does anyone experienced the use of inbound deliveries with STO and what are your recommendation?
Thanks a lot,
Ranjith.

Hi there,
Please have a look at the following link.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/dc/6b828943d711d1893e0000e8323c4f/frameset.htm
Hope this helps,
Kind Regards,
Matthew

VL01N - needs to trigger outbound idoc

Hi all,
As per requirement please tell me information of how to trigger the outbound idoc on save that consist of delivery data with ref to sales order data.
I am not able to create the Output type please tell me steps if possible of provide me some link that helps me.
Regards,

Hello,
You have to create an OUTPUT in the configuration and maintain the condition records in VV21 for the Partner LS which means an output for IDOC
For this configration, Goto the spro
SPRO->LOGISTIC-EXECTION>SHIPPING->OUTPUT DETERMINATION->MAINTAIN OUTPUT DETERMINATION FOR OUTBOUND DELIVERIES---.DEFINE OUTPUT TYPES.
Try to create the output type and maintain the condition records .
Revert back if you need any clarifications
regards,
santosh

About Orders05 outbound Idoc.

Hi,
I am using an outbound idoc of basic type Orders05 with an extension of the idoc header segment.This outbound idoc will get triggered once a PO is saved and sent through EDI.
I have to do an enhancement wherein I have to populate the mode of transport field(EXPVZ) and place of loading(LADEL) in the fields of the extended segment selecting them from EIKP depending upon the BELNR value in the header of the idoc(E1EDK01-BELNR).
I am unable to understand how do I populate the fields.
Could you please help me.
Thanks,
Sandeep.

HI,
see the below steps you will completely understand the processing outbound..
2.1 Outbound Interface
PROCESS DIAGRAM
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.
rewards if useful
regards,
nazeer

Regarding outbound idoc into xml conversion

Hello everyone
can anyone let me kno all the procedure to make our idoc outbound and convert it into XML file, is there any standard program or any other method if i am using we21 then what thing i have to do. is it neccesary for us to go to tc we60 and change schema of our structure or not, i don't want to use XI, please tell me whole procedure if possible, waiting for your reply.
plz reply me.
Thanks & Regards
vimarsh b
Edited by: vimarsh b on Jan 8, 2008 5:58 AM

hai,
check this.
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.
also gothroughthe links,
http://www.theobald-software.com/download/ERPConnect/ERPConnectDevGuide_EN.pdf.
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
With regards,
Sowjanya.B.

Outbound IDOC to be reprocessed

Hi SD experts,
We are sending an o/b 940idoc from delivery to OEM we had sent the idoc thru a wrong port so we want to reprocess the idoc through we19 with the correct port.
When we are reprocessing a inbound idoc we execute using the funtion module, but in case of oubound i suppose it is been run through a program.
How should i identify the program so that i can execute the outgoing idoc.
Regards
Senthil

L.Senthil Kumar wrote:>
> Hi SD experts,
>
> We are sending an o/b 940idoc from delivery to OEM we had sent the idoc thru a wrong port so we want to reprocess the idoc through we19 with the correct port.
>
> When we are reprocessing a inbound idoc we execute using the funtion module, but in case of oubound i suppose it is been run through a program.
>
> How should i identify the program so that i can execute the outgoing idoc.
>
> Regards
> Senthil
Hi Senthil,
Outbound IDocs either get triggerred by Output Types (Output types are linked to Function Modules who create and forward them)
Otherwise you manually trigger them.
In case it is an output type go to delivery
Goto Extras->Delivery Output->Header.
Just check if it has any output types assigned.
Then do as following
1) A single output type assigned.
Just go to delivery and on top right goto
OutBound Delivery->Issue Delivery Output to
If it is giving errors you need to check the configuration for output type assigemnet.
2) Multiple Output types assigned
In this case you need to find out which output needs to be issued as required by your business and issue it as in previous step.
3) No output type assigned.
In this case you must be having a customized program to trigger the Idoc and it will be specific to you so you will hav to enquire what is that program and run it.
Hope it helps
Abhishek

Mapping Inbound-Outbound IDocs

Hy everybody,
Is there a table in the receiving system where inbound IDocs numbers are linked to outbound IDocs numbers from the sending system ?
Regards,
Christian Baldari

Hi,
there is no link from inbound idoc to outbound idoc.
We will only come to know by looking document flow.
Sales order - Docuemnt flow
Delivery - Docuemtn flow.
You will come to know all the things by looking docuemnt flow.
ramesh

Is it possible to generate outbound idocs for FI invoices? How?

Is it possible to generate Outbound idocs for FI invoices? How? or else i have to write program to get data in file and pass it to translator. Please help.

Dear Gabriel
Before letting you know the possibility, can you please let me know why you want such a requirement, since standard has not provided such copy control, to my knowledge.
As you would know order type KB is for consignment fillup where you are just transferring the goods from FG unrestricted to your own warehouse and that is why in standard you can see the copy control KB --> F8 which means you can raise proforma against delivery and not against fillup order.
So think of whether really you wanted to raise proforma against fillup order which is NOT recommended by SAP. However, still if you feel that the requirement is so to have, you can make the settings in VTFA.
thanks
G. Lakshmipathi

Error while creating an outbound idoc using idoc type delvry02

hi,
i getting the following error while creating an outbound idoc(outbound shipping notification) using message type " DESADV" and IDOC TYPE " DELVRY02"
ERROR:
" SPECIFY EITHER ADDRESS NO OR ADDRESS HANDLE"
MESSAGE NO: AM053
Help would be appreciated.
regards
leo

The message is kind of self-explanatory. It seems that some address (delivery address ?) is required but is missing from the IDoc. If it's a syntax error, then the segment with error will appear in red in WE05 transaction.
It is also possible that you have filled some field that you should have left blank and now SAP is trying to find an address based on that field.
Check your IDoc contents. It's really hard to tell from the distance since the requirements and configuration could be very different in different systems. Sometimes the OSS note search by message ID and number is also helpful.

Link delivery to outbound Idoc

Similar Messages

Maybe you are looking for