Need to trigger an idoc from transfer order on confirmation

Hi,
I need to trigger an outbound idoc on the confirmation of a Transfer Order, but I don't know how to do.
The IDoc type i'll use WMTOID02.
Any Help would be greatly appreciated.
Regards,
Supaporn R.

Hi
I think you need to do some configuration using OMKY transaction, pls take help from functional consultant
Regards
MD

Similar Messages

How to trigger an Idoc from Sales order creation and change

We are trying to trigger Idoc from sales order creation and change we have done following setting mentioned below:
Follow the below steps:
1. Go to NACE transaction
2. Select V1 application and select OUTPUT TYPES
3. Select the required output type and double click on Processing routines.
4. Enter Medium as DISTRIBUTION ALE, Program as RSNASTED and Routine as ALE_PROCESSING.
5. Save it.
message type ORDERSP in the distribution model (BD64).
Follow the below steps to configure the condition records:
1. Go to NACE
2. Select V1 application and select CONDITION RECORDS
3. Select the requred output type and click on Condition records
4. Selection screen will be displayed.
5. Go for execution. In that screen enter the selection criteria. For eg Condition record is based on Sales document type. Then
Sales doc type = OR
Funt = SP
Partner = blank. It means there is no restriction on partner numbers.
Medium = A
date/time = 4
Lan = EN.
Note: partner is left blank means, the sales order of type OR can be send to all partners.
6. Save it.
We also done ALE configuration.
We are facing problem that from VA02 "No output has been selected for printing Message no. V1102"
Kindly suggest the solution.
Regards,
Sharad Dixit

Hi ,
Please check the total error description and diagnosis as below :
InVa02 enter SO go to extras->output->Header->edit.You can find a table with all the triggered output types. Choose the output type BA00 with medium Distribution ALE and go for 'Processing log'. It will show you the error description.
Please paste the diagnosis .
Thanks and Regards,
P.Bharadwaj

Trigger IRODER Idoc from IW31 while creating service order

Hi,
Iam trying to trigger an IDoc for service Order from IW31 transaction. I found the Idoc IORDER is for service order and one way of doing it is from IORD transaction.(Please correct me IORDER is not the correct Idoc !!) However, we dont have status profiles maintained for our order type, so Iam not able to use this method. Could anyone tell me if there is any other way to trigger the same?
Thanks & Regards,
Swarna Munukoti

Hello Sandeep,
Sales Representative is a partner funtion. You need to enter this partner function with a BP in the parties involved assignment block.
As for the pop up, it is controlded bu the partner determination procedure. Based on the partner determniation procedure used, if there are more than one sales representative found, there would be the pop for selection.
Hope the above information helps.
Best regards,
Maggie

How can we trigger an IDOC based on Orders creation.

Hiii...experts,
After searching alot in SDN i am taking this very commonly asked to experts in the hope of a better understanding.
If i create a sales order means.. i want to trigger a IDOC based on certain Condition on ORDER data .. how can we do this..
when ever i'm creating a sales order it should be automatically trigger a IDOC , Because when ever sales ordre was created in R/3 system it should be transferred to some destination...
And pls tell me about the reports that does the job of collecting required data from the sales order and converts it into a IDOC.
so, how can we trigger an IDOC based on Orders creation..
pls help.
Ram.

Use IDOC_OUTPUT_ORDERS for creating IDOC
you need to maintain condition records & output type
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Apr 10, 2008 4:18 PM

How to Trigger an IDOC from SAP R/3 to two systems at a time

Hi experts,
Can any one please tell me How to Trigger an IDOC from SAP R/3 to two XI systems at a time.
My current production R/3 system sends a DELVRY03 IDOC to Production XI system ( Name : XIP) .
I would like to route the same IDOC from production R/3 system to my Quality XI System ( Name XIQ) .
Problem is production R/3 system triggers an IDOC once. We need to write a logic to route the same to two different systems
Can any one tell me how can we do that ?
Regards
Ram.

