ME28 triggering an IDOC

Hi Experts,
I have a required of sending ORDERS idoc on release of purchase order by ME28. There will be four different types of orders having different document type and vendors. Now we have configured four different ouput type for document type + storage location + vendor.
In this case we are maintaining four different vendor partner profiles in WE20.
But our requirement is to have only one partner profile that should be LS type. But while triggering the IDOC it should have some thing in header to identify which document type it belongs to. We were thinking to use message function in partner profiles.
Can somebody suggest what will be the best way of achiving it. Make sure there should not be any coding involved.
Thanks very much. If you need any input please let me know.
Thanks
Neha.

My suggestion is to have different output types in message control parameters of the outbound partner you configure

Similar Messages

Triggering inbound idoc for FI T.Code F-02

Hi,
Anybody has triggered idoc for posting key 40 & 50 for F-02 T.Code in ECC 6.0, plz share their experience & triggering inbound idocs.
rgds,
balu

closed

Reg : change pointer mechanism for triggering the IDOC for delivery note

Hi ,
I am working on a change pointer mechanism for triggering the IDOC for delivery note and will be using this message class DESADV.
So SAP has suggested for assigning the message class DESADV with the function module in MASTERIDOC_CREATE_SMD_DESADV in BD60 transaction code.
So I was looking to create this MASTERIDOC_CREATE_SMD_DESADV function module in SAP and SAP suggesting that we should create this MASTERIDOC_CREATE_SMD_DESADV function module as same as the function module MASTERIDOC_CREATE_SMD_MATMAS.
So do anyone knows that is there any tool has been provided by SAP for creating this function module MASTERIDOC_CREATE_SMD_DESADV in SAP system for triggering the change pointer mechanism for outbound Delivery.
Thanks !
Regards,
Kiran

Hi,
When you are change pointer the system itself will take care of sending the changed master data to your partner system and the user will not have any intervention. If you really wanted to have that then you need to use the change pointers to read the master data which is modified in a custom program and then display that on the screen. Once the user selects that master data records then trigger an IDOC for creating the idoc for that master data and also flag that master data record as processed in the SAP BDCPS standard table, so that the same record will not be picked. If you wanted to know how the change pointers piece of code is written go through the program RBDMIDOC and you can understand how the change pointers logic is written.
Thanks,
Mahesh.

Automatic triggering of idoc for Personal Actions T Code ( PA40 )

Hi Experts,
I wanted to do automatic triggering of idoc after performing Personal Actions by transaction PA40.
Needed some info .
Thanx in Advance,
Pradipta

Hi Pradipta,
You can use the change pointers for this. Just check for what fields you want to trigger an IDOC. But this can not be triggered immediately. You have to run RBDMIDOC frequently. It will take the input as messaeg type and generate the IDOCs.
Before that please check if the change pointers are activated for this message type or not.
shylesh

TRIGGERING THE IDOC

Hi
I have one Zxxx table.. that contain some master data details... now i want to send these details to external systems... i created one custom IDoc and Message type.. every thing...
but for triggering the idoc what we need to do.. for example.. for predefined data we have option like BD10, BD12, BD14... these executable programs.. or Chnage pointers(RBDMIDOC) we can trigger the idoc for predifined data..
but for user defind data tables.. what can we do for triggering the idocs..
thanks
BABU

