Agreement IDoc(outbound IDOC)

Hi,
I wrote for OUTBOUND IDOC.
If I execute it by entering a agreement number , it will create one IDOC .
Here my doubt is how can we know that what is the number of the created IDOC?
Help me please.

Hi,
Use we02. Give Creation Date , Time (aap), if u know message type/Basic type/ enter ,U may enter Direction '1' for outbound. It will retrieve all info 4 U !!
Reward if it is helpful.
Cheers.

Similar Messages

How to find Outbound Idoc number from inbound Idoc number.

Hi,
I have one inbound Idoc in my system, then
How to find the idoc number from the system which sends that idoc(Outbound Idoc number).

Hello
You can use fm SREL_GET_NEXT_NEIGHBORS for this purpose.
Scenario: An EDI purchase order is received by SAP-XI and forwarded as Inbound ORDERS IDoc to R/3. SAP-XI generates an (outbound) IDoc number which differs from the (inbound) ORDERS05 IDoc in the R/3 system.
Calling fm SREL_GET_NEXT_NEIGHBORS with the following parameters:
OBJECT-OBJKEY = <IDoc number, 16-digits>
OBJECT-OBJTYPE = 'IDOC'
MAX_HOPS = '99'            " <<< get all links
I get the following result:
0000000000133906                                   IDOC       CUSTOMER   OUTIDOC
0000000000407402                                   IDOC                  INIDOC
000000370383                                       BUS2012    CUSTOMER   OUTBELEG
0010057944                                         BUS2032               INBELEG
Outbound IDoc number
Inbound IDoc number (ORDERS05)
PO number
Sales order (created from inbound ORDERS IDoc)
Regards
Uwe

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

XI generates own IDOC numbers in outbound IDOC

Hello, The scenario we have is R/3 --> XI --> 3'rd party (via IDOC rcvr adapter) AND then SYSTAT back from the 3'rd party to R/3 via XI.
Example: R/3 sends an IDOC with IDOC number 100. XI (by default) submits this IDOC to the 3'rd party system with IDOC number 200 (it's own internally generated number).
Accordingly, the 3'rd party responds back with a status IDOC, SYSTAT, containing IDOC 200 in the E1STATS ==>DOCNUM field.
This is now a problem since if XI submits the SYSTAT as received from the 3'rd party, it has 200 in the DOCNUM field and this fails in R/3 since there is no original IDOC with number 200.
This can be solved if XI is able to pass the original number 100 through to the 3'rd party system (since then when the 3'rd party responds it will send a SYSTAT with IDOCNUM as 100 back, which will setup correctly in R/3).
I have gone through the other pertinent posts and none of them have this specific problem / offer a solution. I'm hoping I have missed something as this seems to be a pretty basic requirement.
Thank you for the time.
Some additional details...
- 3'rd party is non SAP.
- In the IDOC rcvr adapter we have flags 'Apply Control Record Values from Payload', 'Take Sender from Payload' and 'Take Receiver from Payload' fields checked.
- We have not checked any flags in the Rcvr Agreement.
- We are not using BPM and do not have a way to correlate the inbound 200 with the original 100 that went out.

Bhishma,
Just clarrification for you...when you said..
"R/3 sends an IDOC with IDOC number 100. XI (by default) submits this IDOC to the 3'rd party system with IDOC number 200 (it's own internally generated number)."
Here Idoc number 100 is outbound idoc from R/2 where as Idoc number 200 is inbound idoc...n they are totally different idocs..not same
I think there is work around...while mapping data from XI --> 3rd party assign / store outbound idoc in one of the unused field of inbound idoc...and while mapping back use this field to map it back...I think this will work.
Let us know the result.
Nilesh

IDoc Outbound processing

Hi All,
I am doing IDoc to File scenario. I have my IDocs in AXI system and XI in ZXI system.I want to send idocs from AXI to ZXI. I have configured the following in AXI :
RFC dest to ZXI (Dest4ZXI)
Transaction Port to ZXI having RFC dest as Dest4ZXI
Logical system for receiver file system
Partner profile for receiver file system with outbound parameter
and the following configuration in ZXI:
RFC dest to AXI (AXICLNT100)
Port to get IDoc's metadata from AXI (SAPAXI) having RFC dest as AXICLNT100
In SLD, i created a tech sys and business sys for sender system AXI and then i created a scenario in ZXI for IDoc to File. In IR, imported the idoc and created all other objects till interface mapping. In ID, assigned the business system, created a service for file receiver and created rec det,int det and rec agreement.
Using Idoc test tool i started the outbound processing after giving the data and control record and got the IDoc sent successfully message.
Control record values:
Receiver: port = (port created in AXI), partner no = (LS File receiver sys created in AXI)
sender : port = (SAPAXI - port creted in zXI), partner no = (AXICLNT100 - LS created in sld - which is same name as RFC detination created in ZXI)
If i check in we05, its green flag. But in sm58, error status message for the idoc is showing as "No service for the system SAPAXI for client 100 in Integration Directory.
Note: I am using a custom IDoc with 8 fields.
Kindly reply if my descriptions are not clear!
Appreciating all help.
Thanks in advance,
Uma