Hello Ram,
Do you have connectivity between your production & XIQ?
What does "connectivity" mean?
1. RFC destination is maintained.
2. Port defined for the RFC destination.
If no, create these. (Search in SDN for details).
If yes, proceed:
1. Define the logical system for XIQ.(BD54)
2. Define the same as your partner profile. (WE20). Add the message type SYNCH with the port for XIQ.(This is imp)
3. Create a distribution model view with sender as "your production" & receiver as XIQ.
3.1. Add the messages which you want to distribute.
3.2 Generate Partner profiles.
No coding is reqd. for this.
BR,
Suhas

IDOC for transfer order for delivery note LT03

Hi All,
I need to generate an outbound IDOC upon transfer order creation in Tcode LT03.
I found there are two types of IDOC discussed in this forum before. One is the Canceling Transfer Order IDOC and another one is the Confirmation Transfer Order IDOC.
I'm not sure whether these relevant to what I need or not.
Can i know what FM, message type and basic type should I use for this situation?
(generate an outbound IDOC upon transfer order creation in Tcode LT03)
Please advice.
Thanks.
Best Regards,
JL
Message was edited by:
KAR SENG LAW

I found something here,
Someone is using FM: L_IDOC_INPUT_WMTORD, message type WMTORD and basic type WMTOID01 in doing this when trying to send an Idoc to an external system when a transfer order for a delivery note is created (LT03). Is it OK ?
need advice.
Thanks again.

PGI Exit to update serial number from Transfer order

HI Experts,
I would need to update serial number in the outbound delivery while PGI from transfer order created for same delivery.
I found lot many BADI and form exit. But did not find any internal table in the exit where I can update serial number.
Please give your suggestions to solve this problem.
Thanks in advance for quick response.
Regards
Anutosh

I don't think that it is possible in standard.

How to Trigger an IDOC from SAP R/3 to two XI systems

Hi experts,
Can any one please tell me How to Trigger an IDOC from SAP R/3 to two XI systems at a time.
My current production R/3 system sends a DELCERY01 IDOC to Production XI system ( Name : XIP) .
I would like to route the same IDOC from production R/3 system to my Quality XI System ( Name XIQ) .
Problem is production R/3 system triggers an IDOC once.
Regards
Ram.

Hi Ravi,
Thank you very much for your answer.
As I am not completely aware of R/3 side,I am getting little problem in understanding your answer.
Could you please explain the same in some what beter way.. Thank you ..

I need help to create idoc from scrach.

i need help to create idoc from scrach.

Swamy Katta,
Please read "[the rules|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement]" before you post any further, and confirm that you have read them?
=> Search first, ask questions later please!
Julius

How to find the standard Idoc for Transfer Order (LT03)

hi
How to find the standard Idoc for Transfer Order (LT03)
How to create the Idoc on LT03
plz help me out
Thank u
Ram

Someone is using FM: L_IDOC_INPUT_WMTORD, message type WMTORD and basic type WMTOID01 in doing this when trying to send an Idoc to an external system when a transfer order for a delivery note is created (LT03). Is it OK
Please reward points

Can we delete or cancel a Transfer order after confirmation?

Hi,
We want to delete or Cancel a Transfer order after confirmation.
We reversed PGI, cancelled shipment and trying to delete a line in the delivery, but it says "item already confirmed by TO".
Any pointers?
Thanks
Edited by: Chandru on Jun 28, 2008 3:01 AM

Hello,
Cancellation of TO - LT15.
Cancellation of TO for Storage unit - LT16.
LT0G - Return delivery to stock
Prase

IDOCs creation - Transfer Orders(TOs) for Deliveries - Basic doubts, thanq