Hi,
check the below sample code for triggering the idoc..The same thing u can do for ur requirement..slect all then data from ur custom table and finally call the FM
"MASTER_IDOC_DISTRIBUTE".
*& Report ZZ_Program_To_Create_Idoc
report zz_program_to_create_idoc .
tables: ekko,ekpo.
selection-screen skip 3.
selection-screen begin of block b1 with frame title titl.
selection-screen skip.
select-options s_ebeln for ekko-ebeln.
selection-screen skip.
selection-screen end of block b1.
data: header_segment_name like edidd-segnam value 'Z1EKKO',
item_segment_name like edidd-segnam value 'Z1EKPO',
idoc_name like edidc-idoctp value 'Z19838IDOC1'.
data: header_segment_data like z1ekko,
item_segment_data like z1ekpo.
data: control_record like edidc.
data: messagetyp like edmsg-msgtyp value 'ZZ9838MESG1'.
data: i_communication like edidc occurs 0 with header line,
i_data like edidd occurs 0 with header line.
data: begin of i_ekko occurs 0,
ebeln like ekko-ebeln,
aedat like ekko-aedat,
bukrs like ekko-bukrs,
bsart like ekko-bsart,
lifnr like ekko-lifnr,
end of i_ekko.
data: begin of i_ekpo occurs 0,
ebelp like ekpo-ebelp,
matnr like ekpo-matnr,
menge like ekpo-menge,
meins like ekpo-meins,
netpr like ekpo-netpr,
end of i_ekpo.
start-of-selection.
select ebeln aedat bukrs bsart lifnr from ekko
into table i_ekko where ebeln in s_ebeln.
select ebelp
matnr
menge
meins
netpr
from ekpo
into table i_ekpo
where ebeln in s_ebeln.
control_record-mestyp = messagetyp.
control_record-rcvprt = 'LS'.
control_record-idoctp = idoc_name.
control_record-rcvprn = '0MART800'.
loop at i_ekko.
header_segment_data-ebeln = i_ekko-ebeln.
header_segment_data-aedat = i_ekko-aedat.
header_segment_data-bukrs = i_ekko-bukrs.
header_segment_data-bsart = i_ekko-bsart.
header_segment_data-lifnr = i_ekko-lifnr.
i_data-segnam = header_segment_name.
i_data-sdata = header_segment_data.
append i_data.
select ebelp
matnr
menge
meins
netpr
from ekpo
into table i_ekpo
where ebeln = i_ekko-ebeln.
loop at i_ekpo.
item_segment_data-ebelp = i_ekpo-ebelp.
item_segment_data-matnr = i_ekpo-matnr.
item_segment_data-menge = i_ekpo-menge.
item_segment_data-meins = i_ekpo-meins.
item_segment_data-netpr = i_ekpo-netpr.
i_data-segnam = item_segment_name.
i_data-sdata = item_segment_data.
append i_data.
endloop.
clear i_ekpo.
refresh i_ekpo.
endloop.
call function 'MASTER_IDOC_DISTRIBUTE'
exporting
master_idoc_control = control_record
OBJ_TYPE = ''
CHNUM = ''
tables
communication_idoc_control = i_communication
master_idoc_data = i_data
exceptions
error_in_idoc_control = 1
error_writing_idoc_status = 2
error_in_idoc_data = 3
sending_logical_system_unknown = 4
others = 5
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
else.
loop at i_communication.
write: 'IDOC GENERATED', i_communication-docnum.
endloop.
commit work.
endif.
initialization.
titl = 'ENTER THE PURCHASE ORDER NUMBER'.
Reward if hlpful.
Regards,
Nagaraj

Triggering outbound idoc from the transaction VL01N

Hi,
I have requirement where in which i need to create outbound idoc of sales and delivery data as soon as VL01n transaction is saved,Pls let me know how we can achived this , the Idoc needs to be triggered immediatly after saving VL01n transaction.
Thanks
Ravi

>
Sujatha Reddy wrote:
> Hi Ravi,
>
> Goto t-code NACE, select Shipping and press push button 'Output Types', now you will get the output type for delivery and you can configure you own output meduim in this screen.
> select the meduim & assign the require parameters.
>
> and goto VL01N and create a delivery and now you can goto extrats-> delivery out put-> header, here you can assign the output type that has been confugured perviously.
>
> -hope this helps
You could of instead told them to search the forum like I did. Instead you chose to give him the answer, even though it is not the full answer. After they have done what you ask, what result would you expect form the output record on the delivery. I will tell you, it will not process, why, because you have not mentioned anything about partner profiles and the output control.
But I hope you get the points for you reponse and you sleep well.