Hi Uma,
<b>Have u imported the Business System as Service or not?create u r cc in the service for that bs only</b>
If not just try with it..
If the sender system is maintained as the business service then we have to edit adapter specific identifiers and give the appropriate logical system name in the integration directory...
In ID goto Service Adapter-Specific Identifiers and mention the Logicalsystem and Client and ID...
Check this blog
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
and also
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
for refernece...
Regards,
Sridhar

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

Outbound idoc has data from previous idoc as well

Hi Experts
I am doing the goods receipt against a scheduling agreement using idocs. If this goods receipt is succesful, I am triggering an outbound idoc informing the WMS of the goods receipt. For example, if idoc number 1 comes in for GR , code has been mentioned in the inbound function module for trigger of an outbound idoc A. Please note that the difference that this isnt the case of an output type.
Now the problem that arises is , the idoc data for outbound idocs is being accumulated and sent. For example, if 1 is the GR idoc, A is the outbound idoc, then 2 is the 2nd GR idoc, then AB is the data coming 2nd outbound idoc (instead of just B), then 3 is the 3rd GR idoc, then ABC is the data coming for 3rd outbound idoc(instead of just C)
I am a little confused about the same as to which area this pertains to and would really appreciate quick help on the same.
Regards
Shubhankar

Hi,
How are you testing this functionality ? Is it using WE19 test transaction or ??
If that is the case then please come out of transaction everytime you process the idoc.
Also, clarify your scenario in more detail.
Processing of your single inbound idoc creates more than one outbound idocs or
for every inbound idoc which is processed you are creating one outbound idoc in user exit.
Also check if the idocdata internal table is refreshed once an outbound idoc is created.
If possible please send your code.
KR Jaideep,

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

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.

Consuming an outbound iDoc from a Java Web Dynpro application on EP front

Hi,
I am trying to consume an outbound iDoc from a SAP system into a Java Web Dynpro application. The result would be displayed on the Enterprise Portal. Could anyone help me with the process to be followed for the same.
Regards,
Chandrima.

Hi,
I am trying to consume an outbound iDoc from a SAP system into a Java Web Dynpro application. The result would be displayed on the Enterprise Portal. Could anyone help me with the process to be followed for the same.
Regards,
Chandrima.

Creation of Inbound Idoc for the Outbound Idoc in same client

Hi,
My requirement:
Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
I found there is a field for function module in WE21,can this be used to get the requirement done.
Please suggest.
Regards,
Amar

Example of a program that create and post an inbound idoc....maybe that will help you:
report zzinbound_idoc.
data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
data: g_edidd like edi_dd40 occurs 0 with header line.
data: g_e1bpache09 like e1bpache09.
parameter: mode type c default 'A'.
refresh: g_idoc_control_record, g_edidd.
clear:   g_idoc_control_record, g_edidd.
*-Build Control Record -*
g_idoc_control_record-mestyp = 'ACC_DOCUMENT'.   "Message type
g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
g_idoc_control_record-direct = '2'.              "Direction
* Receiver
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-rcvpor = 'SAPDE2'.     "Port
    g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-rcvprt = 'LS'.             "Partner type
g_idoc_control_record-rcvpfc = ''.               "Partner function
* Sender
g_idoc_control_record-sndpor = 'A000000002'.      "tRFC Port
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-sndprt = 'LS'.             "Partner type
g_idoc_control_record-sndpfc = ''.               "Partner function
g_idoc_control_record-refmes = 'Customer clearing'.
append g_idoc_control_record.
*-Build Idoc Segments -*
*---E1KOMG
clear g_edidd.
clear g_e1bpache09.
g_edidd-segnam               = 'E1BPACHE09'.
g_edidd-segnum               = 1.
move g_e1bpache09 to g_edidd-sdata.
append g_edidd.
*-Create idoc -*
*-Syncronous
if mode = 'S'.
call function 'IDOC_INBOUND_SINGLE'
    exporting
      pi_idoc_control_rec_40              = g_idoc_control_record
*     PI_DO_COMMIT                        = 'X'
*   IMPORTING
*     PE_IDOC_NUMBER                      =
*     PE_ERROR_PRIOR_TO_APPLICATION       =
    tables
      pt_idoc_data_records_40             = g_edidd
    exceptions
      idoc_not_saved                      = 1
      others                              = 2.
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*-Asynchronus
else.
call function 'IDOC_INBOUND_ASYNCHRONOUS'
    in background task as separate unit
    tables
      idoc_control_rec_40 = g_idoc_control_record
      idoc_data_rec_40    = g_edidd.
commit work.
endif.
write: / 'Well done!'.

Agreement IDoc(outbound IDOC)

Similar Messages

Maybe you are looking for