Hi Experts,
Am new to IDOCs. I hv a requirement, so, request u that, Can I get some Wht to do tips from u?
My doubts:
1- I hv been asked to create IDOC, Wht does it mean?
2 - How the created IDOC will be get posted?
My requirement is:
Original inbound idoc sent from Gentran will update the delivery with all serial numbers per material for all serialized product. The message code will be the indicator that a Transfer Order-TO, idoc must be created for TO confirmation.
I need to do===>   Should be executed only when the message code on the delivery idoc is u201CTOCu201D. Look up the warehouse code on the delivery header using the delivery nbr in the delivery idoc. Create a new TO confirm idoc per delivery idoc being processed. Create a line item on this idoc for every line on the delivery idoc. Each TO line includes the delivery number and delivery item number so the TO number and line number can be looked up in table LTAP by using the delivery number and line item number found on the delivery idoc. There will be at 2 transfer orders for each delivery item b/c of the 2 step pick process, so select the TO nbr that has 916 as the destination storage type (LTAP-NLTYP). There may be more than 1 pair of TOs per delivery item so this must be completed for each TO found relevant to each delivery item.
The inbound delvry03 idoc will update the delivery with the serial numbers as part of the standard functionality. Since the transfer order must also be confirmed with the quantities on the inbound idoc, an additional idoc must be created from within the delivery update process. The transfer order can be updated and confirmed using the standard idoc and function module which should be created and initiated from the delivery update function module customer exit.
Source = DELVRY03     Destination = WMTCID01
Record Name-Field Name-Record Name-Field Name-Description---Comments
E1EDL20     VBELN-E1LTCOH-LGNUM-Warehouse Number-Look w/ idoc delivery nbr
E1EDL20     VBELN-E1LTCOH-TANUM-Transfer Order Number- Look w/ idoc delivery nbr
E1EDL24     POSNR-E1LTCOI-TAPOS-Transfer Order Line Item- Look w/ idoc delivery line nbr
EVERY THING IS DATA TRIGGERED!!!
thanq
Edited by: Srinivas on Jun 27, 2008 4:41 PM

IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
NEED FOR ABAP PROGRAMMING arises if
1)New IDOC was created
Depending upon the triggering mechanism i.e change pointer,message control
etc the programming technique changes and the type of process.
2)Existing IDOC was extended
User Exits are used to populate data in new segments added and to read them
back.
3)To enhance an exsiting process.
User Exits are used .
Basic structure of an OUTBOUND PROGRAM
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP IDOC type
MESTYP Message Type
RCVPRN Recieving Partner (Destination)
RCVPRT Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
INT_EDIDD-SEGNAM = 'ZSEGMENT'
W_SEGDATA-field1 = value "taken from some table
W_SEGDATA-field2 = value "taken from some table
INT_EDIDD-SEGDATA = W_SEGDATA
APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
OUTBOUND PROCESS AND OUTBOUND PROGRAM.
Outbound programs are used in outbound process to genearte IDOCs . There
purpose is to extract the data from the tables and to fill the IDOC data records
and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
1)Message control
Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
In outbound programs(function module) that use message control the key of the
application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
The parameteers passed to the function module are
IMPORTING PARAMETERS
OBJECT LIKE NAST
It contains documents key.
CONTROL_RECORD_IN LIKE EDIDC
It contains the partailly filled control record
EXPORETING PARAMETER
OBJECT_TYPE
CONTROL_RECORD_OUT LIKE EDIDC
TABLES
INT_EDID LIKE EDIDD
The internal table used to fill the data records in the same order as they exists in the IDOC.
The important parameters that should be filled in the custom function module are
CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
2)Stand alone programs
Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
Data is filled in an internal table of TYPE EDIDD according to segment definitions
and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
3)Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
ALE/IDOC Transaction
SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE57 This is used to assign the Inbound function module to the Message Type
and to the IDOC Type.
WE42 This is used to define the process Code for Inbound Processing.
BD95 Define Filter object type .We can specify the field and the table it belongs
to as a filter object .
BD59 Assignment of Filter object type to the Message Type .Here we create the
link between Filter object and the segment and the message type and the
segment Field.
BD50 Set message Type to reducible.
BD65 Define Mandatory Fields.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
BD21 Creating IDOcs from change pointers.
This can be used to create IDOCs from change pointers for a particular
message LIKE MATMAS.
BD22 This can be used to delete change pointers.
BD87 Status Monitor. Idocs can be selected base on number of criteria and there
processing status can be seen in detail.
BD10 Material Master Data Distribution .
Based on Message MATMAS.
BD12 Customer Master Data Distribution .
Based on Message CREMAS.
BD14 Vendor Master Data Distribution
Based on Message DEBMAS .
BDFG Generate ALE Interface for BAPI.
Here we specify the Business Object and the BAPI Function module for
which the interface has to be created.
WE31 Segment Editor.
This is used to create segments. We create the segment type and
segment definition is automatically created by editor e.g. Z1DUMMY is
segment type and Z2DUMMY is the segment definition .We specify the
fields and the data elements these cp\orresponds to create segments.
WE30 IDOC Editor
It is used to create a new IDOC Type or IDOC Extension .We specify the
segments that will be addd to the IDOC type.
WE02/05 IDOC List.
Various selct options and parameters are provided to select IDOCs
depending on the date, direction , mesage type etc.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.