Auto triggering of IDOC after PO creation

Hi,
Currently after creation of PO, the PO will get triggered automatically to other system in the form of IDOC.
For this we have assign the condition record for the PO vendor and used the standard SAP function module 'IDOC_OUTPUT_ORDERS' to create the IDOC.
But now we have a requirement like for some POs the IDOC should not get auto triggered to other system.
Do we have any user exit available to not to call the SAP standard FM used to create the IDOC??
or Is there any way we can stop auto triggering of POs
Thanks
Nishad Shimpi

Hi,
try using the Badi : ME_PROCESS_PO--method-POST. where you check the condition and trigger the IDOCs.
OR else restrict using the conditions records,
Regards,
Aditya

Triggering MATMAS IDoc

Hi Folks,
I have a requirement to send IDocs to the other system on create or change of material. On any create or change of material I want a MATMAS01 IDoc to be triggered and to be sent to the partner system.
1. I have chceked the Active checkbox for MATMAS in the tcode BD50.
2. I have saved the Change pointer in the tcode BD61
3. I have created the partner profile added the message types to it in the outbound parameter.
4. I have created the distribution channel.
But the problem is the IDoc is not triggering automatically once the material is created or changed in the source system.
Kindly let me know how to resolve this.
Regards,
Santosh

Hi,
Activating the change pointer for the mnessage type wont create the Idoc, you need to manually or schdueld prog to create the idoc against chage pointers.
Via change pointer, you have to run BD21 transaction or need to schedule RBDMIDOC to create an idoc.
If its a new material you need to run BD10 transaction.
Hope you clear, if not pls come back.

Triggering an idoc for Quotation

Dear experts,
I am beginner to ALE & idocs.I want to see how ALE works by triggering idoc for quotation viewed through VA23.
I want to transfer a single quotation between y Development logical clients.
Configuration is done in SALE.
Basic type is ACC_SALES_QUOTA01
Messagetype is ACC_SALES_QUOTA
E1BPACCRSO and E1BPACSQ00 are segment types.
I can also see the documentation of same in WE62
Function module in WE57 is BAPI_IDOC_INPUT1 and BAPI_IDOC_INPUTP ie two different for same basic and message type .
My first question is why so ?.Which will triggger .?
in WE41/WE42 how will i know for given functionmodule which process code is assigned?.
How can i know whether this basic type is an inbound idoc or outbound idoc or any idoc basic type can be used as outbound and inbound ?.I am little confused as i am new to ALE & idocs.
If i assume that any idoc can have any direction ie inbound as well as outbound then i should have process codes in WE41 as well as WE42 ,which is not true here.
Edited by: aditya sharma on Jul 14, 2010 8:15 AM

Hi,
you can refer below link for ALE-IDOC info.
http://help.sap.com/saphelp_46c/helpdata/en/d5/edf163dcdc11d1890c0000e8216438/frameset.htm
WE41 refers to outbound process codes and WE42 refers to inbound process codes.
for quotation use SD12 process code for outbound.

Triggering an idoc

hi all,
could someone explain me , different ways to trigger an idoc.
thanks in advance,
suma sailaja pvn

IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i.     One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii.     One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii.     One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
     Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
     IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
     Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
     Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
     Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
     Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
     Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
     Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch ALE Service).
     IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1.     Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2.     Processing in the ALE/EDI Interface Layer:
     Basic integrity check: A basic integrity check is performed on the control record.
     Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
     Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
     IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
     IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3.     Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function modules output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).
Reward Points if useful.

Triggering an idoc for FI tcodes

Hi all
How to tirgger an idoc for FI transactions for eg F-31.as in SD and MM can we use message control technique to trigger idocs ?
Regards
Uday

