Outbound Idoc bundling Approach

Hi All,
I have a scenario, where in SAP will send the Idoc bundle to PI( will bundle on an interval of 30 minutes), have gone through below blog on SDN.
IDoc Package processing using sender IDoc adapter in PI EhP1
so I will use the Idoc sender adapter in PI to receive the Idocs.
The Idoc which I am using is a standard Idoc, DELVRY05. One of my team mate has told me that, if you do Idoc bundling for a Idoc type in SAP system.then that Idoc bundling will be applicable to all the interfaces in my PI development box which will be using the same Idoc type.
Is this correct? Will it effect the other interfaces,or is there any disadvantages of this.
Please provide your inputs.
Thanks,
Ruchi

Hi,
that could affect other interfaces only if your other interfaces use the same Idoc ( complete same name): Message Type + Idoc Type + Idoc Extension, e.g DESADV.DELVRY05.
Have a look on tx WE20, the collect option is for this triplet. (picture in SDN blog does not see the Message Type, but it well on this triplet)
So if you have other DELVRY05 interfaces, and if you use at least a different Message Type (like ZDESADV.DELVRY05), they will not be affected by this collect in ECC (written for DESADV.DELVRY05) . Same thing with the idoc packaging made in PI, as the sender CC is used for a specific sender agreement (sender + complte Idoc name).
regards.
Mickael

Similar Messages

In Idoc bundling ...message mapping not found

Hi XI Friends..
In my File to Idoc scenario..i want to send multiple IDOCs from the XI without a BPM .
I am following blog by Michal.
<a href="///people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change:///people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
I have xsd for source ..so i created one external definition .and message interface for outbound.
following the above blog by michal..
i imported idoc ..and i exported that idoc into xsd and i changed the occurance of idoc to unbounded and again imported as external definition.
i created the message mapping between these two external definitions.and tested ..
As in michal 's blog..
In Interface mapping..i given source and target interface as standard idoc.and clicked on Read interface then i am not finding the message mapping created in previous step..
i refreshed cache also..
please guide me.....
regards
ram

Hi bavesh...
thank you so much for very your quick responses..
i got xsd as source..based on xsd i created external definition for source xsd and i created outbound interface based on source external deifinition MI_OUT_WearUnits.
and i imported Idoc and exported as xsd and changed occurance to unbounded and again imported as external definition.
i did mapping between these two external definitions.
and i selected standard idoc for source and target interface for interface mapping and given message mapping of previous step.
In ID
sender agreement :
 sender service :BS_external
 sender interface :MI_OUT_WearUnits
receiver agreement:
 receiver service :R/3
 receiver interface : standard Idoc
Interface determination:
sender service :BS_external
sender interface :MI_OUT_WearUnits
reciever service :R/3
and clicked create
inbound interface : Standard IDOc
i am not getting Interface mapping which i created in IR.
i tried Enhance interface determination also..
please guide me....
waiting for your help.
regards
ram

Multimapping to IDOC 1:n via IDOC bundling: Problem

Hi,
Trying the above procedure to send several IDOCS as one bundle to R/3. I followed note 814393 and also checked with weblog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2762. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]
The tests in message mapping run ok, I get exactly the screens as are mentioned in the weblog. yet when I send the actual interface, the message stays on recorded for outbound processing for 4 minutes in SXMB_MONI, then cancels with the following error:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">GENERIC</SAP:Code>
<SAP:P1>com/sap/xi/tf/_IF021_Ordrsp_TD_to_Ordrsp_CCS_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>Failed to load resource from the context classloa~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
The trace says:
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_IF021_Ordrsp_TD_to_Ordrsp_CCS_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.ConnectException: Connection timed out at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:37) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:63) etc
The scenario is client proxy to XI - BPM with sync HTTP - resulting XML mapped to multiple occurence IDOC and then to the IDOC adapter.
Everything works except the last mapping from BPM to outbound IDOC although that works in test as well.
Any ideas?
Thanks
Tom