WM-production order-need change the open quantity in Transfer order

Hi,
   I created the production order (order quantity 1000). i did material staging and generated TR. .
   But i need to change the open quantity in transfer order . i need to create the partial Transfer order
    against TR..
   KINDLY SUGGEST ME
   WITH REGARDS
   Dinesh

Hi Dinesh,
TO for partial qty is possible.
When you are doing material staging with 319 mov.type, you create a transfer order for partial quantity as follows:
You first create a manual transfer order using transaction LT04.
You specify the TR number in the intial screen and navigate to the detail screen, system shows the Open TR quantity and the proposed TO quantity. By default, both these quantities are equal to the TR quantity.
However, when you create by clicing the "Create TO button" (the icon with a plus sign in the tool bar of LT04 screen), system takes you to another screen where it asks for the "Requested Qty" on the top of the screen. Here you can modify the qty as per your requirement; then you can check and confirm the storage type and storage bin for source and destination stocks & save.
It is important that you give the correct source storage type & storage bin that is having stock or otherwise system might give error message.
System will create a TO line item with the entered qty and propose the balance TR qty as the 2nd TO line item. You can skip this 2nd TO item or delete it from the TO.
Once again, if you click the Save button, system will save the TO with the partial quantity.
The balance quantity will be available in the TR as open quantity and this can be seen in the header data of transaction LB03.
Regards
Prabhu

Soniya here!! need help.... Creation of transfer Order. and confirmation.

Hi all ,
I am in need of a fuction module to create a transfer order ( LT03 ) where i am able to pass / specify the source storage unit / handling unit from which the materials can be taken for the TO.
I also need a function module where i can confirm this TO in LT12.
Thank you in advance.
Ponits for sure!!!

Hi,
Use FM : L_TO_CONFIRM to confirm the transfer order.
MOVE wa_to_tab4-tanum TO g_confirm_tab-tanum.
MOVE wa_to_tab4-tapos TO g_confirm_tab-tapos.
MOVE wa_to_tab4-altme TO g_confirm_tab-altme.
MOVE wa_to_tab4-nista TO g_confirm_tab-pickm.
IF NOT wa_to_tab4-vlenr IS INITIAL.
    MOVE wa_to_tab4-vlenr TO g_confirm_tab-lenum.
ELSE.
    MOVE g_vscfld TO g_confirm_tab-lenum.
ENDIF.
MOVE 'X' TO g_confirm_tab-parti.
IF NOT wa_to_tab4-nlpla_old IS INITIAL AND
     NOT wa_to_tab4-nltyp_old IS INITIAL.
    MOVE wa_to_tab4-nlpla TO g_confirm_tab-nlpla.
    g_confirm_tab-squit = 'X'.
ENDIF.
IF wa_to_tab4-nistm > wa_to_tab4-nista.
    l_diff = 'X'.
    g_confirm_tab-kzdif = wa_to_tab4-kzdif.
ENDIF.
PERFORM get_bint_param USING g_lgnum wa_to_tab4-vltyp
                         CHANGING l_returns.
CASE l_returns.
    WHEN '1' OR '3'.
      IF l_diff EQ 'X'.
        MOVE wa_to_tab4-nista TO g_confirm_tab-nista.
        g_confirm_tab-ndifa = wa_to_tab4-vsolm - wa_to_tab4-nista.
      ELSE.
        MOVE wa_to_tab4-nista TO g_confirm_tab-nista.
      ENDIF.
    WHEN '2'.
      IF l_diff EQ 'X'.
        g_confirm_tab-diffm = wa_to_tab4-verme - wa_to_tab4-nista.
        g_confirm_tab-restm = 0.
      ELSE.
        g_confirm_tab-restm = wa_to_tab4-verme - wa_to_tab4-nista.
        g_confirm_tab-diffm = 0.
      ENDIF.
      g_confirm_tab-pickm = wa_to_tab4-nista.
      CONCATENATE '00' wa_to_tab4-vlenr INTO g_confirm_tab-lenum.