Hi
DIRDEB ( Message Type)
Preauthorized withdrawal
- FEDI0003 EXIT_SAPLIEDP_003 FI-EDI outgoing payments: Save PEXR segments (customer directory)
PAYEXT(Message Type)
Extended payment order
- FEDI0003 EXIT_SAPLIEDP_002 FI-EDI outgoing payments: Save PEXR segments (external payments)
- FEDI0004 EXIT_SAPLIEDP_901 FI-EDI outgoing payments: New partner house bank
- FEDI0004 EXIT_SAPLIEDP_902 FI-EDI outgoing payments: End of IDoc payment (VBLNR)
- FEDI0004 EXIT_SAPLIEDP_903 FI-EDI outgoing payments: End of partner house bank
Regards
Pavan

FI - Interface triggerring multiple idoc is not getting posted

Hi all,
I have a scenerio, where I am receving data from SAP PI, which calls standard idoc ACC_DOCUMENT03 and which posts FI Document.
now, the problem is interface trigger's 2idoc with seperate number with same message type and same idoc type, but both the idoc are not getting posted and show's error like 'No currency line exists for line item 0000000001' and so on.
But the same idoc, when i proccess indivisually get's process gets posted successfully.
I have also done implementation in function module IDOC_INPUT_ACC_DOCUMENT.
As an abaper, I am not able to understand problem to take corrective steps.
Thanks & Regards
shashikant

hi,
if the IDoc is stuck in a qRFC queue means that the message did not reach the pipeline to be send to R3 so, anything in wrong at PI side.
please, go to SMQ2 and check whats happening. to know the queue name check the SXMB_MONI, select the proper message and scroll rightto the proper colum.
let us know.
Rodrigo P-.

Problem in triggering MATMAS IDOC through BD10 transaction

Hi,
My scenario is to trigger an IDOC(MATMAS)in BD10 and store it as an XML file in the physical directory.
I have created a logical system for this and also created partner profile for the logical system defined.
Further i've have configured XML Port has my reciever port of the outbound message type(MATMAS). But when i trigger the IDOC, it says that "1 Master IDOC setup for the message type MATMAS" and "0 Communication IDOCs generated" and the outbound IDOC is not recieved at the concerned directory. Please help me out in solving this issue.

Hi,
While doing configuration u must take care of creation of Distribution model. Here you need to give message type,sender & receiver.
At the same time you need to generate partner profiles. Results should give 'SYNCH' along with all info.
Check all the inbound/outbound parameters are correct or not.
If you satisfy with this pls close this issue and allocate some points.
Regards
KER.

Message type :FIDCC2/ IDOCFIDCCP02 - Triggering outbound IDOC

I have to send the FI accounting document of certain customer groups to the third party system .
Can anyone pls let me know how to trigger the outbound IDOC for the message type FIDCC2 after the FI document is created.
I have configured BD64 but can not find which program to trigger to generate the outbound IDOC with the FI data.
Thanks,
Prashanth

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

Mail to be triggered when IDOC fails

Hello experts,
I have created a responsibility and added list of user to it. I have been to WE20 and assigned responsibility to one of the logical system and message type "ORDERS". Whenever an IDOC with message type "ORDERS" fail, respective persons of responsibility shall get mail.
Please let me know what all I need to do.
Thanks,
Krishna.

Hi,
You can achive this in the following way,
1. create a custom workflow to send mail
2. go to Transaction WE42 and select your process code
3. Open the process code by double clicking
4. Here you can find the funtion module ( Identification field ) to process the inbound IDOC.
5. select the button attached with Identification
6. You can find there are several box..
    Select the 'Idoc' Box
7. Here you can find the
   Object Type
   Start Event
   End event
   Success Event
    You can can maintain the requrired event here which will trigger if any idoc failed.
    e.g.
    Object Type                         IDOCHRMD
    Start Event                         INPUTERROROCCURRED
    End event                           INPUTFINISHED
8. link this start event with your custom wokflow.
9. When ever the idoc fails event INPUTERROROCCURRED will trigger and this will start the custom workflow.
Hoping that this will help you.
Thanks and regards,
SNJY

ME28 triggering an IDOC

Similar Messages

Maybe you are looking for