Hi Tom,
1. Please can you check if your HTTP synch is working fine.
2. Please can you goto SXMB_MONI and take the Payload and see if your mapping is fine.
Regards
Vijaya

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

If output type is missing in PO, can system create a Outbound IDOC for that

Hi
Scenario: sales order should get generated in anoter system once PO is saved in first system. But this is not happening for a new vendor. I checked & found that output type is missing in PO. Asked user to provide another PO for which SO was created. I checked that PO, here also output type is missing.
I am surprised that if output type is missing in PO, can system create a Outbound IDOC for that PO? If yes then I am not aware of this process.
Please help me in analyzing this problem.
Regards
Sapmm12

Hi Sridhar,
Thanks for your replay.
I checked for other vendor also. condition records does not exist in NACE for any of them. But user is claiming that sales aorder is getting created for those PO. Though I have asked them to provide the sales order number & possibly outbound IDOC number for at least one vendor.
I tried to search IDOC number with reference to PO number but system is taking too much time & ending with run ime error. Because I do not have details of partner, receiver not even message type. Neither I have any process document which can explain how this process works?
any other approach which may work here?
Regards
sapmm12

IDOC bundling & IDOC packing

Can you explain with examples for IDOC bundling & IDOC packing

Hi
IDoc bundling is like sending multiple IDoc ...
Ex Scenario: U have file containing Multiple Sales order and for every sales order u are generating an IDoc so in the mapping u change the occurance of IDoc. Consider that the occurance of IDoc is 1-1 and now by exporting the IDoc and making changes to the occurance as 1- unbounded in the XSD. Now by importing this xsd we can send multiple IDoc this is IDoc bundling.
IDOC Packaging on outbound side
IDoc Packing is someting Viceversa to IDoc Bundling.
Ex Scenario: Multiple IDoc each containing a Sales Order is sent to XI and we want a single file to be containg all the IDoc sales order details. So we collect all the IDoc sent by R/3 for a perticular time or condition and do a mapping to generate a single file.
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
> 3) IDoc Bundling,
/people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages
http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
Please provide points if helpful
SD

Good Movement Outbound Idoc

Hi ,
We have to transmit Goods movement idoc to our partner.Since i couldn't find any standard outgoing idoc for material document posting.
Therefore we are considering below two approaches to get it done
Solution 1
We will use the user exit / customer exit like MB_CF001 available at material document posting to call FMs which will populate edidc & edidd of idoc type WMMBID02 (WMMBXY message type). We will updated NAST with our hard coded output types like ZABC.As soon as the the output type gets processed the message will be transmitted to partner.(For this output type we are planning to configure despatch time as IMMEDIALTELY therefore i believe message will get transmitted as soon as material document is posted.)
But we can see few challenges in this
1) Which program and routines we have to attach with output types ?
2) In NAST along with output type we also have to update , material document number. How to get it before posting a document ?
Solution 2
We will use the user exit / customer exit like MB_CF001 available at material document posting.Using this exit we create a XML file with field and place into a disred directory. XI people will do the rest work for us.
Need you advice on the feasible solution of two and which is more cost / effort effective
regards
Shrey

Hello,
I've looked into WMMBID02 IDOC with Message type WMMBXY, and looked further into idoc documentation. It is used for inbound GR transactions. Below is what I intent to do. We issue a PO to vendor via edi, vendor ships goods to us, and using MIGO, goods receipt transaction is performed. What I intent to do is to create an outbound idoc when MIGO is performed, so that I can let the vendor know that we received the goods.
Thanks,
S

Outbound IDoc for Goods Movement

HI
We need to generate XML files for goods movement posted in SAP at Goods Receipt (MIGO) and Post Goods Issue (VL02N). Requirement is asynchronous update where the receiving system will poll the xml file at the end of the day.
I have not been able to find any standard outbound idoc for goods movement.Can someone advise how they tackled any similar requirement? Any other approach also appreciated.
Thanks
Sriram