ENDCASE.
APPEND g_confirm_tab.
CALL FUNCTION 'L_TO_CONFIRM'
EXPORTING
    i_lgnum                              = wa_to_tab4-lgnum
    i_tanum                              = wa_to_tab4-tanum
I_SQUIT                              = ' '
I_QUKNZ                              = ' '
I_SUBST                              = ' '
i_qname                              = sy-uname
i_ename                              = sy-uname
I_SOLEX                              = 0
I_PERNR                              = 0
I_STDAT                              = INIT_DATUM
I_STUZT                              = 0
I_ENDAT                              = INIT_DATUM
I_ENUZT                              = 0
I_ISTWM                              = 0
I_KOMIM                              = ' '
I_EINLM                              = ' '
I_TBELI                              = ' '
I_UPDATE_TASK                        = ' '
   i_commit_work                        = 'X'
I_AUSFB                              = ' '
TABLES
    t_ltap_conf                          = g_confirm_tab
T_LTAP_CONF_HU                       =
T_LTAP_CONF_HU_SERIAL                =
EXCEPTIONS
   to_confirmed                         = 1
   to_doesnt_exist                      = 2
   item_confirmed                       = 3
   item_subsystem                       = 4
   item_doesnt_exist                    = 5
   item_without_zero_stock_check        = 6
   item_with_zero_stock_check           = 7
   one_item_with_zero_stock_check       = 8
   item_su_bulk_storage                 = 9
   item_no_su_bulk_storage              = 10
   one_item_su_bulk_storage             = 11
   foreign_lock                         = 12
   squit_or_quantities                  = 13
   vquit_or_quantities                  = 14
   bquit_or_quantities                  = 15
   quantity_wrong                       = 16
   double_lines                         = 17
   kzdif_wrong                          = 18
   no_difference                        = 19
   no_negative_quantities               = 20
   wrong_zero_stock_check               = 21
   su_not_found                         = 22
   no_stock_on_su                       = 23
   su_wrong                             = 24
   too_many_su                          = 25
   nothing_to_do                        = 26
   no_unit_of_measure                   = 27
   xfeld_wrong                          = 28
   update_without_commit                = 29
   no_authority                         = 30
   lqnum_missing                        = 31
   charg_missing                        = 32
   no_sobkz                             = 33
   no_charg                             = 34
   nlpla_wrong                          = 35
   two_step_confirmation_required       = 36
   two_step_conf_not_allowed            = 37
   pick_confirmation_missing            = 38
   quknz_wrong                          = 39
   hu_data_wrong                        = 40
   no_hu_data_required                  = 41
   hu_data_missing                      = 42
   hu_not_found                         = 43
   picking_of_hu_not_possible           = 44
   not_enough_stock_in_hu               = 45
   serial_number_data_wrong             = 46
   serial_numbers_not_required          = 47
   no_differences_allowed               = 48
   serial_number_not_available          = 49
   serial_number_data_missing           = 50
   to_item_split_not_allowed            = 51
   OTHERS                               = 52
Regards
Kannaiah

How to trigger payment Idoc from F110

Hi All,
I am working with a senario where in I need to trigger an payment proposal from F110 with reference of Document number(BKPF-BELNR ).
Stettings which I have done
Posting Date : 24.01.2005
Docs entered up to : 24.01.2005
Customer items due by : 24.01.2005
Company Code : 3000
Payment Method : C/CIT
Vendor : 3802/3803
In Free Selection
The Document Number : 190000....
I Have not selected any logtypes in Addtional Log
Printout/Data Medium
Programs : RFFOAVIS, RFFOEDI1
I have not selected any program for List
I was not able to trigger the Idoc with these setting can any one please send the configuration details in details.
It's very urgent
Thanks & Regards,
Sai Suma

Hi Suma,
Please provide the answer if you have found.
I need very urgent.
Thanks & Regards,
Manju

Need to trigger an idoc from transfer order on confirmation

Similar Messages

Maybe you are looking for