Answer to the question, which would be useful to all.
MIGO
MB_CF001 - Customer Function Exit in the Case of Updating a Mat. Doc.
This exit is called on update task, populate segments (edidc & edidd) of WMMBID02 (WMMBXY message type) and use MASTER_IDOC_DISTRIBUTE. Also you need to maintain the ALE Distribution model in WE64 for this message type.
Inside the code you can restrict based on movement type. No need to issue COMMIT.
VL02N
You can use BAdi: LE_SHP_DELIVERY_PROC to perform this.
Create Implementation and use the method SAVE_AND_PUBLISH_DOCUMENT.
Hope this help to others as well.

How to do configuration to create outbound idoc using message control

The objective is to create outbound idoc based on some selection criteria using message control approach.The interface will be triggered when there is goods receipt via MIGO transaction.............Now based on the material document number from NAST table i am going to fetch data and do further processing inside the function module i am going to create.later idocs will be created via program RSNASTED.How we do the configuration to set up this whole operation?

Please go thru:
1) message control
2) http://help.sap.com/saphelp_di46c2/helpdata/EN/c8/19878343b111d1896f0000e8322d00/content.htm
Regards
Shital

Outbound IDOC process - Using standard or Custom Program

Hi all,
i'm having some doubts regarding IDOC's outbound processing.
I'm trying to understand 2 scenarios:
1- Trigger Standard Outbound IDOC without writting any Z program ou IDOC FM.
It's possible to trigger a outbound idoc for exemple, whenever a sales order is created. To do this is, i suposed i don't need to write any code at all, correct?
What i need to do is create a logical system (SALE), define Transmission protocol (WE20, in here i associate the partner, and the outbound message type? After this point is the idoc automatic triggered?
If not, what is the correct procedure?
2 Trigger Ountbound IDOC using Z program.
Whats is diferent from the point 1 to this situation?
Best regards,
Pedro

Kali,
1. You can search in SE37 using IDOC_OUTPUT* for finding out corresponding function modules. It is based on message types.
2. You can search user exit in above mentioned function module. So first get the correct populating FM & then you can search for Call Customer Function inside the code for user exit.
3.Again ans is same as in point 1.

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

Function Module to Generate Outbound IDOC for Sales Documents

Hello Experts,
Can someone please help me, I need to know which function module to use in order to generate the outbound IDOC for sales documents. Some of the fm's I have come across are the following:
IDOC_OUTPUT_ORDERS, but actually for Purchase Orders
IDOC_OUTPUT_ORDRSP, but did not generate any IDocs for my sample Sales Order.
Points will be given for any help provided.
Thanks in advance.

Hi Nagaraj,
I tried using the IDOC_OUTPUT_ORDERS but I keep getting an error that the Purchase Order <xxx> does not exist, even though the document I tried is a sales order. For everyone's reference here is the code:
form process_data.
DATA v_idoc TYPE edidc-docnum.
DATA i_edidd TYPE TABLE OF edidd.
DATA wa_idoc_ctrl TYPE edidc.
LOOP AT i_nast INTO wa_nast.
 CLEAR i_msgs[].
 CALL FUNCTION 'WFMC_PROTOCOL_GET'
 EXPORTING
 cps_nast = wa_nast
 tables
 messages = i_msgs
 EXCEPTIONS
 NOT_FOUND = 1
 OTHERS = 2.
 LOOP AT i_msgs INTO wa_msgs WHERE arbgb EQ 'E0'.
*--- Check first if there is an IDOC
 IF wa_msgs-msgv1 IS INITIAL.
 CONTINUE.
 ENDIF.
 v_idoc = wa_msgs-msgv1.
 CLEAR i_edidd[].
 CLEAR wa_idoc_ctrl.
 CALL FUNCTION 'IDOC_READ_COMPLETELY'
 EXPORTING
 document_number = v_idoc
 IMPORTING
 IDOC_CONTROL = wa_idoc_ctrl
* NUMBER_OF_DATA_RECORDS =
* NUMBER_OF_STATUS_RECORDS =
 TABLES
* INT_EDIDS =
 INT_EDIDD = i_edidd
 EXCEPTIONS
* DOCUMENT_NOT_EXIST = 1
* DOCUMENT_NUMBER_INVALID = 2
 OTHERS = 3.
 CALL FUNCTION 'IDOC_OUTPUT_ORDERS'
 EXPORTING
 object = wa_nast
 control_record_in = wa_idoc_ctrl
* IMPORTING
* OBJECT_TYPE =
* CONTROL_RECORD_OUT =
 tables
 int_edidd = i_edidd
* EXCEPTIONS
* ERROR_MESSAGE_RECEIVED = 1
* DATA_NOT_RELEVANT_FOR_SENDING = 2
* OTHERS = 3
 IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
 COMMIT WORK.
 ENDLOOP.
ENDLOOP.

Automated error email notification when outbound IDOC fails

Hi,
The requirement is that whenever the outbound IDOC of message type PAYEXT, basic type PEXR2002, fails, then email has to be trigerred to a group id.
I had suggested to write a report program that runs as a job. If the IDOC goes to error status then mail will be sent from this report. Client prefers it to be done through workflow.
There is a standard process code for outbound IDOC failure handling EDIO (we40). standard task 7989 has been assigned to this process code. I dont want to modify this standard task as I am not sure of impact.
Terminating event for this task is 'ERRORPROCESSCOMPLETD'.
I have developed the workflow that has trigerring event 'ERRORPROCESSCOMPLETD' and bound with the IDOC number. This will send mail to the group id with the IDOC details
Now issue is that, I am not sure if standard process EDIO will be trigerred automatically, or should we configure anywhere. Since this is standard outbound IDOC, I am not able to add the process code in partner profile.
Please give your inputs or any other alternate solution to send mail through workflow when outbound IDOC fails.
Thanks in advance.

Hi,
I guess in your outbound partner profile for PAYEXT. you need to add process code EDIO in message control TAb. WHich will cause to trigger the workflow which will send the notification.

Outbound IDOC WPDTAX not getting generated

Hi
I am not able to generate outbound IDOC WPDTAX through WPMA transaction.
We are using TAXUSJ as the tax procedure.
Tax Condition type UTXJ and JR1 has been maintained in the system.
On looking at the code against WPMA ,
POS_TAX_GET is called to calculate taxes.
It does not have a fetch against all the condtion tables for tax.
The above condition has been maintained in table A053.While the above program fetches data against only A003.
Can somebody help?
Regards,
Amit.

Hi Amit,
For TAXUSJ, the conditions maintained are time dependent conditions.
However , IDoc type WPDTAX01 does not support time dependent conditions.
Only time independent conditions will be transferred with the help of Idoc type WPDTAX01.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/3f/81e33bfa5d11d38d1f080009d10d9a/frameset.htm
Regards,
Lisa

Message type for Scheduling Agreement - Outbound IDoc

Hi All,
I have to create an Idoc for Scheduling Agreement through a Z program based on some conditions. I have bit confusion, whether i can use Idoc type for Orders(e.g ORDERS01..05) & Message type ORDERS / ORDCHG to generate Outbound Idoc.
Already there is process code for for ORDCHG mappig IDOC_OUTPUT_ORDCHG & ORDERS mappig IDOC_OUTPUT_ORDERS. Whether there will be any impact on this.
Appreciate your help.
Regards,
Anbalagan.

Hi Anji,
Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
But I have to send Outbound Idoc for a Schedule Agreement.
Whether the same Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
Please Advice.
Regards,
Anbalagan

Outbound Idoc bundling Approach

Similar Messages

Maybe you are looking for